A view from the hill - Linux

GNUPG and locale weirdness

nospam@example.com (Holger Schauer) — Sun, 16 Jan 2011 17:19:43 +0100

Today, I solved a really troubesome problem for me: I couldn't access my GPG secret key. Which means that whenever I needed my secret key, for example when I wanted to sign some text and I typed in my key, I just received a "bad passphrase" error message. Not using GPG on a regular basis, I wasn't at all sure that I had used the right passphrase. However, today I recognized that I had another secret key for special usage, for which I had specifically written down the passphrase -- and which didn't work as well.

This finally convinced me that there was something else wrong beside a faulty memory of the passphrase. And indeed, when I tried signing a mail in Gnus/PGG, typing in the exact same passphrase as I had on the command line, everything was fine and the message got signed. But then what was the difference to using gpg from the command line? I was suspecting that some non-ASCII characters I have in my passphrase might not reach GPG as intended, so I started looking at the locale settings. Some more experiments confirmed it: nowadays, my xterm (which is an lxterm really) is highly probably using a different key setting as it used to, after a re-installation of my desktop some time ago. I'm not too sure what it used to be, probably ISO-8859-1 (aka Latin-1) or ISO-8859-15 (aka Latin-9) or "C", but it's now using de_DE.UTF-8. Simply setting LANG to C inside a running xterm didn't work out as I hoped, probably because of the way the locale settings (probably LC_CTYPE) are used by xterm to set up keyboard handling. But when I start up a different xterm with LANG set to C in advance, i.e. do a "LANG=C xterm &", gpg happily accepts my passphrase. Problem solved.

Moral of the story: charsets and input formats are a constant source of joy unless everything is unicode.

Every planet we reach is dead

nospam@example.com (Holger Schauer) — Thu, 29 Jul 2010 21:02:00 +0200

When I bought a new workstation some time ago, I made sure it would have much more power than I would probably need. One reason for this was that I wanted to toy around more with virtualization. I had successfully used VMware server on a comparingly weak laptop some time ago, but opted to try out the more recent open source solutions. I looked briefly at VirtualBox but that seemed to be very similar to VMware which I already knew, so I didn't really pursue this path. Xen had caught my interest for quite a while, but it looked to me as not to straight forward to setup and as of not-so-recent time, KVM seems to be the new kid on the block that nearly everybody seems to see as the more natural solution for linux users.

What got me going was that I wanted to take a look at how far Debian Squeeze had already got. In particular, I wanted to try the amd64 bit variant, but as I quickly discovered that requires a 64bit host installation. So, off I went, re-installing my lenny system to be 64bit instead of the original 32bit system I had been using up to then, thinking that I could easily re-establish that 32bit system as a virtual system on top of my 64bit host. The general idea was to have a relatively clean host system with several guests for developing, surfing and working running on top of it.

Given the considerations above and that Debian ships with easy to install KVM packages (see the debian wiki on KVM for details), that was the way I choose. In particular, I installed the KVM and qemu packages as well as virt-manager, a graphical frontend to manage virtual machines. And sure enough, setting up a first virtual machine really looked easy: click a few buttons, decide on a few things like image size and feed the machine an installation medium of the OS to boot. For this installation medium, I choose a squeeze netinstall image. However, as I soon discovered, the squeeze guest couldn't see/access the net on boot. No problem, I thought, I'll fix it later on. Unfortunately, though, it turned out that although virt-manager claimed to provide a network card, dnsmasq and stuff was running, the squeeze guest wasn't able to see the outside world -- which is, of course, quite problematic when the guest requires network access to complete installation. The guest was provided a network interface, but it wouldn't recive an IP via DHCP and even setting routes manually didn't allow to access the net.

So I thought, maybe updating the host to squeeze might help -- as the host has a real small and lean installation, this was neither problematic nor taking much time. This time, with the new KVM and virt-manager packages in squeeze, again I had no net on installation, but I had success with regard to the network access afterwards, so I could happily install a complete squeeze system in the guest. Update:What I forgot to mention was that I fiddled around with the available virtual networks with virt-manager, adding a new network. As I recognized that the guest was using the provided default network, I deleted the additional one and re-enabled auto-start on the default one. This, however, doesn't really work: whenever I startup virtmanager, I have to manually restart the virtual net, now (no, virsh net-auto-start didn't help) and worse, I have to first manually add an iptables rule (that then gets deleted on start up of the virtual net) and restart dnsmasq. Sigh

