Date: Thu, 19 Jun 2008 15:40:04 GMT From: "Eugene M. Kim" <20080111.freebsd.org@ab.ote.we.lv> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/120084: [boot] loader_conf_files in /boot/loader.conf no longer works [regression] Message-ID: <200806191540.m5JFe4aV087836@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/120084; it has been noted by GNATS. From: "Eugene M. Kim" <20080111.freebsd.org@ab.ote.we.lv> To: Sam Banks <samb@catalyst.net.nz> Cc: bug-followup@FreeBSD.org Subject: Re: bin/120084: [boot] loader_conf_files in /boot/loader.conf no longer works [regression] Date: Thu, 19 Jun 2008 08:38:30 -0700 Sam Banks wrote: > 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? Yes to all three of them (at least on the 8-CURRENT machine that exhibits the same problem). I recently installed VMware on one of my spare machines, and will try soon to reproduce the problem from scratch. Eugene
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200806191540.m5JFe4aV087836>