From owner-freebsd-arch Mon Jul 17 23:14:19 2000 Delivered-To: freebsd-arch@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 8FAA937B6BF for ; Mon, 17 Jul 2000 23:14:17 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id XAA09376; Mon, 17 Jul 2000 23:03:51 -0700 (PDT) Date: Mon, 17 Jul 2000 23:03:51 -0700 From: Brooks Davis To: Marcel Moolenaar Cc: arch@FreeBSD.ORG Subject: Re: Multiple kernels / module search path Message-ID: <20000717230351.C6353@orion.ac.hmc.edu> References: <3973E698.B8D53F1F@cup.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <3973E698.B8D53F1F@cup.hp.com>; from marcel@cup.hp.com on Mon, Jul 17, 2000 at 10:09:44PM -0700 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message