From: Joshua Pollak <pardsbane@offthehill.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Sandbox suggestion
Date: Tue, 11 Dec 2001 11:22:03 -0500 [thread overview]
Message-ID: <E16DpgG-0004bQ-00@johnson.mail.mindspring.net> (raw)
In-Reply-To: <3C15CC48.7080904@theleaf.be>
On Tuesday 11 December 2001 4:05, you wrote:
> Because then any script that refers to /bin/bash during the installation
> process uses the static bash, while the purpose is this the dynamic bash
> is used. Of course all the scripts could be patched, but then the use of
> the sandbox gets quite a bit devaluated.
Fair enough.
>
> Joshua Pollak wrote:
> >Hi,
> >
> >Just wondering, but I had a suggestion for the dynamic bash ebuild: Rather
> >than replacing the static bash and moving the static bash to /bin/sbash
> >(shouldn't that be /sbin/sbash?) anyway, why not just install the new
> > shell to /bin/dyn-bash or dbash or something, and make the sandbox
> > scripts call everything via that shell?
> >
> >I'm not sure if that's technically possible or not, but it seemed like it
> >would make a lot of things simpler, and reduce the risk of sysadmins
> > messing something up.
> >_______________________________________________
> >gentoo-dev mailing list
> >gentoo-dev@gentoo.org
> >http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2001-12-11 16:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 4:51 [gentoo-dev] Sandbox suggestion Joshua Pollak
2001-12-11 9:05 ` Geert Bevin
2001-12-11 16:22 ` Joshua Pollak [this message]
2001-12-11 18:04 ` Zach Forrest
2001-12-11 18:23 ` Geert Bevin
2001-12-11 19:21 ` Joshua Pollak
2001-12-11 19:25 ` Geert Bevin
2001-12-11 19:40 ` Zach Forrest
2001-12-11 20:04 ` Daniel Robbins
2001-12-11 20:16 ` Zach Forrest
2001-12-11 20:17 ` Daniel Robbins
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=E16DpgG-0004bQ-00@johnson.mail.mindspring.net \
--to=pardsbane@offthehill.org \
--cc=gentoo-dev@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