Path: utzoo!attcan!uunet!sco!seanf From: seanf@sco.COM (Sean Fagan) Newsgroups: comp.unix.sysv386 Subject: Re: SCO-Unix - booting to single user mode and then crash Message-ID: <8305@scolex.sco.COM> Date: 19 Oct 90 23:04:41 GMT References: <9010171604.AA24053@decpa.pa.dec.com> <7965@star.cs.vu.nl> Sender: news@sco.COM Reply-To: seanf (Sean Fagan) Organization: The Santa Cruz Operation, Inc. Lines: 27 In article <7965@star.cs.vu.nl> rvdp@cs.vu.nl (=Ronald van der Pol) writes: >paine@fungus.dec.com (Willy Paine) writes: >>Then it freezes or crashs and I can not press . Notice there >>is no real linefeed between "startup," and "(or give" >I have had the same problem. You can type in your root password >and then (!!!). Control-Enter is newline, the same as Control-J. (I just sent a message to Willy, explaining this.) The problem was probably caused by being in a non-cooked mode on syscon when the system went down. For example, I normally run ksh, even in root, and in emacs mode, so my console is normally in raw mode. One day, I went to shut down, did an 'init 1', and everything was happy. *However*: the init command returned, ksh went back to raw mdoe, and I waited for the system to reboot. When I came up, I got a shell (well, a password prompt first) that was in raw mode. I logged in, set things back to normal, did an 'init 1' again, and that cleared it up. As a result, I now do an 'exec sh' before I shut down that way, and I haven't had any problems. -- -----------------+ Sean Eric Fagan | "*Never* knock on Death's door: ring the bell and seanf@sco.COM | run away! Death hates that!" uunet!sco!seanf | -- Dr. Mike Stratford (Matt Frewer, "Doctor, Doctor") (408) 458-1422 | Any opinions expressed are my own, not my employers'.