[Lxc-users] [PATCH 1/1] Update ubuntu templates

[Serge Hallyn]

Quoting Daniel Lezcano (daniel.lezcano at free.fr):
> On 01/23/2011 06:00 AM, Serge Hallyn wrote:
> >Quoting Daniel Lezcano (daniel.lezcano at free.fr):
> >>On 01/21/2011 06:10 PM, Serge Hallyn wrote:
> >>>Rename 'ubuntu' template to 'lucid'
> >>>
> >>>Add new maverick and natty templates, which do much less tweaking
> >>>of the environment.  These should only be used on a kernel which
> >>>supports sysfs tagging for /sys/class/net, as udev will be running
> >>>in the container.
> >>>
> >>>The natty template needed to slightly change the installed packages
> >>>for dhclient to be correclty installed.
> >>>
> >>>Signed-off-by: Serge Hallyn<serge.hallyn at canonical.com>
> >>>---
> >>While playing with natty and maverick containers I noticed at
> >>startup the udev events are broadcast to all the udev daemons
> >>running on the host and the containers. IMO that should not occur.
> >>
> >>I am looking at the lib/kobject_udev.c and net/af_netlink.c and I
> >>suspect there is a bug with the broadcast filtering of the events
> >>...
> >When I was testing on natty I was pretty sure i only saw syslog
> >entries for the container, not the host - but I may not have
> >been looking for the right thing.  What exactly did you see?
> 
> For example, if you use the command udevadm --trigger in a
> container, you will see the udev daemons receiving the events in
> both the host and in the container.

That's what I mean - I was doing 'udevadm --trigger' in a container,
but based just on the PIDs of udev processes telling syslog that
they were handling events, it seemed to me that they must all be in
a container.

Were you going based on syslog, or did you have another way to
get udevd to tell you it had processed events?

-serge