On 08/11/17 06:23 PM, Stefan Brüns wrote:
May be the correct term would be "frozen" - of course, at some point /usr/ was writable, otherwise it would not exist at all.
Perhaps the issues should be this: What is the minimal set of sub-trees of the file system, other than /home, that needs to be writeable on a 'frozen' system? First we need to define 'frozen, don't we? I'd take it as one that isn't being updated, so we are not changing /bin, /usr/bin, /lib, /usr/lib. This in turn gets to the questions a) What is 'dynamic' and needs to be regularly backed up or must be writeable such as the caches and spool areas? b) What is the static part that would need to be restored/preserved as a "system image"? Now really, this is unfair, as that 'frozen' means that we are never applying updates so the RPM database isn't being updated. But how mch can the system config be changed? Can pritners be added or changed? that affects /etc/cups, but what about a hypothetical "adm" subtree? I believe that we need to think if terms of sub-trees rather than top level file systems. But then I'm biased, being a LVM user and being rather aggressive about isolating sub-trees, for example /usr/share and ~/Documents and more. OK, I'm also trying for a 'mount on demand' but that's beside the point :-) -- "If someone is going down the wrong road, he doesn't need motivation to speed him up. What he needs is education to turn him around." -- Jim Rohn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org