But that's a very short time, compared to the overall length of the
boot process. (Except when probing certain hardware with long
timeouts, but such drivers often need not be included in a production
kernel [as opposed to rescue disks with all the SCSI drivers, etc].)
I'd just propose that the many messages printed before spawning init
can be suppressed (but put in the dmesg buffer of course) by way of a
boot option. So a userland application can seize control of everything
which is printed after "Uncompressing Linux...done".
olaf
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu