Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site hadron.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!bellcore!decvax!genrad!panda!talcott!harvard!seismo!trwatf!rlgvax!prcrs!hadron!jsdy
From: jsdy@hadron.UUCP (Joseph S. D. Yao)
Newsgroups: net.unix-wizards
Subject: Re: Stty/Gtty on System III and PC/IX?
Message-ID: <161@hadron.UUCP>
Date: Thu, 11-Apr-85 14:01:27 EST
Article-I.D.: hadron.161
Posted: Thu Apr 11 14:01:27 1985
Date-Received: Thu, 18-Apr-85 03:21:47 EST
References: <1483@emory.UUCP>
Distribution: net
Organization: Hadron, Inc., Fairfax, VA
Lines: 25

> I am trying to understand the formal connection between
> stty/gtty and system III.  ...
> sgtty.h in /usr/include with a sgttyb structure and
> definitions for the TIOCs. When I try the TIOCGETP it just
> fails. There is also a gtty.o in /usr/lib/lib2.a. I tried
> resolving out of here and find that it needs externals that
> are not in any of the libraries I find.

I don't find any mention of stty/gtty in S-III docs, either, and
am a bit puzzled why sgtty.h is even in your /usr/include.  As
you say, maybe S-III had it as an "invisible compatibility."
Anyway, the relevant ioctl's are in your tty(4) or termio(7) or
whatever version of the manual ... For S-III, they are TCGETA
and TCSETA.  The structure used is almost, but not completely,
unlike the sgtty structure.

If you only have (*shudder*) constants in your code (as 0174130),
you'll have to publish these, plus which system you guess the bits
are for, and you'll get upwards of a half dozen different answers
as to what the stty bits could/did/used to/do mean.

Do  n o t  use lib2.a in your code.  That's the subroutine library
for standalone programs!

	Joe Yao		hadron!jsdy@seismo.{ARPA,UUCP}