The days of my last running Woody are numbered… //at 23:05 //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”.

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.

Goodbye Woody, Welcome Sarge (Penultimate Part) //at 16:17 //by abe

Since security support for Woody ceased recently, and with Kazehakase I’ve found a reasonable successor in Sarge for Galeon 1.2.x, I’ve dist-upgraded my 10 years old Pentium I ThinkPad bijou to Sarge this weekend. Even the XFree86 4, which made so much hassles in Woody by not regcognising nor configuring the graphics card correctly, worked fine from scratch. Well, at least after installing xfonts-base and xfonts-75dpi — the -transcoded versions somehow gave only the error message “default font ‘fixed’ not found”.

So goodbye Galeon, goodbye GNU Emacs 20, goodbye XFree86 3.3. I hope, I won’t miss you. Only my desktop gsa at home still runs Woody, but will be dist-upgraded soon, too.

What though still stayed on my laptop from Woody is Siag Office, since there is no adequate replacement for such a nice office suite with such a low resource footprint.

But it has also an impact on the talks I hold. I held all talks with a patched version of lynx (e.g. with LSS support) as presentation tool on that laptop because initially I didn’t get X running on that box. What started as a makeshift became my hallmark…

But I didn’t manage to get Sarge’s lynx patched so that it gives me the same output as my old version did. So either I would have to reoptimise the layout of my talks for a new lynx version or just start with something new.

Madduck recently showed me python-docutils, which he uses for presentations. Maybe I’ll use that although I have a severe aversion against Python. So it may also be that I’ll stick with WML, but get some new ideas from python-docutils how to use HTML for presentations.

Update: Found out that the interesting part of his presentation technic wasn’t python-docutils but S5: A Simple Standards-Based Slide Show System which in entirely written in XHTML, CSS and JavaScript. S5 is really cool stuff, one of the first cases of useful use of JavaScript, and will surely be used for my next presentation — with Debian Sarge and Kazehakase on a Pentium I ThinkPad. ;-)

FrOSCon, COSIN und ein zu Kazehakase bekehrter Ex-Galeon-Fan //at 03:16 //by abe

Bereits zwei Wochen her, aber trotzdem nett, war die FrOSCon (Free and Open Source Software Conference), auf der ich im normalen Vortragsprogramm drei Vorträge und am Debian Day einen weiteren gehalten habe. (Die Folien zu diesen Vorträgen sind seit dem Wochenende nun auch alle online.) Wie ich schon auf schrieb (und von der Online-Zeitung doppelpunkt: der Fachhochschule Bonn-Rhein-Sieg bereits zitiert wurde), war ich von der FrOSCon recht beeindruckt: Dafür, dass es diese Veranstaltung dieses Jahr zum ersten Mal lief, war sie verdammt gut organisiert. Und trotzdem schien keiner der Orgas Stress zu haben oder liess sich diesen zumindest nicht anmerken.

Die FrOSCon hat in meinen Augen definitiv das Potential, um sich neben den Chemnitzer Linuxtagen zu der Community-Konferenz im deutschsprachigen Raum zu mausern: Eine im Westen, eine im Osten. Ich freue mich jedenfalls schon auf das nächste Mal.

Dieses Wochenende war ich auf dem nächsten Event, der (oder “dem”?) Chaos Singularity (COSIN) im Kulturzentrum Bremgarten (KuZeB), einem bisher noch kleinen, aber dennoch feinen Schweizer Hacker-Treffen, welches von den verschiedenen Chaostreffs der Schweiz, den SheGeeks und trash.net organisiert wurde.

Neben dem Wiedertreffen bekannter Namen und Gesichter habe ich auch viele neue Leute kennen- und schätzen gelernt. Ich muss auf jeden Fall auch mal den Zürcher Chaostreff besuchen.

Und natürlich habe ich auch wieder mal einen Kommandozeilen-Workshop mit Lynx als Präsentationsprogramm auf meinem Pentium-1-ThinkPad bijou (ein Restaurant um die Ecke hieß witzigerweise genauso) gehalten, der anscheinend, wie im Rückblick behauptet wird, dafür sorgte, daß »einige der Besucher […] in bisher nicht gekannte Sphären ihrer Shell eintauchten«. Beeindruckend beim Workshp war für mich, daß extrem viele Zuhörer mitdachten, interessante Fragen stellten und z.T. auch gleich selbst beantworteten. Der beste Dank an den Referent war aber auch hier wieder die leuchtenden Gesichter von Spielkindern, die gerade ein neues Spielzeug gezeigt bekamen. :-)

