Re: [PATCH] minimal SAS transport class

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

 



On 08/24/05 13:12, Patrick Mansfield wrote:
> On Tue, Aug 23, 2005 at 07:55:37PM -0400, Luben Tuikov wrote:
> 
>>Where does udev get its label?
> 
> 
> You can call any script or program from udev and use the result. There are

And where does _it_ get it?

> recent changes for persistent naming, the /dev/by-id naming used in sles9
> is in current udev.
> 
> A tmp /dev node is available to called out programs, so any pass through
> or regular IO can be sent to the device before it has its real name.  So
> you should be able to get anything available on the scsi device that way.

*"SCSI DEVICE"*, not SAS of FC or iSCSI or whatever.
Now, where will that *scsi device* get _its_ label?

> udev now has an "IMPORT" rule, see usage of scsi_id, vol_id, etc. in
> current udev rules.
> 
> Followup posts should go to linux-hotplug-devel@xxxxxxxxxxxxxxxxxxxxx

Hey Patrick, is there a point to this thread?
If you have an idea, please go ahead and share and/or implement it.
If you're unclear on something please ask it directly.

	Luben
-
: 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