> >Whenever this comes up though people say cpuinfo is for human eyes
> >only, it should not be parsed. But when someone suggests making a syscall
> >for it, everyone decries that idea too.
> >
>
> I have always wanted to ask this question, and this seems like an
> appropriate thread.
>
> Coming from a Free/OpenBSD background, I have always really liked
> the sysctl MIB. The sysctl command line too allows values to be manipulated
> and read easily (much easier than parsing the /proc entries).
>
> Why does Linux deprecate that use? Why has is opted for a /proc
> interface?
>
> I do wish that BSD would implement a /sysctl or something interface for
> browsing, but then again, that is what 'sysctl -a | grep' is for :)
Check the latest procps release. There is a sysctl binary in there.
G
-----------------------------------------------------------------------------
George Staikos | staikos@0wned.org | root@0wned.org
-----------------------------------------------------------------------------
When you dream, there are no rules.
People can fly. Anything can happen.
Sometimes there's a moment as you're waking and you become aware of the real
world around you.
But you're still dreaming.
You may think you can fly, but you better not try.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/