From: Markus Nigbur <pYrania@c0ffeine.de>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Gentoo Grsecurity Poll
Date: Thu, 7 Aug 2003 15:13:56 +0200 [thread overview]
Message-ID: <20030807151356.467e853b.pYrania@c0ffeine.de> (raw)
In-Reply-To: <20030807130203.GD25313@enki.datanode.net>
On Thu, 7 Aug 2003 09:02:03 -0400
Michael Cummings <mcummings@gentoo.org> wrote:
> On Thu, Aug 07, 2003 at 08:46:46AM -0400, Chris Gianelloni wrote:
> > On Wed, 2003-08-06 at 18:48, Ned Ludd wrote:
> > > Comments, suggestions and feedback are welcome.
> >
> Perhaps a silly question, but why are patches rolled as their own kernels at
> all? Seems to my little brain (yes, it's real small when it comes to these
> matters) that it would almost make more sense to offer the vanilla kernel as
> is, then have each of these (currently their own ebuilds) patches as add on
> ebuilds, such as emerge vanillia-kernel, emerge grsecurity-patch, emerge
> nvidia-patch, etc. After all, it's not like the ebuild for the kernel
> compiles it in the first place, and as far as I know these patches
> add/replace to the existing structure, right? Just a random thought, feel
> free to ignore :)
we had a discussion about this on bugzilla with ck-sources 2.4.21.
it would be nice to introduce some local flags for the kernel patches.
Bug #22822
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-08-07 13:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 22:48 [gentoo-dev] Gentoo Grsecurity Poll Ned Ludd
2003-08-06 22:55 ` Stuart Herbert
2003-08-06 22:55 ` Mike Frysinger
2003-08-07 12:46 ` Chris Gianelloni
2003-08-07 13:02 ` Michael Cummings
2003-08-07 13:13 ` Markus Nigbur [this message]
2003-08-07 13:16 ` Spider
2003-08-07 13:38 ` Chris Gianelloni
2003-08-07 14:19 ` Stephen Clowater
[not found] ` <20030808172153.GA31148@grsecurity.net>
2003-08-08 22:05 ` [gentoo-dev] Re: [grsec] " Ned Ludd
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=20030807151356.467e853b.pYrania@c0ffeine.de \
--to=pyrania@c0ffeine.de \
--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