Answering question for ' Why is initrd needed for "real storage support"?' because there always be somebody: * need to have sshd at initrd stage to enter encry

Answering question for ' Why is initrd needed for "real storage support"?' because there always be somebody: * need to have sshd at initrd stage to enter encryption keys (remote boot) * need to have recovery tool on hands (going even further: imagine having working graphical browser when storage fails) * have same crazy storage setup - root on ceph/nfs volume with non trial configuration and etc... * in case of electricity fault at home - it only system which have exposed connection to internet My suggestion for booting would be following: 1) having UEFI bootloader which boot some minimal kernel (lets same sort LTS for stability’s sake ) on /boot partition 2) have ability to unlock and read from root filesystem (same as above, rootfs in nfs/ceph/encrypted ir whatever) 3) then scan kernels from /lib/modules/{version}/bzImage (i know there are modules here, but having one additional file would not hurt too much) 4a) kexec kernel with necessary parameters to start system [in this step we do not enter passwords, encryption keys twice!] 4b) or boot without kexec in recovery mode with some GUI (I want ability to have browser in recovery mode)