Also note that storing config or state data in /lib is a violation of the Filesystem Hierarchy Standard (http://www.pathname.com/fhs/pub/fhs-2.3.html) and hence of LSB. According to those standards, such data should go to /etc, /var or /srv. If /var is ruled out because of late mounts, then /srv probably too, so /etc is the only remaining standard-compliant option.
I call this a bug in the file layout, not just a wish.
But i have a feeling that once a ticket has been set to "won't fix", no one with the power to re-open it bothers to read the thread and reconsider. What would we have to do to gain attention?
Also note that storing config or state data in /lib is a violation of the Filesystem Hierarchy Standard (http:// www.pathname. com/fhs/ pub/fhs- 2.3.html) and hence of LSB. According to those standards, such data should go to /etc, /var or /srv. If /var is ruled out because of late mounts, then /srv probably too, so /etc is the only remaining standard-compliant option.
I call this a bug in the file layout, not just a wish.
But i have a feeling that once a ticket has been set to "won't fix", no one with the power to re-open it bothers to read the thread and reconsider. What would we have to do to gain attention?