Avoid setting non-standard GRUB_DISTRIBUTOR in /etc/default/grub if you
use Debian 12 bookworm with enabled Secure Boot and signed grub image
from Debian. Alternatively install grub-2.12 from backports.
On 23/08/2024 11:39, Felix Miata wrote:
I don't know what vexing secure boot might introdu
On 30/08/2024 23:42, Felix Miata wrote:
Max Nikulin composed on 2024-08-30 23:09 (UTC+0700):
How does grubx64.efi find where grub.cfg is located?
I don't know what doc might report this, but in a file viewer I see a string
like
(,gpt7)/boot/grub) embedded in a vast sea of nulls 98% of the wa
Max Nikulin composed on 2024-08-30 23:09 (UTC+0700):
> How does grubx64.efi find where grub.cfg is located?
I don't know what doc might report this, but in a file viewer I see a string
like
(,gpt7)/boot/grub) embedded in a vast sea of nulls 98% of the way into the file.
--
Evolution as taught i
On 23/08/2024 11:39, Felix Miata wrote:
I don't know what vexing secure boot might introduce, but without it,
GRUB_DISTRIBUTOR= was used by grub-install in Trixie here to produce
results I expected:
[...]
# grep TOR /etc/default/grub
GRUB_DISTRIBUTOR="debian13"
[...]
├── debian13
│ └── grub
On 22/08/2024 16:44, Felix Miata wrote:
That is written by any process that
reads GRUB_DISTRIBUTOR= to determine where to do its writing on the ESP.
To avoid confusion of those who may notice this thread in search engine
results:
In Debian GRUB_DISTRIBUTOR value is *not* passed to "grub-inst
Max Nikulin composed on 2024-08-22 22:56 (UTC+0700):
> Felix Miata wrote:
>> # ls -gG/boot/efi/EFI/opensusetw/
>> total 148
>> -rwxr-xr-x 1 151552 Aug 21 16:08 grubx64.efi
> Am I right that you either do not use Secure Boot or generated a local
> key instead of/in addition to Microsoft and SUSE
On 22/08/2024 16:44, Felix Miata wrote:
# ls -gG/boot/efi/EFI/opensusetw/
total 148
-rwxr-xr-x 1 151552 Aug 21 16:08 grubx64.efi
Am I right that you either do not use Secure Boot or generated a local
key instead of/in addition to Microsoft and SUSE ones?
In the case of default or almost defa
Max Nikulin composed on 2024-08-22 10:17 (UTC+0700):
> Felix Miata wrote:
>> My BBS menu contains 4 entries corresponding to output from efibootmgr,
>> with the highlight on the one beginning "opensusetw", as configured via
>> GRUB_DISTRIBUTOR=.
> Or it just coincides with the configured value.
On 22/08/2024 05:21, Felix Miata wrote:
My BBS menu contains 4 entries corresponding to output from efibootmgr,
with the highlight on the one beginning "opensusetw", as configured via
GRUB_DISTRIBUTOR=.
Or it just coincides with the configured value. My expectation is that
EFI/opensusetw/grub.
Max Nikulin composed on 2024-08-21 23:17 (UTC+0700):
> Felix Miata wrote:
>> Max Nikulin composed on 2024-08-21 10:54 (UTC+0700):
>>> I was experimenting trying to get 2
>>> entries from the same vendor in the UEFI (firmware) boot menu and found
>>> it tricky and inconvenient.
>> How so? I fo
Max Nikulin (12024-08-21):
> Have I missed something or GRUB_DISTRIBUTOR affects *grub* menu, but not
> *UEFI* boot menu?
Indeed, it is not just as simple as that.
>I still suspect it is a UEFI+SecureBoot design
> shortcoming that it is not possible to install the same loader
On 21/08/2024 11:25, Felix Miata wrote:
Max Nikulin composed on 2024-08-21 10:54 (UTC+0700):
I was experimenting trying to get 2
entries from the same vendor in the UEFI (firmware) boot menu and found
it tricky and inconvenient.
How so? I found it quite simple to edit /etc/default/grub and re
On Wed, 21 Aug 2024 08:45:05 +0200
Nicolas George wrote:
> Max Nikulin (12024-08-21):
> > Do you mean 3rd party bootloader (e.g. grub)?
>
> There is nothing “3rd party” about GRUB.
>
> > I was responding to
> > "AIUI
> > UEFI/GPT were designed t
Max Nikulin (12024-08-21):
> Do you mean 3rd party bootloader (e.g. grub)?
There is nothing “3rd party” about GRUB.
> I was responding to "AIUI
> UEFI/GPT were designed to support multi-boot".
Yes, and so was I. If you want half a dozen different GRU
Max Nikulin composed on 2024-08-21 10:54 (UTC+0700):
> I was experimenting trying to get 2
> entries from the same vendor in the UEFI (firmware) boot menu and found
> it tricky and inconvenient.
How so? I found it quite simple to edit /etc/default/grub and replace the
default
value of GRUB_DIS
On 20/08/2024 22:50, Nicolas George wrote:
Max Nikulin (12024-08-20):
Single EFI System Partition may contain loaders from different vendors, but
not 2 Debian systems installed on different partitions.
This is not true. The only problem you will have with this setup is that
you will need to in
On 8/20/24 12:29, Jeffrey Walton wrote:
On Tue, Aug 20, 2024 at 11:51 AM Nicolas George wrote:
[...]
EFI files are signed
for Secure Boot, so vendor paths can not be easily adjusted.
Secure boot is a joke when it comes to security, it
On Tue, Aug 20, 2024 at 11:51 AM Nicolas George wrote:
>
> [...]
> > EFI files are signed
> > for Secure Boot, so vendor paths can not be easily adjusted.
>
> Secure boot is a joke when it comes to security, its only “merit” is to
> prevent l
Max Nikulin (12024-08-20):
> Single EFI System Partition may contain loaders from different vendors, but
> not 2 Debian systems installed on different partitions.
This is not true. The only problem you will have with this setup is that
you will need to install and/or configure the bootloader manua
On Tue, Aug 20, 2024 at 05:17:43PM CEST, Max Nikulin said:
> On 20/08/2024 11:27, David Christensen wrote:
> > AIUI UEFI/GPT were designed to support multi-boot
>
> Single EFI System Partition may contain loaders from different vendors, but
> not 2 Debian systems installed on different partitions
20 matches
Mail list logo
