From: Steve McIntyre <93sam@debian.org>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] Make grub-install check for errors from efibootmgr
Date: Thu, 9 Feb 2017 20:37:11 +0000 [thread overview]
Message-ID: <20170209203705.GY12912@einval.com> (raw)
In-Reply-To: <86064712-98a6-0d06-4c53-b7889c3c3d26@gmail.com>
On Thu, Feb 09, 2017 at 09:52:40PM +0300, Andrei Borzenkov wrote:
>30.01.2017 22:04, Steve McIntyre пишет:
>> Code is currently ignoring errors from efibootmgr, giving users
>> clearly bogus output like:
>>
>> Setting up grub-efi-amd64 (2.02~beta3-4) ...
>> Installing for x86_64-efi platform.
>> Could not delete variable: No space left on device
>> Could not prepare Boot variable: No space left on device
>> Installation finished. No error reported.
>>
>> and then potentially unbootable systems. If efibootmgr fails,
>> grub-install should know that and report it!
>
>This looks more or less cosmetic to me. First, errors are displayed to
>user so it is not that user is not aware.
Maybe, maybe not - if this occurs in the middle of a set of package
installations or upgrades on a system, text like this will get lost.
>Second, efibootmgr is more or less optional. This is convenient but
>by far not the only one possibility to use newly installed
>grub.
If you're running on a UEFI system, this is anything *but* optional.
>Third, even successful execution of efibootmgr does not mean it will
>actually boot grub - there are enough systems out there that will
>simply ditch grub entry and replace it with hard coded Windows one.
That's not an excuse for not catching errors on systems that *are*
working.
>So I'm fine with changing "no error reported" to "efibootmgr invocation
>failed; check your firmware settings" or similar, but I am not sure we
>need to abort grub-install in this case. What exact problem do you solve
>by aborting?
You pick up an error correctly, and report it upwards so that other
programs calling grub-install can reliably check for errors, and maybe
deal with those errors.
I don't see why it's a problem to actually handle errors properly?
In Debian we're seeing quite a few people reporting problems in this
area. It would be better to catch and handle errors better here. See
https://bugs.debian.org/852513 for an example.
--
Steve McIntyre, Cambridge, UK. steve@einval.com
You raise the blade, you make the change... You re-arrange me 'til I'm sane...
next prev parent reply other threads:[~2017-02-09 20:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 19:04 [PATCH] Make grub-install check for errors from efibootmgr Steve McIntyre
2017-02-08 16:11 ` Steve McIntyre
2017-02-09 18:52 ` Andrei Borzenkov
2017-02-09 20:37 ` Steve McIntyre [this message]
2017-02-11 15:12 ` Leif Lindholm
2017-02-24 17:23 ` Steve McIntyre
-- strict thread matches above, loose matches on Subject: below --
2018-01-29 14:04 Steve McIntyre
2018-01-29 17:57 ` Daniel Kiper
2018-01-29 18:16 ` Steve McIntyre
2018-01-29 18:54 ` Steve McIntyre
2018-01-30 17:44 ` Daniel Kiper
2018-01-31 21:48 ` Steve McIntyre
2018-01-31 21:49 ` Steve McIntyre
2018-02-06 15:29 ` Daniel Kiper
2018-02-14 15:30 ` Steve McIntyre
2018-02-14 17:54 ` 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=20170209203705.GY12912@einval.com \
--to=93sam@debian.org \
--cc=arvidjaar@gmail.com \
--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.