From: Paul Ruizendaal via TUHS <tuhs@tuhs.org>
To: tuhs@tuhs.org
Subject: [TUHS] Re: RFS (was Re: Re: forgotten versions)
Date: Mon, 20 Jun 2022 14:28:06 +0200 [thread overview]
Message-ID: <94902095-8F4D-4350-8B2E-480E752515ED@planet.nl> (raw)
> I don't know the exact history of RFS a la System V, but I
> don't think it was Peter Weinberger's stuff, and it certainly
> wasn't his code.
Peter’s code is available in the V8 and V9 trees on TUHS.
The Sys V repositories on Github appear to include RFS code in all of R3.0, R3.1 and R3.2.
At first glance, it seems quite different from the V8/V9 code.
> Peter, being a self-described fan of cheap hacks, also wasn't
> inclined to spend much time thinking about general abstractions;
> in effect he just turned various existing kernel subroutines
> (when applied to a network file system) into RPCs. The
> structure of the file system switch was rather UNIX-specific,
> reflecting that.
Yes, well put. I’ve back ported his filesystem switch to V6/V7 and it is very light touch: on the PDP11 it added only some 500 bytes of kernel code (after some refactoring).
With hindsight it seems such a logical idea, certainly in a context where the labs were experimenting with remote system calls in the mid 70’s (Heinz Lycklama's work on satellite Unix) and early 80’s (Gottfried Luderer et al. on distributed Unix — another forgotten version). It is such a powerful abstraction, but apparently very elusive to invent.
Paul
next reply other threads:[~2022-06-20 12:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 12:28 Paul Ruizendaal via TUHS [this message]
2022-06-20 21:53 ` Derek Fawcus
-- strict thread matches above, loose matches on Subject: below --
2022-06-20 0:44 Norman Wilson
2022-06-20 1:02 ` George Michaelson
2022-06-20 4:50 ` arnold
2022-06-18 0:35 [TUHS] Re: forgotten versions Douglas McIlroy
2022-06-18 5:00 ` Kevin Bowling
2022-06-19 20:46 ` [TUHS] RFS (was Re: Re: forgotten versions) Derek Fawcus
2022-06-19 23:07 ` [TUHS] " Larry McVoy
2022-06-19 23:19 ` Brad Spencer
2022-06-20 5:03 ` Arno Griffioen via TUHS
2022-06-20 6:53 ` Theodore Ts'o
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=94902095-8F4D-4350-8B2E-480E752515ED@planet.nl \
--to=tuhs@tuhs.org \
--cc=pnr@planet.nl \
/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).