bug-hurd
[Top][All Lists]
Advanced

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

Re: master's thesis on hurd


From: Neal H. Walfield
Subject: Re: master's thesis on hurd
Date: Fri, 28 Nov 2008 15:46:50 +0100
User-agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (Goj┼Ź) APEL/10.7 Emacs/22.2 (i486-pc-linux-gnu) MULE/5.0 (SAKAKI)

At Thu, 27 Nov 2008 22:58:07 +0100,
Ruben Pollan wrote:
> I'm student of computer engineering on spain. I'm about to finish my degree (5
> years of study). I have to do a master's thesis, I'm interesting on hurd and I
> think will be a good idea do something about hurd.
> 
> I don't have much experience on hurd, I just have user knowledge using a 
> Debian 
> GNU/Hurd. I have some knowledge programming on C, and about operative systems.
> 
> Can you give me some ideas about things that have to be done on hurd?
> 
> Thanks, and sorry if this is not the appropriate list.

I suggest you start by reading these two papers:

  A Critique of the GNU Hurd Multi-server Operating System
  http://walfield.org/papers/200707-walfield-critique-of-the-GNU-Hurd.pdf

  Improving Usability via Access Decomposition and Policy Refinement
  
http://walfield.org/papers/20070104-walfield-access-decomposition-policy-refinement.pdf

They highlight some of the problems with the Hurd and its underlying
design.  Specifically, we identify three general issues: resource
management, security and naming.  I'm doing work on the first in the
context of Viengoos (but it is designed to form a basis for the other
issues as well).  For an overview of resource management in Viengoos,
please read this paper:

  Viengoos: A Framework for Stakeholder-Directed Resource Allocation.
  
http://walfield.org/papers/2009-walfield-viengoos-a-framework-for-stakeholder-directed-resource-allocation.pdf

There are number of interesting projects both on the current version
of the Hurd as well as on as Viengoos.  When you have a better idea of
what sort of issues you want to tackle, feel free to write again.

Neal




reply via email to

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