UNIX.

11 files changed, 37 insertions, 12 deletions

diff --git a/hurd/faq/gramatically_speaking.mdwn b/hurd/faq/gramatically_speaking.mdwn
index f6073376..7aa3edac 100644
--- a/hurd/faq/gramatically_speaking.mdwn
+++ b/hurd/faq/gramatically_speaking.mdwn
@@ -11,7 +11,7 @@ is included in the section entitled
 
 [[meta title="Grammatically speaking, what is the Hurd?"]]
 
-*Hurd*, as an acronym, stands for *Hird of Unix-Replacing Daemons*.  *Hird*, in
+*Hurd*, as an acronym, stands for *Hird of [[Unix]]-Replacing Daemons*.  *Hird*, in
 turn, stands for *Hurd of Interfaces Representing Depth*.
 
 We treat *Hurd* as a title rather than as a proper name: it requires an
diff --git a/hurd/faq/slash_usr_symlink.mdwn b/hurd/faq/slash_usr_symlink.mdwn
index d78913fb..6fa6c58d 100644
--- a/hurd/faq/slash_usr_symlink.mdwn
+++ b/hurd/faq/slash_usr_symlink.mdwn
@@ -11,7 +11,7 @@ is included in the section entitled
 
 [[meta title="Why is `/usr' a symbolic link to `.'?"]]
 
-The distinction between `/` and `/usr` has historical reasons.  Back when Unix
+The distinction between `/` and `/usr` has historical reasons.  Back when [[Unix]]
 systems were booted from two tapes, a small root tape and a big user tape.
 Today, we like to use different partitions for these two spaces.  The Hurd
 throws this historical garbage away.  We think that we have found a more
diff --git a/hurd/networking.mdwn b/hurd/networking.mdwn
index bc33769a..6ed031ed 100644
--- a/hurd/networking.mdwn
+++ b/hurd/networking.mdwn
@@ -16,7 +16,7 @@ where `N` is the numberic value fo the `PF_*` symbol.  Right now
 
 User programs open those files, and use the `socket_create` [[RPC]] to make a
 new socket.  With that socket, they can use the other `socket_*` RPCs and also
-the `io_*` RPCs.  The `socket_*` RPCs are essentially clones of the Unix
+the `io_*` RPCs.  The `socket_*` RPCs are essentially clones of the [[Unix]]
 syscalls in question.
 
 The only exception is `sockaddrs`, which are implemented as [[ports|libports]]
diff --git a/hurd/ng/part2systemstructure.mdwn b/hurd/ng/part2systemstructure.mdwn
index 4ce8026f..0f94ff2a 100644
--- a/hurd/ng/part2systemstructure.mdwn
+++ b/hurd/ng/part2systemstructure.mdwn
@@ -38,7 +38,12 @@ It is clear from this description that the child's existance is completely deter
 
 ## <a name="Canonical_Process_Destruction"> Canonical Process Destruction </a>
 
-Process destruction can be done either cooperatively, or forcibly. The difference corresponds approximately to the difference between SIGTERM and SIGKILL in Unix. To destroy a process cooperatively, a request message is sent to a special capability implemented by the child process. The child can then begin to tear down the program, and at some time send a request back to the parent process to ask for forced process destruction.
+Process destruction can be done either cooperatively, or forcibly.  The
+difference corresponds approximately to the difference between SIGTERM and
+SIGKILL in [[Unix]].  To destroy a process cooperatively, a request message is
+sent to a special capability implemented by the child process.  The child can
+then begin to tear down the program, and at some time send a request back to
+the parent process to ask for forced process destruction.
 
 Forced process destruction can be done by the parent process without any cooperation by the child process. The parent process simply destroys the primary container of the child (this means that the parent process should retain the primary container capability).
 
@@ -84,7 +89,13 @@ I will now describe some common applications that need to be supported, and how
 
 ## <a name="System_Services"> System Services </a>
 
-Unix-style suid applications have been proposed as one application for alternative process construction mechanisms. However, suid applications in Unix are, from the perspective of the parent, not confined, only isolated. Thus, they are readily replaced by a system service that is created by the system software, and that runs as a sibling to any user process. Only the ability to invoke the system service needs to be given to the user, not the ability to instantiate it.
+[[Unix]]-style suid applications have been proposed as one application for
+alternative process construction mechanisms.  However, suid applications in
+Unix are, from the perspective of the parent, not confined, only isolated.
+Thus, they are readily replaced by a system service that is created by the
+system software, and that runs as a sibling to any user process.  Only the
+ability to invoke the system service needs to be given to the user, not the
+ability to instantiate it.
 
 In fact, no gain can derived from letting the user instantiate system services. In Unix, system services run on durable resources, which the user can not revoke. Thus, the system service needs to acquire its resources from a container that is not derived from the user's primary container.
 
diff --git a/hurd/ng/usecaseprivatekeys.mdwn b/hurd/ng/usecaseprivatekeys.mdwn
index 612a8f25..3cb65af2 100644
--- a/hurd/ng/usecaseprivatekeys.mdwn
+++ b/hurd/ng/usecaseprivatekeys.mdwn
@@ -1,6 +1,10 @@
 _Private Keys_ as used by SSH servers, clients and generally by any cryptographic software need to be stored and manipulated securely. These may get replaced with smartcards soon, but in the mean time it appears to be an interesting use case.
 
