Planet Commandline officially online //at 22:25 //by abe

Around the first bunch of postings in my Useful but Unknown Unix Tools, Tobias Klauser of inotail and Symlink fame came up with the idea of making a Planet (i.e. a blog aggregator) of all the comandline blogs and blog categories out there.

A first Planet Venus running prototype based on the template and style sheets of Planet Symlink was quickly up and running.

I just couldn’t decide if I should use an amber or phosphor green style for this new planet. Marius Rieder finally had the right idea to solve this dilemma: Offer both, an amber and a phosphor green style. Christian Herzog pointed me to the right piece of code at A List Apart. So here is it, available in you favourite screen colors:

Planet Commandline

For a beginning, the following feeds are included:

• Myon’s Unix blog category
• Evgeni Golov’s Desktop in a Shell column
• My Useful but Unknown Unix Tools column
• My Shell blog category
• The GRML Development Blog
• Chrütertee (Swiss-German)
• Commandline Magic’s identi.ca feed

Which leads us to the discussion what kind of feeds should be included in Planet Commandline.

Of course, all blogs or blog categories which (nearly) solely post neat tips and tricks about the command line in English are welcome.

Microblogging feeds containing (only) small but useful command line tips are welcome, too, if they neither permanently contain dozens of posts per day nor have a low signal-to-noise ratio. Unfortunately most identi.ca groups do, so they’re not suitable for such a planet.

What I’m though unsure about are non-English feeds. Yes, there’s one in already, but I noticed this only after including Beat’s Chrütertee and his FreeBSD command line tips are really good. So if it doesn’t go overboard, I think it’s ok. If there are too many non-English feeds, I’ll probably split Planet Commandline off into at least three Planets: One with all feeds, one with English only and one with all non-English feeds or maybe even one feed per language. But for now that’s still a long way off.

Another thing I’m unsure about are more propgram specific blogs like the impressive Mastering Emacs blog “about mastering the world’s best text editor”. *g* (Yeah, I didn’t include that one yet. But as soon someone shows me the vi-equivalent of that blog, I’ll include both. Anyone thinks, spf13’s vim category is up to that?)

Oh, and sure, any shell-specific (zsh, tcsh, bash, mksh, busybox) tips & tricks blogs don’t count as program-specific blogs like some $EDITOR, $BROWSER, or $VCS specific blogs do. :-)

Of course I’m happy about further suggestions for feeds to include in Planet Commandline. Just remember that the feed should provide (at least nearly) exclusively command line tips, tricks or howtos. Suggestions for links to other commandline related planets are welcome, too.

Perfect Team: autossh and GNU Screen //at 01:06 //by abe

SSH is definitely one of my most often used tools, not only for system administration at work but also on the road with my netbook, an EeePC 701 running Debian Sid.

On the road, it often happens that I have a flaky WLAN or UMTS connection, so I often have to kill (via <Enter>~.) and reconnect my SSH session due to a changed IP address or so.

First step against problems arising from using SSH over unreliable network connections is of course GNU Screen. Second step is use SSH keys and ssh-agent to not needing to type the password on every reconnect.

But it’s still very annoying to kill the SSH connection and call ssh again manually. For luck there is autossh, a wrapper around SSH which regularily checks via two tunnels connect to each other on the remote side if the connection is still alive, and if not, it kills the ssh and starts a new one with the same parameters (i.e. tunnels, port forwardings, commands to call, etc.).

It’s quite obvious that this is perfect to be combined with screen’s -R and -d options (Reattach if a detached screen is around, else start a new screen; detach a currently attached screen), so I found myself very often typing (or fetching it from the commandline history :-):

autossh -t sym.noone.org 'screen -Rd'

-t is necessary to allocate a terminal device on the remote machine which is not done by default if you directly call a command via ssh.

In comparision to OpenSSH, autossh needs the single quotes, because otherwise it would parse -Rd as options to parse to ssh and bail out. That’s not a real problem, but when you’re used to just type ssh -t sym.noone.org screen -Rd without any quotes, you’ll run into this then and when.

Update, 25-May-2010, 14:55: As Carsten Hey points out, autossh also supports the -- option to declare that all following options and parameters must be passed to ssh itself. (End of Update)

