Now that +VMware
has released a second
version of VMware Player (and presumably VMware Workstation, but I haven't checked) for Linux that will cause guaranteed data loss and upgrade problems on Ubuntu, I think the time has come to shame them publicly for it.
Because of the way their installer was written, VMware's installer will reorder your shutdown sequence in a way that SKIPS SYNCING AND UNMOUNTING FILESYSTEMS. This is more or less guaranteed to cause data loss eventually.
How do you prevent this from breaking your system? VMware's installer is calling the insserv command, which should never
be used on Ubuntu, so you can fool it by running `sudo dpkg-divert --local --rename /usr/sbin/insserv`, which will move it out of the way.
How can you tell if your machine has been screwed up by this? Look at the symlinks in /etc/rc6.d. If you see S40umountfs, S60umountroot, and S90reboot, you're fine. If you see S03umountfs, S03umountroot, and S03reboot, your machine is broken.
How do you recover if your system is broken? Here is the recommended fix:
mv /etc/rc6.d/S*reboot /etc/rc6.d/S90reboot
mv /etc/rc6.d/S*umountroot /etc/rc6.d/S60umountroot
mv /etc/rc6.d/S*umountnfs.sh /etc/rc6.d/S31umountnfs.sh
mv /etc/rc6.d/S*umountfs /etc/rc6.d/S40umountfs
mv /etc/rc6.d/S*sendsigs /etc/rc6.d/S20sendsigs
This bug manifests in subtle ways (for instance, I ran into it because my system wouldn't boot because D-Bus refused to start because the /var/run -> /run transition hadn't completed correctly when I upgraded to Oneiric), so if you use VMware Player/Workstation or have in the past used VMware Player/Workstation, you should check to make sure you're not affected.
Here's the bug where Ubuntu is tracking the issue: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/858122
, but it's a little hard to correct on our side when VMware is blatantly ignoring the way software is supposed to integrate with the system.