From owner-freebsd-hackers  Fri Jun 27 10:32:17 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id KAA03301
          for hackers-outgoing; Fri, 27 Jun 1997 10:32:17 -0700 (PDT)
Received: from dragon.cmnsens.zoom.com (dragon.cmnsens.zoom.com [207.33.155.10])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA03294
          for <freebsd-hackers@freebsd.org>; Fri, 27 Jun 1997 10:32:09 -0700 (PDT)
Received: from cmnsens.cmnsens.zoom.com (cmnsens.cmnsens.zoom.com [207.33.155.2])
	by dragon.cmnsens.zoom.com (8.8.6/8.8.6) with SMTP id KAA00654;
	Fri, 27 Jun 1997 10:31:51 -0700 (PDT)
Message-Id: <199706271731.KAA00654@dragon.cmnsens.zoom.com>
From: "Mike Burgett" <mburgett@cmnsens.zoom.com>
To: "Bruce Evans" <bde@zeta.org.au>
Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>
Date: Fri, 27 Jun 97 10:31:53 -0700
Reply-To: "Mike Burgett" <mburgett@cmnsens.zoom.com>
Priority: Normal
X-Mailer: PMMail 1.92 For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: com console, and h/w flow control...
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Sat, 28 Jun 1997 03:20:24 +1000, Bruce Evans wrote:

>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...)

terminal() {
        ci=$1; shift
        co=$1; shift

        modem $ci $co $*
        for i in $*
        do
                comcontrol /dev/tty$ci$i dtrwait 0
                stty </dev/ttyi$ci$i crtscts 115200
                stty </dev/cuai$co$i crtscts 115200
        done
}

[ .... ]

# Initialize assorted 8250-16550 (sio) ports.
modem    d a    1
terminal d a  0

>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 :-).

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...

Thanks,
Mike