Re: How to load ffs module via boot.cfg?

[Jukka Ruohonen <jruohonen%iki.fi@localhost>]

On Mon, Jun 01, 2020 at 05:26:16AM -0700, Paul Goyette wrote:
> Also, you'll need to include a couple of dependency/required modules:
> 
>  	load=ufs
>  	load=wapbl

Ah yes, it tried to load ffs, but ufs and wapbl were probably missing;

[     1.000000] NetBSD 9.99.64 (MODULAR) #0: Mon Jun  1 14:20:02 EEST 2020
[     1.000000]         jruoho@kafka:/usr/obj/sys/arch/amd64/compile/MODULAR
[     1.000000] total memory = 8075 MB
[     1.000000] avail memory = 7802 MB
[     1.000000] entropy: entering seed from bootloader with 256 bits of entropy
[     1.000000] entropy: ready
[     1.000000] kobj_checksyms, 1020: [/ffs.kmod]: linker error: global symbol `ffs_vnodeop_opv_desc' redefined
[     1.000000] kobj_checksyms, 1020: [/ffs.kmod]: linker error: global symbol `ffs_snapshot_fini' redefined
[...]

> You can strip out a lot more modules and still have a functioning
> system.  Mostly you can remove all the device drivers for devices
> that don't exist, but there are other things, too.
> 
> FWIW,
> 
> $ modstat | grep builtin | wc -l
>        21

Nice!  Since you seem to have this nailed down already, do you have time to
update the off-the-shelf MODULAR config?  I'd also fancy a good development
kernel with which I can unload/patch/load/etc. as much code as is possible.

I also noticed that some things that are disabled in GENERIC (e.g.,
experimental, old, or generally less useful drivers) are available as
modules. The examples include odcm(4), hpacel(4), and hpqlb(4).

- Jukka