Multiboot modules that could not be read successfully (e.g. via network)
should not be added to the list of modules to forward to the operating
system that is to be booted subsequently.
This patch is necessary because even if a grub.cfg checks whether or not
a module was successfully downloaded, i
Multiboot modules that could not be read successfully (e.g. via network)
should not be added to the list of modules to forward to the operating
system that is to be booted subsequently.
This patch is necessary because even if a grub.cfg checks whether or not
a module was successfully downloaded, i
Hey,
On Fri, Oct 25, 2024 at 01:59:25PM +0200, Valentin Gehrke wrote:
> Hey Daniel,
>
> did you have time yet to give the patch in my last email
> a try? I just want to make sure the email didn't get
> overlooked.
Sorry, it looks it fell through the cracks.
Anyway, I think I was going to ask you
024 16:41:23 +0200
> Subject: [PATCH] loader/multiboot: do not add modules before
> successful download
>
> Multiboot modules that could not be read successfully (e.g. via
> network) should not be added to the list of modules to forward to the
> operating system that is to be boote
: Fri, 23 Aug 2024 16:41:23 +0200
Subject: [PATCH] loader/multiboot: do not add modules before successful
download
Multiboot modules that could not be read successfully (e.g. via network)
should not be added to the list of modules to forward to the operating
system that is to be booted subsequent
On Fri, Aug 23, 2024 at 08:20:53PM +0200, Valentin Gehrke wrote:
> Multiboot modules that could not be read successfully (e.g. via network)
> should not be added to the list of modules to forward to the operating
> system that is to be booted subsequently.
>
> This patch is necessary because even i
On Fri, Aug 23, 2024 at 08:20:53PM +0200, Valentin Gehrke wrote:
> Multiboot modules that could not be read successfully (e.g. via network)
> should not be added to the list of modules to forward to the operating
> system that is to be booted subsequently.
>
> This patch is necessary because even i
Multiboot modules that could not be read successfully (e.g. via network)
should not be added to the list of modules to forward to the operating
system that is to be booted subsequently.
This patch is necessary because even if a grub.cfg checks whether or not
a module was successfully downloaded, a
