How to get Network Manager working with ratpoison //at 00:59 //by abe

Using GNOME Network Manager is a neat way to connect to wireless or virtual private networks from a laptop running Debian Lenny, Sid, Etch with Backports or any of the *buntu distributions. You can control everything from the system tray. But not all window managers have a system tray. And with some window managers it’s not obvious how to make them work with one of those lean third party trays and panels.

Especially my favourite window manager for small displays as on the EeePC – ratpoison – insolently puts any panel or tray in the middle of the screen by default. It took me a moment to find out how to make ratpoison work with my favourite third party system tray trayer (which can handle transparency and is only a system tray, no taskbar).

First we need to make ratpoison ignore the trayer on the one hand and and reserve space for it on the screen. Fiddling around with preconfigured frames didn’t work well and the following way is also more straight forward:

1. trayer always has “panel” as window title, so adding the following line to your .ratpoisonrc makes ratpoison ignore trayer:

   unmanage panel

2. Now all windows overlap the trayer, so we need to configure the space for it. Trayer in the default configuration shows up at the bottom and has a height of 26 pixels, so we tell ratpoison to add a padding of 26 pixels at the bottom of the screen by adding the following line to the .ratpoisonrc:

   set padding 0 0 0 26

Now we are confronted with the problem that these settings only apply to new windows, not ones which were already running when ratpoison starts. I usually start my X session using an .xinitrc or an .Xsession which calls the window manager using exec at the end.

We can start the trayer later though by spawning a subshell in the background with a sleep at the beginning. Also the Network Manager applet (nm-applet) can be started that way. In my case the end of the .Xsession looks like this:

( sleep 1; \
  trayer --align right --edge bottom --distance 0 \
	 --expand true \
	 --transparent true --alpha 128 --tint 0 \
	 --SetDockType true --SetPartialStrut true & 
  nm-applet & ) &

exec ratpoison

The result could look like this:

The other programs in the system tray are from right to left: nm-applet (GNOME Network Manager), Twitux (GTK Twitter Client), Audacious, Opera, Pidgin (formerly known as GAIM), Icedove (unbranded Mozilla Thunderbird). The clock on the bottom left is from the package osdclock.

Oh, and although I’m fine with trayer: if anybody knows a possibility to control the GNOME Network Manager without the need for a system tray, I would be very happy if you could tell me. :-)

Update 18-June-2008 23:45:

Matto Fransen used my howto to get ratpoison and nm-applet working together on Ubuntu. He also explains in his blog post, what may be necessary to get nm-applet working as intended in the first place — things I already had forgotten when I wrote this posting initally. :-)

Following Bleeding Edge Software and still using Debian Stable //at 23:47 //by abe

Many Linux fans know that Debian Stable usually already lost the “b” when it’s being released. ;-) What seems not so well known (especially not by some DesktopBSD Marketing guy at last year’s LinuxDay.at :-) is that there is really a lot of people who really like this “stale” software collection — because it’s rock solid — especially compared to the ports in FreeBSD or DesktopBSD *evilgrin* which unnecessarily follow every new feature upstream introduces. This is really annoying in a server environment where you want as less changes as possible when updates are necessary due to security issues. My personal favourites here are Samba and CUPS. *grmpf*

Although I belong to those people who run Debian Stable even on brand-new hardware, I sometimes have to use the newest beta or alpha versions of some software to get it even only running. And doing so is fun but feels strange somehow, though. Currently I follow the pre-releases of three software makers quite close, due to a new laptop:

At the beginning of last semester I bought a brand-new Lenovo ThinkPad T61 (2,2 GHz Intel Core2 Duo T7500, 4 GB RAM, 160 GB HD, 1440x900 14” Widescreen) without preinstalled operating system (possible thanks to the ETHZ Neptun Project) and installed — of course — 64-bit Debian Stable on it.

While the Debian Installer from Etch worked fine even on such new hardware, not all features worked out of the box because some components were just too new.

