From owner-freebsd-arch Tue Jul 18 20:28:43 2000 Delivered-To: freebsd-arch@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B1BDD37BB11 for ; Tue, 18 Jul 2000 20:28:40 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA89252; Tue, 18 Jul 2000 21:28:39 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA76993; Tue, 18 Jul 2000 21:28:30 -0600 (MDT) Message-Id: <200007190328.VAA76993@harmony.village.org> To: Brooks Davis Subject: Re: Multiple kernels / module search path Cc: Marcel Moolenaar , arch@FreeBSD.ORG In-reply-to: Your message of "Mon, 17 Jul 2000 23:03:51 PDT." <20000717230351.C6353@orion.ac.hmc.edu> References: <20000717230351.C6353@orion.ac.hmc.edu> <3973E698.B8D53F1F@cup.hp.com> Date: Tue, 18 Jul 2000 21:28:30 -0600 From: Warner Losh Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000717230351.C6353@orion.ac.hmc.edu> Brooks Davis writes: : 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. I don't think that we want to autmoatically do this. modules need to be verified as working with a given kernel before we go start and loading them automatically... I'm not saying, btw, that a user shouldn't be allowed to setup the search path with /modules in it, but it should be explicit, not implicit. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message