ccoombs@pilot.njin.net (Cliff Coombs) (05/29/90)
I Broke it.... :) In attempting to set up a Next on our campus net, I managed to lock it up. Booting in text mode it halts at: Starting network daemons: inetd The only things I changed before this were the YP domain (I think this is 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) Thanks in advance! Cliff -- Cliff Coombs ccoombs@pilot.njin.net Campus Network Coordinator ccoombs@turbo.kean.edu Kean College of New Jersey, Union.NJ.USA.Earth Fax (201) 355-5143 Disclaimer: I plead the Fifth. Voice (201) 527-2729
rogerj@batcomputer.tn.cornell.edu (Roger Jagoda) (05/30/90)
In article <May.29.09.01.07.1990.14227@pilot.njin.net> 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! --
jconti@barnard.usc.edu (John Conti) (05/31/90)
>In attempting to set up a Next on our campus net, I managed to >lock it up. Booting in text mode it halts at: > Starting network daemons: inetd This problem has been with several releases of the software. If you try to set the inet address manually for ifconfig (INET=xxx.xxx.xxx.xxx in /etc/hostconfig) the box will hang at inetd if the wire is not plugged in. If you set it to -AUTOMATIC- you're fine, but that's probably not what you want. NeXT doesn't seem to care because we should all be using netinfo :-) Oh, if we only had that source code.... ,John John Conti { jconti@usc.edu | jconti@xenon.usc.edu (NeXT mail) } Computing Services, University of Southern California, (213)743-2957