From: "William Knop" <w_knop@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: PROPOSAL: /proc standards (was dot-proc interface [was: /proc
Date: Tue, 06 Nov 2001 16:21:45 -0500 [thread overview]
Message-ID: <F272lT2NqFJ3sl3xbYi00004f63@hotmail.com> (raw)
>>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.
>
>It should not be pretty TO HUMANS. Slight difference. It should be >pretty
>to shellscripts and other applications though.
If this is the case, why are we using ASCII for everything? If the only
interface to /proc will be applications, then we could just as well let the
application turn four bytes into an ASCII IPv4 adddress. We could easily
have it set up to parse using the format [single byte type identifier (ie 4
for string with the first byte of "data" being the string length, 1 for
unsigned int, 2 for signed int, 19 for IPv4, 116 for progress bar,
etc.)][data]. Let people standardize away. Am I missing the point?
I think every aspect of an OS should be intuitive (so long as it is
efficient), which IMO /proc isn't. If this means splitting it in two, as
some have suggested, so be it. It certainly should have a design
guideline/spec so we may at least be consistant. Just my 2 coppers.
Will Knop
w_knop@hotmail.com
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
next reply other threads:[~2001-11-06 21:22 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-06 21:21 William Knop [this message]
2001-11-06 21:31 ` Erik Hensema
2001-11-06 22:09 ` Ricky Beam
2001-11-07 16:08 ` Erik Hensema
2001-11-07 16:19 ` lkml user
2001-11-08 0:22 ` Albert D. Cahalan
2001-11-08 6:19 ` john slee
2001-11-08 8:14 ` Albert D. Cahalan
2001-11-08 11:49 ` john slee
-- strict thread matches above, loose matches on Subject: below --
2001-11-07 19:28 William Knop
2001-11-07 23:01 ` Miquel van Smoorenburg
2001-11-05 13:41 PROPOSAL: dot-proc interface [was: /proc stuff] Petr Baudis
2001-11-06 18:56 ` PROPOSAL: /proc standards (was dot-proc interface [was: /proc stuff]) Stephen Satchell
2001-11-06 20:12 ` PROPOSAL: /proc standards (was dot-proc interface [was: /proc Erik Hensema
2001-11-06 20:58 ` Roy Sigurd Karlsbakk
2001-11-06 21:43 ` Ricky Beam
2001-11-06 22:14 ` Alexander Viro
2001-11-07 0:33 ` Alex Bligh - linux-kernel
2001-11-07 7:20 ` Albert D. Cahalan
2001-11-07 8:07 ` Alexander Viro
2001-11-07 17:24 ` Alex Bligh - linux-kernel
2001-11-07 17:22 ` Blue Lang
2001-11-07 19:21 ` Ricky Beam
2001-11-11 10:27 ` Kai Henningsen
2001-11-08 0:47 ` Albert D. Cahalan
2001-11-08 18:53 ` Alex Bligh - linux-kernel
2001-11-08 21:28 ` Ricky Beam
2001-11-09 5:15 ` Albert D. Cahalan
2001-11-19 19:22 ` bill davidsen
2001-11-07 0:13 ` Martin Dalecki
2001-11-07 0:40 ` Alex Bligh - linux-kernel
2001-11-07 1:10 ` Ricky Beam
[not found] ` <Pine.GSO.4.33.0111061947540.17287-100000@sweetums.bluetronic.ne t>
2001-11-07 1:17 ` Alex Bligh - linux-kernel
2001-11-07 11:32 ` Martin Dalecki
2001-11-07 12:35 ` Remco Post
2001-11-07 23:53 ` Albert D. Cahalan
2001-11-07 22:24 ` Paul P Komkoff Jr
2001-11-07 23:15 ` Phil Howard
2001-11-06 21:24 ` Rik van Riel
2001-11-06 21:45 ` Erik Hensema
2001-11-06 22:06 ` Tim Jansen
2001-11-06 22:28 ` Erik Andersen
2001-11-06 22:33 ` Jan-Benedict Glaw
2001-11-06 22:42 ` Erik Andersen
2001-11-06 22:49 ` Jan-Benedict Glaw
2001-11-06 22:53 ` Patrick Mochel
2001-11-06 22:52 ` Erik Andersen
2001-11-06 22:46 ` Ben Greear
2001-11-06 22:50 ` Jan-Benedict Glaw
2001-11-07 0:17 ` Martin Dalecki
2001-11-06 22:53 ` J . A . Magallon
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=F272lT2NqFJ3sl3xbYi00004f63@hotmail.com \
--to=w_knop@hotmail.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
all inboxes | Powered by JetHome®