Hello, On Mar 21 16:39 Dimstar / Dominique Leuenberger wrote (excerpt):
Transactional Updates ... ... requires a very strict separation of program files managed by the package manager from the data part
how is that requirement enforced? I assume via btrfs subvolumes for the "data part". But what about /etc/ ? Files in /etc/ belong both to the package manager and to the user when the user works as admin. I assume while a transactional update is running the user must not change files in /etc/. I assume on enterprise systems the admins know that but what about unexperienced openSUSE users who may run whatever YaST or other config programs while a transactional update is running? Perhaps a transactional update may even run unnoticed by the user somehow in the background? Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org