[lkml]   [1996]   [May]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectSystem Information
Great news, Matt! I hope you do this.

One suggestion I'd like to make is this: Keep any System Information
(SI) program highly configurable, as far as what it reads to get the
information. If this is not done, I am envisioning an SI which needs
to be updated everytime something in the kernel changes, which causes
a change inthe formatting of the /proc/* file format. If we have
something along the lines of the /etc/magic file, then we can key on
particular field name, or file position, and find the data that way.
If the proc file changes, then all that needs to be fixed in the SI is
a change to the config file. I know this complicates the design quite
a bit, but it save a lot of maintenance down the road.

Here's some flame bait: How about reformatting the /proc files so they
appear more like /proc/cpuinfo? Each item and its associated value is
on a separate line. It seems to me this would make it easier to write
an SI that has to "feel around" for the values in a changing /proc
file (changing per kernel revision). The SI could probably use all
the /proc files as they are, but to make it flexible enough to keep up
with file changes, the SI would have to use scripts or very complex
file description language to define the location of the information
it's looking for. I don't think something like that would be easy for
the average kernel consumer to maintain. I realize this would make
some of the /proc files less readable, but they wouldn 't have to be:
we would use the SI for that. Just a thought.

- ---
Andrew C. Esh
Computer Network Technology (finger for PGP key)
6500 Wedgwood Road 612.550.8000 (main)
Maple Grove MN 55311 612.550.8229 (direct) - CNT Inc. Home Page - ACE Home Page

 \ /
  Last update: 2005-03-22 13:37    [W:0.053 / U:9.484 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site