hello - i've been starting down the migration path from one lts release to another and trying out vm installs using fai 3.4.8ubuntu2 on precise hosts. the vms (ganeti-managed) are built using fai dirinstall.
it appears that upstart in precise behaves differently than lucid with respect to chroots (looks like it started supporting chroot "sessions" in natty). in my testing this caused problems with both lucid and precise guests. when performing a lucid dirinstall i ended up w/atd and acpid processes running outside the chroot. with a precise dirinstall init complained that it had had its "Configuration directory deleted" (referencing the path to the chroot) and was left in a somewhat confused state, logging errs like: init: Failed to spawn network-interface (tap0) pre-start process: unable to execute: No such file or directory on vm bring-up. my workaround for this was to add a hook to updatebase containing: fai-divert -a /sbin/initctl i was wondering if others have encountered this, whether there's a better workaround, and/or if initctl should be added to the list of automatic diversions in updatebase? thanks... andy -- andrew bezella <abeze...@archive.org> Internet Archive