On 1 August 2014 23:44:11 CEST, "Canek Peláez Valdés" <can...@gmail.com> wrote: >On Fri, Aug 1, 2014 at 4:39 PM, J. Roeleveld <jo...@antarean.org> >wrote: >> On 1 August 2014 23:33:05 CEST, "Canek Peláez Valdés" ><can...@gmail.com> wrote: >>>On Fri, Aug 1, 2014 at 4:31 PM, Canek Peláez Valdés ><can...@gmail.com> >>>wrote: >>>> On Aug 1, 2014 3:46 PM, "J. Roeleveld" <jo...@antarean.org> wrote: >>>>> >>>>> On 1 August 2014 15:28:01 CEST, Dale <rdalek1...@gmail.com> wrote: >>>>> >Peter Humphrey wrote: >>>>> >> On Friday 01 August 2014 14:07:08 I wrote: >>>>> >> >>>> >>>> That's still too long :) >>>> >>>> With systemd-nspawn, you only do: >>>> >>>> systemd-nspawn -D /mnt/gentoo >>>> >>>> Systemd takes care of /dev, /sys, etc. If the container has systemd >>>> installed, you can do >>>> >>>> systemd-nspawn -bD /mnt/gentoo >>>> >>>> and the services inside the container will be started like in a >>>regular boot >>>> (you'll need to set the root password for the container). >>>> >>>> Also, if you want to share the /usr/portage directory between host >>>and >>>> container, you only need to >>>> >>>> systemd-nspawn --bind=/usr/portage -bD /mnt/gentoo >>> >>>Oh, and I forgot: to stop the container, just log out if the >container >>>runs OpenRC, or run systemctl poweroff if the container runs systemd. >>> >>>Regards. >> >> That script could easily be written in C and compiled and then called >in a similar way as systemd-nspawn. > >And yet nobody has done it and got it included in most distributions.
Because there is no need. If all you need is merge a few lines into a single command, puttincg it into a shell script is quicker and far easier to maintain. >> What your command does is basically the same apart from doing >something different from using chroots. > >True, but still it's shorter ;) chroot.sh is only 9 characters. Naming the script 'a' would be even shorter. -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
