Date: Tue, 18 Jul 2000 21:28:30 -0600 From: Warner Losh <imp@village.org> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: Marcel Moolenaar <marcel@cup.hp.com>, arch@FreeBSD.ORG Subject: Re: Multiple kernels / module search path Message-ID: <200007190328.VAA76993@harmony.village.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200007190328.VAA76993>