From owner-freebsd-stable Wed Jul 10 19:39:50 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E17537B405 for ; Wed, 10 Jul 2002 19:39:44 -0700 (PDT) Received: from mail7.nc.rr.com (mail7.southeast.rr.com [24.93.67.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82C0643E64 for ; Wed, 10 Jul 2002 19:39:43 -0700 (PDT) (envelope-from bts@babbleon.org) Received: from i8k.babbleon.org ([66.57.86.84]) by mail7.nc.rr.com with Microsoft SMTPSVC(5.5.1877.757.75); Wed, 10 Jul 2002 22:39:32 -0400 Received: by i8k.babbleon.org (Postfix, from userid 111) id 1F72EBA05; Wed, 10 Jul 2002 22:39:25 -0400 (EDT) Content-Type: text/plain; charset="iso-8859-1" From: Brian T.Schellenberger To: bjones@polestar.org, Mike Tancsa Subject: Re: strange ATA behavior with -STABLE Date: Wed, 10 Jul 2002 22:39:24 -0400 X-Mailer: KMail [version 1.3] Cc: stable@FreeBSD.ORG References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020711023925.1F72EBA05@i8k.babbleon.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wednesday 10 July 2002 01:50 pm, Bill Jones wrote: | mike@sentex.net wrote: | >>If we're so willing | >>to make FreeBSD work on laptops, then we should at least give a | | concerned | | >>nod to the most common disk system in average installation. | > | >Most common what ? Legacy system ? Most common out there today | | ? Most | | >common platform someone installs FreeBSD on for the first time | | ? The ata | | >drivers are most certainly broken for some people. Prior to big | | changes | | >Soren made, the ata drivers were most certainly broken for some | >people. Remember when the big round of commits went in last time | | (wd to | | >ad), it broke support for certain old CMD based controllers. | | The obvious answer to me is "Most common platform someone installs | FreeBSD on for the first time." But the new drivers probably support more first-time installs than the old one does. I know that it corrected multiple problems for me. I *am* running on a laptop, though. OTOH, that's sure getting to be more common rather than less over time. The *problem* is that it also broke some old hardware that previously worked. If you agree that the most important is what will work for most *new* installs, I believe that you are probably arguing the wrong side of the issue, or at the very least it's not clear what the right side of the issue would be. If you want to argue that the commit was a bad idea, then you'd have a much stronger case by arguing that FreeBSD shouldn't break what previously worked so that people aren't afraid to upgrade. | All I am simply trying to say is that version 4.6.1 will be minted | to CD and sold through the various outlets that market it. It would | behoove the FreeBSD community greatly if this version of FreeBSD | works out of the box and without need to immediately CVSup on a majority | of systems out there. This means it should install and run without | these errors on both a 128meg system with 80+ gig IDE hard drives | (pretty common at most retailers) and on an older system with 32meg | and 6gig IDE hard drives (a common "older computer"). | | If FreeBSD errors during installation or in the first few days of | operation for a new user, it is likely that person will select another | OS rather than searching the mailing list and website for fixes. | | | Working "out of the box" is good for future growth of FreeBSD. Failing | "out of the box" will have a negative impact. Personally, I'd prefer | growth. | | | | | | | | | To Unsubscribe: send mail to majordomo@FreeBSD.org | with "unsubscribe freebsd-stable" in the body of the message -- Brian, the man from Babble-On . . . . bts@babbleon.org (personal) http://www.babbleon.org http://www.eff.org http://www.programming-freedom.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message