From: Marc Giger <gigerstyle@gmx.ch>
To: Jay Maynard <jmaynard@conmicro.cx>, jwsacksteder@ramprecision.com
Cc: gentoo-alpha@lists.gentoo.org
Subject: Re: [gentoo-alpha] vanilla-sources vs alpha-sources
Date: Wed, 25 Feb 2004 20:07:18 +0100 [thread overview]
Message-ID: <20040225200718.03799597.gigerstyle@gmx.ch> (raw)
In-Reply-To: <20040225183049.GA18436@thebrain.conmicro.cx>
On Wed, 25 Feb 2004 12:30:49 -0600
Jay Maynard <jmaynard@conmicro.cx> wrote:
> On Wed, Feb 25, 2004 at 01:25:15PM -0500,
> jwsacksteder@ramprecision.com wrote:
> > Considering the recent security issues, I want to move up to 2.4.25.
> > It looks like I'm stuck with vanilla-sources unless someone is
> > planning on updating alpha-sources soon.
alpha-sources-2.4.21-r4 should contain all security patches!
If you don't use ipv6, ipsec etc. you should be fine with
vanilla-sources.
>
> I'm currently working on building a new LiveCD, but once that's done,
> I'd be willing to look at this one.
>
> Just what was done to vanilla-sources to get to alpha-sources?
A lot! Some month ago I made a new ebuild for 2.4.23 (search archive),
but it was never picked up and integrated to portage:-(
I'm willing to do the same for 2.4.25 but I'm still waiting for some
updated patches (e.g acl, superfreeswan, USAGI etc).
greets
Marc
--
gentoo-alpha@gentoo.org mailing list
next prev parent reply other threads:[~2004-02-25 19:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 18:25 [gentoo-alpha] vanilla-sources vs alpha-sources jwsacksteder
2004-02-25 18:30 ` Jay Maynard
2004-02-25 19:02 ` Aron Griffis
2004-02-25 19:07 ` Marc Giger [this message]
2004-02-25 19:36 ` Aron Griffis
2004-02-25 20:13 ` Marc Giger
2004-02-25 20:22 ` Aron Griffis
2004-02-25 20:47 ` Marc Giger
2004-02-25 19:01 ` Aron Griffis
-- strict thread matches above, loose matches on Subject: below --
2004-02-25 20:03 Donsbach, Jeff
2004-02-25 20:34 ` Marc Giger
2004-02-25 21:01 Donsbach, Jeff
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=20040225200718.03799597.gigerstyle@gmx.ch \
--to=gigerstyle@gmx.ch \
--cc=gentoo-alpha@lists.gentoo.org \
--cc=jmaynard@conmicro.cx \
--cc=jwsacksteder@ramprecision.com \
/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