On Wed, Nov 16, 2011 at 07:52, Pandu Poluan <[email protected]> wrote: > > On Nov 16, 2011 3:21 AM, <[email protected]> wrote: >> >> The more scenarios we can test, the better. mdev might shave a second >> or two off the VM's bootup time, versus udev. >> > > Okay, I have two staging VMs on XenServer and one on VMware. I'm going to > report back what happens. If anything bad happens, *should* be an easy > rollback to the previous snapshot. >
1st Report: amd64-hardened on XenServer, PV-mode Booted okay. There's 1 (one) red asterisk but it booted so fast I can't see what that asterisk was about. `less /var/log/rc.log` did not show anything... ... but I realized that I can scroll up on XenServer console, so I saw that the asterisk said: * Error: fopen(/lib64/rc/init.d/rc.log) failed: No such file or directory Nothing serious though. I think it was because /lib64/rc/init.d got overlaid by rc-svcdir during boot, so rc.log disappeared. (Doing `mount -o bind / /mnt/rooot && ls /mnt/rooot/lib64/rc/init.d` showed that rc.log existed in the non-overlaid /lib64/rc/init.d) /dev/xvdb* (which was not created statically in the non-overlaid /dev) appeared. /dev/xvdd appeared when I attached an ISO image to the VM. mount /dev/xvdd /mnt/cd worked. I could `ls /mnt/cd` and see the contents of the CD. "Ejecting" the ISO image made /dev/xvdd disappear (as it should). Networking is okay. The Xen virtual console (hvc0) works okay. `rc-update | grep dev` showed `udev-postmount` still part of default, so I did `rc-update del udev-postmount default` and rebooted, and all were still well (and still a glint of red asterisk). Unmerging udev went well. All in all, rebooting after switching to udev *seems* to be faster. Rgds, -- FdS Pandu E Poluan ~ IT Optimizer ~ • LOPSA Member #15248 • Blog : http://pepoluan.tumblr.com • Linked-In : http://id.linkedin.com/in/pepoluan
