summaryrefslogtreecommitdiff
path: root/hurd/translator/unionfs.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'hurd/translator/unionfs.mdwn')
-rw-r--r--hurd/translator/unionfs.mdwn8
1 files changed, 4 insertions, 4 deletions
diff --git a/hurd/translator/unionfs.mdwn b/hurd/translator/unionfs.mdwn
index 2fcd1fad..06524f3e 100644
--- a/hurd/translator/unionfs.mdwn
+++ b/hurd/translator/unionfs.mdwn
@@ -1,5 +1,5 @@
-[[!meta copyright="Copyright © 2008, 2009, 2010, 2013 Free Software Foundation,
-Inc."]]
+[[!meta copyright="Copyright © 2008, 2009, 2010, 2013, 2014 Free Software
+Foundation, Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
@@ -116,7 +116,7 @@ one will see the information about the `<translator>`, not the
`unionfs` translator. Although this might seem the only natural way
to do union mounts, one must keep in mind that such transparency
deprives one of the possibility to modify the unioned virtual
-filesystem exported by `unionfs` at run-time (via `fsysopts`).
+filesystem exported by `unionfs` at run-time (via [[fsysopts]]).
One can create a nontransparent union mount with the following command:
@@ -127,7 +127,7 @@ When running
$ fsysopts <node>
one will see the information about the `unionfs` translator. Although
-this way allows modifying the contents of the unioned filesystem
+this way allows [[modifying|fsysopts]] the contents of the unioned filesystem
exported by `unionfs` at runtime, the access to `<translator>` is
blocked.