From owner-freebsd-arch Tue Jun 19 23:26:28 2001 Delivered-To: freebsd-arch@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 4229637B406; Tue, 19 Jun 2001 23:26:21 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.247.138.115.Dial1.SanJose1.Level3.net [209.247.138.115]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id XAA14036; Tue, 19 Jun 2001 23:24:55 -0700 (PDT) Message-ID: <3B3041D7.28CB375E@mindspring.com> Date: Tue, 19 Jun 2001 23:25:27 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Nate Williams Cc: John Baldwin , Peter Pentchev , arch@FreeBSD.ORG, audit@FreeBSD.ORG Subject: Re: new kldpath(8): display/modify the module search path References: <3B2F958E.BC556A1E@mindspring.com> <15151.41572.721434.703837@nomad.yogotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Nate Williams wrote: > > Having to reboot to make things work really, really sucks -- > > and that is often necessary if you build code from the net, > > which FreeBSD has mistakenly included as part os the base > > system monolith. OpenSSL, OpenSSH, and the resolver library > > are three examples that leap lithely to mind. > > Terry, it's simple to not have to reboot. Many ports already > do this, but a 'ldconfig -R' tells it to re-scan the known > directories to pickup new entries, which can be done at any > time (as root of course). It was pointed out that the code just sets a path (or adds to one, which makes the most sense in the case of multiple rc.d's). I still have a small problem with the path setting automating load of things installed in /usr/local (e.g. the vmware modules), since there isn't a "rebuild requirement" for the modules which are not themselves built as part of the kernel build. I also have a slight problem with the module path being capable of being set to include some directory before /modules. What is the interaction with /etc/modules.old, when you are booting a /kernel.old? It seems to me that it would be very easy to boot a /kernel.old, and end up with mismatched modules from an rc file setting the path to /modules instead of /modules.old... This seems like something that should maybe be a sysctl, instead, and have a default behaviour of "append to path" in the rc file implementation, to ensure that the booted kernel and modules directory matched, no matter what kernel you booted. I might even go so far as to say that if a kernel other than /kernel was being booted, that it ought to become read-only, to prevent a mismatched module from being loaded unintentionally... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message