Path: utzoo!attcan!uunet!samsung!umich!terminator!dabo.ifs.umich.edu!rees
From: rees@dabo.ifs.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: AFS, (was Re: convergence ???)
Keywords: DomainOs, HP-UX, OSF, AFS
Message-ID: <1990Jun15.155125.3593@terminator.cc.umich.edu>
Date: 15 Jun 90 15:51:25 GMT
References: <1640@tuvie> <1990Jun14.165124.15493@terminator.cc.umich.edu> <1990Jun14.190554.1416@bnrgate.bnr.ca>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 16

In article <1990Jun14.190554.1416@bnrgate.bnr.ca>,
awhitton@bcara132.bnr.ca (Alan Whitton) writes:
> Ah but if you look at AFS it looks remarkably like the Apollo File System
> (an AFS of a different kind). In AFS you can access attached nodes via:
> 
> ls /afs/foo.edu/bsd4.3   whereas in Apollo you would do
> ls //foo/bsd4.3              

But that's just syntax.  You still have to have a list of all your nodes
("cells" in AFS terminology) somewhere, although you don't have to mount
each one individually.

The thing I like about the Domain File System is that it's completely
democratic.  Each node is both a client and a server, and they all get the
same view of the file system.  When you plug in a new node, it can
immediately see everyone else's files, and everyone else can see its files.