From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Wed, 02 Jul 2008 16:06:37 +0000 Subject: Re: not all volume types export UUIDs (was: /dev/disk/by-id Message-Id: <1215014797.9721.41.camel@linux.site> List-Id: References: <20080702102820.GB16076@piper.oerlikon.madduck.net> In-Reply-To: <20080702102820.GB16076@piper.oerlikon.madduck.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Wed, 2008-07-02 at 17:49 +0200, martin f krafft wrote: > also sprach Kay Sievers [2008.07.02.1619 +0200]: > > What kind of id's do you have in mind, which would be the same across > > buses? > > I don't. I am trying to understand why the bus type is an integral > part of the /dev/disk/by-id/* links. Because it's the USB-serial-number, the ATA-serial-string, the SCSI-INQUIRY-serial-string, the FireWire-gid-number, the dm-name-string, the md-name-string, the SD-flash-card serial, ..., and not a unique id on its own. All are only unique per namespace/bus, and should better not be mixed. The exception which would allow us moving the number around is ATA devices using SCSI, because ATA synthesizes all SCSI data, but I think we better just create two links in this case, instead of trying to move all different id's into one namespace. Thanks, Kay