The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com
To: douglas.mcilroy@dartmouth.edu, arnold@skeeve.com
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: NFS 40th anniversary event
Date: Wed, 13 Aug 2025 09:34:05 -0600	[thread overview]
Message-ID: <202508131534.57DFY5h2034448@freefriends.org> (raw)
In-Reply-To: <CAKH6PiXVNnz_rmG9BO3=wTFreNG2TZ2OKmer_K-Mu=ZGgb1GaQ@mail.gmail.com>

System V RFS was a different animal that Research RFS. IIRC
Stephen Rago or someone like that did a USENIX paper about putting
the Research RFS into SVR4.

SVR4 RFS required kernel changes for client and server, IIRC,
whereas I believe that Research RFS only needed kernel changes
for the client and used a user-level server.

To borrow a phrase, "memory grows dim", so take the above with a
grain of salt.

Arnold

Douglas McIlroy <douglas.mcilroy@dartmouth.edu> wrote:

> "never made it outside Bell Labs" was a poor choice of words for
> "never gained acceptance outside of Bell Labs".
> I agree with Dan and Arnold, but I lament the fact that NFS : RFS ::
> intranet : internet  RFS had the grander vision. To be fair, I must
> admit that I have no idea how efficient or robust the released version
> was. Certainly the original worked very well.
>
> Doug
>
> On Wed, Aug 13, 2025 at 11:00 AM <arnold@skeeve.com> wrote:
> >
> > Dan Cross <crossd@gmail.com> wrote:
> >
> > > On Wed, Aug 13, 2025 at 10:00 AM Douglas McIlroy
> > > <douglas.mcilroy@dartmouth.edu> wrote:
> > > > I was always sorry that Peter Weinberger's RFS never made it outside
> > > > Bell Labs. It allowed networking between separately administered
> > > > systems by mapping UIDs.
> > >
> > > I believe it did?  If I recall correctly, it was available with System
> > > V, though perhaps I am misremembering.
> >
> > It was a different RFS, developed by USG.  It had full Unix semantics,
> > including ioctls and fcntl, for machines of the same architecture. It
> > was stateful, which meant if the server went away, you could hang your
> > shell at the very least. It first came out in SVR3.
> >
> > Earlier versions of SunOS 5 supported it; it was dropped in later
> > versions.
> >
> > It didn't get widespread support both because NFS had a big head
> > start, and because by the time it came out, the SVR3 licensing terms
> > had gotten onerous for most vendors.
> >
> > No disagreement with the rest of you note. :-)
> >
> > Arnold

  reply	other threads:[~2025-08-13 15:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-13  0:59 [TUHS] NFS 40th anniversary event Tom Lyon
2025-08-13  1:55 ` [TUHS] " Larry McVoy
2025-08-13  3:05   ` Dave Horsfall
2025-08-13  5:59     ` [TUHS] Greetings! Phillip Harbison
2025-08-13 14:00     ` [TUHS] Re: NFS 40th anniversary event Douglas McIlroy
2025-08-13 14:18       ` Dan Cross
2025-08-13 14:59         ` arnold
2025-08-13 15:26           ` Douglas McIlroy
2025-08-13 15:34             ` arnold [this message]
2025-08-13 15:47           ` Martin Schröder
2025-08-14  3:43             ` arnold
2025-08-13 15:56         ` Larry McVoy
2025-08-13 16:24           ` Peter Weinberger (温博格) via TUHS
2025-08-13 16:43             ` Tom Lyon
2025-08-13 17:27               ` Larry McVoy
2025-08-13 20:24               ` Will Senn
2025-08-14  1:41               ` Bakul Shah via TUHS
2025-08-14  2:04                 ` Tom Lyon
2025-08-14  0:31         ` Jonathan Gray
2025-08-14  0:54           ` Charles H. Sauer (he/him)
2025-08-14  1:28             ` Rich Salz
2025-08-14  1:29             ` Tom Lyon
2025-08-13 17:08       ` [TUHS] RFS Lyndon Nerenberg (VE7TFX/VE6BBM)

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=202508131534.57DFY5h2034448@freefriends.org \
    --to=arnold@skeeve.com \
    --cc=douglas.mcilroy@dartmouth.edu \
    --cc=tuhs@tuhs.org \
    /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).