From owner-freebsd-stable@FreeBSD.ORG Fri Jun 1 11:09:53 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2B9D81065675 for ; Fri, 1 Jun 2012 11:09:53 +0000 (UTC) (envelope-from adams-freebsd@ateamsystems.com) Received: from fss.sandiego.ateamservers.com (fss.sandiego.ateamservers.com [69.55.229.149]) by mx1.freebsd.org (Postfix) with ESMTP id 0B9E38FC12 for ; Fri, 1 Jun 2012 11:09:52 +0000 (UTC) Received: from [192.168.15.220] (unknown [118.175.84.92]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by fss.sandiego.ateamservers.com (Postfix) with ESMTPSA id B0A8EB9F22; Fri, 1 Jun 2012 07:09:51 -0400 (EDT) Message-ID: <4FC8A303.1040906@ateamsystems.com> Date: Fri, 01 Jun 2012 18:09:55 +0700 From: Adam Strohl Organization: A-Team Systems User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Jason Leschnik References: <4FC779C0.7020801@ohlste.in> <4FC77EAD.1090900@my.gd> <4FC78A94.8070008@ohlste.in> <4FC79136.6000205@my.gd> <4FC7B4CC.1070507@FreeBSD.org> <4FC87A60.3020102@my.gd> <4FC88827.8020003@FreeBSD.org> <4FC89726.2010601@lavabit.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Cc: Katinka , freebsd-stable@freebsd.org Subject: Re: Why Are You Using FreeBSD? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jun 2012 11:09:53 -0000 On 6/1/2012 18:03, Jason Leschnik wrote: > I may be totally incorrect with my above ideas, but it's what i would > like to see from FreeBSD *again*... This is the reason in the first > place most people used FreeBSD, stability/scalability/performance are > the hallmarks of FreeBSD. If we have these hard hitting numbers > released frequently it gives the dev team a good indication of how > changes reflect on performance. This is a good point and the kind of stuff that would make a, for=20 example, great Slashdot post once finished. Of course there would be arguments but I think it would be good=20 exposure. It certainly would be nice to have a place to point to these=20 things vs. just saying "its more better and stabler", too. And if its=20 not at least its acknowledged so it can be fixed.