I think the warning should be there and/or else (as I was told) a note informing users to script their build should be put there.
You know... it just occurred to me, I started a build let it run about 15 minutes, then realized I forgot to do something and so stopped it. Then I fixed what I forgot and restarted it from the beginning. The book says that we need to backup the temporary toolchain because subsequent commands will damage the temporary toolchain. Do I need tho copy my backup glibcbecause of this. Or perhaps just upack the glibc tar ball again. What do you think? :-)~MIKE~(-: On Thu, Jul 31, 2014 at 3:07 AM, akhiezer <[email protected]> wrote: > > Date: Thu, 31 Jul 2014 11:00:49 +0100 > > From: [email protected] (akhiezer) > > To: LFS Support List <[email protected]> > > Subject: Re: [lfs-support] Please, teach me how to fix problems. > > > > > From: Patrick Kennedy <[email protected]> > > > Date: Thu, 31 Jul 2014 17:20:33 +0800 > > > To: LFS Support List <[email protected]> > > > Subject: Re: [lfs-support] Please, teach me how to fix problems. > > > > > > I prefer working from the online HTML version. However, it's good to > have > > > a PDF version that will not change as newer versions of the LFS are > issued. > > > It's a permanent record - so, you can keep it as a long-term > document; the > > > web site will change periodically. Also, if you are temporarily > offline, > > > you can still use the PDF version. You can also view the PDF on > different > > > devices - so, it's a matter of convenience and choice as well. > > > > > > > > > On Thu, Jul 31, 2014 at 4:51 PM, Simon Geard <[email protected]> > wrote: > > > > > > > On Wed, 2014-07-30 at 10:27 -0500, Bruce Dubbs wrote: > > > > > You are probably trying to select the commands from a pdf before > > > > > pasting. That's a problem with the pdf generation. Use the html > > > > instead. > > > > > > > > Out of curiosity, what's the major use-case for people using a PDF > > > > version of the book, as opposed to the HTML version? PDF seems such a > > > > poor match for a project like LFS... > > > > > > > > > > PK (TP): you can of course download the html tarball - chunked or > no-chunked > > - and read them offline too; and they are a 'parmanent record' too. Ref > e.g.: > > > > http://www.linuxfromscratch.org/lfs/downloads/7.5/ > > > > And similarly for blfs. > > > > > > SG: Often folks 'prefer' pdf (or at least want it in parallel with .e.g > > html versions) because it looks 'nicer' - which I guess is fair enough; > > cf TeX docs. Of course, one could - at least up to a point - adjust the > > html sources to render in a more-preferred font/style/&c. > > > > > But I guess that a central question being raised (again?), at least > implicitly, is: if the copy'n'paste from pdf is proving to be a _known_ > and _ongoing_ problem, then should a note be auto-inserted at the top and > centre of the pdf version to give an appropriate warning. > > > akh > > > > > > -- > -- > http://lists.linuxfromscratch.org/listinfo/lfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page >
-- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
