It seems that Samba 3.5 has problems binding its socket when running on dual-stack Linux systems. This is what I am seeing in log.smbd, right after starting Samba:

Recently I came across this link in #xbmc-linux on Freenode: http://www.webupd8.org/2010/11/alternative-to-200-lines-kernel-patch.html

Have you ever noticed that if you put cron jobs in /etc/cron.daily on a SLES machine, they seem to run at random times? I noticed it a few times, and I find it to be really annoying. Say, I rebooted a machine yesterday around 14:00, and today at 14:15, the machine starts rebuilding the man db, backing up the rpm db, cleaning /tmp, rotating logs, etc. Huh?! Looks like a bad idea to do such things when the system is currently in use by multiple people. Imagine that you put a database backup in there, and that backup locks your database...

In case you're annoyed by the fact that backspace doesn't work by default in vim on SLES, add this to /etc/vimrc or ~/.vimrc:

As you could read in one of my previous posts, I have been investigating my Sagem F@st 3464 modem a little, to see if it ran Linux (which it does). With the help of this topic, I was able to login into the modem with telnet. After entering the password and typing the "shell" command, I was presented an ash shell with BusyBox.