Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!uwm.edu!ux1.cso.uiuc.edu!mp.cs.niu.edu!bennett From: bennett@mp.cs.niu.edu (Scott Bennett) Newsgroups: comp.sys.next Subject: Re: Help! Cube boots only to single user mode... Summary: SysVish mistreatment of MACH single-user mode Message-ID: <1991Feb1.231626.16181@mp.cs.niu.edu> Date: 1 Feb 91 23:16:26 GMT References: <1991Feb1.154516.5275@sctc.com> Organization: Northern Illinois University Lines: 83 In article <1991Feb1.154516.5275@sctc.com> herndon@sctc.com (William R. Herndon) writes: > > About two weeks ago I purchased a Maxtor XT8702S disk drive and > [text deleted --SJB] > entitled "MACH Operating System", in which a shell was running, > and leaving me in single user mode. Fortunately, I know a few things > about UNIX and forced the machine to continue the boot sequence by > going to multi-user mode by issuing an "init 2" command. Well, when That is SysV usage. I wouldn't have dared guess what it would do to a BSD-derived system. Thanks for the info. The correct way to change to multiuser mode in a BSD-derived UNIX is to exit the single-user shell (i.e. hit ^D). The system will then process /etc/rc. > the machine finished starting the system services, I was left with > a login panel and a cursor that the window manager had no control > over. In fact, the keyboard was locked also. Well, I can't explain this, but I'm certainly not surprised to see weird things happening after you started up a second copy of init. > > I then tried to boot again, this time interrupting the boot sequence > in the ROM monitor. I executed: > > b sd(0,0,0) > > which left me in single user mode again, executed an "init 2" to start Again, this is *not* the right thing to do. However, when you have the ROM monitor prompt, check the system parameters ("p" if I remember right.) A default boot command like b sd sdmach -s is what you normally would enter if you *wanted* to start up in single- user mode. If the ROM monitor's current default boot parameters are set such that they result in a command equivalent to the above, then you'll need to change those values to give you what you want. The "-s" is the part that results in single-user mode as opposed to the normal startup into multiuser mode. > multi-user boot, and viola', I'm up and running, with control of the > cursor and keyboard, I might add. > > But what is the problem? I think that it may have to do with a non- > existant network, but I am just guessing. > > FLAMES ON: > > [flame deleted, but my sympathies left in --SJB] > > FLAMES OFF: > > I've just about had it the total lack of support from NeXT. Will > somebody please help me. > > Thanks in advance. > > > > - Max > >------------------------------------------------------------------------------- >William R. Herndon >Secure Computing Technology Corp. > Once you've had black, >herndon@sctc.com you'll never go back...NeXT >(612) 482-7431 > > Scott Bennett, Comm. ASMELG, CFIAG Systems Programming Northern Illinois University DeKalb, Illinois 60115 ********************************************************************** * Internet: bennett@cs.niu.edu * * BITNET: A01SJB1@NIU * *--------------------------------------------------------------------* * "WAR is the HEALTH of the STATE" --Albert Jay Nock (I think:-) * **********************************************************************