On 9/17/09 2:16 PM, "Adam Thornton" <athorn...@sinenomine.net> wrote:
> "Administrator typo" is not a failure mode the operating system is > designed to protect you from. That may be true now, but I think the point of the argument is that it should not be. On VMS, if you have a SYSTEM priv bit set, the system will still warn you if you're about to do something that seems stupid. If there is an architected limit (note that the 9.7TB got clipped to 8TB, so SOMETHING noticed a problem), then it's not too unreasonable for the system to take defensive measures and issue a warning that all is not right in in the kingdom of Denmark, cream or no cream dresses. It seems like a basic defense that if CP notices you starting something that it KNOWS it may not have resources to complete, requiring confirmation that you know what you're doing (or about to do) is a good defensive measure. Did the system do what you told it to do when you told it to do it? Yes. Whether it should march off a cliff without at least questioning the order is the question at hand. -- db
