Hello. The userland tools for TOMOYO 2.2.0/2.3.0 were updated.
/sbin/tomoyo-init (the policy loader which is automatically executed when /sbin/init starts) mounts sysfs only when /sys/kernel/ directory does not exist. However, on SUSE (and maybe other) environments, /sys/kernel/debug/ directory exists even if sysfs is not mounted. On such environments, /sbin/tomoyo-init tries to mount securityfs on /sys/kernel/security/ without mounting sysfs on /sys/ directory. As a result, mounting securityfs fails (because /sys/kernel/ exists but /sys/kernel/security/ does not exist) and /sbin/tomoyo-init exits without loading files in /etc/tomoyo/ directory. Therefore, booting the system fails with kernel panic. Profile 0 (used by '<kernel>') not defined. To solve this problem, I modified to mount sysfs when /sys/kernel/security/ directory does not exist (rather than when /sys/kernel/ directory does not exist). Those who want to try TOMOYO 2.x on SUSE environments, please use the updated tarballs. http://sourceforge.jp/frs/redir.php?f=/tomoyo/41908/tomoyo-tools-2.2.0-20110211.tar.gz (for TOMOYO 2.2) http://sourceforge.jp/frs/redir.php?f=/tomoyo/48663/tomoyo-tools-2.3.0-20110211.tar.gz (for TOMOYO 2.3) Also, regarding tomoyo-tools-2.3.0-20110211.tar.gz , I fixed a bug in tomoyo-diffpolicy . Also I removed help2man and gzip packages from build dependency by using preformatted manpages. Thanks. _______________________________________________ tomoyo-users-en mailing list [email protected] http://lists.sourceforge.jp/mailman/listinfo/tomoyo-users-en
