Had an idiot “fix” a permission problem by running “sudo chmod -R 777 /”
And that is why sudo privileges were removed for the vast majority of people.
Shared this before, but someone I know did a chmod on /bin which nuked all the SUID/GUID bits which borked the system lol.
Surpsingly easy enough to undo by getting a list of the correct perms from a working system, but hilarious nonetheless
Oh… That sounds like a nightmare. How do you even fix that? There’s no “revert the entire filesystem’s permissions to default” button that I’m aware of
You restore the system from backup
If you are lucky your system is atomic or has other roll back feature. Otherwise it’s reinstall time.
I guess you could set up a fresh system, run a script that goes through each folder checking the permission and setting it on the target system.
seems reasonable to me, root is just a made up concept and the human owns the machine.
as a GUI pleb i just doubleclick the file, which opens kate.
i edit the file and click save, get asked for my password
and all is fine.
that’s way too simple, the linux gods demand more esoteric suffering
How dare you use computers to do stuff the way they were invented for?
A fellow nano user! There are dozens of us!
Hell yeah gotta embrace the pain of using archaic key bindings that you’ll forget until the next time you need to edit a file in the terminal, you must suffer like man. Modem and sane terminal editors are for pussies! If it doesn’t load in 0.01 ms it’s bloated… Whatever you do don’t install anything like micro, just keep suffering!
pico gang rise up!
G T F O !
-nano4lifegang
Yikes it was just a joke guys
sudo chmod -R 777 /
It’s safe because it’s sudo! Like sudo rm -rf /*
At one of my prior positions they outsourced all the junior engineers to this firm that only had windows desktop support experience.
Actual escalation I got:
contractor: I am trying to remove this file that is filling the drive but it won’t let me
me: show me what you are doing.
contractor (screenshot): # rm -f /dev/hdc
another one did rm -rf /var to clear a stuck log file, which at least did solve the problem he was having.
After that I sent out an email stating that I would not help anyone who used he rm command unless they consulted with a senior first. I was later reprimanded for saying I wouldn’t help people.
I was later reprimanded for saying I wouldn’t help people.
I’ve heard that before. “No. I won’t close the circuit breaker while you’re holding the wires.” “Boss!..”
Back in the olden days we used to nfs mount every other machines file system on every machine. I was root and ran “rm -rf /" instead of "./”.
After I realized that it was taking too long, i realized my error.
Now for the fun part. In those days nfs passed root privileges to the remote file system. I took out 2.5 machines before I killed it.
Anyone remember that nvidia fix where a space slipped in like: rm -rf / nvidia ?
Back in the olden days we used to nfs mount every other machines file system on every machine. I was root and ran “rm -rf /” instead of “./”.
I still do. With NFS4 even more than ever. Won’t let it go unless for a SAN.
Now for the fun part. In those days nfs passed root privileges to the remote file system.
no_root_squashmuch?
Like I said, olden days.
Holy smokes. That must have been before 1989 (that’s when RFC1094 was released, explicitely prohibiting to map the root user to UID 0). I thought, I was old…
You won’t be able to do certain things. Either .ssh or ~ expects certain exact permissions and pukes if it’s different, IIRC
Yep. I fucked up once when I meant to type chmod for something but with “./” but I missed the “.”. It was not good.
Getting flashbacks of me trying to explain to a mac user why using sudo “to make it work” is why he had a growing problem of needing to use sudo… (more and more files owned by root in his home folder).
sudo = shut up dammit, obey!
personally, I prefer the good ol double bang (!!), but whatever floats yer boat, and all that.
:w !sudo tee %sudo dolphin
Then I act like a Windows user and go there via the GUI because I didn’t feel like learning how to use nano.
If you’re running dolphin as sudo and open like a text file in an editor, does it edit the file with sudo?
When you run a process under
sudo, it will be running as the root user. Processes that that process launches will also be running as the root user; new processes run as the same user as their parent process.So internally, no, it won’t result in another invocation of
sudo. But those processes a dolphin process running as root starts will be running as the root user, same as if you had individually invoked them viasudo.But in my experience Dolphin refuses to run via sudo anyway.
why tho?
If it’s a file I have to modify once why would I run:
sudo chmod 774 file.conf
sudo chown myuser:myuser file.conf
vi file.conf
sudo chown root:root file.conf
sudo chmod 644 file.conf
instead of:
sudo vi file.conf
Inane. Intentionally convoluted, or someone following the absolute worst tutorials without bothering to understand anything about what they’re reading.
I have questions:
- Why are your configurations world readable?
- Why are you setting the executable bit on a .conf file?
- Why change the files group alongside the owner when you’ve just given the owner rxw and you’re going to set it back?
- If it was 644 before, why 774?
- Why even change the mode if you’re going to change the ownership?
- Why do you want roots vimrc instead of your users
- Why do you hate sudoedit
- Why go out of your way to make this appear more convoluted than it actually is?
Even jokey comments can lead to people copying bad habits if it’s not clear they’re jokes.
This was a joke right? I was baited by your trolling?
I felt kinda bad doing that at first. then your absolute rage made my doubt’s melt away.
doubt’s
I see what you did there
