linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Remco <remco@d-compu.dyndns.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] Update writing udev rules documentation
Date: Sun, 04 Jun 2006 16:24:44 +0000	[thread overview]
Message-ID: <20060604162446.B45761EF2@mail.d-compu.nl> (raw)
In-Reply-To: <4481B0C5.80301@gentoo.org>

> Comments appreciated.
> 

This may be an useful addition, gave me a bit of a headache the past two
days. 

Both the lp and the usblp driver create devices named lp[n], though
the kernel messages suggest an usblp[n] device for the USB printer.

When both a parallel port printer and an USB printer are attached they will
both be called lp0 leaving the system with only one device node. (So one of
the printers will be missing)

So far the best way to make a distinction seemed to be filtering on
subsystem, e.g.:

# printers
KERNEL="lp[0-9]*", SUBSYSTEM="printer",  NAME="printer/lpt%n"
KERNEL="lp[0-9]*", SUBSYSTEM="usb",      NAME="printer/usb%n"

This way parallel port printers will be called 'printer/lpt[n]' and USB
printers 'printer/usb[n]'.



_______________________________________________
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-06-04 16:24 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 [this message]
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

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=20060604162446.B45761EF2@mail.d-compu.nl \
    --to=remco@d-compu.dyndns.org \
    --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).