diff options
author | scolobb <scolobb@web> | 2009-07-16 19:52:22 +0000 |
---|---|---|
committer | GNU Hurd web pages engine <web-hurd@gnu.org> | 2009-07-16 19:52:22 +0000 |
commit | 851f0c887ba0dd4e596d44b6dea57f20e465d882 (patch) | |
tree | 27e633cfb636b089b099236146a5c384a9cc038c /user | |
parent | aa0a2173333bc148991c92c67bc26d488f82c408 (diff) |
Diffstat (limited to 'user')
-rw-r--r-- | user/scolobb.mdwn | 20 |
1 files changed, 5 insertions, 15 deletions
diff --git a/user/scolobb.mdwn b/user/scolobb.mdwn index e322c930..c97359f1 100644 --- a/user/scolobb.mdwn +++ b/user/scolobb.mdwn @@ -158,25 +158,15 @@ For documentation, see [[hurd/translator/unionmount]]. translators fail to run when they try to obtain the pseudo master device ports from the `eth-multiplexer`. -* **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. +* **Employ `unionmount` in `eth-multiplexer`.** *(1 Aug)* `unionmount` + will have to merge the dynamic filesystem of `eth-multiplexer` with + the directory tree it will be sitting on. The latter directory tree + will contain static nodes with `devnode` translators. -* **Wrap up the project for upstream inclusion.** *(1 Aug)* +* **Wrap up the project for upstream inclusion.** *(5 Aug)* `unionmount` is intended to be included upstream, therefore it should be mostly complete and polished by the end of GSoC. -* **Decide as to location of unionmount.** *(1 Aug)* Presently, - `unionmount` is a (local) branch in `unionfs` git repository. The - first step of publishing it is planned to be pushing it to the - Savannah `unionfs` repository. Some agree that there should also be - a second step consisting in splitting `unionmount` in a separate git - repository, since the destinations of `unionfs` and `unionmount` are - *similar*, and not identical. - -* **Employ `unionmount` in eth-multiplexer.** *(10 Aug)* I still have - to scrounge for details. - * **Use a different (better?) implementation idea.** *(17 Aug)* It has been pointed out several times that `unionmount` could be implemented not by forking off `unionfs`, but by keeping the merging |