Comment 13 for bug 1782379

Brian,

I just re-read your initial bug report. You stated: "Interestingly, if I select the 20 kernel and do the install, the new kernel is running on the resulting system"

This is normal/ correct behavior.

If you install a new kernel in the Cubic's chroot environment...
- The new kernel will be used inside your Live environment, launched from your customized ISO.
- The new kernel will be installed, if you install the OS from your customized ISO.

On Cubic's "Kernels" tab...
- You are ***NOT*** selecting which kernel your Live ISO uses.
- You are selecting which kernel is used by Casper to ~boot~ your live ISO.
- Theoretically, you could use any kernel to boot Casper,as long at it works.

When is this an issue?..
- If you install kernel modules or drivers in the chroot environment, but they are installed for a specific kernel
- In that case, those modules may not be available when you boot your Live ISO.
- An example may be Wi-Fi drivers. If they are installed for a different kernel than what you boot with, you may not have Wi-Fi access in your Live environment.
- Generally, this is not an issue.

TLDR...
- Leaving the default kernel should be good enough for most cases.
- You will still get to use your newly installed kernel in your Live ISO and in your OS installation.