SuSE sucks! //at 05:44 //by abe

Since SuSE closes the security support two years after release and the recent KDE JavaShit remote code execution hole wasn’t patched as fast as I would have expected it (the patch came out after the upgrade I’m writing about here) in the SuSE 9.0 which was installed on my 2.66 GHz AMD desktop at work (it started as in 2002 as a SuSE 7.3 on a 400 MHz box and has been upgraded since then to 8.0, 8.2 and 9.0 IIRC), I decided, it’s now really time to upgrade to SuSE 10.0. (Although 10.1 will be out soon, I just don’t want to wait for it.) And since my boss only wants SuSE boxes and neither Debian (which I would prefer) nor Gentoo (which a colleague prefers), I couldn’t simply install Sarge on this box although I would have chosen that option if it would have been available.

Since my former SuSE experiences told me that this would mean a lot of trouble, I took notes from the beginning, once for the blog and once for my boss to show him, that most trouble doesn’t come from me being a power user used to being allowed to touch any config file (like I am on Debian).

Preparations

So I begin with the preparations: Starting the 400 MHz Debian Woody box on my desktop (whose operating system is more than a year older than SuSE 9.0 and still has security support, yeah!) I usually need to build custom Debian packages for customers. There I could chat in IRC and took notes while trying to upgrade and get the whole thing working again.

When everything was ready, I put the SuSE DVD in — just to notice, that it’s just a CD-ROM. So I put the SuSE 10.0 CD1 in the CD-ROM drive and typed “sudo shutdown -r now” in the shell. The box starts shutting down and tells me:

Please stand by while rebooting the system…

But it didn’t reboot. I waited for several minutes, nothing happend. Well, seems as if the SuSE upgrade already starts as I expect it to end: Horrible.

Read more…

abe@debian.org //at 02:02 //by abe

On Wednesday I got DAM approval and since Saturday late evening I’m officially a Debian Developer. Yay! :-)

My thanks go to

• Christoph Berg (Myon) whom I know for more than a decade since we studied together, and who’s career in Debian was way faster than mine, but who on the other hand probably knows me better than nobody else in Debian — which made him the perfect advocate;
• Bernd Zeimetz (bzed) whom I know from my times at DaLUG and who was the friendliest Application Manager I could imagine — he’s probably also one of the fastest (8 days from application to AM report :-);
• Luca Capello (gismo), who was the most demanding but also most inspiring sponsor I ever had and who became a very good friend after we found each other over my package conkeror.
• Arne Wichmann (Y_Plentyn) for being my first drop-in center for Debian questions (like “can I directly dist-upgrade from 2.0 to 3.0?” :-);
• Martin Zobel-Helas (zobel) who was always encouraging me to continue exploring new sides of Debian;
• Gerfried Fuchs (Rhonda) just for being there (and for being a package maintainer with good relations to upstream ;-);
• my coworkers at the IT Services Group of the Department of Physics at ETH Zurich, who always found new challenges in Debian for me to solve;
• … and all those others who offered to also advocate me (e.g. Otavio Salvador) or sponsored my packages so far (or at least offered to do so), e.g. Alexander Wirt (formorer), Martin F. Krafft (madduck), Robert Jördens (jordens), …

As Bernd cited in his AM report, my earliest activity within the Debian community I can remember was organising the Debian booth at LinuxDay.lu 2003, where I installed Debian 3.0 Woody on my Hamilton Hamstation “hy” (a Sun SparcStation 4 clone).

I wrote my first bugreport in November 2004 (#283365), probably during the Sarge BSP in Frankfurt. And my first Debian package was wikipedia2text, starting to package it August 2005 (ITP #325417).

My only earlier documented interest in the Debian community is subscribing to the lists debian-apache@l.d.o and debian-emacsen@l.d.o in June 2002.

I though remember that I started playing around with Debian 2.0 Hamm, skipping 2.1 (for whatever reasons, I can’t remember), using 2.2 quite regularily and started to dive into with Woody which also ran on my first ThinkPad “bijou”. I installed it over WLAN with just a boot floppy at the Chemnitzer Linux-Tage. :-)

Anyway, this has led to what it had to lead — to a new Debian Developer. :-)

The first package I uploaded with my newly granted rights was a new conkeror snapshot. This version should work out of the box on Ubuntu again, so that conkeror in Ubuntu should not lag that much behind Debian Sid anymore.

