linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: add/remove actions for usb devices
Date: Sun, 28 Mar 2004 14:58:20 +0000	[thread overview]
Message-ID: <20040328145820.GA5442@vrfy.org> (raw)
In-Reply-To: <40648838.2040703@labri.fr>

On Sun, Mar 28, 2004 at 04:35:27PM +0200, jjluza wrote:
> I try to do that too.
> I have a script called usbst.dev in /etc/dev.d/block
> it contains :
> 
> #!/bin/bash
> 
> case $ACTION in
> 
> add)
>         ls -l /dev/usbst1 >> /tmp/udeveventlog
>         mount -t vfat -o sync /dev/usbst1 /mnt/usbst
>         echo "mount done" >> /tmp/udeveventlog
>         ls -l /dev/usbst1 >> /tmp/udeveventlog
> esac
> 
> 
> if I try to add a case "remove)", it fails on syntax error
> it seems udev handles add and remove in the same case (ie "add)"), maybe it is 
> what it should do, but it's not easy to manage.
> 
> More, when I plug my usb stick, /tmp/udeveventlog contains :
> brw-------    1 root     root       8,   1 Mar 28 16:20 /dev/usbst1
> brw-------    1 root     root       8,   1 Mar 28 16:20 /dev/usbst1
> mount done
> mount done
> brw-------    1 root     root       8,   1 Mar 28 16:20 /dev/usbst1
> brw-------    1 root     root       8,   1 Mar 28 16:20 /dev/usbst1
> 
> This behaviour seems strange for me, isn't it ?
> Anyway, my usb stick is well mounted, but I get some messages in console which 
> say (2 times) that my stick is already mounted (it seems that the script is 
> run several times), so it's not very clean.

The script is called for every device node udev has created.
You get one event for the main device and one for the partition.
I expect, that you need to look at DEVPATH to catch the
"partition call" only.

Kay


-------------------------------------------------------
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

  parent reply	other threads:[~2004-03-28 14:58 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
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 [this message]
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=20040328145820.GA5442@vrfy.org \
    --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).