[Bug 295485] need a way to block zfs.ko from being autoloaded by tools like puppet and facter
[email protected] Fri, 22 May 2026 21:31:07 +0000
| Newsgroups | gmane.os.freebsd.devel.file-systems |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=295485 --- Comment #6 from Dan Mahoney <[email protected]> --- (In reply to Alan Somers from comment #4) Okay, I concede your point, but one of these directly has to do with configuring that network card. That command needs that module to do its job, ostensibly. I mean, it'll also load the module even if that card isn't present, but the card may not show up until the module is loaded, so that's sort of requisite. On the other hand, what I'm working with is a built-in behavior to a *port* (which I guess runs something like zpool status to get the state of the mounted drives), It's not like puppet/facter has a "load the ZFS module" function built in. This happens even on systems where you _know_ you're not running ZFS. If you were running ZFS, the .ko would already be loaded. Arguably, zpool status should just return "zfs not enabled" when you run zpool status or whatever. Just like "ipmitool lan print 1" doesn't magically force ipmi.ko to be loaded. It would be super if there were a global tunable that just said "don't load anything that I didn't set foo_load in /boot/loader.conf or didn't manually kldload", without the headache of everything else associated with securelevels. -- You are receiving this mail because: You are the assignee for the bug.