From: Mark Swanson <swansma@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: Terrehon Bowden <terrehon@pacbell.net>,
Bodo Bauer <bb@ricochet.net>,
Jorge Nerin <comandante@zaralinux.com>
Subject: RFC: /proc key naming consistency
Date: Tue, 12 Feb 2002 21:50:35 -0500 [thread overview]
Message-ID: <20020213030047.8B1FB2257B@www.webservicesolutions.com> (raw)
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().
Fire away...
next reply other threads:[~2002-02-13 2:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 2:50 Mark Swanson [this message]
2002-02-13 5:00 ` Cameron Simpson
2002-02-13 20:07 ` H. Peter Anvin
2002-02-13 20:52 ` Daniel Phillips
2002-02-13 21:04 ` H. Peter Anvin
2002-02-13 23:31 Luke Burton
2002-02-14 12:19 ` Miquel van Smoorenburg
2002-02-14 12:25 ` Wichert Akkerman
2002-02-14 16:09 ` Vince Weaver
2002-02-14 19:02 ` ertzog
2002-02-14 16:12 ` Alexander Viro
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=20020213030047.8B1FB2257B@www.webservicesolutions.com \
--to=swansma@yahoo.com \
--cc=bb@ricochet.net \
--cc=comandante@zaralinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=terrehon@pacbell.net \
/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
all inboxes | Powered by JetHome®