From: Jeff Garzik <jeff@garzik.org>
To: Mark Lord <liml@rtr.ca>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Merging libata PATA support into the base kernel
Date: Thu, 10 Aug 2006 02:13:51 -0400 [thread overview]
Message-ID: <44DACE9F.3090909@garzik.org> (raw)
In-Reply-To: <44DA4288.6020806@rtr.ca>
Mark Lord wrote:
> This will also allow time for things like "udev" to perhaps think about
> an option to someday provide /dev/hd* symlinks for PATA devices when
> libata is used instead of IDE (?). That might be a possible migration
> path in the far future.
Unfortunately a symlink won't work because of compatibility issues.
/dev/hd supports more partitions, and a different set of ioctls.
Jeff
next prev parent reply other threads:[~2006-08-10 6:13 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 17:29 Merging libata PATA support into the base kernel Alan Cox
2006-08-09 20:16 ` Mark Lord
2006-08-10 6:13 ` Jeff Garzik [this message]
2006-08-10 6:20 ` Jan Engelhardt
2006-08-10 6:25 ` Olaf Hering
2006-08-11 15:47 ` Mark Lord
2006-08-15 13:31 ` Matthieu CASTET
2006-08-15 13:35 ` Tejun Heo
2006-08-15 14:01 ` Jeff Garzik
2006-08-09 21:21 ` /dev/sd* Adrian Bunk
2006-08-09 21:40 ` /dev/sd* Mark Lord
2006-08-09 22:01 ` /dev/sd* Alan Cox
2006-08-09 22:18 ` /dev/sd* Adrian Bunk
2006-08-10 1:44 ` /dev/sd* Alan Cox
2006-08-10 6:19 ` /dev/sd* Jan Engelhardt
2006-08-10 4:46 ` /dev/sd* Greg KH
2006-08-10 12:36 ` /dev/sd* Gabor Gombas
2006-08-10 12:37 ` /dev/sd* Jeff Garzik
2006-08-17 3:17 ` /dev/sd* Lee Trager
2006-08-17 7:58 ` /dev/sd* Michael Tokarev
2006-08-17 8:10 ` /dev/sd* Jan Engelhardt
2006-08-17 8:42 ` /dev/sd* Alan Cox
2006-08-17 8:01 ` /dev/sd* Jan Engelhardt
2006-08-17 8:29 ` /dev/sd* Lee Trager
2006-08-17 9:21 ` /dev/sd* Jan Engelhardt
2006-08-18 7:11 ` /dev/sd* Seewer Philippe
2006-08-18 8:52 ` /dev/sd* Jan Engelhardt
2006-08-18 9:19 ` /dev/sd* Tejun Heo
2006-08-18 14:57 ` /dev/sd* Alan Cox
2006-08-18 15:51 ` /dev/sd* Jan Engelhardt
2006-08-18 16:47 ` /dev/sd* Lee Revell
2006-08-18 17:02 ` /dev/sd* Alan Cox
2006-08-21 6:04 ` /dev/sd* Lee Trager
2006-08-21 6:17 ` /dev/sd* Jan Engelhardt
2006-08-18 12:45 ` /dev/sd* Bill Davidsen
2006-08-18 15:48 ` /dev/sd* Jan Engelhardt
2006-08-19 0:15 ` /dev/sd* Gabor Gombas
2006-08-17 8:45 ` /dev/sd* Alan Cox
2006-08-10 6:24 ` Merging libata PATA support into the base kernel Andi Kleen
2006-08-10 12:37 ` Alan Cox
2006-08-10 12:20 ` Jens Axboe
2006-08-10 14:14 ` Alan Cox
2006-08-10 13:59 ` Jens Axboe
2006-08-10 15:54 ` Alan Cox
2006-08-10 19:02 ` Jason Lunz
2006-08-10 19:40 ` Rafael J. Wysocki
2006-08-17 3:26 ` Lee Trager
2006-08-17 9:18 ` Pavel Machek
2006-08-17 9:52 ` Alan Cox
2006-08-17 9:45 ` Pavel Machek
2006-08-17 11:51 ` Alan Cox
2006-08-18 3:38 ` Lee Trager
2006-08-18 3:57 ` Lee Trager
2006-08-18 16:01 ` Alan Cox
2006-08-18 19:22 ` Lee Trager
2006-08-18 20:50 ` Alan Cox
2006-08-19 8:17 ` Lee Trager
2006-08-21 0:44 ` Lee Trager
2006-08-10 19:47 ` Jens Axboe
2006-08-10 19:54 ` Rafael J. Wysocki
2006-08-11 15:48 ` Mark Lord
2006-08-10 22:27 ` Krzysztof Halasa
2006-08-24 3:31 ` Albert Lee
2006-08-24 3:38 ` Jeff Garzik
2006-08-24 4:13 ` Doug Maxey
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=44DACE9F.3090909@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=liml@rtr.ca \
--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;
as well as URLs for NNTP newsgroup(s).