5 ms·
It feels to me like you have approached this with a wrong mindset, like you focused too much on finishing the whole process. With LFS you must put substantial
by aflukasz 2y ago
It feels to me like you have approached this with a wrong mindset, like you focused too much on finishing the whole process.
With LFS you must put substantial amount of value into the journey itself. It's not about copy-pasting commands, it's about trying to actually understand what and, more importantly, why your are doing each step. My recollection is that LFS docs were good in helping with that. Or maybe it was coming from reading docs of the actual components as I went along? I don't remember, probably some mix of both.
I did set LFS system up once, I think it was 2001 or 2002. I specifically remember that it took many days (due to compilation times), was very interesting, and at the end I was putting final touches to my mutt and slrn configs. With a vague memory that I had some TODO for mutt that I didn't finish, still lingering in my mind, apparently! :)
All in all, great and satisfying learning experience.
I would not use such system as a daily driver, though. I think it's good only if you have time and want to learn. I'm curious if someone here is brave enough to have different approach.
- oorza 2y agoLFS to a computer scientist should be like soap to a chemist. Something you can do as a fun, educational experiment, but not where you source a necessary tool for your life.
- NegativeK 2y agoI daily drove it for a few months, back in the early 2000s (like many in this thread, it seems.) I kept it updated by subscribing to Freshmeat emails for releases, and I'd download and install the tarball. My review is that I'm glad I did it, it's a terrible idea, and it's debatable (honestly, not facetiously) as to whether the classes I skipped were more valuable.