On Thu, 2014-10-23 at 22:11 +0200, Ralf Mardorf wrote: > On Thu, 2014-10-23 at 22:08 +0200, Ralf Mardorf wrote: > > On Thu, 2014-10-23 at 15:52 -0400, [email protected] wrote: > > > given that Ubuntu will use it in the future > > > > Systemd is the future init process of _all_ Linux distros. I respect the > > work of the Ubuntu Studio developers, that's why I monitor your work, > > but my favourite distro is Arch Linux, so I'm quasi forced to use > > systemd since a very long time. I really hate systemd, the only > > advantage IMO is systemd-nspawn over chroot. > > > > YMMV! :D > > Send from the wrong account ;).
PS: [root@archlinux rocketmouse]# systemd-nspawn -D /mnt/saucy Spawning container saucy on /mnt/saucy. Press ^] three times within 1s to kill container. root@saucy:~# apt-get update Err http://dl.google.com stable InRelease Err http://de.archive.ubuntu.com saucy InRelease [snip] Shit happens, but usually I'm able to maintain one Linux install while running another Linux install and systemd-nspawn makes it easier than a chroot. Pff, that's the so called "demo effect". It worked a hundred times before, it failed for the very fist time now. Wow! ;). *lol* -- ubuntu-studio-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
