[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071017094838.GB18035@boogie.lpds.sztaki.hu>
Date: Wed, 17 Oct 2007 11:48:39 +0200
From: Gabor Gombas <gombasg@...aki.hu>
To: david@...g.hm
Cc: Matthew Wilcox <matthew@....cx>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Stefan Richter <stefanr@...6.in-berlin.de>,
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?
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.
There is one thing however that could be improved: renaming a disk in an
udev rule should propagate the new name back to the kernel, just like
renaming an ethernet interface does. That way mapping error messages to
physical disk locations could be made much easier.
Gabor
--
---------------------------------------------------------
MTA SZTAKI Computer and Automation Research Institute
Hungarian Academy of Sciences
---------------------------------------------------------
-
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