I don't consider that a good argument... But that may be just me. I
mean, why shouldn't /proc/cpuinfo be of any interest to any tools? It
may be that it isn't because it can't be parsed in a portable manner.
There is information in there that isn't available in /proc/stat.
But since /proc/stat calls that chip in the big socket a "cpu", I'd at
least consider changing the string in the i386 /proc/cpuinfo from
"processor" to "cpu". I haven't checked to see if the other ports use
something other than "cpu", though.
Anyway, this is just a pedantic thing. After all, if no tools use it,
it shouldn't hurt to change it and make it consistent, now would it?
-- Forte International, P.O. Box 1412, Ridgecrest, CA 93556-1412 Ronald Cole <ronald@forte-intl.com> Phone: (760) 499-9142 President, CEO Fax: (760) 499-9152 My PGP fingerprint: 15 6E C7 91 5F AF 17 C4 24 93 CB 6B EB 38 B5 E5- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/