Oops. I'm a bit confused though. What are the scenarios that trigger an autorelabel? I've not had any luck with the -autorelabel kernel boot parameter, nor with the /.autorelabel flag file. OTOH sometimes when I reboot it (apparently) decides to autorelabel. > Ok, so all of your processes are still running in kernel_t, and all of your files are > labeled file_t. You need to label your filesystems and reboot. -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with the words "unsubscribe selinux" without quotes as the message.
