From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Doug Goldstein <cardoe@cardoe.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel@lists.xen.org, Keir Fraser <keir@xen.org>,
Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>
Subject: Re: [PATCH] build: save generated config in /boot
Date: Wed, 6 Jan 2016 10:31:17 +0000 [thread overview]
Message-ID: <1452076277.7292.17.camel@citrix.com> (raw)
In-Reply-To: <568CEAFB02000078000C3D0F@prv-mh.provo.novell.com>
On Wed, 2016-01-06 at 02:22 -0700, Jan Beulich wrote:
> > > > On 05.01.16 at 17:53, <cardoe@cardoe.com> wrote:
> > On 12/22/15 10:09 AM, Jan Beulich wrote:
> > > > > > On 22.12.15 at 17:02, <cardoe@cardoe.com> wrote:
> > > > How does it not make sense in this case? That's what Andrew and I
> > > > are
> > > > asking you to explain.
> > >
> > > But I already explained it: The file isn't needed for booting.
> >
> > One use of it in /boot would be to check the file in 20_linux_xen like
> > we check the kernel config for different options to add different
> > parameters.
>
> Which, if you search for it, is a very controversial thing: I agree
> with the side demanding for grub to not inspect the kernel's
> .config.
What is the preferred mechanism for determining from the contents of /boot
whether an XSM entry should be produced or not?
Ian.
next prev parent reply other threads:[~2016-01-06 10:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 21:35 [PATCH] build: save generated config in /boot Doug Goldstein
2015-12-21 12:11 ` Jan Beulich
2015-12-21 12:40 ` Andrew Cooper
2015-12-21 12:53 ` Jan Beulich
2015-12-22 12:45 ` Doug Goldstein
2015-12-22 12:50 ` Jan Beulich
2015-12-21 14:35 ` Doug Goldstein
2015-12-21 14:51 ` Jan Beulich
2015-12-21 15:20 ` Doug Goldstein
2015-12-21 15:35 ` Jan Beulich
2015-12-22 12:45 ` Doug Goldstein
2015-12-22 12:52 ` Jan Beulich
2015-12-22 14:46 ` Andrew Cooper
2015-12-22 15:59 ` Jan Beulich
2015-12-22 16:02 ` Doug Goldstein
2015-12-22 16:09 ` Jan Beulich
2016-01-05 16:53 ` Doug Goldstein
2016-01-06 9:22 ` Jan Beulich
2016-01-06 10:31 ` Ian Campbell [this message]
2016-01-06 10:38 ` Jan Beulich
2016-01-06 11:58 ` Ian Jackson
2016-01-06 12:56 ` Jan Beulich
2016-01-06 12:17 ` Wei Liu
2016-01-06 13:01 ` Jan Beulich
2016-01-04 11:27 ` Ian Campbell
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=1452076277.7292.17.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=ian.jackson@eu.citrix.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.