From: "Mike Gilbert" <floppym@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] data/gentoo-news:master commit in: 2024-02-01-grub-upgrades/
Date: Tue, 6 Feb 2024 19:27:12 +0000 (UTC) [thread overview]
Message-ID: <1707247589.e0e93c981baef4a697dac91e8a9efed0a4a204b5.floppym@gentoo> (raw)
commit: e0e93c981baef4a697dac91e8a9efed0a4a204b5
Author: Mike Gilbert <floppym <AT> gentoo <DOT> org>
AuthorDate: Tue Feb 6 19:26:29 2024 +0000
Commit: Mike Gilbert <floppym <AT> gentoo <DOT> org>
CommitDate: Tue Feb 6 19:26:29 2024 +0000
URL: https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=e0e93c98
2024-02-01-grub-upgrades: x86_64-pc -> x86_64-efi
Signed-off-by: Mike Gilbert <floppym <AT> gentoo.org>
2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt b/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt
index f7aaa72..ddcc224 100644
--- a/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt
+++ b/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt
@@ -1,7 +1,7 @@
Title: GRUB upgrades
Author: Mike Gilbert <floppym@gentoo.org>
Posted: 2024-02-01
-Revision: 1
+Revision: 2
News-Item-Format: 2.0
Display-If-Installed: sys-boot/grub
@@ -24,7 +24,7 @@ a stale core image to exist. For example:
/boot/efi/EFI/BOOT/BOOTX64.EFI (grub 2.06 core image)
/boot/efi/EFI/gentoo/grubx64.efi (grub 2.12 core image)
-/boot/grub/x86_64-pc/*.mod (grub 2.12 modules)
+/boot/grub/x86_64-efi/*.mod (grub 2.12 modules)
Booting this system using BOOTX64.EFI image would likely fail due to a
symbol mismatch between the core image and modules. [1]
next reply other threads:[~2024-02-06 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 19:27 Mike Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-06 19:30 [gentoo-commits] data/gentoo-news:master commit in: 2024-02-01-grub-upgrades/ Mike Gilbert
2024-02-06 0:03 Mike Gilbert
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=1707247589.e0e93c981baef4a697dac91e8a9efed0a4a204b5.floppym@gentoo \
--to=floppym@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox