On Wed, 2008-01-23 at 20:43 +0100, Jan Ritzerfeld wrote: > Am Mittwoch, 23. Januar 2008 schrieb Roger Oberholtzer: > > > [...]. > > The trick here is finding what rules are consulted for each device. The > > udevmonitor program is nice for pluggable devices. I have never been > > able to find an easy human usable method to get the same info for static > > devices, like a built-in cd drive. > > For me, the output of "udevtest /sys/block/sr0" (my built-on dvd writer) > looks quite verbose.
But part of the trick when debugging new rules is knowing that the name of the device in this context is /sys/block/sr0. This gets more interesting for pluggable devices. You have to know the name to find out about it. But where do you get a list of those udev-compatible complete device name in the first place? What is missing from udevtest's list is which name will be called, for example, KERNEL, when the rule is used. udevmonitor can be made to do this, but only for pluggable devices. Unless one changes daemon default startup parameters and reboots. A neat tool would be one that listed all the variables supplied to udev rules for all devices currently in the system. By combining a couple of programs and changing some system daemon options, perhaps with a boot or two added, the info can eventually be obtained. There has to be an easier way. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
