bably just as well, since i
didn't set a root password :)
what *I* did, that didn't work was:
# debootstrap unstable /srv/mumble
that is what resulted in a lack of /etc/inittab fwiw ... perhaps that's
useful for future googlers ...
thanks,
jake
--
Jake Edge - LWN - j...@lwn.n
on that ...
it is nearly two years old, but your "Here's an example how in three
commands you can boot a Debian OS on your Fedora machine inside an
nspawn container" in systemd for admins VI seems a little less that
entirely accurate :)
thanks for the help ...
jake
--
Jake Ed
On Fri, 8 Feb 2013 20:24:55 +0100 Lennart Poettering wrote:
> On Fri, 08.02.13 09:54, Jake Edge (j...@lwn.net) wrote:
>
> >
> > so, i'm trying to follow along with systemd for admins part 6 and
> > hitting the following problem on Fedora 18 (audit=0, fwiw):
> &
spawn -D debian/
but can't boot it ... init 1 and 2 are the same ... maybe this is some
problem with debootstrap? or the current state of Debian unstable? or
do i need to use systemd in the Debian for this to work? i thought
not ...
thanks,
jake
--
Jake Edge - LWN - j...@lwn.
On Tue, 5 Feb 2013 20:43:58 +0100 Kay Sievers wrote:
> On Tue, Feb 5, 2013 at 8:34 PM, Jake Edge wrote:
> > Howdy Lennart and the systemd gang,
> >
> > Trying to play with systemd-nspawn on a Fedora 18 system using a
> > 3.8-rc5 kernel (if it matters) with audit turned
go to another window and kill the
nspawn ...
any help would be appreciated, thanks!
jake
--
Jake Edge - LWN - j...@lwn.net - http://lwn.net
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
guess, even those
that are currently expecting to find shared mounts. And that probably
was true with or without the change Lennart made ...
jake
--
Jake Edge - LWN - j...@lwn.net - http://lwn.net
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Fri, 01 Feb 2013 16:33:26 -0500 Colin Walters wrote:
> On Fri, 2013-02-01 at 12:50 -0700, Jake Edge wrote:
>
> > I am not sure that I want the default to be "private", but if I did,
> > what is the proper, systemd-ish way to do so?
>
> If you're c
c411f0a0
where you say:
Setups which prefer the default of "private" should undo this change
via invoking "mount --make-private /" or a similar command after boot.
I am not sure that I want the default to be "private", but if I did,
what is the proper, systemd-is