From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev - simpler PROGRAM execution with arguments
Date: Wed, 25 Feb 2004 01:42:09 +0000 [thread overview]
Message-ID: <1077673328.1167.5.camel@pim> (raw)
In-Reply-To: <20040225011944.GA25022@vrfy.org>
On Wed, 2004-02-25 at 02:34, Patrick Mansfield wrote:
> On Wed, Feb 25, 2004 at 02:19:44AM +0100, Kay Sievers wrote:
> > While putting the limitations of our PROGRAM execution with arguments in
> > the man page, I asked myself why we don't simply use a subshell if a space
> > is found in the PROGRAM key.
> > It would be possible to use all shell functions like pipe or diversion
> > and we get rid of the hardcoded argument limit.
>
> But now you depend on /bin/sh, is that acceptable?
If it's not there, only the PROGRAM call with arguments will fail.
I think there are only few systems without /bin/sh but udev :)
> > Pat, is this fine with you? scsi_id without arguments is still called
> > directly. As promised, I've added a info() for a failing PROGRAM execution.
>
> Yes, especially since scsi_id should be called with no arguments.
Fine.
thanks,
Kay
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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
next prev parent reply other threads:[~2004-02-25 1:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 1:19 [PATCH] udev - simpler PROGRAM execution with arguments Kay Sievers
2004-02-25 1:34 ` Patrick Mansfield
2004-02-25 1:42 ` Kay Sievers [this message]
2004-02-26 21:31 ` Greg KH
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=1077673328.1167.5.camel@pim \
--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 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.