Date: Wed, 20 Jun 2001 20:01:04 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: John Baldwin <jhb@FreeBSD.ORG> Cc: Terry Lambert <tlambert2@mindspring.com>, arch@FreeBSD.ORG, Peter Pentchev <roam@orbitel.bg>, Nate Williams <nate@yogotech.com> Subject: Re: new kldpath(8): display/modify the module search path Message-ID: <Pine.BSF.4.21.0106201942360.23554-100000@besplex.bde.org> In-Reply-To: <XFMail.010619232327.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 19 Jun 2001, John Baldwin wrote: > On 20-Jun-01 Terry Lambert wrote: > > What is the interaction with /etc/modules.old, when you are > > booting a /kernel.old? > > In -current (which is where kldconfig(8) is going, btw) all modules live with > their correspnding kernel in the same directory under /boot. Thus modules and > kernel are in sync for kernel.old, kernel, and > kernel.fix_it_after_joe_random_committer_broke_it. This means that the existence of a module search path is just a bug. The kernel shouldn't use a search path or add a path prefix for kldload(2) any more than it should for execve(2), but adding a path prefix is necessary for modules loaded directly by the kernel. I used to think that a search path (with one element) was necessary for locating the modules, but now the modules are together with the kernel, the one-element search path can be derived from kernelname[]. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0106201942360.23554-100000>