summaryrefslogtreecommitdiff
path: root/user
diff options
context:
space:
mode:
authorscolobb <scolobb@web>2009-07-16 13:24:53 +0000
committerGNU Hurd web pages engine <web-hurd@gnu.org>2009-07-16 13:24:53 +0000
commitaa0a2173333bc148991c92c67bc26d488f82c408 (patch)
tree8ab53685835551189c71acb85a779ceceb5b4c8d /user
parentd5616131e5784e421b5203f8d1e27c557c64ce3c (diff)
Diffstat (limited to 'user')
-rw-r--r--user/scolobb.mdwn14
1 files changed, 10 insertions, 4 deletions
diff --git a/user/scolobb.mdwn b/user/scolobb.mdwn
index 5496de36..e322c930 100644
--- a/user/scolobb.mdwn
+++ b/user/scolobb.mdwn
@@ -135,14 +135,20 @@ For documentation, see [[hurd/translator/unionmount]].
`unionmount` to become transparent, most of the RPCs invoked on the
its control port should be forwarded to the mountee.
+* **Fix adding filesystems to `unionmount`** *(16 Jul)* `settrans -a
+ foo unionfs -a <dir> -u -t <translator>` worked, but `settrans -a
+ foo unionfs -u -t <translator> -a <dir>` didn't. The problem was
+ that in a series of rebase operations I accidentally left the
+ "Orphan the mountee" commit out and the problem appeared when the
+ `start_mountee` function tried to attach the mountee. Of course,
+ this is not the definite solution, since I don't know why should the
+ attempt to attach the mountee work in the former case and fail in
+ the latter, but I will leave the investigation for some future time.
+
### TODO
(Dates in brackets show the *expected* completion date)
-* **Fix adding filesystems to `unionmount`** *(16 Jul)* At the moment
- `settrans -a foo unionfs -a <dir> -u -t <translator>` works, but
- `settrans -a foo unionfs -u -t <translator> -a <dir>` doesn't.
-
* **Create the patch for supplying the mountee with a port to the
underlying node of unionfs** *(17 Jul)* Such functionality should
make `unionmount` even more transparent.