On Tuesday 05 May 2009 01:55:33 pm Ken Moffat wrote: > > For clfs, I've always had to add things to the minimalist rules in > that book. In this case, a rule for the printer: > > BUS=="usb", KERNEL=="lp[0-9]*", NAME="usb/%k", GROUP="lp"
I surmise perhaps a more 'detailed' entry for for say epson-usb-printer rules could be useful. So I decided to try udevfinfo to get some ideas. This has now morphed into udevadm (I am using udev-128). There is a mini-tutorial on using udevdm at this url:- http://linuxtidbits.wordpress.com/2008/12/02/creating-a-unique-device-node/ the printer is seen as /dev/usb/lp0. unfortunately after issuing the command:- #udevadm info -a -p `udevadm info -q path -n /dev/usb/lp0` I get device path not found. And it does not matter what I set after the -n option -i.e /dev/hda, /sys/block/sda /dev/lp0, /dev/usb/lp0 etc. I checked the manpage for udevadm info and --path=devpath of device to query and --query says it needs the path or name of the device. I thought the -n tag fulfills this. If anyone on list is able to offer assistance with using udevadm and where I am going wrong, your comments will be appreciated. yours sinceely lux-integ > > ĸen > -- > das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
