From owner-freebsd-current Tue Jan 16 17:11:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from VL-MS-MR003.sc1.videotron.ca (relais.videotron.ca [24.201.245.36]) by hub.freebsd.org (Postfix) with ESMTP id 8CD1D37B69C for ; Tue, 16 Jan 2001 17:11:12 -0800 (PST) Received: from jehovah ([24.201.144.31]) by VL-MS-MR003.sc1.videotron.ca (Netscape Messaging Server 4.15) with SMTP id G7A8MN00.I8A; Tue, 16 Jan 2001 20:11:11 -0500 Message-ID: <00b001c08022$95a18d90$1f90c918@jehovah> From: "Bosko Milekic" To: "Peter Wemm" , "Warner Losh" Cc: References: <200101160947.f0G9lKs11014@mobile.wemm.org> <200101161813.f0GIDFs29904@harmony.village.org> Subject: Re: HEADS UP: I386_CPU Date: Tue, 16 Jan 2001 20:12:39 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm sorry guys, I haven't been really "up-to-date" on this thread, but I was wondering: can config be made to define I386_CPU 0 if any other cpus are defined (or the inverse behavior)? (Maybe this was already done?) In the sysinstall case, I think it's safe to just exclude all other processors and use the slower I386_CPU kernel. Since the GENERIC kernel config file may contain all of the different CPU types, the config hack may ensure that we're excluding I386_CPU code. Cheers, Bosko. Warner wrote: > In message <200101160947.f0G9lKs11014@mobile.wemm.org> Peter Wemm writes: > : I've requested a change for UPDATING: > > It is in my queue... I have a few other entries I need to dust off. > I'll try to do that today. > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message