Date: Wed, 18 Jun 2008 21:10:03 GMT From: Sam Banks <samb@catalyst.net.nz> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/120084: [boot] loader_conf_files in /boot/loader.conf no longer works [regression] Message-ID: <200806182110.m5ILA33N026900@freefall.freebsd.org>
index | next in thread | raw e-mail
The following reply was made to PR bin/120084; it has been noted by GNATS. From: Sam Banks <samb@catalyst.net.nz> 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?home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200806182110.m5ILA33N026900>