From owner-freebsd-bugs@FreeBSD.ORG Wed Jun 18 21:10:04 2008 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 111D61065670 for ; Wed, 18 Jun 2008 21:10:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E73038FC14 for ; Wed, 18 Jun 2008 21:10:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m5ILA3KU026901 for ; Wed, 18 Jun 2008 21:10:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m5ILA33N026900; Wed, 18 Jun 2008 21:10:03 GMT (envelope-from gnats) Date: Wed, 18 Jun 2008 21:10:03 GMT Message-Id: <200806182110.m5ILA33N026900@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Sam Banks Cc: Subject: Re: bin/120084: [boot] loader_conf_files in /boot/loader.conf no longer works [regression] X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Sam Banks List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jun 2008 21:10:04 -0000 The following reply was made to PR bin/120084; it has been noted by GNATS. From: Sam Banks To: bug-followup@FreeBSD.org, 20080111.freebsd.org@ab.ote.we.lv Cc: Subject: Re: bin/120084: [boot] loader_conf_files in /boot/loader.conf no longer works [regression] Date: Thu, 19 Jun 2008 09:03:51 +1200 I've tested this on 7.0-RELEASE and can't reproduce the problem using the following: Inside /boot/loader.conf, I have loader_conf_files="/boot/modules.conf". Inside /boot/modules.conf, I have nullfs_load="YES" and ntfs_load="YES". When I reboot, both of those modules are loaded into the kernel. The only thing I can do to reproduce the results is, inside /boot/modules.conf, modify it to read NULLFS_load="YES" and NTFS_load="YES". I wasn't sure if the capitilised module name inside MODULENAME_load="YES" was just a "replace with lower case module name" or whether the module name is being entered in capitals. Just to check the basics: 1. Is loader_conf_files spelled correctly in /boot/loader.conf? 2. Does the value of loader_conf_files in /boot/loader.conf match the file in /boot it's meant to load? 3. Do the modules load when you kldload them manually when the system is up and running?