From: Tobias Klauser <tklauser@access.unizh.ch>
To: linux-hotplug@vger.kernel.org
Subject: Re: bash script not CORRECTLY working from /etc/dev.d/foo/foo.dev
Date: Sat, 26 Feb 2005 11:28:35 +0000 [thread overview]
Message-ID: <20050226112835.GA1155@neon> (raw)
In-Reply-To: <1109415279.16172.8.camel@X40.blinkeye.ch>
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
A: No.
Q: Should I include quotations after my reply?
(Sorry fo stealing this, Greg)
On Sat, Feb 26, 2005 at 11:54:40AM +0100, BlinkEye wrote:
> i do read the man page. i still believe this is a bug. the script IS
> executed, but not the hole part. (i easily verified that with playing
> sounds in different parts of the script). i tried putting it in
> /etc/dev.d/default - still the same behaviour. it works comletely if i
> execute it manually. besides - i removed the ACTION commands - so it's
> not that either.
It may be an error in your script which is causing the misbehaviour.
Perhaps you could post it here to clarify this.
Cheers, Tobias
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-02-26 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-26 10:54 bash script not CORRECTLY working from /etc/dev.d/foo/foo.dev BlinkEye
2005-02-26 11:28 ` Tobias Klauser [this message]
2005-02-26 14:21 ` BlinkEye
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=20050226112835.GA1155@neon \
--to=tklauser@access.unizh.ch \
--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.