linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: sean <seandarcy2@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] Update writing udev rules documentation
Date: Mon, 10 Jul 2006 01:37:35 +0000	[thread overview]
Message-ID: <e8sb10$2eq$1@sea.gmane.org> (raw)
In-Reply-To: <4481B0C5.80301@gentoo.org>

Daniel Drake wrote:
> Hi,
> 
> I finally got around to reworking the udev rules documentation. It is 
> now more of a general guide to rule writing and the various things you 
> can do, with examples.
> 
> The patch isn't very readable, if anyone wants to review the changes I 
> suggest you just look at the online version as almost all of it has been 
> rewritten:
> http://www.reactivated.net/writing_udev_rules.html
> 
> Comments appreciated.
> 
> Daniel

Even this late?

Just been trying to set up a usb printer.

 From Writing udev rules:

Examples
USB Printer

I power on my printer, and it is assigned device node 
/dev/lp0. Not satisfied with such a bland name, I decide to 
use udevinfo to aid me in writing a rule which will provide 
an alternative name:

# udevinfo -a -p $(udevinfo -q path -n /dev/lp0)
........

At least on my fc6-test1 ( 2.6.18-rc1) machine, /dev/lp0 is 
for the parallel port (even though no printer is attached ) 
and /dev/usb/lp0 is for the usb printer.


dmesg |grep lp0
PM: Adding info for No Bus:lp0
drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer 
dev 2 if 1 alt 0 proto 2 vid 0x04B8 pid 0x0803
lp0: using parport0 (interrupt-driven).
lp0: console ready
drivers/usb/class/usblp.c: usblp0: off-line

Did earlier kernels use lp0 for usb printers? If not, how about:

I power on my printer, and it is assigned device node 
/dev/usb/lp0. Not satisfied with such a bland name, I decide 
to use udevinfo to aid me in writing a rule which will 
provide an alternative name:

# udevinfo -a -p $(udevinfo -q path -n /dev/usb/lp0)


sean




-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

      parent reply	other threads:[~2006-07-10  1:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-03 15:54 [PATCH] Update writing udev rules documentation Daniel Drake
2006-06-03 16:09 ` Andrey Borzenkov
2006-06-03 16:40 ` Daniel Drake
2006-06-03 23:38 ` Nick
2006-06-04 10:57 ` Remco
2006-06-04 16:24 ` Remco
2006-06-05  1:15 ` MUNEDA Takahiro
2006-06-06 12:24 ` Bryan Kadzban
2006-06-06 16:19 ` Kay Sievers
2006-06-09 21:52 ` Daniel Drake
2006-06-09 21:58 ` Daniel Drake
2006-06-09 22:34 ` Kay Sievers
2006-07-10  1:37 ` sean [this message]

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='e8sb10$2eq$1@sea.gmane.org' \
    --to=seandarcy2@gmail.com \
    --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).