summaryrefslogtreecommitdiff
path: root/hurd/virtual_file_system.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <tschwinge@gnu.org>2007-09-14 18:23:56 +0200
committerThomas Schwinge <tschwinge@gnu.org>2007-09-14 18:23:56 +0200
commit3a7bbd73c8e364d290175ae5afee60f6d825ea36 (patch)
tree62ba65085f3b4fbb8998b25f13ebcd806b3121aa /hurd/virtual_file_system.mdwn
parentde2e5a00f7be56e07340d37a639f0e21ddd98c93 (diff)
Even more page naming consistency.
Diffstat (limited to 'hurd/virtual_file_system.mdwn')
-rw-r--r--hurd/virtual_file_system.mdwn34
1 files changed, 34 insertions, 0 deletions
diff --git a/hurd/virtual_file_system.mdwn b/hurd/virtual_file_system.mdwn
new file mode 100644
index 00000000..33e4f8a7
--- /dev/null
+++ b/hurd/virtual_file_system.mdwn
@@ -0,0 +1,34 @@
+[[license text="""
+Copyright © 2007 Free Software Foundation, Inc.
+
+Permission is granted to copy, distribute and/or modify this document under the
+terms of the GNU Free Documentation License, Version 1.2 or any later version
+published by the Free Software Foundation; with no Invariant Sections, no
+Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included
+in the section entitled [[GNU_Free_Documentation_License|/fdl.txt]].
+
+By contributing to this page, you agree to assign copyright for your
+contribution to the Free Software Foundation. The Free Software Foundation
+promises to always use either a verbatim copying license or a free
+documentation license when publishing your contribution. We grant you back all
+your rights under copyright, including the rights to copy, modify, and
+redistribute your contributions.
+"""]]
+
+Path names are resolved using a distributed protocol.
+No single entity is responsible for the resolution of
+path names. A file system server (a [[translator]])
+attaches to translators (`fs.defs:file_set_translator`).
+
+When a process resolves an aboslute path, it queries
+its root file system server by invoking the `fs.defs:dir_lookup`
+method in the capability in its root directory slot. The
+file system server resolves as much as it knows about locally
+and when it encounters a translator, it replies to the client
+indicating how much it resolved and where to continue its
+lookup. This continues until the name is fully resolved
+or an error occurs. The same happens for relative path
+names but a different capability is used.
+
+For a more detailed explanation of the protocol, look at the section
+2.2 of the [[critique]].