From: Michael Schierl <schierlm@gmx.de>
To: grub-devel@gnu.org
Cc: cjwatson@debian.org
Subject: Re: [PATCH v2] i386-pc: build verifiers API as module
Date: Sun, 22 Aug 2021 21:50:11 +0200 [thread overview]
Message-ID: <34abca76-58c4-4da6-4f93-e1e43f480e61@gmx.de> (raw)
Hello,
On Fri, 16 Apr 2021 22:23:39 +0100, Colin Watson wrote:
> I have on my to-do list an item to add something to the Debian release
> notes about this, since that's a way to reach less-engaged users who
> won't read the GRUB manual or mailing lists. That will likely help to
> some extent, although I can't say how much.
Did anything like this happen for the Debian Bullseye release? I found
many interesting things in the release notes, but nothing about GRUB.
Also, updating some existing systems created emails about breaking
changes in some packages to the root user (I believe it is
apt-listchanges which is doing this) but nothing about GRUB either.
(Those systems either used a large MBR gap or a simple setup with only
ext4 and no LVM etc).
I also "just for fun" took the official Debian Installer ISO
(debian-11.0.0-i386-netinst.iso) and used it to install Debian Bullseye
into a new volume on an aleady existing LVM volume group (that is on a
part_msdos style partition that still uses a small MBR gap). The
installer did not complain, and proceeded to the point where it wanted
to install GRUB, but then stopped with a fatal error while executing
"grub install /dev/sda". Did not even show me the real error message.
Seems that core.img was 33 KB large and could therefore not be embedded
into the small MBR gap. To be honest, I am not sure whether this was
still possible with the GRUB version included in Buster.
Regards,
Michael
next reply other threads:[~2021-08-22 19:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 19:50 Michael Schierl [this message]
2021-08-22 20:23 ` [PATCH v2] i386-pc: build verifiers API as module Didier Spaier
-- strict thread matches above, loose matches on Subject: below --
2021-03-18 11:30 Michael Chang
2021-03-22 15:20 ` Daniel Kiper
2021-03-22 16:16 ` Colin Watson
2021-03-22 20:09 ` Colin Watson
2021-03-22 20:19 ` Glenn Washburn
2021-03-22 20:45 ` Colin Watson
2021-03-23 16:33 ` Daniel Kiper
2021-03-23 17:45 ` Lennart Sorensen
2021-03-24 4:44 ` Michael Chang
2021-03-26 17:01 ` Daniel Kiper
2021-04-12 13:15 ` Daniel Kiper
2021-04-13 4:13 ` Michael Chang
2021-04-14 13:22 ` Daniel Kiper
2021-04-16 21:23 ` Colin Watson
2021-04-20 3:49 ` Michael Chang
2021-04-28 13:45 ` Daniel Kiper
2021-03-22 21:43 ` James Bottomley
2021-03-23 4:16 ` Michael Chang
2021-03-23 11:37 ` Javier Martinez Canillas
2021-03-23 13:27 ` Colin Watson
2021-03-23 14:26 ` Javier Martinez Canillas
2021-03-23 17:26 ` Daniel Kiper
2021-03-23 16:48 ` Daniel Kiper
2021-03-24 3:50 ` Michael Chang
2021-03-26 17:22 ` Daniel Kiper
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=34abca76-58c4-4da6-4f93-e1e43f480e61@gmx.de \
--to=schierlm@gmx.de \
--cc=cjwatson@debian.org \
--cc=grub-devel@gnu.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 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.