3 ms·
Exokernel was designed to run multiple applications that needn't know of each other's existence, on real hardware. The idea behind an unikernel is to run a sin
by Someone 11y ago
Exokernel was designed to run multiple applications that needn't know of each other's existence, on real hardware.
The idea behind an unikernel is to run a single application on virtual hardware.
Both minimize the OS to only provide what the application(s) on the system need. Exokernel also tried to move as much code as possible from the OS into the applications. Unikernels do not do that, but do minimize what the 'real' OS that runs on the hardware need to do.
And something can easily be 'just another novelty' and 'take off'. Whether unikernels will is anybody's guess, IMO.
- drudru11 11y agoThey are very similar, but your answer hits on a good distinction between them. There was a lot of work in Exokernels to allow them to run multiple libOSs on the same hardware safely and securely. Another distinction was that Exokernels did require a single language. For example, each OS asked for packets using a network interface language. I guess a way to look at it is alluded in another comment I just saw here. Virtual machine hardware was not even a consideration in those days. An exokernel played the role of VMM and libOS. The unikernel technology of today pretty much requires a VMM layer (which is fine).