Hey Serge,
On Wed, 2013-08-14 at 07:13 -0500, Serge Hallyn wrote:
> Quoting Michael H. Warfield (m...@wittsend.com):
> > On Tue, 2013-08-13 at 20:57 -0500, Serge Hallyn wrote:
> > > The current code is testing for systemd on the host. That's not right.
> > > You're right that checking for the r
Quoting Michael H. Warfield (m...@wittsend.com):
> On Tue, 2013-08-13 at 20:57 -0500, Serge Hallyn wrote:
> > The current code is testing for systemd on the host. That's not right.
> > You're right that checking for the running systemd in the guest isn't
> > right either :)
> >
> > So I'd say th
On Tue, 2013-08-13 at 20:57 -0500, Serge Hallyn wrote:
> Quoting Michael H. Warfield (m...@wittsend.com):
> > Woa! Hold! Time out. Do not do this.
> >
> > On Tue, 2013-08-13 at 16:36 +0900, Satoshi Matsumoto wrote:
> > > Configure the guest init based on whether the PID 1 process is systemd
>
Quoting Michael H. Warfield (m...@wittsend.com):
> Woa! Hold! Time out. Do not do this.
>
> On Tue, 2013-08-13 at 16:36 +0900, Satoshi Matsumoto wrote:
> > Configure the guest init based on whether the PID 1 process is systemd
> > or not.
>
> > In the template for Fedora, currently the guest
Woa! Hold! Time out. Do not do this.
On Tue, 2013-08-13 at 16:36 +0900, Satoshi Matsumoto wrote:
> Configure the guest init based on whether the PID 1 process is systemd
> or not.
> In the template for Fedora, currently the guest is configured based on
> whether the /bin/systemd exists in the
Configure the guest init based on whether the PID 1 process is systemd
or not.
In the template for Fedora, currently the guest is configured based on
whether the /bin/systemd exists in the host or not. This doesn't work
correctly because the /usr/bin/systemd symlink has been removed from the
syste
