Qrux wrote:

> One solution is to keep saying: "Reread Section 5."

5.3?

> I'm exploring other solutions, because I think it's silly to insist that the
> book is well-written when, for every single release, many people are confused
> by how to begin Chapter 5.  I didn't have an issue.  But I can certainly
> understand how others might.

The problem is that some users are trying to build LFS before they have 
sufficient background.  You obviously do have the background, but it's not 
appropriate for others who have basically never used a shell to start LFS until 
they have developed more experience.  The first clue is when users refer to 
folders instead of directories.

> If you always have the same issue at the same point in the book, you might
> come to the conclusion that it's a hard part, and only
> (careful|smart|hard-working) people will understand.  You could also conclude
> that it's a confusing part (perhaps also hard), and while we need people to
> be able to read, we can also provide a warning here that highlights the
> relative importance of this statement.
> 
> The point is, there is plenty of prose in the book.  I could completely skip
> every word of Section i, Section ii, Section iii, Section iv, and Section v,
> and successfully build the book.  In fact, I've done exactly that, and had no
> issue.

Yes, you could, but as I said, you have the appropriate background.  I think 
everyone needs to read vi and vii.

> But, then, you want me to read Section vi and take it as gospel?  Are you
> starting to understand what I mean about signposts?  There is nothing special
> about the appearance of Section iv.  Do you see how that might relate to
> organization of the information, and not the content?

Speaking of understanding, what does that mean?

>> We did add to 5.4: "Go back and re-read the notes in the previous section.
>>  Understanding the notes labeled important will save you a lot of problems
>> later."
> 
> And, while the unpacking instructions in 5.3 are indeed marked as
> "important", do you also see that Sections 5.1 and 5.2 are completely
> irrelevant to the explicit directions?  You know how some text books often
> have sections which are only meant to be read in an advanced course?  Well,
> 5.2 is exactly like that.  But, why strew information all across the book?
> Chapter 5 is the backbone to the entire thing.  But it starts with a somewhat
> irrelevant section (5.1), and an advanced section (5.2).  Then, you want
> people to know that the "Important" part of (5.3) is *actually* important?
> 
> Here's something "Important" from 5.2:

[deleted quote]

I can agree that the section of 5.2 could be changed to a note.

There are 3 "important" sections in chapter 5, and 6 in chapter 6.

> I'd argue that it's not important at all.  Maybe to someone who's taking LFS
> and working on a derivative work.  Or to someone who's messing about with the
> toolchain.
> 
> But, put simply: it's pretty hard to separate the complete irrelevance of
> 5.2-"Important" from the absolute necessity of 5.3-"Important".  This is an
> issue of poorly structured book organization--not the information intended to
> be conveyed in the book.

Is the extent of the changes you think are needed to just relabel one section?

   -- Bruce
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to