I installed the latest update (as of thursday last week) for OpenAFS
1.7.0600 last week on my windows 7 afs client. Everything runs fine until
I get to a symbolic link in my Linux file system. The Windows 7 navigtor
will not follow the symlink, it will not change directory from the command
line either. The navigator seems to think it is a link because it has the
chain symbol on the icon but the icon is faded. I get a message when I
try to follow the symlink that I do not have permission. I have no
trouble traversing the symlink on the linux client I use (don't believe
Linux client is running open afs, I don't own that box, so that last was a
statement that I do have file system permissions, not a difference in
windows versus linux implementations).
This is a new install of the OpenAFS to update my laptop. I can get to
all the files in the file system until I hit a symlink, so everything else
runs really nice. Another possible difference is that its more likely
that access to file system objects that I symlink to is granted via a
group permission, my own files inside the symlink perimeter are more
likely to be accessed via my user id.
Any ideas?
Gary Coryer
