Real pros shuffle across the carpet to build a static charge and do their system administration by electrical fault injection.
linuxmemes
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
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.
Doesn't it break a lot of things? Half the stuff refuses to work when some specific files have too permissive chmod.
Really only SSH and sudo broke. sudo would still work but you'd have to re-enter your password every time. It was a painful experience and I'm glad I know better now.
Goodbye ssh access
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.
Jesus, every time I have to run glx or vaapi under a container I end up having to do this then cringe.
Come on! I've stopped logging on as root, can't we just leave it at that?
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.
Could you not just use root to give your user sudo? Seems like a pretty dumb restriction
sudo steam
then at first day of work:
just use sudo su, we don't have all day here.
I'm in jail because I was not in the sudoer file
This incident was, in fact, reported.
Well, you were warned 🤷.
Sometimes your package manager asks you for root password every minute while doing few hours long update and cancelling process if you don't enter anything for few minutes, "yay" aur manager looking at you, and you got to do other things than sit and look in the monitor all day long, things like cleaning house or touching grass for example
sudo visudo
At the end:
Defaults:USER timestamp_timeout=30
USER is obviously changed to your username.
Thank you
If I remember correctly the default sudo timeout is set to 5 minutes on Yay, you should be able to increase it to something more reasonable
Reminds me of all of those vendors that require Windows Admin for no reason.
sudo -s
for auditability
Our crappy vendor software will only function if IPv6 is disabled network wide. Even if one machine has it enabled, the whole thing breaks
Lol our former crappy vendor solution required to be run directly from AD Administrator. Pure luck the entire business didn't collapse before we replaced it.
A thread I read a long time ago on r/sysadmin
That's at least once a week
Reminds me of software saying to put your docker socket into the docker container you are starting for convenience.
Wasn't it 2017 where they had the race condition in sudo su
as the command elevates up to root and drops back down?
Every other year, sudo su
was not unsafe but merely ghetto. 'sudo su' is the dutch-rudder of 'sudo'.
run0
is the new sudo su
You're going to start a fight with the doas
people.
sudo !!
:p
sudo vi
Yeah. After that everything can be done with !sh
.
(Edit: This is a joke. There's a lot of reasons not to do this.)
sudoedit is what you're looking for. Don't elevate the text editor.
Tell me you use Ubuntu without telling me you use Ubuntu.
Wait till you try this on Debian or non Ubuntu variants.
sudo -i ?
sudo su -c "man man"