linux-kernel - Re: Patch: usblp quirk for zebra printers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 25 May 2008 12:03:45 +0300
From:	"P. Christeas" <p_christ@....gr>
To:	Pete Zaitcev <zaitcev@...hat.com>
Cc:	Oliver Neukum <oliver@...kum.org>,
	lkml <linux-kernel@...r.kernel.org>, linux-usb@...r.kernel.org,
	twaugh@...hat.com
Subject: Re: Patch: usblp quirk for zebra printers

On Thursday 22 May 2008, Pete Zaitcev wrote:
> On Wed, 21 May 2008 20:57:49 +0300, "P. Christeas" <p_christ@....gr> wrote:
> > I guess such a quirk may be a little odd, but it has been a blocking
> > point in my system not being able to support more than one printer.
> Personally, I don't like this. In kernel, we typically try not to
> fake things in lower levels in order to fool upper levels. 
>...
> I'm cc-ing this to Tim Waugh.

I'm now working in a more "politically correct" way around that issue [1]. The 
outline is that we _add_ a backend to CUPS[2], which will bring back USB 
addressing by /dev/.. name. Then, we could implement udev rulesets which will 
create "by-id" symlinks to the usblpX devices. 
My work is at github under "cups-usbbackend".


[1] it is a blocking point for my business, as I cannot attach a second 
printer.
[2] it could remain a complementary package until we really agree we want that 
code mainline.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/