Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site hou3c.UUCP
Path: utzoo!linus!decvax!genrad!grkermit!masscomp!bonnie!clyde!burl!hou3c!ka
From: ka@hou3c.UUCP
Newsgroups: net.bugs,net.unix
Subject: Re: Why 4BSD 'stty' uses stdout instead of stdin
Message-ID: <753@hou3c.UUCP>
Date: Wed, 31-Dec-69 18:59:59 EDT
Article-I.D.: hou3c.753
Posted: Wed Dec 31 18:59:59 1969
Date-Received: Sun, 19-Aug-84 11:17:38 EDT
References: <895@trwrb.UUCP> <1228@dalcs.UUCP> <747@dual.UUCP> <46@rlgvax.UUCP> <318@wucs.UUCP> <5024@utcsrgv.UUCP> <2540@mit-eddie.UUCP> <2993@utah-cs.UUCP>
Organization: Bell Labs, Holmdel, NJ
Lines: 8

> On 4BSD (and V7?) a tty must be opened for writing in order for a
> process to set the tty's modes.  This does make a certain amount of
> sense; if you don't want someone to write on your tty, then you usually
> don't want them to set your tty's mode either.

It certainly does not make sense to me.  Why would you give somebody
read permission on your tty but not write permission?
				Kenneth Almquist