Re: sysctl(3) interface

2007-02-02 Thread Dag-Erling Smørgrav
Daniel Rudy <[EMAIL PROTECTED]> writes: > Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes: > > man 3 devinfo > A little too late since I already hacked the source for sysctl(8) and > figured out how it works. The dev sysctl tree contains only a subset of the information available through devinfo(3)

Re: sysctl(3) interface

2007-02-01 Thread Daniel Rudy
At about the time of 1/31/2007 2:10 AM, Dag-Erling Smørgrav stated the following: > Daniel Rudy <[EMAIL PROTECTED]> writes: >> I've been taking apart and analyzing the sysctl(8) program to gain a >> better insight into how to use the sysctl(3) interface. [...] >>

Re: sysctl(3) interface

2007-02-01 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> [EMAIL PROTECTED] (Dag-Erling Smørgrav) writes: : Daniel Rudy <[EMAIL PROTECTED]> writes: : > I've been taking apart and analyzing the sysctl(8) program to gain a : > better insight into how to use the sysctl(3) interface. [...] :

Re: sysctl(3) interface

2007-01-31 Thread Dag-Erling Smørgrav
Daniel Rudy <[EMAIL PROTECTED]> writes: > I've been taking apart and analyzing the sysctl(8) program to gain a > better insight into how to use the sysctl(3) interface. [...] > It's using an oid of 0 and 2 to get something, then it comes up with 440 > and then a

sysctl(3) interface

2007-01-27 Thread Daniel Rudy
Hello List, I've been taking apart and analyzing the sysctl(8) program to gain a better insight into how to use the sysctl(3) interface. Adding some debugging code to the program in strategic locations, this is what I have as an output: debug: name: dev debug: all: oid: 0 2 440 debug: