[OpenAFS-devel] Has openafs always been this way?

[Kris Van Hees]

That has been the behaviour for all versions I have looked at.  It seemed a bit
odd to me as well when I was looking into it while writing Samba support for
@sys substitution, but it simply seems to be the way it is.  Back when I wrote
that code I spoke to some old time users for AFS, and they didn't even realize
it works that way (and went to check that indeed this is the behaviour seen in
AFS).

I have not found any explanation on why it is this way, other than that it
seems this was the easiest way to implement it (when @sys is only allowed by
itself or at the end of a pathname element, you simply copy the part before it
and append the sysname, whereas if it can appear near the front or the middle,
you need to copy up to the @sys token, then insert the sysname, and then
append the rest).  Of course, when I wrong my Samba code, I implemented it in
a way where it could appear anywhere in the pathname element, and I can't say
I found that to be difficult to implement :)

	Kris

On Thu, Dec 16, 2004 at 04:31:55PM -0800, mmarion@qualcomm.com wrote:
> I just encountered something that I guess I've never noticed before.
> 
> I had a directory structure setup with:
> gnu64 -> .@sys.gnu64 
> which worked fine for some amd64_linux26 hosts running arla.  Testing openafs
> 1.3.76 today (we need FileServerPrefs to work, which arla doesn't seem to
> support yet) and the gnu64 directory didn't work:
> rs-workstation qct {982}$ ls -l gnu64
> lrwxr-xr-x  1 mmarion root 11 2004-12-16 15:55 gnu64 -> .@sys.gnu64
> rs-workstation qct {983}$ file gnu64
> gnu64: broken symbolic link to `.@sys.gnu64'
> rs-workstation qct {984}$ fs sys
> Current sysname is 'amd64_linux26'
> rs-workstation qct {985}$ ls -ld .amd64_linux26.gnu64/
> drwxrwxrwx  9 root root 2048 2004-09-30 16:21 .amd64_linux26.gnu64/
> 
> Changing it around to .gnu64.@sys instead seems to have fixed it.  I thought
> perhaps it was a dev version issue, but I logged into an ia64_linux24 host and
> it exhibited the same problem on that path, until I changed it.
> 
> Has openafs always preferred links to be:
> .dir.@sys 
> vs
> .@sys.dir
> for some reason?
> 
> I just tested on an older i386_linux24 host, and the same holds true..
> it doesn't like .@sys being first:
> schwarzes001 qct {984}$ mkdir .`sys`.foo
> schwarzes001 qct {987}$ ln -s .@sys.foo foo
> schwarzes001 qct {988}$ file foo
> foo: broken symbolic link to .@sys.foo
> schwarzes001 qct {990}$ mv .i386_linux24.foo .foo.`sys`
> schwarzes001 qct {991}$ rm foo
> schwarzes001 qct {992}$ ln -s .foo.@sys foo
> schwarzes001 qct {993}$ file foo
> foo: symbolic link to .foo.@sys
> 
> 
> 
> -- 
> Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com
> Peggy: "12 years old and drinking a beer!?!"
> Bobby: "I didn't even like it!"
> Hank: "Well now you're just trying to get me mad!" ==> King of the Hill
> 
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel

-- 
Never underestimate a Mage with:
 - the Intelligence to cast Magic Missile,
 - the Constitution to survive the first hit, and
 - the Dexterity to run fast enough to avoid being hit a second time.