From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Fabio Natali <me@fabionatali.com>
Cc: Oleg Pykhalov <go.wigust@gmail.com>,
Felix Lechner <felix.lechner@lease-up.com>,
guix-devel@gnu.org
Subject: Re: LUKS2 support in Guix
Date: Sat, 02 Mar 2024 22:08:16 -0500 [thread overview]
Message-ID: <87wmqkhv1b.fsf@gmail.com> (raw)
In-Reply-To: <878r30iyzx.fsf@fabionatali.com> (Fabio Natali's message of "Sat, 02 Mar 2024 12:45:06 +0000")
Hello,
Fabio Natali <me@fabionatali.com> writes:
> On 2024-03-02, 10:41 +0300, Oleg Pykhalov <go.wigust@gmail.com> wrote:
>> I also lost some time due to this incorrect statement.
>
> Brilliant, thanks Felix and Oleg.
>
> FWIW, micro-patch submitted here⁰.
>
> Let's see what the patch reviewer thinks. I'm not terribly happy about
> "downgrading" the manual's recommendation from LUKS2 to LUKS1, but if
> LUKS2 is really not supported, then of course that needs to be reflected
> in the docs.
>
> Best wishes, Fabio.
>
>
> ⁰ Ticket 69507 on debbugs.gnu.org. I wanted to link to the relevant page
> on https://lists.gnu.org/archive/html/guix-patches/2024-03/index.html
> but it seem it's taking a while for the mail to pass moderation.
Is there something preventing us from updating GRUB to benefit from full
LUKS2 support?
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-03-03 3:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 9:08 LUKS2 support in Guix Fabio Natali
2024-03-01 13:25 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-03-02 7:41 ` Oleg Pykhalov
2024-03-02 12:45 ` Fabio Natali
2024-03-02 21:23 ` Josselin Poiret
2024-03-03 8:58 ` Fabio Natali
2024-03-03 16:42 ` [PATCH 1/2] gnu: grub: Update to 2.12 Josselin Poiret
2024-03-03 16:42 ` [PATCH 2/2] gnu: grub: Modernize Josselin Poiret
2024-03-05 9:53 ` Fabio Natali
2024-03-09 9:42 ` Josselin Poiret
2024-03-11 14:47 ` Fabio Natali
2024-03-03 3:08 ` Maxim Cournoyer [this message]
2024-03-03 9:03 ` LUKS2 support in Guix Fabio Natali
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=87wmqkhv1b.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=felix.lechner@lease-up.com \
--cc=go.wigust@gmail.com \
--cc=guix-devel@gnu.org \
--cc=me@fabionatali.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).