From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick Mansfield Date: Tue, 24 Feb 2004 01:23:48 +0000 Subject: Re: Udev and SCSI/Fiber channel devices Message-Id: <20040223172348.A15243@beaverton.ibm.com> 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 Mon, Feb 23, 2004 at 03:43:13PM -0800, Sabharwal, Atul wrote: > Greg, > > Besides USB, can udev be used for persistent names for SCSI and fiber > channel devices ? Do the drivers need to be > > loaded as modules ? Does udev handle boot time events for devices ? Are > these available with the latest v0.18 ? Atul - 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. linux scsi can be all modular (drivers and scsi core), but then of course you need an initrd to boot from your scsi disks. scsi_id uses scsi vpd page 0x80 or 0x83 to get a unique id, and then that id can be used to give a peristent name to your scsi device. You have to edit the /etc/scsi_id.config or run it with '-g' to get anything useful out of it. If you have any questions about it, let me know. FYI I just fixed a bad bug with with it not handling disk partitions at all, and will post a new version RSN. -- Patrick Mansfield ------------------------------------------------------- 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