starman,
sudo rm -rf --no-preserve-root /
metaStatic, starman is not in the sudoers file.
This incident will be reported.
starman, Oh no, Linus Torvalds is gonna call me again
borlax, Linus calling you to belittle your management of the sudoers file is the FOSS form of swatting lol.
Number358, su -
Time
Dirk,
sudo rm -rf /*
HiddenLayer5,
sudo rm -rf i_want_to_delete_everything_in_this_folder /*
oops…
roi, UP ARROW!!
bear_with_a_hammer, “Hello, we are fucked up, let us explain what happened and why is this not our fault”
dontblink, You just need to reboot it manually
HiddenLayer5, Just press and hold the power button smh
abcd, Have you tried turning it off and on again?
Iniquity, Awww, what a shame though. This probe was doing some really cool stuff, it’s kinda iconic in my head.
HiddenLayer5, (edited ) Yeah all jokes aside this is a actually pretty big loss for the scientific community. Assuming it’s completely unrecoverable. We blew our chance to actually measure the conditions in interstellar space and see if it lines up with our theories, and another probe is not only not planned for the foreseeable future by any space agency, it will also take decades to get to where Voyager 2 is now.
Edit: Nevermind, see the other comment. It’s likely not permanently lost!
agent_flounder, Also haven’t we been gathering interstellar readings for a while now?
fiat_lux, It should be ok. It's due to self-reset its orientation on October 15, they put measures in place for if they accidentally lost contact.
I would still be besides myself if I had made that error though.
IHeartBadCode, Next hardware reset and automatic reorientation for Voyager 2 is October 15th. Yes the device automatically resets itself about four to five times a year. Communications are expected to be reestablished then.
HiddenLayer5, That’s good news! I was about to ask whether they have some absolute software recovery procedure and glad they do!
fiat_lux, In the meantime, they're going to shout at it.
JackbyDev, That’s great to know. This post made me weirdly depressed and was a bad way to start the morning lol.
fibojoly, Almost like real engineers planned for such an event!
yoz, Wow! Wondering how the guy is being treated who sent the wrong command. I did it once at my work and people were acting really Weird. In my defense, I never really liked the job.
Dirk, I bet you don’t simply send random commands to the probe. There are likely a dozen of people who need to approve literally every keystroke.
yoz, 🤦♂️
lowleveldata, “I’m gonna click approve without looking because the tons of people before / after me must have / will review it.”
Dirk, I’m gonna click approve without looking
… and at this moment it is no longer my problem. I have written evidence that I forwarded my command for approval.
Gecko, This. And even then there should be procedures in place to essentially make it impossible to send the wrong inputs.
It’s like when an intern accidentally drops the production database. It’s not the interns fault for sending the wrong command. It’s the managements fault for not restricting access in the first place.
InputZero, This. This. I used to work on safety control systems for heavy industrial applications and it’s this. Once the system is running any changes at all went through a whole chain of people. When the change was being implemented I had my supervisor and their manager checking every line over my shoulder before we wrote it. Then test. Then lock it down with a digital signature.
It’s not at all like in college/university where you’re making changes to your code over and over. Well it is in simulations but that’s long before you deploy it. By the end everyone involved should be able to say exactly what every line of code is going to do. This isn’t an intern fucking up, the whole team did, and whomever the buck stops with at the top is responsible.
agent_flounder, They have like a whole test environment that is an exact duplicate right?
InputZero, If you’re talking about Voyager, I’d assume so, but I don’t have any source to back that up. If you’re talking about my previous work, the test environment was exact enough… Cough not-even-close cough.
iByteABit, Hello IT, have you tried turning it off and on again?
bob, iptables -P INPUT DROP
hemko, Patching recent ssh vulnerabilities I see
mayflower, Must have been an intern.
independantiste, Probably played with the firewall settings and accidentally disabled port 22… It sucked when I did that
Goodman, No biggie just get someone to mount the files system and edit the ssh file 😌
platysalty, When you ufw enable but forgot to whitelist port 22
Add comment