My user account doesnt have sudo despite being in sudoers. I cant run new commands i have to execute the binary. Grub takes very long to load with "welcome to grub" message. I just wanted a stable distro as arch broke and currupted my external ssd
My user account doesnt have sudo despite being in sudoers. I cant run new commands i have to execute the binary. Grub takes very long to load with "welcome to grub" message. I just wanted a stable distro as arch broke and currupted my external ssd
why do you want to use sudo? As normal user you can run most of commands. If you are the only one user do not need sudo, use "su" instead with the admin password.
It's bad practice to stay in a root shell because it's easy to screw up and break something. That's why sudo exists… you only run something privileged if it absolutely has to.
Just to be pedantic you could use su -c "$command"
Can not screw up and break things with sudo?
Pretty sure most people just use sudo for everything if they aren't a sysadmin, I use sudo and almost never touch su unless I'm recovering from a major screwup
You also have
sudo -s, which is similar tosu.Some distros set up
sudoby default, and some don't. I started out on Red Hat, back in the 1990s, and I don't believe that they set up sudo by default; the norm there, at least at the time, was tosu. Ubuntu, as I recall, installssudoand I believe configures it to grant sudo access to the user account who did the installation. There, the convention is to kindasudo. I can't recall whether the default is passwordless, though.I don't think that using either is a horrendously bad practice. I tend to set up sudo in password-requiring mode and use
sudothese days, but I wouldn't blink an eye at usingsueither.I think that the most-significant security concern with
suis that you can leave a root shell lying around if you walk away from your computer, and whilesudomay reduce the frequency with which that happens – if one is prone to walking away from their computer and leaving it unlocked in the first place – you can do that withsudo -sas well, which I certainly use, so…shrugs Plus, if you havesudoset up with passwordless root access, any shell is functionally a root shell anyway. And, frankly, if someone has physical access to a system, most people don't bother to lock down their system against settinginit=/bin/shon the kernel command line in GRUB, passwording their BIOS and restricting it from booting from alternate boot media, etc, so…I am not a sysadmin, jus user since 2000. I think if you ever need to do something with sudo it will be as dangerous as using su.