public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Benda Xu <heroxbd@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Functional portage with namespace (Was: Integrating Portage with other package managers)
Date: Fri, 09 Mar 2018 09:46:15 +0900	[thread overview]
Message-ID: <87y3j2rs88.fsf_-_@gentoo.org> (raw)
In-Reply-To: <CAGfcS_kw=Vvp0-PVpJwhW=KKNWKPvoWwGuzCpTyAPz+eXWnfng@mail.gmail.com> (Rich Freeman's message of "Thu, 8 Mar 2018 12:50:36 -0500")

Rich Freeman <rich0@gentoo.org> writes:

> If you have util-linux installed then try running (as any user - you
> don't have to be root): unshare -i -m -n -p -u -C -f --mount-proc -U
> -r /bin/bash
>
> Congrats.  You are now root in a container.  You're in the same root
> filesystem as always.  You'll note that you can't actually see
> anything that you couldn't see before.  If you run ps -ea you'll see
> that you're the only process running on the system.  Devices like
> /dev/sda aren't actually accessible.  A lot of container managers
> would mount a new /dev and just hide most of that stuff.  You can
> probably imagine how something like this could be useful for isolating
> processes.  

Just a side node, this seems to be the ultimate sandbox we (Gentoo and
portage) are after.  With this, we might even be able to have portage
full functional: a build is completely determined and only determined by
the dependencies and USE flags.


  parent reply	other threads:[~2018-03-09  0:46 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-07 16:06 [gentoo-dev] Integrating Portage with other package managers anoteros
2018-03-07 16:51 ` Michael Orlitzky
2018-03-07 17:52   ` Alec Warner
2018-03-07 18:22     ` R0b0t1
2018-03-07 19:15       ` Alec Warner
2018-03-07 20:55         ` R0b0t1
2018-03-07 21:06           ` Rich Freeman
2018-03-08 16:44             ` R0b0t1
2018-03-08 17:50               ` Rich Freeman
2018-03-08 21:00                 ` R0b0t1
2018-03-08 21:38                   ` Rich Freeman
2018-03-09  0:46                 ` Benda Xu [this message]
2018-03-09  1:06                   ` [gentoo-dev] Functional portage with namespace (Was: Integrating Portage with other package managers) Rich Freeman
2018-03-09  2:11                     ` R0b0t1
2018-03-09  2:16                       ` Rich Freeman
2018-03-09 13:12                   ` X dej
2018-03-11 22:55                     ` [gentoo-dev] Functional portage with namespace Benda Xu
2018-03-16 23:40                       ` Kent Fredric
2018-03-17 13:32                         ` Francesco Riosa
2018-03-09 16:17               ` [gentoo-dev] Integrating Portage with other package managers Alec Warner
2018-03-09 17:44                 ` Rich Freeman
2018-03-09 20:11                 ` R0b0t1
2018-03-09 20:56                   ` Rich Freeman
2018-03-10  8:36           ` Kent Fredric
2018-03-07 18:42     ` Rich Freeman
2018-03-08  2:38       ` Benda Xu
2018-03-08  7:56         ` Dawid Weglinski
2018-03-07 20:12     ` Michael Orlitzky
2018-03-07 20:35       ` Alec Warner
2018-03-08  5:54   ` Benda Xu
2018-03-08 12:25     ` Michael Orlitzky
2018-03-08 14:47       ` kuzetsa
2018-03-08 15:23         ` kuzetsa
2018-03-08 20:59 ` James Le Cuirot
2018-03-10  5:26 ` Kent Fredric
2018-03-11 23:32 ` Benda Xu

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=87y3j2rs88.fsf_-_@gentoo.org \
    --to=heroxbd@gentoo.org \
    --cc=gentoo-dev@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