From owner-freebsd-stable Wed Jul 10 15:45: 8 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 EF4B237B401; Wed, 10 Jul 2002 15:45:03 -0700 (PDT) Received: from mrburns.nildram.co.uk (mrburns.nildram.co.uk [195.112.4.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF30A43E54; Wed, 10 Jul 2002 15:45:01 -0700 (PDT) (envelope-from muttley@gotadsl.co.uk) Received: from VicNBob (muttley.gotadsl.co.uk [213.208.123.26]) by mrburns.nildram.co.uk (Postfix) with SMTP id CF2A91E1B4A; Wed, 10 Jul 2002 23:44:54 +0100 (BST) From: Matthew Whelan To: "Andrew P. Lentvorski" , Doug Barton Cc: Helge Oldach , Jay Sachs , stanb@awod.com, freebsd-stable@FreeBSD.ORG, des@FreeBSD.ORG Date: Wed, 10 Jul 2002 23:44:59 +0100 X-Priority: 3 (Normal) In-Reply-To: <20020709231825.L5990-100000@master.gorean.org> Message-Id: <085ZD83DCOI01WSJ4ZGFURN87PJ.3d2cb8eb@VicNBob> Subject: Re: ssh to remote machines problem after cvsup MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Mailer: Opera 6.0 build 1010 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 10/07/2002 07:23:43, Doug Barton wrote: >the distinction that you are failing to make is that there are many >different kinds of "changes" to the system. Changes that improve a driver, >changes that update systems like sendmail, even when they require some >small config changes, are candidates for -stable. Changes like this that >have serious potential for causing major problems, AS HAS ALREADY BEEN >DEMONSTRATED; are not. Most people seem to feel that if you were adding ssh a-fresh now, you'd add it with 2,1 not 1,2. UPDATING clearly flags the change. You only get bitten if you remote upgrade without first understanding the significance of the changes from your current version of the O/S. Why do we even have an UPDATING if you're going to preclude making changes that bite people who are unaware of the details it lays out? And yes I understand people installing releases might not read UPDATING, but they really should be reading the release notes, which have also been updated. The number of people asking for help on this issue on -stable has been relatively low, and some of them were in the window between the initial commit and the current version of the UPDATING text so were bitten by a lack of documentation that has since been rectified. How much are you going to hold back developement on the chance that people doing stupid things get hurt? Are you going to remove fdisk because it has the potential to trash a hard disc? Matthew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message