All of lore.kernel.org
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: Colin Watson <cjwatson@debian.org>,
	Glenn Washburn <development@efficientek.com>,
	mchang@suse.com, Marco A Benatto <mbenatto@redhat.com>,
	Javier Martinez Canillas <javierm@redhat.com>
Subject: Re: [PATCH v2] i386-pc: build verifiers API as module
Date: Tue, 23 Mar 2021 13:45:35 -0400	[thread overview]
Message-ID: <20210323174534.vpgek445wb5wiidf@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20210323163312.xmhzcsxfqovgm27y@tomti.i.net-space.pl>

On Tue, Mar 23, 2021 at 05:33:12PM +0100, Daniel Kiper wrote:
> How long are you going to support such systems? 1, 5 or 10 years? This
> approach makes GRUB upstream as a hostage of small MBR gaps users.
> Anyway, I think we have to make users aware that small MBR gaps are not
> supported any longer. Otherwise we will be playing whack-a-mole game
> which we will loose sooner or later.

I was surprised to find a 63 sector gap on one of my systems recently
when upgrading the root disk to a larger drive (by cloning the old disk
and then resizing with gparted).  I decided being that this was an SSD
it was in my interest to change it to 1MB alignment while doing the
resizing anyhow.  I guess this install has been around for a while from
before Debian changed to using 1MB alignment by default.  So some such
systems apparently are still around.

Perhaps you need to actually have grub generate a warning when installed
in a 63 sector gap for a while (where a while preferaby is more than one
release cycle for common distributions, so hence more than 2 or 3 years)
so that people get told there will be a problem with upgrades at some
point and they should look into fixing their partitioning now.

Ideally to make people know about it, put the warning on the boot screen,
not just when doing grub install.  Make people aware so they can start
to look into what they need to do to change their system.  Finding out
after they can't boot is too late.

-- 
Len Sorensen


  reply	other threads:[~2021-03-23 17:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 11:30 [PATCH v2] i386-pc: build verifiers API as module 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 [this message]
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
2021-08-22 19:50 Michael Schierl
2021-08-22 20:23 ` Didier Spaier

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=20210323174534.vpgek445wb5wiidf@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=cjwatson@debian.org \
    --cc=development@efficientek.com \
    --cc=grub-devel@gnu.org \
    --cc=javierm@redhat.com \
    --cc=mbenatto@redhat.com \
    --cc=mchang@suse.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.