From owner-freebsd-hackers  Fri Jun 27 10:56:15 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id KAA04350
          for hackers-outgoing; Fri, 27 Jun 1997 10:56:15 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA04342
          for <freebsd-hackers@freebsd.org>; Fri, 27 Jun 1997 10:56:10 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id DAA01701; Sat, 28 Jun 1997 03:52:45 +1000
Date: Sat, 28 Jun 1997 03:52:45 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199706271752.DAA01701@godzilla.zeta.org.au>
To: bde@zeta.org.au, mburgett@cmnsens.zoom.com
Subject: Re: com console, and h/w flow control...
Cc: freebsd-hackers@freebsd.org
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>>Apparently /dev/ttyid0 never gets used because /dev/ttyd0 never gets
>>reopened (init opens it before executing /etc/rc, and syslogd holds
>>it open).  The state is easy to change by stty'ing /dev/ttyd0 in
>>/etc/rc.serial or /etc/rc.local.
>
>I've done that (at least I think I have... rc.serial is a strange beast to 
>me...)
>...
># Initialize assorted 8250-16550 (sio) ports.
>modem    d a    1
>terminal d a  0

rc.serial normally only doesn't touch the normal ports, and you don't
seem to have changed this.

>Seems hard enough to me already :) ... I keep a terminal emulater window open 
>on another computer on the console at all times anyway, so I'd really like to 
>be able to get around the flow control issue...

You can stty it from any root login (stty crtscts </dev/ttyd0) or put this
at the end of /etc/rc.serial or in /etc/rc.local.  rc.local is best unless
there is enough early console i/o to need flow control.

Bruce