Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!ihnp4!qantel!lll-lcc!lll-crg!nike!think!mit-eddie!genrad!decvax!ucbvax!ucbcad!zen!cory.Berkeley.EDU!chapman
From: chapman@cory.Berkeley.EDU (Brent Chapman)
Newsgroups: soc.college
Subject: Re: Printout theft (was: Grading, atmosphere at Georgia Tech)
Message-ID: <357@zen.BERKELEY.EDU>
Date: Fri, 26-Sep-86 23:22:09 EDT
Article-I.D.: zen.357
Posted: Fri Sep 26 23:22:09 1986
Date-Received: Tue, 30-Sep-86 06:17:16 EDT
References: <599@ukecc.UUCP> <119@blnt1.UUCP> <933@usl.UUCP>
Sender: news@zen.BERKELEY.EDU
Reply-To: chapman@cory.Berkeley.EDU.UUCP (Brent Chapman)
Distribution: net
Organization: UNIXversity of California at Berkeley
Lines: 33

In article <933@usl.UUCP> jew@usl.UUCP (James E. Wilson) writes:
>I would  be interested in hearing about IO arrangements at other
>schools.

I/O arrangements?  What I/O arrangements?

Seriously.  We have about a half-dozen line printers and a couple of Sun
(really Apple, but anyway) LaserWriters that are generally used by
undergrads.  All are in totally open, non-monitored environments, adjacent
to terminal rooms.  The biggest problems we have are when the output
doesn't stack right (does it ever?), and when the tiny printer rooms
(the smallest is also one of the busiest) fill up with trash (discarded
headers, old printouts, etc.).  You sometimes have to dig to find a
printout.  General cleanup method for these rooms is to dump everything,
so if you print something, but don't go dig it out before the room
gets purged, you're usually out of luck.

We generally don't have problems with printout theft; most people run
a print job, then go pick it within the next five minutes.  That, or
they don't pick it up at all...  "Abandoned" printouts are a bigger
problem than "missing" printouts.

I like things this way; I generally hack during the wee hours of the
morning, when I/O rooms on other campuses are apparently closed.


Brent

--

Brent Chapman

chapman@cory.berkeley.edu	or	ucbvax!cory!chapman