unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <m.othacehe@gmail.com>
To: "pelzflorian \(Florian Pelz\)" <pelzflorian@pelzflorian.de>
Cc: 40662@debbugs.gnu.org
Subject: [bug#40662] [PATCH 0/2] Add efivarfs support.
Date: Fri, 01 May 2020 11:16:34 +0200	[thread overview]
Message-ID: <875zdguia5.fsf@gmail.com> (raw)
In-Reply-To: <20200430154150.eogbhn6crje4tho6@pelzflorian.localdomain> (pelzflorian@pelzflorian.de's message of "Thu, 30 Apr 2020 17:41:50 +0200")


Hey Florian,

Thanks a lot for having a look.

> 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?

I think the full NVRAM is only one part of the issue. There could also
be errors for variables > 1024 bytes using the legacy sysfs API, see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933523.

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

Oh, it seems that elogind has support to mount efivarfs.

Mathieu




  reply	other threads:[~2020-05-01  9:17 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)
2020-05-01  9:16     ` Mathieu Othacehe [this message]
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

  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=875zdguia5.fsf@gmail.com \
    --to=m.othacehe@gmail.com \
    --cc=40662@debbugs.gnu.org \
    --cc=pelzflorian@pelzflorian.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).