Afterwards, I turned to re-install my private data in the guest which I had previously copied to an external USB drive. This turned out to be a bad idea. First of all, you can't easily assign new hardware to a running virtual machine -- you have to startover the guest. But second, and much more problematic, was IO time. Looking at iotop, I saw an average data transfer of 500k/sec with reads from the USB disk, which means copying a single gigabyte would nearly take forever. Compared to copying the same data from the same disk on the host, iotop showed an average of 31M/sec! I haven't as of yet tried to verified that the problem is accessing the USB or if a similar problem exists with accessing "local" disks (i.e. reading/writing to the virtio disk/image is equally slow). If it's only USB access, the problem is a lot smaller in everyday usage, but still this experience was a real disappointment. Update:In the meantime I've verified that the problem is reading from the USB disc. Reading and writing to the guest virtio filesystem is, of course, slower than IO on the host, but it's not that huge a difference.

But that's still not the end of the story. Given that I really wanted to more or less live inside my guests, I also wanted to use multimedia stuff there. That this idea might turn out to have restrictions with regard to video performance was clear to me from the beginning. However, I didn't expect that I might have trouble to have audio. It looks like the problem is best summarized in this ubuntu bug report on virt-manager and vnc: while qemu/KVM of course can hand over audio to the host, this fails when using virt-manager with VNC because the vnc viewer virt-manager is using doesn't handle audio. There are ways around this, for instance Russel Crockers advise to use Xephyr, but this a) takes even more time to setup and b) takes away the bit of comfort of using virt-manager.

So, in summary, using KVM as provided by Debian Lenny and or Squeeze turned out to be quite a disappointment. I would go so far and claim that it's not really recommandable unless you're willing to invest a substantial amount of time. I've had my fair share of trouble with VMware, too, but getting things up and running was never so troublesome as this.

ObTitle: Gorillaz, "Demon Days"

Men in love

nospam@example.com (Holger Schauer) — Wed, 27 Jan 2010 11:23:16 +0100

When I got a Handspring Visor (a Palm Pilot offspring) roughly ten years ago, I was amazed about all the nice things you could do with the device. I even wrote a German version of the visor linux howto, although I never really finished it. What I especially liked was the possibility to install a ssh client and use it to connect on the push of a button to my workstation -- which I took to good use several imes when my Xserver went beserk. Unfortunately, over time the major incentive to use the thing, syncing calender and address book vanished, as it turned out to be a major hassle when the main calendar to sync with was Lotus Domino. So, since some years my trusty Visor has only gathered dust. But even back in 2000, it was clear to me that the Palm Pilot would only be the starting point and that at some time in the then-unknown future, we would have small devices that would allow issuing phone calls, taking pictures, listening to music as well as providing the "usual" features of handhelds.

Back then, I didn't really think about when exactly that device would arrive but I think the time has come finally. Some days ago I bought a Nokia N900, which is a mobile device running Maemo on top of a Linux kernel on an ARM platform (see this overview of the hardware for more details). This is really a neat little gadget which is really as close to my ten year old dream as you can get: It comes with mobile phone capabilitiy, UMTS and wlan connection, 5MP camera, media player, RSS feed reader, etc. and also has a quite usable sliding keyboard. It's not really a mobile phone but a pocket computer which you can also use to call people with, which shows for instance in that most applications require the device to held in landscape position.

Of course, what's most interesting to me is the software on the device. Basically, Maemo 5 is a linux distribution based on Debian technology, e.g. apt/dpkg and friends work as expected. You don't get all of your favourite linux applications of course, but still there are quite a lot of the regular stuff you would expect. This includes the mobile version of Firefox, Fennec, vim, OpenSSH (client and server) and even Emacs. Being the geek that I am, nearly the first thing I did was a remote login via ssh from my workstation on the N900 (also see this overview of USB networking on the N900). Native maemo applications are typically developed with Python and GTK, although that is probably going to change for Maemo 6 (Nokia has announced it favours Qt over GTK). The community seems quite active, too: just shortly, a port of Clisp (a Common Lisp compiling to byte code) was announced (including a running Swank backend, so you can connect from your development Emacs remotely), although I imagine that the development environment for Python is, generally speaking, more advanced (for Maemo development, this is). I haven't looked any closer into developing for Maemo up to now, but it surely looks interesting.

