The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Help request: uucp, mail on 4.2BSD
Date: Tue, 7 Mar 2017 12:17:09 -0500	[thread overview]
Message-ID: <CAC20D2MCFBN4e=4j2B0L1=WchCVgEf7sVVv2KGNa4ECWjSSXgA@mail.gmail.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1829 bytes --]

On Tue, Mar 7, 2017 at 10:23 AM, Dave Horsfall <dave at horsfall.org> wrote:

> It's been ages since I delved into UUCP; first was the
> ​ ​
> "original", then HoneyDanBer.
>

​Actually this is a great question for this list .. how many
implementations were created?
1.) The original 1978 version that shipped with V7 and 32/V (BSD 4.1 and
4.2)
2,) PC-UUCP for DOS came next -- I never knew how much was ripped off from
the original, because at the time, the Chesson's G protocol was not well
specified.   The authors claimed to have reverse engineered it - I will say
it worked.
3.) Honey-Dan-Ber rewrite - most popular for a long time
4.) Taylor UUCP first real clone that I know of that I do think was done
with out looking at other's source.  G protocol had been publicly
documented by then and the Trailblazer in fact was shipping with the
protocol imbedded in it.

Any others that folks know about and how well were they used?  Did things
like Coherent have a UUCP?   Linux and FreeBSD were able to use to Taylor
UUCP because it became available by then.    Whitesmith's Idris lacked
anything like UUCP IIRC (but was based on V6).   Same with Thoth originally
at Waterloo, but by the time they shipped it as the QNX product it was V7
compliant but I do not remember a UUCP being included in it.    Minux
lacked a UUCP as I recall, but I'm hazy on that has Andy's crew wrote a lot
of the user space.   Coherent was a "full" V7 clone and include things like
the dev tools including yacc/lex and was released much, much before the
Taylor version came out -- so what do they use for uucp if at all?

Does anyone remember any other implementations?

Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170307/f8d811e1/attachment.html>


             reply	other threads:[~2017-03-07 17:17 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07 17:17 Clem Cole [this message]
2017-03-07 17:43 ` Jaap Akkerhuis
2017-03-07 21:14   ` SPC
2017-03-08  1:51     ` John Labovitz
2017-03-10  0:31   ` Steve Simon
2017-03-10  2:04     ` Lyndon Nerenberg
2017-03-10  2:09       ` Lyndon Nerenberg
2017-03-10  2:23         ` [TUHS] uucp protocol nits Lyndon Nerenberg
2017-03-10  2:57           ` Larry McVoy
2017-03-10  3:08             ` Lyndon Nerenberg
2017-03-10  3:28               ` Lyndon Nerenberg
2017-03-10  3:28                 ` Lyndon Nerenberg
2017-03-10 14:28           ` Brad Spencer
2017-03-10 20:34           ` Ron Natalie
2017-03-10 21:42             ` Arthur Krewat
2017-03-10 22:10             ` Lyndon Nerenberg
2017-03-10 22:26               ` Corey Lindsly
2017-03-12 19:38             ` Dave Horsfall
2017-03-10  2:51     ` [TUHS] Help request: uucp, mail on 4.2BSD Dave Horsfall
2017-03-10  3:45       ` Dan Cross
2017-03-10  4:40         ` Lyndon Nerenberg
2017-03-10  9:57           ` Joerg Schilling
2017-03-10  6:34     ` Jaap Akkerhuis
2017-03-10  7:22       ` Erik E. Fair
2017-03-10  7:27         ` Lars Brinkhoff
2017-03-10 15:00         ` Dave Horsfall
2017-03-07 17:45 ` Arthur Krewat
2017-03-07 18:30 ` Jacob Goense
2017-03-07 18:30 ` Dan Cross
2017-03-07 19:00   ` Erik E. Fair
2017-03-07 22:04   ` Dave Horsfall
2017-03-10  6:10   ` Jim Carpenter
  -- strict thread matches above, loose matches on Subject: below --
2017-03-07  7:09 Warren Toomey
2017-03-07  7:11 ` Cory Smelosky
2017-03-07  7:54 ` Lars Brinkhoff
2017-03-07  8:27   ` Warren Toomey
2017-03-07  9:09 ` Warren Toomey
2017-03-07 15:23   ` Dave Horsfall
2017-03-07 20:43   ` Warren Toomey
2017-03-07 22:38     ` Dave Horsfall
2017-03-07 22:45       ` John Floren
2017-03-07 22:50       ` Jacob Goense
2017-03-07 22:58       ` Warren Toomey
2017-03-07 23:46         ` Cory Smelosky
2017-03-07 23:54           ` William Pechter
2017-03-07 23:55             ` Cory Smelosky
2017-03-08  0:03           ` John Floren
2017-03-08  0:05             ` Cory Smelosky
2017-03-08  4:05         ` Dave Horsfall
2017-03-08 10:21         ` arnold
2017-03-07 23:14       ` Arthur Krewat
2017-03-07 23:19         ` Dave Horsfall
2017-03-07 23:27           ` Arthur Krewat
2017-03-08 21:20             ` Josh Good
2017-03-08 21:42               ` Corey Lindsly
2017-03-08 22:59                 ` Arthur Krewat
2017-03-09 20:26                   ` Josh Good
     [not found]     ` <86varkclj1.fsf@molnjunk.nocrew.org>
2017-03-08  7:17       ` Warren Toomey
2017-03-08 22:03 ` Joerg Schilling
2017-03-08 23:07   ` Arthur Krewat
2017-03-08 23:18     ` Cory Smelosky
2017-03-08 23:39       ` Arthur Krewat
2017-03-09  0:22         ` Cory Smelosky
2017-03-09 14:51           ` Arthur Krewat
2017-03-09 17:53             ` SPC
2017-03-11  5:29             ` jsteve
2017-03-09  1:59     ` Dave Horsfall
2017-03-09  9:30     ` Joerg Schilling

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='CAC20D2MCFBN4e=4j2B0L1=WchCVgEf7sVVv2KGNa4ECWjSSXgA@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).