The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: pepe@naleco.com (Josh Good)
Subject: [TUHS] Sun NFS version 2.0
Date: Sun, 26 Feb 2017 11:50:00 +0100	[thread overview]
Message-ID: <20170226104958.GA15670@naleco.com> (raw)
In-Reply-To: <20170224205731.GA14701@minnie.tuhs.org>

On 2017 Feb 25, 06:57, Warren Toomey wrote:
> 
> I eyeballed it against the 4.3BSD from UWisc that is in the archive already.
> It looks like the UWisc code is either a later version or a modified version
> of this NFSv2 code. Therefore, I think it's safe to put the original NFSv2
> code into the archive.
> 
> It's at http://www.tuhs.org/Archive/Distributions/Sun/
> 
> I'll add it and the early networking code to the Unix Tree soon.
> 
> Thanks Arthur!
> 	Warren

Hi, Warren.

Perhaps it's because of the ancient version of GnuPG that I am running,
but your PGP-signed message I'm replying to does not verify with your
public key you have published here: http://minnie.tuhs.org/warren.html

I get this output from my GnuPG install:
---------------------------------------
gpg: Signature made Fri Feb 24 21:57:31 2017 CET
gpg:                using RSA key 0xAC26979D28FF474E
gpg: Can't check signature: public key not found
---------------------------------------


I must be doing something wrong, I suppose.

-- 
Josh Good



  parent reply	other threads:[~2017-02-26 10:50 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21 12:02 [TUHS] Mach for i386 / Mt Xinu or other Noel Chiappa
2017-02-21 12:24 ` Steffen Nurpmeso
2017-02-21 12:57   ` Michael Kjörling
2017-02-21 15:02 ` Clem Cole
2017-02-22  1:50   ` Dan Cross
2017-02-22  2:25     ` Steve Nickolas
2017-02-22  3:11     ` Clem Cole
2017-02-22  4:07       ` Dan Cross
2017-02-22  4:17         ` Larry McVoy
2017-02-23 15:31           ` Nemo
2017-02-23 16:00             ` Clem Cole
2017-02-23 16:50               ` Nemo
2017-02-23 22:02               ` Dave Horsfall
2017-02-24  1:30                 ` Clem Cole
2017-02-24 20:54                   ` Dave Horsfall
2017-02-24  1:01               ` Jason Stevens
2017-02-22 10:16       ` jsteve
2017-02-21 15:15 ` Chet Ramey
2017-02-21 16:47 ` Larry McVoy
2017-02-21 18:58   ` Clem Cole
2017-02-21 19:21     ` Larry McVoy
2017-02-21 20:17       ` Clem Cole
2017-02-21 20:28       ` Steve Nickolas
2017-02-21 20:32         ` Larry McVoy
2017-02-21 22:58           ` Wesley Parish
2017-02-22  1:19             ` Clem Cole
2017-02-22  1:35               ` [TUHS] Sun NFS version 2.0 Arthur Krewat
2017-02-22  1:46                 ` Clem Cole
2017-02-22 13:33                   ` Arthur Krewat
2017-02-23 23:48                     ` Arthur Krewat
2017-02-24  7:47                       ` arnold
2017-02-22  2:07                 ` Cory Smelosky
2017-02-22 13:25                   ` Arthur Krewat
2017-02-22  3:17                 ` Larry McVoy
2017-02-22  8:43                   ` arnold
2017-02-24 20:57                 ` Warren Toomey
2017-02-24 22:09                   ` Warren Toomey
2017-02-26 10:50                   ` Josh Good [this message]
2017-02-22  9:00             ` [TUHS] Mach for i386 / Mt Xinu or other jsteve
2017-02-22  0:52   ` Andy Kosela
2017-02-22  1:04     ` ron minnich
2017-02-22  1:33       ` jason-tuhs
2017-02-22  3:18       ` Larry McVoy
2017-02-22  3:45         ` ron minnich
2017-02-22  4:06           ` Larry McVoy
2017-02-22  4:11             ` Larry McVoy

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=20170226104958.GA15670@naleco.com \
    --to=pepe@naleco.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).