diff options
Diffstat (limited to 'user/scolobb.mdwn')
| -rw-r--r-- | user/scolobb.mdwn | 59 |
1 files changed, 45 insertions, 14 deletions
diff --git a/user/scolobb.mdwn b/user/scolobb.mdwn index 76b72864..610937ae 100644 --- a/user/scolobb.mdwn +++ b/user/scolobb.mdwn @@ -98,26 +98,57 @@ For documentation, see [[hurd/translator/unionmount]]. `gcc-4.3`, I got strange behaviour of pfinet and spend a week trying to figure out the reason. +* **Try to start the mountee during initialization of `unionfs`** *(4 + 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. + +* **Orphan the mountee after starting it** *(7 Jul)* Orphaning the + mountee after starting it up seems to be a nice work-around for the + necessity of keeping a proxy node in unionmount in simple + use-cases. It is possible that this functionality will provided as a + 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`. + +* **Fix the patches the have already been commented on** *(14 Jul)* + 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** *(14 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. + +* **Make `unionmount` go away when the mountee goes away** *(14 Jul)* + `unionmount` makes sense only while the mountee is running, so it + has to go away as soon as the mountee has been shut down for some + reason. + +* **Proxy the control port of `unionmount`** *(14 Jul)* For + `unionmount` to become transparent, most of the RPCs invoked on the + its control port should be forwarded to the mountee. + ### TODO (Dates in brackets show the *expected* completion date) -* **Try to start the mountee during initialization of `unionfs`** *(4 - Jul)* Presently the mountee is started at the first lookup, although - it is desirable to have it started during the initialization of - `unionmount`. - -* **Fix the patches in ``--mount'' option series** *(4 Jul)* The - patches have been reviewed by **antrik** so they have to be - corrected. +* **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. -* **Read the relevant code of `devnode`, `eth-multiplexer`, and - `pfinet`.** *(6 Jul)* At the moment a part of `devnode` - functionality appears in `eth-multiplexer` and (probably) because of - this, `devnode` cannot use `eth-multiplexer`'s pseudo master device - port. I'll have to figure out why it happens like that. +* **Try to make `eth-multiplexer` work with statically set instances + of `devnode`** *(18 Jul)* At the moment statically set `devnode` + translators fail to run when they try to obtain the pseudo master + device ports from the `eth-multiplexer`. -* **Implement merging rules.** *(25 Jul)* I will have to make the +* **Implement merging rules.** *(30 Jul)* I will have to make the merging of the virtual filesystem published by `eth-multiplexer` and the real filesystem containing static nodes possible. |