The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Jonathan Gray <jsg@jsg.id.au>
To: Dan Cross <crossd@gmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: NFS 40th anniversary event
Date: Thu, 14 Aug 2025 10:31:26 +1000	[thread overview]
Message-ID: <aJ0uXkqVf5cCMJer@largo.jsg.id.au> (raw)
In-Reply-To: <CAEoi9W46uvjWtpTG-qP_EtdBQLzA0+0VmHJK+p8WxEOzWyfhGQ@mail.gmail.com>

On Wed, Aug 13, 2025 at 10:18:34AM -0400, Dan Cross 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.
> 
> I have no doubt that RFS was technically superior to NFS, but Sun had
> non-technical market advantages. Assuming that I am remembering
> correctly, I suspect it was unsuccessful commercially for two reasons:
> 
> 1. Sun gave NFS (and the associated RPC layer) away for free, under a
> particularly liberal license, which lead to lots of interoperability
> (Larry's and Dave's comments notwithstanding). I suspect by the time
> RFS was available, it was much more expensive and less interoperable
> across heterogeneous systems.

The NFS reference code was licensed under NDA with some cost involved
according to Rick Macklem who wrote the NFS code in 4.3BSD-Reno.

Rick Macklem post to comp.protocols.nfs Aug 6, 1999
https://groups.google.com/g/comp.protocols.nfs/c/npQbxPe_ZeQ/m/Z_yQcsh56mkJ

The userland RPC part was under different terms.

"Sun will publish the source code for the user-level libraries that
implement RPC and XDR."

Bill Shannon post to net.unix-wizards Jan 13, 1985
https://groups.google.com/g/net.unix-wizards/c/PkJdZgCbrC4/m/u0kt3eeFSt4J

Sun RPC sources were later posted to mod.sources and included
on USENIX tapes.

  parent reply	other threads:[~2025-08-14  0:31 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
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 [this message]
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=aJ0uXkqVf5cCMJer@largo.jsg.id.au \
    --to=jsg@jsg.id.au \
    --cc=crossd@gmail.com \
    --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).