From owner-freebsd-current Wed Oct 9 01:46:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA05687 for current-outgoing; Wed, 9 Oct 1996 01:46:54 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA05652 for ; Wed, 9 Oct 1996 01:46:27 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id SAA03927; Wed, 9 Oct 1996 18:42:18 +1000 Date: Wed, 9 Oct 1996 18:42:18 +1000 From: Bruce Evans Message-Id: <199610090842.SAA03927@godzilla.zeta.org.au> To: hoek@freenet.hamilton.on.ca, msmith@atrad.adelaide.edu.au Subject: Re: 961006-SNAP comments Cc: freebsd-current@FreeBSD.org, henrich@crh.cl.msu.edu Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> (Incidentally, removing the syscons driver causes a sig12, page fault >> while in kernel mode when one continues booting)). Oops, switching from sc0/pcvt to a serial console is currently broken. When the highest priority console device is disabled (or a higher priority one is disabled) the next highest priority one is supposed to take over. If all console devices are disabled, you are supposed to get what you asked for - no console device. Only a few devices support consoles (this is a bug). Their priorities are: syscons pcvt sio0 >You can blame(?) Bruce for that; he insisted on being able to have both >syscons and pcvt in the same kernel so it had to be possible to disable >them. I don't like it for exactly the reason you've noted. It should be possible to disable any driver. It is possible to disable any isa driver. Bruce