From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752376Ab3AAPzu (ORCPT ); Tue, 1 Jan 2013 10:55:50 -0500 Received: from caibbdcaaaaf.dreamhost.com ([208.113.200.5]:39197 "EHLO homiemail-a47.g.dreamhost.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752305Ab3AAPzr (ORCPT ); Tue, 1 Jan 2013 10:55:47 -0500 Message-ID: <50E306FB.6080607@shealevy.com> Date: Tue, 01 Jan 2013 10:55:39 -0500 From: Shea Levy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: linux-efi@vger.kernel.org CC: Linux Kernel Mailing List Subject: Revisiting EFI boot stub config file support Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi all, In March last year, I submitted a patch to enable the EFI boot stub to read its config arguments from a file on the ESP, both to help with booting from livecds and to avoid having to use efibootmgr every time you change your boottime arguments. I ended up dropping the submission because I ended up coming to the conclusion that tools like rEFInd and gummiboot were better suited to the task of boot managing than the kernel itself. Since then, however, I've received enough emails asking about the status of the patch that I think there is room for a simpler entrant into the field of linux EFI boot management. This could be in-kernel, as per my original patch, or a very simple out-of-kernel (but maybe distributed in-tree?) efi image that simply reads linux.conf and boots linux with those parameters. My personal bias is still toward handling this functionality outside of the kernel itself, but before I started the work I thought I'd ask here if anyone thought I should instead bring my old patch up-to-date. Thoughts? Thanks, Shea Levy P.S. I am subscribed to linux-efi but not lkml, please include me in any replies to lkml.