From owner-freebsd-hackers  Fri Oct 11 21:37:35 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id VAA24618
          for hackers-outgoing; Fri, 11 Oct 1996 21:37:35 -0700 (PDT)
Received: from w2xo.pgh.pa.us (w2xo.pgh.pa.us [206.210.70.5])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA24609
          for <freebsd-hackers@FreeBSD.ORG>; Fri, 11 Oct 1996 21:37:31 -0700 (PDT)
Received: (from durham@localhost) by w2xo.pgh.pa.us (8.6.12/8.6.9) id AAA23268 for freebsd-hackers@FreeBSD.ORG; Sat, 12 Oct 1996 00:38:58 -0400
Message-ID: <XFMail.961012003857.durham@w2xo.pgh.pa.us>
X-Mailer: XFMail 0.5-alpha [p0] on FreeBSD
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
In-Reply-To: <199610110807.KAA04744@uriah.heep.sax.de>
Date: Sat, 12 Oct 1996 00:35:43 -0400 (EDT)
Organization: Very little
From: Jim Durham <durham@w2xo.pgh.pa.us>
To: (FreeBSD hackers) <freebsd-hackers@FreeBSD.ORG>
Subject: Re: Serial console for FreeBSD?
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


On 14:07:04 J Wunsch opined:
>>As Jordan K. Hubbard wrote:
>
>> > disasters.  I'd particularly like to be able to control the
>> machine in single > user mode after a failed fsck.  Does FreeBSD
>> support this level of control?
>
>> Yep!  See /sys/i386/conf/LINT where COMCONSOLE is defined.  On
>> ftp.cdrom.com, in fact, the console is watched by yet another machine
>> which can also reset it under remote control.
>
>Better yet, patch your bootblocks to force a serial console.  The
>bootblocks already allow you to toggle between the serial and graphics
>console with -h; all you need is changing the default.  This gives you
>the added feature that you can boot an alternate kernel even with a
>serial console.

Does the console have to be on sio0 ? How does one
specify which com port if not ?

-Jim