From: Tim Hockin <thockin@sun.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: Jeff Sipek <jeffpc@optonline.net>,
Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: sysconf - exposing constants to userspace
Date: Thu, 19 Feb 2004 16:21:41 -0800 [thread overview]
Message-ID: <20040220002140.GG9155@sun.com> (raw)
In-Reply-To: <20040220002034.GC5590@mail.shareable.org>
On Fri, Feb 20, 2004 at 12:20:34AM +0000, Jamie Lokier wrote:
> 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?
sysctls are all writable (unless I am missing something). A lot of these
things are not really tunables.
--
Tim Hockin
Sun Microsystems, Linux Software Engineering
thockin@sun.com
All opinions are my own, not Sun's
next prev parent reply other threads:[~2004-02-20 0:26 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
2004-02-20 0:21 ` Tim Hockin [this message]
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=20040220002140.GG9155@sun.com \
--to=thockin@sun.com \
--cc=jamie@shareable.org \
--cc=jeffpc@optonline.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.