In other News

Since Wednesday I own a Nokia N900 and use it as my primary mobile phone now. Although it’s not as free as the OpenMoko (see two other recent posts by Lucas Nussbaum and by Tollef Fog Heen on Planet Debian) it’s definitely what I hoped the OpenMoko will once become. And even if I can’t run Debian natively on the N900 (yet), it at least has a Debian chroot on it. :-)

A few weeks ago, I took over the organisation of this year’s Debian booth at FOSDEM from Wouter Verhelst who’s busy enough with FOSDEM organisation itself.

Last Monday the organiser of the BSD DevRoom at FOSDEM asked on #mirbsd for talk suggestions and they somehow talked me into giving a talk about Debian GNU/kFreeBSD. The slides should show up during the next days on my Debian GNU/kFreeBSD talks page. I hope, I’ll survive that talk despite giving more or less a talk saying “Jehova!”. ;-)

What a week.

The days of my last running Woody are numbered… //at 21:29 //by abe

As many of the Planet Debian readers know, I bemoan Galeon 1.2 and therefore Woody. For a long time I haven’t found an appropriate browser replacement for Galeon 1.2 in Sarge, so I never switched my home workstation called “gsa” (Pentium II, 400 MHz, 572 MB RAM) to Sarge, since Woody was rockstable and just worked.

Though, after a few Galeon 1.3/2.0 rants, someone pointed me to Kazehakase, which indeed is a fine Galeon 1.2 replacement. But I noticed that Kazehakase in Sarge was in an early stage and the Kazehakase from testing (now Etch) were already much more matured.

So in comparison to Sarge with Etch I won’t have the problem of not having a mature and sage web browser in main. And due to security support for Woody ceased a few months ago and Etch is now declared stable, it’s time to reinstall my last Woody box with Etch.

For that, a repartioning of it’s two hard disks (8 GB and 40 GB) sounds like a good idea and so I had look, what’s on all those partitions where I once had a shot on quite a few Linux distributions and other unix-like operating systems. (Although I was already a big fan of Debian at that time, I wanted to look over my own nose and ordered a few CDs of free operating system at LinISO.de.)

So here’s what I found, never really used and will throw away quite soon:

• RedHat 9
• Mandrake 9.2beta2
• FreeBSD 4.8
• OpenBSD 3.3
• one more, not yet identified (or perhaps even never formatted) Linux partition

That should give enough space for an Etch installation without touching the Woody installation first. Thanks to Venty, I’ve got a DVD drive for that box, so I can install from DVD.

And for toying around with all those other neat and free operating systems nowadays, I’ve got my MicroClient Jr. named “c2”.

Goodbye Woody, Welcome Etch //at 10:54 //by abe

It finally happened. I installed Debian Etch on my last Woody box, a 400 MHz Pentium II with 576 MB RAM named gsa which is my home desktop since I bought it at LinuxTag 2003 in Karlsruhe.

And no I didn’t do a dist-upgrade, neither direct no via Sarge. As already planned I removed some no more necessary operating systems from that box and installed Etch on the freed disk space. Woody is still installed on that box in parallel and was recognized perfectly by Etch’s installer.

I took a few hours but also was big fun to go through Etch package list and to decide what to install. Overall the installation of 5 GB of software took about half a day.

In general everything went fine, the only thing I’m yet missing is sound. Etch didn’t seem to recognize my soundcard at all although it’s a well-known brand and defacto standard for many other soundcards: a Creative Labs Soundblaster. Well, the 16-Bit ISA version, needing the full length of the slot. Worked fine under Woody. Well, I hope I’ll get it working again manually.

What on the other hand is really nice with udev hell —eh— hal and all those new automatic bells and whistles: The desktop (well, at least GNOME Nautilus as well as XFCE, but probably also KDE) recognises when I insert a 3.5” floppy into the drive and shows me a nice floppy icon on the desktop. You think, that’s impossible? Floppy drives don’t inform the rest of the system when a floppy has been inserted without you polling the drive every few seconds? Well, USB floppy drives can. And they do. :-)

I still need time to migrate all the old settings from Woody to Etch. I’ll probably stick with FVWM, but perhaps will use the GNOME enabled version. What’s already done is the migration from tcsh to zsh. On all new or dist-upgraded systems after Etch I’ve chosen zsh so with my last Woody installation retiring I’ve also fully migrated to zsh.

