From: hpa@zytor.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: where to export system tuneables, /proc/sys/kernel or /sys/?
Date: Tue, 8 Feb 2005 22:44:25 +0000 (UTC) [thread overview]
Message-ID: <cubfc9$2th$1@terminus.zytor.com> (raw)
In-Reply-To: 4207A395.1060901@nortel.com
Followup to: <4207A395.1060901@nortel.com>
By author: Chris Friesen <cfriesen@nortel.com>
In newsgroup: linux.dev.kernel
>
> I'm doing some kernel work that will export tuneables to userspace. In
> 2.4 I would have used /proc/sys/kernel, but now there is /sys, which was
> supposed to be for system information.
>
> However, a bit of poking around in /sys didn't reveal any obvious place
> to put it. Is current practice to still put this sort of thing in /proc?
>
/proc/sys/kernel, using the sysctl internals, yes.
Note that the use of the sysctl(2) system call is highly deprecated,
but the /proc/sys filesystem tree is not; the reason is that the
numeric API used by the former is unstable.
-hpa
prev parent reply other threads:[~2005-02-08 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 17:21 where to export system tuneables, /proc/sys/kernel or /sys/? Chris Friesen
2005-02-08 22:44 ` H. Peter Anvin [this message]
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='cubfc9$2th$1@terminus.zytor.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