From: Gary_Lerhaupt@Dell.com
To: linux-hotplug@vger.kernel.org
Subject: partition unique identifiers
Date: Mon, 14 Oct 2002 15:52:43 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-103461080604378@msgid-missing> (raw)
I just discovered that via the Intel Extensible Firmware Interface
Specification, there are allowances for partition specific unique
identifiers. Such a thing would be quite handy within devlabel and I was
wondering if anybody knew of any user space programs which currently capture
these identifiers? Something like my scsi_unique_id but for partitions.
Not only would this allow for the unique identification of MegaRAID
partitions (which currently do not produced IDs), but it would also allow
devlabel to handle inter-disk renaming events. So, in the event that
/dev/sda6 was deleted and /dev/sda7 became /dev/sda6, the symlink pointing
to /dev/sda7 could be rerouted to its new location.
Let me know if you have any insight. Assuming this code doesn't currently
exist somewhere, I will be writing it myself. I've also made some bugfixes
to devlabel and the latest rev will always be available at
www.domsch.com/linux/devlabel.
Also, I'm looking to get some more concrete feedback on whether my simple
hotplug patches will make their way into those scripts ( if [ -x
/sbin/devlabel]; then /sbin/devlabel restart).
Gary Lerhaupt
Linux Development
Dell Computer Corporation
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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 reply other threads:[~2002-10-14 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 15:52 Gary_Lerhaupt [this message]
2002-10-14 17:15 ` partition unique identifiers 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=marc-linux-hotplug-103461080604378@msgid-missing \
--to=gary_lerhaupt@dell.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).