From: Mark Bellon <mbellon@mvista.com>
To: linux-scsi@vger.kernel.org
Subject: ANNOUNCE: User-space System Device Enumation (uSDE)
Date: Mon, 27 Oct 2003 13:40:29 -0700 [thread overview]
Message-ID: <3F9D82BD.4080609@mvista.com> (raw)
Initial availability of User-Space System Device Enumeration (uSDE)
package, version 0.74, can be found at http://sourceforge.net/projects/usde
The uSDE provides an open framework for the enumeration (specification)
of system devices in a dynamic environment. Device handling is
implemented via plug-in programs known as policy methods. Policy methods
are free to handle their devices in any way, from trivial to complex -
anything from providing LSB device nodes to persistent device name
handling with
replacement and relocation strategies.
The uSDE depends on /sbin/hotplug (for dynamic insertions and removals),
sysfs (for device information) and /proc (various pieces of
information). It is not dependent on initrd - it explicitly scans sysfs
upon system startup to determine the initial device ensemble.
Part of the uSDE release is a collection of sample polices:
disk-ide-policy - handles IDE, EIDE, SATA and USB-EIDE disks. Implements
persistent device naming, automatic device replacement and automatic
device relocation features.
disk-scsi-policy - handles SCSI, IEEE-1394, FibreChannel and USB-SCSI
disks including multiported devices. Iplements persistent device naming,
automatic device replacement and automatic device relocation features.
multipath-policy - handles the automatic provisioning of multipathing
for multiported storage devices.
ethernet-policy - handles ethernet interefaces. Implements persistent
interface naming, interface anchoring, automatic device replacement and
automatic device relocation features.
floppy-policy - handles internal floppy disks.
simple-device-policy - a "catch all" policy for block and character devices.
devfs-policy - provides devfs device names.
lsb-policy - provides LSB device names.
Location: http://sourceforge.net/projects/usde
Mailing list: usde-general@lists.sourceforge.net
mark
next reply other threads:[~2003-10-27 20:40 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 20:40 Mark Bellon [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-27 20:41 ANNOUNCE: User-space System Device Enumation (uSDE) Mark Bellon
2003-10-27 21:00 ` Lars Marowsky-Bree
2003-10-27 21:14 ` Mark Bellon
2003-10-28 11:00 ` Lars Marowsky-Bree
2003-10-28 11:00 ` Lars Marowsky-Bree
2003-10-28 18:12 ` Steven Dake
2003-10-28 18:12 ` Steven Dake
2003-10-28 22:44 ` Greg KH
2003-10-29 14:30 ` Andreas Jellinghaus
2003-10-29 17:20 ` Daniel Stekloff
2003-11-02 17:28 ` Andreas Jellinghaus
2003-11-03 23:29 ` Daniel Stekloff
2003-10-29 19:18 ` Greg KH
2003-10-29 22:12 ` Andreas Jellinghaus
2003-10-29 22:43 ` Greg KH
2003-10-27 23:15 ` Steven Dake
2003-10-27 23:19 ` Mark Bellon
2003-10-28 22:44 Greg KH
2003-10-29 5:12 ` Guo, Min
2003-10-29 7:41 ` wwp
2003-10-29 16:10 ` Steven Dake
2003-10-29 19:04 ` Greg KH
2003-10-29 19:05 ` Greg KH
2003-10-30 16:09 ` A. Craig West
2003-10-31 0:45 ` David Dodge
2003-10-31 0:58 ` Greg KH
2003-10-31 2:29 ` Dave Dodge
2003-10-29 5:12 Guo, Min
2003-10-29 5:12 ` Guo, Min
2003-10-29 16:10 ` Steven Dake
2003-10-29 16:10 ` Steven Dake
2003-10-29 19:04 ` Greg KH
2003-10-31 0:45 David Dodge
2003-10-31 0:58 ` Greg KH
2003-10-31 0:58 ` Greg KH
2003-10-31 2:29 ` Dave Dodge
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=3F9D82BD.4080609@mvista.com \
--to=mbellon@mvista.com \
--cc=linux-scsi@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 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.