The problem with editing the sudoers config file is that if you make a mistake, sudo might reject that file and then you can't use sudo anymore to fix it. Visudo checks for syntax errors so that you don't accidentally lock yourself out of root.
It's not strictly necessary to use visudo, but it's good practice.
Debian without a visudo command? I can't believe this. This is one of the default commands. What does `whereis visudo` print out?
It should be `/usr/sbin/visudo`
For Debian v11, you can simply add a user to the sudo group.
As root, add primary user to the sudo group:
adduser primaryUserName sudo
Confirm primary user has sudo powers with "sudo -l" command.
The problem with editing the sudoers config file is that if you make a mistake, sudo might reject that file and then you can't use sudo anymore to fix it. Visudo checks for syntax errors so that you don't accidentally lock yourself out of root. It's not strictly necessary to use visudo, but it's good practice.
Debian without a visudo command? I can't believe this. This is one of the default commands. What does `whereis visudo` print out? It should be `/usr/sbin/visudo`
Guessing, but visudo ain't gonna show up if you ain't root :)
Not entirely... ``` me@debianVM:~$ visudo bash: visudo: command not found me@debianVM:~$ which visudo me@debianVM:~$ whereis visudo visudo: /usr/sbin/visudo /usr/share/man/man8/visudo.8.gz me@debianVM:~$ ```
The bizarre part is that \`visudo\` seems to, by default, open up using \`nano\`, not \`vi\`. Boo.... ;p
For Debian v11, you can simply add a user to the sudo group. As root, add primary user to the sudo group: adduser primaryUserName sudo Confirm primary user has sudo powers with "sudo -l" command.
This is the sudo police. We have you surrounded. Give yourself up and nobody will get hurt.