Make your OS means changing the operating system you use.
Make your OS means changing the operating system you use.
Guys, don't let this be dull if it worked out. If Bill Gates handed you a thousand developers to build your own OS, you'd probably take it seriously.
Search for the insightful Terry A Davis who constructed God's third temple independently. Temple OS represents a fully operational system created by a single individual, embodying the idea of building something complex without external assistance.
I’d like a personal init system after login, allowing background programs to run smoothly with tools like watchdog or service restarts. Watching for issues is straightforward, but root access is needed for init access, which isn’t ideal. I opted for a simple Python mini-init system—it’s not perfect but works now. I’d also set up a virtual network share where users can mark files as shared via simple checkboxes, publishing them as needed. This lets friends easily replicate your setup and roll back if problems arise, like missing kernel options. Most features are optional extras, but even basic implementations would be valuable. Ideally, these could be part of the OS itself, which would be great for younger users. The login should include Bible Captcha, and I’m still figuring out the right age-appropriate translations—KJV is fine for 18+, but simpler versions suit younger audiences.
Systemd handles this functionality, and I'm sure Windows does as well. Many of my complaints about current operating systems center on limited customization or control (on Windows) or lack of compatibility and fragmentation (Linux). The first is simply a decision by Microsoft, while the second stems from low adoption rates—something you can't overcome just by creating your own OS. On desktop platforms, I'd like to see more emphasis on app sandboxing and detailed permission management, similar to what Android implements. Programs should generally be restricted from having full access to your system unless you explicitly allow it.
Only a limited amount of monitoring and crash reporting is available for system services, not personal ones. This could be handled with SELinux, though it's a necessary task. A good unified SELinux interface and consistent app policies might address this, but it would require significant effort.