Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#38220 - [tomoyo-tools] 2.5.0.20130406-2 Advice for TOMOYO_trigger is wrong
Attached to Project:
Community Packages
Opened by Florian (Katastrophe) - Saturday, 21 December 2013, 18:52 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 26 February 2014, 11:53 GMT
Opened by Florian (Katastrophe) - Saturday, 21 December 2013, 18:52 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 26 February 2014, 11:53 GMT
|
DetailsHi,
when TOMOYO_trigger is set to the command line according to the installation advice to TOMOYO_trigger=/usr/bin/init Tomoyo does not work properly(at all?): For example tomoyo-editpolicy shows only the kernel domain. dmesg output: [ 0.003387] TOMOYO Linux initialized Setting it to TOMOYO_trigger=/usr/lib/systemd/systemd fixes the issue dmesg output [ 0.003387] TOMOYO Linux initialized [ 6.241253] TOMOYO: 2.5.0 How can I ensure that I always have the correct init path in my boot configuration? Greetings |
This task depends upon
> How can I ensure that I always have the correct init path in my boot configuration?
As CONFIG_SECURITY_TOMOYO_ACTIVATION_TRIGGER is set properly in the stock configuration files, leaving out TOMOYO_trigger is the best approach.