The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Tom Lyon <pugs78@gmail.com>
To: Bakul Shah <bakul@iitbombay.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: NFS 40th anniversary event
Date: Wed, 13 Aug 2025 19:04:32 -0700	[thread overview]
Message-ID: <CANxB0bT9KU79hQFV=F2=hv8xsPyUkviV+3GFN4uzhsG3+xzPcQ@mail.gmail.com> (raw)
In-Reply-To: <BA8655B3-A268-47C4-9ACD-C412534FDC0B@iitbombay.org>

[-- Attachment #1: Type: text/plain, Size: 2273 bytes --]

No collaborators.  Not that I'm trying at all, the talk kinda got the urge
out of my system.
I therorize that many people could benefit - but no hard data.

On Wed, Aug 13, 2025 at 6:41 PM Bakul Shah <bakul@iitbombay.org> wrote:

> I viewed this last October. Seemed like a bunch of sensible ideas. Did you
> find any collaborators? [Not offering, just curious!]
>
> I see these "storage" categories: chunks, files, namespaces, metadata,
> databases & streams [1]. If you define a network protocol to handle
> critical operations on them all, implementations would likely follow.
> Engineers do better with well defined boundaries compared to "somewhere
> beyond there"!
>
> [1] probably could be simplified.
>
> On Aug 13, 2025, at 9:43 AM, Tom Lyon <pugs78@gmail.com> 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.
>>
>
>

[-- Attachment #2: Type: text/html, Size: 3506 bytes --]

  reply	other threads:[~2025-08-14  2:04 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 [this message]
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='CANxB0bT9KU79hQFV=F2=hv8xsPyUkviV+3GFN4uzhsG3+xzPcQ@mail.gmail.com' \
    --to=pugs78@gmail.com \
    --cc=bakul@iitbombay.org \
    --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).