Hi AFS folks.
We're in an initial phase of AFS deployment, where we also have to
maintain an old NFS and autofs based system (i.e. this is a @!=+!!@^%$#
Solaris 2.4 system).
The AFS version is the newly released 3.4 (GA).
We expect that the AFS deployment will take quite a while until it is
accepted evrywhere at our campus. ("Quite a while" most probably means
several years)
During that time we MUST be able to use the old style of pathnames to
our home directories. To accomplish this, we use the automounter
(autofs) to either mount AFS directories via a translator machine on
machines not having AFS installed, or mounting through
"localhost:/afs/@cell/user/..." on machines that are true AFS clients.
This setup works fairly well for normal file operations.
One "anomaly", however, is that the "fs" command seem to use a bad
mechanism for determining whether a file or directory given as argument
is within AFS or not.
E.g.
/users/cs/foo is the autofs mounted path of /afs/@cell/user/cs/foo.
%cd /afs/@cell/user/cs/foo
%fs la .
Access list for . is
Normal rights:
foo rlidwka
%cd /users/cs/foo
%fs la .
fs: Invalid argument; it is possible that . is not in AFS.
This is somewhat annoying, and promotes AFS badwill.
On other systems (like DEC Alphas) which uses the old automounter ,
everything works fine. In that case the automounter uses symbolic links,
but Solaris autofs does some other kind of magic.
Have anyone seen this before ?
Does anyone use AFS and NFS together (in such a weird setup)
What can I do about it.
Regards
Chris.
--------------------------------------------------
Christer Bern�rus E-mail: [EMAIL PROTECTED]
UNIX Systems Manager Phone: +46 31 7721036
Chalmers U. of Technology Fax: +46 31 165655
Department of Computing Science Ham radio: SM6FBQ, Loc: JO67BQ
S-412 96 Gothenburg, SWEDEN 144.050 T, 144.027 EME
