The logical conclusion of that is that everything should be built into
the kernel. Where a failure brings the system down or worse. Where you
have to bear the memory footprint whether you ever use the functionality
or not. Where to update the functionality you need to deploy a new
kernel (possibly introducing unrelated bugs) and reboot.
If userspace daemons are such a deployment and usability nightmare,
maybe we should fix that instead.
You have to modify the guest anyway by deploying a new kernel.
inetd.d style 'drop a listener config here and it will be executed on
connection' should work. The listener could come with the kernel
package, though I don't think it's a good idea. module-init-tools
doesn't and people have survived somehow.
Thanks.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
--
