[lkml]   [2001]   [Jan]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: RFC: /xproc -> /proc files in xml grammer?
> Would XML be considered human readable enough for /proc files?  If not,
> how about a /xproc filesystem ( maybe as a kernel build option ), same
> as /proc but uses an xml grammer for reporting.
> I can see tons of uses for this, no more 'fuzzy' parsing for gui
> configuration tools, resource monitors, etc.


No XML. No colons. No newlines. No embedded whitespace.
No quoting. No field names. No other screwing around.

Option 1 looks like this: 42 8842 0 4234 898 33 221 2512

Option 2 is a raw array of 64-bit binary data

Anything else, and somebody like you will be tempted to muck with it.
We've seen spelling changes and column alignment break things. We've
seen parsers break on /proc/cpuinfo because someone decided whitespace
and extra columns might be nice. XML wouldn't be immune to the recent
"features" vs. "flags" problem, but the two options above are.

Now, what is your problem? Grab libgtop (GPL) or libproc (LGPL) and
be happy. All of "ps" is in fact under the LGPL, so you can grab
anything else you might need. (LGPL: not just for libraries anymore)

You get libproc and ps here:
(maybe wait a week or two before you grab that -- new one coming)

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

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