On 2017-10-04 14:05:53 +0200, Richard Brown wrote:
On 4 October 2017 at 13:38, Carlos E. R.
wrote: On 2017-10-04 13:16, Richard Brown wrote:
For systems with a read-write rootfs, we will be slightly bending the rules of the FHS, in the sense that the FHS claims /usr should be 'read-only data'
What about machines that share /usr from a central machine over the network?
Putting the rpmdb in /usr/share is no worse than the current situation
Right now machines sharing /usr from a central machine over the network are going to have an rpmdb that will contain an invalid picture of the contents of /usr
Any person with root access to any machine accessing that shared /usr can attempt to install/remove packages. If the share is read-write that will currently lead to changes for all systems but only the system doing the installation will be aware of what it did and able to uninstall the rpms that changed /usr
This will lead to untrackable inconsistencies in other areas of the filesystem, as only /usr is shared.
Hmm it depends a bit on the use case: if people want to share /usr (for whatever reason...) and have the rpmdb in /var/lib/rpm, they can still install 3rd party rpms, which only install files into /opt/*, without causing "inconsistencies" to the other systems' rpmdb. Anyway, this use case can still be realized with the new rpmdb location. Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org