From: lars at nocrew.org (Lars Brinkhoff)
Subject: [COFF] [TUHS] VFS prior to 1984
Date: Wed, 24 Jun 2020 18:46:01 +0000 [thread overview]
Message-ID: <7wsgek5ml2.fsf@junk.nocrew.org> (raw)
In-Reply-To: <CAFH29trjwiRvjT=XUd=Nnigfygvn921Ocy890bEB2MHdqhi9fw@mail.gmail.com> (Richard Salz's message of "Wed, 24 Jun 2020 14:13:20 -0400")
Redirected to COFF, since this isn't very TUHS related.
Richard Salz wrote:
> Noel Chiappa wote:
>> MLDEV on ITS would, I think, fit under that description.
>> I don't know if there's a paper on it; it's mid-70's.
I don't think there's anything like an academic paper.
The earliest evidence I found for the MLDEV facility, or a predecessor,
is from 1972:
https://retrocomputing.stackexchange.com/questions/13709/what-are-some-early-network-file-systems
> A web search for "its mldev" finds several things (mostly by Lars Brinkhoff
> it seems) , including
> https://github.com/larsbrinkhoff/mldev/blob/master/doc/mldev.protoc
That's just a copy I made.
parent reply other threads:[~2020-06-24 18:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAFH29trjwiRvjT=XUd=Nnigfygvn921Ocy890bEB2MHdqhi9fw@mail.gmail.com>]
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=7wsgek5ml2.fsf@junk.nocrew.org \
--to=coff@minnie.tuhs.org \
/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).