Date: Sat, 19 Apr 2003 11:34:36 -0400 From: Mike Barcroft <mike@FreeBSD.org> To: Bruce Evans <bde@zeta.org.au> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: config(8) should check if a scheduler is selected Message-ID: <20030419113436.C8793@espresso.bsdmike.org> In-Reply-To: <20030419165033.V15269@gamplex.bde.org>; from bde@zeta.org.au on Sat, Apr 19, 2003 at 05:17:02PM %2B1000 References: <200304182047.h3IKlhIZ000817@number6.magda.ca> <20030418214702.GA98907@rot13.obsecurity.org> <20030419165033.V15269@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Bruce Evans <bde@zeta.org.au> writes: > On Fri, 18 Apr 2003, Kris Kennaway wrote: > > > On Fri, Apr 18, 2003 at 04:47:43PM -0400, David Magda wrote: > > > > > If you run config(8) on a kernel configuration file which doesn't > > > have a scheduler selected then it does *NOT* complain. > > > > How is this different to any of the other mandatory kernel components > > or dependencies? You can build a kernel that will refuse to link in > > many ways; missing a scheduler is just a new mistake you might make if > > you forget to read /usr/src/UPDATING. > > It is the only mandatory option (sic). Kernels with no options (although > they might not be useful) can be built except for this bug. Example of > a minimal config file (before misconfiguration of the configuration of > scheduling). > > %%% > machine i386 > cpu I686_CPU > ident MIN > %%% > > BTW, a minimal kernel is now almost 3 times as large as in FreeBSD-2 due > to general bloat and misconfiguration of configuration in the opposite > way (subsystems much larger than scheduling are standard; you can still > leave out FFS and INET but many less useful subsystems are standard). Since all `options' are optional, maybe `sched' should be its own directive with two possible values: `4BSD' or `ULE'. Best regards, Mike Barcroft
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030419113436.C8793>