In a lot of situations it’s actually bad to use sudo because it can impact settings that make programs or file ownership go to root instead of the user.
You’ve got to be a damn idiot jumping over his own shadow to get that done. How would you even do that? Running
chown -R root.root
over directories or mount points? Deleting files in /dev or /run and recreating them using “touch” without looking up ownerships before? I wrote “touch” because anyone proceeding to “mknod” would at least have read some man pages. BTW, you’d need su for that rather than sudo.
Shut the front door!
In a lot of situations it’s actually bad to use sudo because it can impact settings that make programs or file ownership go to root instead of the user.
You’ve got to be a damn idiot jumping over his own shadow to get that done. How would you even do that? Running
chown -R root.rootover directories or mount points? Deleting files in /dev or /run and recreating them using “touch” without looking up ownerships before? I wrote “touch” because anyone proceeding to “mknod” would at least have read some man pages. BTW, you’d need su for that rather than sudo.
makepkg won’t even run as root iirc
sudo -i -u user -s /usr/bin/bash