Path: utzoo!attcan!uunet!mcsun!tuvie!mike
From: mike@tuvie (Inst.f.Techn.Informatik)
Newsgroups: comp.sys.apollo
Subject: Re: reason to buy Apollos
Message-ID: <1679@tuvie>
Date: 13 Jul 90 12:14:42 GMT
References: <9007121442.AA01927@richter.mit.edu> <1990Jul12.181524.1462@terminator.cc.umich.edu>
Organization: Technical University of Vienna, AUSTRIA
Lines: 28

In article <1990Jul12.181524.1462@terminator.cc.umich.edu>, rees@dabo.ifs.umich.edu (Jim Rees) writes:
> In article <9007121442.AA01927@richter.mit.edu>, krowitz@RICHTER.MIT.EDU
> (David Krowitz) writes:
>   It would be *much* cleaner if AFS did what Domain/OS does ...
>   namely put the host entry directories in // rather than in /.
> 
> Actually, you might be surprised at how many programs break because of the
> '//' notation.  AFS currently puts all the machine names in /afs.  But each
> machine is not an equal member of a large distributed file system.  Instead,
> it's much more of a traditional client/server relationship.  I don't
> particularly like this aspect of AFS.
If it breaks programs, those programs are broken and should be fixed.
This is difficult to do for Apollos alone, but if OSF breaks programs, 
they will be changed, not OSF.

The problem is that mounting something in a directory implies that it is
subordinated to this tructure. This is not the case with the network/computer
relationship. Clearly, computers should be subordinated to networks, not
vice versa.

				bye,
					mike
       ____  ____
      /   / / / /   Michael K. Gschwind             mike@vlsivie.at
     /   / / / /    Technical University, Vienna    mike@vlsivie.uucp
     ---/           Voice: (++43).1.58801 8144      e182202@awituw01.bitnet
       /            Fax:   (++43).1.569697
   ___/