*BSD News Article 6810


Return to BSD News archive

Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!uwm.edu!rpi!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] help: init FATAL error
Sender: usenet@ns1.nodak.edu (News login)
Message-ID: <BwH7p6.9EH@ns1.nodak.edu>
Date: Wed, 21 Oct 1992 14:46:18 GMT
References: <1992Oct20.051614.24998@hpcvmcdj.cv.hp.com> <1992Oct21.041117.3709@hpcvmcdj.cv.hp.com>
Nntp-Posting-Host: plains.nodak.edu
Organization: North Dakota State University
Lines: 18

In article <1992Oct21.041117.3709@hpcvmcdj.cv.hp.com> carlj@hpcvmcdj.cv.hp.com (Carl Johnson) writes:
>Yesterday I asked about a boot problem where I was getting a message:
>
>:    init FATAL error: console: Interrupted system call
>
>Anyways I found the problem tonight.  ...

 this is really unrelated, but important to those running X. I found using
 my init, and is also present in the shipped/patched init with X that
 "dev/console" should now be changed to "dev/vga" else single user mode
 (in case fsck fails) will give garbage. This is also important with the
 shipped init when boot/rebooting it temporarily goes into single user mode.

 I believe those not running X still should use the "/dev/console" in their
 init. Yes, the best thing to do is do this automatically (maybe send an
 option to init when ever the X server pccons.c code is present in the kernel).

--mark.