From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Rene Rebe <rene@rocklinux-consulting.de>
Cc: kangur@polcom.net,
Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>,
rock-user@rocklinux.org
Subject: Re: Distributions vs kernel development
Date: Tue, 25 May 2004 19:53:12 +0200 [thread overview]
Message-ID: <1085507592.9516.14.camel@nosferatu.lan> (raw)
In-Reply-To: <20040525.102241.635758403.rene@rocklinux-consulting.de>
[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]
On Tue, 2004-05-25 at 10:22, Rene Rebe wrote:
> Hi,
>
> On: Mon, 24 May 2004 21:17:21 +0200,
> Martin Schlemmer <azarah@nosferatu.za.org> wrote:
> > On Sun, 2004-05-09 at 11:13, Rene Rebe wrote:
> >
> > > But the last time I took a look not even an installer or such. +
> > > Gentoo has no support for custom modifications not even thinking about
> > > a way to group such custom modifications / build configuration into a
> > > well defined way to form a distribution. + ROCK Linux has a real
> > > sandbox build environment, not this optimization via CFLAGS, and so on
> > > Gentoo wannabe.
> > >
> >
> > Weird .. last time I checked, Gentoo sandbox was originally derived from
> > ROCK Linux's sandbox wrapper ....
>
> Interesting ,) I did not know Gentoo copied ROCK Linux code, too.
Yeah, well, started out that way, as G. Bevin who wrote it at the
time, came from ROCK Linux (user I think). I do not think it resembles
it much, if at all anymore though, and I know some additions have
been added that you guys might think about, like also hooking execve
(meaning subsequent bash's will still have LD_PRELOAD=sandboxlib
in env, and if make/whatever sets LD_PRELOAD, the wrapper will add
the sandboxlib back, etc), and one or two others I think.
Regards,
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-25 17:53 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-07 15:53 Distributions vs kernel development Stephen Hemminger
2004-05-07 16:02 ` Arjan van de Ven
2004-05-07 16:03 ` Jeff Garzik
2004-05-07 21:20 ` Florian Weimer
2004-05-07 23:13 ` Paul Jakma
2004-05-09 6:49 ` Rene Rebe
2004-05-09 7:07 ` John Bradford
2004-05-09 8:52 ` Rene Rebe
2004-05-09 8:59 ` Grzegorz Kulewski
2004-05-09 9:13 ` Rene Rebe
2004-05-09 18:40 ` J. Ryan Earl
2004-05-24 19:17 ` Martin Schlemmer
2004-05-25 8:22 ` Rene Rebe
2004-05-25 17:53 ` Martin Schlemmer [this message]
2004-05-09 10:53 ` John Bradford
2004-05-12 19:11 ` Rob Landley
2004-05-19 8:49 ` John Bradford
2004-05-20 1:59 ` Rob Landley
2004-05-20 10:40 ` John Bradford
2004-05-24 18:31 ` Jon Portnoy
2004-05-25 10:49 ` John Bradford
2004-05-09 7:33 ` William Lee Irwin III
2004-05-09 21:06 ` Lech Szychowski
2004-05-07 16:05 ` Måns Rullgård
2004-05-07 16:22 ` Martin J. Bligh
2004-05-07 21:08 ` Daniel Egger
2004-05-07 17:09 ` Felipe Alfaro Solana
2004-05-07 17:28 ` Timothy Miller
2004-05-09 18:54 ` J. Ryan Earl
[not found] <1TfVQ-4T4-21@gated-at.bofh.it>
2004-05-07 18:42 ` Andi Kleen
2004-05-10 15:39 ` James Morris
2004-05-10 16:49 ` Chris Mason
2004-05-07 19:41 ` Pascal Schmidt
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=1085507592.9516.14.camel@nosferatu.lan \
--to=azarah@nosferatu.za.org \
--cc=kangur@polcom.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rene@rocklinux-consulting.de \
--cc=rock-user@rocklinux.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