synergy of loxal

Messed up with Subversion and want simply a clean restart? You can have a clean slate by executing this command which is actually a one-liner shell script in the directory you want to clean from Subversion folders containing its metadata by deleting all directories named ".svn".

The corresponding magic all-answering Ant man page tells that you can increment the build number using the directive. If you insert this directive directly after the opening project tag of your build.xml file, the build number will be increased, every time any of the targets in build.xml are executed. In this way you can increment e.g. the minor version of your build and have not to write a custom extra task.

You can also specify a custom "build.number" file with You can also limit the scope of the buildnumber directive by putting it only into a specific target.

Mathematics is about solving traffic problems and computer science is about translating these problem solutions for machines. (These machines have not necessarily to be only digital computers but may be also mechanical machines!) The problems mathematicians and computer scientists are dealing with are of formal nature. Understanding web evolvement is a complex problem. Solutions for problems that come along with web evolvement, have to be of formal nature as they must be understandable for computers. But to find formal solutions for complex problems, you have to be rather a complexity expert than a formalism expert.

The U.S. government support of bankrupt financial institutions like Freddi Mac, Fannie Mae, and AIG will cost the tax payer billions of USD (overall cost of one trillion USD). After the financial support was announced the global markets realized the highest one-day growth since years. As far as I know, this is biggest financial intervention of the government in the U.S. history. The short-term and mid-term effect of this gigantic money injection will becalm the markets and will prevent the really big stock market crunch from happening. But the long-term effect on the market is much more fatal as this support remains an intervention of the government in the market proceedings and as such it is also a disruption of the natural structure and procedures of the market ecosystem. And this ecosystem as every other (also natural) ecosystem is dominated by the principles of evolution. One of this principles is: Inefficient or unadjusted concepts and entities have to vanish in favor of their more adjusted and more efficient competitors; the unadjusted and inefficient entities have to die as justice have to be respected! If this evolutionary justice principle is consequently ignored, the whole system became successively uncompetitive, inefficient, and weak. The long-term result: Not only the respective system dies in an everything-in-it-destroying gigantic big crunch but damages also all other systems that interact with it.



"The current system is all about privatizing profits and socializing loses."

Many people hate the caps lock key as the accidental activation of the "caps lock" mode disrupts regularly the workflow. Entering

in the console will deactivate the "caps lock" key for the respective user and session. If your want to permanently ban this devil's handiwork from your keyboard layout you should reconfigure xserver-xorg

and when you are at the point where your can enter the "Keyboard options", you should enter

Also if it cannot be recognized at first glance, this blog is hosted by Google's Blogger blog platform. But where is the Blogger-typical navigation bar and its favicon? To remove the navigation bar you have to edit your Blooger template and add this magic line
as the very first tag directly after the opening "body" tag. To inject this hack, you have to choose "Edit HTML" in the "Layout" tab of your Blogger administration panel. This line simply tells the browser not to display the HTML element with the ID "navbar-iframe" wich is actually the HTML tag ID of the iframe containing Blooger's navigation bar. As now you cannot login using the link on your blog's navbar, you have to sign in using the Blogger's secure login site.

To change the default Blogger favicon, you have to add this line
to the HTML "head" section of your Blogger template. Whereas the "href" attribute should contain the URL of your favicon. Thereby href shoud not be set simply to "favicon.ico" as it would point to Blogger's default favicon.

Building Chromium, the raw version of Googles state of the art browser Chrome under Linux x64/x86_64 the following error occurred



as there were no x86 libraries. Installing these libraries solved the problem for me:

This is a known bug in Ubuntu/Hardy that have caused many nasty error messages during several operations. The defective package responsible for this bug is findutils. As there is still no fixed findutils package in Hardy, I took the package from the upcoming Ubuntu release Intrepid. To do so, you have to do the follwing steps:

and tell Vim to replace all occurrences of the "hardy" string by "intrepid":

Now you should have the sources.list of Intrepid.

...installs the fixed Intrepid findutils package.
Change the sources.list back to the Hardy revision:


Now you should have the fixed version of the xargs command, which can be used in one-liners like:

which showed me the following information:


So I have searched for the string "Name[ru]" in my Desktop directory and got the corresponding file name with the line number containing this string. ...also a really nice example for the expressiveness of the cmd line UI.

Many technology enthusiasts think that with Chrome Google sound the bell for a new era of applications. In fact the popularity momentum of this bleeding edge technology using browser is just amazing. On the other hand many other tech enthusiasts think that this is just another hype nobody needs. One of these skeptics have wrote an article with three really nice models describing the difference between software of yesterday and the software of tomorrow.



Inspired by these impressive models, I have remembered an article, I wrote one year ago. This article described the evolution of software on the basis of LVM. Hereby LVM was characterized as just a further abstraction layer that offers capabilities to manage complex file system setups and which can -- in certain circumstances (but not necessarily!) -- simplify the management of complex data storage facilities: Such technologies enable to manage the progressive complexity which is a (positive correlating) predicate of evolution.



So the "Fuck" label on the last model indeed shows that also techies have emotions but is also quite imprecise! I would label the last model more precise: Evolution!