From: Larry McVoy <lm@mcvoy.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: NFS 40th anniversary event
Date: Wed, 13 Aug 2025 10:27:15 -0700 [thread overview]
Message-ID: <20250813172715.GB25260@mcvoy.com> (raw)
In-Reply-To: <CANxB0bTVx-bVo7syZLwgfPz8Kh2PM8pHoLdiAYLN9cFqW16SYQ@mail.gmail.com>
They both served a purpose. I'm still a fan of both, C especially,
but I'll admit that C needs careful programmers. When my older son was
getting into programming, he asked about C (he started with python and
hates it, has moved to Julia for most mathy stuff). I told him that C is
like a sports car on a narrow, twisty, mountain road with no guard rails.
If you drive a car like that in those conditions, and look at your phone,
you're gonna have a very bad day. On the other hand, if you are a good
driver and are paying attention, that can be a boat load of fun.
I'm watching your talk and I'm struct by how much of this problem space
we solved in BitKeeper. Someone had a .signature that said "You're lost
in a tree of repositories, all almost the same". We certainly solved the
shared mutable data problem. Our stuff didn't scale to billions of files
though we took a stab at that with nested repositories that worked pretty
well.
I got to the point where you are more or less arguing for the same thing.
I'd be careful about scaling. If you want consistency, you have to keep
a list of files you are managing. That list gets big.
As for POSIX, I've very much read the early spec, the whole thing, many
times. My first job at Sun was implementing POSIX conformance in SunOS.
Maybe I'm naive, but I didn't find it particularly hard, it was a lot of
grunt work, a lot of checking each file system to make them all the same.
I'm sure there is some subtle thing I've missed but Sun was happy with
my work so I don't think I was that far off.
On Wed, Aug 13, 2025 at 09:43:08AM -0700, Tom Lyon wrote:
> BTW, my own opinions abut NFS can be seen in my "NFS Must Die!" talk here:
> https://www.youtube.com/watch?v=ZVF_djcccKc&ab_channel=TomLyon
>
> Not that NFS *was* bad - but it *is* bad (for non-casual use).
> Like the C language, it was great for its time. Not so much anymore.
>
>
>
> On Wed, Aug 13, 2025 at 9:24???AM Peter Weinberger (?????????) via TUHS <
> tuhs@tuhs.org> wrote:
>
> > It was a research proof-of-princple. (i.e.. partly principled and
> > partly really hacky. My list of its issues was pretty long.)
> >
> > (If A mounted B's file system somewhere, and B mounted A's, then the
> > directory tree was infinite. That's mathematics, not a bug.)
> >
> > On Wed, Aug 13, 2025 at 11:56???AM Larry McVoy <lm@mcvoy.com> wrote:
> > >
> > > 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.
> > >
> > > Sunos had it, my office mate ported it. I was unimpressed, it worked
> > well
> > > between the same archs but was riddled with byte order problems and
> > > ioctl calls that were not portable.
> >
--
---
Larry McVoy Retired to fishing http://www.mcvoy.com/lm/boat
next prev parent reply other threads:[~2025-08-13 17:27 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 [this message]
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=20250813172715.GB25260@mcvoy.com \
--to=lm@mcvoy.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).