From: schily@schily.net (Joerg Schilling)
Subject: [TUHS] NFS aka the guy who brought up SVr4 on Sun machines
Date: Tue, 10 Jan 2017 22:40:03 +0100 [thread overview]
Message-ID: <587554b3.6O+E9BGOgaxwufwc%schily@schily.net> (raw)
In-Reply-To: <201701102033.v0AKXvrc018898@coolidge.cs.Dartmouth.EDU>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
Doug McIlroy <doug at cs.dartmouth.edu> wrote:
> And, sadly, NFS is still with us, having somehow upstaged Peter
> Weinberger's RFS (R for remote) that appeared at the same time.
> NFS allows one to add computers to a file system, but not to
> combine the file systems of multiple computers, as RFS did
> by mapping uids: NFS:RFS::LAN:WAN.
This changed long ago, NFSv4 no longer sends uid's but user names and supports
mappings.
NFS won because it was not built on top of UNIX semantics and thus allowed to
port it to other platforms.
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.
The funny thing: RFS was supported in SunOS4, but not in SunOS-5.
Jörg
--
EMail:joerg at schily.net (home) Jörg Schilling D-13353 Berlin
joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/
next prev parent reply other threads:[~2017-01-10 21:40 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 [this message]
2017-01-10 21:43 ` Larry McVoy
2017-01-11 0:56 ` Steve Simon
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=587554b3.6O+E9BGOgaxwufwc%schily@schily.net \
--to=schily@schily.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).