Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!munnari.oz.au!goanna!minyos.xx.rmit.oz.au!s900387
From: s900387@minyos.xx.rmit.oz.au (Craig Macbride)
Newsgroups: comp.unix.sysv386
Subject: Re: slip for sysv386 unix?
Keywords: unix slip sysv386
Message-ID: <1991Feb1.130904.14880@minyos.xx.rmit.oz.au>
Date: 1 Feb 91 13:09:04 GMT
References: <1019@ra.MsState.Edu> <1113@idcapd.idca.tds.philips.nl>
Organization: VUT(RMIT), Melbourne, Australia
Lines: 20

Well, SLIP in ISC's version 2.2 certainly works ... well, for most things,
anyway. rcp, rlogin, and so on across a serial line are not too slow (if you
are used to modems!), but if I attempt to use talk, it sits and puts up a
message about contacting the other machine. Unfortunately that's all it does:
put up a message. It will sit there all day if you let it, without any sign of
activity at the other machine.

Admittedly, the documentation is pathetic, and assumes you already know what
you are doing. Basically (for ISC, at least), you set up net addresses on
machines, configure them to use run state 3 to start up inetd, and insert
appropriate calls to slattach in some rc.d file for that run state. (The last
of these is not done for you by the system admin menus, which also fail to
create the sl login account, as the script for this is missing from the 2.2
distribution!!!)

-- 
 _____________________________________________________________________________
| Craig Macbride, s900387@minyos.xx.rmit.oz.au |  Reality is for people who   |
| Only the equipment belongs to Victoria Uni.  | can't handle science fiction.|
| of Technology (RMIT); The opinions are mine. |______________________________|