Subject: Re: tty layer bogons from the depths of the abyss
To: Erik E. Fair <fair@clock.org>
From: John Nemeth <jnemeth@cue.bc.ca>
List: tech-kern
Date: 03/20/1998 13:09:50
On Mar 20, 12:51pm, "Perry E. Metzger" wrote:
} "Erik E. Fair" writes:
} > There is actually one other case to think about supporting (it may not be
} > important these days): dual-use modems, dial-in and dial-out. Something
} > like uugetty (or its equivalents) can help, or you can play the two tty
} > locking game used in SunOS (two /dev/ttyfoo's, one device, one for getty,
} > one for cua0 (or equiv), mutually exclusive use locking in the kernel).
} 
} I am happiest with the SunOS /dev/ttyN vs /dev/cuaN game -- it works
} *VERY* well, and it is the one thing from SunOS I miss in NetBSD.

     I second this.  It's really annoying to have to shut off the
getty and set clocal on a port everytime I want to dialout or talk to
a modem using cu.  I know could do a kludge, i.e. install mgetty, but
I shouldn't have to do things like that.  It should work properly out
of the box.  Once upon a time, cgd produced a patch to implement this
functionality, which I still have somewhere.  It would be nice if that
patch could be redone for the current com.c.  The SunOS method was
really nice.  Attach a getty to one port, do whatever you want with
the other, and it all just worked (the way things should be).

}-- End of excerpt from "Perry E. Metzger"