From fdb126c8705db2506120bb06953d3fc76c09334b Mon Sep 17 00:00:00 2001 From: scolobb Date: Fri, 10 Jul 2009 13:26:09 +0000 Subject: --- user/scolobb.mdwn | 18 +++++++----------- 1 file changed, 7 insertions(+), 11 deletions(-) (limited to 'user') diff --git a/user/scolobb.mdwn b/user/scolobb.mdwn index b4b0a42f..75ed692b 100644 --- a/user/scolobb.mdwn +++ b/user/scolobb.mdwn @@ -117,22 +117,18 @@ For documentation, see [[hurd/translator/unionmount]]. (Dates in brackets show the *expected* completion date) -* **Orphan the mountee after starting it** *(10 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`. * **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`.** *(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. +* **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 + device ports from the `eth-multiplexer`. * **Implement merging rules.** *(25 Jul)* I will have to make the merging of the virtual filesystem published by `eth-multiplexer` and -- cgit v1.2.3