From: Brandon Hale <brandon@comp-u-tek.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] chroot USE flag?
Date: 18 Jul 2003 02:44:56 -0400 [thread overview]
Message-ID: <1058510696.8671.7.camel@y0shi> (raw)
In-Reply-To: <20030717125214.GB1205@fuerzag.ulatina.ac.cr>
On Thu, 2003-07-17 at 08:52, Alvaro Figueroa Cabezas wrote:
> On Jul 18 01:15, Brandon Hale wrote:
> > I propose a new USE flag for a few key services that would install the
> > package in a chroot "out of the box."
>
> > I further discussed this idea w/ memebers of the gentoo-hardened team
>
> Well, it the idea is to harden boxes, this chroot flag should
> apply to every service thinkable... (And this is a _lot_ of work)
>
> But is the idea is to really harden boxes, chroots should be forgoten,
> and capabilities applied :).
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-07-18 2:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 5:15 [gentoo-dev] chroot USE flag? Brandon Hale
2003-07-17 12:52 ` Alvaro Figueroa Cabezas
2003-07-18 6:44 ` Brandon Hale [this message]
2003-07-18 6:54 ` Brandon Hale
2003-07-18 3:08 ` Ned Ludd
2003-07-18 6:43 ` Toby Dickenson
2003-07-18 2:08 ` Alvaro Figueroa Cabezas
2003-07-18 0:49 ` Matt Rickard
2003-07-18 1:25 ` Christian Axelsson
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=1058510696.8671.7.camel@y0shi \
--to=brandon@comp-u-tek.com \
--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