ObTitle: Gossip, "Music for men"

Break so easily

nospam@example.com (Holger Schauer) — Sun, 13 Dec 2009 15:20:07 +0100

When I upgraded lately, my old fbpanel configuration was broken. I basically stumbled over Debian bug #288594, my old configuration as well as the system default pointed to a no longer existing /etc/fbpanel/menu file. So, my fbpanel no longer showed a menu. Sure enough, my WindowMaker has its own menu, so it was not much of a hassle. The broken menu entry (I just edited out the reference in my .fbpanel/default) annoyed me nethertheless, so I gtfn[*] today and found the missing info: in order to include the system menu, you just have to include a systemmenu entry. My menu referencing section now looks like this and I have a working menu again.

Plugin {
    type = menu
    config {
	image = /usr/share/icons/gnome/16x16/places/gnome-main-menu.png
        systemmenu {
        }

	separator {
	}
        
        item {
            name = terminal
            image = /usr/share/fbpanel/images/gnome_terminal.svg
            action = /usr/bin/x-terminal-emulator
        }

    }
}

ObTitle: The Mighty Mighty Bosstones, "Let's face it"

[*] gtfn: googled the friendly net

November has come

nospam@example.com (Holger Schauer) — Mon, 02 Nov 2009 15:05:04 +0100

November is here and Ubuntu 9.10 Karmic Koala is there, too. As one of its promises is faster start-up time, I used the weekend to update my laptop (a Dell 610) which was still running Hardy (8.04). The upgrade path (hardy->intrepid->jaunty->karmic) took quite some time and I'm not entirely sure it was worth it:

- Bootup time doesn't seem to have improved, quite to the contrary. I'm mounting ntfs volumes on startup and it seems that
the new parallel bootup procedure seems to run into trouble with that.
- I lost support for fglrx, the proprietary driver for the ATI graphics. It's possible to reinstall the package, but modprobing the module gives a "failed to allocate memory" error. Hence, no "graphics effects" (aka) compiz for me.
- Gnome-Shell isn't installed by default for me.
- The xemacs21-mule package postinstall script fails. This has the not exactly nice side effect that the upgrade procedure decided to quit after installing new packages, which means that it didn't clean up the cruft left behind from the old installation and also didn't boot into the new kernel.
- The update to grub2 didn't honour my old selection for which OS to boot by default (the laptop is mostly used by family members who prefer alternative systems).

And as always on Ubuntu update, a lot of crap that I got rid off previously, gets reinstalled. Like fspot, tomboy and wvdial, to name but a few. I can't help being reminded of adware.

Update:Turns out that newer fglrx modules don't support my ATI Radeon Mobility 1400 any longer (since jaunty, that is). To get GLX working, I had to un-install everything related to fglrx and re-install mesa. What I learned again the hard way during me fiddling with my old xorg.conf is that gdm is a real PITA if you have no working X configuration. What really annoyed me, though, was that status messages from dosfsck hosed the recovery (boot) mode in that the keyboard became unusable. Worse, my hard configured wlan setup at boot time is currently not working anymore, I can connect to my WiFi only through network manager. But without X I couldn't startup network manager, of course, so I also could't do a remote login. And the Wifi connection is really flakey whereas it had been stable ever since with the older hardy installation. Probably a driver issue. Update 2: Various forum entries suggested using backported modules for wifi, including a newer version of the iwl3945 driver. However, this didn't solve my problem. Another entry suggested switching to wicd instead of NetworkManager. And yes, indeed, my wifi problems are gone now.

ObTitle: Gorillaz, "Demon Days"

It's oh so quiet

nospam@example.com (Holger Schauer) — Fri, 31 Jul 2009 08:29:50 +0200

