* where to export system tuneables, /proc/sys/kernel or /sys/?
@ 2005-02-07 17:21 Chris Friesen
2005-02-08 22:44 ` H. Peter Anvin
0 siblings, 1 reply; 2+ messages in thread
From: Chris Friesen @ 2005-02-07 17:21 UTC (permalink / raw)
To: Linux 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?
Thanks,
Chris
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: where to export system tuneables, /proc/sys/kernel or /sys/?
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
0 siblings, 0 replies; 2+ messages in thread
From: H. Peter Anvin @ 2005-02-08 22:44 UTC (permalink / raw)
To: linux-kernel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-02-08 22:47 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox