[comp.unix.admin] Recreational Computing policies, guidelines, etc.

vturner@nmsu.EDU (Vaughan Turner) (12/06/90)

We are attempting to set up a campus-wide computing policy here at
NMSU.

I'm interested in what policies other universities (businesses, etc)
are using, and how effective they are.

I'd really like to know about *in place* policies (including "we don't
have a policy") and problems resulting/alleviated by these policies.

For the time being, I am *NOT* asking for a "Well, I think..." series
of responses.

Some people may relate the term "recreational computing" to game
playing, but I would like it to be broader than that.  It should also
include programming for fun, etc.

I am looking for policy on any type of recreational computing, be it
on multi-user systems (Unix boxes) as well as standalone machines
(IBMs, Macs, etc).

Thanks for your attention,

Vaughan
--
                     VaughAn Turner     Internet: vturner@nmsu.edu
     Networking/Workstation Support     Box 30001, Dept. 3AT
    Computer Center, Networking/WSC     Las Cruces, New Mexico
        New Mexico State University     88003-0001
        Bitnet: vturner@nmsu.bitnet     UUCP: ucbvax!nmsu.edu!vturner
  Work: (505) 646-4244     FAX: (505) 646-5278      Home: (505) 522-3653

     Home Address: 1115 Larry Drive     Las Cruces, New Mexico 88001-5457

"...the first rule of engineering [is] to work with Earth's natural forces,
never against them."
                                                     "Earth"  by David Brin

tchrist@convex.COM (Tom Christiansen) (12/06/90)

In article <VTURNER.90Dec5171956@wilma.nmsu.EDU> vturner@nmsu.EDU (Vaughan
Turner) asks about a campus wide policy on recreational computing.

I was a sysadmin at a large university computing center for five years.
Game playing was restricted to only times when the load was low, and a
daemon would get you if you didn't respect this policy.  

Recreational programming, however, was permitted and encouraged, so long
as it didn't interfere with people's classwork.  In practice, there were
only two cases of this: now and then someone or other would inevitably
write a program that forked forever or else stepped backwords in memory a
page at a time, trashing the VM system.  This was considered harmful, and
the perpetrator was told to cut it out.

Don't discourage recreational programming -- learning is what
a university is all about.

--tom
--
Tom Christiansen		tchrist@convex.com	convex!tchrist
"With a kernel dive, all things are possible, but it sure makes it hard
 to look at yourself in the mirror the next morning."  -me