From owner-freebsd-arch@FreeBSD.ORG Sat Apr 19 10:49:30 2003 Return-Path: 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 09EE937B401; Sat, 19 Apr 2003 10:49:30 -0700 (PDT) Received: from bluejay.mail.pas.earthlink.net (bluejay.mail.pas.earthlink.net [207.217.120.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AC1243F3F; Sat, 19 Apr 2003 10:49:29 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0234.cvx22-bradley.dialup.earthlink.net ([209.179.198.234] helo=mindspring.com) by bluejay.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 196wSr-0007TC-00; Sat, 19 Apr 2003 10:49:26 -0700 Message-ID: <3EA18BD4.5E21C678@mindspring.com> Date: Sat, 19 Apr 2003 10:48:04 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Evans References: <200304182047.h3IKlhIZ000817@number6.magda.ca> <20030419165033.V15269@gamplex.bde.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4b7bbce3e6de443404300eea9bdaf7d28387f7b89c61deb1d350badd9bab72f9c350badd9bab72f9c cc: arch@freebsd.org cc: jeff@freebsd.org cc: David Magda cc: Kris Kennaway 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Apr 2003 17:49:30 -0000 Bruce Evans wrote: > 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). Make the scheduler code stop moving for a good week, and I am willing to fix this with linker sets and an opaque indirection interface. It won't fix the primary problem of coexistance, at least up front, but it could allow you to select your scheduler in loader.conf (-current should remain buildable and runnable in that same week, of course). -- Terry