I received a request to add insmod.static to the module-init-tools
package, but I do not really like either solution.
Does anybody have an opinion about this?
----- Forwarded message from "Richard W.M. Jones" <firstname.lastname@example.org> -----
From: "Richard W.M. Jones" <email@example.com>
To: Marco d'Itri <firstname.lastname@example.org>, Guido Günther <email@example.com>,
Subject: Bug#627353: Please include insmod.static
[Previous response appears to have been consumed in the aether]
> Can you clarify why it does?
> I do not really like wasting space on every Debian system without a good
Well I can tell you what we use it for in febootstrap:
We boot the appliance using a custom initramfs which has a statically
linked init (no libc6) and which has to load kernel modules in order
to mount the real root filesystem. In order to load those, we need a
statically linked insmod.static.
However I understand that having insmod.static on every Debian machine
just for this purpose is a waste of space. Can it be easily included
in a sub-package?
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
----- End forwarded message -----