sudo chmod -R 777 /
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.
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.
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_squash
much?
You won’t be able to do certain things. Either .ssh or ~ expects certain exact permissions and pukes if it’s different, IIRC
