Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mcvax!ukc!hrc63!miduet!misoft!jgh
From: jgh@gec-mi-at.co.uk (Jeremy Harris)
Newsgroups: comp.os.minix
Subject: Re: ns32016 port + misc.
Message-ID: <602@gec-mi-at.co.uk>
Date: Fri, 19-Jun-87 05:04:45 EDT
Article-I.D.: gec-mi-a.602
Posted: Fri Jun 19 05:04:45 1987
Date-Received: Fri, 26-Jun-87 03:28:37 EDT
References: <549@ubu.warwick.UUCP>
Sender: news@gec-mi-at.co.uk
Reply-To: jgh@gec-mi-at.co.uk (Jeremy Harris)
Organization: Marconi Instruments Ltd., St. Albans, UK
Lines: 26
Keywords: stty
Summary: V7 & Minix stty not broken

In article <549@ubu.warwick.UUCP> ham@warwick.UUCP (Hot Air Machine Project) writes:
>....And the bugfix.  stty.c performs its ioctl()s on file descriptor 0 (stdin)
>this means that to change the settings on terminals other than the one you
>are using, you have to type e.g: stty -echo < /dev/tty1
>which is rather counter-intuitive, not to mention different to UNIX.  The
>
>Tim Bissell
>donald@warwick.UUCP      or   {..seismo!}mcvax!ukc!warwick!donald

From memory, this is what V7 stty does. Where's it gointa put its output,
eh? Stdout. What is there left to ioctl on? Choice of stdin or stderr.
Stdin wins. Yes, one's mind glitched when first meeting it, but if you're
stty-ing someone else's terminal then you're probably heading for 'local guru'
status anyway :-)  I didn't mind it.

The horror started (for me, I think I remember) with Sys III. Some bright
spark had decided that they didn't like the above behavior, and adjusted
stty to tweak it's stdout (just like you want)  *and put its output on stderr*.
Now, I expect error messages to come to stderr, and normal operating output
to come to stdout. I hated it.

Disclaimer: It was some time ago, and they weren't AT&T systems. Sorry if I
	just annoyed anybody.

(Not my company's opinions)
Jeremy Harris	jgh@gec-mi-at.co.uk	...!mcvax!ukc!hrc63!miduet!jgh