| |||||||||||||
LPC: Booting and systemdLPC: Booting and systemdPosted Sep 18, 2011 21:39 UTC (Sun) by mjg59 (subscriber, #23239)In reply to: LPC: Booting and systemd by raven667 Parent article: LPC: Booting and systemd
There's no problem in configuring EFI to boot a kernel. The problem is in the UI that the firmware will expose to let you choose which kernel to boot or which boot arguments to pass. That's entirely non-standard, requires different keypresses on different hardware, looks different depending on a variety of circumstances and may not actually exist in any UI.
(Log in to post comments)
LPC: Booting and systemd Posted Sep 19, 2011 3:44 UTC (Mon) by raven667 (subscriber, #5198) [Link]
As long as it has the information and _can_ load a kernel with options and _can_ present a UI I don't think the actual UI needs to be standard. I would expect it to be branded by the hardware vendor for example. As long as there is a standard place to put kernel images and a standard way to add/remove labeled boot entries and if you can manually boot custom options using the EFI shell then I think that would solve the problem. I don't think the actual UI needs to be standardized beyond that.
|
|||||||||||||