From: "Theodore Ts'o" <tytso@mit.edu>
To: Arno Griffioen <arno.griffioen@ieee.org>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: RFS (was Re: Re: forgotten versions)
Date: Mon, 20 Jun 2022 02:53:22 -0400 [thread overview]
Message-ID: <YrAZYlxrExiu5Jk1@mit.edu> (raw)
In-Reply-To: <Yq//slwWEXME+Ul7@ancienthardware.org>
I'll note there was another RFS that was posted to net.sources and
net.unix-wizards by Todd Brunhoff in January 1986. This was
completely different from the AT&T System V's; Todd's RFS was done as
part of his Master's Degree at the University of Denver, and it was
heavily dependant on BSD 4.2/4.3's sockets interface.
For more information, see:
https://groups.google.com/g/net.unix-wizards/c/QwRVsZS9jEM/m/V4ZI64CKopsJ?pli=1
We used this version of RFS at MIT Project Athena for a while before
switching to AFS, and it's mentioned in Professor Saltzer's Athena
Technical Plan, in the section entitled, "The Athena File Storage
Model":
https://web.mit.edu/saltzer/www/publications/athenaplan/c.6.pdf
Project Athena integrated MIT Kerberos (Version 4) into both NFS and
RFS, and of course AFS used Kerberos for its authentication tokens.
- Ted
next prev parent reply other threads:[~2022-06-20 6:53 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
2022-06-20 5:03 ` Arno Griffioen via TUHS
2022-06-20 6:53 ` Theodore Ts'o [this message]
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:
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=YrAZYlxrExiu5Jk1@mit.edu \
--to=tytso@mit.edu \
--cc=arno.griffioen@ieee.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).