On Sat, 09.02.13 02:58, Michael Biebl (mbi...@gmail.com) wrote:
> basically works. I idid get a few error messages when the container
> was booted like
>
> Netlink failure for request 1: Operation not permitted
> Failed to configure loopback device: Operation not permitted
> Failed to enable ctrl
On Sat, 9 Feb 2013 02:58:05 +0100 Michael Biebl wrote:
> >> yes ... and there was a /usr/share/sysvinit/inittab, just not
> >> in /etc/inittab for reasons unknown ... i symlinked it and it gets
> >> a lot further (but not to a login prompt) now ...
> >
> > Uh, that's weird. Michael, Tollef, any id
2013/2/9 Michael Biebl :
> # in a F18 system
> systemd-nspawn -b -D /srv/sid/ /bin/systemd
This looks like that then:
Inside the container:
root@pluto:~# systemd-cgls
└ system
├ 1 /lib/systemd/systemd /bin/systemd
├ console-shell.service
│ ├ 89 bash
│ └ 97 systemd-cgls
├ rsyslog.service
2013/2/8 Lennart Poettering :
> On Fri, 08.02.13 13:31, Jake Edge (j...@lwn.net) wrote:
>> On Fri, 8 Feb 2013 21:19:22 +0100 Lennart Poettering wrote:
>> > Well, you'll have to build systemd inside the container, because you
>> > need to build it against the Debian version of the libraries, of
>>
On Fri, 08.02.13 13:31, Jake Edge (j...@lwn.net) wrote:
>
> On Fri, 8 Feb 2013 21:19:22 +0100 Lennart Poettering wrote:
>
> > Well, you'll have to build systemd inside the container, because you
> > need to build it against the Debian version of the libraries, of
> > course. Building it inside t
On Fri, 8 Feb 2013 21:19:22 +0100 Lennart Poettering wrote:
> Well, you'll have to build systemd inside the container, because you
> need to build it against the Debian version of the libraries, of
> course. Building it inside the container should be easy, even if you
> cannot make the container b
On Fri, 08.02.13 13:00, Jake Edge (j...@lwn.net) wrote:
> > What I did is this: I installed Debian unstable into a directory with
> > debootstrap, then installed Debian's systemd .deb into it and then
> > manually built systemd git in it and simply install it into the
> > container's /usr. That wo
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):
> >
> > # debootstrap --arch=amd64 uns
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):
>
> # debootstrap --arch=amd64 unstable debian/
> ...
> (needed to put /sbin in my path in order for deboots
so, i'm trying to follow along with systemd for admins part 6 and
hitting the following problem on Fedora 18 (audit=0, fwiw):
# debootstrap --arch=amd64 unstable debian/
...
(needed to put /sbin in my path in order for debootstrap to work, btw)
# systemd-nspawn -D debian/ /sbin/init
Spawning nam
10 matches
Mail list logo
