linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: patches from the debian package
Date: Tue, 08 Feb 2005 19:50:10 +0000	[thread overview]
Message-ID: <1107892210.5536.12.camel@localhost.localdomain> (raw)
In-Reply-To: <20050205155031.GA12611@wonderland.linux.it>

On Mon, 2005-02-07 at 10:39 -0800, Patrick Mansfield wrote:
> On Mon, Feb 07, 2005 at 12:13:09AM +0100, Kay Sievers wrote:
> > On Sun, 2005-02-06 at 11:05 -0800, Patrick Mansfield wrote:
> > > On Sat, Feb 05, 2005 at 04:50:31PM +0100, Marco d'Itri wrote:
> > > 
> > > > 
> > > > scsi_id_tmp: when udevstart is started, /tmp is not writeable.
> > > > 
> > > 
> > > What if /dev does not exist (udev_root modified) or perhaps not writable?
> > > 
> > > Does udev put temp files under /dev?
> > 
> > Hmm, what about letting udev create the temporary node, instead of doing
> > it in the *_id programs itself? That may be the best solution.
> > 
> > Something like:
> >   PROGRAM="/sbin/scsi_id -d %N", ...
> > 
> > What do you think?
> 
> Yes, that would be nice.
> 
> scsi_id pre-dates the addition of any of the % code, and relies on the
> DEVPATH environment variable.
> 
> So it also needs code changes to use the DEVPATH plus any command line
> option, and/or a new % value for the sysfs path, like:
> 
> 	PROGRAM="scsi_id -d %N -s %p", ...

Ok, I did that. We have %N and %p now. 

> It should still figure out whether or not to print a trailing "\n" for
> normal command line usage. DEVPATH set could be the trigger, though that
> is not clean (using -s <devpath> for sysfs path, but then using DEVPATH to
> figure out if \n is printed).

RESULT does not care about a trailing \n.

Thanks,
Kay



-------------------------------------------------------
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 19:50 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 [this message]
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
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=1107892210.5536.12.camel@localhost.localdomain \
    --to=kay.sievers@vrfy.org \
    --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).