summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorscolobb <scolobb@web>2009-07-14 17:40:01 +0000
committerGNU Hurd web pages engine <web-hurd@gnu.org>2009-07-14 17:40:01 +0000
commit38e962ec933a6eacfc378477b4efa75f8ea19d07 (patch)
tree29abe6851fcdf0285dae93e7d3abde862561aa77
parent41f759660d5b0ef95d7209810fc3e8fb88bf0576 (diff)
-rw-r--r--user/scolobb.mdwn17
1 files changed, 8 insertions, 9 deletions
diff --git a/user/scolobb.mdwn b/user/scolobb.mdwn
index f30e4415..1f463fba 100644
--- a/user/scolobb.mdwn
+++ b/user/scolobb.mdwn
@@ -102,9 +102,9 @@ For documentation, see [[hurd/translator/unionmount]].
Jul)* Initially the mountee was started at the first lookup. Now it
is started immediately after initialization of `unionmount`.
-* **Fix the patches in ``--mount'' option series** *(5 Jul)* The
- patches have been reviewed by **antrik**. I corrected them and
- posted them to the ML for final reviews.
+* **Fix the patches in `--mount` option series** *(5 Jul)* The patches
+ have been reviewed by **antrik**. I corrected them and posted them
+ to the ML for final reviews.
* **Orphan the mountee after starting it** *(7 Jul)* Orphaning the
mountee after starting it up seems to be a nice work-around for the
@@ -121,6 +121,11 @@ For documentation, see [[hurd/translator/unionmount]].
The new patches I have submitted have been reviewed; also, the older
patches have been reviewed again, which required correcting them.
+* **Add the `--no-mount` option** *(17 Jul)* Using the `--no-mount`
+ and `--mount` options, the user can decide whether unionmount should
+ be completely transparent (i.e. most control-port RPCs forwarded to
+ the mountee) or not.
+
### TODO
(Dates in brackets show the *expected* completion date)
@@ -130,12 +135,6 @@ For documentation, see [[hurd/translator/unionmount]].
has to go away as soon as the mountee has been shut down for some
reason.
-* **Add the command-line options for choosing between the transparent
- and non-transparent unionmounts** *(17 Jul)* Using these options,
- the user will be allowed to decide whether unionmount should be
- completely transparent (i.e. most control-port RPCs forwarded to the
- mountee) or not.
-
* **Proxy the control port of `unionmount`** *(17 Jul)* For
`unionmount` to become transparent, most of the RPCs invoked on the
its control port should be forwarded to the mountee.