All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kyle Rankin <kyle.rankin@puri.sm>
To: Daniel Kiper <daniel.kiper@oracle.com>
Cc: chris@z9.de, alexander.burmashev@oracle.com,
	pmenzel@molgen.mpg.de, phcoder@gmail.com, grub-devel@gnu.org
Subject: Re: [PATCH] templates: Add GRUB_CMDLINE_LINUX_RECOVERY
Date: Wed, 15 Sep 2021 08:35:36 -0700	[thread overview]
Message-ID: <20210915153536.GK965@disp7009> (raw)
In-Reply-To: <20210915151210.lneu6b4tf6s3vsxv@tomti.i.net-space.pl>

[-- Attachment #1: Type: text/plain, Size: 1703 bytes --]

On Wed, Sep 15, 2021 at 05:12:10PM +0200, Daniel Kiper wrote:
> On Wed, Sep 15, 2021 at 03:18:40PM +0200, Paul Menzel wrote:
> > [Cc: +Kyle]
> >
> > Am 14.09.21 um 21:25 schrieb chris@z9.de:
> > > From: Chris Vogel <chris@z9.de>
> > >
> > > When generating grub.cfg using grub-mkconfig and the scripts 10_linux and
> > > 20_linux_xen there is no way to add kernel command line parameters _only_ to
> > > the recovery entries generated.
> > >
> > > This is needed to e.g. start a debug shell in installations using systemd
> > > using the kernel command line parameter "systemd.debug-shell" or to recover
> > > in a system with encrypted root in situations where the decryption of the
> > > root filesystem per crypttab in the intiramfs image is broken and the recovery
> > > entry should contain informations about how to decrypt the rootfs (cryptopts=).
> > >
> > > This patch does not change the default behaviour of grub if
> > > GRUB_CMDLINE_LINUX_RECOVERY is not set.
> > >
> > > If GRUB_CMDLINE_LINUX_RECOVERY is set and the generated recovery entry should
> > > include the kernel parameter 'single' the parameter must be explicitly included
> > > in GRUB_CMDLINE_LINUX_RECOVERY.
> > >
> > > As far as I know all credits for the idea and the initial implementation go to
> > > Kyle Ranking of Purism.
> > >
> 
> "Signed-off-by: Kyle Rankin <kyle.rankin@puri.sm>" is missing here.
> I can add it before committing the patch if Kyle does not object of
> course... :-)
> 

Signed-off-by: Kyle Rankin <kyle.rankin@puri.sm>

-Kyle

> > > Signed-off-by: Chris Vogel <chris@z9.de>
> 
> Otherwise: Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com>
> 
> Daniel

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-09-15 17:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14 19:25 [PATCH] templates: Add GRUB_CMDLINE_LINUX_RECOVERY chris
2021-09-15 13:18 ` Paul Menzel
2021-09-15 15:12   ` Daniel Kiper
2021-09-15 15:35     ` Kyle Rankin [this message]
2021-09-15 15:42 chris

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=20210915153536.GK965@disp7009 \
    --to=kyle.rankin@puri.sm \
    --cc=alexander.burmashev@oracle.com \
    --cc=chris@z9.de \
    --cc=daniel.kiper@oracle.com \
    --cc=grub-devel@gnu.org \
    --cc=phcoder@gmail.com \
    --cc=pmenzel@molgen.mpg.de \
    /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.