Hi Adam, On Sun, 18 Mar 2018 12:32:18 -0400 Adam Van Ymeren <[email protected]> wrote:
> Fundamentally I think the problem is that check-device-initrd-modules is > checking modules for the currently running kernel which is not > necessarily the kernel that I will be installing. Yeah, otherwise it would have to build everything first. > At the very least however it would be nice if I could override this > check with a --i-know-what-im-doing flag of some sort. It exists: --skip-checks > It seems odd that check-device-initrd-modules will not prevent your > installation from continuing if it can't find modules.alias, but if it > can find it and you didn't specify the initrd-modules it thinks you need > then it becomes a hard error that you can't override. > Perhaps it should > always be a warning or prompt the user if they want to continue. Yeah, I'd prefer a warning and sleep 5 since the result is not guaranteed to be correct. Also it would be possible to build a Frankenstein's monster version where it checks the new kernel config and finds out which modules would be builtin (that would involve a lot of Makefile and Kconfig parsing... ugh). An additional more complete check (with the new kernel etc) at the end would make sense.
pgpQObd2niK2r.pgp
Description: OpenPGP digital signature
