Re: [PATCH] minimal SAS transport class

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 08/22/05 17:53, Mike Anderson wrote:
> Luben Tuikov <luben_tuikov@xxxxxxxxxxx> wrote:
> 
>>Yes, that's cool.
>>
>>How about specifying the LU label _and_ the FS label to "root="?
>>
>>root=[<disk label>:]<fs label>
>>
>><disc label> :=
>>	WWN,
>>	HCIL,
>>	Funky name 1,
>>	Funky name 2.
>>
>><fs label> :=
>>	filesystem specific label.
>>	
>>All those labels are tacked onto the LU, and are provided by
>>various layers: transport, LLDD, vendor, manufacturer, etc, etc, etc.
>>
> 
> 
> What is the difference between this disk label and what you can do with a
> udev rules file today?

Where does udev get its label?

	Luben

> On SUSE today you can boot a system using a udev
> created name "root=/dev/disk/by-id/351234560000007d0" which is one example
> of using the udev rules "PROGRAM" call to generate a name. You should be
> able to cover all your examples with a call-out program knowledgeable of
> where to find this disk label information and create a device node for
> them.
> 
> -andmike
> --
> Michael Anderson
> andmike@xxxxxxxxxx
> 

-
: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux