I'd like to share BoringOS, an independent x86_64 desktop operating system written primarily in C.
This is not a Linux distribution or a customized existing OS. The project is developing its own kernel, userspace, filesystem functionality, USB/xHCI and HID support, process/task architecture, and a native desktop environment called BoringWM.
For developers interested in OSDev and low-level systems programming, it's an interesting project to explore and follow.
I'm particularly interested in hearing from developers with experience in kernel or systems programming:
Which subsystem would you be most interested in contributing to or seeing developed further—kernel architecture, filesystems, USB support, process management, or the desktop environment?
🔗 GitHub: https://github.com/dennishilk/boringos
Top comments (4)
Honestly, I think what makes BoringOS interesting is that it's being built independently from the ground up rather than as another Linux-based project. There's a lot going on, from the kernel and filesystems to USB support and the desktop environment. Curious to know—which part would you personally be most interested in working on or exploring?
For an OS project, I’d prioritize a small, observable process and memory model before broad device coverage. A clear kernel/userspace boundary plus traceable failure paths gives contributors a stable place to add drivers and filesystems without turning early debugging into guesswork.
I think what makes BoringOS interesting is that it's being built independently from the ground up rather than as another Linux-based project. There's a lot going on, from the kernel and filesystems to USB support and the desktop environment.
Building an OS from scratch is seriously impressive. BoringOS looks like a great project for anyone interested in understanding systems at a deeper level. I’d be especially interested in seeing how the kernel architecture and process management evolve. Looking forward to following the project!