Here is a quick how-to for password protecting and encrypting your partition using cryptsetup under Ubuntu/Kubuntu Oneiric Ocelot. It should work for older versions too but haven’t tested it.
cryptsetup luksFormat /dev/sdaX
cryptsetup luksOpen /dev/sdaX cryptname
echo 'cryptname /dev/sdaX none luks' >> /etc/crypttab
echo '/dev/mapper/cryptname /media/cryptname ext4 defaults 0 2' >> /etc/fstab
Obviously you have to be root and have cryptsetup installed.
PS: I’m NOT responsible for any damage or data loss caused by executing the supplied code.
To fix the recent bug with VMware Player 2.5.3 and Workstation 6.5.3 Build 185404 under Karmic Koala Ubuntu just paste this line in your console before launching vmplayer/vmware:
you may also modify the VMware starting script so you don’t have to export it every time.
With no surprise the update from Interpid Ibex to Jaunty Jackalope was not as easy as I hoped. After booting the fresh 2.6.28 kernel I was welcomed with “Press enter for maintenance (or type Control-D to continue)” and errors when trying to mount my RAID0. After some investigations found that the devices are now named md_d* and there are some devices in /dev/md/. Because of this change I had to do the following things to get my raid up and running:
- Reassemble the raid (check if it is inactive with less /proc/mdstat) – in my case the command looked like this:
mdadm --assemble /dev/md_d1 /dev/sdb2 /dev/sda5
mdadm --detail --scan >> /etc/mdadm/mdadm.conf and comment your previous ARRAY definition in the config file
/etc/fstab if needed
Also if DKMS fails to build the new NVIDIA driver be sure to check that you have installed the headers files (the upgrade process did not install them for me).
Again : I’m NOT responsible for any damage or data loss you might experience. Backup often, backup soon!
After switching from Debian Unstable to Kubuntu 8.10 I reinstalled my VMware Player 2.5.1 and started my Windows XP virtual machine. Soon I found that most of the keys near the numeric pad (del, home, right enter, etc) are either not working at all or doing wrong things. The obvious reason was some wrong keyboard mappings.
$ echo 'xkeymap.nokeycodeMap = true' > ~/.vmware/config
or if the config already exists
$ echo 'xkeymap.nokeycodeMap = true' >> ~/.vmware/config
More info here