|John S. Dyson||Dec 6, 1997 5:30 am|
|Joao Carlos Mendes Luis||Dec 7, 1997 10:24 am|
|John S. Dyson||Dec 7, 1997 10:29 am|
|Eivind Eklund||Dec 7, 1997 4:43 pm|
|Wolfram Schneider||Dec 7, 1997 5:37 pm|
|John S. Dyson||Dec 7, 1997 5:51 pm|
|Mike Smith||Dec 7, 1997 11:05 pm|
|Eivind Eklund||Dec 8, 1997 12:36 am|
|Johan Granlund||Dec 8, 1997 11:05 am|
|Andrew Reilly||Dec 8, 1997 1:27 pm|
|Mike Smith||Dec 8, 1997 4:04 pm|
|Eivind Eklund||Dec 8, 1997 4:39 pm|
|Mike Smith||Dec 8, 1997 4:58 pm|
|Terry Lambert||Dec 8, 1997 6:03 pm|
|Eivind Eklund||Dec 9, 1997 6:11 am|
|Eivind Eklund||Dec 9, 1997 6:32 am|
|Charles Henrich||Dec 9, 1997 8:43 am|
|Poul-Henning Kamp||Dec 9, 1997 9:18 am|
|Charles Henrich||Dec 9, 1997 9:39 am|
|Eivind Eklund||Dec 9, 1997 10:58 am|
|Charles Henrich||Dec 9, 1997 11:55 am|
|J Wunsch||Dec 9, 1997 3:09 pm|
|Mike Smith||Dec 9, 1997 3:25 pm|
|Terry Lambert||Dec 9, 1997 7:35 pm|
|Terry Lambert||Dec 9, 1997 7:54 pm|
|Bruce Evans||Dec 9, 1997 11:27 pm|
|John S. Dyson||Dec 10, 1997 9:27 am|
|Subject:||Re: VM system info|
|From:||Eivind Eklund (perh...@yes.no)|
|Date:||Dec 8, 1997 4:39:20 pm|
Would you buy it in /usr/share/misc/sysctl_nodes? I was thinking about that when I saved John's message...
If extracted from the kernel source, I'd say it was OK.
Extracting from kernel source (at build time) is quite obviously pointless.
I'd say this give you a fairly recent snapshot of the available IOCTLs; I certainly update my kernel more often that my manpages (and much more often that /usr/share).
I'd opt for it to be compiled as part of 'make world' instead, but there are certainly some good points to doing it at the kernel build tilme.
It's also not useful for parts of the tree that are dynamically generated (although sysctl isn't actually too good at walking those parts of the tree anyway).
Ehm - what tree? The sysctl tree in the kernel? I'd guess we'd be able to find some way to document that in the source too, if we really wanted to. A single SYSCTL_DOC() macro could do it.
However, if this is a file that developers are supposed to to keep up to date manually, I'm much more sceptical. Keeping documentation outside the source up to date has a tendency to be forgotten/ignored.
This is the only way to do it; maintaining a document which describes a superset of nodes. Even if it's incomplete (like scsi_modes) it would be Better than Nothing.
It might be better than nothing, but it is almost certainly going to wander far from the ultimate. Any form of documentation that is in-line in the code is much more likely to be kept up-to-date, and it _is_ fairly cheap.
<GENERAL RANT> Any attempt at making things easier for the newcomers at a slight, indirect expense to the people 'in the know' seems to be shouted down immedately. Leanness of the kernel and the source tree seems to have a small but vocal minority that shout down any documentation that might actually be kept up to date. (Ref my attempt at finding some tolerable way to provide inline documentation for kernel file use last easter). </GENERAL>