Re: Request for comments: new `lpd' suite feature

2000-07-16 Thread Garance A Drosihn
At 9:25 PM -0700 7/14/00, Thomas D. Dean wrote: How would this work with printers on local networks? Say, a print server 192.168.1.73? If you do not have a special DNS entry for that printer, then this new synthetic-printcap option would do nothing for you. In other words, you would continue

Re: Request for comments: new `lpd' suite feature

2000-07-16 Thread Garance A Drosihn
At 12:09 AM -0400 7/15/00, Louis A. Mamakos wrote: I almost hate to bring this up, but I think the unnamed-here proposed replacement for our lpd allows you to set your PRINTER environment variable to something like [EMAIL PROTECTED] louie For what it's worth, I think that feature is a

Re: Request for comments: new `lpd' suite feature

2000-07-16 Thread Garrett Wollman
On Sun, 16 Jul 2000 16:46:58 -0400, Christopher Masto [EMAIL PROTECTED] said: Huh? Security through ignorance? Remember that `lpr' is setuid-root and uses a ``privileged'' port for its communications. Many sites may still be using trusted-host ``authentication'' internally, and LPRng's

Re: Request for comments: new `lpd' suite feature

2000-07-16 Thread Christopher Masto
On Sun, Jul 16, 2000 at 08:15:05PM -0400, Garrett Wollman wrote: On Sun, 16 Jul 2000 16:46:58 -0400, Christopher Masto [EMAIL PROTECTED] said: Huh? Security through ignorance? Remember that `lpr' is setuid-root and uses a ``privileged'' port for its communications. Many sites may still

Re: Request for comments: new `lpd' suite feature

2000-07-16 Thread Cyrille Lefevre
Christopher Masto [EMAIL PROTECTED] writes: On Sun, Jul 16, 2000 at 08:15:05PM -0400, Garrett Wollman wrote: On Sun, 16 Jul 2000 16:46:58 -0400, Christopher Masto [EMAIL PROTECTED] said: Huh? Security through ignorance? Remember that `lpr' is setuid-root and uses a ``privileged''

Re: Request for comments: new `lpd' suite feature

2000-07-14 Thread Garance A Drosihn
At 5:39 PM -0400 7/14/00, Garrett Wollman wrote: Around here, we have a convention that each printer has a record in the DNS for printername.lpd-spooler which points to the print server for that printer. It occurred to me that, if there are no local printers, no additional information is needed

Re: Request for comments: new `lpd' suite feature

2000-07-14 Thread Louis A. Mamakos
I almost hate to bring this up, but I think the unnamed-here proposed replacement for our lpd allows you to set your PRINTER environment variable to something like [EMAIL PROTECTED] louie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of

Re: Request for comments: new `lpd' suite feature

2000-07-14 Thread Thomas D. Dean
How would this work with printers on local networks? Say, a print server 192.168.1.73? tomdean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message