Quoting xlyz (<email address hidden>):
> @serge: udev and coreutils are already installed in default lucid container.
Of course, but they fail to upgrade because they expect mknod. As I was
saying, and as the blog you reference shows, you can let the upgrade succeed
by adding mknod to the devices access whitelist.
> if I add updates repo and just install openshh-server everything is
> fine.
Ok, good.
> if I try to full-upgrade, or just try to install udev from lucid-
> updates it throw
>
> Setting up udev (151-12.3) ...
> mknod: `/lib/udev/devices/ppp': Operation not permitted
yes.
> dpkg: error processing udev (--configure):
> subprocess installed post-installation script returned error exit status 1
>
> the other two packages have just udev as dependency.
yes.
As I say it should be possible to update the lxc-ubuntu template to
create 'lucid-updates' (etc) caches and containers, so that you don't
have to mess with this at all.
Quoting xlyz (<email address hidden>):
> @serge: udev and coreutils are already installed in default lucid container.
Of course, but they fail to upgrade because they expect mknod. As I was
saying, and as the blog you reference shows, you can let the upgrade succeed
by adding mknod to the devices access whitelist.
> if I add updates repo and just install openshh-server everything is
> fine.
Ok, good.
> if I try to full-upgrade, or just try to install udev from lucid- devices/ ppp': Operation not permitted
> updates it throw
>
> Setting up udev (151-12.3) ...
> mknod: `/lib/udev/
yes.
> dpkg: error processing udev (--configure):
> subprocess installed post-installation script returned error exit status 1
>
> the other two packages have just udev as dependency.
yes.
As I say it should be possible to update the lxc-ubuntu template to
create 'lucid-updates' (etc) caches and containers, so that you don't
have to mess with this at all.