* maximilian attems <[EMAIL PROTECTED]> [20070315 01:15]: > On Thu, Mar 15, 2007 at 12:17:33AM +0100, Michael Prokop wrote: > > * David Härdeman <[EMAIL PROTECTED]> [20070314 20:58]:
[...] > > It would be fine to provide some output while running the "sleep > > $ROOTDELAY" so users without usplash_write are notified about this > > issue as well. > well that is nice to have, > but not a killer feature we just do what the user asked aka sleep. Sure, but inform the user that it's sleeping *now* for $ROOTDELAY seconds. That's a simple "echo Delaying booting as requested via bootoption rootdelay for $ROOTDELAY seconds now" or something like that. Doesn't hurt anyone but informs the user what's going on *now*. > > If mounting the rootdevice *fails* there should be some basic > > documentation available on the screen how to fix this issue. The > > rootdelay stuff should be mentioned as well as using features like > > root=UUID=$UUID_OF_DEVICE (which works fine as well). > you are overshooting here, > that is support request on some irc or mailing list. > also d-i will soon install by uuid by default. > we provide already a help message when someone gets dropped to > shell and the message gets improved for 0.87. > also we can't put too much text there otherwise the interesting > error info scrolls off, yes nobody uses serial anymore.. I'm aware of that. But "the message gets improved for 0.87" is exactly what I requested. ;-) I don't expect to find tons of information in the booting sequence, but *if* it fails just give the appropriate hints how to start debugging and solving the problem in one or two short sentences. A system that does not boot because the rootdevice can't be mounted is definitely a serious problem for the user. regards, -mika-
pgpEad03t26Go.pgp
Description: PGP signature
