Greetings,
Two issues:
The CacheOS Kernel is missing an explicit call to “/sbin/init” in its config:
zgrep DEFAULT_INIT /proc/config.gz
CONFIG_DEFAULT_INIT=“”
This causes a bug with the Tomoyo LSM of the Kernel, since the Tomoyo LSM treats actions taken by the domain “ /sbin/init” as being strarted directly by “” instead, which messes up the domain call order of that security implementation.
Explicitely specifying “init=/sbin/init” in the bootloader does not seem to fix this.
Actual possible fix:
Simply define “/sbin/init” explicitely as the CONFIG_DEFAULT_INIT init binary in the kernel configuration of future kernel versions.
Second related bug:
Tomoyo has its startup process trigger set as “/usr/lib/systemd/systemd” instead of “/sbin/init”. While “/sbin/init” is a symlink to “/usr/lib/systemd/systemd”, Tomoyo needs the actual entry in the process list to match, else it starts later than it should - namely when /sbin/init calls itself on later execution via “/usr/lib/systemd/systemd”.
zgrep TOMOYO_ACTIVATION /proc/config.gz
CONFIG_SECURITY_TOMOYO_ACTIVATION_TRIGGER=“/usr/lib/systemd/systemd”
Fix:
Set this kernel config value to “/sbin/init” instead.
That should resolve all Tomoyo related Problems with the current Kernel(s). 
