Jacob Gorm Hansen wrote:
> We are currently trying to make L4Linux (linux2.2 running on the L4
> micro kernel) boot several in L4Linux instances.
>
> The good thing about L4 is that it gives us address space protection and
> IPC, but sometimes the 'every linux tasks is an l4 task' way of doing
> things seems a bit much.
>
> We want to be able to migrate entire OSes between machines, and thus we
> cannot trust the OSes to be friendly or correct.
>
> If we had the time, it seems that implementing protection in adeos would
> be interesting and easier to work with than L4 (which is a very nice
> u-kernel btw).
L4 is very interesting indeed. Last I read about it, though, its
licensing was problematic (i.e. couldn't be released "open source"
because of the funding of the project) and it is very hardware dependent
(in order to achieve better performance). Is this still true?
I understand the need to be able to migrate entire OSes between
machines. Because we do not virtualize the physical RAM, this
may a little harder to do with Adeos. But since we assume that
we can modify the OSes to better interact with Adeos, then it
should not be that much harder to implement code that "rewires"
the kernels' mappings. Of course, this would require some work,
and time ... ;)
Cheers,
Karim
===================================================
Karim Yaghmour
[EMAIL PROTECTED]
Embedded and Real-Time Linux Expert
===================================================
