From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andi Kleen <andi@firstfloor.org>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
jeff@garzik.org
Subject: Re: Libata PATA status
Date: Wed, 4 Jul 2007 14:18:19 +0100 [thread overview]
Message-ID: <20070704141819.01a357fa@the-village.bc.nu> (raw)
In-Reply-To: <20070704130258.GA10904@one.firstfloor.org>
> > > disabled without risking breaking old root file systems.
> >
> > That would be udevd for new systems or "ln -s" for old ones ?
>
> Then old kernels couldn't be booted anymore.
Why not. I boot back and forth randomly between old and new IDE kernels
without problems. The root fs loaded is set in kernel or grub (or on most
distros nowdays by label scanning from initrd) so just works. Then mount
label or uuid based mounting does the rest.
> Sure for SATA. But surely for PATA it would be possible to fake
> the mapping of the old driver? Doing it simple minded (e.g. only
> for the builtin devices) would be probably sufficient.
You could probably reliably map "hda/b/c/d" initially with some kind of
forwarder providing nobody hot plugged them. Just not sure I see the
point of doing it kernel side.
Alan
next prev parent reply other threads:[~2007-07-04 13:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 17:51 Alan Cox
2007-07-04 3:04 ` Kyle Moffett
2007-07-04 9:21 ` Alan Cox
2007-07-04 11:31 ` Marc Dietrich
2007-07-04 12:10 ` Alan Cox
2007-07-04 14:18 ` Marc Dietrich
[not found] ` <20070705183355.187e96bc@the-village.bc.nu>
2007-07-06 8:58 ` Marc Dietrich
2007-07-04 13:00 ` Andi Kleen
2007-07-04 12:17 ` Alan Cox
2007-07-04 13:02 ` Andi Kleen
2007-07-04 13:18 ` Alan Cox [this message]
2007-07-04 13:29 ` Andi Kleen
2007-07-04 14:23 ` Alan Cox
2007-07-04 12:19 ` Alan Cox
2007-07-05 23:25 ` Jeff Garzik
2007-07-05 22:27 ` Rod Whitby
2007-07-06 9:48 ` Libata PATA status (pata_artop) Michael-Luke Jones
2007-07-04 9:17 Libata PATA status Mikael Pettersson
2007-07-05 8:18 Chris Rankin
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=20070704141819.01a357fa@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=andi@firstfloor.org \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®