From 564f3b1b7a1c349f5ce811c15dd71b14543789f3 Mon Sep 17 00:00:00 2001 From: scolobb Date: Tue, 2 Jun 2009 13:12:55 +0000 Subject: --- user/scolobb.mdwn | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-) (limited to 'user') diff --git a/user/scolobb.mdwn b/user/scolobb.mdwn index 4817a002..d2194f49 100644 --- a/user/scolobb.mdwn +++ b/user/scolobb.mdwn @@ -78,12 +78,11 @@ For documentation, see [[hurd/translator/unionmount]]. comments in the sources. The goal is to write a more coherent documentation. -* **Use a different (better?) implementation idea.** It has been - pointed out several times that `unionmount` could be implemented not - by forking off `unionfs`, but by keeping the merging functionality - in a stand-alone module (which could then be used by `unionfs` as - well). Different implementation ideas with their own specific - advantages may also arise in the future. +* **Implement merging rules.** Some details are still awaiting + discovery by me. + +* **Employ `unionmount` in eth-multiplexer.** I still have to scrounge + for details. * **Decide as to location of unionmount.** Presently, `unionmount` is a (local) branch in `unionfs` git repository. The first step of @@ -93,8 +92,12 @@ For documentation, see [[hurd/translator/unionmount]]. since the destinations of `unionfs` and `unionmount` are *similar*, and not identical. -* **Employ `unionmount` in eth-multiplexer.** I still have to scrounge - for details. +* **Use a different (better?) implementation idea.** It has been + pointed out several times that `unionmount` could be implemented not + by forking off `unionfs`, but by keeping the merging functionality + in a stand-alone module (which could then be used by `unionfs` as + well). Different implementation ideas with their own specific + advantages may also arise in the future. --- -- cgit v1.2.3