From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] UUCP mis-history?
Date: Wed, 8 Mar 2017 09:10:52 -0500 [thread overview]
Message-ID: <CAC20D2Pa197zAwZwahDn4WRJPNUz8nUoKL9X1Rix-yaLLxKF4g@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.20.1703081443490.2854@aneurin.horsfall.org>
Lesk's version predates V7 as was pointed out. Which I had forgotten in my
counting.
The V7 version (or traditional) is what they are referring here I believe
and indeed that spread as part of V7
On Tue, Mar 7, 2017 at 10:45 PM, Dave Horsfall <dave at horsfall.org> wrote:
> http://www.thefullwiki.org/UUCP
>
> ``UUCP was originally written at AT&T Bell Laboratories, by Mike Lesk, and
> early versions of UUCP are sometimes referred to as System V UUCP.''
>
> Err, it was V7, wasn't it? That considerably predates SysV...
>
> --
> Dave Horsfall DTM (VK2KFU) "Those who don't understand security will
> suffer."
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170308/ce647416/attachment.html>
next prev parent reply other threads:[~2017-03-08 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 3:45 Dave Horsfall
2017-03-08 14:10 ` Clem Cole [this message]
2017-03-08 23:49 ` Steve Johnson
2017-03-09 14:48 ` Arthur Krewat
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=CAC20D2Pa197zAwZwahDn4WRJPNUz8nUoKL9X1Rix-yaLLxKF4g@mail.gmail.com \
--to=clemc@ccc.com \
/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).