The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: web@loomcom.com (Seth Morabito)
Subject: [TUHS] Old Usenet newsreader source code?
Date: Tue, 08 May 2018 10:01:19 -0700	[thread overview]
Message-ID: <1525798879.1346575.1365076168.7DACCEFA@webmail.messagingengine.com> (raw)
In-Reply-To: <3d106621-3889-19b5-4162-4bc039699a84@kilonet.net>

On Tue, May 8, 2018, at 9:53 AM, Arthur Krewat wrote:
> 
> 
> On 5/8/2018 12:25 PM, Seth Morabito wrote:
> > I'm looking especially for nn, which was my go-to at the time. The oldest version I've found so far is nn 6.4, which is too big to compile on a 3B2/400. If I could get my hands on 6.1 or earlier, I think I'd have a good chance.
> >
>  From this: 
> https://webcache.googleusercontent.com/search?q=cache:NhNfJ21wtY8J:https://static.loomcom.com/3b2/software/3b2archive/yahozna/misc/unix-c/usenet/000-index.txt+&cd=2&hl=en&ct=clnk&gl=us&client=firefox-b-1
> 
> I assume that nn 6.4 was indeed able to run on 3B2 but maybe not a model 
> 400?

Well now I have to laugh... loomcom.com is my own server. Apparently I had old versions of trn and nn *right under my own nose*. That just goes to show how badly I need to curate that big dump of 3B2 stuff I've been hoarding.

Thank you for finding that.

(By the way, I reorganized recently. Everything under https://static.loomcom.com/3b2/software moved to https://static.loomcom.com/3b2/software_archive/ so I could build a brand new repository under the 'software' directory.)

-Seth
-- 
  Seth Morabito
  web at loomcom.com


  reply	other threads:[~2018-05-08 17:01 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08 16:25 Seth Morabito
2018-05-08 16:36 ` Larry McVoy
2018-05-08 16:43   ` Warner Losh
2018-05-08 17:06   ` arnold
2018-05-08 17:27     ` Dan Cross
2018-05-08 17:42       ` Andy Kosela
2018-05-08 21:27         ` [TUHS] Old Usenet / local communitites Mike Markowski
2018-05-08 17:53       ` [TUHS] Old Usenet newsreader source code? Seth Morabito
2018-05-08 18:28         ` Grant Taylor
2018-05-08 18:35         ` Arthur Krewat
2018-05-08 18:45           ` Warner Losh
2018-05-08 19:00           ` Lyndon Nerenberg
2018-05-08 19:09             ` Grant Taylor
2018-05-08 19:11             ` Arthur Krewat
2018-05-08 21:50               ` Grant Taylor
2018-05-08 21:54                 ` Larry McVoy
2018-05-08 21:58                   ` Grant Taylor
2018-05-08 22:22               ` Henry Bent
2018-05-08 22:32                 ` Arthur Krewat
2018-05-08 22:59                   ` Henry Bent
2018-05-09  2:01                     ` Michael Parson
2018-05-09  1:55                 ` Michael Parson
2018-05-08 20:01             ` Bakul Shah
2018-05-08 21:56               ` Grant Taylor
2018-05-08 20:54             ` Lyndon Nerenberg
2018-05-08 19:05           ` Grant Taylor
2018-05-08 19:15             ` Arthur Krewat
2018-05-08 19:35               ` Grant Taylor
2018-05-08 19:23             ` Steve Nickolas
2018-05-08 19:29               ` Grant Taylor
2018-05-09  0:46                 ` Steve Nickolas
2018-05-08 19:26         ` Ron Natalie
2018-05-08 19:48           ` Grant Taylor
2018-05-08 20:54           ` Daniel Camolês
2018-05-08 22:55             ` Grant Taylor
2018-05-08 23:16               ` Lyndon Nerenberg
2018-05-08 23:18                 ` Henry Bent
2018-05-08 23:21                   ` George Michaelson
2018-05-08 23:25                   ` Grant Taylor
2018-05-08 23:22                 ` Grant Taylor
2018-05-08 23:37                   ` Grant Taylor
2018-05-09  0:54                 ` Steve Nickolas
2018-05-08 17:09   ` Clem Cole
2018-05-08 16:53 ` Arthur Krewat
2018-05-08 17:01   ` Seth Morabito [this message]
2018-05-08 19:41 ` Dave Horsfall
2018-05-08 21:49 ` Jeremy C. Reed
2018-05-08 23:39 ` John Labovitz
2018-05-09  0:08   ` Jeremy C. Reed
2018-05-09  0:11     ` Jeremy C. Reed
2018-05-09  0:42       ` Warren Toomey
2018-05-09  0:31   ` Bakul Shah

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=1525798879.1346575.1365076168.7DACCEFA@webmail.messagingengine.com \
    --to=web@loomcom.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).