Dear Glenn,
Am 06.03.21 um 00:15 schrieb Glenn Washburn:
On Fri, 5 Mar 2021 17:27:01 +0100 Daniel Kiper wrote:
[…]
By the way, my I ask you once again to send each patch series as
separate thread. Now you are attaching all patch sets to one cover
letter which is confusing. Please stop
- disable os-prober by default in grub-mkconfig.in by setting
GRUB_DISABLE_OS_PROBER to true
- fixes logic in 30_os-prober.in
Reason for code shuffle in grub-mkconfig.in:
The default was GRUB_DISABLE_OS_PROBER=false if you don't set
GRUB_DISABLE_OS_PROBER at all. To prevent os-prober from
On Fri, 5 Mar 2021 17:27:01 +0100
Daniel Kiper wrote:
> On Thu, Mar 04, 2021 at 06:22:31PM -0600, Glenn Washburn wrote:
> > Daniel, you mentioned wanting a separate patch series which is the
> > real fix for patch #12. I've added it to this patch series, since
> > they go together. I can send
Le 05/03/2021 à 22:15, Philip Müller a écrit :
- disable os-prober by default in grub-mkconfig.in by setting
GRUB_DISABLE_OS_PROBER to true
- fixes logic in 30_os-prober.in
Reason for code shuffle in grub-mkconfig.in:
The default was GRUB_DISABLE_OS_PROBER=false if you don't set
On Thu, Mar 04, 2021 at 06:22:31PM -0600, Glenn Washburn wrote:
> Daniel, you mentioned wanting a separate patch series which is the real fix
> for patch #12. I've added it to this patch series, since they go together.
> I can send the single patch as a separate thread if that still desirable.
On Thu, Mar 04, 2021 at 04:46:50PM -0600, Glenn Washburn wrote:
> On Thu, 4 Mar 2021 20:03:34 +0100
> Daniel Kiper wrote:
>
> > Does this patch fix all such issues in the GRUB source code?
> >
> > Daniel
>
> I don't know and its unclear the scope of your question. However, this
> is the grep I
On Fri, Mar 5, 2021 at 1:34 PM Michael Chang wrote:
>
> On Fri, Mar 05, 2021 at 12:21:49PM +, Dimitri John Ledkov wrote:
> > This is not an oversight but intentional.
> >
> > Currently there is no chainloader support with SBAT as further
> > development is required to ensure policy is applied
This is not an oversight but intentional.
Currently there is no chainloader support with SBAT as further
development is required to ensure policy is applied correctly. Once
SBAT support for chainloading is defined, it will be introduced.
And yes it is intended to continue to allow "boot windows"
While attempting to dual boot Microsoft Windows with efi chainloader, it
failed with below error when secure boot was enabled.
error ../../grub-core/kern/verifiers.c:119:verification requested but
nobody cares: /EFI/Microsoft/Boot/bootmgfw.efi.
It is a regression, as previously it worked without
On Fri, Mar 05, 2021 at 12:21:49PM +, Dimitri John Ledkov wrote:
> This is not an oversight but intentional.
>
> Currently there is no chainloader support with SBAT as further
> development is required to ensure policy is applied correctly. Once
> SBAT support for chainloading is defined, it
On Fri, Mar 05, 2021 at 01:32:57PM +0100, Thomas Frauendorfer wrote:
> On Fri, Mar 5, 2021 at 1:12 PM Michael Chang via Grub-devel
> wrote:
> >
> > While attempting to dual boot Microsoft Windows with efi chainloader, it
> > failed with below error when secure boot was enabled.
> >
> > error
On Fri, Mar 5, 2021 at 1:12 PM Michael Chang via Grub-devel
wrote:
>
> While attempting to dual boot Microsoft Windows with efi chainloader, it
> failed with below error when secure boot was enabled.
>
> error ../../grub-core/kern/verifiers.c:119:verification requested but
> nobody cares:
While attempting to dual boot Microsoft Windows with efi chainloader, it
failed with below error when secure boot was enabled.
error ../../grub-core/kern/verifiers.c:119:verification requested but
nobody cares: /EFI/Microsoft/Boot/bootmgfw.efi.
It is a regression, as previously it worked without
13 matches
Mail list logo
