From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: bash script not working from /etc/dev.d/foo/foo.dev
Date: Sat, 26 Feb 2005 00:30:06 +0000 [thread overview]
Message-ID: <1109377806.7242.151.camel@localhost.localdomain> (raw)
In-Reply-To: <1109368267.31191.7.camel@X40.blinkeye.ch>
On Fri, 2005-02-25 at 22:51 +0100, BlinkEye wrote:
>hello,
>
>i think i found a bug. i've written a bash script which should be
>executed upton plugin in my digital camera on a usb port. the thing is
>that it simply DOESN'T work CORRECTLY if it is automatically executed
>from /etc/dev.d/foo/foo.dev upon plugin in my device. it WORKS if i
>execute the script directly. the strange thing is that it IS being
>executed, but not the hole script.
>first i thought i couldn't use functions in /etc/dev.d/foo but it didn't
>change a thing.
>is there a limit of instructions? i tried to just add a line which
>executes the script on another location, still no go.
>
>ANY ideas?
Yeah, read the udev man page. :)
And place your script in /etc/dev.d/default/
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
prev parent reply other threads:[~2005-02-26 0:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-25 21:51 bash script not working from /etc/dev.d/foo/foo.dev BlinkEye
2005-02-26 0:30 ` Kay Sievers [this message]
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=1109377806.7242.151.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).