On 2022/06/14 5:20, Andre T wrote: >> Please check that /sbin/tomoyo-init exists and can be manually executed from >> a shell on PC2. Then, please check that either >> >> Calling /sbin/tomoyo-init to load policy. Please wait. >> >> or >> >> Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist. >> >> appears in the dmesg output when you reboot PC2. > > From what it seems so far neither of the two lines seems to appear on the PC. (dmesg output included furthest below) > OK. Then, I guess that the program which is specified using CONFIG_SECURITY_TOMOYO_ACTIVATION_TRIGGER does not exist on PC2. It seems that Arch Linux has multiple choices for the init system. https://wiki.archlinux.org/title/init https://wiki.archlinux.org/title/Mkinitcpio I guess that the program used as init on PC1 and PC2 differs. Please compare ls -l /proc/1/ (as root user) between PC1 and PC2. If the program indicated by /proc/1/exe differs, try specifying that program using TOMOYO_trigger= kernel command line parammeter; like TOMOYO_trigger=/usr/lib/systemd/systemd if /proc/1/exe indicates /usr/lib/systemd/systemd . > (I'm noticing the "Unknown kernel command line parameters ..." line so whether > or not that might affect tomoyo i'm not sure, but it's definetly to be checked > out what's going on there none the less) That is expected behavior and is irrelevant to this problem. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=86d1919a4fb0d9c115dd1d3b969f5d1650e45408 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8bc2b3dca7292347d8e715fb723c587134abe013 Regards.
TOMOYO
Fork