pwatk wrote:I suppose it doesn't matter but since your going to need an initrd anyway, you might as well use the generic kernel! On the other hand, the only real difference (apart from size) is seeing errors generated by instmod trying to install built-in modules.
But it should work with kernel-huge, right? One can install kernel-huge and then, after the installation is done, can replace it with kernel-generic or whatever.
pwatk wrote:You don't even need cryptsetup and mdadm if you just temporarily copy over the static versions from the installation ramdisk before running mkinitrd.
So cryptsetup and mdadm are not needed on the installed system, they should just be available during installation, which they already are?
pwatk wrote:Other things to consider are usb keyboards (ehci-hcd, uhci-hcd, ohci-hcd, usbhid),
But these aren't issues at all, if kernel-huge is used, right?
pwatk wrote:hibernation and the possibility someone will add in a new device (e.g. a sata cd/dvd-rom). I just did this and in throws everything out. Using UUID's would solve this but I don't know how to implement this (on the "to do when time stands still" list).
Are we still talking about the installation here? What does the installation have to do with any changes you might do after it's done?
It seems to me that the only thing that is really needed is for the installation to not automatically reboot, but offer an option to reboot or exit to command line.