On 9 May 2011 11:50, Kay Sievers <[email protected]> wrote: > Works all fine here with: > # grep SECURITY .config > CONFIG_EXT3_FS_SECURITY=y > CONFIG_EXT4_FS_SECURITY=y > # CONFIG_SECURITY_DMESG_RESTRICT is not set > # CONFIG_SECURITY is not set > # CONFIG_SECURITYFS is not set > CONFIG_DEFAULT_SECURITY_DAC=y > CONFIG_DEFAULT_SECURITY=""
Thanks for the suggestions. Only major difference on my system was CONFIG_EXT4_FS_SECURITY=y but I don't think its relevant. I tried anyway, same problem: system won't boot (with errors regarding systemd-logger and systemd-kmsg-syslogd) without commenting out those CapabilityBoundingSet lines. # CONFIG_IP_NF_SECURITY is not set CONFIG_EXT4_FS_SECURITY=y CONFIG_SECURITY=y # CONFIG_SECURITYFS is not set CONFIG_SECURITY_NETWORK=y CONFIG_SECURITY_NETWORK_XFRM=y # CONFIG_SECURITY_PATH is not set # CONFIG_SECURITY_TOMOYO is not set # CONFIG_DEFAULT_SECURITY_SELINUX is not set # CONFIG_DEFAULT_SECURITY_SMACK is not set # CONFIG_DEFAULT_SECURITY_TOMOYO is not set CONFIG_DEFAULT_SECURITY_DAC=y CONFIG_DEFAULT_SECURITY="" Any other ideas? Thanks, Daniel _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
