From owner-freebsd-current Wed Oct 9 22: 5:24 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69A8937B401 for ; Wed, 9 Oct 2002 22:05:23 -0700 (PDT) Received: from conure.mail.pas.earthlink.net (conure.mail.pas.earthlink.net [207.217.120.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0926E43E6A for ; Wed, 9 Oct 2002 22:05:23 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0137.cvx22-bradley.dialup.earthlink.net ([209.179.198.137] helo=mindspring.com) by conure.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17zVVT-00016Q-00; Wed, 09 Oct 2002 22:05:07 -0700 Message-ID: <3DA50A3B.6E0521E6@mindspring.com> Date: Wed, 09 Oct 2002 22:03:55 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "M. Warner Losh" Cc: drosih@rpi.edu, FreeBSD-current@FreeBSD.ORG Subject: Re: Do we still need portmap(8)? References: <200210072127.58523.dzerkel@columbus.rr.com> <3DA498EA.C7BF77A@mindspring.com> <20021009.220112.82861653.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "M. Warner Losh" wrote: > In message: > Garance A Drosihn writes: > : I think most of us realize that we need a solution which can be > : automatically executed as part of every installworld or mergemaster > : run. The debate is over the most reasonable method of doing that. > > My suggestion would work, and would be a viable solution, so far the > only one presented in this whole silly thread. The mtree.obsolete approach is flawed, in that it's a delta without an anchor: it's all fine and good to delete things, when you know that it's a delta from/to. It's less fine, if you don't know where you are coming from. The other problem with an mtree.obsolete is that it assumes the the upgrade process completes successfully. This doesn't mean that it completes without an error in the upgrade process, it means that the resulting system functions. The only safe way to do the delete is as part of a binary upgrade process (if you can't make it reversible, then make it so the forward process can't fail). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message