Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!decvax!crltrx!treese
From: treese@crltrx.crl.dec.com (Win Treese)
Newsgroups: comp.unix.ultrix
Subject: Re: SLIP over a DECserver and LAT from ULTRIX
Message-ID: <122@crltrx.crl.dec.com>
Date: 1 Apr 89 07:57:32 GMT
References: <88360@felix.UUCP> <6425@cbmvax.UUCP> <1400@blake.acs.washington.edu> <6467@cbmvax.UUCP>
Reply-To: treese@crltrx.crl.dec.com.UUCP (Win Treese)
Organization: DEC Cambridge Research Lab
Lines: 28

Keywords: ultrix,slip,decserver,lat

In article <6467@cbmvax.UUCP> grr@cbmvax.UUCP (George Robbins) writes:
>In article <1400@blake.acs.washington.edu> mtsu@blake.acs.washington.edu (Montana State) writes:
>> 
>> Are the IOCTL()'s that allow you to make a connection to a remote LAT port
>> documented anywhere??  Obviously lpd uses them, but I don't see any 
>> how-to's anywhere.
>
>NO!  This is the big gripe, that DEC has chosen not to document or provide
>access to the same facilities that sytem programs like lcp and lpd use,
>limiting your ability to upgrade/replace these programs with ones that
>you feel to be better in some way.

Actually, 3.0 contains the information.  I don't think there's much in
the documentation, but there is code in /usr/examples/lat that show you
how to do it.

As George Robbins noted later in his message, 3.0 also provides the facility
for lcp to associate a tty with a LAT line automatically, without an
application having to worry about LAT at all.  This works fine for printers,
at least -- I haven't tried it for SLIP yet.

/usr/examples also contains other code that might be of interest to
you systems hackers out there...

Win Treese						Cambridge Research Lab
treese@crl.dec.com					Digital Equipment Corp.