On 17 December 2014 at 19:13, Laszlo Ersek <[email protected]> wrote: > Lack of -initrd results in a zero-sized initrd file in the synthetic > filesystem, and a kernel command line parameter that references that > zero sized file ("initrd=initrd"), so the firmware code itself does not > break. > > Second, AFAICT there's basically no modern Linux system that is possible > to boot without an appropriate initrd *at all*. But, if you insist, I > can add a small check that avoids appending the "initrd=initrd" kernel > command line option if the initrd size is zero.
You definitely should support "no initrd", it works fine for the non-UEFI QEMU booting case. It's perfectly possible to have a kernel with all the support it needs built into it for booting the root filesystem directly without messing with an initrd. I find it a useful config for simplicity when doing development. thanks -- PMM ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
