Re: SLFS book chapter proposals

On Sunday 21 December 2003 21:47, Archaic wrote:
> On Sun, Dec 21, 2003 at 01:19:47AM +0200, Christos Gioran wrote:
> > I vote: Let's build a self contained book, that if read will make the
> > reader owner of a very secure box and enough knowledge to keep it that
> > way.
>
> You are contradicting yourself from before. 

You noticed too!! :-) Allow me to explain myself...

> We can give self-contained
> instructions on how to build a system, but we can't teach much about it
> without tons of verbage. This is where I think the links to already
> existing resources comes in handy. Let's face it, neither LFS nor BLFS
> strive to teach you how to use your system. It's such a large topic that
> can never fully be realized without massive amounts of dedicated
> researchers and editors. However, we can teach some general concepts and
> practices, and give the reader the base needed to then continue in his
> quest for further knowledge.

After this task switches into maintanance mode (i.e. the layout and basic 
packages have been decided upon, only improvements implemented) then we can 
(and should) start looking at the subject with a broader prospective. The 
initial links to "keeping it secure" bibliography could start becoming text 
written by us, backed up by the knowledge we will have gathered building the 
thing. Thus the project will have begun its life as "*building* a secure 
system" and afterwards it will start transforming (hopefully) to the Tome 
entity mentioned previously. But *definetely* our first edition could not in 
any way be this Tome. Hope this clarifies my sayings to this point. Apologies 
for any inconsistencies.

> How many people really learned how linux worked from reading LFS versus
> how many used LFS as a springboard to greater understanding? LFS and
> BLFS are great at teaching some basics and giving the reader enough
> understanding to then seek further knowledge without getting lost in all
> the noise that is out there.

The point not clarified (at least IMO) as of yet is whether we will mention 
only differences from the LFS book or list *all* compilation commands. My 
proposal is that after deciding on the contents of the book, we will have a 
clear idea of the extent of differences. If it is tolerable then document the 
differences only. Otherwise (most probably) we will have to include all 
instructions from the beginning.

> Archaic

-- 
himicos
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-security
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page