qemu: could not load PC BIOS 'bios-256k.bin' The file exists here: /usr/share/qemu/bios-256k.bin It is symlinked to here: /usr/share/seabios/bios.bin A quick fix is manually specifying the BIOS: -bios /usr/share/qemu/bios-256k.bin........

You can read lots of posts about this issue but there is not much information about why this is the case or how grub determines the root= device name. Some even suggest modifying grub.cfg manually which is a disaster as the next kernel update will cause grub to revert back to the device name. For most people this won't be an issue but those using template system, automated deployments and working in embedded may run into this issue with custom embedded and created minimal kernel........

This is not so much of a vi error as it is a physical filesystem error in the sense that the file you are trying to write to is a symlink and the destination doesn't exist or for some other reason is inacessible. So vi is tellng you "you're writing to a symlinked file and the file the symlink points to cannot be written to". This is especially highlighted byt he fact that if you are using wq! to write and you still get the error.........

ecryptfs-mount-private Enter your login passphrase: Inserted auth tok with sig [ee16d84] "into the user session keyring mount: No such file or directory" [ 156.118113] ecryptfs_mount: kern_path() failed [ 156.118431] Reading sb failed; rc = [-2] [ 164.233055] traps: mate-notificati[3472] trap int3 ip:7f43d7002c13 sp:7fff162c6600 error:0 [ 166.017061] ecryptfs_mount: kern_path() failed........

This can be very tricky, say you are doing development on a file that is symlinked. Doing a "cp dev.file dev.file-bk" won't do what you expect, it just links back to the same file so you haven't copied or backed anything up. You need the "-H" switch to copy the actual file that is referenced by the symlink: cp -Hdev.file dev.file-bk........

When trying to even cd or ls the mounted OCFS2 partition it crashes. Ithink this is a combination of VMWare Server's problem and the way I mounted and symlinked to it. More than anything this shows the problem and lack of forsight with VMWare, but also that OCFS2 is easily crashed if you do strange things. Output of /var/log/messages for OCFS2 Apr 10 15:57:45 localhost kernel: [84331.691258] Modules linked in: vmnet vmci vmmon ocfs2_stac........