The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Derek Fawcus <dfawcus+lists-tuhs@employees.org>
To: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] RFS (was Re: Re: forgotten versions)
Date: Sun, 19 Jun 2022 21:46:31 +0100	[thread overview]
Message-ID: <Yq+LJxIW6cyotGfo@clarinet.employees.org> (raw)
In-Reply-To: <CAK7dMtALWesXWaw6n-oH+5XRK8ayLz2F2ZNAhN3VUFbTCeL_Gw@mail.gmail.com>

On Fri, Jun 17, 2022 at 10:00:19PM -0700, Kevin Bowling wrote:
> On Fri, Jun 17, 2022 at 5:35 PM Douglas McIlroy douglas.mcilroy@dartmouth.edu> 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. […]

  […]

  Remote File System Release 1.0 was first introduced in 1986 with Release 3.0 of UNIX System V for AT&T 3B2 machines with Starlan network connections. It makes heavy use of STREAMS, which were also introduced at that time. The next release RFS 1.1, accompanying System V Release 3.1, was greatly enhanced. At this time releases for other machines became available. In particular, with the release of a standard UNIX for Intel 80386-based machines that incorporated STREAMS, vendors of networking products could arrange for RFS to operate with those products, and RFS could run over Ethernet or any other network that could support a solid transport connection such as TCP/IP or NetBIOS. […]

So that may be somewhere to search, possibly someone can find a '386 image with it included?

DF

  parent reply	other threads:[~2022-06-19 20:46 UTC|newest]

Thread overview: 11+ 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   ` Derek Fawcus [this message]
2022-06-19 23:07     ` [TUHS] Re: RFS (was Re: Re: forgotten versions) 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=Yq+LJxIW6cyotGfo@clarinet.employees.org \
    --to=dfawcus+lists-tuhs@employees.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).