system-config-printer

[Felipe Alfaro Solana]

On 2 Feb 2005, at 12:08, Arjan van de Ven wrote:

> On Wed, 2005-02-02 at 10:49 +0000, Tim Waugh wrote:
>> On Tue, Feb 01, 2005 at 06:06:06PM -0500, Matthew Miller wrote:
>>
>>> On Tue, Feb 01, 2005 at 05:05:14PM -0500, Havoc Pennington wrote:
>>>> The remaining design would be the sysadmin UI, primarily for 
>>>> configuring
>>>> a print *server*. There's a general problem here that we need to 
>>>> define
>>>
>>> Don't forget an easy way to distribute configurations to client 
>>> systems.
>>
>> That certainly was important before we switched to CUPS, but is it
>> now?  Doesn't browsing solve that problem?
>
> it would be nice if there was a zeroconf (or whatever that is called
> this week) thing that advertized a "I have the master printer list for
> cups HERE". All clients would then, without sysadmin work, use this
> list. List would include prefered printer etc etc

Why a master printer list would ever be needed? CUPS support automatic 
printer advertising, so I don't understand the need of a master printer 
list.