1) I had to disable the DKMS AUTOINSTALL feature to to let the module be built on Ubuntu or any other system that does not have the "dkms_autoinstaller" service enabled. This service is disabled on Ubuntu by default and I believe this is a wise decision. The idea to build the modules at boot time seems to me rather dubious for any system. And it is especially dubious for the firewall module, which should be available at the earliest stages of the boot process.
So let the module be built upon the kernel upgrade, in the quiet and controlled environment. Anyone who likes to wait some extra minutes for the system to boot and then to see whether all necessary modules were built and loaded, may turn this feature manually.
2) I also added some "make" defs for the proper module VERMAGIC to be emitted.
Lochnair
commented
4 years ago
1) I had to disable the DKMS AUTOINSTALL feature to to let the module be built on Ubuntu or any other system that does not have the "dkms_autoinstaller" service enabled. This service is disabled on Ubuntu by default and I believe this is a wise decision. The idea to build the modules at boot time seems to me rather dubious for any system. And it is especially dubious for the firewall module, which should be available at the earliest stages of the boot process.
So let the module be built upon the kernel upgrade, in the quiet and controlled environment. Anyone who likes to wait some extra minutes for the system to boot and then to see whether all necessary modules were built and loaded, may turn this feature manually.
2) I also added some "make" defs for the proper module VERMAGIC to be emitted.