Comment 27 for bug 1892369

@gpiccoli

I've mentioned this bevore in #13

> Why the heck is a CTRL+C during integrity check not
> enough expression of my will to skip that process?

Just now I am in the same hazzle again. I've pressed E during boot, tried to apply fsck.skip=false, but via IPMI, the keyboard layout is somewhat dice-rolled. So again, the integrity check wasn't skipped and I had 40 minutes to think about restarting over or just get out of the house to have a walk with the dog. After returning, I tried to express another wish to the installer by hitting "Skip updates". Of course, the update after the setup wasn't skipped. Due to high IO (because of RAID), the update process takes another 15 minutes now and still isn't finished.

This installer is entirely unusable in manual datacenter operations. It is *that* unusable, that I think about creating my own installer ISO with customized scripts for the installation process, just for skipping integrity checks and autoupdates.

I also want to use the ISO over IPMI to enter a rescue console. Again, there must be an integrity check before I can use it. For now, I use Ubuntu 18.04 for that.

Please consider respecting the users commands given to the installer. There may be cases, where the user knows what he wants.

Thanks,
Sebastian