In article <Pine.LNX.4.43.0401071637390.29450-100000@pilchuck.reedmedia.net>,
Jeremy C. Reed <reed@reedmedia.net> wrote:
>On Thu, 8 Jan 2004, matthew green wrote:
>
>> i disagree.  if something is important enough to need a kernel thread
>> then the man page for it should meantion such.  eg, all the driver
>> man pages should meantion it.  there are a limited number of non-driver
>> kernel threads, and they also should have man pages with the same name.
>
>What is a quick way to know what are non-driver kernel threads and which
>aren't? (Are they the ones with a zero appended to name?)
>
>Or which of the following need their own manpage? (And for the
>others, which existing man pages should document them?)
>
>aiodoned
>atapibus0
>ioflush
>nell0
>nfsio
>pagedaemon
>pms0
>reaper
>scsibus0
>swapper
>usb0
>usbtask
>
>(Also, let me know of others.)
>
>I can work on making a simple man page for each missing. And I can submit
>patches for review for existing manpages (for drivers) to make sure they
>mention their related kernel threads.
>
I fixed intro.2 to document all the mi bus style drivers and kernel threads
but not the individual device driver threads. These should be documented in
the device drivers themselves. Also there are missing cross reference man
pages. Look in intro.2

christos