Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!mtxinu!shore
From: shore@mtxinu.COM (Melinda Shore)
Newsgroups: comp.unix.wizards
Subject: AFS (Was Re: What kinds of things would you want in the GNU OS?)
Message-ID: <881@mtxinu.UUCP>
Date: 7 Jun 89 05:54:49 GMT
References: <106326@sun.Eng.Sun.COM> <4315@ficc.uu.net> <338@arc.UUCP> <208@sopwith.UUCP> <3306@cps3xx.UUCP> <11856@bloom-beacon.MIT.EDU>
Reply-To: shore@mtxinu.com (Melinda Shore)
Organization: mt Xinu, Berkeley
Lines: 27

[]
Allow me to add a few items to the bad things list:

1)  The semantics really are different from Unix filesystem semantics.
	Permission bits take on new and twisted meanings, and links to files
	in different directories are not allowed.

2)  Directories, which you and I consider to be files, aren't treated as
	files by AFS.  *No* caching, which means that you can ls until the
	cows come home but the 80th time is not going to be any faster than
	the first.

3)  Performance.  The whole file is copied over at access time, which
	speeds up future file accesses but can turn "grep string *" into a
	fairly unpleasant experience.

4)  Disk usage.  Because entire files are copied over it can be something
	of a disk burner.

5)  Administration is somewhat (!) complex.  I have high hopes that
	someone can clean this up, though.

AFS certainly has its uses, though, and its appropriateness will depend
heavily on the environment and on the applications.
-- 
Melinda Shore                                     shore@mtxinu.com
Mt Xinu                                  ..!uunet!mtxinu.com!shore