Re: Problems using scsi_id with udevstart

[Andrew Patterson <andrew.patterson@hp.com>]

[-- Attachment #1: Type: text/plain, Size: 2165 bytes --]

On Wed, 2004-10-06 at 09:59 -0700, Patrick Mansfield wrote:
> On Wed, Oct 06, 2004 at 10:26:13AM -0600, Andrew Patterson wrote:
> 
> > Note: here is the error you get when scsi_id is run without any
> > parameters:
> > 
> > # /sbin/scsi_id
> > -s must be specified
> 
> For the udev PROGRAM rules with no arguments, it is effectively invoked
> like this (well there are other environment values but scsi_id only cares
> about DEVPATH):
> 
> DEVPATH=/block/sda /sbin/scsi_id block
> 

This is what I thought was supposed to happen.  I printed out the
arguments and the environment when scsi_id was invoked through
udevstart.  No arguments were passed and UDEVPATH was always set
to /class/net/lo for every path in /sys.  Note that DEVNAME does seem to
be set correctly.

Example:

DEVNAME=/dev/sda
DEVPATH=/class/net/lo

> Since udev does not have a % whatever for the DEVPATH, you can't pass it
> in the rule file, that is this rule would not work for anything but sda:
> 
> 	PROGRAM="/sbin/scsi_id -s /block/sda"
> 
> You would need a new udev %-something, like:
> 
> 	PROGRAM="/sbin/scsi_id -s %p"

Yeah, I was hoping for something like the %p.  Seems like it would be
nice to have one in any case.  However, I think udevstart should just
work like using plain /sbin/scsi_id.  That way, you don't have to have a
separate rules for udev and udevstart (if this is even possible).

I am still not sure if I am running into a bug, or that I just don't
understand how udevstart is supposed to work.  My goal is to be able to
just plug in arbitrary SCSI devices and not have to worry about human-
readable device files being created.  From the sample scripts I have
seen, the current method is to plug in your device, then run some script
(like gen_scsi_id_udev_rules.sh that comes with scsi_id) that generates
udev rules for you, which you must then hand add to the udev rulesets.
If udevstart worked like I hoped it would, you could just
edit /etc/scsi_id.conf to account for bad devices that need special
handling.

Andrew

> 
> -- Patrick Mansfield
> 
-- 
Andrew Patterson                
Hewlett-Packard

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]