From: Florian Iragne <florian.iragne@labri.fr>
To: linux-hotplug@vger.kernel.org
Subject: Re: add/remove actions for usb devices [oups]
Date: Sun, 28 Mar 2004 12:08:40 +0000 [thread overview]
Message-ID: <4066C048.8050202@labri.fr> (raw)
Greg KH wrote:
>On Fri, Mar 26, 2004 at 10:22:14PM +0100, Florian Iragne wrote:
>
>
>>
>>
>>>Or if you want to catch the fact when udev removes a /dev node (which
>>>odds are is what you really want to catch), put your script, or a link
>>>to it in /etc/dev.d/block/ with the extension .dev and you will get both
>>>add and remove events that corrisponded to a udev create or remove
>>>device node.
>>>
>>>
>>>
>>>
>>>
>>just one more stupid question! ;-)
>>
>>is this /etc/dev.d/block/ directory supposed to already exist? i think
>>so but can't find it. On my debian sid, i have /etc/udev directory, but
>>no block in this
>>
>>
>
>You need the 023 release for this to work.
>
>And no, that directory will not be there, you need to create it
>yourself.
>
>
>
>>and another one in fact : is the creation of a SYMLINK considered as a
>>node add?
>>
>>
>
>No, but the SYMLINK had to be created to point to some real node, right?
>:)
>
>That should all happen in one action.
>
>thanks,
>
>greg k-h
>
>
oups, i just find your article about this feature!
http://lwn.net/Articles/77350/
sorry! ;-)
Florian
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&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
reply other threads:[~2004-03-28 12:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4066C048.8050202@labri.fr \
--to=florian.iragne@labri.fr \
--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.