Subject: Re: howto debug kernel
To: Michael Graff <explorer@flame.org>
From: Jonathan Stone <jonathan@DSG.Stanford.EDU>
List: tech-kern
Date: 05/12/1997 14:34:31
Michael Graff <explorer@flame.org> writes:

>>Jason Thorpe <thorpej@nas.nasa.gov> writes:
>
>> ...not really, but it works like:

>How about I commit this?

Minor nits:
 * Should also document addlog() :)

 * Could perhaps document kernel printf()  (see above!)

Less minor nits:

 * All of log(), addlog(),  printf(), tprintf() etc. are really just
   wrappers to kprintf(), but specifying different output  (to /dev/klog,
   to console, to both; to ctty of (session of) current process; etc.

   There should really be a manpage documenting the printf() control
   strings used by all the kernel printf() functions, including  %b and %:.
   (I couldn't find them anywhere in the  current manpages.)

   I think that should probably be a separate manpage, though:
   for example, panic(9) should refer to printf(9), not  to printf(3).

A name change for the kernel printf() function might make the
documentation cleaner., too.  We already have printf(3) and printf(1),
do we really want printf(9) too?