} On Wed, 4 May 1994 email@example.com.EDU.AU wrote:
} > If we start to get worried about what sys admins are going to be doing and
} > logging every command then I think the learning experience will be lessened.
} Yes, but logging is also a good way to see what went wrong. If everytime
} somthing bad happen the solution is "thats ok, we'll just reinstall it", I
} don't think there is much learning going on. If on the otherhad the
} sequence of events can be studied, somthing may be learned.
} This is assuming that logging is for repairing problems, not giving fault.
True. It comes down to trust and responsible use again.
} Once blaim is dished out, the log will be useless.
Not so. Fingers, once pointed, are then unpointed. A finger should not
need to be pointed with great frequency, and (especially on this system),
no-one should really have to worry about what they do. Repeat: this is a
learning system. If you break it, fine. If you break it irreparably, then
it'd be nice to see how you did it so that others can avoid that in
future. If you deliberately set out to do damage, then you're a social
If you want to do bizarre network stuff, then we should be
able to arrange a physically disconnected local network for "testing
purposes." Ethernet is cheap.
} 'A monkey throws,
} A spinning bone,
} A silent spaceship'
'A flying bone curves,
Spinning in freckled blackness,
Does an ape wonder?'