I have for quite some time had all my serial drivers paying special
attention when they were opened with the O_TRUNC flag in which case I
did a ttstart in order to handle XOFFs without XONs (e.g. line noise can
make this happen) and bugs in general handshaking, leaving ttys in
stopped state.  Only just recently I rediscovered the TIOC{START,STOP}
ioctls which I had forgot all about since the first time I read a
tty(4) man page.  Great, I thought, what user-level commands
implements this interface on ttys then?  I grepped the whole tree only
to find that no program did this.  So I implemented them in stty(1).
The only thing that bothers me is that stty deals with modes and not
events.  But in order to keep related things close to each other I put
them in stty anyway.

What I wonder is:

+	Is there any interest at all having the extra TIOC* ioctls of
	tty(4) easily done by a system-supplied user-level command?

+	Should that command by stty(1)?  Creeping featuritis...

+	Today, I only implemented the START/STOP ioctls.  I call the
	stty options "ostart" and "ostop" respectively.  The mnemonic
	`o' stands for "output".  If stty is the place for this
	functionality, are these names well chosen?

+	Does anybody want my small stty patch?

Niklas

Niklas Hallqvist	Phone: +46-(0)31-40 75 00
Applitron Datasystem	Fax:   +46-(0)31-83 39 50
Molndalsvagen 95	Email: niklas@appli.se
S-412 63  GOTEBORG	WWW:   Here
Sweden