Messages in this thread | | | From | (david parsons) | Subject | Re: /proc/cpuinfo verbiage differ unnecessarily between ports... | Date | 1 Sep 1999 08:44:29 -0700 |
| |
In article <linux.kernel.d3k8qbf1lk.fsf@lxp03.cern.ch>, Jes Sorensen <Jes.Sorensen@cern.ch> wrote: >>>>>> "David" == david parsons <o.r.c@p.e.l.l.p.o.r.t.l.a.n.d.o.r.u.s> writes: > >David> In article <linux.kernel.d3r9kjzjjl.fsf@lxp03.cern.ch>, Jes >David> Sorensen <Jes.Sorensen@cern.ch> wrote: >>> Since none of the info in /proc/cpuinfo should be of interest to >>> any tools > >David> Why not? I'd say that the contents of /proc/cpuinfo would >David> be very interesting to tools, because it's what the operating >David> system thinks it's running on. > >Why, it's a name of the CPU, MMU and FPU a bunch of version levels and >a list of bugs. In principle these are of no interest to user space >applications
I suspect this is a matter of personal bias; I own a bunch (20) of Linux machine, plus administer a bunch (15? 20?) more, so I find the contents of cpuinfo to be very useful for accounting purposes.
____ david parsons \bi/ It's easier to remember one machine than it is to \/ remember 35 or 40.
- 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/
| |