From: Hannes Reinecke <hare@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: NAA identifiers with scsi_id
Date: Tue, 15 Jun 2004 14:39:37 +0000 [thread overview]
Message-ID: <40CF0A29.2010308@suse.de> (raw)
Hi all,
having checked scsi_id, I found out that it will always prefer NAA ids
in favour of any other types (EUI-64 et.al.).
This is not very helpful if scsi_id is used to generate meaningful
persistent driver ids, as the user might want to check the links created
by udev against the device list presented by the system (e.g. via
'dmesg' or 'cat /proc/scsi/scsi' or even by scanning sysfs).
Can't we just ignore NAA ids and fall back to page 0x80 + inquiry if
these are all we will get via page 0x83? Just having an arbitrary number
is not very helpful and totally intransparent to the user.
Cheers,
Hannes
--
Dr. Hannes Reinecke hare@suse.de
SuSE Linux AG S390 & zSeries
Maxfeldstraße 5 +49 911 74053 688
90409 Nürnberg http://www.suse.de
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
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:[~2004-06-15 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 14:39 Hannes Reinecke [this message]
2004-06-15 21:54 ` NAA identifiers with scsi_id Patrick Mansfield
2004-06-16 4:59 ` Douglas Gilbert
2004-06-16 16:49 ` Bryan Henderson
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=40CF0A29.2010308@suse.de \
--to=hare@suse.de \
--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).