linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: [udev] support arguments in callout exec
Date: Thu, 20 Nov 2003 20:14:43 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-106941050507604@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106934057408109@msgid-missing>

On Friday 21 November 2003 07:53, Greg KH wrote:
> On Thu, Nov 20, 2003 at 01:47:36AM +0100, Arnd Bergmann wrote:
> > CALLOUT, PROGRAM="sh -c 'echo ${DEVPATH} | tr a-z A-Z'", BUS="usb",
> > ID="XXX", NAME="webcam%n"
>
> Oh come on, why not just make that into a simple script, we're trying to
> keep udev simple :)

Ok, that makes sense.

> > To take that even further, do you think it might be a good idea to
> > preprocess the string in the same way as the NAME= argument, allowing
> > e.g. PROGRAM="/bin/devname %b %M:%m" ?
>
> Hm, good idea.
>
> Someone else also proposed adding a number modifier to the %b field to
> pick out a specific character from a bus id.  Anyone have any thoughts
> about this?  Personally, I think it will be a bit hard to handle bus ids
> that are not fixed widths all the time, but might be handy to try to
> implement a devfs-like udev config file.

When we allow %b in PROGRAM= and find a good way to use the output of
the program as the device name, there won't be any need for such a hack,
as it can better be done in an external script. Getting it right in
udev would be too complicated IMHO (both usage and implementation).

	Arnd <><



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
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:[~2003-11-20 20:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20  0:47 [udev] support arguments in callout exec Arnd Bergmann
2003-11-20  2:59 ` Arnd Bergmann
2003-11-20  3:21 ` Kay Sievers
2003-11-20 12:31 ` Kay Sievers
2003-11-20 16:07 ` Kay Sievers
2003-11-20 17:31 ` Kay Sievers
2003-11-20 20:14 ` Arnd Bergmann [this message]
2003-11-21  6:50 ` Greg KH
2003-11-21  6:53 ` Greg KH
2003-11-22 18:14 ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2003-11-20  1:42 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=marc-linux-hotplug-106941050507604@msgid-missing \
    --to=arnd@arndb.de \
    --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).