KMODULEDIR is no longer absolute (${DESTDIR} is added to it by the system
makefile because we need to install the module in two places the debug part
and the regular part)

Get rid of static Atffiles and let bsd.test.mk generate them on the fly.

Fix two bugs to make MKMODULAR=yes builds will work again, for the
first time.

share/mk/bsd.kmodule.mk: only set _INST_DIRS if KMODULEDIR is not
set. That we we avoid installing some bogus directories in
the DESTDIR and in $DESTDIR/METALOG.

tests/modules/k_helper/Makefile: add missing .include <bsd.own.mk>,
and set the KMODULEDIR that the author seems to have intended.

branches: 1.3.2;
Fix MKMODULAR=yes builds by resolving installation problems of the k_helper
test module after the introduction of bsd.kmodule.mk. The files list was
inconsistent with the new module structure and the Makefile did not use the
correct variable to specify the installation of the module. Hi ad@!

- Add a bsd.kmodule.mk to build new style modules.
- Set the file suffix to .kmod

branches: 1.1.4; 1.1.6;
Add preliminary tests (basically a placeholder for now) for the new modules
framework. At the moment, this just tests for plain load (i.e. no arguments
passed to load) and later unload of the module through the modctl(2) system
call. The tools are not tested yet.

Update the t_modctl test to ensure that static evcnts are added.

While here, remove the explicit call to sysctl_setup() routine,
since the module infrastructure already invokes such routines
automatically.

branches: 1.6.32;
Fix build - delete extra &

branches: 1.5.6;
add Makefile.inc everywhere so that we can set WARNS=4 by default. Amazing
how many bugs this found :-)

Add a new atf test-case to check that recursive module calls actually work.

Remove clause 3 and 4 from TNF licenses

branches: 1.2.2; 1.2.4;
Add tests for load-time parameter passing to modules, both at the syscall
level through modctl(2) and at the user level through the modload(8)
utility.

branches: 1.1.2;
Add preliminary tests (basically a placeholder for now) for the new modules
framework. At the moment, this just tests for plain load (i.e. no arguments
passed to load) and later unload of the module through the modctl(2) system
call. The tools are not tested yet.