r6798 - in trunk: BOOK/introduction/welcome BOOK/x/installing auxfiles/xorg

Dan Nicholson dbn.lists at gmail.com
Thu May 31 06:30:46 PDT 2007

On 5/31/07, Randy McMurchy <randy at linuxfromscratch.org> wrote:
> dnicholson at linuxfromscratch.org wrote:
> > Author: dnicholson
> > Date: 2007-05-31 01:26:14 -0600 (Thu, 31 May 2007)
> > New Revision: 6798
> >
> > @@ -90,7 +90,8 @@
> >      for an x86 PC as the Sun drivers will expect to see SPARC symbols
> >      exported from the kernel.  Failure to follow this warning will result
> >      in a display lockup, which requires a hard reboot, when configuring
> > -    <application>Xorg</application> for the first time.</para></warning>
> > +    <application>Xorg</application> for the first time. For this reason,
> > +    these drivers have been commented out in the wget file.</para></warning>
> Why would this still be a warning? If the drivers have been commented
> out (they have), what is there to warn about. Please, Dan, consider
> what is *in* the book, not what *used* to be in the book.
> It's my feeling that we don't place warnings in the book for things
> that are not there any longer in the theory that folks won't change
> their scripts unless they see a big warning box.
> Though it could be thought that someone needs to *uncomment* the
> drivers from the wget list if they are building on Sparc, I'd bet
> that the BLFS instructions wouldn't work for Sparc anyway, so I
> think the warning could be changed to a note or just a simple
> paragraph.
> Bottom line is that I feel (and just my opinion) a warning should be
> placed to remind a user to *do* something or the build will fail,
> but in this case, simply following the book without any special
> attention to anything else creates a successful build.

I have no problem removing the warning. The comments in the wget file
are more than enough for me. I was just sticking with what's in the


More information about the blfs-book mailing list