Quoting Michael H. Warfield (m...@wittsend.com):
On Tue, 2013-11-19 at 14:53 -0600, Serge Hallyn wrote:
Quoting Michael H. Warfield (m...@wittsend.com):
If autodev is not specifically set to 0 or 1, attempts to determine if
systemd is being utilized and forces autodev=1 to prevent host
I guess I should comment as well...
On Wed, 2013-11-20 at 10:59 -0600, Serge Hallyn wrote:
Quoting Michael H. Warfield (m...@wittsend.com):
On Tue, 2013-11-19 at 14:53 -0600, Serge Hallyn wrote:
Quoting Michael H. Warfield (m...@wittsend.com):
If autodev is not specifically set to 0
On Wed, Nov 20, 2013 at 10:59:51AM -0600, Serge Hallyn wrote:
Quoting Michael H. Warfield (m...@wittsend.com):
On Tue, 2013-11-19 at 14:53 -0600, Serge Hallyn wrote:
Quoting Michael H. Warfield (m...@wittsend.com):
If autodev is not specifically set to 0 or 1, attempts to determine if
Quoting Michael H. Warfield (m...@wittsend.com):
If autodev is not specifically set to 0 or 1, attempts to determine if
systemd is being utilized and forces autodev=1 to prevent host system
conflicts and collisions.
If autodev is enabled and the host /dev is mounted with devtmpfs
or
On Tue, 2013-11-19 at 14:53 -0600, Serge Hallyn wrote:
Quoting Michael H. Warfield (m...@wittsend.com):
If autodev is not specifically set to 0 or 1, attempts to determine if
systemd is being utilized and forces autodev=1 to prevent host system
conflicts and collisions.
If autodev is
Crap...
Playing around with git and I totally forgot to sign off on these
things...
Signed-off-by: Michael H. Warfield m...@wittsend.com
On Mon, 2013-11-11 at 20:08 -0500, Michael H. Warfield wrote:
If autodev is not specifically set to 0 or 1, attempts to determine if
systemd is being
