An exokernel just multiplexes resources, similar concept to 'unikernel'
design such as ellcc bare metal project except that unikernels includes the
api within the kernel (as I understand). IMO the best would a single
address space but would require a language that could guarantee safety, you
would still need to the split though to verify that it isn't something that
shouldn't be loaded though. Correct me if I'm wrong.
On Jan 28, 2015 7:41 AM, "stephen Turner" <stephen.n.turner@gmail.com>
wrote:

> so I have found 4 kernel types, exo, mono, mach, hybrid.
>
> the Exo sounds like the way to go but im curious if it could be built to
> work with the existing linux world without rewriting everything for it.
> since i have no programming knowledge im just curious what you guys think
> about it if you have given it any thought.
>
> It is definately the ideal for hypervisors and with what little i have
> read thus far feels like it manages hardware usage like containers but
> without most of the kernel overhead to do so.
>
> Im getting tickled about this exo kernel. think i will go find more on it.
>
> stephen
>