Adding new top-level section to Developer's Handbook: System Architecture?
Hiten Pandya
hmp at FreeBSD.ORG
Tue May 20 11:20:32 UTC 2003
On Mon, May 19, 2003 at 08:39:16PM -0700, Murray Stokely wrote:
> On Mon, May 19, 2003 at 02:54:08PM -0400, Robert Watson wrote:
> > I'm not sure adding a High Level Architecture section is the long term
> > solution. The long term solution might be to break it into two books --
> > one on developing/debugging FreeBSD, and the other on developing/debugging
> > on FreeBSD. Or perhaps an Architecture/design book separate from a
> > practices and procedures book.
>
> Yes I've been threatening to split this up for years and I think it's
> certainly where we need to go in the long run.
>
> > Regardless, would anyone object to my taking the above described strategy
> > for the time being, when I bring in the current draft?
>
> Not at all. I think bringing it in as a new section is fine for now,
> and we'll make sure to coordinate with you when it comes time to split
> into two books.
Chapter naming in Dev-Handbook is really messed, IMHO. Also, we
need to add ``empty still todo'' sections as <sect> tags, rather
than just naming them inside a chapter.
When I get more time, I am thinking of writing a ``Kernel
Programming FAQ'' like the one available in NetBSD's doc, but a
little more comprehensive. No promises yet. :-)
Cheers.
-- Hiten (hmp at FreeBSD.ORG)
More information about the freebsd-doc
mailing list