Path: utzoo!utgpu!watmath!iuvax!cica!tut.cis.ohio-state.edu!oz.cis.ohio-state.edu!jgreely From: jgreely@oz.cis.ohio-state.edu (J Greely) Newsgroups: comp.sys.next Subject: Re: Diskless NeXT's?? Message-ID: Date: 8 Aug 89 22:23:17 GMT References: <1989Aug8.192101.3060@ee.rochester.edu> Reply-To: J Greely Distribution: na Organization: Ohio State University Computer and Information Science Lines: 25 In-reply-to: jal@ee.rochester.edu's message of 8 Aug 89 19:21:01 GMT In article <1989Aug8.192101.3060@ee.rochester.edu> jal@ee.rochester.edu (John Lefor) writes: [networked NeXTs, running diskless] >It occurs to us that in this environment, a student could insert >their own optical disk and defeat some of the controls we have >instituted. Under 0.9, that is true. There's not much you can do to prevent these problems right now. >Thus the question - is it possible to defeat the optical disk for >purposes of system boot without completely disabling the optical? Not yet. Under 1.0, you will be able to prevent users from mucking about in the ROM monitor, which, in the absence of unforseen problems, should suffice to make ODs safe to use on networked machines. The changes were done a while ago, and I haven't heard of any problems with them. Of course, I haven't had a chance to beat on it myself, but that should come soon (my latest release quote, as of about an hour ago, is "early September"). "Fixed in 1.0" -=- J Greely (jgreely@cis.ohio-state.edu; osu-cis!jgreely)