From: chad brown <yandros@MIT.EDU>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] history question ("Athena's OldFiles")
Date: Fri, 2 Jun 2006 12:31:37 -0400 [thread overview]
Message-ID: <90BB8E89-C38B-4FE6-972A-B9404005DCD6@mit.edu> (raw)
In-Reply-To: <B69F441D-E7C3-4BA5-A927-6EE1868EFFD3@mit.edu>
In case anyone cares...
Athena started using AFS in the late 80's, and switched mostly
wholesale in the early 90's. OldFiles comes directly from
that time.
Athena was using Kerberos authentication in AFS right from the
start -- and I believe is still using the home-grown Kerberos support,
not the stuff that CMU added to AFS shortly thereafter.
*chad
On May 12, 2006, at 11:01 PM, Dave Eckhardt wrote:
> According to http://cm.bell-labs.com/plan9/about.html:
> Slowly, ideas from Plan 9 are being adopted by other systems.
> [...] The dump file system has been mimicked in Athena's
> OldFiles directories or Network Appliance's .snapshot
> directories.
>
> I don't know much about Athena, but I believe OldFiles
> has been the name for "yesterday's read-only snapshot"
> in AFS since the mid 1980's. The snapshot is mentioned,
> although not by name, in Section 6.5 ("Backup") of
> "Scale and Performance in a Distributed File System"
> (Howard et al., ACM TOCS, Feb. 1988), which documents
> AFS as of early 1987.
>
> My vague understanding, which could be wrong, is that
> in the late 80's or early 90's, there was cross-fertilization
> when Athena switched from NFS to AFS, and AFS switched
> from home-grown authentication to Kerberos. If so the
> appearance of OldFiles at MIT may well be after, but not
> caused by, the Plan 9 WORM file server's dump tree.
>
> Dave Eckhardt
prev parent reply other threads:[~2006-06-02 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-13 3:01 Dave Eckhardt
[not found] ` <B69F441D-E7C3-4BA5-A927-6EE1868EFFD3@mit.edu>
2006-06-02 16:31 ` chad brown [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=90BB8E89-C38B-4FE6-972A-B9404005DCD6@mit.edu \
--to=yandros@mit.edu \
--cc=9fans@cse.psu.edu \
/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).