Date: Fri, 13 Jun 2003 12:37:49 +0200 From: Marko Kuntic <mkuntic@mioc.hr> To: FreeBSD-gnats-submit@FreeBSD.org Subject: kern/53276: modules ignore kernel configuration upon kernel building Message-ID: <E19QlwL-000FtT-00@zagreb.mioc.hr> Resent-Message-ID: <200306131040.h5DAeBtC041658@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 53276 >Category: kern >Synopsis: modules ignore kernel configuration upon kernel building >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Fri Jun 13 03:40:10 PDT 2003 >Closed-Date: >Last-Modified: >Originator: Marko Kuntic >Release: FreeBSD 5.0-RELEASE-p6 i386 >Organization: XV. gimnazija, Zagreb, Croatia >Environment: System: FreeBSD zagreb.mioc.hr 5.0-RELEASE-p6 >Description: When the kernel is built along with all the modules, the latter don't seem to apply configuration options specified in the kernel configuration file. >How-To-Repeat: For example, I don't want to compile ipfw into the kernel, but wish to use the module. But, at the same time, I require divert sockets. So in the appropriate kernel configuration file, applying common sense and logic, I comment out: #options IPFIREWALL and uncomment: options IPDIVERT I then happily make the kernel and all the modules, only to discover that the module doesn't support divert sockets, and thus conclude that the configuration option had no effect. >Fix: UNKNOWN >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E19QlwL-000FtT-00>