Messages in this thread | | | Date | Wed, 7 Jul 1999 10:26:30 +0200 (MET DST) | From | Bjorn Wesen <> | Subject | Re: Patch for 2.2.10 (Quelle surprise!) |
| |
On 7 Jul 1999, Jes Sorensen wrote: > >> > Basically it just returns a structure filled out with processor > > >> information a la 'cat /proc/cpuinfo', except that this is done via > >> > >> That is exactly the sort of thing that sysctl() was designed for.
> You still haven't explained why a syscall/sysctl is needed for this > when all the information can be obtained by parsing /proc/cpuinfo
otoh, all the sys parameters are in /proc/sys as well. i guess cpuinfo was left out in the cold because its typically read-only ? but still, its not like sysctl and proc are completely orthogonal..
DESCRIPTION The _sysctl call reads and/or writes kernel parameters. For example, the hostname, or the maximum number of open files.
$ ls -l /proc/sys/kernel total 0 -rw-r--r-- 1 root root 0 Jul 7 11:17 domainname -rw-r--r-- 1 root root 0 Jul 7 11:17 file-max -r--r--r-- 1 root root 0 Jul 7 11:17 file-nr -rw-r--r-- 1 root root 0 Jul 7 11:17 hostname [snip]
- 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/
| |