AT-HE <[EMAIL PROTECTED]> wrote: > if you have a simlink pointing to a directory, chdir to that symlink > dir, and type something with '..', > you access the parent of real directory, not previous simlinked one.
That's the kernel's doing, not bash's. When interpreting pathnames relative to the current working directory, the kernel only cares about where you are, not how you got there. It's been that way for as long as Unix has had symlinks, and changing it now would break a lot of programs that expect the current behavior. paul
