From: Florian Iragne <florian.iragne@labri.fr>
To: linux-hotplug@vger.kernel.org
Subject: Re: add/remove actions for usb devices
Date: Fri, 26 Mar 2004 21:13:23 +0000 [thread overview]
Message-ID: <40649CF3.6000400@labri.fr> (raw)
In-Reply-To: <40648838.2040703@labri.fr>
Greg KH wrote:
>On Fri, Mar 26, 2004 at 08:44:56PM +0100, Florian Iragne wrote:
>
>
>>Hello everybody,
>>
>>i've just a simple question and i didn't find any clues about the answer
>>on the internet, so i ask you : why is there no "remove" action for usb
>>devices with hotplug?
>>
>>
>
>The remove event happens just fine. It's just that the current scripts
>don't do anything with it :)
>
>
>
>>my current problem is that i looking for a solution to mount/umount
>>usb-storage devices automagically when they are plugged/unplugged, but
>>since there is no remove event, i must write a complex script to do it
>>(currently working on 2.6.4-ck1 and udev).
>>
>>
>
>But there is an event. You can catch it on your own if you want. Just
>put your script in /etc/hotplug.d/usb/
>
>
>
well actually, i've already try this and never catch the remove event.
just to test i've made this single script :
if [ "$ACTION" = "add" -a "$TYPE" = "usb" ]; then
echo "add" >> /var/log/hotplug
fi
if [ "$ACTION" = "remove" -a "$TYPE" = "usb" ]; then
echo "remove">>/var/log/hotplug
fi
i do catch the add, but no trace of remove action in the log
>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.
>
>
yes, i think it's a better way, since currently i have to add a "sleep
10" instruction to wait for udev to create th node i want to move
>Hope this helps,
>
>greg k-h
>
>
thanks a lot, i will try this!
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
next prev parent reply other threads:[~2004-03-26 21:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 19:44 add/remove actions for usb devices Florian Iragne
2004-03-26 19:51 ` Greg KH
2004-03-26 21:13 ` Florian Iragne [this message]
2004-03-26 21:22 ` Florian Iragne
2004-03-26 22:59 ` Greg KH
2004-03-28 12:05 ` Florian Iragne
2004-03-28 13:45 ` Florian Iragne
2004-03-28 13:52 ` Kay Sievers
2004-03-28 14:08 ` Martin Lohmeier
2004-03-28 14:35 ` jjluza
2004-03-28 14:58 ` Kay Sievers
2004-03-28 16:16 ` jjluza
2004-03-28 18:02 ` Florian Iragne
2004-03-28 18:19 ` Kay Sievers
2004-03-29 16:21 ` Florian Iragne
2004-03-29 16:36 ` Florian Iragne
2004-03-29 18:51 ` Patrick Mansfield
2004-03-29 19:11 ` Martin Lohmeier
2004-03-29 23:26 ` jjluza
2004-03-30 7:22 ` Florian Iragne
2004-03-30 7:25 ` Florian Iragne
2004-03-30 8:35 ` jjluza
2004-03-30 8:49 ` Florian Iragne
2004-03-30 9:48 ` jjluza
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=40649CF3.6000400@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 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).