Typing that often and mistyping it then and when cries for an shell alias or an shell function. So I came up with the following shell function:

asc() {
    autossh -x -a -t "$@" 'screen -RdU'
}

I used a function instead of an alias in case of autossh will in future regard all parameters given after the command as part of the command as ssh does.

The additional options -x and -a disable X and SSH Agent forwarding which both don’t work if you reattach to an already running screen.

And if you’re using Zsh as I do, you can even add some more format string magic to set the window title more or less to the expanded alias, eh, function:

function asc() {
    # Set the title to something more obvious, e.g. the expanded
    # alias, eh, function
    print -Pn "\e]0;%n@%m: autossh -t $* 'screen -RdU'\a";
    autossh -x -a -t "$@" 'screen -RdU'
}
compdef asc=ssh

Update, 25-May-2010, 14:59: As Hauke points out in a comment, Zsh users should also declare that asc should have the same tab completion as ssh itself. The example above has been updated accordingly. (End of Update)

In the meantime on the EeePC I use asc on the commandline more often than ssh itself. And I nearly no more type autossh. (The most common exception here is autossh hostname tail -F /path/to/some/logfile.)

Using that function you can also add common ssh options for tunneling, etc. — I use it most often like this:

asc -D 1080 sym.noone.org

This opens a SOCKS proxy on localhost, port 1080 and that way I can surf via the host I’m connecting to by SSH.

There’s one small drawback though: You didn’t expect that I can just invent some new three letter command without a namespace clash, did you? There is a free game called Advanced Strategic Command whose binary (and Debian package) is named asc, too. If you have that game installed, you can always call it using its full path, e.g. /usr/games/asc on Debian.

P.S.: My whole grml based .zshrc is also available via git at git.noone.org as well as on github.

Thoughts on Gitorious and GitHub plus a useful git hook //at 11:36 //by abe

When I took over the developement of xen-tools, I looked around for an appropriate git hosting. I especially had a look at GitHub and Gitorious.

If you just regard the features, GitHub is definitely more targetted on single developers and Gitorious more towards projects:

At GitHub, every repository has its URL under the URL of a user page which makes it nearly impossible to have user independent, “official” repositories for projects which have more than one official developer.

At Gitorious, every hosted repository needs to belong to a project, even if it’s only a published configuration. But a project can have more than one git repository. You only seem to be able to have personal repositories if you clone some existing Gitorious repository.

So from a feature point of view, the xen-tools git repositories fit way better to Gitorious’ hosting while the git repositories with zshrc, conkerorrc and desktop configuration files defintely have a more fitting addresses on GitHub, in my case http://github.com/xtaran/$repository. On Gitorious, they are now together under a “project” called “Axel’s configuration files” at http://gitorious.org/abe which contains git repositories of my on grml’s .zshrc based .zshrc, my configuration for Conkeror and all the files necessary for my ratpoison/xmobar based netbook/laptop desktop.

I though feel a little bad for giving the project the very short “slug” name “abe” instead of “abe-config” (as I did initially) since “abe” is IMHO not a proper “project name” for my configuration files and possibly other projects would have a more reasonable claim for that project name on Gitorious. But that way it suites more its purpose: Gather some of my git repositories which don’t belong to a proper project.

But there’s another important point when comparing Gitorious and GitHub: Free Software needs free tools as Benjamin Mako Hill posted recently on Planet Debian. Despite my (probably well known) distrust against Google and therefore also Google Code, and despite knowing the history of SourceForge becoming non-free, I was not that much aware that GitHub’s software is only partially open source and therefore also not free software while Gitorious is both as it’s licensed under the GNU Affero General Public License (like StatusNet/identi.ca for example) which is basically GPLv3, but its ideas applied to hosted web applications scenario (where the GPL itself doesn’t grasp), too.

Initially I just had the xen-tools git repositories on Gitorious and all my small one-repository “projects” as copies of the repositories on my own git server on GitHub to get some more publicity for them and allow “social cloning”. After reading Mako’s article, I decided to at least have repository clones on Gitorious of all repositories I mirror at GitHub, too.

That way I force nobody to use the non-free tools on GitHub for “social cloning” one of my git repositories. And of course I have copies of my code somewhere on the net as backup. Or to say it with Linus Torvalds’ (slightly updated) words: Only wimps use tape backup: real men just upload their important stuff on git, and let the rest of the world clone it. ;-)

