From owner-freebsd-stable@FreeBSD.ORG Tue Apr 25 21:50:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 1552716A440; Tue, 25 Apr 2006 21:50:45 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63E7243D66; Tue, 25 Apr 2006 21:50:44 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.6/8.13.1) with ESMTP id k3PLog69021396; Tue, 25 Apr 2006 18:50:42 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR To: freebsd-stable@freebsd.org Date: Tue, 25 Apr 2006 18:50:37 -0300 User-Agent: KMail/1.9.1 References: <20060424181531.GA13774@xor.obsecurity.org> <20060425211417.GA58948@xor.obsecurity.org> <444E96A1.3010307@rogers.com> In-Reply-To: <444E96A1.3010307@rogers.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200604251850.38063.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on msrv.matik.com.br X-Virus-Status: Clean Cc: Mike Jakubik , stable@freebsd.org, re@freebsd.org, Dmitry Morozovsky , Kris Kennaway Subject: Re: fsck_ufs locked in snaplk 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: Tue, 25 Apr 2006 21:50:46 -0000 On Tuesday 25 April 2006 18:37, Mike Jakubik wrote: > Kris Kennaway wrote: > > This is true, but I hope you recognise that a good part of the > > responsibility for this falls on the users when asked to test proposed > > fixes. If the developers are not aware of remaining problems they > > can't reasonably be expected to fix them :-) > > Indeed, but the developers should also realize that a lot of users have > servers in production and can not afford the downtime, or simply don't > have the resources to test. I think the developers should also spend a > little more time doing more extensive testing of their own code. > what do you think about you to test before putting "something|anything" int= o=20 production? Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br