From: Joe <joeja@mindspring.com>
To: linux-kernel@vger.kernel.org
Subject: /proc & xml data
Date: Sun, 29 Oct 2000 21:21:11 -0500 [thread overview]
Message-ID: <39FCDB16.B0955558@mindspring.com> (raw)
I remember hearing about various debates about the /proc structure. I
was wondering if anyone had ever considered storing some of the data in
xml format rather than its current format? Things like /proc/meminfo
and cpuinfo may work good in this format as then it would be easy to
write a generic xml parser that could then be used to parse any of the
data. "MemTotal: %8lu kB\n"
In the case of the meminfo it would be a matter of changing the lines in
fs/proc/array.c function get_meminfo(char * buffer) from
"MemTotal: %8lu kB\n"
to something like
"<memtotal>%8lu kB</memtotal>\n"
Joe
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-10-30 6:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-30 2:21 Joe [this message]
2000-10-30 6:54 ` /proc & xml data Eric W. Biederman
2000-10-30 12:33 ` Moritz Schulte
2000-10-30 23:20 ` Olaf Titz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39FCDB16.B0955558@mindspring.com \
--to=joeja@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox