On Sun, Sep 24, 2006 at 02:42:03PM -0300, Duane Whitty wrote:
[...]
>
> >
> >If you want to just merge/copy some manual pages parts in the
> >arch-handbook then you miss the point since there's no gain in
> >duplicating the information. For example if you want to talk about the
> >ULE schedule we are not looking for a sched_ule(4) manual page copy but
> >a documented text covering the features, how to use it or code with it,
>
> I agree.
>
> >etc.; another example would be the USB devices, if your look at the
> >current chapter, the text explain how the USB stack works (it's quite
> >the case) but miss a part explaining how to write a simple USB (HID?)
> >driver.
>
> I somewhat agree but I also don't believe that the
> Architecture Handbook is the best location for detailed
> tutorial information on how to develop for a specific
> subsystem; Just my opinion. Is that not be what the
> Developers' Handbook is for? [Not meant as a rhetorical
> question]
>
[...]
The Developers Handbook is for people who want to develop under FreeBSD,
the Arch Handbook is for people who want to develop or understand
FreeBSD internals.
Just read, as example,
http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/devicedrivers.html
etc.
Marc
_______________________________________________
freebsd-doc@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-doc
To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org"