On Thursday 02 November 2006 17:28, Randall R Schulz wrote:
OK. For starters, tell me what these mean:
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx est tm2 cx16 xtpr lahf_lm Your response indirectly begs the question... of all the human readable output from /proc/cpuinfo (which is useful to you) flags does not include information which is directly useful... but at least your question begins to get to the specific points... so here we go...
[ fields left justified, explanations indented ] processor : 0 One processor installed, the first processor (numbering is from 0) vendor_id : GenuineIntel Intel built the cpu chip installed in this system cpu family : 6 The processor is an i686 chip model : 13 The processor model.... model name : Intel(R) Celeron(R) M processor 1.60GHz The processor name.... and freq (rounded) stepping : 8 Frequency stepping... not something relevant to most users in any gui.... cpu MHz : 1598.081 The precise CPU operating frequency just less than 1.6Ghz cache size : 1024 KB The cache size... in kilobytes fdiv_bug : no Floating point division bug.... uh, nope.... hlt_bug : no another hardware bug.... nope, f00f_bug : no another bug.... ,nope coma_bug : no and another bug...., nope fpu : yes Floating Point Unit.... Yes fpu_exception : yes Floating Point Unit Exception Yes flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx There are those pesky little kernel/processor flags... which are not relevant to ANYONE who has to use a third party gui.... or anyone who is not a kernel developer... or the just plain curious... like the kitties that got killed by it.... bogomips : 3199.39 Bogus Millions of Instructions Per Second.... this is a relative measure of how (relatively) fast the machine is.... although, as the name implies... its well, bogus. My first Linux system had a bogomip reading of about 200 (486 DX 40, running RH5.2 2.0.36 kernel) Get serious... all of the output fields from /proc/cpuinfo *could* be placed into a "dialog box" with little text fields and an "OK" button. We could even write the stupid thing (like most windoze utils) in C++ or C# and have it take up oh... 4.5 meg or so... and give it an icon and place it in a folder called "Expensive Useless Utilities" and charge people for it.... BUT WHY WOULD WE WANT TO DO THAT. Windoze already does that. The Linux way is sweet, simple, free (as in freedom), and relatively inexpensive (as in money). (I trust this is at least a little constructive, or at least constructively pedantic, or maybe pedantically instructive) :-| -- Kind regards, M Harris <><