So I finally bought a new desktop computer in order to replace my old and loud one. The new one should fulfill two more or less conflicting requirements: it should be fast and quiet. "Fast" mainly refers to cpu and disk speed, for the gpu I only had the minimal requirement that it would be possible to see videos (non-HD) and show some basic 3d effects. I left most of the details to a local dealer, but I verified that the components would work with Linux, which actually means I only needed to ensure that the board, an Asus P5Q-VM, which is based on the intel G45 chipset, would work. A little digging showed that there might be some problems with X11 if the distribution didn't provide new enough drivers but I found enough success reports to be optimistic.

Well, I finally got the new workstation. It's an impressive black box with a Silentmaxx ST-11 tower which is really very silent -- it's so quiet that they provide large blue leds on the box to that you have a reminder that the system is on -- this was one of the details I wasn't aware of when ordering the system. I started installing Debian Lenny on the box, as I always followed the rule that buying a new computer is a good point in time to install from scratch and get rid of old software cruft. So I did nothing to carry over my old installation which I had regularly updated at least since Sarge. That was actually a quite pleasant way for me as it was the first time I've got to see the "new" graphical installer. There were some minor obstacles, though. First, this time I wanted to have both an LVM setup and encryption running. I was pleasantly suprised to see the installer providing an option for such a setup, but quite less suprised to see it fail with a segmentation fault during wiping the (500GB sata) disk. Fortunately, the manual partitioning option provided enough easy guidelines to quickly rebuild the setup of the automated partitioning scheme while allowing to leave out the unneeded step to clean the disk, so this was not a big issue. Another point that I think is interesting is that hibernation worked out of the box even with the LVM/crypto setup -- I had thought that hibernate or better said, suspend to disk, would requre the swap to be unencrypted but apparently I was wrong. Very nice.

I went on to install a very minimal system without any desktop setup. I went away from Gnome back to WindowMaker some time ago, but I had seen the LXDE as an install option which is a much smaller "desktop environment" with OpenBox2 as the central window manager. Now, compare the list of packages for Gnome with the list of list of packages for lxde -- that's quite a difference. But soon enough I realized how difficult it has become to avoid the larger environments. There are quite a lot of applications which I am used to using right now (having installed Gnome on my older desktop as well as running Ubuntu with Gnome on several other installations) which depend on Gnome. Evolution, for instance, which I privately mainly use as a glorified calender, depends on Gnome just as Rhythmbox does. This may hardly come as a suprise, but I've simpy not thought about it in advance. So I'm now looking for replacements for some applications.

Of course, in order to run any desktop environment you have to have a running X11 installation. This failed at first: I had connected my 19"-TFT (an old Benq one) via VGA to the on-board graphic chipset from the G45, which resulted in the monitor proclaiming to get out-of sync timings. After replacing the VGA connection with a DVI one, the vesa driver provided a working X11 setup. However, I soon discovered that I would not want to stick with the vesa setup, as for instance there is no xvideo extension. Unfortunately, the xserver-xorg-video-intel package in Lenny is version 2.3.2, which is too old to support the G45, so even though I specified the intel driver in the device section of /etc/X11/xorg.conf, I didn't get a usable screen. However, packages for Xorg in version 2.8 had entered unstable some time ago -- as I had quickly installed kernel 2.6.30 from backports.org and the packages doesn't have to broad version requirements on other packages, this seemed like a viable option. So I know have an up and running intel driver for X11, but it remains to be seen how stable it really is over time. And, of course, I've got to keep an eye on security updates.

ObTitle: Björk, "Post", (more info)

Love is a loosing game

nospam@example.com (Holger Schauer) — Tue, 05 May 2009 08:26:22 +0200

Some time ago I updated my trusty old workstation from Debian Etch to Lenny. As always, there were some minor glitches, not necessarily all of them were due to Lenny itself, though. Here's a rough list.

One really annoying issue was that my trusty old Matrox G400 suddenly behaved unbelievably slow under X11. I could nearly watch the pixels going by. I could tell by the X server log that some things had changed (like Xrandr now running) but I couldn't tell what was responsible for the problem. Explicitly setting the option "NoAccel" to "false" and "NoHal" to "true" (I have a single screen setup) finally settled the problem. I also tried "UseFBDev" "true" but this only works for me with a Depth of 24, which in turn screws my screen whenever I switch to the console (for instance on hibernate), so I'm back to not using the framebuffer device (and a depth of 16).

