From: Felix Lechner via <help-guix@gnu.org>
To: Roman Riabenko <roman@riabenko.com>
Cc: Roman Riabenko via <help-guix@gnu.org>,
Christophe Pisteur <christophe.pisteur@fsfe.org>,
Leo Famulari <leo@famulari.name>, Wilko Meyer <w@wmeyer.eu>
Subject: Re: Could not prepare Boot variable
Date: Thu, 09 Jan 2025 13:45:03 -0800 [thread overview]
Message-ID: <87zfjzbr1c.fsf@lease-up.com> (raw)
In-Reply-To: <20250109223541.37c294e1ca563edc4e4d239b@riabenko.com> (Roman Riabenko's message of "Thu, 9 Jan 2025 22:35:41 +0200")
Hi Roman,
On Thu, Jan 09 2025, Roman Riabenko wrote:
> some distributions turn this backend off by default to prevent users
> from getting into a trap. However, they seem to turn it off when
> packaging the software, not via a kernel argument.
It's in the kernel's configuration, i.e. the first hit here. [1]
I looped in Leo and Wilko. (EFI dump files exhaust space on the ESP.)
Kind regards
Felix
[1] https://codesearch.debian.net/search?q=pstore_disable&literal=1
prev parent reply other threads:[~2025-01-09 21:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 19:01 Could not prepare Boot variable Christophe Pisteur
2025-01-09 19:19 ` Felix Lechner via
2025-01-09 19:33 ` Christophe Pisteur
2025-01-09 19:38 ` Felix Lechner via
2025-01-09 20:04 ` Christophe Pisteur
2025-01-09 20:05 ` Roman Riabenko via
2025-01-09 20:15 ` Christophe Pisteur
2025-01-09 20:24 ` Roman Riabenko via
2025-01-09 20:42 ` Christophe Pisteur
2025-01-09 20:49 ` Roman Riabenko via
2025-01-09 21:10 ` Christophe Pisteur
2025-01-09 21:34 ` Roman Riabenko via
2025-01-09 22:04 ` Christophe Pisteur
2025-01-09 22:34 ` Roman Riabenko via
2025-01-09 20:16 ` Felix Lechner via
2025-01-09 20:35 ` Roman Riabenko via
2025-01-09 21:45 ` Felix Lechner via [this message]
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=87zfjzbr1c.fsf@lease-up.com \
--to=help-guix@gnu.org \
--cc=christophe.pisteur@fsfe.org \
--cc=felix.lechner@lease-up.com \
--cc=leo@famulari.name \
--cc=roman@riabenko.com \
--cc=w@wmeyer.eu \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.