From owner-cvs-all Sun Jan 14 5:10:50 2001 Delivered-To: cvs-all@freebsd.org Received: from 200-227-201-118-as.acessonet.com.br (200-227-201-118-as.acessonet.com.br [200.227.201.118]) by hub.freebsd.org (Postfix) with ESMTP id 02D2637B404 for ; Sun, 14 Jan 2001 05:10:32 -0800 (PST) Received: (qmail 4831 invoked by uid 1001); 14 Jan 2001 13:10:16 -0000 From: "Mario Sergio Fujikawa Ferreira" Date: Sun, 14 Jan 2001 11:09:54 -0200 To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/conf GENERIC Message-ID: <20010114110954.A3945@Fedaykin.here> References: <28586.979469127@critter> <200101141115.f0EBFBQ89810@mobile.wemm.org> <20010114130017.A1612@student.uu.se> <20010114040933.A35126@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010114040933.A35126@dragon.nuxi.com>; from TrimYourCc@NUXI.com on Sun, Jan 14, 2001 at 04:09:11AM -0800 Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 14, 2001 at 04:09:11AM -0800, David O'Brien wrote: > On Sun, Jan 14, 2001 at 01:00:17PM +0100, Erik Trulsson wrote: > > I don't agree. Removing 386 support from GENERIC I can live with (although I > > don't like it much) but removing 386 support entirely would be a bad idea > > IMNSHO. > > I don't have any experience with -current but -stable works fine on 386 and > > Please try -current on a i386 before voicing an opinion. I don't know > why you think experience with one counts for the other. > > -stable and -current are now very different beasts. > src/release/scripts/dokern.sh (which strips things out of the GENERIC > kernel for the boot floppy) cuts out a lot more on -current than -stable. To voice a different direction on this. I believe that by the time current comes out as release (a year or so), only a few users will say that 386 is a MUST and that it should be maintained. I myself require 386 support for some console terminals at Univ, but aware of the compromise necessary to keep supporting this platform: I would stick with 4.x for this. Just consider the additional number of platforms that will be supported when current comes out: sparc, ... It is only predictable that some oldies will have to be left out; or, otherwise, left in but without maintainance for sheer lack of time. Therefore, as long as the 386 removal is not MFCed into 4.x, I don't mind it at all. Dishing out platforms should be left out as a major number release exercise. However, if leaving this in won't hurt (improvements, performance) and there is ppl available/willing to support it. What is the matter too? :) Just my 2 cents, ps: I'll go back into my hibernation tank, my back hurts. Cya. -- Mario S F Ferreira - UnB - Brazil - "I guess this is a signature." lioux at ( freebsd dot org | linf dot unb dot br ) flames to beloved devnull@someotherworldbeloworabove.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message