Archive 7. June 2005

Clement will ALG-II recipients to be more strictly controlled

Owl Content

Clement will ALG-II-Empfänger schärfer kontrollieren and make social workers into agents. They are supposed to monitor benefit recipients more closely and snoop around after them. Because, of course, our biggest problem is not the 4.8 million missing jobs and not the thousands of further job cuts every month, but the few people who claim their household as a community of need.

And so the myth is further fueled that the problem is solely the unwilling and fraudulent unemployed. In Clement's eyes, it's all just scum, while he naturally vehemently defends himself against attacks on the economy he so loves.

And we can be sure that Clement will not have to receive unemployment benefits even after the defeat of Red/Green, because he has his share in the dry ...

Podcasts and the Governor

Arnie podcasted: Welcome to California. What the hell.

Supreme Court makes supreme blunder

morons.org - Supreme Court makes supreme blunder - in America, the state can take action against people who use marijuana for medical reasons (pain therapy for end-stage cancer, for example). Even if the marijuana is prescribed by a doctor. And this was not just some backwoods court that made the decision ...

System upgrade on simon.bofh.ms

Since I need to upgrade a Debian 3.0 to 3.1 somewhere to gain some experience for the company, I'm just using my own server. So, it might be that things get a bit messy here in the next time or something might fly around your ears. You have been warned.

System Upgrade simon.bofh.ms Part 2

Ok, the system upgrade is basically done. The only losses so far are the mailing list system - although that's mainly because I simply have no interest in running it anymore. In principle, it was completely updated, I just threw it out because I don't want to do anything else with it - there was only one list in it. And otherwise, mainly old junk has been thrown out.

However, after two system upgrades, I have to say that I'm not really enthusiastic about this upgrade - it already shows the problem of the extremely long release cycle. The first upgrade went through quite smoothly - the machine in question was one that already ran Sarge, just an old version from Testing and not the current Stable. The upgrade caused no problems.

The second upgrade, however, was simon.bofh.ms - a machine that was still largely on Stable, with a whole range of backports (self-made and from the net). The latter is of course the real problem - because the release cycles are very long, it is often necessary to install packages yourself. The Debian upgrade mechanism should still handle this. But reality shows that packages from backports often refer to intermediate states in which bugs in testing packages are present or simply special features that were not taken into account. As a result, a whole range of package upgrades were very tricky and I would not want to subject any normal user to going through that.

The highlight of all the problems was the PostgreSQL upgrade, which went through cleanly but then did not start due to an outdated option in the config. The messages were so cryptic that even I could not immediately see what it was - only digging in the logs and looking in the scripts confirmed to me that the upgrade was clean and really only the start had jammed.

However, I still have to say that the upgrade of a machine with partly up to 3 years old program versions went surprisingly well and 99% of the packages were updated completely problem-free - even things like my rather exotic Exim4 installation (a self-made backport with special features) went through quite smoothly - manual fixes were necessary, but I had caused them myself. The Apache and the whole PHP mess ran completely problem-free, the MySQL database also ran immediately. And one should also note that the whole upgrade - although described by me as suboptimal - only took 1:45 hours. And most of that was waiting for the packages to unpack ...

Well, in the next few days it will show what else has broken and which of the scripts no longer run that I have overlooked so far.

The Transporter

Three men, 254 kilos, that was the deal!

WebKit, WebCore and JavaScriptCore - Open Source

Surfin' Safari reports that WebKit (the Objective-C API for the Safari renderer), WebCore (the base code) and JavaScriptCore (the base code for the JavaScript implementation) are now open source. With CVS repository and public bug tracking system.

Ultimately, this is of course a fork of khtml and kjs, but by disclosing the sources, everyone can now freely use each other's code and thus the problems between the projects should be off the table for now. Contributions are also to be accepted.

WebObjects Part of XCode 2.1

In the WebObjects 5.3 Release Notes I saw and immediately checked: WebObjects is now part of the XCode 2.1 (available for ADC members) distribution. I downloaded the over 700 MB and checked: yes, there is a WebObjects.mpkg in it. Quite strange, because so far WebObjects was not a cheap package - is now the whole deployment free, or do you still need some kind of runtime for the generated applications that then costs money again?