diff options
| -rw-r--r-- | user/scolobb.mdwn | 14 |
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. |