From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Shea Levy <shea@shealevy.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Revisiting EFI boot stub config file support
Date: Wed, 2 Jan 2013 17:43:19 +0000 [thread overview]
Message-ID: <20130102174319.GA2590@srcf.ucam.org> (raw)
In-Reply-To: <710F73BE-9F65-48C9-8739-BFCF097F4B07@shealevy.com>
On Wed, Jan 02, 2013 at 08:26:29AM -0500, Shea Levy wrote:
> Hm, ok. Does the boot stub have access to CONFIG_CMDLINE? Or could
> another compile-time setting be added so that distros can ship livecds
> that automatically use a config file found at a hard-coded location?
Just pass the config file as the first argument?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2013-01-02 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-01 15:55 Revisiting EFI boot stub config file support Shea Levy
2013-01-01 17:24 ` H. Peter Anvin
2013-01-02 13:26 ` Shea Levy
2013-01-02 17:43 ` Matthew Garrett [this message]
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=20130102174319.GA2590@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shea@shealevy.com \
/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