Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA7392 ; Fri, 22 Jan 93 11:44:07 EST Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!olivea!uunet!pipex!demon!crucible!mtrim From: mtrim@crucible.demon.co.uk (Mike Trim) Newsgroups: comp.unix.bsd Subject: Re: 386BSD INIT Problem? Message-ID: <C16913.Kn@crucible.demon.co.uk> Date: 20 Jan 93 21:29:25 GMT References: <C15t62.Du8@ns1.nodak.edu> Sender: news@crucible.demon.co.uk (Usenet News Administrator) Organization: HOME Lines: 18 X-Newsreader: Tin 1.1 PL4 tinguely@plains.NoDak.edu (Mark Tinguely) writes: : 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). Thankyou to all respondees for taking the time. For the benefit of any interested readers the simplest suggestion (and the one I used) was to rename the old init file before installing the new. After reboot the old init can be safely deleted. I've noted your comments about /dev/vga. Installing `X' is next. Mike Trim -- mtrim@crucible.demon.co.uk