Benefit

Users migrating from the vast majority of distros, or even first time users who have just gained a cultural understanding of sudo from others, will be confused when they attempt to use sudo and are met with sudo: command not found. This doesn't provide them with any information on how to proceed without sudo, and if their instincts lead them astray, they may simply try to install sudo rather than finding out about run0.

Solution

When running sudo in an interactive terminal will result in a 127 error code (command not found), show a message clarifying that sudo is not installed, and the user should try using run0 instead and see if it works for their usecase.

Alternatives

Simply aliasing sudo to run0. However, run0 is not a 1:1 replacement for sudo, so this could cause unintended breakage, leading to possibly worse confusion.

Declaration

• I agree to follow this project's Code of Conduct.
• I declare that this is not a request for alternate community messaging or social platforms.
• I declare that I have read the secureblue website and my feature request is in-scope.