From owner-freebsd-arch Tue Jul 18 9:32:31 2000 Delivered-To: freebsd-arch@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 7747037BEEA for ; Tue, 18 Jul 2000 09:32:29 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id 13FEB18C0; Tue, 18 Jul 2000 09:32:28 -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 JAA17075; Tue, 18 Jul 2000 09:32:26 -0700 (PDT) Message-ID: <3974869B.22E7924@cup.hp.com> Date: Tue, 18 Jul 2000 09:32:27 -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: Sheldon Hearn Cc: arch@FreeBSD.ORG Subject: Re: Multiple kernels / module search path References: <49681.963925937@axl.ops.uunet.co.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > On Mon, 17 Jul 2000 22:09:44 MST, Marcel Moolenaar wrote: > > > Question 3: Should we change the order in which modules are searched to > > /modules{.NAME}:/boot:/, where {.NAME} denotes the optional name suffix. > > I really don't think that this is the way to go. A module should be a > module should be a module. That's certainly where we're headed, right? Building the modules as part of the kernel seems like a step away from it, because if modules are modules are modules, we could build them as part of world as we used to do and avoid building and rebuilding modules with every kernel we're building. But building modules as part of the world resulted in kernel and modules to be out of sync. We all know what that means :-) We currently don't have the interfaces to make that happen (modules being modules that is). This implies that different installed kernels can not always share the same /modules directory. This is especially true during an upgrade, when the new kernel will be version V.x and the old kernel will be version (V-1).y. If we don't have a seperate /modules directory for the old kernel, we still have the "out-of-sync" problem. -- 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