Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA7325 ; Mon, 18 Jan 93 10:51:55 EST Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!uunet!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!usenet.coe.montana.edu!news.u.washington.edu!ns1.nodak.edu!plains.NoDak.edu!tinguely From: tinguely@plains.NoDak.edu (Mark Tinguely) Subject: Re: 386BSD INIT Problem? Sender: usenet@ns1.nodak.edu (News login) Message-ID: <C15t62.Du8@ns1.nodak.edu> Date: Wed, 20 Jan 1993 15:46:50 GMT References: <C12nrG.19p@crucible.demon.co.uk> Nntp-Posting-Host: plains.nodak.edu Organization: North Dakota State University Lines: 22 In article <C12nrG.19p@crucible.demon.co.uk> mtrim@crucible.demon.co.uk (Mike Trim) writes: >I've installed the 386BSD system together with the patch kit (except 47) >as seems to be recommended. ... All seems to be >working except the `init' program rebuilt after installing the patch kit. >I'm currently using the distribution `init'. I am no fan of the distributed init -- it temporarilly goes multi-user or single-user when you reboot and sometimes hard to get into single-user mode. I am biased since -- I run my own that was posted in 0.0 days. Any way I mentioned this before -- no matter what init you run, when installing the X patches to the kernel, change "/dev/console" to "/dev/vga" in init.c (or else you get garbage on the screen when you reboot, and will not be able to go single user). As I said before, I think we should really send a flag and have this done automatically. I have seen your problem before, what you need is a clean fsck. put the new /sbin/init into place. shutdown, boot from floppy, fsck manually, then reboot. If you made the changes above and you can get some cooperation from the init, you could do this in single user mode. Also be sure that the getty now runs on /dev/vga instead of /dev/console AND before you reboot /dev/vga exists (mknod /dev/vga c 12 0).