From owner-freebsd-current  Sun Feb  2 07:56:05 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id HAA23274
          for current-outgoing; Sun, 2 Feb 1997 07:56:05 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA23247
          for <freebsd-current@FreeBSD.org>; Sun, 2 Feb 1997 07:56:00 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id CAA25130; Mon, 3 Feb 1997 02:55:42 +1100
Date: Mon, 3 Feb 1997 02:55:42 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702021555.CAA25130@godzilla.zeta.org.au>
To: freebsd-current@FreeBSD.org, j@uriah.heep.sax.de
Subject: Re: getty patches
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>> BTW, I'm happy to implement this if someone comes up with the RI
>> detection in open(). An O_RI on open, perhaps?
>
>I rather think it should be an ioctl specific to those drivers that
>implement it.  Sure, it only makes sense if the state of this `enable
>RI pseudo-carrier' bit is retained across open/close, so you can open
>the port once with O_NONBLOCK set, issue the ioctl, close the port,
>and reopen it without the O_NONBLOCK.

There's not much experience with using RI.  It should be in the drivers
so that new software can play with it.  It should be possible to select
on modem status changes, and the SIGIO support should be better (I think
you can now get a SIGIO when carrier rises, but only for controlling
terminals).

Side effects of open() are probably more of a problem.  First-opens
always turn on RTS and DTR.

Bruce