LFS learning curve is too steep, lacking progressive guidance
Problem
Users generally find the LFS documentation information-heavy, with unreasonable step order, lacking an intuitive entry point and progressive learning path, causing newcomers to feel confused and struggle to complete the build.
Pain points
- Information is presented all at once, making it hard to digest
- Lack of a clear starting point and navigation
- Unreasonable step order (e.g., compiling a cross-toolchain first and adding a bootloader later)
- Documentation does not provide tiered guidance for users of different experience levels
Questions to verify
- Do you encounter difficulties understanding the documentation or finding the step order reasonable when using LFS?
- Would you like a more modular, on-demand learning tool or guide?
- Would you be willing to pay for such a product or switch from your current learning resources?
Evidence
quote · @匿名
LFS takes the wrong approach in my opinion. I did it once manually over a couple of days. I suppose I hoped enduring the pain of waiting for the packages to compile would somehow make me smarter. It didn’t. I didn’t learn much. It was like following a baking recipe. I know I need to add eggs and sugar in the ratio it says but I’d be damned if I could tell you why that specific ratio works.It’s just too much to take in at once. You start by building a cross compilation toolchain but… why? And you add the bootloader dead last, even though it’s the first thing you see when you boot a Linux machine?I reckon a better approach would be to build it step by step, only adding new things once you’ve discovered a need for them.
quote · @匿名
You can tell it's written by real Linux users because the landing page UX doesn't make it immediately obvious where to even start reading.
quote · @匿名
For a long time (probably 2002-2010) I really wanted to do LFS. But I've been on Gentoo since 2004 which, over the last ~22 years, has probably exposed me to almost everything LFS would have, plus a lot more it wouldn't have. I still wish I'd did it way back when. I probably would stumbled through fewer issues had I.
Disclaimer: this card is distilled by AI from community discussions as “pain point evidence”. It is a starting point for need analysis and validation, not a “validated market need”. AI has analytical limits; please open the original discussion above to manually verify before key decisions.