From: Roman Riabenko via <help-guix@gnu.org>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: Roman Riabenko via <help-guix@gnu.org>,
Christophe Pisteur <christophe.pisteur@fsfe.org>
Subject: Re: Could not prepare Boot variable
Date: Thu, 9 Jan 2025 22:35:41 +0200 [thread overview]
Message-ID: <20250109223541.37c294e1ca563edc4e4d239b@riabenko.com> (raw)
In-Reply-To: <87bjwfd9p0.fsf@lease-up.com>
On Thu, 09 Jan 2025 12:16:43 -0800
Felix Lechner <felix.lechner@lease-up.com> wrote:
> On Thu, Jan 09 2025, Roman Riabenko via wrote:
>
> > To prevent dump files from filling up space, I disabled the pstore
> > backend
>
> I think I want that, too. Did you submit a patch?
While researching my issue, I noticed that 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.
I do not know who should take care of that. Maybe some upstream
developers should have it turned off by default?
I do not know, but I assume that the real culprit is the faulty models
of UEFI. Maybe UEFI should clear itself up for new boot variables
instead of refusing to do so.
Unfortunately, I am not knowledgeable enough to answer these questions
and propose a correct solution in a patch.
Roman
next prev parent reply other threads:[~2025-01-09 20:36 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 [this message]
2025-01-09 21:45 ` Felix Lechner via
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250109223541.37c294e1ca563edc4e4d239b@riabenko.com \
--to=help-guix@gnu.org \
--cc=christophe.pisteur@fsfe.org \
--cc=felix.lechner@lease-up.com \
--cc=roman@riabenko.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).