Tip

I ran into this issue a couple of days ago and cannot recall the exact error message. However, the problem was effectively that aptitude could not install the new kernel update because my partition had apparently run out of space. An interrupted update to Klipper is one thing and the Linux kernel a whole 'nother kettle of fishies. Thinking that I simply needed to free up some space on my partition, I checked the current status via df.

Since I keep forgetting this shortcut, here it is for posterity. Activating GNU Screen's scrollback feature can be done by pressing CTRL + a + [. This is especially handy when you are using Screen from within PuTTY.

While a number of sites provide additional Vim-esque shortcuts to navigate within the buffer, I've been able to get by fine with just the navigational arrow keys on my keyboard.

I got a new 3TB hard disk. While it's being detected in Windows 7, initializing it has proved to be impossible as I keep running into the following error:

The request could not be performed because of an I/O device error

After testing this one a couple of different systems and in Linux, I have arrived at the conclusion that the drive is screwed. Time to get it replaced.

Today, I'm trying to root one of my Android phones in order to install Cyanogen Mod 7.2! First issue: while attempting to root the phone (a Motorola Defy running Android 2.2.2 Froyo), I ran into the following error message while following this guide:
C:\Users\foo>adb push rageagainstthecage-arm5.bin /data/local/tmp/
cannot stat 'rageagainstthecage-arm5.bin': No such file or directory

This is my week of playing around with mail servers and I have been keeping an eye on the logs on a regular basis. I noticed that the auth.log was riddled with millions of these pointless (from my POV anyhow) log entries:

CRON: pam_unix(cron:session): session opened for user root by (uid=0)
CRON: pam_unix(cron:session): session closed for user root

While trying to debug a postfix authentication issue in Debian 6, I had to use testsaslauthd to test things out:
testsaslauthd -s smtp -u foo@example.com -p test

only to get the following error:
connect() : No such file or directory 0

This is apparently because a lot of people (and authors) follow the same guide for configuring postfix and saslauthd. One of the steps missing is to symlink and saslauthd directory to a location within postfix. To fix:

I've been trying to .. empower .. the Nagios 3 web interface in Ubuntu/Debian to allow me to turn off service checking at will. I do this when I am checking logs etc. to debug some issue and all the spam from Nagios' polling is getting in the way. Nagios comes with an option to "disable active checks of this service" which when click should, well, disable active checks of the service. Clicking it, however, resulted in the following message:

Nagios is currently not checking for external commands.

While setting up Drupal on a friend's Ubuntu server, I ran into the following error message:

This basically simply means that the PHP PDO extension has not been installed. It can be installed via something along the lines of:
sudo aptitude install php5-mysql

While you are at it, make sure that all the other PHP extensions that Drupal requires are also installed.

The following are some tools I'd like to note down that are handy when it comes to checking server configurations and security:

I just finished setting up postfix on a Debian 6 machine. All is peachy. However, when I checked my mail logs to see how things were going I noticed a number of entries for messages being sent from smmsp@example.com to root. Checking root's mail led to messages with the following content:
/usr/share/sendmail/sendmail: line 880: /usr/sbin/sendmail-msp: No such file or directory