On Monday, August 22, 2016 02:59:55 PM Rich Freeman wrote: > On Mon, Aug 22, 2016 at 2:34 PM, Håkon Alstadheim > > <ha...@alstadheim.priv.no> wrote: > > Booting straight into linux on an EFI system without a boot-loader means > > you have no way to provide command-line or initramfs as far as I can > > tell, all modules must be compiled in, and default command-line needs to > > be set in the kernel config. > > You can have an initramfs, but it also has to be compiled in. Just as > with the command line there is an option to include an initramfs in > the kernel. I think it actually always builds with some kind of stub > of one. This means that you can use modules. It is a pita though, > since you'd need to configure your kernel without the initramfs, build > everything, install your modules, build your initramfs, then change > your config to include the initramfs, and THEN rebuild the kernel > itself (which would be fast since most of it is already built), and > run the final make install I guess.
Why not simply follow best practices when configuring your own kernel and put all boot-necessary modules internal? > Heaven help you if you need single-user mode or whatever. Though, I > guess you could build a bunch of kernels with various command lines. > They'd use a lot of space comparatively, but wouldn't actually take > that long to build since again the makefile is reasonably efficient. > Plus I always build kernels on a tmpfs anyway. What about an init-script that checks for a specific key-press during boot and switches to single-user mode when necessary? > It generally makes sense to use a bootloader with EFI as a result. It helps :) -- Joost
