From: Robbie Harwood <rharwood@redhat.com>
To: Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>,
The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH v2 1/1] Add support for grub-emu to kexec Linux menu entries
Date: Thu, 11 Aug 2022 14:02:53 -0400 [thread overview]
Message-ID: <jlgr11mk69e.fsf@redhat.com> (raw)
In-Reply-To: <CAEaD8JNOnW20W1LYCES2b5TVyfPynfzY2fu2gbdX-_YBxerrDg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
"Vladimir 'phcoder' Serbinenko" <phcoder@gmail.com> writes:
> I like it in general however I had a comment: in future GRUB could be able
> to do the same through second approach: load a constructed kexec blob with
> all the parts. This would allow to e.g. kexec FreeBSD. This didn't have to
> be implemented now. Meanwhile can we use "kexec" as command name? It's fine
> to have aliases "linux" and co, just let's have a command line that won't
> be broken if second approach becomes a reality
I don't think I follow. In this hypothetical future, couldn't we just
rename this code to something else and avoid the problem entirely? But
maybe I'm misunderstanding.
In any case, I don't see support for aliases anywhere, so I'm not sure
what you're referring to.
Be well,
--Robbie
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2022-08-11 18:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 20:39 [PATCH v2 1/1] Add support for grub-emu to kexec Linux menu entries Robbie Harwood
2022-08-03 15:26 ` Daniel Kiper
2022-08-08 18:58 ` Robbie Harwood
2022-08-11 18:08 ` Daniel Kiper
2022-08-15 13:16 ` Raymund Will
2022-08-16 16:07 ` Robbie Harwood
2022-08-20 11:23 ` Daniel Kiper
2022-08-23 21:03 ` Robbie Harwood
2022-08-08 21:43 ` Vladimir 'phcoder' Serbinenko
2022-08-11 18:02 ` Robbie Harwood [this message]
2022-08-11 18:13 ` Daniel Kiper
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=jlgr11mk69e.fsf@redhat.com \
--to=rharwood@redhat.com \
--cc=grub-devel@gnu.org \
--cc=phcoder@gmail.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 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.