On Wed, 2004-11-03 at 13:50 -0700, CW Harris wrote: > On Wed, Nov 03, 2004 at 12:29:49PM -0800, Rich Rudnick wrote: > > On Wed, 2004-11-03 at 19:39 +0000, Adam Funk wrote: > [...] > > > > > > Thanks for that info. As I said in another post in this thread, > > > modifying /etc/printcap alone didn't seem to have any effect---does my > > > lpr command (from the packages I listed above) use it at all or not? > > > > > No, CUPS doesn't use printcap, or at least it doesn't with the version > > in unstable. > > > > cupsys-bsd provides the lpr used with CUPS, which is a near replacement > > for for the bsd lpr. IIRC it is missing a few options and has a few of > > it's own, but I've never had any incompatibilities with programs > > expecting bsd's lpr. In other words, just use localhost:631/admin to > > define your printers, ignore /etc/printcap and everything should work as > > expected. > > Rather than ignore it, I think it is better to link /etc/printcap to the > CUPS printcap file (/etc/printcap.cups by default IIRC), then applications > that try to use /etc/printcap will be using the correct one.
Except that I don't have an /etc/printcap.cups :) The changelog states that it's been moved to /var/run/cups/printcap, 'since it's generated and non-editable', and says 'take care of the /etc/printcap symlink.' Don't know what that means, since my existing /etc/printcap was generated on Feb 28 by cupsys and is not a link. I think I need to look at the bug reports. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
