I recently had cause to install FlightGear 2.4.0 on Ubuntu 10.04. It’s not packaged in the form of a deb yet, so I’ve documented the commands I used. No guarantees this’ll work for you, as I haven’t tested them rigorously; and I’m assuming some Linux and command-line knowledge.

• Install some dependencies (this may not be a complete list; it’s simply the set I was missing). If you get warnings below about missing libraries, hunt around for them in the Ubuntu archives.

  sudo apt-get install libboost-graph-dev libopenal-dev libalut-dev libopenscenegraph-dev libjpeg62-dev libplib-dev

• Get SimGear 2.4.0, unpack it into a temporary directory, and install it (checkinstall will create a deb for you as a side-effect, and install that so you can uninstall with apt if necessary). I’m using -j10on make as I have many CPU cores; you may want to tune this to match your number, although it will only affect the speed of build.

  ./configure --with-jpeg-factory ; make -j10 ; sudo checkinstall

• Get the FlightGear 2.4.0 source(at the time of writing, the file with the slightly more recent timestamp) and install it:

  ./configure ; make -j10 ; sudo checkinstall

• Get the 2.4.0 “Base” package and unpack it to /usr/share/local/flightgear. The tarball contains a data/ directory at the top level; you need to move directories around after unpacking so that the flightgear/directory contains direct subdirectories:

  ls -1 /usr/local/share/flightgear/
  AI
  Aircraft
  Airports
  Astro
  ATC
  AUTHORS
  etc...

• You’re done! Run fgfs to launch Flightgear (there’s no GUI so you’ll have to become familiar with the command-line switches).

I discovered that the solution was to disable 3D graphics acceleration – in the VM’s settings, untick Display / Accelerate 3D Graphics. The VM now works smoothly.

I also recently installed µswsusp on one of my laptops, a userspace hibernation facility. I didn’t really connect the dots until one day I left the laptop running, coming back to find it hibernated. When I tried to resume, the boot process hung as the kernel complained it couldn’t resume the image. After a facepalm moment (of course this wouldn’t work – the encryption key isn’t constant across boots -  you have to use a constant key if you want to get hibernation working), I eventually figured out how to book the machine: use the noresume parameter when booting the kernel.

The only thing blocking me from using this now was getting the Grub menu to come up so I could change that kernel boot line. It appears that in the switch to Grub 2, the key to do this changed to the Shift key, from the Esc key as it had been in Grub 1. After I managed to bring up the menu, I could boot the kernel without resuming the image. I then deinstalled µswsusp.

sudo aptitude install usb-modeswitch
sudo usb_modeswitch -v 0x12d1 -p 0x1521 -M \
 55534243123456780000000000000011060000000000000000000000000000

Once the modeswitch command is executed, the USB stick will present itself as a modem and you can use the standard Ubuntu NetworkManager mechanisms to define your service provider and set up the connection. The stick should remember its state, and so you should only ever need the above utility (and command) once.

1. Install two packages if they aren’t already installed (gpointing-device-settings is the more modern version of gsynaptics and will uninstall it if it’s installed):

   sudo aptitude install xserver-xorg-input-synaptics gpointing-device-settings

2. Start gpointing-device-settings from the command line and select “Touchpad off”, as shown here:
3. Exit the tool and reboot.

I particularly wanted something more meaty than my NSLU2 so I could do full-disk encryption, fully-encrypted offsite backups, so it seemed ideal. The variation I ordered has:

• Dual-Core Intel(R) Atom(TM) CPU 330 (1.6GHz)
• 1GB RAM
• 1TB Western Digital “GreenPower” Hard Drive
• Intel 82945G/GZ Integrated Graphics
• Onboard audio, 6 USB 2.0 ports, a serial port, a parallel port
• Integrated 100MB Ethernet
• RaLink RT2561/RT61 802.11g PCI Wireless Card
• DVD-RW drive

(total approximately £370)

Very PC seem fairly reputable, and their customer service was adequate, if not outstanding (they didn’t keep me up-to-date on my order until I emailed them, at which point they interrupted me by calling, they didn’t always respond to sales enquiry emails, and were coy about their returns policy). Nevertheless, they do offer a 3-year warranty as standard, which shows confidence in their products.

Nevertheless, the PC arrived fairly promptly (~5 days), and appears to be robustly built: whilst compact, the case is very solid and feels strong. The whole machine exudes a feeling of high build quality, and is mostly constructed from metal rather than cheap plastic. Here’s what it looks like from the outside:

The machine came shipped with Ubuntu (Desktop) pre-installed, although I rapidly reinstalled it with the Ubuntu Server (a wise decision anyway, since VeryPC forgot to include information on the default username and password!). As such, every piece of hardware works well with the exception of the wi-fi card, which, using the default driver, suffered from frequent drop-outs (a problem I’ve had before with the RaLink cards under Linux). Replacing the standard driver with a ndiswrapper verison (more information here and here) resolved this. Channels 12 and 13 also don’t seem to work correctly with this driver, so the wi-fi network has to run on another channel.

The main disappointment was the noise generated by the machine. To be fair, VeryPC described it as ‘ultra quiet’, and with other noisy items on (e.g. a modern laptop with the fan spinning), you won’t hear it. However, in an otherwise silent room, you definitely will – and you don’t have to get close to it either. I haven’t done any formal tests, but if you want a completely silent machine, this is not the one for you. If you can tolerate a small amount of fan noise in very quiet environments, it should be OK.

Another minor point: the machine has an external power supply brick (like a laptop). VeryPC didn’t make this clear, but you should factor it in if you’re considering buying one.

Otherwise, though, I’m fairly satisfied. It does what it says on the tin, I’ve had no reliability problems whatsoever (save for the wi-fi card issues mentioned above), and the machine is running 24h a day and doing a solid job. So kudos to veryPC for putting together a good bit of kit.

I recently installed Ubuntu 64bit (amd64) on my Lenovo Thinkpad T61. Unfortunately, the Network Client is not available in a 32bit edition. So I had to perform a few tweaks to get it to work. Here’s the steps I took:

• Install the ia32-libs package and all it’s dependencies:

sudo apt-get install ia32-libs

• Install the AT&T client itself (IBM colleagues can obtain this from the OCDC website):

sudo dpkg -i --force-architecture agnclient_1.0~2.0.1.3000-3_i386.deb

• Add some symlinks:

sudo ln -s /usr/lib32/libssl.so.0.9.8 /usr/lib32/libssl.so.4
sudo ln -s /usr/lib32/libcrypto.so.0.9.8 /usr/lib32/libcrypto.so.4

• You should now be able to start the Network Client from the Internet section of the Gnome menu, or from /opt/agns/bin/agnclient. Click Connect and enter your details as normal.