On Thu, May 24, 2007 at 10:00:51AM -0500, Jason L Tibbitts III wrote:
>>>>> "BW" == Bruno Wolff
<bruno(a)wolff.to> writes:
BW> Because if the OS is borked, you might not be able to interrupt
BW> that next process.
So the first thing it should do is up the timeout and then set it back
after the boot process is done.
Which makes a crash in the kernel, an incorrect root= or an initrd
problem which makes disks impossible to mount unfixable, while
choosing a different kernel and/or changing root= could be enough to
go to the fixing stage.
It's not as if issues like this haven't been solved
elsewhere.
Where and how?
OG.