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

[Daniel Gerzo]

Hello Hiroki,

Monday, May 8, 2006, 1:35:06 AM, you answered:

> Giorgos Keramidas <keramida at ceid.upatras.gr> wrote
>   in <20060507163758.GA51229 at gothmog.pc>:

ke>> I would probably like seeing something like an ``Embedded FreeBSD''
ke>> chapter in the Handbook, where all available options would be listed,
ke>> including NanoBSD, FreeSBIE, and the upcoming TinyBSD too.

>  I think it is good for us to have a document for such variants of
>  installation method, but I disagree with adding a chapter to Handbook
>  for them.  This is because NanoBSD and so on are nothing but special
>  methods of build/installation and IMHO they are beyond the scope
>  of Handbook.

 We have even more advanced topics in Handbook than NanoBSD is. See
 next paragraph.

>  As you know, Handbook introduces a basic installation procedure
>  and explains several common tasks for system administrators basically
>  on the assumption that they are using a normally-installed FreeBSD box.
>  So, we include advanced topics beyond the scope such as articles/multi-os
>  or article/fbsd-from-scratch (both explain some special methods of
>  build/installation) as articles so far.  In short, I think Handbook
>  should be organized for average sysadmins, not as an encyclopedia,
>  and topics like NanoBSD are too advanced.

 Then we can tell the same about the whole MAC and Audit chapters,
 since they seem a lot more advanced and tricky to me than NanoBSD.

> Daniel Gerzo <danger at rulez.sk> wrote
>   in <198819470.20060508002924 at rulez.sk>:

da>> What I dislike on articles is that they are not under such view as a
da>> Handbook chapters are, so they are getting outdated easier as well as
da>> people often dig only in Handbook for information.

>  How likely sentences are getting outdated is nothing to do with
>  whether it is in Handbook or not, and if people often look for information
>  only in Handbook we should encourage them to look at the other materials
>  by adding pointers, for example, instead of adding all of information into
>  Handbook.

 The FreeBSD project is known as a very well documented Operating
 System. As far as I've been working with FreeBSD and seeking for
 documentation and more information about things I wanted to try
 out, the first place I've looked at was our great Handbok. I feel
 that having documentation at one place is more comfortable than
 googling it for XY minutes.

 Also if I was an avarage system administrator and I would notice a
 NanoBSD chapter in Handbook, I would say: "Wow, what is this?
 Let's see...". So there's a higher chance that more people can
 notice it and play with it.

 At least, we have some discussion about it here, the doc@ list seemed
 to me as it has been already dead :-)
 
-- 
Sincerely,
  Daniel Gerzo