But isn’t that tedious to always push your code to three repositories? No, it isn’t. I just push my code to git.noone.org where I have configured the according remotes and the following post-receive hook:

#!/bin/sh
                                                                     
read oldrev newrev refname
git push gitorious ${refname:t}
git push github ${refname:t}

The only other thing necessary is to use ssh-agent and SSH agent forwarding to at least the host you’re pushing to.

Still happy with the ASUS EeePC 701 //at 16:02 //by abe

Recently Eric asked on the LUG Vorarlberg mailing list about netbook experience. I wrote a lengthy reply summarizing my experiences with the ASUS EeePC 701. And I thought this is something I probably should share with more people than only one LUG:

I ordered an ASUS EeePC 701 (4G) with US keyboard layout at digitec in Spring 2008, got it approximately one month later and posted a first resumé after one month in my blog.

I’m still very happy with the EeePC 701, despite two commonly mentioned drawbacks (the small screen resolution and the small SSD – which I both don’t see as real problems) and some other minor issues.

What matters

• Very robust and compact case. And thanks to a small fan being the only moving part inside, the EeePC 701 is also very robust against mobile use.
• Very pleasing always-in-my-daypack size (despite the 7" screen it’s the typical 9" netbook size) and easily held with one hand.
• Black. No glossy display. Neither clear varnish nor piano laquer. Short: No bath room tile. Textured surface, small scratches don’t stick out and don’t matter.
• Debian (previously Lenny, now Sid) runs fine on it, even the webcam works out-of-the-box.
• Despite all those neat features, it was fscking cheap at that time. And it was available without Windows.

Nice to have

• There’s power on the USB sockets even if the EeePC is turned off but the power supply is plugged in.
• The speakers are impressingly good and loud for their size. (But my demands with regards to audio are probably not too high, so audiophiles shouldn’t run to ebay because of this. ;-)
• It has three external USB sockets.

What doesn’t matter

• The small 7" 800×480 screen: I like small fonts and do most things inside a terminal anyway. And even with 800×480, those terminals are still much bigger than 80×25 characters. Only some applications and webpages have no heart for small screens.
• The small disk size: Quite a lot of programs fit on 4 GB of disk space. Additionally I use tmpfs a lot. And music and video files are either on a external 500 GB Western Digital 2.5" “My Passport” disk (which I need quite seldomly) or much more come via sshfs and IPv6 from my home server anyway. :-)
• The small keyboard: I just don’t have any problems with the size or layout (right shift right of the cursor up key, etc.) of the keyboard. Well, maybe except that any standard sized keyboard feels extremely large after having used the EeePC exclusively for some weeks. ;-)
• The to 630 MHz underclocked 900 MHz Intel Celeron: It’s enough for most of the things I do with the EeePC. Also the original 512 MB RAM are somehow ok, but for using tmpfs, but no swap space at all, 1 GB or 2 GB are surely the better choice.
• A battery runtime of 2.5h to 3h is fine for me.

What’s not so nice

• The “n” key needs to be pressed slighty stronger than other keys, otherwise no “n” appears. So if one of my texts in average misses more “n” than other letters, I typed it on the EeePC. ;-)
• Home, End, Page-Up, and Page-Down need the Fn key. This means that these keys can only be used with two hands (or one very big hand and I have quite small hands). This is usually no problem and you get used to it. It’s just annoying if you hold the EeePC with one hand and try to type with the other.
• What looks like a single mouse button is a seesaw and therefore two mouse buttons below one button. This makes it quite hard to press both at the same time, e.g. for emulating a middle mouse button press. It usually works in about half of all cases I tried it. My solution was to bind some key combination to emulate a middle mouse button in my window manager, ratpoison:

  bind y ratclick 2

  And that mouse button bar already fell off two times.
• The battery reports only in 10% steps, and reporting in percentage instead of mAh is an ACPI standard violation because reporting in percentage is only allowed for non-rechargable batteries. It also doesn’t report any charging and discharging rates. But in the meanwhile nearly all battery meter can cope with these hardware bugs. This was quite a problem in the early days.
• Now, after approximately 1.5 years, the battery slowly fritzes: When charging there are often only seconds between 10% and 40%. Rigorously using up all power of the battery helped a little bit. Looks like some kind of memory effect althought the battery is labeled Li-Ion and not Ni-MH and Li-Ion batteries are said to have no memory effect.
• The SD card reader only works fine if you once completed the setup of the original firmware or set the corresponding BIOS switch appropriately. No idea why.

