From: Patrick Mansfield <patmans@us.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Udev and SCSI/Fiber channel devices
Date: Tue, 24 Feb 2004 01:23:48 +0000 [thread overview]
Message-ID: <20040223172348.A15243@beaverton.ibm.com> (raw)
In-Reply-To: <2F75A5CCEF1E6A4C8CA2E75CF7F529E901F260D7@orsmsx409.jf.intel.com>
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_id\x1356&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
next prev parent reply other threads:[~2004-02-24 1:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 23:43 Udev and SCSI/Fiber channel devices Sabharwal, Atul
2004-02-24 1:19 ` Greg KH
2004-02-24 1:23 ` Patrick Mansfield [this message]
2004-02-24 1:33 ` Sabharwal, Atul
2004-02-24 2:06 ` Greg KH
2004-02-24 2:09 ` Sabharwal, Atul
2004-02-24 2:22 ` Kay Sievers
2004-02-24 4:58 ` Patrick Mansfield
2004-02-24 11:22 ` Kay Sievers
2004-02-24 17:03 ` Sabharwal, Atul
2004-02-24 17:32 ` Patrick Mansfield
2004-02-24 18:03 ` Sabharwal, Atul
2004-02-24 18:11 ` Sabharwal, Atul
2004-02-24 18:16 ` Kay Sievers
2004-02-24 18:19 ` Greg KH
2004-02-24 18:20 ` Sabharwal, Atul
2004-02-24 18:24 ` Sabharwal, Atul
2004-02-24 18:31 ` Patrick Mansfield
2004-02-24 18:40 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040223172348.A15243@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).