[Bug 258749] /etc/defaults/rc.conf says devmatch_blacklist doesn't need .ko, but it does
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 258749] /etc/defaults/rc.conf says devmatch_blacklist doesn't need .ko, but it does"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 258749] /etc/defaults/rc.conf says devmatch_blacklist doesn't need .ko, but it does"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 27 Sep 2021 18:11:09 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258749
Bug ID: 258749
Summary: /etc/defaults/rc.conf says devmatch_blacklist doesn't
need .ko, but it does
Product: Base System
Version: 13.0-STABLE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: conf
Assignee: bugs@FreeBSD.org
Reporter: mwlucas@michaelwlucas.com
Not sure what the correct behavior is, so I'm pointing out the inconsistency
and letting y'all decide. /etc/defaults/rc.conf says:
devmatch_blacklist="" # List of modules (w/o .ko) to exclude from devmatch.
This appears to be incorrect.
Thanks to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253175 I had to
disable virtio_random on my new VM at install time. I set
devmatch_blacklist="virtio_random"
and the module was loaded anyway.
devmatch_blacklist="virtio_random.ko" prevented the module from being loaded.
So, either the script is working wrong or the comment is incorrect.
I checked rc.conf(5) for a tiebreaker, but it doesn't specifically mention .ko.
--
You are receiving this mail because:
You are the assignee for the bug.