From: Warner Losh <imp@bsdimp.com>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>, Paul Ruizendaal <pnr@planet.nl>
Subject: Re: [TUHS] Origins of PPP
Date: Thu, 5 Dec 2019 12:41:02 -0700 [thread overview]
Message-ID: <CANCZdfo0BZODmF8fZFJ1=UGw2a2OEF=Y7Fu9unR6XbQGXnnG7g@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2OBuTOWucRze=xhAEmgGeKu4wQxgtdab1EWLwo=8fHNcQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
On Thu, Dec 5, 2019 at 9:40 AM Clem Cole <clemc@ccc.com> wrote:
> What was common was the SLIP line discipline code under the covers, but
> how the line got set up to start running it was different. The original
> SLIP 'kit' from Harvard/MIT lacked anything like PPPD to start and was sort
> of ad hoc. I think originally it used a program called 'chat' that had been
> pulled out uucico that set things up then exec'ed the SLIP stuff; but
> chat(1) may have been round 2 or 3. I've forgotten the name of the
> original daemon, I bet it you look in the Usenet archives from 82-84 and
> look for 'SLIP' you find a couple of things.
>
There never was a slipd, at least in this time frame. The chat program
would login to the remote system, start SLIP on the remote end, then run a
program that effectively put the slip line discipline into place and then
maybe did an ifconfig. It was hit dinosaur over head with club level of
sophistication, if it was that advanced...
Warner
[-- Attachment #2: Type: text/html, Size: 1453 bytes --]
next prev parent reply other threads:[~2019-12-05 19:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 10:34 Paul Ruizendaal
2019-12-05 10:58 ` Michael Kjörling
2019-12-05 15:50 ` Richard Salz
2019-12-05 16:39 ` Clem Cole
2019-12-05 19:41 ` Warner Losh [this message]
2019-12-05 21:03 ` Clem Cole
2019-12-05 23:09 ` Doug McIntyre
2019-12-06 2:05 ` Lawrence Stewart
2019-12-06 18:31 ` Warner Losh
2019-12-05 19:05 Noel Chiappa
2019-12-05 19:21 ` ron
2019-12-05 19:37 ` Warner Losh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANCZdfo0BZODmF8fZFJ1=UGw2a2OEF=Y7Fu9unR6XbQGXnnG7g@mail.gmail.com' \
--to=imp@bsdimp.com \
--cc=clemc@ccc.com \
--cc=pnr@planet.nl \
--cc=tuhs@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).