🚀 go-pugleaf

In article <1992Jan14.104223.9892@vax5.cit.cornell.edu> umh@vax5.cit.cornell.edu writes:

   In article <37447@icspub.ics.osaka-u.ac.jp>,
   youki@rd.ecip.osaka-u.ac.jp (Youki Kadobayashi) writes: 
   > What will the GNU gurus adopt as their standard distributed file system?
   > I think they won't adopt bare NFS because NFS do not scale well.
   > Same goes for Sprite File System. I think realistic approach would be
   > NFS+something or Sprite FS+something..
   > 

   Isn't Andrew public domain, since it was invented at CMU? That might be easier
   than trying to reverse-engineer NFS.


   Maynard Handley

nobody needs to reverse-engineer NFS.  the specification is public
domain, and 4.3BSD-Reno includes a completely rewritten implementation
(at least according to the announcement).

anyway...

I think AFS would be a good choice for very large networks and for
wide-area access.  but for small installations, NFS comes with fewer
surprises and corresponds more closely to how people have become used
to the file systems on Unix-like OS's to work.  if AFS is chosen as
the distributed file system,  there will, in my opinion, need to be a
lot of work done to merge the AFS file system manipulation commands
with the current standard unix ones. chmod and ls come to mind as
programs that are mostly useless under AFS.  any changes will, of
course, need to be fully compatible with Transarc's implementation of
DFS for OSF/DCE.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vick Khera, Gradual Student/Systems Guy   Department of Computer Science
ARPA:   khera@cs.duke.edu                 Duke University
UUCP:   ...!mcnc!duke!khera               Durham, NC 27706     (919) 660-6528