The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Brad Spencer <>
To: Larry McVoy <>
Subject: [TUHS] Re: RFS (was Re: Re: forgotten versions)
Date: Sun, 19 Jun 2022 19:19:31 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (message from Larry McVoy on Sun, 19 Jun 2022 16:07:20 -0700)

Larry McVoy <> writes:

> On Sun, Jun 19, 2022 at 09:46:31PM +0100, Derek Fawcus wrote:
>> On Fri, Jun 17, 2022 at 10:00:19PM -0700, Kevin Bowling wrote:
>> > On Fri, Jun 17, 2022 at 5:35 PM Douglas McIlroy> wrote:
>> > >
>> > > V8 also had Peter Weinberger's Remote File System. Unlike NFS, RFS
>> > > mapped UIDS, thus allowing files to be shared among computers in
>> > > different jurisdictions with different UID lists. Unfortunately, RFS
>> > > went the way of Reiser paging.
>> > 
>> > I believe RFS shipped in SVR3, at least as a package for the 3b2.
>> Apparently. I've a book (ISBN 0-672-48440-4) with a short chapter on it within, authored by Douglas Harris.
>> It happens to state:
>>   AT&T's approach towards UNIX System V, Release 3.0 and beyond is to provide a /Remote File System/ (RFS) that is an extension of the ordinary file system arrangement. [???]
> SunOS 4.x shipped RFS, Howard Chartok (my office mate at the time) did
> the port I believe.  Thankless work since Sun ran their entire campus
> on NFS; RFS never got any attention.  It's too bad because it did solve
> some problems that NFS just punted on.  NFS is Clem's law in action,
> it was good enough, not great, but still won.

I remember SunOS 4.x having RFS..  I never used it but I vaguely recall
(probably misremembering) that there was a warning in the man page about
it that it might not interoperate with /dev devices correct if the byte
order of the machines was different.  I seem to recall that with RFS if
/dev was remoted you actually accessed the remote devices and not just
the device nodes from the system that /dev was mounted to.  At the AT&T
site I was at we used NFS exclusively too.

Brad Spencer - - KC8VKS -

  reply	other threads:[~2022-06-19 23:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-18  0:35 [TUHS] Re: forgotten versions Douglas McIlroy
2022-06-18  5:00 ` Kevin Bowling
2022-06-18  5:13   ` Adam Thornton
2022-06-18 16:58     ` Clem Cole
2022-06-18 17:18       ` Warner Losh
2022-06-18 17:57         ` Clem Cole
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 [this message]
2022-06-20  5:03         ` Arno Griffioen via TUHS
2022-06-20  6:53           ` Theodore Ts'o
2022-06-20  0:44 Norman Wilson
2022-06-20  1:02 ` George Michaelson
2022-06-20  4:50 ` arnold
2022-06-20 12:28 Paul Ruizendaal via TUHS
2022-06-20 21:53 ` Derek Fawcus

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).