From: Shea Levy <shea@shealevy.com>
To: linux-efi@vger.kernel.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Revisiting EFI boot stub config file support
Date: Tue, 01 Jan 2013 10:55:39 -0500 [thread overview]
Message-ID: <50E306FB.6080607@shealevy.com> (raw)
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.
next reply other threads:[~2013-01-01 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-01 15:55 Shea Levy [this message]
2013-01-01 17:24 ` Revisiting EFI boot stub config file support H. Peter Anvin
2013-01-02 13:26 ` Shea Levy
2013-01-02 17:43 ` Matthew Garrett
2013-01-02 17:52 ` Shea Levy
2013-01-02 17:54 ` Matthew Garrett
2013-01-02 17:52 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50E306FB.6080607@shealevy.com \
--to=shea@shealevy.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox