linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Kevin Hendricks <khendricks@ivey.uwo.ca>
Cc: linuxppc-dev@lists.linuxppc.org,
	yellowdog-devel@lists.terrasoftsolutions.com
Subject: Re: Status of 2.5.X kernels on PPC Linux, anyone working with NPTL?
Date: Wed, 9 Oct 2002 19:26:26 -0700	[thread overview]
Message-ID: <20021010022626.GB1967@opus.bloom.county> (raw)
In-Reply-To: <8B16CEB0-DB99-11D6-BCE2-0030654D6A26@ivey.uwo.ca>


On Wed, Oct 09, 2002 at 11:12:36AM -0400, Kevin Hendricks wrote:

> Hi,
>
> Can anyone bring me up to date on the buildability and useability of the
> latest 2.5.X kernels on PPC Linux?  How stable and useful are these
> given the recent changes to revert back to 2.4 IDE code and other
> changes?

Depending on the time and day of course, the linuxppc-2.5 tree is
generally left in a buildable state, at least for some target or
another.  IMHO, it is still easiest to NFS root a 2.5 box than to worry
about IDE / SCSI being perfectly sane.  That said, IDE / SCSI have been
rather sane for a while now, so the chances are low of you kicking
yourself for not having done a backup recently..

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2002-10-10  2:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-09 15:12 Status of 2.5.X kernels on PPC Linux, anyone working with NPTL? Kevin Hendricks
2002-10-09 16:34 ` David Edelsohn
2002-10-09 17:14   ` Kevin Hendricks
2002-11-03 18:28   ` Aldy Hernandez
2002-11-03 18:45     ` Kevin B. Hendricks
2002-11-03 18:55       ` Aldy Hernandez
2002-11-03 20:06         ` Kevin B. Hendricks
2002-10-10  2:26 ` Tom Rini [this message]
2002-10-27 12:30 ` Giuliano Pochini

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=20021010022626.GB1967@opus.bloom.county \
    --to=trini@kernel.crashing.org \
    --cc=khendricks@ivey.uwo.ca \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=yellowdog-devel@lists.terrasoftsolutions.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;
as well as URLs for NNTP newsgroup(s).