I am thinking about adding a new section to the book to address two tickets:
#2196 LSB compliance for LFS #1673 Why is each package in the book? The tentative title of the section is "LFS and Linux Standards". I'm thinking about adding it as the first section of the Introduction, but it could go in the Preface, the Appendix, or some other location in Chapter 1. The first issue I'd like to discuss now is the name and location. I'm requesting feedback on the above proposal. --------- The contents of the section will discuss those things we do to make LFS as close as possible to a 'standard' Linux system. This includes references from the Linux Standards Base (LSB), Filesystem Hierarchy Standard (FHS), and The Open Group Single UNIX Specification (POSIX). http://refspecs.freestandards.org/LSB_4.0.0/LSB-Core-generic/LSB-Core-generic/book1.html http://www.unix.org/single_unix_specification/ http://www.pathname.com/fhs/pub/fhs-2.3.html I would also add a subsection discussing why each package in the book was selected. Most packages are there, of course, because the programs they provide are needed to meet the goal of creating a system capable of self-replication, but a few packages are there because of choice (bash vs sh, vim vs vi, etc). We might also consider addressing why some packages/programs are omitted from LFS but are required by the LSB Core Specification (bc, at, batch, cpio, lpr, sendmail, etc). We don't even have at or batch in BLFS. (Of the above, the only one I use is bc.) After I have a draft of the new section, I'd like to address the above in more detail. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