So the first thing I did was installing 2.6.22 from Backports.org, quickly moving farther to vanilla 2.6.23. Nearly everything I needed worked except the wireless network card. It needs the iwlwifi driver which is officially in the Linux kernel starting at the upcoming 2.6.24 (said to be released during the next few days). So I run 2.6.24 pre-releases on the laptop since the first release candidate, always eagerly waiting for either the next RC or the final release. (And 2.6.24 looks impressively stable to me — even since the early release candidates. :-)

I even got the fingerprint reader working for login and sudo (but not xscreensaver) using libthinkfinger backported to Etch from Debian Experimental. I’m just not sure if this is a good idea since the back of the screen already has enough of my fingerprints on it. ;-)

The next software of which I’m currently running an alpha version is 64-bit Opera 9.50 (aka Kestrel, available at snapshot.opera.com) because no earlier Opera version is available for 64-bit Linuxes. Here I had different experiences: The builds from October and November were already quite stable, but since December it crashes usually several times a day.

At work I also run the 64-bit Opera on my workstation, but stalled updating it when I noticed that it became so unstable. So my Opera at work has currently an uptime of nearly four weeks — and would have probably more if I hadn’t rebooted my workstation in Mid-December.

Somehow this hunting for new versions and eagerly waiting for every new (pre-)release makes me really fidgety sometimes. And my understanding for people doing this for there whole userland or even operating system has grown, but I still prefer to have stale but stable software on all my productive machines, even on my laptop — just with some few and handpicked excpetions.

The third but less thrilling thing I’m following are nVidia drivers for X. Since the free nv driver of X.org doesn’t support (and not only just doesn’t know) my graphics card yet and nouveau isn’t ready yet, I run the binary only and closed source driver from nVidia, waiting for that one release which supports Xen since I really would like to run a Xen guest with Debian Unstable for testing purposes and package building on my laptop. Until then I have to content myself with the much more unwieldy QEMU respectively KVM.

Anyway, I’m very happy with the T61 and Debian Stable and can easily connive at the few not (yet) perfect issues like missing Xen support by nVidia, broken ad-hoc mode in the wireless card, no internal card-reader (as announced in the Neptun specifications) and no native serial port.

Some useful links regarding the subject of this post:

• Linux Weather Forecast
• Opera Desktop Team
• Nouveau: Open Source 3D acceleration for nVidia cards
• ThinkWiki

Now playing: Jean Michel Jarre — Rendez-vous à Paris

Group packages by origin in aptitude //at 02:00 //by abe

I always wondered how others recognise non-Debian packages in the aptitude package tree. I also missed the additional priority level in the hierachy well-known from good old dselect.

For the last one, I quickly found out that you can set the priority as subsection — it’s straight forward after you’ve read the documentation: Just add ,priority at the end of the default grouping method for package views under “Options → UI Options” in the aptitude menu.

Getting the origin as given in the Release file of the repository a package originates from is a little bit more difficult. You need to use the pattern() group function with the appropriate search pattern: pattern(~O)

Since already the default default grouping method for package views doesn’t fit into the dialog, I nowadays just edit /etc/apt/apt.conf directly for changes on aptitude’s default grouping method for package views. It now looks like this on several of my machines:

Aptitude::UI {
  Default-Grouping "filter(missing),status,section(subdir,passthrough),pattern(~O),section(topdir),priority";
};

In aptitude this looks like this:

[...]
  --- text - Text processing utilities
  --\ utils - Various system utilities
    --- Debian
    --- Mowgli
    --- volatile.debian.org
  --\ web - Web browsers, servers, proxies, and other tools
    --- Debian
    --- Opera Software ASA
  --\ x11 - The X window system and related software
    --\ Debian
      --- contrib - Programs which depend on software not in Debian
      --\ main - The main Debian archive
        --- Priority optional
        --- Priority extra
      --- non-free - Programs which are not free software
    --- Mowgli
[...]

Unfortunately this doesn’t work with all non-Debian repositories since a few repository maintainer, e.g. those from Emdebian, arrogate to just keep “Debian” as their packages’ origin. This could be solved, if there’s a possibility to group by e.g. repository URL (host and/or path).

Another problem I haven’t solved yet is that grouping by origin does neither work with locally created nor virtual packages nor tasks — probably since all of them lack an origin. Those branches are just empty or don’t even show up anymore with this configuration. I probably have to dig a little bit more in the aptitude documentation to resolve this.

Now playing: E-Rotic — Max don’t have sex with your ex

Gaia resurrection //at 20:35 //by abe

On Thursday, 24th of November 2006 evening (about one and a half week ago) we got an anonymous Symlink submission about gaia 0.1.0, a simple, but free (GPL‘ed) client for Google Earth, solely based on reverse engineering. Liked the idea of a really free client for such a popular service, so I posted it as Symlink article (German) quite shortly after noticing the submisson.

Since it’s under GPL and uses only libraries already being in Debian (OpenGL, SCons, cURL, SDL, libjpeg, libpng, libgps and Doxygen), I really would like to see it in Debian. But since I have never programmed with most of them, I did not try to compile gaia but instead took the easy way for myself and filed an RFP bug for it in Debian.

The next day in office, Gürkan, a coworker of mine and currently in NM, told me that he tries to package gaia for Debian and that it doesn’t compile on Sarge. So I gave him access to my Sid chroot and asked him if he has read about the RFP at debian-devel or debian-wnpp. To my surprise he answered that he didn’t read about it on Debian lists at all but on Symlink and therefore didn’t knew about the RFP at all.

So I pointed him to the RFP just to notice, that it wasn’t an RFP anymore but already an ITP. Strangely I didn’t get any mail notice about this change although the retitling happend only shortly after the initial RFP… Of couse, Gürkan wasn’t very happy about this, since he planned to maintain gaia himself, but at least he provided his working proof of concept package for Sid to Jordà Polo who intends to maintain an official Debian package of gaia. We then also met Jordà on the #debian-games channel in OFTC. He told us, that he’ll check some more licensing issues before uploading a package of gaia.

Well, since I had a working gaia package installed in my Sid chroot, you can probably imagine what I did half the evening? Right: Surfing around the earth with gaia and visiting my favourite places on earth. While virtually visiting places here and there, I listened to Venty’s first podcasts and seem to have downloaded 444 MB of Google Earth images (at least according to du -sh ~/.gaia). Goddamned addiction! ;-)

During the night from Friday to Saturday, I got a mail that the RFP/ITP has been closed and that Jordà was right with his suspiciousness: Google has sent a cease and desist letter to the gaia developers and they removed the downloads from their site. (So how was that Google motto? “Don’t be evil”? Well, good joke! Yet again the monopolist clearly shows that it doesn’t really mean what it says.) Since the gaia developers were allowed to post the mail from Google on their website, you can read parts of it there. I really wonder what was written in the left out parts of the mails. Job offers? ;-)

But it’s interesting to see that until one week ago gaia 0.1.0 already made it into the FreeBSD ports as well as into the ArchLinux User Repository. Both noticed, too, that gaia version 0.1.0 has been withdrawn by the authors.

Today in the morning Gürkan noticed that there’s a new version (0.1.1) of gaia at SourceForge using free NASA WorldWind / OnEarth imagery. Although the imagery is far away from the detailedness of the Google Earth imagery, this has one big advantage: There wasn’t really a X port for the windows-only client from NASA until now. (No real wonder, since they use proprietary and operating specific libraries such as .NET and DirectX…) And now we have gaia, a free client for free imagery on free operating systems. That made my day!

I hope that this will revive the packaging of gaia, at least Gürkan has already built a new proof of concept package of 0.1.1 for Sid. (Today in the afternoon, they released 0.1.2.) And if everything goes fine and Dunc-Bank manages to delay Etch until gaia has been 10 days in Unstable without bugs, we’ll have it even in Etch. ;-)

The mouseless side of X //at 00:48 //by abe

Although I like the idea of a tiling and completely keyboard focused window manager, I never fell in love with Ion because the default keybindings weren’t really intuïtive (to me). A few months ago I noticed, that ratpoison is also a tiling and completely keyboard focused window manager, only with much more intuitive usage: If you know screen and it’s keybindings, you also know ratpoison and it’s keybindings: Just exchange Ctrl-A with Ctrl-T. This sounds perfect for usage on my low performance laptops, where I have small screens and usually also no virtual desktops in use.

