From: Aron Griffis <agriffis@gentoo.org>
To: gentoo-alpha@gentoo.org
Subject: Re: [gentoo-alpha] grsec patch for 2.4.23 with XFS
Date: Wed, 10 Dec 2003 18:22:19 -0500 [thread overview]
Message-ID: <20031210232219.GK9669@time> (raw)
In-Reply-To: <20031210234043.4498252d.gigerstyle@gmx.ch>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
Marc Giger wrote: [Wed Dec 10 2003, 05:40:43PM EST]
> Sorry, why to push out the do_brk fix? It's fixed only since 2.4.23
> or do I missing something??
The stable alpha-sources was 2.4.21-r1. The do_brk fix was added to all
existing alpha-sources ebuilds, but that doesn't push the fix out for
users when they do "emerge -u world" ... for that one needs to bump the
revision.
The rule in Gentoo is:
- If it's a compile-time problem, don't need to bump the revision
(because the user couldn't compile it anyway).
- If it's a run-time problem, bump the revision so that users will
get the new package when they update.
> Ok, I will see what and when I can do it. I think I will build it on
> top of the XFS patches. Is this ok?
> And whats about grsec? Should it be included too?
Yeah, I'd say just keep both of them. If alpha users don't want those
patches, they can always use vanilla sources or roll their own.
alpha-sources is intended to be like gentoo-sources, but for alpha...
Thanks!
Aron
--
Aron Griffis
Gentoo Linux Developer (alpha / ia64 / ruby / vim)
Key fingerprint = E3B6 8734 C2D6 B5E5 AE76 FB3A 26B1 C5E3 2010 4EB0
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-12-10 23:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 18:08 [gentoo-alpha] grsec patch for 2.4.23 with XFS Marc Giger
2003-12-10 19:15 ` Aron Griffis
2003-12-10 20:23 ` Marc Giger
2003-12-10 20:33 ` Aron Griffis
2003-12-10 22:40 ` Marc Giger
2003-12-10 23:22 ` Aron Griffis [this message]
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=20031210232219.GK9669@time \
--to=agriffis@gentoo.org \
--cc=gentoo-alpha@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