OSDev.org

Thanks Roman and omarrx024 for trying it out and leaving a message. It means a lot to me. Thanks also to Kazinsal for graciously setting up a mirror.

Roman, if you don't want to **** up your system, then don't kill init. That said, the system should panic then (due to abnormal exit of init), but there's a bug where init deadlocks the system on exit if it has children remaining.

Sounds like a bad idea. I can just "sudo kill -9 init" to cause a panic. I'd recommend changing this so that kill() can never deliver certain signals to init.

Tested. Great OS. I like your asteroids game!

mariuszp, well, don't do that then. As root you can kill any process, and there's lots of processes besides init you can kill that would **** up your running system. The obvious case is the ext2 filesystem driver which is an user-space filesystem. There'll be more cases as I add more daemons in the future. You can also delete all files. Feels a bit weird to zoom in on this particular issue when there's lots other ways root can mess things up, and you're never going to normally be killing init anyway.

catnikita255, thanks! It means a lot that you tried it out. I like my asteroids game too. The source is included so it's possible to mod it and turn it into something new. I should do that, I have some ideas.

I've also found a bug or cheat in it - pressing B creates second spaceship that follows you, and pressing A creates some kind of black hole.

Windows prevents you killing vital programs started over the " system" user. Even with admin rights, you cannot kill them ( unless you open a task manager for that user but this is tricky )

This is really frustrating. As a almighty user in my system, I want full control over the stupid things I do.
I'm okay with the no init=panic rule.

When you kill the spawner process in Ghost, you can't launch any executable anymore, thus leaving the system unusable. I think it's ok to be able to funk up the system as the root user.

Yep. Those are features.

Cognative dissonance?