On Tue, Feb 4, 2020 at 1:37 PM Pierre Labastie via lfs-dev < [email protected]> wrote:
> Le 04/02/2020 à 07:47, Walter P. Little via lfs-dev a écrit : > > Hi All - > > > > I recently volunteered to give a talk next month about LFS/BLFS to the > San > > Fernando Valley Linux User Group (Los Angeles) that one of my employees > organizes. > > > > The main purpose of my talk will be to inspire people in the audience to > > embark on their own LFS journey, as it is probably the *best* way to see > how > > all the pieces of a Linux machine are put together (certainly was for me > when > > I did my first LFS build in 2003, and has continued to be as I build a > new one > > roughly annually since). > > > > I plan to outline the basic process at a high level using various > pre-staged > > VM snapshots to demo selected points of interest. The idea being to go > from > > zero to a functioning environment in about an hour... so a *lot* of > details > > will be omitted (therefore not cheating the audience of the opportunity > to > > learn on their own after the talk). > > > > If I may ask a couple questions of this group: > > > > 1. What parts of the process are newcomers tending to get hung up on > that I > > should address specifically? (Host system requirements comes to mind...) > > In addition to what Bruce and others said: > - avoid the pdf version for copy/paste, it sometimes insert spaces at the > end > of the lines, which defeats the backslash line continuation character. This > leads to weird errors not always easy to diagnose. > - in any case, be very careful with backslash line continuation characters. > One common error I've seen on -support is people believing that settings of > CC, AR, etc in -pass2 pages come as a commands by themselves, instead of > being > part of the configure command > - commands for gcc-passx are somewhat complicated. Try to analyze them and > _really_ check that the intended commands are applied > - it's very easy to skip a line or a character when doing copy/paste. > Always > double check what is written on screen. If anything goes wrong, erase the > build directory(ies) and extract the tarball again > - refrain from using jhalfs, at least for the first few times when doing > lfs, > but it's a good exercise to write scripts for part or all of the build. > - very frequent error: not setting LFS as root, or not su to user lfs after > logging out and logging in. > > > > > 2. Is there anything coming up on the horizon that you’d like me to > mention?> > > I am looking forward to promoting LFS and informing people about this > > wonderful resource you all have worked so hard on all these years. I > don’t > > chime in on this list very often, but I’m extremely grateful for how LFS > > continues to stay current/relevant while staying true to its long > standing > > mission of being an educational tool. That’s because of the dedicated > efforts > > of this group of editors and contributors, so thanks for all you do! > > > > Regards, > > > > -wpl > > > > > > > > Thanks Bruce, Tom, and Pierre for the feedback. I will incorporate these things into my talk. -wpl > -- > http://lists.linuxfromscratch.org/listinfo/lfs-dev > FAQ: http://www.linuxfromscratch.org/faq/ > Unsubscribe: See the above information page
-- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
