diff options
Diffstat (limited to 'hurd/translator')
| -rw-r--r-- | hurd/translator/examples.mdwn | 4 | ||||
| -rw-r--r-- | hurd/translator/pflocal.mdwn | 5 | ||||
| -rw-r--r-- | hurd/translator/unionfs.mdwn | 8 |
3 files changed, 11 insertions, 6 deletions
diff --git a/hurd/translator/examples.mdwn b/hurd/translator/examples.mdwn index 4947808e..69f15c02 100644 --- a/hurd/translator/examples.mdwn +++ b/hurd/translator/examples.mdwn @@ -1,4 +1,4 @@ -[[!meta copyright="Copyright © 2007, 2008, 2013 Free Software Foundation, +[[!meta copyright="Copyright © 2007, 2008, 2013, 2014 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable @@ -92,4 +92,4 @@ To join "foo/" "bar/" and "baz/" in the directory "quux/", just do: $ settrans -capfg quux/ /hurd/unionfs foo/ bar/ baz/ If you want to join even quux/ contents in the union itself, add `-u` as a translator argument. -You can add filesystems at run-time with the `fsysopts` command. +You can add filesystems at run-time with the [[fsysopts]] command. diff --git a/hurd/translator/pflocal.mdwn b/hurd/translator/pflocal.mdwn index 6cb01e18..13b5e01b 100644 --- a/hurd/translator/pflocal.mdwn +++ b/hurd/translator/pflocal.mdwn @@ -67,3 +67,8 @@ implementation). <braunr> being faster isn't the side effect itself ;p <braunr> nice, sudo was bugged on linux too, its behaviour matched its hurd version perfectly + + +## [[hurd/fsysopts]] + +Doesn't support [[hurd/fsysopts]]. 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. |
