From owner-freebsd-current@FreeBSD.ORG Thu May 1 10:39:16 2003 Return-Path: <owner-freebsd-current@FreeBSD.ORG> Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6CC937B401; Thu, 1 May 2003 10:39:16 -0700 (PDT) Received: from kientzle.com (h-66-166-149-50.SNVACAID.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55C9143FBD; Thu, 1 May 2003 10:39:15 -0700 (PDT) (envelope-from kientzle@acm.org) Received: from acm.org (ugly.x.kientzle.com [66.166.149.51]) by kientzle.com (8.11.3/8.11.3) with ESMTP id h41HdEv69281; Thu, 1 May 2003 10:39:14 -0700 (PDT) (envelope-from kientzle@acm.org) Message-ID: <3EB15C12.1020704@acm.org> Date: Thu, 01 May 2003 10:40:34 -0700 From: Tim Kientzle <kientzle@acm.org> User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.6) Gecko/20011206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin <jhb@freebsd.org> References: <XFMail.20030501103729.jhb@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: URGENT HELP REQUIRED X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kientzle@acm.org List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current> List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 01 May 2003 17:39:17 -0000 John Baldwin wrote: > On 30-Apr-2003 Terry Lambert wrote: > >>CARTER Anthony wrote: >>>I was following a post on current when I changed to CPU_TYPE=p4... >> >>Kind of makes you want to check in the Makefile that the CPU_TYPE= >>is less than or equal to the current CPU_TYPE from dmesg, when >>doing an "installworld" target. > > Not appropriate if you are doing an installworld into a NFS-mounted root > directory for a test machine. :) A non-fatal warning might still be a good idea. Given what I've read on this list so far, it might be a good idea to issue a non-fatal warning for setting CPU_TYPE at all. Tim