Reset all computers in the embassy with F7? No warning prompt? Fire the idiot who wrote that function.
"take a deep breath, count to ten"
61–70 of 284 posts
Reset all computers in the embassy with F7? No warning prompt? Fire the idiot who wrote that function.
"take a deep breath, count to ten"
Reset all computers in the embassy with F7? No warning prompt? Fire the idiot who wrote that function.
In fairness, it was a different world back then. There were so few people administering computer networks that you could generally assume someone who was doing so had been thoroughly trained; and the thing about highly trained people is that they tend to view things like failsafes and safeties as pointless time-wasters. "I know what I'm doing when I hit F7, but the damn system makes me sit there for 30 seconds before…
If something has changed over these years, it's the overall understanding of design principles and their popularization. (Thanks, Don Norman and other people in the field!)
Training has nothing to do with it. Even if you can train a person to work with a badly designed system without making mistakes (often), designing the system well in the first place is almost always significantly easier and cheaper.
For example, accidental key presses can be easily prevented by requiring the user to type a command of reasonable length. Typing "reboot-all-workstations" is not that difficult, but it would definitely prevent the incident described in the article.
Earlier quoted context omitted.
Not really, a lot of novice unix users are of the habit of removing files with -rf switch. I cringe everytime I see it. The command "rm -rf ~/blue/" is just a single space key from being equivalent to "rm -rf /" with "rm -rf ~/blue /"
On any modern system it's actually "sudo rm -rf / --no-preserve-root" and then entering your password while staring at the command. "rm -rf ~/blue /" will not come close to deleting / unless you are in the habit of running every command as sudo, even ignoring the presence of --no-preserve-root
1. You type it into the wrong system (D'oh)
2. You have run `mount --bind / /somewhere/else` then `rm -rf /somewhere` a week later
:(
I disagree that it was appropriate that you were fired, but interesting story all about.
For security reasons I think that it might have been justified, considering the events that had just taken place. Still a crappy way to go out though.
Reset all computers in the embassy with F7? No warning prompt? Fire the idiot who wrote that function.
Reset all computers in the embassy with F7? No warning prompt? Fire the idiot who wrote that function.
Earlier quoted context omitted.
But typing "rm -rf /" is significantly harder to do accidentally than typing F7 instead of F6.
The / key was right next to Enter on a lot of old keyboards. It was quite easy to type 'rm -rf /tmp/garbage*' and have a simple fumble turn it into 'rm -rf /'. I mean, there's this guy I know, he did that once.
Such as this classic:
https://github.com/MrMEEE/bumblebee-Old-and-abbandoned/commi...
Reset all computers in the embassy with F7? No warning prompt? Fire the idiot who wrote that function.
I don't remember how it is on the newer versions, but try using fdisk in an old linux distro and see how many confirmations you get when deleting a partition. Or just the old rm -rf / Older stuff asks for much less confirmations.
Earlier quoted context omitted.
Or, you know, he had a perfectly good reason to think that accidentally resetting all the computers in the building at that time would not be a problem: "Not long after I arrived in my office, I received a call from a secretary in the Agriculture Department who liked to play a computer game before her workday started. Her favorite game had a bug that regularly froze her workstation. [...] I realized that I had mistak…
Yes, he had a pretty good reason to think that probably no major damage was done, and this was sufficient to comfort him. This kind of carelessness about the possibility of causing harm or having caused harm suggests to me that he wasn't taking his responsibility as seriously as he should.
In any case, we already know where your line of thought leads, risk adverse cultures ultimately stagnate and wither away.