From: Patrick Mansfield <patmans@us.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: adding callouts to udev for scsi identifiers/serial numbers
Date: Wed, 15 Oct 2003 00:31:02 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106617796007651@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106565105203794@msgid-missing>
On Tue, Oct 14, 2003 at 03:40:54PM -0700, Greg KH wrote:
> Any pointer to where this program is located at?
Not yet, I'm presently having password problems to an external web page.
> > In order to call out and cache one time, I was thinking of adding
> > namedev.config syntax like:
> >
> > SET=somevar1, BUS="scsi", PROGRAM="/usr/sbin/scsi_id"
> >
> > USE=somevar1, BUS="scsi", ID="200609487340b71da", NAME="disk-1"
> > USE=somevar1, BUS="scsi", ID="somenumber", NAME="disk-2"
> >
> > Any comments or suggestions on the above?
>
> Caching is good. And yes, something like the above is needed. Hm, but
> how can we pass command line arguments to the program to be run?
I have a scsi_id.config file that can be used to set global and per SCSI
vendor + product specific options, but arguments could also be passed via
the PROGRAM string.
-- Patrick Mansfield
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
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:[~2003-10-15 0:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 22:06 adding callouts to udev for scsi identifiers/serial numbers Patrick Mansfield
2003-10-14 22:40 ` Greg KH
2003-10-15 0:31 ` Patrick Mansfield [this message]
2003-10-15 18:27 ` Greg KH
2003-10-15 19:48 ` Patrick Mansfield
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-106617796007651@msgid-missing \
--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 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.