3 ms·
Really Google, really?! Check the CPU capabilities for fscks sake! This is CPU features 101. Read the manufacturer's manual, they point that out. Sorry for th
by raverbashing 14y ago
Really Google, really?!
Check the CPU capabilities for fscks sake! This is CPU features 101. Read the manufacturer's manual, they point that out.
Sorry for the aggressive tone, but this is really idiotic. Checking CPU string is worse, more buggy and less compatible EVEN among different CPUs from the same vendor!
"Because our system is potentially vulnerable to incorrect x86 implementations"
Fine, check the capabilities FIRST, then check the string. Not the other way around.
Same thing for the "firmware developers" who check for Windows and Red Hat at the string. Someone needs to buy a large batch of these and return them as being defective.