On Thu, May 07, 2009 at 10:32:38AM +0100, lux-integ wrote: > 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. > The only specific advice I can offer is "keep a note of what worked" - it won't continue to work as udev evolves, but it might be enough to prompt google into divulging useful information.
The last tiem I used udevinfo was last summer, and I've now lost the scars from trying to work out WTF the man page *means* (as distinct from what it *says*). In my case (trying to find out how new memory sticks were identifying themselves, so that I could mount them at the same place as existing sticks) I ended up using udevinfo -a -p `udevinfo -q path -n /dev/sda` (note the "double" involation) - possibly, something similar may help. FWIW, I got that from the Arch wiki like a lot of recent things. Re your earlier post - you mentioned enable and cupsenable - I've never used those (I do it all from the browser), but I can confirm that 1.3.9 and 1.3.10 installed cupsenable. The upgrade to cups in the book hasn't happened yet, so it's still showing the no-longer-supportable 1.2.12. I'm assuming you (as a user) are in the group 'lp' and that you have perms like this: k...@bluesbreaker ~ $ls -l /dev/usb total 0 crw-rw---- 1 root lp 180, 0 2009-05-07 14:25 lp0 If this turns out to be a general cups problem, try changing LogLevel to debug instead of info in /etc/cups/cupsd.conf. That will churn out a vast amount of messages to the cups log. ĸ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
