From: Mangus <ml@deprecated.it>
To: linux-hotplug@vger.kernel.org
Subject: rules and RUN key
Date: Tue, 22 Nov 2005 23:01:29 +0000 [thread overview]
Message-ID: <200511230001.45163.ml@deprecated.it> (raw)
[-- Attachment #1: Type: text/plain, Size: 1752 bytes --]
Hi all, I'm trying to study the RUN key of udev rules, but I really don't
understand why this rule doesn't work..
BUS=="usb", SYSFS{product}="Sony DSC", KERNEL="sda1", ACTION=="add",
SYMLINK+="digitalcamera", RUN="/opt/kde/bin/digikam"
the symlink 'digitalcamera is correctly done in /dev and I can easily mount it
but the RUN key seems not executed.
Does the RUN command has to be executed when a rule is matched?
what I'm missing or doing wrong??
root@saturno:~# udevtest /sys/block/sda/sda1 usb
main: looking at device '/block/sda/sda1' from subsystem 'usb'
add_to_rules: error parsing SYSFS attribute in 'BUS'
main: opened class_dev->name='sda1'
udev_rules_get_name: add symlink 'digitalcamera'
udev_rules_get_name: reset run list
udev_rules_get_name: rule applied, 'sda1' becomes 'sda1'
create_node: creating device node '/dev/sda1', major = '8', minor = '1', mode
= '0660', uid = '0', gid = '6'
create_node: creating symlink '/dev/digitalcamera' to 'sda1'
root@saturno:~# udevmonitor
udevmonitor prints the received event from the kernel [UEVENT]
and the event which udev sends out after rule processing [UDEV]
UEVENT[1132699412.958174] add@/devices/pci0000:00/0000:00:03.3/usb1/1-1
UEVENT[1132699413.031376]
add@/devices/pci0000:00/0000:00:03.3/usb1/1-1/1-1:1.0
UEVENT[1132699413.038090] add@/class/scsi_host/host3
UEVENT[1132699413.189695] add@/class/usb_device/usbdev1.5
UEVENT[1132699418.191140]
add@/devices/pci0000:00/0000:00:03.3/usb1/1-1/1-1:1.0/host3/target3:0:0/3:0:0:0
UEVENT[1132699418.250136] add@/block/sda
UEVENT[1132699418.308443] add@/block/sda/sda1
UEVENT[1132699418.354008] add@/class/scsi_device/3:0:0:0
thanks for hints and explanations
--
Fede
Be cool - get Slack.
--
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-11-22 23:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 23:01 Mangus [this message]
2005-11-22 23:18 ` rules and RUN key Kay Sievers
2005-11-23 11:26 ` Harald Hoyer
2005-11-23 18:44 ` Mangus
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=200511230001.45163.ml@deprecated.it \
--to=ml@deprecated.it \
--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).