In that case you can't use the autoconfigurator anyway. You're going
to have to make sure by hand that the controller, bus type, and file
system code for your root device are hard-compiled in. (This is at
least no worse off than you were under CML1.)
Rob Landley pointed out correctly that the vitality flag was not
actually solving this problem, and it was an ugly wart on the
language. Instead, there's a symbol property "BOOTABLE" in the new
rulebase that is attached to IDE and SCSI hardware symbols that are
controllers for what could be boot devices.
One of the remaining limitations of the autoconfigurator is that it
only knows how to detect IDE and SCSI boot devices. I want to be able
to make it nail NFS and USB storage being used as root, but it's not
there yet.
-- <a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>The American Republic will endure, until politicians realize they can bribe the people with their own money. -- Alexis de Tocqueville - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/