> LFS is an amazing project, and there's so, so, so much I don't know. I got > through my first build by blindly following the recipes, and not taking the > time to read up on what I was building.
That's par for the course the first time around. Then we learn what we *should have done*. ;-) > That's why I've started over - trying to learn and read more, taking my > time. So this time make build scripts. If you've got to do it twice, what the chance you'll be doing it again? So, as I said, don't wing-it everytime. > boot Manjaro - I built it without being in the chroot environment. I'm > embarrassed to admit such a stupid mistake, but I did it. "Experience is directly proportional to the amount of computer time wasted." "You're going to make a mistake; guaranteed. Plan for it!" > I've got plenty of questions, but they're OT for this email chain... "Questions are more valuable than answers." ___8<... > > But you have to start with winging it, and eventually notice where Sure, once! > *and* remember the symptoms when they recur. I'm not good at that Remember what? ;-) > > What really made me spend the time replying is > '/usr/src/linux-X.Y.Z'. Next thing, you'll be telling me you build > the kernel as root (yeah, ok, the book does for the first build, and I do. And I never build sudo! It's going to protect me from what? > I admit I build most packages as root). But /usr/src ? Next thing > you'll be advocating /usr/local for BLFS. Oh, wait, you do, don't > you. ;-) I regard LFS as THE system, spartan and barely usable though it be. Everything after that is all local stuff, even if it includes ripping out all the LFS SysV boot scripts from rc on down, and replacing everything with my own redesign. > > My point is that we each, if we continue to use LFS/BLFS, need to > find methods which suit us as individuals. What works for one of us > can be regarded as horrendous by another. Sure, but sometimes one sees something that prompts, "Oh, I never thought of that before! Maybe I can use that." > I'm told that even intel (Skylake and later) now need firmware for Euew! > KMS. On modern hardware (my ryzen laptop is 1920x1080 on a screen > with a 40cm diagonal) the default fonts can be unreadable in many > cases. The kernel has a 12x22 framebuffer font available, my Have you tried telling the framebuffer driver what resolution to use? I admit to being somewhat naive about framebuffers. I've tried them a few times, all on my desktops, and missed CTL-SHIFT-+ much more than any supposed advantage, so now just use VESA drivers. > I just turned 50 and have learned what I know by hacking and poking at > things - but I’ve clearly missed some fundamental material. I would > appreciate one last burst of advice. I think you should be looking for a textbook for a system administration class, not one of the far more plentiful handbook things. Also, look for books about "best practices". -- 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/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
