On Mon, 27 Jul 2020 at 01:19, Bruce Dubbs via lfs-dev <lfs-dev@lists.linuxfromscratch.org> wrote: > > I haven't checked, but I think you may be taking the word 'minimal' too > literally. Perhaps we should just change the description to: > > Creating a Limited directory layout in LFS filesystem > > Whether or not all the directories created in Chapter 4 are needed in > Chapters 5 and 6, they are certainly needed in Chapters 7 and 8. When > they are created is really not very important. > > -- Bruce
I am more in a "why does it even need to be limited in Chapter 4" camp than literally looking to make one part of an ad-hoc split more (or less?) minimal/limited. If, as you say, in LFS's "build every package as root and so don't become aware of what directories are getting created when, why or by what" model, it doesn't matter when, then I can't see the benefit, to the learning experience of the "new to Linux" user, in performing the "core" directory hierarchy creation in two stages. Introducing a standard, rather, the FHS, and creating that hierarchy, modulo directories that LFS can justify leaving out, in one place, would seem to have a more coherent feel than splitting things up without saying why, or rather saying why, but then recognising that that's not why one needs to do that. Having said that, I'm sure there are reasons why a "limited" hierarchy was thought to be a good thing to get across to users. -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
