[lkml]   [2001]   [Nov]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: PROPOSAL: /proc standards (was dot-proc interface [was: /proc stuff])

Stephen Satchell wrote:

> The /proc API was developed to solve a specific problem. Now, people
> have proposed and The Powers That Be have accepted extensions to the
> /proc interface as a superior way to tune the kernel, particularly from
> shell scripts, and to monitor the kernel, again from shell scripts.
> It's a good thing, actually, in that it preserves the best of the Unix
> mentality: don't re-invent, reuse.

I definately like this approach....

> The RIGHT tool to fix the problem is the pen, not the coding pad. I
> hereby pick up that pen and put forth version of the
> Rules of /Proc:
> 1) IT SHOULD NOT BE PRETTY. No tabs to line up columns. No "progress
> bars." No labels except as "proc comments" (see later). No in-line
> labelling.

Tabs and/or multiple spaces should not be any harder to parse than
a single space, so I don't necessarily see the need to restrict them.

> 3) All integral decimal values shall be assumed by both programs and
> humans to consist of any number of bits. [C'mon, people, dealing with
> 64-bit or 128-bit numbers is NOT HARD. If you don't know how, LEARN.
> bc(1) can provide hints on how to do this -- use the Source, Luke.]
> Numbers shall contain decimal digits [0-9] only. Zero-padding is allowed.

Sometimes HEX is the best way to display things. I think we should be
able to use 0xAABBCCDD type formatting. The key here is to always prefix
with 0x so we can parse it correctly.

Ben Greear <> <Ben_Greear AT>
President of Candela Technologies Inc

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

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