--adJ1OR3c6QgCpb/j
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Sep 13, 2005 at 03:47:19PM -0400, Jim Wise wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> On Tue, 13 Sep 2005, Perry E. Metzger wrote:
>=20
> >I have to say I disagree. Often, in trying to debug one portion of the
> >kernel or another, it is VERY valuable to understand the inside of how
> >that portion of the kernel works. The 4.4 book is pretty old at this
> >point and was woefully incomplete.
>=20
> I don't see a problem with keeping such documents, but it strikes me=20
> that putting them in manual section 9 is an overloading of the meaning=20
> of that section.
>=20
> If I am looking for a kernel API to do something in a driver, lkm, or=20
> kernel change, and keep seeing promising-looking man pages which turn=20
> out to be false leads as they document internal workings with no visible=
=20
> (and thus usable) API, I'm likely to get frustrated.
>=20
> This doesn't mean we shouldn't keep such documentation, but I think it=20
> _does_ mean such documents should go either in /usr/share/doc (my=20
> preference), manual section 4 (perfectly reasonable) or in a new man=20
> section.

I think either /usr/share/doc or a new man section would be best.

Take care,

Bill

--adJ1OR3c6QgCpb/j
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFDKe7KWz+3JHUci9cRAj/7AJ9aPqtlqBZ53xeq/JFjMKv8LAxavACdFz93
0E/ZSNIB6ex78uyVKllG6VE=
=GpEp
-----END PGP SIGNATURE-----

--adJ1OR3c6QgCpb/j--