Date: Mon, 20 Jan 2025 18:17:07 +0000
From: Mark Hills <mark@xwax.org>
To: Steffen Nurpmeso <steffen@sdaoden.eu>
CC: ~alpine/users@lists.alpinelinux.org
Subject: Re: Solutions for EFI booting / copying kernels
In-Reply-To: <20250119034300.U38149mm@steffen%sdaoden.eu>
References: <8f3899df-71b7-6562-7688-7bebc6ac1f94@xwax.org> <20250119034300.U38149mm@steffen%sdaoden.eu>
Message-ID: <BD2FAE77-F90E-4617-A918-F5338881E6FE@xwax.org>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable



On 19 January 2025 03:43:00 GMT, Steffen Nurpmeso <steffen@sdaoden=2Eeu> w=
rote:
> Mark Hills wrote in
>  <8f3899df-71b7-6562-7688-7bebc6ac1f94@xwax=2Eorg>:
>  |I have a few Alpine systems which use EFI to boot with syslinux=2E
>  |
>  |I'd like to improve this setup=2E
>  |
>  |The kernel+initramfs are copied to /efi, where syslinux finds them=2E
>  |
>  |Invariably, after "apk upgrade" I forget to do this copy, resulting in=
 a=20
>  |system that won't boot=2E
>=20
> Use overlay / --bind mounts?

Can you be more specific please? How to apply these to the problem=2E

> Why use a boot loader at all, i think the AlpineLinux kernel has
> EFI_STUB enabled?  efibootmgr and you should be fine=2E

Is that an improvement though? It locks in the need for kernel+initramfs t=
o be on the EFI partition, but doesn't help with making it happen=2E

--=20
Mark