Path: utzoo!utgpu!attcan!uunet!wuarchive!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!mailrus!iuvax!purdue!mentor.cc.purdue.edu!pur-ee!pur-phy!tippy!emerrill From: emerrill@tippy.uucp Newsgroups: comp.sys.apple Subject: Re: mouce security. Message-ID: <145300001@tippy> Date: 30 Sep 89 16:56:00 GMT Lines: 30 Nf-ID: #R:<8909291639.aa08421@SMOKE.BRL.MI:-34:tippy:145300001:000:1407 Nf-From: tippy.uucp!emerrill Sep 30 11:56:00 1989 /* Written 10:07 pm Sep 29, 1989 by jac@paul.rutgers.edu in tippy:apple */ >gwyn@smoke.BRL.MIL (Doug Gwyn) >> Sounds to me like you're trying to solve the wrong problem. >> Why not tell the students that further theft will not be >> tolerated, and the stolen equipment will not be replaced >> even though all students will still held responsible for >> completing the assignments. You might find that the >> student body will police themselves under such circumstances. >This is nonsense. If I can't complete an assignment because SOMEBODY >who I don't even KNOW stole a mouse, how can I > (1) get the mouse back? > (2) see that it doesn't happen again? >You might try making students swap an student ID for a mouse. This >will tend to insure that you get them back in one piece. I totally agree! The former solution is analogous to 1st grade when the teacher made all the students put their heads on their desks because one student did something wrong. _________________________________________________________ | | | Eric Merrill tippy!emerrill@newton.physics.purdue.edu | | | | Disclaimer: | | If you think I'm serious, that's your problem! | |_________________________________________________________|