From owner-freebsd-arch@FreeBSD.ORG  Sat Apr 19 00:17:20 2003
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id DD72F37B401; Sat, 19 Apr 2003 00:17:20 -0700 (PDT)
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 54BE543F75; Sat, 19 Apr 2003 00:17:19 -0700 (PDT)
	(envelope-from bde@zeta.org.au)
Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246])
	by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id RAA10391;
	Sat, 19 Apr 2003 17:17:03 +1000
Date: Sat, 19 Apr 2003 17:17:02 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender: bde@gamplex.bde.org
To: Kris Kennaway <kris@obsecurity.org>
In-Reply-To: <20030418214702.GA98907@rot13.obsecurity.org>
Message-ID: <20030419165033.V15269@gamplex.bde.org>
References: <200304182047.h3IKlhIZ000817@number6.magda.ca>
 <20030418214702.GA98907@rot13.obsecurity.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: arch@freebsd.org
cc: jeff@freebsd.org
cc: David Magda <dmagda+fbugs@ee.ryerson.ca>
Subject: Re: config(8) should check if a scheduler is selected
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Apr 2003 07:17:21 -0000

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).

Bruce