[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

GNU Hurd SoC projects

From: Wei Shen
Subject: GNU Hurd SoC projects
Date: Sat, 24 Mar 2007 18:00:24 +0800

Ok, I would like to try it. Here are my preliminary thoughts:
I think there are at least three solutions:
1) Modify each default server that needs to support overriding. A default server should check wether it should redirect a service call to an overriding server.
It is the current solution of exec server (task #6611). However, the shortage is obvious - the modification locates in every server, though the process of checking and redirecting can be encapsulated in a shared lib or header file.
2) Let the root fs server judge which server port to return on a specific name qurry.
The performance influence on name qurries of this solution needs evaluation. 
3) Modify hurd_file_name_lookup function in the C lib. If necessary, replace the default sever name to the name of an overiding server before qurring the root fs.
There may be performance and security problems.
For extensibility considerations, I perfer a centralized solution, especially solution 2). However, a further investigation is required to get a final conclusion.
For security concerns as noted in task #6612, a mechanism to control the use of server overriding is needed. This task actually is about designing a framework for service multi-instance.

Wei Shen
On 3/23/07, Thomas Schwinge <tschwinge@gnu.org > wrote:
Hello Wei Shen!

Thanks for your interest!

> I choose a task from your task list: *task
> #6612*<http://savannah.gnu.org/task/?6612>:
> Overriding the system's default servers, and wonder whether I can apply for
> it as a SoC project.

Sure, you can apply for it.  I can -- of course -- give no guarantees
that your application will finally be accepted, but without giving it a
try we'll never know.  :-)

If you want access to a GNU/Hurd system, but have difficulties with
getting it installed, then please see here:
< http://www.gnu.org/software/hurd/devel.html#machinery>.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]