From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [Thinstation-developer] Re: udev PROGRAM action
Date: Wed, 24 Aug 2005 10:39:15 +0000 [thread overview]
Message-ID: <20050824103915.GB5943@vrfy.org> (raw)
In-Reply-To: <430C3C87.4080209@xtra.co.nz>
On Wed, Aug 24, 2005 at 10:17:57PM +1200, Miles Roper wrote:
> this still doesn't work.
>
> is this the way I should be hotplugging? I've spent hours looking on the
> net and hotplug.d seems depreciated with udev0.68.
A while ago we moved hotplug.d/ handling into udev to be able to plug
HAL into the hotplug process and get rid of the hotplug/sysfs races.
Now we removed that from udev itself again, cause with udev-rules you
can do the same as hotplug.d/ did without all the problems of matching
only on the subsystem.
You can still use the old hotplug multiplexer or put a small helper
from the extras/run_directory/ into a udev rule that runs the hotplug.d/
programs.
> From what I see of udev
> it seems to do everything I need. Not being able to specify the name when
> using RUN by design, or will that get added later?
I'm not sure what you mean. If you specify a NAME rule, RUN will also
be called, but if you use NAME, no other action than "add" can ever
trigger that rule. So if you want to call a script for a specific device
for _all_ actions and rename the device at the same time, just use two rules,
one for the name and one for the "generic" RUN.
I think the best way to do this is to add two rules, one for "add" and
one for "remove".
Kay
> Kay Sievers wrote:
> >On Wed, Aug 24, 2005 at 09:23:19PM +1200, Miles Roper wrote:
> >
> >>KERNEL="sd*", ACTION="add", NAME="%k", RUN=+"/etc/udev/scripts/usb.sh
> >>%k"
> >>KERNEL="sd*", ACTION="remove", NAME="%k",
> >>RUN=+"/etc/udev/scripts/usb.sh %k"
> >>
> >>what i'm trying to achieve is hotpluging my usbkey. removing the NAME
> >>key above still doesn't seem to work, infact it stops it from even
> >>calling the script. the line now is
> >>
> >>KERNEL="sd*", BUS="usb", RUN=+"/etc/udev/scripts/usb.sh %k"
> >>
> >>if I remove the NAME key, how can I specify the device name I want in
> >>/dev?
> >
> >
> >It will just get the default name.
> >
> >
> >>Can I use the %k in above, as I need to pass this to the script so I know
> >>which device to mount/umount?
> >
> >
> >Yes, also the environment contains DEVNAME.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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-08-24 10:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 9:23 [Thinstation-developer] Re: udev PROGRAM action Miles Roper
2005-08-24 10:11 ` Kay Sievers
2005-08-24 10:17 ` Miles Roper
2005-08-24 10:39 ` Kay Sievers [this message]
2005-08-24 11:05 ` Miles Roper
2005-08-24 13:47 ` Bill Nottingham
2005-08-24 15:30 ` Christian Zoz
2005-08-24 19:06 ` Kay Sievers
2005-08-24 19:27 ` Thierry Vignaud
2005-08-25 10:53 ` Miles Roper
2005-08-25 11:55 ` Kay Sievers
2005-08-25 12:03 ` Miles Roper
2005-08-31 7:20 ` Greg KH
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=20050824103915.GB5943@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).