Norost B v0.1
Posted: Sun May 15, 2022 8:11 am
Hello,
I'm happy to announce Norost B, my OS project.
Norost B is an object-oriented OS built around a microkernel. It is mainly focused on isolating processes from the rest of the system to improve security, portability & scaling. It achieves this by implementing all I/O operations in terms of objects.
For example, a web server may have a handle to an object representing a directory with files and a handle to another object that accepts incoming TCP connections. The latter object creates a new object for each connection.
I intend to make it useful as a general-purpose OS. I use it to host the OS' website*. I hope to eventually use it for most of my tasks, though I suppose this will only happen very far in the future.
You can find ISOs here. It should work in QEMU and Bochs and also on hardware with legacy / BIOS boot. If you don't add a virtio-net and virtio-blk device I recommend using the no-virtio image to avoid high CPU usage.
* It's running on a nested VM behind an nginx proxy since updating the website would otherwise be a giant PITA.
I'm happy to announce Norost B, my OS project.
Norost B is an object-oriented OS built around a microkernel. It is mainly focused on isolating processes from the rest of the system to improve security, portability & scaling. It achieves this by implementing all I/O operations in terms of objects.
For example, a web server may have a handle to an object representing a directory with files and a handle to another object that accepts incoming TCP connections. The latter object creates a new object for each connection.
I intend to make it useful as a general-purpose OS. I use it to host the OS' website*. I hope to eventually use it for most of my tasks, though I suppose this will only happen very far in the future.
You can find ISOs here. It should work in QEMU and Bochs and also on hardware with legacy / BIOS boot. If you don't add a virtio-net and virtio-blk device I recommend using the no-virtio image to avoid high CPU usage.
* It's running on a nested VM behind an nginx proxy since updating the website would otherwise be a giant PITA.