Comment # 1 on bug 1213222 from Stefan Hundhammer

> 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.

And then what? What is a user supposed to do? This isn't anything that even
advanced users will be able to fix. They might try the installation again, and
very likely they will get the same result.

We are trying our best not to get the user into that situation in the first
place. If that fails, very few users can do anything about it.

And the information from such an improved message is the same as you get when
the system can't boot: You'll realize that it doesn't boot. Not that you can
realistically do anything about it, though. In particular not the kind of users
that you mean to target with this: Those who are not familiar with the Linux
boot process, as you write. What are they supposed to do in that situation?


> 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.