4 ms·
I am not sure if you would want to run all your software as ‘root’.
by Koshkin 8y ago
I am not sure if you would want to run all your software as ‘root’.
- Spivak 8y agoJust because a system is single user doesn't mean there can't be a permission system and/or multiple levels of privilege.
- whatshisface 8y agoIf you have a permission system and multiple levels of privilege, why not password-protect the different levels? I guess we would also want to name them. In fact, another cool feature would be remote desktop like Windows has. So we should have permissions, in named groups that you have to know the password to access, and I should be able to log in to them remotely. Sounds like a time-sharing system to me.
- Spivak 8y agoThe user doesn't have multiple levels of privilege, applications do.
- Koshkin 8y agoWhich simply means the application is the user.
- Spivak 8y agoApplications that run under different user-supplied constraints (cpu, memory, syscalls, file access) doesn't really feel much like having different users. Things that are separate users by this definition: - Every VM running under my account. - Every docker container. - Every SELinux process/file type combination. - Every cgroup. - Each CPU ring. - Each call to pledge.
- em-bee 8y agoand wanting to be able to decide by myself which of these should not run under my user account, as opposed to letting the OS designer make that decision is why i can't imagine working on a single user system. call them users or roles, doesn't matter. it is crucial that privilege separation is baked into the core and customizable by the owner of the device. at the moment i only see a mulituser system capable of doing that.
- deleted 8y ago[deleted]