unofficial mirror of guix-patches@gnu.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 14:46:18 +0200	[thread overview]
Message-ID: <20200430124618.r4yck2mmenup6p5n@pelzflorian.localdomain> (raw)
In-Reply-To: <20200416150436.3274-1-m.othacehe@gmail.com>

On Thu, Apr 16, 2020 at 05:04:36PM +0200, Mathieu Othacehe wrote:
> Hello,
> 
> 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.

I have no idea why I only ever got the [Patch 0/2] e-mail delivered to
my inbox.  I look at <https://issues.guix.info/issue/40662#1> now.


> [PATCH 2/2] file-system: Add efivarfs support.
> […]
> Tools such as efibootmgr rely on the deprecated /sys/firmware/efi/vars API as
> well as on the new /sys/firmware/efi/efivars API. The later needs to be
> mounted.

Typo: The latter needs to be mounted.


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.

Regards,
Florian




  reply	other threads:[~2020-04-30 12:47 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) [this message]
2020-04-30 15:41   ` pelzflorian (Florian Pelz)
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

  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=20200430124618.r4yck2mmenup6p5n@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 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).