all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tomas Volf <~@wolfsden.cz>
To: Tadhg McDonald-Jensen <tadhgmister@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 70826@debbugs.gnu.org
Subject: bug#70826: luks-device-mapping-with-options breaks bootloader
Date: Tue, 23 Jul 2024 20:19:49 +0200	[thread overview]
Message-ID: <Zp_0RcfVu1bbXDoH@ws> (raw)
In-Reply-To: <ecfd1524-9d20-491c-b2be-8b7122c28d71@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 862 bytes --]

On 2024-05-25 10:30:49 -0400, Tadhg McDonald-Jensen wrote:
> That unfortunately doesn't fix the problem,
> `luks-device-mapping-with-options` is a routine that returns the
> `mapped-device-kind` so it won't check by equality.
>
> A possible solution is to check whether the `mapped-device-kind-close`
> routines are the same as these are shared.

What I find interesting is that I too am using luks-device-mapping-with-options
and my system boots just fine.  So I wonder what the difference is.  Could you
share your system configuration please?  Or at least the relevant parts (I
assume at least bootloader, file-systems and mapped-devices fields)?

I would like to properly understand the problem here and why it works for me.

Thanks,
Tomas Volf

--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-07-23 18:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-07 18:54 bug#70826: luks-device-mapping-with-options breaks bootloader Tadhg McDonald-Jensen
2024-05-25  9:47 ` Ludovic Courtès
2024-05-25 14:30   ` Tadhg McDonald-Jensen
2024-07-23 18:19     ` Tomas Volf [this message]
2024-08-11 22:33       ` Tadhg McDonald-Jensen
2024-08-11 23:19         ` Tadhg McDonald-Jensen

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=Zp_0RcfVu1bbXDoH@ws \
    --to=~@wolfsden.cz \
    --cc=70826@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=tadhgmister@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.