Date: Tue, 21 Jan 2025 11:20:48 +0000 (GMT)
From: Mark Hills <mark@xwax.org>
To: Sertonix <sertonix@posteo.net>
cc: ~alpine/users@lists.alpinelinux.org
Subject: Re: Solutions for EFI booting / copying kernels
In-Reply-To: <D774PQ9SBXGN.2JIXM10VQVUNH@posteo.net>
Message-ID: <37f7104c-96b0-7c19-a35a-081f879c71d6@xwax.org>
References: <8f3899df-71b7-6562-7688-7bebc6ac1f94@xwax.org> <D774PQ9SBXGN.2JIXM10VQVUNH@posteo.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Mon, 20 Jan 2025, Sertonix wrote:

> > 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.
[...]
> I think it should work if you mount the EFI partition at /boot instead
> of /efi. Then there isn't any copying needed.

I had assumed having /boot as some kind of DOS/VFAT filesystem would cause 
trouble. It 'feels' very wrong, but I had assumed it would cause problem 
with filenames & permissions managed by apk, disk checks and so on.

Is this a common practice?

Thanks

-- 
Mark