All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: patches from the debian package
Date: Tue, 08 Feb 2005 21:32:58 +0000	[thread overview]
Message-ID: <20050208213258.GA1883@us.ibm.com> (raw)
In-Reply-To: <20050205155031.GA12611@wonderland.linux.it>

On Tue, Feb 08, 2005 at 09:38:46PM +0100, Kay Sievers wrote:
> On Tue, 2005-02-08 at 12:11 -0800, Patrick Mansfield wrote:

> > Okay. Then there is no change needed in scsi_id, and that code should be
> > removed from it. I'm not sure if scsi_id DEVPATH environment variable
> > usage should be removed (for backwards compatibility).
> 
> I think that functionality it's not really needed outside of udev.
> But you still use it for vpd@page0 validation. You may compare that with
> inquiry@page0 instead of using the vendor/model values from sysfs?

I'm not sure what you mean by the above. Can you clarify? Or does the
following answer your question?

The DEVPATH usage and hotplug_mode are mainly for use with udev, the code
is also there for ease of use in any hotplug program (though a script
can easily run scsi_id -s ${DEVPATH}).

There are also some other oddities based on hotplug_mode being set (use
syslog, don't warn on what would be errors for command line usage).

I get the vendor/model via sysfs as there are some quirks related to use
of the INQUIRY and I did not want to duplicate that code or the devinfo
list (black/white list, see drivers/scsi/scsi_scan.c and the scsi_devinfo.c
table; especially the BLIST_INQUIRY_36 and 58). 

In short scsi_inquiry() is always called with evpd set to 1.

> > Given this change, can you revert the tmp directory change (if Marco's OK
> > with that)? Mainly for non-udev command line usage.
> 
> I will do that. Care to give it a try, if it really works with the new
> code. Also with the \n RESULT matching.

OK, I will test it out.

I still haven't tried building and running udev from source on my laptop
(with FC3, better make sure I have a backup boot device).

-- Patrick Mansfield


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
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

  parent reply	other threads:[~2005-02-08 21:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-05 15:50 patches from the debian package Marco d'Itri
2005-02-05 16:14 ` Kay Sievers
2005-02-06 19:05 ` Patrick Mansfield
2005-02-06 19:16 ` Marco d'Itri
2005-02-06 23:13 ` Kay Sievers
2005-02-07 18:39 ` Patrick Mansfield
2005-02-08 19:50 ` Kay Sievers
2005-02-08 19:52 ` Kay Sievers
2005-02-08 20:11 ` Patrick Mansfield
2005-02-08 20:15 ` Greg KH
2005-02-08 20:26 ` Kay Sievers
2005-02-08 20:38 ` Kay Sievers
2005-02-08 21:32 ` Patrick Mansfield [this message]
2005-02-08 21:59 ` Kay Sievers

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=20050208213258.GA1883@us.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 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.