Obligatory DO NOT RUN THIS ON YOUR COMPUTER (or anyone else’s).
You’d think with fully open permissions, everything would work better, but many programs, including important low level things, interpret it as a sign of system damage and will refuse to operate instead.
If you do run it, you’d better have a backup or something like Timeshift to bail you out, and even if you do have that, it’s not worth trying it just to see what will happen.
It’s not quite as bad as deleting everything because you can boot from external media and back up non-system files after the fact, but the system will almost certainly not work properly and need to be repaired.
Someone actually ran it on a server at my workplace, trying to fix file permissions on a samba share. Broke SSH and the samba daemon. Thankfully I was able to fix by removing the permissions from the config files the error logs pointed to.
Just saying, I think it was a ChatGPT idea, other people use it every day. I only use it if I’m completely stumped, and only take it as suggestions.
One of our servers is a rotting carcass being kept alive by our collective prayers. It runs Windows 7 and custom software whose developer is dead and the source is missing, nothing has been updated for over a decade, and it has its own independent UPS because once it goes down, it has an extremely slim chance of recovering, and we’re afraid to test it. It controls the card entry system into the building, including the server room. Boss doesn’t want to replace it because we’d have to replace all of the terminals and controllers too, and it hasn’t catastrophically failed yet.
You’re right. It’s not a pet. It’s like one of the Saw movies: if it dies, we’re all fucked.
I learned this relatively quickly running my own server with the intention of my family also using it. Data on a separate drive, backed up regularly and automatically. System on it’s own drive, dd’d when it’s in it’s final state and backed up before I screw around any deeper than trying out a new container. I can bring my server back up in however long it takes to transfer data.
Obligatory DO NOT RUN THIS ON YOUR COMPUTER (or anyone else’s).
You’d think with fully open permissions, everything would work better, but many programs, including important low level things, interpret it as a sign of system damage and will refuse to operate instead.
If you do run it, you’d better have a backup or something like Timeshift to bail you out, and even if you do have that, it’s not worth trying it just to see what will happen.
It’s not quite as bad as deleting everything because you can boot from external media and back up non-system files after the fact, but the system will almost certainly not work properly and need to be repaired.
You have been warned.
One time I introduced someone to Linux then left them to their own devices.
I returned to them hours later to find out they had gotten annoyed with permissions errors and run
chown -R ${THEIRUSER}: /.The results were not what they wanted.
Someone actually ran it on a server at my workplace, trying to fix file permissions on a samba share. Broke SSH and the samba daemon. Thankfully I was able to fix by removing the permissions from the config files the error logs pointed to.
Just saying, I think it was a ChatGPT idea, other people use it every day. I only use it if I’m completely stumped, and only take it as suggestions.
New guy at work ran this to try to fix permissions on his home folder, accidentally ran it on root (both would have been bad)
Several highly paid and experienced Linux admins finally just gave up and deleted the server and built a new one from the backups.
Why does he have rights to use sudo in the first place?
Which, honestly, is the better way to go. Treat your compute resources like cattle, not pets.
One of our servers is a rotting carcass being kept alive by our collective prayers. It runs Windows 7 and custom software whose developer is dead and the source is missing, nothing has been updated for over a decade, and it has its own independent UPS because once it goes down, it has an extremely slim chance of recovering, and we’re afraid to test it. It controls the card entry system into the building, including the server room. Boss doesn’t want to replace it because we’d have to replace all of the terminals and controllers too, and it hasn’t catastrophically failed yet.
You’re right. It’s not a pet. It’s like one of the Saw movies: if it dies, we’re all fucked.
So… the dead server controls who is even able to enter the building? Wow. That is one big juggernaut of a problem heading for you.
I learned this relatively quickly running my own server with the intention of my family also using it. Data on a separate drive, backed up regularly and automatically. System on it’s own drive, dd’d when it’s in it’s final state and backed up before I screw around any deeper than trying out a new container. I can bring my server back up in however long it takes to transfer data.
I will make a disclaimer. Thanks.
But how else will I make everything work without issues