Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 25 Nov 2011 11:43:26 +0000
From:      Alexander Best <>
To:        Thomas Mueller <>
Cc:, "b. f." <>
Subject:   Re: Quick build of stripped-down kernel
Message-ID:  <>
In-Reply-To: <>
References:  <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Fri Nov 25 11, Thomas Mueller wrote:
> from "b. f." <>:
> > If you are going to build most of the modules, but only want to
> > exclude a few, then add the directories of the modules to be excluded
> > (relative to /usr/src/sys/modules) to WITHOUT_MODULES, for example in
> > /etc/make.conf. If you are only going to build a few modules, and want
> > to exclude the majority of the modules, then add the directories of
> > the modules that are to be built to MODULES_OVERRIDE.  For no modules
> > at all, set NO_MODULES.  See /usr/src/sys/modules/Makefile and
> > /usr/src/sys/conf/ for details. You may also save some
> > time by using one of your faster machines to build the OS for the
> > slower machines.
> Suppose you want to build more than one kernel so as to be able to choose at boot time.
> Then you might not want to build modules redundantly.  So how would you make the modules from /boot/kernel accessible when booting /boot/kernel2?

irrc there was a patch posted on some of the mailinglists not a long time ago,
which added support for building only those modules, which aren't part of the
kernel. this might be a good alternative, if you want a small footprint, but
want to take advantage of all the freebsd kernel drivers/etc.


> Tom

Want to link to this message? Use this URL: <>