diff options
| -rw-r--r-- | user/scolobb.mdwn | 16 |
1 files changed, 13 insertions, 3 deletions
diff --git a/user/scolobb.mdwn b/user/scolobb.mdwn index 75ed692b..103b213f 100644 --- a/user/scolobb.mdwn +++ b/user/scolobb.mdwn @@ -113,18 +113,28 @@ For documentation, see [[hurd/translator/unionmount]]. separate patch (without inclusion in master) should it turn out that orphaning the mountee is a bad idea. +* **Decide which RPCs should be forwarded to the mountee and how this + should happen** *(10 Jul)* This is the primary requirement in being + able to proxy the control port of `unionmount`. + ### TODO (Dates in brackets show the *expected* completion date) -* **Decide which RPCs should be forwarded to the mountee and how this - should happen** *(10 Jul)* This is the primary requirement in being - able to proxy the control port of `unionmount`. +* **Add the command-line options for choosing between the transparent + and non-transparent unionmounts** *(10 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`** *(10 Jul)* It was agreed that `unionmount` be completely transparent, therefore a number of RPCs on the control port should be forwarded to the mountee. +* **Create the patch for supplying the mountee with a port to the + underlying node of unionfs** *(10 Jul)* Such functionality should + make unionmount even more transparent. + * **Try to make `eth-multiplexer` work with statically set instances of `devnode`** *(14 Jul)* At the moment statically set `devnode` translators fail to run when they try to obtain the pseudo master |