Path: utzoo!attcan!uunet!mcvax!hp4nl!philapd!ssp15!jos
From: jos@idca.tds.PHILIPS.nl (Jos Vos)
Newsgroups: comp.dcom.lans
Subject: Re: Problem with running "rn" over Starlan
Keywords: starlan, rn
Message-ID: <742@ssp15.idca.tds.philips.nl>
Date: 28 Dec 88 07:05:21 GMT
References: <518@cfctech.UUCP>
Organization: Philips Telecommunication and Data Systems, The Netherlands
Lines: 20

In article <518@cfctech.UUCP> alexb@cfctech.UUCP (Alex Beylin) writes:

>One of the things that we could not get to work over the
>net is "rn".  It dies as soon as it tries to go in the 
>cbreak mode.  Now, that is fully understandable as rn
>expects a "tty" port and starlan-10 is talking to it over
>some "slan" device rn knows nothing about.

We did have the same problems using rn with a V.3 streams terminal.
Is that the case at your site?

The V.3 read(2) returns -1 when the O_NDELAY flag is set on a streams tty
and there is no data, i.s.o. 0 what is done with "normal" tty's.
I did make 3 very minor changes to the code of rn to let it work properly
on all devices. 
If you are interested, I can find them in my "history".

-- 
-- ######   Jos Vos   ######   Internet   jos@idca.tds.philips.nl   ######
-- ######             ######   UUCP         ...!mcvax!philapd!jos   ######