> On 2020-04-18 18:46, Sreyan Chakravarty wrote: > > Well, since selinux operates on file/directory contexts and no files or directories are > involved as mentioned bySamuel: "The header contains pointers to the rest of the > data. It doesn't have to know anything about the filesystem." And since selinux > is implemented in > the kernel and that isn't "running" yet. It stands to reason that you > won't have problems. > > At least that is my stab at explaining it. :-) Thats interesting but then why did I get the problem in the first place then ? My other topic is labelled SELinux is blocking Hibernate, and SELinux was legitimately interfering with the hibernate process, specifically blocking systemd-sleep to read the hibernate file. The weird thing is why did it stop me once and then didn't stop me once I set it back from permissive to enforcing ? Did SELinux "learn" somehow that it is ok to allow access to the swap file ? This is all very confusing. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/users@xxxxxxxxxxxxxxxxxxxxxxx
