On Fri, 2013-10-04 at 11:56 -0500, Serge Hallyn wrote:
> Quoting Michael H. Warfield (m...@wittsend.com):
> > My second takeaway from the Linux Plumbers conference was to do an
> > automatic heuristic determination when we should enable autodev
> > (mounting of something on /dev/ in the container
Quoting Michael H. Warfield (m...@wittsend.com):
> My second takeaway from the Linux Plumbers conference was to do an
> automatic heuristic determination when we should enable autodev
> (mounting of something on /dev/ in the container at startup for things
> like systemd). If autodev is not enable
On Thu, 2013-10-03 at 23:30 +0100, Christian Seiler wrote:
> Hi there,
>
> > The initial heuristic, in this case, is the existence
> > of /etc/systemd/system in the container to enable autodev. This is
> > the
> > heuristic used in the lxc-fedora template but it applicable to all
> > systemd co
Hi there,
> The initial heuristic, in this case, is the existence
> of /etc/systemd/system in the container to enable autodev. This is
> the
> heuristic used in the lxc-fedora template but it applicable to all
> systemd containers, as far as I can determine.
Just a quick note about the specific
My second takeaway from the Linux Plumbers conference was to do an
automatic heuristic determination when we should enable autodev
(mounting of something on /dev/ in the container at startup for things
like systemd). If autodev is not enabled when it is required (systemd)
the container can cause t
