Well, looks like /usr is the proper future location for selinux store. The point of my idea is to provide a better support to keep consistency for the critical components of system when it has different kind of rollback mechanisms (btrfs with snapper, ostree based systems).
For example, a customized btrfs installation where you have the following subvolumes: root > / home > /home srv > /srv opt > /opt usr_local > /usr/local var > /var And the case of the Atomic spins. As you know, some things are incompatible with the current rollback mechanisms, like the package manager database that was relocated to /usr, and it's the same case for the SELinux store. When you develop a rollback mechanism, you want to exclude some directories to save space or simply bc said directory must be always mutable and the data needs to keep that state (logs, vm pool disks). The thing is that we don't have coordination on how to handle all these kind of mechanisms, distributions are evolving, and people have their own preferences on what rollback mechanism to use, we have traditional systems with btrfs or LVM rollbacks, and the new atomic & immutable systems. So we need to discuss this issue further before it's too late and it becomes very difficult to change a configuration to give everyone the opportunity to use the mechanism that works best for them without running into difficulties with the filesystem architecture or having to resort to risky or complex workarounds. Like the current case of Atomic spins using /etc now but with the future transition to /usr, this will add more complexity bc is read-only. -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
