Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!uwm.edu!rpi!batcomputer!rogerj From: rogerj@batcomputer.tn.cornell.edu (Roger Jagoda) Newsgroups: comp.sys.next Subject: Re: Next locks up at Starting network deamons Keywords: inetd Message-ID: <10333@batcomputer.tn.cornell.edu> Date: 30 May 90 00:29:54 GMT References: Reply-To: rogerj@tcgould.tn.cornell.edu (Roger Jagoda) Followup-To: comp.sys.next Distribution: na Organization: Cornell Theory Center, Cornell University, Ithaca NY Lines: 36 In article ccoombs@pilot.njin.net (Cliff Coombs) writes: > >I Broke it.... :) Relax, it can be fixed! > > Starting network daemons: inetd > >the problem) and the Router address. Unfortunately, our Next has only a >40meg drive and this was our only boot disk. (If anyone wants to make >a backup boot disk for us I'll send them a blank) > No need! Use the ROM Monitor "bod -s" command for coming up as stand-alone and the interface won't be a problem because it won't get configured! Then undo what you did (methinks the router address is the culprit as inetd probably went out to start up the tcp-ip routed service and bombed) and issue "exit" (which will start the multi-user boot-up...you'll know if you get it right if you get it right if you can get past the inetd part....) If you bomb, use "cmd-cmd-~" then "halt" to get back to ROM Monitor and start again! See? >Thanks in advance! No sweat! --Roger Jagoda --Cornell University --FQOJ@CORNELLA.CIT.CORNELL.EDU -- ------------------------------------------------------------------------------ Roger Jagoda -- My employers don't even like paying Cornell University me, let alone accept responsibility fqoj@cornella.cit.cornell.edu for anything I say or do! --