-All Unix systems that I am aware of do not allow secrets to be protected in a manner that I would feel is appropiate. A users compromised web browser could either read your private key file or talk to the very popular ssh-agent program and get your secrets out (not sure how popular distributions are configured, but it can be done).
+All [[Unix]] systems that I am aware of do not allow secrets to be protected in
+a manner that I would feel is appropiate.  A users compromised web browser
+could either read your private key file or talk to the very popular ssh-agent
+program and get your secrets out (not sure how popular distributions are
+configured, but it can be done).
 
 The requirements so far are:
 
diff --git a/hurd/ng/usecaseuserfilesystem.mdwn b/hurd/ng/usecaseuserfilesystem.mdwn
index 6dce5670..4e4fdf35 100644
--- a/hurd/ng/usecaseuserfilesystem.mdwn
+++ b/hurd/ng/usecaseuserfilesystem.mdwn
@@ -3,7 +3,7 @@
 These appear as _translators_ in the current Hurd and something similar needs to appear in the next hurd.
 
 * The user should be able to dynamically add and remove translators
-* For some reason it seems appropiate to have seperate namespaces (VFS's) for each user (this is quite a departure from Unix. [[SamMason]])
+* For some reason it seems appropiate to have seperate namespaces (VFS's) for each user (this is quite a departure from [[Unix]]. [[SamMason]])
 * translators can be used to expose the structure of an archive file
 * translators can be provide access to remote file systems
 
diff --git a/hurd/running/gnu.mdwn b/hurd/running/gnu.mdwn
index 322597ec..2ae2f2ca 100644
--- a/hurd/running/gnu.mdwn
+++ b/hurd/running/gnu.mdwn
@@ -2,7 +2,12 @@
 
 # <a name="The_GNU_Operating_System"> </a> The GNU Operating System
 
-The GNU Operating System, or GNU System as it is more commonly known, will be a complete Unix-like operating system composed entirely of [free software](http://www.gnu.org/philosophy/free-sw.html). The creation of the GNU System is one of the goals of the [GNU Project](http://www.gnu.org/), which was [launched in 1983](http://www.gnu.org/gnu/initial-announcement.html) by [Richard Stallman](http://www.stallman.org/). 
+The GNU Operating System, or GNU System as it is more commonly known, will be a
+complete [[Unix]]-like operating system composed entirely of [free
+software](http://www.gnu.org/philosophy/free-sw.html).  The creation of the GNU
+System is one of the goals of the [GNU Project](http://www.gnu.org/), which was
+[launched in 1983](http://www.gnu.org/gnu/initial-announcement.html) by
+[Richard Stallman](http://www.stallman.org/).
 
 
 
diff --git a/hurd/running/gnu/gnu.mdwn b/hurd/running/gnu/gnu.mdwn
index 22bb5161..2a3629d7 100644
--- a/hurd/running/gnu/gnu.mdwn
+++ b/hurd/running/gnu/gnu.mdwn
@@ -2,7 +2,12 @@
 
 ## <a name="GNU_FSF_amp_RMS"> </a> GNU, FSF &amp; RMS
 
-GNU stands for GNU's Not Unix. It is a project announced in 1983 by [[RichardStallman]] (RMS). The Free Software Foundation ([FSF](http://www.fsf.org/fsf/fsf.html)) was founded in 1985 to act as a parent organization for GNU and many other projects. GNU and some non-GNU projects are now hosted on the [Savannah](http://savannah.gnu.org) platform similar to SourceForge.net.
+GNU stands for GNU's Not [[Unix]].  It is a project announced in 1983 by
+[[RichardStallman]] (RMS).  The Free Software Foundation
+([FSF](http://www.fsf.org/fsf/fsf.html)) was founded in 1985 to act as a parent
+organization for GNU and many other projects.  GNU and some non-GNU projects
+are now hosted on the [Savannah](http://savannah.gnu.org) platform similar to
+SourceForge.net.
 
 <dl>
 <dt>[[History]]</dt>
diff --git a/hurd/running/gnu/names.mdwn b/hurd/running/gnu/names.mdwn
index d470a632..fcab6a11 100644
--- a/hurd/running/gnu/names.mdwn
+++ b/hurd/running/gnu/names.mdwn
@@ -1,4 +1,4 @@
-The GNU stands for GNU's Not Unix. It is a project as described in [[GNU]].
+The GNU stands for GNU's Not [[Unix]].  It is a project as described in [[GNU]].
 
 What can be confusing is the usage. GNU can stand for:
 
diff --git a/hurd/running/qemu.mdwn b/hurd/running/qemu.mdwn
index 3a9784f7..1cf149bd 100644
--- a/hurd/running/qemu.mdwn
+++ b/hurd/running/qemu.mdwn
@@ -1,4 +1,4 @@
-This page discusses things for Unix systems, there is a separate page for
+This page discusses things for [[Unix]] systems, there is a separate page for
 [[Microsoft_Windows]] systems.
 
 
diff --git a/hurd/translator.mdwn b/hurd/translator.mdwn
index 9cdd8a31..b9952931 100644
--- a/hurd/translator.mdwn
+++ b/hurd/translator.mdwn
@@ -26,7 +26,7 @@ that to access the indiviudal resources they use.
 This is primarily the [[backing_store]] and the node
 they attach to.  Typically, a translator can
 only be attached to a node by the node's owner.
-On Unix this is not possible because file systems
+On [[Unix]] this is not possible because file systems
 and the virtual file system are implemented in the
 kernel and thus have absolute access to the machine.
 As the protocols do not require any special privilege