<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr">Hi,</div><div dir="ltr"><br></div><div dir="ltr">So I’ve implemented this feature in the master branch. It works the same way as FreeBSD.</div><div dir="ltr"><br></div><div dir="ltr">FYI, the changes to the kernel part and kldstat(8) are obtained from FreeBSD. However, the boot loader part is quite different and took much efforts.</div><div dir="ltr"><br></div><div dir="ltr">Cheers,</div><div dir="ltr">Aaron</div><div dir="ltr"><br><blockquote type="cite">On Jan 11, 2023, at 05:53, Will Senn <will.senn@gmail.com> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<font face="Helvetica, Arial, sans-serif">Hi,<br>
<br>
Is there a way to determine whether or not a module is being
loaded from /boot/kernel or /boot/modules.local? I tried kldstat
-v, but it doesn't show the path:<br>
<br>
<font face="monospace"> 4 1 0xffffffff82600000 3972000
amdgpu.ko<br>
Contains modules:<br>
Id Name<br>
329 vgapci/amdgpu</font><br>
<br>
vs on freebsd:<br>
<font face="monospace"><br>
2 1 0xffffffff825c1000 5a2c28 openzfs.ko
(/boot/modules/openzfs.ko)<br>
Contains modules:<br>
Id Name<br>
1 zfsctrl<br>
3 zfs<br>
4 zfs_zvol<br>
2 zfs_vdev</font><br>
<br>
Thanks,<br>
Will<br>
</font>
</div></blockquote></body></html>