From: lm@bitmover.com (Larry McVoy)
Subject: [TUHS] TUHS Digest, Vol 31, Issue 5
Date: Sun, 14 May 2006 21:22:38 -0700 [thread overview]
Message-ID: <20060515042238.GA25047@bitmover.com> (raw)
In-Reply-To: <mailman.3.1147658400.31029.tuhs@minnie.tuhs.org>
> in particular - I've seen RFS be mentioned. This was
> AT&T's implementattion of transparent real-time (for
> contrast with UUCP, FTP, etc.) remote file access.
It wasn't real time, it was "remote file system" == RFS.
It was different than NFS in that it was stateful and that it knew that the
other side knew what it knew (think ioctls, yuck).
My officemate worked on it, it was problematic. Don't go there. NFS is
bad enough, but it works.
--
---
Larry McVoy lm at bitmover.com http://www.bitkeeper.com
next parent reply other threads:[~2006-05-15 4:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3.1147658400.31029.tuhs@minnie.tuhs.org>
2006-05-15 4:22 ` Larry McVoy [this message]
2006-05-15 7:46 ` Tim Bradshaw
2006-05-15 14:02 ` Larry McVoy
2006-05-15 10:57 ` [TUHS] RFS (Remote? File System) (A. Wik) Berny 'Scouser' Goodheart
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=20060515042238.GA25047@bitmover.com \
--to=lm@bitmover.com \
/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).