On Wed, Oct 3, 2018, at 5:01 PM, Alex Bosworth wrote: > laptop, I was quite certain, it was going to be a breeze. It's a bit > daunting and discouraging to encounter repeated failures. > > Any suggestions?
Specifically? No. But some general observations. I find it's never "a breeze"! I don't mean to offend, but I think that was likely your first mistake--something wrong "slipped by" and you are being distracted because it's not working as you expected. The book has always worked for me. (For upgrading that is, downgrading doesn't because of incompatible instruction sets.) When it hasn't, it has alway been something I messed up or an oversight when I wasn't paying enough attention. Debugging requires a certain mental approach that's neither common nor easy. It requires one be able to put out of one's mind what's "supposed to happen" and analyze what *has happened* with an "open mind", then ask oneself *what do I know for sure and how do I know it*. There are a lot of assumptions one has made along the way. One can knock them off top-down or bottom-up, but each one must be found and examined. For example, assuming your LFS is properly made when the evidence you're relying on is that it boots and seems to run. I wouldn't be willing to assume the problem is in BLFS. It's also very important to not get discouraged by repeated failures and dead-ends. The becomes its own distraction that gets in the way. One must approach each foray with the same open mind, care, and essential optimism that it will all work once one finds where one went wrong. But on the very positive side, when I find where I made my mistake, I always find it was very educational. -- Paul Rogers [email protected] Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
