[16] in athena10
Re: Printing and Athena 10
daemon@ATHENA.MIT.EDU (Tim Abbott)
Sun Dec 23 21:51:31 2007
Date: Sun, 23 Dec 2007 21:51:18 -0500 (EST)
From: Tim Abbott <tabbott@MIT.EDU>
To: Greg Hudson <ghudson@mit.edu>
cc: athena10@mit.edu
In-Reply-To: <200712231423.lBNENwPG022060@equal-rites.mit.edu>
Message-ID: <Pine.LNX.4.64L.0712232121330.9498@coset.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Sun, 23 Dec 2007, Greg Hudson wrote:
> Considerations for the future:
>
> * Going one step up, Operations could run a cupsd with printer
> definitions for the centrally-maintained printers. cupsd on
> Athena 10 machines could then be configured with a "BrowsePoll"
> directive to incorporate this list of printers. People could
> define locally-maintained printers in their local cupsd
> configurations. Even the centrally-maintained printers would be a
> fairly big list, so this might not be the best user experience,
> but it would work.
One thing that might help with this is to name the Printers in CUPS
cleverly. Rather than calling it "ajax", call it "(W20-5) ajax"; assuming
that these get sorted alphabetically, it would make the UI disaster of the
centrally-maintained printers in a big list a bit better. geofft is
working on setting up a test CUPS server exporting the cluster printers
using this trick.
> * The best user experience might come from configuring the routers
> to advertise a subnet-specific list of printers over multicast DNS
> (or broadcast SNMP). That would require help from NIST and
> presumably depends on what our router equipment supports.
> Printers specified this way would show up automatically on stock
> Ubuntu and OSX machines (I believe) in addition to Athena
> machines.
Would this mean that you couldn't (easily) print to machines on a "far
away" subnet?
-Tim Abbott
