From: Moritz Schulte <tux@gmx.li>
To: linux-kernel@vger.kernel.org
Subject: Re: /proc & xml data
Date: 30 Oct 2000 13:33:00 +0100 [thread overview]
Message-ID: <87d7giecg3.fsf@gryffindor.sc> (raw)
In-Reply-To: <39FCDB16.B0955558@mindspring.com> <m1n1fmhl9b.fsf@frodo.biederman.org>
In-Reply-To: ebiederm@xmission.com's message of "29 Oct 2000 23:54:24 -0700"
ebiederm@xmission.com (Eric W. Biederman) writes:
> The general consensus is that if we have a major reorganization, in proc
> the rule will be one value per file. And let directories do the grouping.
IIRC some time ago somebody suggested to rename 'proc' to something
like 'sys' or 'system', because it contains so many sytem information,
not only about processes; or extract all non-process-information from
proc to sys. Will this, or something like that, eventually be done
while the reorganization?
moritz
-
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 prev parent reply other threads:[~2000-10-30 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-30 2:21 /proc & xml data Joe
2000-10-30 6:54 ` Eric W. Biederman
2000-10-30 12:33 ` Moritz Schulte [this message]
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=87d7giecg3.fsf@gryffindor.sc \
--to=tux@gmx.li \
--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