[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Coyotos vs. EROS
From: |
Justin Emmanuel |
Subject: |
Re: Coyotos vs. EROS |
Date: |
Fri, 28 Oct 2005 09:52:35 +0200 |
OK! I give up.
1) What is an endpoint?
Once I know that I will know what a capability or an IPC endpoint is.
Been searching for this information on the net and I have not so far
come up with anything.
On 28/10/05, Jonathan S. Shapiro <address@hidden> wrote:
> I do not recall if I have described the gap from Coyotos to EROS here. I
> have just updated the comparison page at
>
> http://www.coyotos.org/docs/misc/eros-comparison.html
>
> Surprisingly, the items haven't changed much since I first wrote it. If
> you read the list of changes, what you will conclude is that
>
> a) This is a total kernel rewrite. We can borrow a lot of code and
> ideas from the EROS kernel, but we are touching enough places that
> it really isn't the same kernel.
>
> b) With the exception of endpoints, none of the changes are
> conceptually very large. We have refined various data structures
> and simplified some of them, but the basic ideas and concepts of
> EROS are pretty clearly preserved in Coyotos.
>
> c) A few programs will change significantly because endpoints and
> events will have significant impact on these programs.
>
> The really important thing here is that the basic design model and idiom
> hasn't changed. This means that the intuition and experience we have
> from EROS is very directly applicable in Coyotos.
>
>
> shap
>
>
>
> _______________________________________________
> L4-hurd mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/l4-hurd
>
- Coyotos vs. EROS, Jonathan S. Shapiro, 2005/10/27
- Re: Coyotos vs. EROS,
Justin Emmanuel <=