181–190 of 284 posts
Earlier quoted context omitted.
The proper answer is to type "rm -rf" otherwise you're risking a stray strike on enter.
The other proper answer is to have a good backup and recovery system.
And, of course, that should've been the solution to OP's incident with the Korean Airlines flight 007. Backups, surprisingly, are scarcely mentioned at all in this whole thread.
Earlier quoted context omitted.
If a police officer shot and killed innocent bystanders, should they get achievement awards for doing their job otherwise? My answer would be no, you failed at your job regardless. Same thing with military.
That's a very narrow minded position. Gosh I hope you never screw up even once, cause you'll never live it down.
The author states they felt it was appropriate when they were fired. In what world would it be appropriate to get fired for a single, simple, incredibly easy to make mistake? Doubly insane when there were exactly zero safeguards in place to prevent the mistake from being made.
The world where you know you that a) you have an incredibly powerful key with no safeguards at your fingertips and b) you might be in a breaking news situation and nonetheless you go for the key right next to the dangerous one carelessly enough that you miss? Think about it: Unix is equally as "insane". If you're the guy on the console who meant to clean out some crap dir and accidentally typoed "rm -rf /" and then c…
Far from perfect - it depended on the order of deletion - but a more general solution than preserve root. Of course it still requires the user to mark things they consider "important".
Earlier quoted context omitted.
The world where you know you that a) you have an incredibly powerful key with no safeguards at your fingertips and b) you might be in a breaking news situation and nonetheless you go for the key right next to the dangerous one carelessly enough that you miss? Think about it: Unix is equally as "insane". If you're the guy on the console who meant to clean out some crap dir and accidentally typoed "rm -rf /" and then c…
But typing "rm -rf /" is significantly harder to do accidentally than typing F7 instead of F6.
rm -rf *
in their shell history? Now it's just one accidental twitch away.
> That Korean announcement and the slow response by the US President — both caused by delayed real information — caused decades of conspiracy theories. I appreciate that the OP was a part of the situation, but conspiracy theories were not caused by this. It was time of very high tension between the US and Soviet Union. So when a plane veers off the course into not just Soviet airspace, but into an explicitly cordoned…
Through the glass of a yellow newspaper box, the Miami News headline that the Soviets had shot down a plane carrying a Congressman. My first thought was "This is the war." Not 'a' but 'the'. The primary stance of the US military was squared off against the USSR and had been for more than 30 years.
Earlier quoted context omitted.
But typing "rm -rf /" is significantly harder to do accidentally than typing F7 instead of F6.
Be honest, who doesn't have rm -rf * in their shell history? Now it's just one accidental twitch away.
Earlier quoted context omitted.
If you go with this line of reasoning, whoever put him in that position should also be fired, and their boss should be fired for putting someone in charge who made such a poor decision in the first place.
The person that should be fired is always the person who has responsibility for the amount of budget represented by the loss. e.g. No intern that needs permission to get a box of pencils from the supply closet should ever be fired for putting a mistake into production that costs a company $100,000. If a company loses $100,000 on a mistake, you look to the person in the hierarchy who manages budgets of that size. It's…
The author states they felt it was appropriate when they were fired. In what world would it be appropriate to get fired for a single, simple, incredibly easy to make mistake? Doubly insane when there were exactly zero safeguards in place to prevent the mistake from being made.
According to his next post: What I didn’t say is that it was the last day of my summer internship. The next summer they invited me back again. Everyone understood it was a mistake, but by officially firing me, someone had been punished … :)
Earlier quoted context omitted.
He said he came in to find the system running, and the only time that happened was when Washington was waiting for info. And even if you don't buy that, if pushing the button's not a big deal it doesn't need all the safeguards everyone's yelling for. (Had such safeguards been in place he might equally well have seen them, thought "oh, nobody's in, this will do what I want anyway" and approved it).
That button needs a safeguard even if it's not an international incident. Even if only one person would lose a few hours' work from an all-nighter, work for something that's not so important, it's still someone's work. And given that it's right next to a 'single terminal reset' key, it should be immediately obvious to anyone who's ever used a keyboard - mistakes can and do happen, even when you're fluent.
Earlier quoted context omitted.
According to his next post: What I didn’t say is that it was the last day of my summer internship. The next summer they invited me back again. Everyone understood it was a mistake, but by officially firing me, someone had been punished … :)
Well, that clears it up - and it's quite a clever way to tick the arbitrary "someone took the fall" box.