For myself, after my first LFS-4.1 build, all by hand with copious written notes from the book, I began using a "directory watcher" called "git" by Ingo Bruekel. It was apparently "abandon-ware", and I found a few "fixes" necessary. And of course, the name got usurped. So I renamed my version, but I still use it. My build scripts basically encapsulate the commands in the book.
But all this isn't, I think, the point from the modern newbie's perspective. Because modern distros strive to provide a complete desktop environment competitive with common, errrm, commercial software, they hide what the fundamental parts of a useful Linux system are. I think, clearly, newbies don't know what additions from BLFS to the extremely Spartan LFS makes a modestly functional, manageable, common system which should be made first. I think if we stripped away all the foliage from the systems we use, we'd find underneath a fairly common, consistent set of packages--from which our individual interests caused divergences, mostly by addition. I think what the newbie wants is a page in BLFS that lists the packages, and order, that get them to that next plateau of functionality. -- Paul Rogers [email protected] http://www.xprt.net/~pgrogers/ Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://www.fastmail.fm - Same, same, but different... -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
