Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!umd5!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.wizards
Subject: Re: Is rlogin protocol documented anywhere?
Message-ID: <11548@mimsy.UUCP>
Date: 18 May 88 03:46:54 GMT
References: <3274@phri.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 31

In article <3274@phri.UUCP> roy@phri.UUCP (Roy Smith) writes:
>... can't seem to find where the rlogin protocol is documented.

Document? *snicker*

Just kidding.  Actually, it is not documented anywhere save by the source,
as far as I can tell.

>Why does rlogin.h have
>#ifndef TIOCPKT_WINDOW
>#define TIOCPKT_WINDOW 0x80
>#endif
>in it?  Why supply a default for TIOCPKT_WINDOW but not TIOCPKT_NOSTOP and
>TIOCPKT_DOSTOP?

This makes the same source compile on SunOS [23].*, where TIOCKPT_WINDOW is
not defined, but all the others are.

>And, just what do these later two mean?

NOSTOP means ^S/^Q are not being used as flow control, so they should
be passed through rather than acting as local flow control.  DOSTOP
is the inverse.

>Ditto for TIOCPKT_FLUSHWRITE; it's not clear under what circumstances this is
>sent.

Whenever the user types ^O or (if not NOFLSH) ^C, does something else
that makes the tty driver attempt to flush pending output.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris