Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 10 Aug 2004 12:30:07 +0200
From:      Pawel Jakub Dawidek <pjd@FreeBSD.org>
To:        John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Cc:        cvs-all@FreeBSD.org
Subject:   Re: cvs commit: src/sys/boot/common help.common src/sys/boot/forth loader.conf
Message-ID:  <20040810103007.GB30151@darkness.comp.waw.pl>
In-Reply-To: <20040809173814.GG991@funkthat.com>
References:  <200408061506.i76F66sl018247@repoman.freebsd.org> <20040809124153.GN628@darkness.comp.waw.pl> <20040809173814.GG991@funkthat.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--neYutvxvOLaeuPCA
Content-Type: text/plain; charset=iso-8859-2
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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 +02=
00:
+> > If kernel name is given for the 'boot' command, '/boot/<kernname>' pat=
h 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 n=
ow.
+> > Please fix.
+>=20
+> Have you verified this is a problem?  On my test box that has:
+> defaults/loader.conf:module_path=3D"/boot/modules"        # Set the modu=
le search path
+>=20
+> and was booted:
+> [...]
+> /boot/kernel/accf_http.ko text=3D0xb84 data=3D0x150+0x4 syms=3D[0x4+0x31=
0+0x4+0x334]
+>=20
+> Hit [Enter] to boot immediately, or any other key for command prompt.
+> Booting [/boot/kernel/kernel]...              =20
+>=20
+> (i.e. normal boot process w/ no interaction)
+>=20
+> My sysctl returns:
+> -bash-2.05b$ sysctl kern.module_path
+> kern.module_path: /boot/kernel;/boot/modules
+>=20
+> 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?

--=20
Pawel Jakub Dawidek                       http://www.FreeBSD.org
pjd@FreeBSD.org                           http://garage.freebsd.pl
FreeBSD committer                         Am I Evil? Yes, I Am!

--neYutvxvOLaeuPCA
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFBGKOvForvXbEpPzQRAtL7AKCreKy85rt+gk5RUggrKT+NymwhlQCgjFtU
U8jyjuDIjvjtcKxd0LLK3YU=
=aVkh
-----END PGP SIGNATURE-----

--neYutvxvOLaeuPCA--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040810103007.GB30151>