Greetings Packet Fencers, The PacketFence Installation Guide §4.3 (“Installing PacketFence on existing Linux”) says to “disable SELinux from the /etc/selinux/config file”. Fedora 37 has instructions in that file:
# NOTE: In earlier Fedora kernel builds, SELINUX=disabled would also # fully disable SELinux during boot. If you need a system with SELinux # fully disabled instead of SELinux running with no policy loaded, you # need to pass selinux=0 to the kernel command line. You can use grubby # to persistently set the bootloader to boot with selinux=0: # # grubby --update-kernel ALL --args selinux=0 My question is, does PacketFence depend on SELinux being “fully disabled” or is it sufficient to run “with no policy loaded”? If the verbiage predates the change above, it could be either one. I’m accumulating a few documentation edits in hopes of submitting a pull request and would like to clarify this in the docs for future readers. Thanks, Tom _______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
