4 ms·
I think the title and the main page are really bad at explaining what IncludeOS actually is. The author probably is trying to impress readers too much. The thi
by esjeon 5y ago
I think the title and the main page are really bad at explaining what IncludeOS actually is. The author probably is trying to impress readers too much.
The thing is, this is something called “unikernel[1]”, which basically can be linked directly into your application. With this, you just boot into your application instead of general-purpose OS like Linux. IIRC, it’s even possible to this on top of another OS. This comes with a lot of benefits, but with a lot of caveats, too.
[1]: https://en.wikipedia.org/wiki/Unikernel https://en.wikipedia.org/wiki/Unikernel
- ksec 5y agoOr the link on the page [Tell me more] [1], >IncludeOS is an operating system written as a library. When building an application, the build system includes the code that would typically reside in your operating system into the application itself. When it is done building a bootloader is added. So, after a successful build, you now have a standalone application that boots without an operating system. The application is now capable of driving the hardware, it has an IP stack and manages its memory. >Unlike more traditional operating systems IncludeOS is meant for single task computers. There is only a single application running. For multiple security domains, we require multiple machines, and we leave the separation task to the hypervisor. They could have just called it Cloud-DOS. [1]https://www.includeos.org/technology.html https://www.includeos.org/technology.html