all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: 40662@debbugs.gnu.org
Subject: [bug#40662] [PATCH 0/2] Add efivarfs support.
Date: Thu, 30 Apr 2020 17:41:50 +0200	[thread overview]
Message-ID: <20200430154150.eogbhn6crje4tho6@pelzflorian.localdomain> (raw)
In-Reply-To: <20200430124618.r4yck2mmenup6p5n@pelzflorian.localdomain>

On Thu, Apr 30, 2020 at 02:46:18PM +0200, pelzflorian (Florian Pelz) wrote:
> On Thu, Apr 16, 2020 at 05:04:36PM +0200, Mathieu Othacehe wrote:
> > Here's a small serie to add support for efivarfs and fix the issue reported
> > here: https://lists.gnu.org/archive/html/bug-guix/2020-04/msg00274.html.
> Well I had no issues with efivars on install without your patch.  I
> will try to provoke the error by adding more efivars.  I did not yet
> manage to create a new efivar via dd or via the efivar program though.

Actually I see no reason to test after provoking Keyhenge’s error.
How does your patch fix a full NVRAM?  I thought Keyhenge resolved
their error by deleting “files” from the full NVRAM.  Do I
misunderstand Keyhenge’s issue?

But /sys/firmware/efi/efivars probably should be mounted anyway.

Do you know why

efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)

is mounted even without your patch once I add %desktop-services to my
config.scm?

Regards,
Florian




  reply	other threads:[~2020-04-30 15:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16 15:04 [bug#40662] [PATCH 0/2] Add efivarfs support Mathieu Othacehe
2020-04-30 12:46 ` pelzflorian (Florian Pelz)
2020-04-30 15:41   ` pelzflorian (Florian Pelz) [this message]
2020-05-01  9:16     ` Mathieu Othacehe
2020-04-30 16:06 ` pelzflorian (Florian Pelz)
2020-05-01  9:39   ` Mathieu Othacehe
2020-07-31 12:19     ` bug#40662: " Mathieu Othacehe

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=20200430154150.eogbhn6crje4tho6@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=40662@debbugs.gnu.org \
    --cc=m.othacehe@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.
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.