Re: cvs commit: doc/en_US.ISO8859-1/books/handbook Makefile book.sgml chapters.ent doc/en_US.ISO8859-1/books/handbook/nanobsd Makefile chapter.sgml

[Giorgos Keramidas <keramida_(_at_)_FreeBSD_(_dot_)_org>]

On 2006-05-12 21:06, Marc Fonvieille <blackend_(_at_)_FreeBSD_(_dot_)_org> wrote:
> On Sat, May 13, 2006 at 01:28:24AM +0900, Hiroki Sato wrote:
> > Daniel Gerzo <danger_(_at_)_rulez_(_dot_)_sk> wrote
> >   in <168248421_(_dot_)_20060508023256_(_at_)_rulez_(_dot_)_sk>:
> >
> > da>  Then we can tell the same about the whole MAC and Audit chapters,
> > da>  since they seem a lot more advanced and tricky to me than NanoBSD.
> >
> >  Not the same.  Again, what I wanted to mean is that it is not a
> >  typical installation/building method for users who read a chapter
> >  for normal installation in Handbook.  I did not mean by the word
> >  "advanced" it is difficult to understand or simply complex, so I
> >  showed multi-os and fbsd-from-scratch as examples.  They are
> >  actually useful configurations but not topics which Handbook has to
> >  cover in detail, and I think they are ones which users should read
> >  *after* Handbook.  Mixing these two sort of topics often makes
> >  Handbook's structure complex.  A lot of information at one place is
> >  not always good.
> [...]
>
> I share the same opinion.  I'm more for an embedded-handbook since
> it's a very specific domain and since we want FreeBSD to cover the
> embedded world in a more important way than it was till today.  A
> specific book or article will give us more ease to add and develop
> documentations on this area.

Ok, I'll split-off "NanoBSD" in a nanobsd/ article for now.  When we
start getting more documentation for embedding FreeBSD, we can either
make it a collection of articles or a book.

_______________________________________________
freebsd-doc_(_at_)_freebsd_(_dot_)_org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-doc
To unsubscribe, send any mail to "freebsd-doc-unsubscribe_(_at_)_freebsd_(_dot_)_org"