Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site fisher.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!princeton!astrovax!fisher!djl
From: djl@fisher.UUCP (Dan Levin)
Newsgroups: net.bugs
Subject: Intel XENIX release 3.0 manual lies...
Message-ID: <1351@fisher.UUCP>
Date: Mon, 9-Dec-85 01:23:27 EST
Article-I.D.: fisher.1351
Posted: Mon Dec  9 01:23:27 1985
Date-Received: Tue, 10-Dec-85 05:01:50 EST
Distribution: net
Organization: Princeton University.Mathematics
Lines: 25
Keywords: Kernel Internals, tty driver, broken

I don't mean to continually pick on Intel, but this one really got
me steamed up.  I spent my Saturday bringing up a new line
discipline under Intel XENIX 3.0 (on a 310/286 if anyone cares),
and tonight realized that my problems were due to a faulty manual
entry.

Well, perhaps I am too kind.  A lying manual.  In particular, the
section of the XENIX device driver guide which discusses the
tty driver and line discipline routines.

ttopen (and thus all LD open routines) take ttopen(tp, dev), not
ttopen(dev, tp) like the man (and most other UN*X's) says.

ttinput takes ttinput(tp, c, flag), not ttinput(c, tp).  The flag
is totally undocumented, and seems to be 0 under normal situations.

These answers were ferreted(sp?) out using adb, and are not warranted
in any way.  I find it hard to believe that a for-profit company
could publish something so bad, for an operating system that takes
pride in its flexibility.
-- 
			***dan

{allegra,astrovax,princeton}!fisher!djl
The misplaced (That car sure is rusty!) Californian