The big problem is making sure they then see the error, and the previous
progress information. On a solid hang they might not get it
> more for feedback that the boot is proceeding ok. The fact the boot
> sequence isn't even interactive should also be a big hint that it isn't
> really necessary (except for kernel and driver developers).
You are thinking the small picture not the big one. If you are going to
graphical in init then you want to make full use of the graphical
environment to clearly show things like parallel fsck behaviour, what
servers are starting up (with pretty icons) and to do interactive things
like starting a rescue shell, going single user, pausing the boot,
changing run level, interactive boot.
Alan
-
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/