[OpenAFS] problems with file links under Windows XP

[Dan Pritts]

On Thu, Jan 24, 2008 at 08:59:14AM -0500, Jeffrey Altman wrote:
> 
> Also, I would really like to understand the rationale for creating
> a link that includes either ".." or "../..".  Can you provide me an 
> example where this makes sense?

I've done this, albeit in a unix environment.  

We used a software packaging scheme like so (use a monospaced font):

/usr/local/
           pkg/
               foo-1.0/
                       bin/
                       man/
               bar-1.2/
                       bin/
                       man/
           bin/
           man/

So that all files for a given software package, foo-1.0 or bar-1.2
in this example, were located under a single directory tree.

In /usr/local/bin, man, etc., were symlinks to the files in each
package's directory.

Rather than hardcoding the symbolic link like so:

   cd /usr/local/bin
   ln -s /usr/local/pkg/foo-1.0/bin/foo foo

We did it with relative paths like so:

   cd /usr/local/bin
   ln -s ../pkg/foo-1.0/bin/foo foo

using relative paths instead of absolute paths in the links allowed people
to put the packages in different locations on their systems, perhaps
allowing them to use multiple package trees from multiple providers, etc.

danno