On 01/02/2016 04:49 PM, Stephanie Daugherty <sdaugherty@???> wrote:
> Might be worth trying to get interest upstream for functionality to
> "merge" binary modules with an already compiled kernel as a single
> file. Presumably, it wouldn't be *that* difficult for the kernel to
> look for modules at the end of its image and load them early. Not sure
> what the kernel maintainers would say to this idea, but it seems like
> it would be more robust than initrd/initramfs. On Sat, Jan 2, 2016 at
> 6:25 AM, aitor_czr <aitor_czr@???> wrote:
>> >On 01/02/2016 11:28 AM, Mitt Green<mitt_green@???>
>> ><mitt_green@???> wrote:
>> >
>> >I think that there is no real alternative to initrd/initramfs for a>general-purpose kernel, as those included in the install image of a>distro. At the same time, nothing prevents a user from compiling and>installing her own preferred kernel, with or without initramfs.
>> >
>> >What prevents devs (kernels packages' maintainers)
>> >from compiling a kernel without initramfs support? (:
>> >
>> >Peace,
>> >Mitt

Devuan-installer can replace the kernel in the target (the installed
system) during the installation adding/removing all the wanted/unwanted
modules. One year ago i debianized Linux-Libre-3.16.7 adding some
kernel-modules (like, for example, floppy-modules) to the default
configuration of debian, including the .udeb packages for d-i:

http://apt-gnuinos.org/pool/main/l/linux/

Shortly i'm going to do the same with the latest version of
Linux-Libre-4.4-rc7 for the following architectures: i586, i686-pae,
amd64 and armhf (Raspberry Pi). But now i'm working on netman-gtk3 and
the .deb packages of vdev.

Any suggestion about the included kernel modules?

    Aitor.