Date: Mon, 9 Aug 2004 10:38:14 -0700 From: John-Mark Gurney <gurney_j@resnet.uoregon.edu> To: Pawel Jakub Dawidek <pjd@FreeBSD.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/boot/common help.common src/sys/boot/forth loader.conf Message-ID: <20040809173814.GG991@funkthat.com> In-Reply-To: <20040809124153.GN628@darkness.comp.waw.pl> References: <200408061506.i76F66sl018247@repoman.freebsd.org> <20040809124153.GN628@darkness.comp.waw.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040809173814.GG991>