From: Jeff Donsbach <jeff_donsbach@yahoo.com>
To: gentoo-alpha@lists.gentoo.org
Subject: Re: [gentoo-alpha] 2.4 -> 2.6
Date: Wed, 7 Dec 2005 14:31:36 -0800 (PST) [thread overview]
Message-ID: <20051207223136.42196.qmail@web32902.mail.mud.yahoo.com> (raw)
In-Reply-To: <43923672.7010308@jdfiles.org>
What kind of machine do you have? In general, I
believe "vanilla-sources" are the recommended portage
tree for Alpha.
Jeff D
--- Jeff Sacksteder <jeff@jdfiles.org> wrote:
> I'll be transitioning from 2.4 to 2.6 shortly. I do
> this with great
> trepidation. Are there any pitfalls to be aware of
> other than the devfs
> -> udev change?
>
> Should update the kernel or my toolchain first?
>
> Which source tree is safe-n-stable for SMP Alpha?
__________________________________________
Yahoo! DSL Something to write home about.
Just $16.99/mo. or less.
dsl.yahoo.com
--
gentoo-alpha@gentoo.org mailing list
prev parent reply other threads:[~2005-12-07 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-04 0:21 [gentoo-alpha] 2.4 -> 2.6 Jeff Sacksteder
2005-12-04 19:10 ` Davide Cittaro
2005-12-07 22:31 ` Jeff Donsbach [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=20051207223136.42196.qmail@web32902.mail.mud.yahoo.com \
--to=jeff_donsbach@yahoo.com \
--cc=gentoo-alpha@lists.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