-- so KRNL_VERS was an array of the different kernels found, and KRNL would then pick the most recent version.
KVER is then an array built by splitting $KRNL on -
But the current code is a bit of a mix b/w handling multiple kernels, and single ones and thus
mv ${KRNL_VERS[@]} /boot/${KRNL}
# would expand to
mv /boot/vmlinuz-5.3.0-59-generic /boot/vmlinuz-5.3.0-62-generic /boot/vmlinuz-5.3.0-64-generic /boot/vmlinuz
However, all this is probably moot as I believe we would only have a single Kernel in /boot (especially during image building time) so I simplified it to explicitly set it directly to vmlinuz to avoid any confusion.
From a2efe8bf5e7da00eb639ec8105168f09d01ebd16, isn't https://github.com/volumio/Build/blob/a2efe8bf5e7da00eb639ec8105168f09d01ebd16/recipes/devices/families/x86.sh#L169-L170 a rather roundabout way of just setting the current kernel to
vmlinuz
? i.eKRNL=vmlinuz
The initial stuff was written to handle multiple kernels - on my system,
This gives:
-- so
KRNL_VERS
was an array of the different kernels found, andKRNL
would then pick the most recent version.KVER
is then an array built by splitting$KRNL
on-
But the current code is a bit of a mix b/w handling multiple kernels, and single ones and thus
However, all this is probably moot as I believe we would only have a single Kernel in /boot (especially during image building time) so I simplified it to explicitly set it directly to
vmlinuz
to avoid any confusion.