cvs commit: src/sys/boot/common help.common src/sys/boot/forth loader.conf

[Pawel Jakub Dawidek]

On Mon, Aug 09, 2004 at 10:38:14AM -0700, John-Mark Gurney wrote:
+> Pawel Jakub Dawidek wrote this message on Mon, Aug 09, 2004 at 14:41 +0200:
+> > If kernel name is given for the 'boot' command, '/boot/<kernname>' path is
+> > probably added to kern.module_path, but for normal boot process it is not,
+> > so kern.module_path is set only to "/boot/modules".
+> > Some applications depend on this sysctl and they don't work properly now.
+> > Please fix.
+> 
+> Have you verified this is a problem?  On my test box that has:
+> defaults/loader.conf:module_path="/boot/modules"        # Set the module search path
+> 
+> and was booted:
+> [...]
+> /boot/kernel/accf_http.ko text=0xb84 data=0x150+0x4 syms=[0x4+0x310+0x4+0x334]
+> 
+> Hit [Enter] to boot immediately, or any other key for command prompt.
+> Booting [/boot/kernel/kernel]...               
+> 
+> (i.e. normal boot process w/ no interaction)
+> 
+> My sysctl returns:
+> -bash-2.05b$ sysctl kern.module_path
+> kern.module_path: /boot/kernel;/boot/modules
+> 
+> Please include complete information of the breakage that this change
+> is suppose to cause.

I've just checked on the next machine (this is 3rd machine) and it doesn't
put '/boot/kernel' into 'kern.module_path' sysctl. That's why kldload(8)
cannot work properly.

The only difference that I'm seeing between our environments is that I use
new loader (with beastie picture) everywhere and you don't use it, right?

-- 
Pawel Jakub Dawidek                       http://www.FreeBSD.org
pjd at FreeBSD.org                           http://garage.freebsd.pl
FreeBSD committer                         Am I Evil? Yes, I Am!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/cvs-src/attachments/20040810/cbbe89d5/attachment.bin