From: lm@bitmover.com (Larry McVoy)
Subject: [TUHS] TUHS Digest, Vol 31, Issue 5
Date: Mon, 15 May 2006 07:02:42 -0700 [thread overview]
Message-ID: <20060515140242.GA27749@bitmover.com> (raw)
In-Reply-To: <C5D6F2D0-E9DF-41AC-B33F-C85177F64E0F@tfeb.org>
On Mon, May 15, 2006 at 08:46:33AM +0100, Tim Bradshaw wrote:
> On 15 May 2006, at 05:22, Larry McVoy wrote:
> >
> >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 memory, which may be wrong, is that some SunOS 4s had support for
> it (may be all did), so there are probably manuals and so forth which
> can still be found there.
That's correct and I have those manuals somewhere (anyone want a full
set of 4.x manuals?)
--
---
Larry McVoy lm at bitmover.com http://www.bitkeeper.com
next prev parent reply other threads:[~2006-05-15 14:02 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
2006-05-15 7:46 ` Tim Bradshaw
2006-05-15 14:02 ` Larry McVoy [this message]
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=20060515140242.GA27749@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).