Currently the FHS has a discussion in Chapter 2 about sharable and unsharable files that are static or dynamic.
The example shows /usr as a prototypical static, shared directory. The implication is that /usr can be mounted from a remote host. The problem is that /usr has become a place that is necessary before a network mount is available. For instance, if an administrator finds it necessary to use lspci, or lsusb before the networked /usr is mounted, the pci.ids and usb.ids files are not available. Where then, should a program store auxiliary data files that may be needed before any networking is configured? Candidates from the current top level programs include /bin, /boot, /dev, /lib, /root, and /sbin. None of these seems appropriate. Perhaps a subdirectory hierarchy in /lib, say /lib/data/<package>/ may be appropriate, but that goes against the current definition of /lib that says: 'Essential shared libraries and kernel modules'. Another option is yet another top level directory, but that is unappealing. I take no position on this topic right now, but want to present it for discussion. -- Bruce Dubbs _______________________________________________ fhs-discuss mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/fhs-discuss
