On Friday 23 October 2009 01:24:44 pm Per Nystrom wrote: > > > But I have nothing in dev except console, null, and zero so I can't > > > actually fsck root. Not that it really needs it -- when I reboot with > > > selinux=0 it comes up normally and with a clean root filesystem. > > > > > > I think your disk needs relabeling. You might need to do a > > > > touch /.autorelabel > > I did this, but I don't think it ever gets to that point in the boot > sequence. Just so everyone knows how this turned out...I worked with Per offline to see if we could come up with a solution that preserved the current boot method this project has setup. It looks like we've hit a deadend for the moment in getting SE Linux working. However, in chatting with Dan Horák, he says that he has SE Linux working by using the kernels that he's been releasing. (See his announcements on this mail list.) The difference is that it uses a ramdisk during boot and that takes care of loading policy just like the main Fedora distribution does. This boot method would also need to be used if you ever wanted to run in the FIPS-140 mode. -Steve _______________________________________________ fedora-arm mailing list fedora-arm@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-arm
