i have a script that has 2 invocations of udevadm, ...
+ /sbin/udevadm info --query=all
--path=/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/0003:1808:5555.0004
device path not found
+ /sbin/udevadm test
/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/0003:1808:5555.0004
run_command: calling: test
udevadm_test: version 136
parse_file: reading '/lib/udev/rules.d/10-moblin.rules' as rules file
parse_file: reading '/etc/udev/rules.d/12-usb.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-alsa.rules' as rules file
parse_file: reading '/lib/udev/rules.d/50-firmware.rules' as rules file
parse_file: reading '/lib/udev/rules.d/50-udev-default.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-cdrom_id.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-serial.rules' as
rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-storage-tape.rules'
as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-v4l.rules' as rules
file
parse_file: reading '/lib/udev/rules.d/61-persistent-storage-edd.rules'
as rules file
parse_file: reading '/etc/udev/rules.d/70-persistent-net.rules' as rules
file
parse_file: reading '/lib/udev/rules.d/75-cd-aliases-generator.rules' as
rules file
parse_file: reading
'/lib/udev/rules.d/75-persistent-net-generator.rules' as rules file
parse_file: reading '/lib/udev/rules.d/79-fstab_import.rules' as rules file
parse_file: reading '/lib/udev/rules.d/80-drivers.rules' as rules file
parse_file: reading '/etc/udev/rules.d/90-alsa.rules' as rules file
parse_file: reading '/etc/udev/rules.d/90-hal.rules' as rules file
parse_file: reading '/etc/udev/rules.d/92-connman.rules' as rules file
parse_file: reading '/lib/udev/rules.d/95-udev-late.rules' as rules file
parse_file: reading '/etc/udev/rules.d/iwmxsdk.rules' as rules file
udev_rules_new: rules use 9048 bytes tokens (754 * 12 bytes), 5641 bytes
buffer
udev_rules_new: temporary index used 6820 bytes (341 * 20 bytes)
unable to open device
'/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/0003:1808:5555.0004'
This program is for debugging only, it does not run any program,
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
how come the info failed to find the path that the test did?
just checking, jackc...
--
jack craig
[email protected]
831-684-1375 (Office)
831-596-6924 (cell)
IM: jackcraigaptos (AIM)
_________________________________
This email has been ClamScanned !
www.LinuxLightHouse.com
_______________________________________________
Moblin dev Mailing List
[email protected]
To manage or unsubscribe from this mailing list visit:
https://lists.moblin.org/mailman/listinfo/dev or your user account on
http://moblin.org once logged in.
For more information on the Moblin Developer Mailing lists visit:
http://moblin.org/community/mailing-lists
