From: Christian Hesse <list@eworm.de>
To: Michael Chang via Grub-devel <grub-devel@gnu.org>
Cc: Michael Chang <mchang@suse.com>,
Tobias Powalowski <tobias.powalowski@googlemail.com>
Subject: Re: Arch Linux latest git snapshot has too many issues to be a new release base
Date: Fri, 21 Feb 2025 10:33:26 +0100 [thread overview]
Message-ID: <20250221103326.51495d45@leda.eworm.net> (raw)
In-Reply-To: <72rffodssuonk4nktl2msx6tl5n6u6aiklh2byudbe4x7d65fg@g37h4ti4bwuz>
[-- Attachment #1.1: Type: text/plain, Size: 1016 bytes --]
Michael Chang via Grub-devel <grub-devel@gnu.org> on Fri, 2025/02/21 15:55:
> > - encrypted devices is not working anymore for him
>
> I have no idea about this. Is there any error message that could help to
> understand how it failed?
Actually I can no longer reproduce. %-p
Last time I had to recover quickly and missed to copy the output. I just
decided to try again and gather information, do so with my latest build (that
includes the fs/ext2 out-of-bounds read fix).
This time it opened the encrypted disk and booted fine, just like expected -
or actually *not* as expected, but as it is supposed to.
Wondering if I missed to run `grub-mkconfig` after `grub-install`, that
*could* be. Does the new code from git master need anything new in `grub.cfg`?
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];)
putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 141 bytes --]
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
prev parent reply other threads:[~2025-02-21 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 11:27 Arch Linux latest git snapshot has too many issues to be a new release base Tobias Powalowski via Grub-devel
2025-02-21 7:33 ` Glenn Washburn
2025-02-21 9:37 ` Christian Hesse
2025-02-21 7:55 ` Michael Chang via Grub-devel
2025-02-21 9:01 ` Christian Hesse
2025-02-21 9:19 ` Michael Chang via Grub-devel
2025-02-21 9:33 ` Christian Hesse [this message]
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=20250221103326.51495d45@leda.eworm.net \
--to=list@eworm.de \
--cc=grub-devel@gnu.org \
--cc=mchang@suse.com \
--cc=tobias.powalowski@googlemail.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.
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.