On Sat, 27 Jul 2024 19:31:37 +0100
void wrote:
> On Sat, Jul 27, 2024 at 03:01:22PM +, Gary Jennejohn wrote:
>
> >filemon is not a device, it's an option. So you can't have "device
> >filemon" in your kernel config file.
> >
> >I compile it with makeoptions MODULES_OVERRIDE="filemon ..." in my
> >kernel config file.
>
> What's the actual line in your kernel config file please?
>
makeoptions MODULES_OVERRIDE="cpuctl filemon aesni vesa amdsmn amdtemp"
These are the only modules under /usr/src which I use, so I limit
building modules using MODULES_OVERRIDE.
> >I also load it from /boot/loader.conf using filemon_load="YES"
>
> Why do you do both? (I presume both as you're saying you 'also load')
>
Because filemon.ko has to be loaded.
But you're right, device filemon works in my kernel config file. I
added device filemon (and removed it from MODULES_OVERRIDE) and
my kernel compiled successfully.
I removed filemon_load="YES" from /boot/loader.conf and booted the
new kernel. kldstat -v showed that filemon was in the kernel.
So I guess I misunderstood what optional means in
/sys/conf/files:dev/filemon/filemon.c optional filemon
--
Gary Jennejohn
