public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chad Huneycutt <chad.huneycutt@acm.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Braindump wrt fakeroot and path sandboxing
Date: Fri Nov  2 09:46:02 2001	[thread overview]
Message-ID: <3BE2CDA2.9040301@acm.org> (raw)
In-Reply-To: 20011102170755.434fbea8.karltk@prosalg.no

Karl Trygve Kalleberg wrote:

> For those who're not up to date on this subject, the reason why we want a
> combination of subterfugue's SimplePathSandbox and fakeroot is that
> 1) We don't want ebuilds to write outside of ${S}, /tmp or ${D}
> 2) We really don't want to run the ebuilds as the real root, if we can
> fake it,
>    hence fakeroot. (Fakeroot lets the ebuild think it runs as root; in
> practice
>    this infers chown-privileges to a regular user).
> 3) We do not want to use subterfugue since it's too slow. Fakeroot seems
> to have
>    some features that are overkill for this project, and at any rate, we
> really
>    only want to do syscall tracing once. (The alternative would be a
> sandbox
>    process that contained fakeroot that contained the ebuild...)

I am sure I have heard the argument, but I can't remember it.  Is there 
a reason other than (2) that we can't just do a chroot to the image 
directory?

-- 
Chad Huneycutt
Ph.D. Student
http://www.cc.gatech.edu/~chadh




  reply	other threads:[~2001-11-02 16:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-02  8:10 [gentoo-dev] Braindump wrt fakeroot and path sandboxing Karl Trygve Kalleberg
2001-11-02  9:46 ` Chad Huneycutt [this message]
2001-11-05  8:54   ` Aron Griffis

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=3BE2CDA2.9040301@acm.org \
    --to=chad.huneycutt@acm.org \
    --cc=gentoo-dev@cvs.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