On Sat, 22 Apr 2006 13:45:35 +0100 (BST) Robert Watson <[EMAIL PROTECTED]> wrote:
> > On Sat, 22 Apr 2006, Tom Rhodes wrote: > > > Which is why I suggested that, similar to Linux, we make everything an > > option instead of either Warning before you build/install the new kernel or > > add the addition headache of turning it on later. Thus, I'm still of the > > opinion that one does not blindly add a newfs option during the install > > without understanding what's going on. > > The problem you're diagnosing is booting a kernel that doesn't support > features requested by the administrator. When this happens, there are really > only two things you can do: > > (1) Generate warnings and continue. > (2) Generate warnings and stop. > > We opt for (1) because it makes recovery easier. Deleting the warnings helps > neither case. Booting an SELinux system without an SELinux kernel will fail > in many spectacular ways, but I'm not sure if they generate a warning > equivilent to the one you deleted. > > BTW, turning on the multilabel flag in sysinstall is not an option offered by > the installer -- by setting it using sysinstall's "additional flags" field, > you're specifially doing something not part of the install path. The MAC Heh, exactly why I wanted to remove it. :) Someone would need a reason to do it this way, I was hoping in this case that someone would have a clue. It's reverted in any case. ;) -- Tom Rhodes _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "[EMAIL PROTECTED]"
