Changes between Version 1 and Version 2 of HowAthenaWorks


Ignore:
Timestamp:
10/28/13 20:54:00 (8 years ago)
Author:
ambhave
Comment:

Fixed small type "systms" to "systems"

Legend:

Unmodified
Added
Removed
Modified
  • HowAthenaWorks

    v1 v2  
    1313As far as printing is concerned, the current setup is a single CUPS server, printers.mit.edu (well, actually several behind a hardware load balancer), and clients configured to "BrowsePoll" against that server. We have custom lpr/lpq/etc. commands that themselves end up calling the CUPS versions of those commands, partly to translate syntax from our previous printing system (LPRng) and partly to run lpq, lprm, etc. against the server behind the load balancer that actually owns the print job. For a smaller setup you can just run a single CUPS server, set /etc/cups/client.conf to point all clients to that server (which will break non-networked printers as a side effect), and use CUPS' own lpr/lpq/etc. -- this is what CSAIL does, for instance, since they only have a couple dozen printers in one building. 
    1414 
    15 If you're interested in historical context behind the design, I'm a fan of the 20-year-old paper "Berkeley UNIX on 1000 Workstations: Athena Changes to 4.3BSD"; although operating systes have become much more modular and lots of Athena software, such as Kerberos, has gotten adopted in the world at large, surprisingly much of the paper is still relevant. 
     15If you're interested in historical context behind the design, I'm a fan of the 20-year-old paper "Berkeley UNIX on 1000 Workstations: Athena Changes to 4.3BSD"; although operating systems have become much more modular and lots of Athena software, such as Kerberos, has gotten adopted in the world at large, surprisingly much of the paper is still relevant. 
    1616  http://geofft.mit.edu/p/berkeley-unix-on-1000-workstations.pdf 
    1717