On 21:50 12 Feb 2002, Mark Swanson <swansma@yahoo.com> wrote:
| I would like to hear people's opinions on making the keys in the /proc
| hierarchy consistent wrt the space character. The current Linux
| Documentation/filesystems.proc.txt does not suggest any standard naming
| conventions. F.E. cat /proc/cpuinfo
| (partial list)
|
| cpu family : 5
| model : 9
| model name : AMD-K6(tm) 3D+ Processor
| stepping : 1
| cpu MHz : 400.907
| cache size : 256 KB
| fdiv_bug : no
| hlt_bug : no
| f00f_bug : no
|
| Notice the space between "cpu" and "MHz", or "cpu" and "family" yet there is
| no space between "fdiv" and "bug" (_).
|
| The reason I think NOT using a space is a good idea because it makes life
| easier for developers parsing /proc entries. Specifically, Java developers
| could use /proc/cpuinfo as a property file, but the space in the 'key' breaks
| java.util.Properties.load().
Personally, I have LONG wished all /proc/* entries were shell parsable values, eg:
cpu_family=5
model=9
model_name='AMD-K6(tm) 3D+ Processor'
etc. The amound of userland parsing code this would obviate must be quite
large, and it certainly would make simple scripts to do things with the
values much easier.
instead, there are all these "pretty" files, with formatting code that
properly belongs in userland tools residing in the kernel (yes, mostly
just printf but still).
Flame on dudes,
-- Cameron Simpson, DoD#743 cs@zip.com.au http://www.zip.com.au/~cs/They call me a bummer and a gin-sop,too....but what care I for praise! - Bob Dylan. "The days of '49" - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Feb 15 2002 - 21:00:52 EST