Migrate packages requiring kernel modules to `modules-load.d`

[sighook]

Background

Some packages (e.g. openvpn, fuse, cdrtools) currently instruct users to edit /etc/rc.modules to load required kernel modules. This is fragile and inconsistent.

Zeppe‑Lin provides modules-load(8), a declarative system. Packages can ship a static config file in /lib/modules-load.d/ listing required modules. This ensures modules are loaded automatically at boot, while still allowing administrators to override or disable.

Goal

• Each package that requires a kernel module must install a file:

  /lib/modules-load.d/<package>.conf
  

  containing the module name(s).
• README files must be updated to use the standard template (below).
• Reword instructions telling users to edit /etc/rc.modules (below).

Scope

• Identify all packages that require kernel modules.
• Add modules-load.<package>.conf to each.
• Update package Pkgfiles to install the file into /lib/modules-load.d/<package>.conf.
• Update README content with the standard template.

Standard README Template

REQUIREMENTS
============

Kernel Configuration
--------------------

<add if needed for custom kernel setups>

Kernel Module
-------------

This package needs the **<module_name>** kernel module.

It provides `/lib/modules-load.d/<package>.conf` for `modules-load(8)`.
The module will be loaded at boot.

- To override: copy to `/etc/modules-load.d/` and edit.
- To disable: symlink `/etc/modules-load.d/<package>.conf` to `/dev/null`.

Legacy `/etc/rc.modules` still works if you prefer manual loading.

Maintainers only replace <package> and <module_name>(s).

Candidate Packages (initial list)

• openvpn → tun
• fuse → fuse
• wireguard-tools → wireguard
• v4l2loopback → v4l2loopback
• net/tuntap → tun
• virtualbox → vboxdrv, vboxnetflt, vboxnetadp
• nfs-utils → nfsd
• iscsi-tools → iscsi_tcp

Expand list with results from:

grep 'KERNEL MODULE' -R /usr/src/pkgsrc-* --include=README*

Acceptance Criteria

• Installing a package automatically prepares its required modules for boot.
• Removing a package cleans up its module requirement.
• Administrators can override or disable via /etc/modules-load.d/.
• README files are uniform and minimal.
• No regressions in boot‑time module availability.

[sighook]

Shipping /lib/modules-load.d/*.conf files to auto‑load kernel modules at boot imposing policy on all systems, even when modules were optional or not needed.

Updating Policy

• No package ships /lib/modules-load.d/*.conf.
  Auto‑loading modules is an administrator decision, not package policy.
• Packages only document requirements.
  READMEs must state which modules are needed and show how to load them manually or automatically.
• Administrators choose the method:
  • Declarative: add module names to /etc/modules-load.d/*.conf (one per line).
  • Imperative: add /sbin/modprobe <module> lines to /etc/rc.modules.

Standard README Template

REQUIREMENTS
============

Kernel Module
-------------
This package requires the **<module_name>** kernel module.

Load manually:

    /sbin/modprobe <module_name>

Load automatically at boot:
- Add `<module_name>` to `/etc/modules-load.d/<package>.conf`, or
- Add `/sbin/modprobe <module_name>` to `/etc/rc.modules`

This package does not install a default config; administrators should
add modules as needed by their setup.

Maintainers only replace <package> and <module_name>.

Scope

• Identify all packages that mention kernel modules in their README.
• Remove any shipped /lib/modules-load.d/*.conf files.
• Update README content to use the standard template.
• Ensure consistency across packages (required vs optional modules).

Acceptance Criteria

• Packages no impose module auto‑loading.
• Administrators retain full control over module policy.
• README files are uniform, minimal, and clear.
• No regressions in boot‑time module availability (admins can still configure as needed).