Date: Fri, 8 Dec 2017 16:54:24 +0100
From: Maxime Villard <m...@m00nbsd.net>
Message-ID: <96c690fd-8577-0e4d-dcbb-84c51aed0...@m00nbsd.net>
| No, it wasn't barbaric, it made perfect sense:
It was, and made no sense.
| when modloaded the linux execsw is not registered,
I don't know enough about the module structures and what the module
init code does to answer that, but I do believe that other modules
can be loaded (incl autoloaded) and do not need some extra sysctl enable
routine to make them operable - hence that should not be necessary
here either.
If something more is needed than is there now (for the case of the built-in
module, or for later loaded modules) someone who understands can fix it
all I'm sure. But forcing the module to be disabled as part of its init
routine will not be a part of that.
kre
