summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas Schwinge <tschwinge@gnu.org>2008-03-27 17:07:59 +0100
committerThomas Schwinge <tschwinge@gnu.org>2008-03-27 17:08:34 +0100
commit41d3692a0fff0879c12ca21d859482fb22d6720e (patch)
tree8e6001c0ce1988379de6a3d2a311d19860f61d58
parent83a7d85d60efb36d7dabe98f8ad7e3b82a8708b6 (diff)
community/gsoc/project_ideas (lexical dot-dot resolution): Link to GNU Savannah bug #17133.
-rw-r--r--community/gsoc/project_ideas.mdwn7
1 files changed, 5 insertions, 2 deletions
diff --git a/community/gsoc/project_ideas.mdwn b/community/gsoc/project_ideas.mdwn
index de5df566..af3e9cfa 100644
--- a/community/gsoc/project_ideas.mdwn
+++ b/community/gsoc/project_ideas.mdwn
@@ -647,11 +647,11 @@ any design work, only good debugging skills.
## lexical dot-dot resolution
-For historical reasons, UNIX filesystems have a real (hard) .. link from each
+For historical reasons, UNIX filesystems have a real (hard) `..` link from each
directory pointing to its parent. However, this is problematic, because the
meaning of "parent" really depends on context. If you have a symlink for
example, you can reach a certain node in the filesystem by a different path. If
-you go to .. from there, UNIX will traditionally take you to the hard-coded
+you go to `..` from there, UNIX will traditionally take you to the hard-coded
parent node -- but this is usually not what you want. Usually you want to go
back to the logical parent from which you came. That is called "lexical"
resolution.
@@ -666,6 +666,9 @@ to use lexical resolution, and to check that the system is still fully
functional afterwards. This task requires understanding the filename resolution
mechanism. It's probably a relatively easy task.
+See also [[GNU_Savannah_bug 17133]].
+
+
## secure chroot implementation
As the Hurd attempts to be (almost) fully UNIX-compatible, it also implements a