Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 May 2006 22:17:51 +0300
From:      Giorgos Keramidas <keramida@FreeBSD.org>
To:        Marc Fonvieille <blackend@FreeBSD.org>
Cc:        doc@FreeBSD.org, cvs-doc@FreeBSD.org, Hiroki Sato <hrs@FreeBSD.org>, cvs-all@FreeBSD.org, doc-committers@FreeBSD.org
Subject:   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
Message-ID:  <20060512191751.GA17919@gothmog.pc>
In-Reply-To: <20060512190629.GD83314@abigail.blackend.org>
References:  <20060507163758.GA51229@gothmog.pc> <20060508.083506.59684188.hrs@allbsd.org> <168248421.20060508023256@rulez.sk> <20060513.012824.32706574.hrs@allbsd.org> <20060512190629.GD83314@abigail.blackend.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2006-05-12 21:06, Marc Fonvieille <blackend@FreeBSD.org> wrote:
> On Sat, May 13, 2006 at 01:28:24AM +0900, Hiroki Sato wrote:
> > Daniel Gerzo <danger@rulez.sk> wrote
> >   in <168248421.20060508023256@rulez.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.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060512191751.GA17919>