From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 22 18:22:20 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4000B106568B; Tue, 22 Sep 2009 18:22:20 +0000 (UTC) (envelope-from nate@thatsmathematics.com) Received: from euclid.ucsd.edu (euclid.ucsd.edu [132.239.145.52]) by mx1.freebsd.org (Postfix) with ESMTP id 1CBD38FC12; Tue, 22 Sep 2009 18:22:19 +0000 (UTC) Received: from zeno.ucsd.edu (zeno.ucsd.edu [132.239.145.22]) by euclid.ucsd.edu (8.11.7p3+Sun/8.11.7) with ESMTP id n8MI31o03472; Tue, 22 Sep 2009 11:03:01 -0700 (PDT) Received: from localhost (neldredg@localhost) by zeno.ucsd.edu (8.11.7p3+Sun/8.11.7) with ESMTP id n8MI31a00118; Tue, 22 Sep 2009 11:03:01 -0700 (PDT) X-Authentication-Warning: zeno.ucsd.edu: neldredg owned process doing -bs Date: Tue, 22 Sep 2009 11:03:00 -0700 (PDT) From: Nate Eldredge X-X-Sender: neldredg@zeno.ucsd.edu To: John Baldwin In-Reply-To: <200909221027.48607.jhb@freebsd.org> Message-ID: References: <200909211203.n8LC3hhn090227@fire.js.berklix.net> <200909221027.48607.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Alexey Shuvaev , "Julian H. Stacey" , hackers@freebsd.org Subject: Re: genuine cpu I386_CPU kernel support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2009 18:22:20 -0000 On Tue, 22 Sep 2009, John Baldwin wrote: > My comment is to just use 4.x (seriously). A true 386 is going to be quite > slow and the overhead of many things added that work well on newer processors > is going to be very painful on a 386 (probably on a 486 as well). 4.x runs > fine on a 386 and should support all the hardware you can stick into a > machine with an 80386 CPU. Unless, of course, you plan to put it on a network. I doubt that 4.x is up to date with respect to security patches. -- Nate Eldredge nate@thatsmathematics.com