From: berny.goodheart@myrealbox.com (Berny 'Scouser' Goodheart)
Subject: [TUHS] RFS (Remote? File System) (A. Wik)
Date: Mon, 15 May 2006 11:57:47 +0100 [thread overview]
Message-ID: <003501c6780e$6be0aec0$4405a6c0@FERRARI> (raw)
In-Reply-To: <mailman.3.1147658400.31029.tuhs@minnie.tuhs.org>
From: "A. Wik" <aw@aw.gs>
>
> In the context of non-local file systems - Sun's NFS
> 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.
>
> But that's all I know. Does anyone know of useful
> sources of information (or just anecdotes, for that
> matter)?
>
> -aw
There's an entire section devoted to RFS in the USL SVR4 Network
User's And Administrator's Guide. What is it you after
Exactly?
-Berny
prev parent reply other threads:[~2006-05-15 10:57 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 ` [TUHS] TUHS Digest, Vol 31, Issue 5 Larry McVoy
2006-05-15 7:46 ` Tim Bradshaw
2006-05-15 14:02 ` Larry McVoy
2006-05-15 10:57 ` Berny 'Scouser' Goodheart [this message]
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='003501c6780e$6be0aec0$4405a6c0@FERRARI' \
--to=berny.goodheart@myrealbox.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).