On 8 November 2017 at 15:24, Bernhard Voelker <mail@bernhard-voelker.de> wrote:
On 11/08/2017 09:28 AM, Thorsten Kukuk wrote:
Why should they be moved out of /var? /usr is not writeable, /var is writeable. /var is for variable data, /usr for static. Everything you listed is variable data generated at runtime, so it's not possible to put that in /usr (since that could be read-only) and exactly for this data we have /var.
TBH I didn't follow the "move RPM DB to /usr/lib" discussion for long, but I read your statement as THE argument against the move, isn't it?
I personally do not have a strong preference, but moving data around just for the sake of a file system type doesn't seem to warrant the hassle. Well, if it works (and also works with other file system types!) - which I'll see soon -, then I won't bother too much.
Have a nice day, Berny
I can assure you Thorsten is not arguing against the move of the rpmdb to /usr - He was the one telling me to look at it :) The need to move rpmdb is justified by a number of usecases - supporting snapshot centric workloads, read-only filesystems, and general backup sanity (/var/lib/rpm is the only thing in /var which needs to be treated as 'core system information' to backup) In discussions with rpm upstream, we came to the agreement that /usr/lib/sysimage/rpm is the correct place to put the rpm database when you are concerned about those use cases Of course, with the openSUSE and SLE distributions we are installing btrfs by default, with snapshotting enabled, so we have an immediate justification for using that location by default on the *SUSE distributions, hence my move. We also have openSUSE Kubic which has a read-only filesystem, and it's nice that Kubic will not need to diverge from the base Tumbleweed configuration. We aren't an isolated group with these needs - RH have similar needs with rpm-ostree. They had been using /usr/share/rpm before I had started this discussion but appear to agree that /usr/lib/sysimage/rpm is the correct location for their similar usecases to our own. And of course everyone now has an opportunity to tidy up their backup configuration if they were (like me) having to snipe /var/lib/rpm when backing up their _system_ because they were otherwise treating /var as part of a different tier of backup. fillup-templates is a different type of data from the rpmdb, but it is still grossly missplaced in /var/adm According to the FHS /var/adm is meant to be for variable log data. fillup-templates are not variable, and not logs. The data is static - the templates do not change at any time besides package installation. However unlike rpmdb, fillup-templates is not system sensitive, system specific, system-image data, so I do not think we can justify putting it in the new /usr/lib/sysimage/ location The data has a lot more in common with information like man pages, which are stored in /usr/share. Therefore my proposal (being discussed on opensuse-packaging@ at the moment) will be to relocate /var/adm/fillup-templates to /usr/share/fillup-templates Hope this helps. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org