From: Dan Cross <crossd@gmail.com>
To: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: NFS 40th anniversary event
Date: Wed, 13 Aug 2025 10:18:34 -0400 [thread overview]
Message-ID: <CAEoi9W46uvjWtpTG-qP_EtdBQLzA0+0VmHJK+p8WxEOzWyfhGQ@mail.gmail.com> (raw)
In-Reply-To: <CAKH6PiVDCdD8JLAvgA9Bbb8nHrUz=9JQY0U-LpeiPq9LTFAOYA@mail.gmail.com>
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.
2. Sun was quite adamant that NFS be stateless, and also not tied to
Unix filesystem semantics, whereas (as I understood it) RFS was both
stateful and deeply imbued with Unix semantics.
Related to (2), while the File System Switch that was developed to
support RFS was very elegant, I think that Sun's "vnode" architecture
was seen as more flexible, permitting Unix to incorporate support for
all sorts of foreign filesystem types (useful when CD-ROMs and things
like floppy disks using the MS-DOS FAT format started becoming
common). I suppose RFS could have been adapted to use vnodes, but by
then it probably wasn't considered worth the effort due to lack of
adoption.
It may be worth mentioning that some NFS implementations are
configurable for UID remapping in the server.
I recall Sun environments with NFS and NIS (the mechanism for
distributing /etc/passwd, groups, and other administrative data around
a network). It was a really pleasant environment, and extremely
productive. Properly configured, you could log into essentially any
machine on the network and have access to your home directory, common
data, locally installed programs (that of course lived on NFS), and so
on. It was quite common to tell a colleague to just have a look in
your home directory for something you were working on, facilitating
collaboration, and so on. Diskless and "dataless" machines were
common; the latter being machines that mounted _most_ things from a
central NFS server, but had the operating system itself (really, /,
/usr and /tmp) locally installed on a disk.
It required a lot of effort to maintain, since Unix machines were
still fundamentally meant to be standalone, and it wasn't as elegant
as Plan 9 ultimately was, but it was very nice for the time.
- Dan C.
> On Tue, Aug 12, 2025 at 11:05 PM Dave Horsfall <dave@horsfall.org> wrote:
> >
> > On Tue, 12 Aug 2025, Larry McVoy wrote:
> >
> > > I think Sun people love it, because the Sun implementation just worked,
> > > the rest of the world mostly hates it. I learned this when I left Sun
> > > and got to use other NFS implementations, they sucked.
> >
> > I can vouch for Sun's NFS working well, and others' not so much (zeroed
> > blocks returned etc)...
> >
> > > We supported BitKeeper on NFS which meant we had to do lock files on NFS
> > > on all platforms. Believe me when I say I know that other NFS
> > > implementations were a mess. Read all the drama here:
> >
> > I'm impressed by the workarounds for obscure kernel bugs :-)
> >
> > -- Dave
next prev parent reply other threads:[~2025-08-13 14:19 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 [this message]
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
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=CAEoi9W46uvjWtpTG-qP_EtdBQLzA0+0VmHJK+p8WxEOzWyfhGQ@mail.gmail.com \
--to=crossd@gmail.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).