zhengda wrote:
[EMAIL PROTECTED] wrote:
Hi,
Well, I must remind you that you were supposed to provide a schedule in
your application... I accepted your not doing so, because the task
description was very unspecific, and you were not really in a position
to provide a schedule without discussing things first; but now that you
have an idea what you will be actually working on, you should be able to
come up with a rough schedule...
I suggest you start with the server overriding mechanism, as it's the
easier part, and there is less to discuss...
-antrik-
Hi,
I think maybe I can set up multiple pfinets and modify glibc as the
exercise and try to finish it next week.
After that, I can go back and work on the mechanism for communication
among different pfinet servers.
Afterwards, I implement other mechanisms for the server overriding.
So the rough schedule could be:
today~June 13rd: the exercise. discuss the mechanism for communication
among different pfinet servers.
June 14th~July 14: implement the mechanism for communication among
different pfinet servers and discuss the server overriding mechanism.
July 15th~August 18: implement the server overriding mechanism.
I hope I leave enough time for the second work (pfinet server
communication).
I have a question:
antrik, you said someone had already implemented the BPF translator,
but where is the code?
I cannot find it in the CVS.
Best,
Zheng Da
Hi,
I have already been able to run mutiple pfinet in my hurd.
and I modified the glibc which now allows the user to override the
default path for pfinet server.
The environment variable for the path of socket servers is "SOCK_SERV_PATH".
It works.
Another interesting thing is that when I ping from one pfinet server to
another, I get the reply.
Does it mean the two pfinets are already able to communicate with each
other?
Back to my real work and I need to change the schedule.
I will implement the server overriding mechanism. and I can make a
choice between options, mainly from option 4 and 5.
(4) Either all filesystem servers could provide a mechanism to modify
the namespace they export to certain clients
(5) proxies could be used that mirror the default namespace but override
certain locations.
Here is my rough schedule:
June 06~June 13: make a choice among all different options for server
overriding mechanism.
June 14~July 07: implement the server overriding mechanism and discuss
about the mechanism for the communication among pfinet servers.
July 08~July 14: test the implementation
July 14~August 11: implement the mechanism for pfinet server
communication. continue testing the first part of work.
August 12~August 18: final test.
Best,
Zheng Da