The Postgres update didn't work for me. I guess that this was mainly due to a lack of disc space. It took me some time to figure out that no default cluster had been created, which was the reason that the manual restore of the DB backup I had made failed.

I took the chance and finally updated to Iceweasel (firefox) 3. Some of my extensions were lost this way, but I managed to replace or update nearly all of them. Only Hit-a-Hint required a manual intervention directly in the install.rdf of the extension.

One typical annoyance of updates is that user settings are often not updated. This time I experienced that mainly with FBpanel in which all icon settings were broken.

Of course, the update broke some of my proprietary programs because of library problems. Korrektor, BMM, all are history now. As are some trusty old programs I still used, for instance xmms is gone, too. I used to stick with xmms mainly due to the Windowmaker mini app wmusic which allowed control of xmms via the dock, but as I've been using Rhythmbox for quite a while now, which has a NETWM compliant panel control, I could finally let it go.

ObTitle: Amy Whinehouse, "Back to black"

Busy doing nothing

nospam@example.com (Holger Schauer) — Thu, 30 Apr 2009 15:26:30 +0200

I've got tired of writing perl snippets just for simple shell tasks [*]. One such typical task is summing up the occurences of a particular pattern in a set of files to get a total of matches. Of course, this is trivial, but it's so trivial I tend to forget the use of 'expr'.


# code snippet GUID: 3E731D3F-51A3-43C7-B567-26760636DBCD
result=0
for i in `grep -c '[[:digit:]]:|>>>' .local*| cut -f2 -d: `
do
  result=`expr $result + $i` 
done
echo $result

As a one liner for copy&paste:

result=0; for i in `grep -c '[[:digit:]]:|>>>' .local*| cut -f2 -d: `; do result=`expr $result + $i`; done; echo $result

[*] The following quote is due to Kristian Köhntopp: "Use perl. It's necessary to know shell programming but not to use it."

ObTitle: Love is all, "Nine times that same song"

Close range

nospam@example.com (Holger Schauer) — Mon, 16 Feb 2009 09:56:49 +0100

I can't believe it: Debian really misses out on it's own records. Lenny was released this weekend although the usual two years since the previous release are not over yet. Congratulations. Now, I just have to go and check how old the packages of interest to me are out of the box this time ...

Wlan update

nospam@example.com (Holger Schauer) — Mon, 19 Jan 2009 21:23:01 +0100

Some time ago I started having nothing but trouble with my rt2570 based USB wlan stick. After we moved into our new flat, I finally started out and looked for a better solution. Looking through some retail market I found a package claiming it would support linux. After I was ensured I could return the thing in case of trouble (like outdated proprietary drivers), I bought it -- a Dlink pci card. After installing the thing, I quickly discovered that it's again a Ralink based product -- this time a RT61 based one, requiring firmware. I'm not happy with that but at least my workstation has wifi again.

One thing has changed, btw.: the newer kernels (I run 2.6.27 at the time of this writing) happily support the driver out of the box (i.e., after a recompilation and figuring out where to put the firmware), no more manual compiling and patching of drivers is required. And then you can also use wpa_supplicant to configure the network, which makes the entry in /etc/network/interfaces alot simpler:


auto wlan1
iface wlan1 inet dhcp
      pre-up ifconfig wlan1 up
      wpa-conf /etc/wpa_supplicant.conf
      post-up iwconfig wlan1 rate 54M
      post-up /etc/network/if-post-up.d/bauhaus.fw

Unfortunately, as you can probably guess, my connection is rather lousy and setting the rate up doesn't help much. It's wlan1 for me, btw., because I told /etc/udev/rules.d/z25_persistent-net.rules to configure it that way.

Debian scratch-n-half

nospam@example.com (Holger Schauer) — Wed, 30 Jul 2008 20:29:39 +0200

Debian just published an update to their stable distribution etch dubbed etch-and-a-half. The big news here for everyone not accustomed with Debians release cycle anyway is that it's the first time that it's not only a point release that fixes security issues but it's an update to the stable release that gasp adds support for new hardware, too. It even brings important fixes for some applications.

