diff options
| -rw-r--r-- | user/scolobb.mdwn | 23 |
1 files changed, 19 insertions, 4 deletions
diff --git a/user/scolobb.mdwn b/user/scolobb.mdwn index aae646da..a17e3bad 100644 --- a/user/scolobb.mdwn +++ b/user/scolobb.mdwn @@ -98,16 +98,31 @@ 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. + ### TODO (Dates in brackets show the *expected* completion date) -* **Fix the patches in ``--mount'' option series** *(4 Jul)* The - patches have been reviewed by **antrik** so they have to be - corrected. +* **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. * **Read the relevant code of `devnode`, `eth-multiplexer`, and - `pfinet`.** *(6 Jul)* At the moment a part of `devnode` + `pfinet`.** *(14 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. |