From: Jim Gifford <maillist@jg555.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Udev question PROGRAM= question
Date: Tue, 15 Mar 2005 06:53:23 +0000 [thread overview]
Message-ID: <42368663.2010803@jg555.com> (raw)
In-Reply-To: <42364AA2.8080306@jg555.com>
Kay Sievers wrote:
>On Mon, 2005-03-14 at 18:38 -0800, Jim Gifford wrote:
>
>
>>If I run a program during the rules creation, example rule
>> KERNEL="fd[0-9]*", PROGRAM="/etc/udev/scripts/floppy-devices.sh %k"
>>When the device gets removed, how do I tell it to remove everything, or
>>run the same program, to remove the /dev entries??
>>
>>
>
>PROGRAM= is used to return a string that can be matched against with
>RESULT=, or be used to set the name of a node with %c. You should not do
>anything else on with a callout.
>
>
>
Kay, let me rephrase my response.
The output of my script is the following
# ./* fd0
fd0 b 2 0
fd0u360 b 2 12
fd0u720 b 2 16
fd0u800 b 2 120
fd0u820 b 2 52
fd0u830 b 2 68
fd0u1040 b 2 84
fd0u1120 b 2 88
fd0u1440 b 2 28
fd0u1600 b 2 124
fd0u1680 b 2 44
fd0u1722 b 2 60
fd0u1743 b 2 76
fd0u1760 b 2 96
fd0u1840 b 2 116
fd0u1920 b 2 100
fd0u2880 b 2 32
fd0u3200 b 2 104
fd0u3520 b 2 108
fd0u3840 b 2 112
What would my udev rule be?
--
----
Jim Gifford
maillist@jg555.com
-------------------------------------------------------
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-03-15 6:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 2:38 Udev question PROGRAM= question Jim Gifford
2005-03-15 2:54 ` Kay Sievers
2005-03-15 5:42 ` Jim Gifford
2005-03-15 6:53 ` Jim Gifford [this message]
2005-03-15 11:36 ` 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=42368663.2010803@jg555.com \
--to=maillist@jg555.com \
--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).