From: johnl@johnlabovitz.com (John Labovitz)
Subject: [TUHS] Help request: uucp, mail on 4.2BSD
Date: Tue, 7 Mar 2017 17:51:21 -0800 [thread overview]
Message-ID: <2DEF9163-44DA-44C7-90F3-FAF63760E495@johnlabovitz.com> (raw)
In-Reply-To: <CACytpF-K3N_=Lv==FbhfDrMb_BGHrTdpsqU5NGnNV-RmD893JA@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 401 bytes --]
On Mar 7, 2017, at 18:17, Clem Cole <clemc at ccc.com> wrote:
> Does anyone remember any other implementations?
I ported UUCP and either B or C News to the Mac ca. 1989-1990, using the Lightspeed/THINK C compiler on System 6 or 7. Can’t remember exactly how I read news or mail — maybe I wrote a simple GUI? Regretfully, I never released the code, and don’t have it around any more.
—John
next prev parent reply other threads:[~2017-03-08 1:51 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 17:17 Clem Cole
2017-03-07 17:43 ` Jaap Akkerhuis
2017-03-07 21:14 ` SPC
2017-03-08 1:51 ` John Labovitz [this message]
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=2DEF9163-44DA-44C7-90F3-FAF63760E495@johnlabovitz.com \
--to=johnl@johnlabovitz.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).