From: Patrick Mansfield <patmans@us.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Patch to multipath-tools 0.2.4
Date: Fri, 09 Jul 2004 15:32:10 +0000 [thread overview]
Message-ID: <20040709153210.GA27948@beaverton.ibm.com> (raw)
In-Reply-To: <40E92177.7000800@suse.de>
On Mon, Jul 05, 2004 at 11:37:59AM +0200, Hannes Reinecke wrote:
> We should actually be using the scsi_id package directly as this would
> give us identical mappings for udev and multipath tools. But as this
> would mean a major restructuring of the program itself I took the cheap
> way out. Patrick, can you think of a clever way of integrating both?
Christophe -
How about a callout line, similiar to that in udev, so any program can be
specified to get the id of the device?
Does this still need to work with 2.4? If so, the current get_evpd_wwid
can be left in place.
The corresponding config file syntax could be:
getuid_function exec /sbin/scsi_id
-- Patrick Mansfield
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
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-07-09 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 9:37 Patch to multipath-tools 0.2.4 Hannes Reinecke
2004-07-05 12:11 ` christophe.varoqui
2004-07-09 15:32 ` Patrick Mansfield [this message]
2004-07-09 15:50 ` christophe varoqui
2004-07-09 16:00 ` Patrick Mansfield
2004-07-12 21:46 ` christophe varoqui
2004-07-13 0:26 ` Patrick Mansfield
2004-07-13 8:17 ` christophe.varoqui
2004-07-13 16:57 ` Patrick Mansfield
2004-07-14 9:49 ` christophe varoqui
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=20040709153210.GA27948@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).