From owner-freebsd-hackers  Fri Jun 27 10:20:58 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id KAA02687
          for hackers-outgoing; Fri, 27 Jun 1997 10:20:58 -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 KAA02678
          for <freebsd-hackers@FreeBSD.ORG>; Fri, 27 Jun 1997 10:20:54 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id DAA01015; Sat, 28 Jun 1997 03:20:24 +1000
Date: Sat, 28 Jun 1997 03:20:24 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199706271720.DAA01015@godzilla.zeta.org.au>
To: freebsd-hackers@FreeBSD.ORG, mburgett@cmnsens.zoom.com
Subject: Re: com console, and h/w flow control...
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>My various attempts to convince it to use h/w flow control have been 
>unsuccessful, as far as /dev/ttyd0 goes, though it looks like the init device, 
>/dev/ttyid0, is set correctly:
>
># stty -f /dev/ttyd0
>speed 115200 baud;
>lflags: echoe echoke echoctl
>cflags: cs8 -parenb clocal
>erase   status
>^H      ^T
># stty -f /dev/ttyid0
>speed 115200 baud;
>lflags: echoe echoke echoctl
>oflags: -oxtabs
>cflags: cs8 -parenb clocal crtscts
>#

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.

crtscts is not the default, and clocal _is_ the default, to prevent
processes endless waits for console output.  clocal is locked on.
-current also locks the speed.  Perhaps crtscts should be locked
(off) too.  Then stty'ing /dev/ttyd0 would be harder :-).

Bruce