From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What to put in chroot mtab
Date: Sat, 02 Aug 2014 02:27:43 +0200 [thread overview]
Message-ID: <9cebf0b9-0330-45cc-bc91-912a5c66ad2b@email.android.com> (raw)
In-Reply-To: <CADPrc82YCbmYR6E+iCg1Sy9hua4YgGqSn6+oSH6C4Q1d3+7yfw@mail.gmail.com>
On 1 August 2014 23:46:00 CEST, "Canek Peláez Valdés" <caneko@gmail.com> wrote:
>
>Sorry; I almost missed this. Actually systemd-nspawn does much more
>than chroot'ing and bind-mounting some dirs; it also runs the
>container in its own namespace. And it can add virtual networking a
>lot more stuff. See [1] for details.
>
>Regards.
>
>[1] http://www.freedesktop.org/software/systemd/man/systemd-nspawn.html
Sounds like overkill just to create a chroot to build packages.
Is usefull if you want to isolate services into seperate containers. In which case this is just another system partitioning tool merged into the init system.
--
Joost
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2014-08-02 0:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 13:07 [gentoo-user] What to put in chroot mtab Peter Humphrey
2014-08-01 13:12 ` Peter Humphrey
2014-08-01 13:28 ` Dale
2014-08-01 20:46 ` J. Roeleveld
2014-08-01 21:31 ` Canek Peláez Valdés
2014-08-01 21:33 ` Canek Peláez Valdés
2014-08-01 21:39 ` J. Roeleveld
2014-08-01 21:44 ` Canek Peláez Valdés
2014-08-01 21:46 ` Canek Peláez Valdés
2014-08-02 0:27 ` J. Roeleveld [this message]
2014-08-02 0:21 ` J. Roeleveld
2014-08-02 10:08 ` Peter Humphrey
2014-08-01 23:39 ` Dale
2014-08-01 14:56 ` Peter Humphrey
2014-08-01 15:00 ` Canek Peláez Valdés
2014-08-01 15:07 ` Rich Freeman
2014-08-01 15:25 ` Peter Humphrey
2014-08-01 15:21 ` Peter Humphrey
2014-08-01 15:29 ` Canek Peláez Valdés
2014-08-01 16:50 ` Peter Humphrey
2014-08-02 18:28 ` Rich Freeman
2014-08-01 14:02 ` Rich Freeman
2014-08-01 19:32 ` Neil Bothwick
2014-08-01 20:40 ` J. Roeleveld
2014-08-02 10:38 ` Peter Humphrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9cebf0b9-0330-45cc-bc91-912a5c66ad2b@email.android.com \
--to=joost@antarean.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox