From: Jamie Lokier <jamie@shareable.org>
To: Jeff Sipek <jeffpc@optonline.net>
Cc: thockin@sun.com,
Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: sysconf - exposing constants to userspace
Date: Fri, 20 Feb 2004 00:20:34 +0000 [thread overview]
Message-ID: <20040220002034.GC5590@mail.shareable.org> (raw)
In-Reply-To: <200402191630.47047.jeffpc@optonline.net>
Jeff Sipek wrote:
> I think that making something in /sys would make the most sense,
> with one constant per file. We could dump the consts files to for
> example /sys/consts, or make a logical directory structure to make
> navigation easier.
Isn't that very similar to the /proc/sys/kernel we have now?
-- Jamie
next prev parent reply other threads:[~2004-02-20 0:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 20:48 sysconf - exposing constants to userspace Tim Hockin
2004-02-19 21:30 ` Jeff Sipek
2004-02-20 0:20 ` Jamie Lokier [this message]
2004-02-20 0:21 ` Tim Hockin
2004-02-20 0:35 ` Chris Wright
2004-02-20 0:29 ` Jeff Sipek
2004-02-20 0:34 ` Tim Hockin
2004-02-20 0:52 ` Chris Wright
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=20040220002034.GC5590@mail.shareable.org \
--to=jamie@shareable.org \
--cc=jeffpc@optonline.net \
--cc=linux-kernel@vger.kernel.org \
--cc=thockin@sun.com \
/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