The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: steve@quintile.net (Steve Simon)
Subject: [TUHS] NFS  aka the guy who brought up SVr4 on Sun machines
Date: Wed, 11 Jan 2017 00:56:52 +0000	[thread overview]
Message-ID: <E2C48D73-3F63-489E-B14F-F2BFA0768AC5@quintile.net> (raw)
In-Reply-To: <20170110214355.GM24126@mcvoy.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]

Beware of confusion.

There is the 8th and 9th edition remote file protocol
(I have papers somewhere I think), by Weinberger.
This evolved into 9p, Plan9’s file protocol.

There is also RFS, I think a USG package for SYSVr3. The paper I have 
About this is by Author L Sabsevitz, though I don’t know if he was the author
of the code, or just the paper.

They are rather different beasts with similar names.

-Steve

> On 10 Jan 2017, at 21:43, Larry McVoy <lm at mcvoy.com> wrote:
> 
> On Tue, Jan 10, 2017 at 10:40:03PM +0100, Joerg Schilling wrote:
>> The nice idea in RFS was that it supported remote devices, but the iotcl 
>> handling was a problem in AT&T UNIX before SVr4 ??? added a flag to tell 
>> whether the data source was in kernel or userland. I am not sure wether RFS 
>> had a concept like XDR for ioctls.
> 
> I believe it did not.
> 
>> The funny thing: RFS was supported in SunOS4, but not in SunOS-5.
> 
> And Howard Chartok was ecstatic over that decision (he was my office
> mate and did the port into SunOS 4.x.  Not one of his favorite projects.)



  reply	other threads:[~2017-01-11  0:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10 20:33 Doug McIlroy
2017-01-10 21:40 ` Joerg Schilling
2017-01-10 21:43   ` Larry McVoy
2017-01-11  0:56     ` Steve Simon [this message]
2017-01-11  3:17       ` Mary Ann Horton
2017-01-11  3:32         ` Larry McVoy
2017-01-11  3:40         ` arnold

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=E2C48D73-3F63-489E-B14F-F2BFA0768AC5@quintile.net \
    --to=steve@quintile.net \
    /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).