From: Miles Roper <mroper@xtra.co.nz>
To: linux-hotplug@vger.kernel.org
Subject: Re: [Thinstation-developer] Re: udev PROGRAM action
Date: Thu, 25 Aug 2005 10:53:05 +0000 [thread overview]
Message-ID: <430DA311.3010407@xtra.co.nz> (raw)
In-Reply-To: <430C3C87.4080209@xtra.co.nz>
Hi Kay,
Oops missed that. Thanks for your help on this. I've got it working now :o)
Another question for you ;o)
I've noticed that there is a devfs udev rules file, but it says not to use it as devfs compatibalty
isn't really the way to go. I've also noticed mandrake & others all seem to use it. Is there a
standard defined somewhere which lists what device name/symlinks you should use for likes of ide
devices & others? Either I try to get the devfs script file working, or recode several different
scripts. Both is about the same amount of work as the script doesn't work on busybox ash.
Also, I don't want to have to recode things again later on so are trying to work out the best way to
do it now.
Thanks
Miles
Kay Sievers wrote:
> On Wed, Aug 24, 2005 at 09:47:47AM -0400, Bill Nottingham wrote:
>
>>Miles Roper (mroper@xtra.co.nz) said:
>>
>>>Thanks very much for your help so far. Its starting to make sense :o)
>>>
>>>I still can't get the below rule to work :o(
>>>
>>>KERNEL="sd*", ACTION="add", BUS="usb", RUN=+"/etc/udev/scripts/usb.sh"
>>>KERNEL="sd*", ACTION="remove", BUS="usb", RUN=+"/etc/udev/scripts/usb.sh"
>>>
>>>neither script gets run (as they create a test file in /tmp if they run)
>>>
>>>I can post info from syslog when the device is added if you want?
>>
>>sd* device names are on the SCSI bus, not the USB bus.
>
>
> That should match, cause udev will walk up the chain of devices in
> sysfs. Matching on SYSFS, DRIVER and BUS on any of the devices
> following the "device" link should work. (But all matches must be true on
> the same device directory, you can't match BUS and SYSFS from different
> devices at the same time. See "udevinfo -a -p /block/sda".)
>
> It's RUN+="...", not RUN=+"...". :)
> And you can't match on BUS with "remove" cause there is no bus anymore,
> while the device is removed. Only in the environment of the event you
> will find PHYSDEVBUS, cause the kernel knows that, but the sysfs
> directory is already gone. ENV{PHYSDEVBUS}="..." should work if really
> needed.
>
> Kay
>
-------------------------------------------------------
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-25 10:53 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
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 [this message]
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=430DA311.3010407@xtra.co.nz \
--to=mroper@xtra.co.nz \
--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).