Date: Sun, 19 Jan 2025 04:43:00 +0100
Author: Steffen Nurpmeso <steffen@sdaoden.eu>
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Mark Hills <mark@xwax.org>
Cc: ~alpine/users@lists.alpinelinux.org
Subject: Re: Solutions for EFI booting / copying kernels
Message-ID: <20250119034300.U38149mm@steffen%sdaoden.eu>
In-Reply-To: <8f3899df-71b7-6562-7688-7bebc6ac1f94@xwax.org>
References: <8f3899df-71b7-6562-7688-7bebc6ac1f94@xwax.org>
Mail-Followup-To: Mark Hills <mark@xwax.org>,
 ~alpine/users@lists.alpinelinux.org
User-Agent: s-nail v14.9.25-636-gc7c14cee09-dirty
OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD;
 url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in
 the world can make no bugs.

Mark Hills wrote in
 <8f3899df-71b7-6562-7688-7bebc6ac1f94@xwax.org>:
 |I have a few Alpine systems which use EFI to boot with syslinux.
 |
 |I'd like to improve this setup.
 |
 |The kernel+initramfs are copied to /efi, where syslinux finds them.
 |
 |Invariably, after "apk upgrade" I forget to do this copy, resulting in a 
 |system that won't boot.

Use overlay / --bind mounts?
Why use a boot loader at all, i think the AlpineLinux kernel has
EFI_STUB enabled?  efibootmgr and you should be fine.

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)
|
|In Fall and Winter, feel "The Dropbear Bard"s pint(er).
|
|The banded bear
|without a care,
|Banged on himself for e'er and e'er
|
|Farewell, dear collar bear