From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: no /dev entry for printer when it is out of ink
Date: Tue, 22 Nov 2005 03:32:47 +0000 [thread overview]
Message-ID: <20051122033247.GA4090@vrfy.org> (raw)
In-Reply-To: <4381C39A.6080907@kordik.net>
On Mon, Nov 21, 2005 at 10:08:44PM -0500, Mike wrote:
> The rule:
> BUS="usb", SYSFS{serial}="0HSLL0108041158030", NAME="lp0", SYMLINK="printers/EPC80"
You may look at:
udevinfo -a -p /class/usb/lp0
if that matches your keys and better use "=" for comparison, but with
the keys you use, it should not cause a problem.
> /dev/lp0 is being created. So it looks like the generic udev rule is
> working. I can change my path to now point there. I don't understand why
> my rule quit working though. I tried escputil with it pointing to
> /dev/lp0 but it just times out.
>
> I changed my printer to point /dev/lp0 but nothing happens when I print.
> I am just going to give in an replace all my color ink cartridges and
> see if that changes anything.
Yeah, that may help to get it to print something, but it's unlikely to
change udev's behavior.
Kay
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_idv28&alloc_id\x16845&op=click
_______________________________________________
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
next prev parent reply other threads:[~2005-11-22 3:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 12:54 no /dev entry for printer when it is out of ink Mike
2005-11-21 18:44 ` Kay Sievers
2005-11-22 1:10 ` Mike
2005-11-22 2:18 ` Kay Sievers
2005-11-22 3:08 ` Mike
2005-11-22 3:32 ` Kay Sievers [this message]
2005-11-22 23:28 ` Mike
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=20051122033247.GA4090@vrfy.org \
--to=kay.sievers@vrfy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.