Comment # 5 on bug 1213222 from Alexander Kruppa

(In reply to Stefan Hundhammer from comment #1)
> > My enhancement suggestion is: 
> > 
> > 1. If dracut fails during installation, state clearly that this leaves the
> > system in an unbootable state. This would help users who are not familiar
> > with the Linux boot process to understand what the problem is.
> 
> I have serious doubts that this would help any user in any way. Something
> that few users know what it is in the first place failed, so the resulting
> system won't be able to boot.

It took me a while to realize that dracut failing was the reason for why the
system wouldn't boot and I dearly wished that someone (i.e., yast) had told me
of this. Once I knew what the problem was, fixing it in a rescue system was
relatively straight-forward.


> > 2. If dracut fails because of missing modules during installation, allow the
> > user to edit the INITRD_MODULES setting and trying dracut again.
> 
> That is clearly a totally overengineered approach that only a miniscule
> number of users will be able to benefit from. It might rival only the Dracut
> emergency shell in terms of usability: When that thing appears, I'll simply
> reinstall. It's not humanly usable IMHO.

This is fine. I thought it would be convenient to have, but maybe it's too rare
a problem to have recovery built into yast.