Direkt nach dem Workshop bin ich noch mit Folken ins Gespräch gekommen und er hat irgendwann zwischendrin mal über Webbrowser geflucht und als in diesem Bereich in der Zwischenzeit sehr sensible Person konnte ich nicht anders und etwas in der anscheinend noch offenen Wunde herumstochern: Und siehe da, ein weiterer Galeon-1.2-Fan, der von Galeon 1.3 und von Epiphany und Firefox erst recht massiv enttäuscht ist. Während ich über viel Konfigurationsgerödel mit gconf-editor und anderen wilden Sachen meinen Galeon 1.3 einigermaßen gefügig machte, bis ich Kazehakase entdeckte, ging er einen wesentlich radikaleren Weg: Er stellte auf links2 im grafischen Modus um. Als ich ihm dann nach etwas Zappeln-Lassen Kazehakase und die wichtigsten Einstellungen (UI-Level auf “Expert” setzen) zeigte, gab es ein zweites Mal an diesem Abend leuchtende Augen. Wieder einen zum einzig wahren Browser™ bekehrt. ;-)

Sehr gut war auch noch das Essen (Dank an Beni vom KuZeB!) und sehr nett auch noch die abendliche Beschallung mit Welle-Erdball-SIDs von einem echten C64 aus. (Deswegen einen anlachen werde ich mir trotzdem nicht. :-)

Und da Venty ja dieses Wochenende im Triemlispital lag, hat er mir für diese Zeit sein TomTom zur Verfügung gestellt. Für die Hinfahrt war das ganz nett und funktionierte wunderbar, aber auf der Rückfahrt (mit tiCo zusammen zum Triemlispital um Venty zu besuchen) hat es uns sooft fehlgeleitet, daß wir per Landkarte vermutlich schneller gewesen wären, weil ich mir dann den ganzen Weg einmal im Voraus angeschaut hätte und nicht nach jeder vom TomTom fehlgeleiteten Kreuzung erstmal rätseln mußten, was jetzt schon wieder schiefgegangen war und wo wir wirklich hin sollten. Mal ganz davon abgesehen, daß eine Ente mit Navigationsgerät doch schon sehr komisch anmutete und Landkarten da einfach stilgerechter sind. ;-)

SuSE sucks! //at 02:24 //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…

The World without a sage web browser? — or — Why Firefox sucks //at 11:44 //by abe

Although I read our Debian’s Joey’s blog posting about not being able to produce Mozilla security updates for Debian, only now, after reading about other Debian’s Joey’s try to fix a security hole in Debian’s Mozilla Firefox, I see how asshole-like the Mozilla Foundation’s security policy looks to Linux (and maybe other operating system’s) distributions, who favour stableness over feature richness.

As many know (or at least were forced to know ;-) I don’t like Firefox, because in spite of all the plugins it can’t cope with all the useful features of Galeon 1.2.x or Opera. That’s the UI point of view.

But from the political (correctness) point of view, we have to ask ourself: What sage browser does the open source world still have?

• Mozilla does not provide security patches, so Firefox, Mozilla (RIP), Epiphany and Galeon are no more acceptable for distribution use.
• Konqueror has planed to drop KHTML in favor of Mozillas Gecko. So see above.
• Dillo’s rendering engine is fast but not really state of the art. Same counts for glinks (aka “links -g”).
• Lynx, links and w3m somehow don’t count since the distributions (and sometimes, me too ;-) primarily need a graphical web browser.

But back to usaility: I heard from quite a few people — even open source people — evaluating or even already using Opera as an alternative, because there is no sage open source web browser, even if you don’t count Mozillas security policy. And I can understand them. If Galeon wouldn’t exist, I probably would be a convinced Opera on Debian user myself, although Opera is closed source. But I and many more can’t live without a working and sage web browser.

The only thing, I don’t like with Opera is that this company seems to be (or at least was a few years ago) very chaotic and uncoordinated. (And I really wonder, how they are able to produce such impressive software.) But that’s another story…

X on IBM ThinkPad 760ED //at 02:39 //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.