So I’ve got now most of my active private boxes running Etch. Only the noone.org web and mail server “sym” (an amd64 box) as well as my 133 MHz ThinkPad “bijou” are still running Sarge, both with 2.6 kernels.

So with switching to Etch on gsa, I also got no more Debian box running a 2.4 kernel. The only 2.4 kernel I run is on my FreeWRT WLAN router named pluriel, which runs 2.4.33.3. But I expect that 2.6.18 will be as stable and long lasting as the famous and rock-solid 2.4.18 from Woody. 18 seems to be Debian’s favourite kernel minor version recently. ;-)

VCFe talk online / bijou vs Etch //at 00:52 //by abe

With a few days lag, the slides to my VCFe 8.0 talk Aktuelle, freie Software auf alter Hardware (“Up to date, free software on old hardware”, held in German using Kazehakase and S5) are now online. In comparision to my former talks on that subject (held at some DebianDays), this talk was not Debian focused but focused more on not so well known, but resource-friendly free software as well as focused on an audience which has more knowledge of old hardware than of current software. :-)

Additionally, I updated my old blog post about X on my ThinkPad 760ED named bijou so that now also my current XF86Config-4 for Sarge on that box is linked in there.

Apropos bijou: I couldn’t recommend Debian 4.0 Etch that much for old computers with not so much memory since especially aptitude has grown much in regards of it’s memory and performance needs. Regarding my experiences with Etch, any computer with less than 50 MB of RAM will start to swap if aptitude is only started on such a box. I’ve looked throough the aptitude documentation, but I haven’t found a way to switch of some of the tables it generates internally. E.g. I have no need for the tag database it always generates. I really would be happy, if someone knows a way to turn even only that feature off. Then I may dist-upgrade bijou to Etch, since I found that dselect is no real alternative to aptitude anymore.

Oh yeah, and I of course bought new old hardware at the VCFe: A 386SX Thin Client named Flytech Carry-I 9300 from 1991 with about 200 MB of harddisk and 10 MB of RAM.

X on IBM ThinkPad 760ED //at 00:13 //by abe

As many of my friends know, I installed Debian GNU/Linux 3.0 aka Woody on my IBM ThinkPad 760ED (Pentium 1, 133 MHz, 48 MB RAM, 1 GB HD) named bijou at Chemnitzer Linux-Tage this spring. Although many helped me trying to configure X, I didn’t get rid of the LCD “forgetting” more or less pixels each row so that the picture got blurred towards the right rim.

During Berlinux, a not so convinced Linux user (he told me he likes the feeling of Windows, but got stick with Debian because his modem just didn’t work with Windows) told me that he had similar problems with a graphics card with similar chips as the ones in my ThinkPad. Since I never was sure, if my problem is a hardware defect, a driver or a configuration problem (but I tended to hardware defect or a not supported chipset, since I read about several Trident 96xx and 98xx chipsets to be unsupported under Linux), his comment was a ray of hope to me. He told me he found the solution on Werner Heuser’s TuxMobil website, whom I showed my X problem also Berlinux but who hadn’t an idea what it could be. He also told me, that XFree86 4.x doesn’t support this graphics chip, but XFree86 3.3.x does.

But somehow I had forgotten that TuxMobil not only has informations about Linux on laptops but also a big bunch of links to pages which deal with specific models. I can’t remember, if I looked there already back in March, but it felt like I didn’t although my own small text about bijou is linked there, too. I looked through the other 760/770 ED/XD pages and on the second or third I found someone who seems to have had the same problem and also with a 760ED. He wrote, someone else has gone down that path already so he linked directly to the XF86Config he found elsewhere. That sounded like an easy earned money so I followed the link — 404. Shit! For luck a few lines down he linked also his own XF86Config, so I grabbed it, uncommented everything unnecessary and put in the essential parts of his XF86Config of which the most important parts probably were the modelines. The one for 1024×768 was commented as the only one working, those for 800×600 and 640×480 were commented out. Then I downgraded X to XFree86 3.3.6.

It didn’t work as expected. The display stayed black which was less than I had accomplished before. Shit! But giving up is not my style. So first I reduced the color depth. No change. Then I started with reducing the resolution. With 800×600 and 16 bit color depth, it finally worked. No hardware defect, no unsupported graphics chip. Just not the right modelines. That was all. YESSS!

