From owner-freebsd-arch Tue Jul 18 9:24:41 2000 Delivered-To: freebsd-arch@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 1506437BDB8 for ; Tue, 18 Jul 2000 09:24:40 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id 527E710DF; Tue, 18 Jul 2000 09:20:43 -0700 (PDT) Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.02) with ESMTP id JAA16655; Tue, 18 Jul 2000 09:20:39 -0700 (PDT) Message-ID: <397483D7.DFEC9BBC@cup.hp.com> Date: Tue, 18 Jul 2000 09:20:39 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Brooks Davis Cc: arch@FreeBSD.ORG Subject: Re: Multiple kernels / module search path References: <3973E698.B8D53F1F@cup.hp.com> <20000717230351.C6353@orion.ac.hmc.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brooks Davis wrote: > > On Mon, Jul 17, 2000 at 10:09:44PM -0700, Marcel Moolenaar wrote: > > Question 4: Do we want /modules in the search for kernels with a > > non-zero name so that the search path will be > > /modules.NAME:/modules:/boot:/ > > I agree with you except here (and you may be able to find a solution > here.) My problem with not doing this is that ports and third party > software that creates modules (vmware, etc) needs a place to put them, > and currently that's modules. While you could put them in /boot, that > seems ugly at best. Otherwise, I like ideas very much. I've been > wanting to build and install my custom kernel and GENERIC in one fell > swoop since {build|install}kernel was added. The problem is with versioning. If I add 3rd party module foo.ko to modules, while it actually is a module for kernel 'kernel.bar' *and* kernel and kernel.bar are sufficiently incompatible, then kernel won't boot (for example) if the module is loaded at boot time. Or, if kernel.bar is booted and I want to load foo.ko, I might pick up the version from /modules if I don't happen to have a foo.ko in /modules.bar, which may be sufficiently incompatible and cause a kernel panic. -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message