From: Michael Buesch <mb@bu3sch.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: My udev rule doesn't work
Date: Sun, 08 Apr 2007 19:59:01 +0000 [thread overview]
Message-ID: <200704082159.01796.mb@bu3sch.de> (raw)
In-Reply-To: <200704071544.36669.mb@bu3sch.de>
On Sunday 08 April 2007 21:53, Michael Buesch wrote:
> run_program: '/lib/udev/deathaddercfg' (stdout) 'run_program: program '/lib/udev/deathaddercfg' not found'
> run_program: '/lib/udev/deathaddercfg' returned with status 1
Oh I'm sorry. Did not see my error here.
So when I put the tool (with full path) into PROGRAM, it's _not_
called on the ADD event, but on udevtest it is and correctly configures the device.
root@powermac:/etc/udev/rules.d# udevtest /class/usb_device/usbdev1.21
main: looking at device '/class/usb_device/usbdev1.21' from subsystem 'usb_device'
run_program: '/usr/local/bin/deathaddercfg -C'
run_program: '/usr/local/bin/deathaddercfg' returned with status 0
run_program: 'usb_device_name --export usbdev1.21'
run_program: '/lib/udev/usb_device_name' (stdout) 'USB_BUS\01'
run_program: '/lib/udev/usb_device_name' (stdout) 'USB_DEV\x021'
run_program: '/lib/udev/usb_device_name' returned with status 0
udev_rules_get_name: rule applied, 'usbdev1.21' becomes 'bus/usb/001/021'
udev_db_get_device: no db file to read /dev/.udev/db/class@usb_device@usbdev1.21: No such file or directory
udev_node_add: creating device node '/dev/bus/usb/001/021', major = '189', minor = '20', mode = '0664', uid = '0', gid = '0'
main: run: 'socket:/org/freedesktop/hal/udev_event'
main: run: 'socket:/org/kernel/udev/monitor
It seems that some sysfs attributes are missing when ADD event is happening, so the
rule doesn't match.
Kernel bug?
--
Greetings Michael.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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:[~2007-04-08 19:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-07 13:44 My udev rule doesn't work Michael Buesch
2007-04-08 19:37 ` Kay Sievers
2007-04-08 19:53 ` Michael Buesch
2007-04-08 19:58 ` Michael Buesch
2007-04-08 19:59 ` Michael Buesch [this message]
2007-04-08 20:28 ` Bryan Kadzban
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=200704082159.01796.mb@bu3sch.de \
--to=mb@bu3sch.de \
--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.