From owner-freebsd-questions@FreeBSD.ORG Sat Sep 16 04:51:09 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC2E216A47C for ; Sat, 16 Sep 2006 04:51:09 +0000 (UTC) (envelope-from henry.lenzi@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86BD943D53 for ; Sat, 16 Sep 2006 04:51:08 +0000 (GMT) (envelope-from henry.lenzi@gmail.com) Received: by nf-out-0910.google.com with SMTP id n29so2529355nfc for ; Fri, 15 Sep 2006 21:51:07 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=OJaCbGehfB3XYJvqJAEbCsRVN9psaxQvQfHQxTk18cu5lk7B/8HhVz3GIPYXYvIXp4Nnm7B8q1fevGmPGSzDrJdDYWTtbu4Njk3PBkplvXtVYq9XnuyiZwHp6Jg+ya+w6gVPkOABacRU6V5XyXU1VNuOj1a0GWn5PA2SfqEdRes= Received: by 10.78.204.7 with SMTP id b7mr2186659hug; Fri, 15 Sep 2006 21:51:06 -0700 (PDT) Received: by 10.78.141.6 with HTTP; Fri, 15 Sep 2006 21:51:06 -0700 (PDT) Message-ID: <8b4c81f0609152151y5c6a1851n5d53514c670be54f@mail.gmail.com> Date: Sat, 16 Sep 2006 01:51:06 -0300 From: "Henry Lenzi" To: freebsd-questions@freebsd.org In-Reply-To: <20060915164046.GN11663@tigger.digitaltorque.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200609150147.k8F1l73F029577@banyan.cs.ait.ac.th> <450A0E7F.5090400@voidcaptain.com> <20060915164046.GN11663@tigger.digitaltorque.ca> Subject: Re: Poutupgrade unsafe X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Sep 2006 04:51:09 -0000 > A nice portupgrade feature would be to grok UPDATING, and present you with any > such notes before the upgrade occurs. > > Mike I fully agree. It's not the best solution to have an UPDATE file that is very large and that is not integrated in the updating process. UPDATE should be machine-readable, for starters. Henry