There’s only one thing which annoys me in ratpoison: If I use a mostly mouse driven application like e.g. a webbrowser with ratpoison, I have no problems to click on links, even if the webbrowser is not in the so called “current frame”. But if e.g. click into an input field, I usually notice much too late that while the mouse works fine in the browser, keyboard focus is still in some other window. Currently they all use flwm, the Fast and Lite Window Manager.

So what I would need is a tiling and keyboard focused window manager but with “focus follows mouse” politics. And since the laptops on which I intend to use such a window manager, all have a touchpad or thumbstick, the mouse there counts as keyboard focused, too somehow, doesn’t it? :-) I wonder, if an ion3 could be configured to use the same keybindings as ratpoison. That would probably fulfil this desire.

On the other hand, there are browsers which are fine without mouse. lynx or links2 for example, so the focus problem I have with ratpoison wouldn’t occur. But what if I need or want a keyboard driven and full blown webbrowser? Ok, Firefox as well as Opera are not that bad in keyboard only use, but they still are focused on the mouse using user.

But Gecko wouldn’t be Gecko, if there wasn’t some Gecko based browser with this features: On the ratpoison website I found a link to a very interesting Firefox plugin which makes Firefox a complete new browser, a keyboard driven webbrowser named Conkeror. It has no toolbars at all, no (visible) tabs, no menus, no nothing — it shows only the website in fullscreen, a status line and a multipurpose command line — exactly like the mini-buffer of GNU Emacs.

But not only the layout, even the keybindings are very emacsish: C-x C-f opens an URL in a new buffer -eh- tab, C-x 5 C-f opens an URL in a new frame (window), C-x C-v opens a new URL in the current tab (buffer) with the current URL as editable default value, C-x b switches to another tab, C-x k kills -eh- closes a tab, C-x C-b lists all open tabs, l goes back (remember the Emacs info reader, eh?), C-g quits accidently requested dialogs or stops loading a web page, Ctrl-s and Ctrl-r give you forward and backward i-search, C-n, C-p, C-f and C-b scroll, etc. Even M-x works, e.g. will M-x revert-buffer reload the web page. (Unfortunately Esc-x doesn’t work. Yet.) And for vi freaks, there is even M-x use-vi-keys. There’s even one lynxish keybinding: \ lets you view the source.

And although it’s one of the strangest webbrowsers I saw yet, I somehow like it and also would like to see it in Debian as package, since it is the perfect companion for ion or ratpoison. Looking through apt’s package cache as well as the wnpp bugs, I haven’t found any hint on somebody already packaging it, so I’ll have a look on it and on how to to package a Firefox extension for Debian.

BTW: While looking through the wnpp bugs, I found bug #335459, which is the ITP flock, an also Gecko based browser with a lot of cool features for blogger who like social network tools.

Another nice thing I found today in Debian was the xfonts-artwiz package whose small fonts are very suitable for small resolution screens, especially if a tiling window manager is used with a e.g. 800×600 resolution. Unfortunately they aren’t available in a charset with German umlauts.

Apropos tiling window managers: Anyone tried pconsole with an automatically tiling and resizing window manager? I wonder if it’s usable. At least on MacOS X with its cascading window positioning algorithm, pconsole is a pain. — But even without cascading windows, MacOS X is a pain for keyboard users. Just think of its default behaviour when using the tab key inside a form mask: It will skip all buttons, all checkboxes, all radio buttons and all select boxes. Argh!

wApua now in Debian Unstable //at 00:38 //by abe

Hey, the actual version 0.06 of my Perl written WAP browser wApua now is in Debian Sid!

It’s the first software written by me which has entered the Debian repository as its own package (since pum is included in the package pisg which is in testing now for a while) as well as the first software debianized by me which reached Debian Unstable.

Things are always exciting when they happen the first time. ;-)

Thanks to Myon for sponsoring the package.

Yet another old laptop //at 04:13 //by abe

My father got me a nice IBM ThinkPad from 1996 earlier this year, so the next old laptop he digged up was planned to become a christmas present for my brother. But my father didn’t manage to find out, how old nor how fast that laptop was. And when I found out that it was a Pentium I with 90 MHz, it was clear, that my brother wouldn’t have any use for it, so he got “only” the used 850 MHz AMD Duron midi tower and my parents declared that old Compaq LTE 5100 laptop as a christmas present for me. :-)

As my IBM ThinkPad bijou, this Compaq LTE 5100 is from 1996 and has a Pentium I processor. Both also have a 800×600 resolution, a double PCMCIA slot and a floppy drive, which can be replaced by a CD-ROM drive (if I had one). But that are all similarities. Technically the Compaq has 90 MHz instead of the ThinkPad’s 133 MHz, but therefore has 72 MB RAM in comparison to the 48 Megs the ThinkPad has. Also regarding disk space the Compaq outperforms the ThinkPad: 1.6 Gigs of disk space in comparison to the ThinkPad 1.0 GB hard disk. Another difference is the battery: While the ThinkPad can work over 2.5 hours without external power, the Compaq even didn’t manage to completely boot its currently installed Windows 98 (the ThinkPad had a Windows NT installed when I got it) when running on battery. (Will do that test again when I can confirm, that the battery was full before testing. :-) Yet another difference is the keyboard layout: The ThinkPad has an US layout while the Compaq has a Swiss-German layout. But the most obvious difference is the look: The black ThinkPad still looks like having a modern design while the Compaq looks very very outdated in its perfect computer beige and with its quite small display.

So retroperspectively, it was a good a idea to name the ThinkPad “bijou” (French for jewel, jewellery, gem, etc.; named after a very neat british two-door limousine built in the UK by Slough on a 2CV base during the ’50s). Because now I have the choice between a lot of not so nice looking (not to say ugly ;-) 2CV derivatives to name the Compaq after. My favourites currently are the Iranian “Baby Brousse”, the Greek “Namco Pony” and the German “Fiberfab Sherpa”, all canvas and flatbed style 2CV based buggies, similar to the original Citroën Méhari but with steel body instead of the Méhari’s controversial plastic body. And one of the not used names, I can use for further ugly Compaq laptops¹.

Another question yet to answer is the question of what operating system to install on it. Since the ThinkPad runs fine with Debian 3.0 Woody and I have a lot of other Debian boxes at home (running Woody, Sarge or Sid), I currently think about installing the very fresh NetBSD 3.0 (released on Christmas’ Eve 2005), FreeBSD 6.0 (released early November 2005), DragonFly BSD 1.4 (to be released in December :-) or DeLi Linux 0.7 pre (which was also released in early December 2005 and already uses X11R7). Another idea was to install grml 0.5, but since grml is a live CD distribution, it probably would be hard to install it over network. Same counts for ReactOS (version 0.2.9 was released shortly before Christmas 2005), which doesn’t seem to have a floppy disk plus network install. Since I always planed to upgrade my currently defective Toshiba T6400 i486 laptop ayca (maybe after getting an organ donor on eBay or so) to DeLi Linux 0.7 (and perhaps write a review about it for Linux Magazine or so) and I may get an Sun Ultra Enterprise 2 soon (on which NetBSD 3.0 would be the perfect OS since Linux’ performance still seems to suck on Sparc :-), I currently prefer the FreeBSD or DragonFly idea. If the Ultra doesn’t come, it probably will get NetBSD, since I haven’t a NetBSD box yet. (Haven’t a DragonFly box either, but a FreeBSD 4.x running somewhere. :-)

Well, I guess, I’ll take even more old laptops than last year to the Vintage Computer Festival Europe (VCFe) in Munich next May. And since the two 1996 laptops are now 10 years old, they’re even ontopic! Yeah! ;-)

¹: I have two other not yet working Compaq laptops, both from an elder generation than Pentium I. One I got on a Swiss flea market for a few euros and the other was the first laptop of my boss, which he else would have thrown away. Unfortunately both are without power adapter and neither the usual allround laptop power adapters from Conrad, etc. nor the one from the LTE 5100 fits. But since there is eBay, I expect to get such a power adapter once. :-)