[Top][All Lists]

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

Re: L4Hurd at Sourceforge

From: Farid Hajji
Subject: Re: L4Hurd at Sourceforge
Date: Tue, 23 Oct 2001 02:38:00 +0200 (CEST)

> What are the advantages of Savannah?
That is the official repository for FSF-owned code. It's the home of
the Hurd ;-)

> As for GNU coding standards, I think the main argument they make for C
> is portability and a large developer base. It seems to me that our
> interface for this project is L4, so anything that "talks" L4 is fine,
> regardless of what it's written in.
L4 is _defined_ in terms of primitives it provides. If you look at the
defining documents, you'll see that:
  1. the primitives are (nearly) the same, regardless of the architecture,
  2. you get pro architecture (x86, mips, ...) a different set of syscalls,
     which implement the primitives.
More importantly, the L4 APIs are currently binary API (or if you prefer,

What is important to us here is:
  a. that we will use the c-bindings of a particular L4 implementation,
  b. that we will strive to use a _common_ c-binding that is available
     to all currently available L4 implementations.

The current API (as well as the corresponding C-bindings) is in the
process of moving from X.0/X.1 towards a new version that is not yet
publicly released. Any comments on this from the L4 people would be
greatly appreciated. Could be we a _preliminary_ (non definitive view)
of the upcoming API, including C-bindings? That would be very helpful
right now.

> I think writing our own L4 variant is a bit extreme. My vision for this
> project is to refactor the Hurd to be able to run on L4. Until we have
> that, I don't see much need for another L4 kernel out there.


Farid Hajji -- Unix Systems and Network Admin | Phone: +49-2131-67-555
Broicherdorfstr. 83, D-41564 Kaarst, Germany  | address@hidden
- - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - -
One OS To Rule Them All And In The Darkness Bind Them... --Bill Gates.

reply via email to

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