Similar models

Technically, most of this also counts for the EeePC 900SD (not 901) which only differs in screen, resolution and disk size as well as CPU, but not on the the case. So same size, same robustness, same battery, same mainboard, bigger screen, resolution, disk and faster CPU. (The 901 has a different CPU, a different battery, and a different, glossy and partially chromed case.) See Wikipedia for the technical specifications of all EeePC models.

ASUS’ only big FAILure

Stopping to sell most EeePCs with Linux and cowardly teaming up with Microsoft after having shown big courage to come out with a Linux only netbook. Well, you probably already know, but it’s better without Windows…

So basically you no more get these really neat netbooks from ASUS anymore and you get nearly no netbooks with Linux from ASUS in the stores anymore. It’s a shame.

Would I buy it again?

Sure.

Well, maybe I would also buy the 900SD, 900AX (replacing the harddisk with an SSD) or 702 (8G) instead of the 701, but basically they’re very similar. See Wikipedia for the differences between these EeePC models. And of course I still prefer the versions without Windows.

But despite the low price, the EeePC 701 is surprisingly robust and still works as on the first day (ok, except battery, the mouse button bar and the “n” key ;-), so I recently bought a second power supply (only white ones were available *grrrr*) and ordered a bigger third party battery plus an adapter to load the battery directly from the (second) power supply without EeePC inbetween.

What desktop do I use on the EeePC?

None.

I use ratpoison as window manager, uxterm, urxvt, and yeahconsole as terminal emulators (running zsh with grml based .zshrc even as root’s login shell :-), wicd-curses as network manager and xmobar (previously dzen2) with i3status as text-only panel. Installed editors are GNU Emacs 23, GNU Zile and nvi. (No vim. :-)

And of course a netbook wouldn’t be a netbook if it wouldn’t have a lot of network applications installed. For me the most important ones are: ssh, scp, autossh, sshfs, miredo, conkeror, git, hg, and rsync.

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. :-)

¹: 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. :-)

WYSE: Jetzt mit Linux 6! //at 01:36 //by abe

dkg hat gestern auf Pro-Linux einen Artikel über die neue grml 0.6 geschrieben. Soweit so gut und alles ganz toll. Nur ist da dieser Flash-Werbebanner von WYSE über dem Artikel.

Als erstes stieß mir das “Wo f hlt sich Tux am wohlsten?” auf. Kein Umlaut. Nuja, mag vielleicht noch an der frisch auf 10.0 geupgradeten SuSE liegen. (Ausführlicher Rant Bericht dazu kommt noch. *eg*)

Heftiger war allerdings die Antwort: “In einem Winterm ThinClient mit Linux Version 6!”

<sarcasm>Linux 6?!? Da ist aber ein altes Linux drauf. Ich hab’ schon Linux 10!</sarcasm>

Mal ganz davon abgesehen, daß ein Klick auf das Banner zu http://www.wyse.de/linux/ führt, was per META-Refresh mit einer Sekunde Verzögerung auf http://de.wyse.com/linux/ weiterleitet und damit auch nicht grade von sehr viel Durchblick in Sachen Medium und Leserschaft zeugt sowie den Groll desjenigen, der wissen will, was verdammt nochmal mit “Linux 6” gemeint sein könnte, nur noch weiter aufheizt.

Wann lernen die Marketing-Fuzzies endlich mal, daß es (noch) kein “Linux 6” oder “Linux 10” gibt, dafür aber wesentlich schnellere, bessere und sinnvollere Methoden als META-Refresh? (in diesem Fall z.B. die Werbung direkt mit der eigentlichen Seite verlinken… *hinthint*) Sorry, aber mit so ‘ner Werbung ist man zumindest auf Pro-Linux gewaltig fehl am Platz und vergrault sich eher potentielle Kunden als welche zu gewinnen. Ich werde jedenfalls WYSE zukünftig genüßlich meiden.