From: sullivan <sullivan@austin.ibm.com>
To: linux-scsi@vger.kernel.org
Cc: mochel@osdl.org
Subject: [RFC] Persistent naming of scsi devices
Date: Wed, 5 Jun 2002 15:13:36 -0500 [thread overview]
Message-ID: <20020605151336.A1139@austin.ibm.com> (raw)
Thanks for your postings to the original RFC submitted under this subject. Based on your feedback two utilities are now available at http://oss.software.ibm.com/devreg/
a. scsiname utility
- Makes sg calls to collect device info used to make naming decisions
- Hooked into the hotplug interface using Doug Gilbert's scsimon patch
- Targeted specifically to scsi devices
- Implemented completely in userspace
b. devnaming utility
- Utilizes Patrick Mochel's driverfs fs to collect device info
- Can easily be extended to support other device types (non scsi)
- Includes a kernel patch to create/publish device info in driverfs
- Hooked into hotplug interface using scsimon patch
Why two utilities? I see scsiname providing an immediate fix for providing a persistent set of /dev scsi names across boots. The devnaming utility is more long term in that it anticipates that driverfs will evolve into providing the device information necessary, removing the need for interfacing through sg. The config and hotplug portions of the utilities are consistent and should (hopefully) provide a smooth migration path.
I'd appreciate feedback from anyone that has the interest and the time to take a further look.
next reply other threads:[~2002-06-05 20:13 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-05 20:13 sullivan [this message]
2002-06-06 1:08 ` [RFC] Persistent naming of scsi devices Douglas Gilbert
-- strict thread matches above, loose matches on Subject: below --
2002-04-12 18:03 berthiaume_wayne
2002-04-12 17:18 Bryan Henderson
2002-04-12 13:15 berthiaume_wayne
2002-04-11 16:01 Bryan Henderson
2002-04-10 20:24 berthiaume_wayne
2002-04-10 19:02 Martin Peschke3
2002-04-10 16:44 berthiaume_wayne
2002-04-10 15:52 Martin Peschke3
2002-04-10 19:33 ` Matthew Jacob
2002-04-10 15:28 Bryan Henderson
2002-04-10 14:36 berthiaume_wayne
2002-04-10 16:02 ` Matthew Jacob
2002-04-10 14:28 berthiaume_wayne
2002-04-10 1:40 Bryan Henderson
2002-04-08 22:05 Martin Peschke3
2002-04-08 22:17 ` Matthew Jacob
2002-04-08 19:18 Martin Peschke3
2002-04-08 20:45 ` Matthew Jacob
2002-04-10 1:16 ` Rick Stevens
2002-04-10 2:01 ` Matthew Jacob
2002-04-10 2:17 ` Linus Torvalds
2002-04-10 3:37 ` Martin K. Petersen
2002-04-10 13:19 ` Theodore Tso
2002-04-10 14:04 ` Eddie Williams
2002-04-10 17:45 ` Mike Anderson
2002-04-08 16:11 Matt_Domsch
2002-04-08 15:18 sullivan
2002-04-08 15:04 ` Christoph Hellwig
2002-04-08 15:59 ` Matthew Jacob
2002-04-08 16:34 ` James Bottomley
2002-04-08 18:27 ` Patrick Mansfield
2002-04-08 19:17 ` James Bottomley
2002-04-09 0:22 ` Douglas Gilbert
2002-04-09 14:35 ` sullivan
2002-04-09 14:55 ` sullivan
2002-04-08 17:51 ` Oliver Neukum
2002-04-08 18:01 ` Christoph Hellwig
2002-04-08 18:18 ` Matthew Jacob
2002-04-08 18:28 ` James Bottomley
2002-04-08 18:34 ` Matthew Jacob
2002-04-08 19:07 ` James Bottomley
2002-04-08 20:41 ` Matthew Jacob
2002-04-08 18:45 ` Tigran Aivazian
2002-04-08 20:18 ` Eddie Williams
2002-04-09 0:48 ` Kurt Garloff
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=20020605151336.A1139@austin.ibm.com \
--to=sullivan@austin.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mochel@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.