I guess the guy whose XF86Config I used didn’t have a 760ED but a similar model with a LCD with higher resolution. because my 760ED definitely has no 1024×768 resolution because 800×600 fills the screen completely.

Still leaves the problem with the svgalib: The system just freezes with a black screen if I start a svgalib application like e.g. zgv. First I found out, that svgalib indeed has a configuration file which (at least under Woody) can be found at /etc/vga/libvga.conf. Copied the modelines from the now working XF86Config, configured the mouse and tried again. Freeze. Hmmm, in the config there is mentioned that if svgalib doesn’t correctly recognise the graphics card’s chipset, you can hardcode it with a configuration directive, e.g. “chipset VGA” for otherwise unsupported chipsets. And that worked, although only with 640×480 yet. So I tried the only setting for Trident cards found in the list of supported chipsets. And what happend? Right, the system froze again. So svgalib probably recognised the card as Trident and used the only available Trident driver which was obviously the wrong one. So here are my XF86Config and my libvga.config working on the IBM ThinkPad 760ED.

But nevertheless — this 0€ laptop has just proven that it can be even more useful than it already was with text mode only. I also already played Frozen Bubble up to level 25 or so on the train back from Berlin. Old hardware rules.

But I now also have another problem (again): Since X works now, I can run Galeon 1.2 on the ThinkPad, but GTK 2 respective GNOME 2 are much slower than in the 1.x versions and also need much more ressources, which the laptop just does not have. And since I — as most of the people who read my blog or Planet Debian should know ;-) — don’t like Galeon 1.3, I probably won’t dist-upgrade my ThinkPad to Sarge that fast although I already thought about it. XFree86 3.x isn’t in Sarge either IIRC but this should be no problem since the Woody packages are said to work under Sarge, too. Well, still yet another reason for forwardports.org… ;-) Or maybe I can get Kazehakase running on Woody so I can drop at least the whole ballast GNOME 2 comes with. We’ll see…

JFTR (Update on 2nd of May 2007): My current XF86Config-4 for Sarge on my ThinkPad 760ED named bijou.

Surfing on two screens? //at 22:31 //by abe

At work, I’ve got two screens on my Sarge workstation “snitch”. Since I want to switch virtual desktops independently on both screens, I don’t have a Xinerama setup but a Dual Screen setup. So my left and right screen do have different $DISPLAY (“:0.0” and “:0.1”) set.

This is neither a problem for FVWM nor xlock nor XScreenSaver. But it is a problem for nearly every modern web browser available which checks, if there’s already an instance of it running. So if you try to start a new instance of a web browser on the other screen, most graphical web browsers make more or less problems:

• Galeon 1.3 and Epiphany always opens new tabs or windows on the display where its first instance is running, i.e. ignores $DISPLAY completely except on the first call.
• Kazehakase (0.3.7) just opens a new tab in the running instance.
• Firefox 2.0 thinks it crashed and asks if it should restore tabs and windows. Haven’t tried any further.
• Opera 9.20 pops up a dialog, says, there seems already a copy of Opera running and asks if it should continue with startup. If you say yes, only the bookmarks of one of the two instances get saved, probably those of the one with the last added bookmark or the one which exited last.

The only graphical web browsers which simply just work on a Dual Screen setup are Konqueror, Links2 (called with the -g option for a GUI), Chimera 2, Amaya and of course Dillo. Unfortunately I’m neither a fan of KDE nor of Konqueror and I do want a web browser with CSS and tab support… And Amaya is, well, only a reference implementation… (Chimera 2 from Sarge btw. segfaulted on two of the four pages I tested it with. Seems to have problems with PNG images.)

So my current setup is to have Kazehakase as my main work web browser (with all the local web applications I need) on the right screen while I have Opera on the left screen for surfing, looking up documentation, testing web pages and other things.

BTW: I don’t use Gecko based browsers for surfing on that box at the moment, since there are some web pages (the spammer vandalised Kazehakase wiki for example, at least a few months ago) which manage to be rendered in such an ugly way by Gecko so that XFree86 with the binary Nvidia (at least the last five or six versions I tried) just crashes away — either at once or when you try to switch to a text console by pressing e.g. Ctrl-Alt-F1 while such a page is displayed.