4 ms·
But there's also "presumed" and "did not think" in there. When there's a problem with your killing device you probably shouldn't use it until you've clarified w
by zeeZ 9y ago
But there's also "presumed" and "did not think" in there. When there's a problem with your killing device you probably shouldn't use it until you've clarified what the problem is and don't just assume your end users will use it correctly.
That's like saying "It's fine, the critical vulnerability patch will be applied on reboot", while in reality all your users just suspend to disk and move that annoying reboot nag window behind the task bar where it's out of sight.
- mikeash 9y ago“You probably shouldn’t use it until you’ve clarified...” doesn’t work so well for a defensive system.
- lostlogin 9y agoHow long was the off/on cycle? If it was short it would be reasonable to do it periodically. I don't think one can pin the blame on the vendor alone.
- mikeash 9y agoClearly the vendor thought it would be reasonable. They failed at communicating it, though. Putting a number on it would have made things clear: “The system must be rebooted after at most 12 hours [or whatever the appropriate value would be] of operation.”
- dragonwriter 9y ago> When there's a problem with your killing device Patriot, in the role deployed in that Gulf War, is a “not being killed” device, but not really a killing device.