From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Tue, 24 Feb 2004 02:22:14 +0000 Subject: RE: Udev and SCSI/Fiber channel devices Message-Id: <1077589333.23341.28.camel@pim> List-Id: References: <2F75A5CCEF1E6A4C8CA2E75CF7F529E901F260D7@orsmsx409.jf.intel.com> In-Reply-To: <2F75A5CCEF1E6A4C8CA2E75CF7F529E901F260D7@orsmsx409.jf.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Tue, 2004-02-24 at 03:09, Sabharwal, Atul wrote: > You can use scsi_id in a callout rule with udev for scsi persistent > names. > scsi_id is released along with udev under extras/scsi_id. > >> I tried a callout rule as follows : > > CALLOUT="/sbin/scsid -p 0x80 -s /block/sda| awk ' {}; end { print$3 }'", BUS="scsi", ID="325687809", NAME="host_scsi" Huh, do we really need this complex callout argument line. We are not prepared for something like this, cause we pass only 7 arguments down to the program. If it's really needed, I can have look. Pat? thanks, Kay ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56&alloc_id438&op=click _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel