Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934965AbXJQRZf (ORCPT ); Wed, 17 Oct 2007 13:25:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760340AbXJQRZX (ORCPT ); Wed, 17 Oct 2007 13:25:23 -0400 Received: from einhorn.in-berlin.de ([192.109.42.8]:57184 "EHLO einhorn.in-berlin.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760147AbXJQRZW (ORCPT ); Wed, 17 Oct 2007 13:25:22 -0400 X-Envelope-From: stefanr@s5r6.in-berlin.de Message-ID: <4716452F.4080408@s5r6.in-berlin.de> Date: Wed, 17 Oct 2007 19:23:59 +0200 From: Stefan Richter User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.6) Gecko/20070807 SeaMonkey/1.1.4 MIME-Version: 1.0 To: Gabor Gombas CC: david@lang.hm, Matthew Wilcox , Alan Cox , Rob Landley , David Newall , linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org, Suparna Bhattacharya , Nick Piggin Subject: Re: What still uses the block layer? References: <200710141836.55211.rob@landley.net> <4712FE33.3000400@s5r6.in-berlin.de> <200710150426.04924.rob@landley.net> <20071015160800.GA324@parisc-linux.org> <47139F15.7050702@s5r6.in-berlin.de> <20071016111911.30a18e12@the-village.bc.nu> <20071016195432.GA31306@parisc-linux.org> <20071017094838.GB18035@boogie.lpds.sztaki.hu> In-Reply-To: <20071017094838.GB18035@boogie.lpds.sztaki.hu> X-Enigmail-Version: 0.95.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1374 Lines: 29 Gabor Gombas wrote: > On Tue, Oct 16, 2007 at 01:55:07PM -0700, david@lang.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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/