This video goes over how to use sudo su root or use sudo no password to avoid getting prompted all the time. It covers why people new to Linux like to use sudo su and why this messes up their installs.
Commands:
Switch to Root user
# sudo su
Change your user to auto elevate without password in sudo visudo
# sudo visudo
—–APPEND either of the following——
–CHANGE USER—– myuser ALL=(ALL) NOPASSWD:ALL
–CHANGE GROUP– %usergroup ALL=(ALL) NOPASSWD:ALL .
►► Digital Downloads ➜ https://www.cttstore.com
►► Patreon ➜ https://www.patreon.com/christitustech
►► Twitch ➜ https://www.twitch.tv/christitustech
►► Website and Guides ➜ https://christitus.com
change user not to use password for sudo things AT ALL ? :0
Nice concise explaination.
In der Beschreibung wird deutsch geschrieben und dann ist das komplette Video auf Englisch, was soll der Mist
thank you. Good explanation
What is the meaning of sudo -u oracle -i?
Good video, but for me, thanks, but no thanks. I'd rather type it in 20k times, the benefits are big for the effort that is comparatively small. I suppose changing that with a script in Path and forcing a script to return to default on boot is a valid solution. Requiring you to compromise your security only while installing packages.
Do you mean you have to type your sudo pswd every time you used it? because if I have a terminal window that I typed the sudo password in, even if use sudo again it won't prompt me for a pswd for at least 15-25mins. In that terminal window.
What about without sudo?
You only need -get after apt pre reload or specify outside of apt.sources
When I even type ''sudo su'' I always get to the point where I have to type my password in. When I type it in the correct way it says ''(my username) is not in sudoers file. This incident will be reported.'' Like, what do I actually do as I am new to linux. Even if I run your command ''sudo nano /ect/sudoers'' I still get the same thing when I type in my password.
this guy is so helpful to new linux users. what a nice guy. not a pretentious linux deuche
Thanks for the help! I've saved the link to this video in my browser. I started using computers in the DOS days, so Terminal is familiar to me. Even some of the commands are the same; just the modifiers are different.
Bro, how have you got PhotoShop on there? Is that WINE or something else?
@Chris Titus Tech OK I have a question for you. In an enterprise environment, how do i manage user sudo rights from a Windows Active Directory? I'm guessing that I need to set X commands to only be run by DOMAIN group, then add users to that group from ADUC. is that the best way to do this? editing SUDO directly for each user on each box is cool if you only have 3 boxes. but if you have 50 boxes……… o my.
How you highlight commands like "ALL" to red color?
Love this intro music man, you have a link?
Hey Chris, an experienced user can edit sudoers with any editor but, as for the beginners, the recommended and safer way to edit sudoers is via: sudo visudo. This will prevent them from commiting syntax errors because if you put a single comma in a wrong place, you can break sudo and then they are going to have troubles restoring it.
HO LEE CHIT! YOU DA MAN!… er… YOU DAEMON!
Thank you this really helped me. That was fast and easy.
Good tip and advice. Thanks. When I would do server admin I normally would ssh in as root (using private key always). I'd very rarely login as non-root account. On desktop in home environment will use your tip because installing packages and entering PW is a PIA everytime! Also if somebody does install as root and can't access as user they can always chown the file/folder.
If I want to change e.g fstab, I use "sudo gedit /etc/fstab". It is somewhat easier to work with a graphical editor.