[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4716452F.4080408@s5r6.in-berlin.de>
Date: Wed, 17 Oct 2007 19:23:59 +0200
From: Stefan Richter <stefanr@...6.in-berlin.de>
To: Gabor Gombas <gombasg@...aki.hu>
CC: david@...g.hm, Matthew Wilcox <matthew@....cx>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Rob Landley <rob@...dley.net>,
David Newall <david@...idnewall.com>,
linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
Suparna Bhattacharya <suparna@...ibm.com>,
Nick Piggin <piggin@...erone.com.au>
Subject: Re: What still uses the block layer?
Gabor Gombas wrote:
> On Tue, Oct 16, 2007 at 01:55:07PM -0700, david@...g.hm wrote:
>> why is this any different from the external enclosures? they have always
>> appeared as the type of device that connects them to the motherboard, (and
>> even with SCSI, there are some controllers that don't generate sdX devices)
>
> In the past enclosures supported only one kind of connector so this
> assumption was fine. But nowadays an external disk may have several
> connectors (like USB, Firewire and eSata). Why should the disk's name
> depend on what type of cable did I manage to grab first? It is the
> _same_ disk regardless of the cable type.
Yes, but even udev won't give you one and the same symlink to the disk's
device file then.¹ There isn't a persistent unique target/unit property
which all of these transports have in common.
The only thing that could be common in the best case is the symlink to
the partition's device file, based on filesystem UUID or filesystem label.
¹) unless you write your own rule specific to this on particular enclosure
--
Stefan Richter
-=====-=-=== =-=- =---=
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists