From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Device Registry (DevReg) Patch 0.2.0
Date: 25 Apr 2001 11:09:16 -0700 [thread overview]
Message-ID: <9c73sc$uds$1@cesium.transmeta.com> (raw)
In-Reply-To: <3AE704FA.DCF1BEC6@kegel.com>
Followup to: <3AE704FA.DCF1BEC6@kegel.com>
By author: Dan Kegel <dank@kegel.com>
In newsgroup: linux.dev.kernel
>
> The only problem with /proc as it stands is that there is no formal
> syntax for its entries. Some of them are hard to parse.
>
/proc/sys is probably the method to follow. Every item is a datum of
a simple datatype.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
next prev parent reply other threads:[~2001-04-25 18:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-25 17:10 Device Registry (DevReg) Patch 0.2.0 Dan Kegel
2001-04-25 18:09 ` H. Peter Anvin [this message]
2001-04-25 18:55 ` /proc format (was Device Registry (DevReg) Patch 0.2.0) Tim Jansen
2001-04-25 19:19 ` Dan Kegel
2001-04-25 23:09 ` Tim Jansen
2001-04-25 19:37 ` Jesse Pollard
2001-04-25 20:08 ` Dan Kegel
2001-04-25 20:40 ` Tim Jansen
2001-04-25 21:16 ` Jesse Pollard
2001-04-25 21:50 ` J . A . Magallon
2001-04-25 21:58 ` Doug McNaught
2001-04-25 22:03 ` J . A . Magallon
2001-04-25 22:24 ` Marko Kreen
2001-04-25 22:42 ` Alexander Viro
2001-04-25 22:24 ` Mark Hahn
2001-04-26 14:06 ` Tim Jansen
2001-04-25 22:46 ` Tim Jansen
-- strict thread matches above, loose matches on Subject: below --
2001-04-24 1:08 Device Registry (DevReg) Patch 0.2.0 Tim Jansen
2001-04-24 9:40 ` Martin Dalecki
2001-04-24 11:44 ` Tim Jansen
2001-04-24 16:39 ` Martin Dalecki
2001-04-24 18:27 ` Tim Jansen
2001-04-24 16:43 ` mirabilos
2001-04-24 18:57 ` Tim Jansen
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='9c73sc$uds$1@cesium.transmeta.com' \
--to=hpa@zytor.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