As I'm going through the BLFS-Bootscript dependencies, there are many
scripts which should've have a Should-Start dependency on $remote_fs
because they live in the /usr hierarchy. Things like sysstat can't exist
in sysinit, no network manager because it needs dbus and dbus needs
networking, etc. This used to be explicitly required in earlier variants
of the FHS. While the document pays homage to the idea with static vs
variable filesystems (even using /usr as an example in a chart as a
static filesystem that can be remotely mounted), there is no requirement
in current FHS-3.0 (it would have been exceptionally difficult to make
dbus, systemd, or elogind FHS compliant under FHS-2.3).
Since this requirement is no longer present, does LFS want to explicitly
disallow a remote /usr mount? That is actually where we are currently,
as well as almost every other distro out there -- /usr must be a local
filesystem -- but it is not explicitly stated (should a note be added to
LFS to this effect?). I'm reasonably certain that I already know the
answer, and am proceeding locally as if I do, but I'm throwing it out
there so that it was at least discussed. FYI, while LFS is fine on SysV,
several changes are required to BLFS to make a remote /usr supportable
again (and this is almost impossible as noted above for desktop systems,
and really difficult on systemd - though I do have some ideas about
netbooting lab PCs with no local HDD at all as this is actually easier
for this old use case... ;-) ).
--DJ
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
