Newsgroups: comp.unix.ultrix
Path: utzoo!utgpu!watserv1!watcgl!idallen
From: idallen@watcgl.waterloo.edu (Ian! D. Allen [CGL])
Subject: Re: Ultrix 3.1C uucp will not dial a LAT terminal modem
Message-ID: <1990Sep19.012424.8586@watcgl.waterloo.edu>
Organization: University of Waterloo
References: <1990Sep17.063335.17243@watcgl.waterloo.edu> <15412@shlump.nac.dec.com>
Date: Wed, 19 Sep 90 01:24:24 GMT
Lines: 23

In article <15412@shlump.nac.dec.com> thomas@mipsbx.lkg.dec.com (Matt Thomas) writes:
>LAT will connect during the open sequence.  One the open finishes, either
>you are connected (0 is returned) or it failed.  The line may or may not
>have carrier but LAT doesn't (can't) know that.  I could support TIOCWONLINE
>but it would always return success and would never sleep.  Would that help
>any?

No, TIOCWONLINE should not be supported if it doesn't work.  *You* don't
have to do anything -- the fellow who added stuff to UUCP and didn't
check his system calls has to clean up his act.

>The LAT protocol does not contain any support for manipulation
>or control of modem signals beyond the act of connecting to the port.

I wish my sales reps had known that before I bought three DS200/MC
terminal servers and tried for days to make UUCP work on them.  UUCP
and TIP have all this wonderful code for setting baud rates and using
serial lines, and it's all useless on Ultrix LAT ports.  I have a pair
of DS5400's sitting here and I have to put my outgoing TIP and UUCP
line on a MVII!
-- 
-IAN! (Ian! D. Allen) idallen@watcgl.uwaterloo.ca idallen@watcgl.waterloo.edu
 [129.97.128.64]  Computer Graphics Lab/University of Waterloo/Ontario/Canada