First of all, that's a tremendously good step in the right direction. In the past I've been bitten more than once by the long release cycle of Debian, outlasting all care taking of hardware compatibility. It's the primary reason that the only machine under my direct control running Debian is my rusty private workstation at the moment, all other machines needed newer drivers and hence are installed with Ubuntu. So, if Debian finally realizes that it has to change something to support newer hardware that's more than welcome.

However, it's not really etch-and-a-half. It's not much more than a new kernel which I would compile regularly from kernel.org myself anyway. Admittedly, there are also two new xservers (for nv and intel), but that's still not very helpful for people with newer ati hardware, for instance. But I'm a developer and much more than any hardware hassle I'm much more bitten by really outdated development tools. I've written only one blog entry about the issue, but it's a topic that most developers could write books about -- or maybe not, most of them probably just compile newer versions as needed and are done with the issue. This looks like the easy way out but it doesn't really solve the issue: if you've got to deploy your software you'll need to ensure that what you need is there. But using newer versions of base libraries forces you to deploy them yourself, which also means that you got a problem whenever a security issue will be found in those libraries. On the contrary, with system libraries you don't need any manual deployment of libraries you're only using and you can hope to participate of all system updates. So, in my eyes that's clearly a big advantage for using system libraries. But with Debian (and etch-and-a-half doesn't change this) you're stuck with older libraries which a) might lack long wanted functionality and b) are incompatible with versions from other vendors, which is a pain if you need to deploy on different platforms. Now, granted that the latter problem is not only tied to the age of libraries, but it would be a lot smaller if Debians general release cycle wouldn't be that long. I know of software vendors who have thus decided to develop for Ubuntu but not for Debian, in order to minimize portability issues due to library/functionality mismatches between platforms. To me, that looks like quite high a price to pay.

Everything is average nowadays

nospam@example.com (Holger Schauer) — Fri, 30 May 2008 20:00:00 +0200

I've tried Compiz with Metacity again and switch it off after a day -- again. I'm not willing to do without working software suspend just for some graphical whizz. I've been using Metacity for, I think nearly two years now, on my work computers and have somehow accomodated to it's various glitches (for instance the unusable keyboard settings). On my trusty home workstation, however, I've stuck with WindowMaker, which I think I've been using roughly since 1997 (I can't remember the version number, but it was fairly low). Unfortunately, development seems to have stopped -- since quite some time there is no sign of activity on the webpage and the mailing list archive is dead.

Yesterday, out of a current frustration about Metacity, I installed a naked current version of WindowMaker on one of my machines, under Ubuntu 8.04 (don't try to make WindowMaker work under Gnome: While WindowMaker does "work" under Gnome, it is really crippled. For instance, the keyboard setting know nothing about WindowMaker but still override your keyboard settings via, say, WPrefs.). Nearly everything worked as expected, but there were two glitches: the menu didn't reflect the installed software. Having customized the thing under my Debian system, I knew that this was supposed to work with the update-menu script, but that was missing. Some web-searching revealed that for some reason or other Ubuntu no longer installs the menu(-xdg) package. The other glitch was a very old complaint: That WindowMaker doesn't ship with a virtual desktop switcher or pager. You don't need to tell me about the different philosophy of WindowMaker, I know all about it. However, I've been using Fvwm and OpenLook (OLVWM) too long.

I could use gnome-panel (which I've done before in the past), but of course that brings me those two panels that make sense for Metacity and besides it also means that I would still depend on gnome. I've did quite a bit of looking around to find out what all the cool Fluxbox, Openbox etc. users are using and finally found fbpanel (the trick was to search for "taskbar" instead of "pager"). So, finally thanks to netwm support (which I think is in WindowMaker since 0.90), the one missing bit from WindowMaker is finally there without Gnome. Oh my, I'm finding this out really late.

Running Linux on Dell systems

nospam@example.com (Holger Schauer) — Mon, 21 Apr 2008 19:51:00 +0200

Dell is selling Ubuntu equipped systems since about a year now and seems to be quite happy with it. Whatever that effectively means, at least I can tell that I'm quite happy with Linux on Dell systems, too.

Through the last five years, I've been using Linux on a number of Dell systems. Under my personal control there have been three laptops (Dell C610, D610 and a Latitude 640) and a desktop (Optiplex 755), on which I have been running Debian Sarge, Ubuntu Dapper, Feisty and now Hardy. We also had several Dell servers at work running more or less smoothly with Debian (sarge, etch). Using Linux wasn't always without problems: I had trouble with built-in modems, PCMCIA ISDN cards and acpi/hibernation. For example, on my private Latitude 640, I have trouble suspending at all, because of the ipw3945 driver for the wlan. But the important thing to note is that basically all problems were really small and never of a size requiring me to use some other OS in the first place.

The only real issue is not with Dell per se, but more with my favourite OS, Debian: over the years, and especially with the ever-lasting sarge release, getting Debian to run on a recent system got more and more difficult. That's the main reason why I've been using Ubuntu on all recent hardware I had contact with: it's more or less (more so than less) a Debian system but does run on modern hardware. Main issues here were graphics adapters, sata/scsi hostadapters and network/wifi cards, or to put it otherwise: too old kernels, too old X.org. Both problem sources can simply be solved by using a recent version of Ubuntu. Sorry, Debian, but your release cycle is just too long to be acceptable. Granted, all these problems are mostly an issue when installing a new system, but it's not always possible to plug in some old disc with a working version of Linux.

Hang Wire

nospam@example.com (Holger Schauer) — Tue, 08 Apr 2008 07:55:39 +0200

Recent fun:
- Working hibernate/suspend without any manual configuration on a brand new Dell desktop using Ubuntu 8.04 (beta).
- Watching a self-generated video CD (probably done under Windows) under Linux without any problem with my wife that we couldn't watch on Windows due to scrambled colours under Windows media player.

Recent less fun:
- Hibernate/suspend on our older Dell laptop with Ubuntu 7.10 and finding it's a known issue with the ipw3945 driver.
- Getting vmware to work on a recent 2.6.24 system.
- Having fixed that finding out the hard way that Aero won't display in the VM, requiring to go back to cloning the (not so small) physical machine a third time.
- Being unable to get a DHCP lease over the rt2x00 driver for my USB wlan stick with kernel 2.6.24, despite being able to get a sucessful connect via wpa_supplicant/wext.

You gain something, you lose something

nospam@example.com (Holger Schauer) — Fri, 05 Oct 2007 08:33:29 +0200

Two days ago, I updated my laptop from Ubuntu 6.06 "Dapper Drake" (aka LTS) to "Feisty Fawn", aka version 7.04. Just in case you wonder, how I did that, I just followed the usual directions and first updated to Edgy and then to Feisty via issuing "gksu 'update-manager -c'" twice. Things went quite smoothly, but I did encounter some problems:

- I lost access to my databases during the migration from Postgres 7.4 to 8.2., i.e. there was no proper migration and as support for version 7.4 has been dropped, I even have no way to dump the old data and import it again. I need to figure out whether I can easily access the old dbs from Postgres 8.2 (mind you, I'm talking of the raw data and the DB server, not client access).

- As a result, my local copy of serendipity stopped working. I re-installed serendipity (a clean start seemed to be a good idea), but still Iceweasel gets wrong information about the phtml files it generates. Probably a problem with the PHP installation, which I need to get straight (I'm not a PHP guy, though).

- When booting into Edgy, when switching from the splash screen to X. the screen went black and there was no way to get a display. I solved that by ssh-ing into the box, modifying /etc/X11/xorg.conf by using the ati driver instead of the fglrx driver and then editing /boot/grub/menu.lst so that it wouldn't show the splash screen or suppress messages. The problem went away after going to Feisty.

- To get VMware running again, it wasn't enough to issue the usual /opt/bin/vmware-config.pl that you have to do with every new kernel. It kept telling me that the headers directory wouldn't fit my current running kernel. Fortunately, I already had loaded the new version down which solves the problem (I guess there is a new version numbering scheme in newer kernels).

- The update of course also brought with it the switch to Iceweasel, so of course, I lost some of my trusted extensions (Reveal, Surfkeys).

- What really annoyed me was the ugly, fat looking "optimal" font that I encountered in most applications. Why Gnome doesn't use subpixel hinting as a default is beyond me (especially as I'm quite certain to have had that setting in the old setup, too).

- The new eclipse version of course knew nothing about my local installed plugins, implying that I had to reinstall them.

On the nice side, my mail setup kept working and the network setup kept working, which I think is way more important.