Project/ModularKernel

Kernel modules are cool, and important to have!
 * Smaller dtbImage sizes
 * More drivers, strings, whatever else without hitting bootloader limits
 * In line with distribution standard practice
 * The end of #KernelTooBig

Using kernel modules requires the distribution and the kernel to be version-matched - aka, the distribution provides its own kernel with matched modules. This is also really good for distributions that might want a patched or minimal kernel.
 * linux-loader can only read fat32 partitions off the SD card
 * distributions need to be kept separate, each with its own kernel
 * distributions want to write their kernels to /boot
 * creating a separate boot partition is probably a bit much - users want to drop some files on the SD, flash a USB, and go. Would be different if linux-loader could read USB.

So, here's the plan:
 * User starts with a non-modular kernel to boot up, run install scripts, whatever
 * User creates a folder - sdmc:/linux/boot/, updates linux-loader config to load kernel from sdmc:/linux/boot/ /dtbImage.wiiu
 * User adds the following snippet to their /etc/fstab:
 * sd is now mounted to /media/sdcard, then distro boot folder is bindmounted over
 * User installs distro-specific kernel package, extracting kernel into /boot -> sdmc:/linux/boot/ and modules in the usual place
 * Distribution kernel and modules are now version-matched!

What needs to happen?
 * Kernel builds with modules need to be made available - done, artifacts in linux-build-modular job
 * Modular kernel packages built and shipped for distros - deb.linux-wiiu.org? Collaboration with Void/Adelie? Repackaging tarball distros?
 * Users actually need to make the changes described - most can probably be scripted. "currently booted profile" commandline flag is being considered for linux-loader to help name distro folder.
 * Documentation updates across the board