There may be good reason to break one or more of these rules at one time, but never all four.
so for now there is no good solution to avoid potentially bricking your system
Have you tried not running rm -rf
Only to still replace it with air cooling further down the line.
Sure, admittedly so, of course. The point, though, is clearly to be able to use a larger or otherwise better air cooler in the end, which I can certainly see being the point in this case, seeing is how the PCI specification gives too little room for a proper cooler on the card itself, especially if it's going to fit in only two slots.
It's mostly a matter of incompetence in the implementation, indeed. The Java vulnerabilities I have followed have always included calling some obscure part of the Java class library which is implemented using native code (mostly for optimization reasons) that happened to be buggy in some way.
It should be said in this case, however, that the new Java 7 dynamic language support infrastructure, which is one of the things Oracle added since they took Java over. Many of the things Oracle has done to Java lately (and especially as additions in Java 7) have struck me as poorly designed features that just allowed Oracle to check of some feature-lists to make Java appear as "feature-complete" as dotnet.
You don't normally use LVM for RAID1 (you can, but it kind of sucks and is a bit immature). Normally, you'd use mdraid for that, and then construct a LVM PV from the resulting mdraid device(s).
Neither ext3, LVM nor mdraid checks for silent corruption, however. That's strictly a feature of filesystems like ZFS or btrfs that explicitly checksum all data.
A debugged program is one for which you have not yet found the conditions that make it fail. -- Jerry Ogdin