From owner-freebsd-current  Fri Dec  6 20:22:27 1996
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id UAA28214
          for current-outgoing; Fri, 6 Dec 1996 20:22:27 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA28194
          for <current@freebsd.org>; Fri, 6 Dec 1996 20:22:14 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id PAA14363; Sat, 7 Dec 1996 15:19:40 +1100
Date: Sat, 7 Dec 1996 15:19:40 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199612070419.PAA14363@godzilla.zeta.org.au>
To: bde@zeta.org.au, toor@dyson.iquest.net
Subject: Re: 3.0-current Kernel panicking on bootup
Cc: current@freebsd.org, dyson@dyson.iquest.net, markm@iafrica.com
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>> >> I think it needs to be a positive option so that it fails safely.
>> >> 
>> >Okay, then make it conditional on the various processors that support
>> >it?  As opposed to the processor that doesn't?
>> 
>> No.  Many configurations, e.g. GENERIC, have support for all x86 processors.
>> 
>That means that people who run GENERIC won't get the advantage
>of disabling the 386.  So what?

This means that if you make it conditional on the various processors that
support it, then you break GENERIC on i386's.  GENERIC is configured to
support all processors.  If you remove the support for i486's and up from
it then people who run GENERIC will get all the disadvantages of the i386,
e.g., no CR0_WP.

Bruce