From owner-freebsd-arch Thu Nov 30 15:29:28 2000 Delivered-To: freebsd-arch@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 368DF37B400; Thu, 30 Nov 2000 15:29:23 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_18979)/8.9.3) with ESMTP id KAA21472; Fri, 1 Dec 2000 10:29:19 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01JX6QHY1B00EAF49C@cim.alcatel.com.au>; Fri, 1 Dec 2000 10:29:17 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.0/8.11.0) id eAUNTF802533; Fri, 01 Dec 2000 10:29:15 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Fri, 01 Dec 2000 10:29:15 +1100 From: Peter Jeremy Subject: Re: RANDOMDEV inspired realitycheck regarding i386/i486... In-reply-to: <11485.974210886@critter>; from phk@FreeBSD.ORG on Tue, Nov 14, 2000 at 03:08:06PM +0100 To: Poul-Henning Kamp Cc: arch@FreeBSD.ORG Mail-followup-to: Poul-Henning Kamp , arch@FreeBSD.ORG Message-id: <20001201102915.G1474@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <11485.974210886@critter> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Nov-14 15:08:06 +0100, Poul-Henning Kamp wrote: >Has anybody run a 486 or 386 under current recently ? X on a PRE_SMPNG 486 is painful - mouse movements no longer make the X pointer move in real time. I haven't noticed the seeding issue (probably just luck). >What is the consensus ? I think 386/486 remains a significant market and would not like to see support dropped. I'd go so far as to suggest that if -current does drop support for the 386/486, the then-stable version will need to be actively maintained indefinitely to provide continued support. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message