From: Andi Kleen <andi@firstfloor.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
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 15:29:30 +0200 [thread overview]
Message-ID: <20070704132930.GB10904@one.firstfloor.org> (raw)
In-Reply-To: <20070704141819.01a357fa@the-village.bc.nu>
> 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
PATA hotplug?
SATA systems typically already use /dev/sda*, it just applies to PATA.
> point of doing it kernel side.
The point would be that old user land just works without any changes.
I know that is a virtue that has gone out of fashion recently
with udev and sysfs, but older distributions that weren't
that sysfs-layout-of-the-week dependent used to be fairly kernel version
independent. I always found that very useful.
The hda->sda move would be the only "radical" change that prevents booting for
a long time (the last one before that was the 2.5 modutils transition)
-Andi
next prev parent reply other threads:[~2007-07-04 13:29 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
2007-07-04 13:29 ` Andi Kleen [this message]
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=20070704132930.GB10904@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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®