On 12/29/21 09:59, Stephen John Smoogen wrote:
The modern day case where /usr is read-only is inside a container and you put an overlay or using some sort of linking to /var which is read-write in case of reboots.
Right, that makes sense.
To me this is like saying 'move everything into /usr but because its volitile move it back into /var but in a sub-directory from where it was so you can keep an image running.' In this case, this doesn't sound like any savings and more of a headache of why did it corrupt this time.
But this doesn't. Why would you need to move the rpmdb? Users probably aren't installing rpm packages in containers at run time (particularly if /usr is read-only); installation typically happens when building the container image, at which point /usr isn't read-only.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
