All right, yes, the fact that you let udev upgrade succeed is the
problem. If you look in /etc/init, you now have udev.conf, whereas
before (or in a non-upgraded container) you had udev.conf.orig.
Please see /usr/lib/lxc/lxc/templates/lxc-ubuntu for some of the
slicing and dicing it does inside /etc/init, including:
chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls u*.conf); do
mv $f $f.orig; done'
chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls
tty[2-9].conf); do mv $f $f.orig; done'
chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls
plymouth*.conf); do mv $f $f.orig; done'
chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls
hwclock*.conf); do mv $f $f.orig; done'
chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls module*.conf);
do mv $f $f.orig; done'
Since we don't actually use udev in the container, but since
intricate package dependencies make it hard to remove, I think
my earlier suggestion of having dpkg 'hold' the udev package
is going to be the way to go.
-serge
------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users
