just worked a job where I did not have privlages to sudo commands. except su. had to sudo su so I could run a script.
Guilty as charged, officer.
Real pros shuffle across the carpet to build a static charge and do their system administration by electrical fault injection.
REAL pros use butterflies!
Still not as bad as
chmod -R 777
.Once had a friend run
sudo chmod -R 777 /
on a (public) Minecraft server we were running back in highschool. It made me die a bit on the inside.As a one time noob I may have done this once or more.
To get one thing working I borked everything.
Understanding permissions is pretty basic. But understanding permission requirements for system and user apps and their config and dirs can be a bit overwhelming at first.
Thinking a little change to make your life simpler will break something else doesn’t always register immediately.
Shit, even recently, wondering why my SSH keys were being refused and realising that somehow i set my private keys world readable.
Thank god SSH checks file and dir permission.
I get tired of typing the same command twice.
helenslunch doesn’t know about
sudo !!
sudo -s
for auditabilitysudo -u root bash
ftwMissing the
-i
.The
-i
is not required.It’s silent.
sudo vi
sudo -s vi &
Yeah. After that everything can be done with
!sh
.sudoedit is what you’re looking for. Don’t elevate the text editor.
run0
is the newsudo su
You’re going to start a fight with the
doas
people.And the people that don’t use systemd.
Come on! I’ve stopped logging on as root, can’t we just leave it at that?