From owner-freebsd-current Thu Oct 10 1:33:39 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 8BC0E37B401 for ; Thu, 10 Oct 2002 01:33:37 -0700 (PDT) Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1CDB43EAC for ; Thu, 10 Oct 2002 01:33:36 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0055.cvx40-bradley.dialup.earthlink.net ([216.244.42.55] helo=mindspring.com) by albatross.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 17zYl8-0007bx-00; Thu, 10 Oct 2002 01:33:30 -0700 Message-ID: <3DA53B12.836E1249@mindspring.com> Date: Thu, 10 Oct 2002 01:32:18 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: "M. Warner Losh" , 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> <3DA50A3B.6E0521E6@mindspring.com> <20021010073304.GE99645@starjuice.net> 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 Sheldon Hearn wrote: > On (2002/10/09 22:03), Terry Lambert wrote: > > 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. > > Why not just let Warner (or whoever) make this "solution" available and > see how it flies? It was discussed already, the last 3 times this topic came up. I believe that the only inoffensive thing that everyone could agree to was: "do it however you want, as long as it requires a special (non-default) target to make it do its thing". No one wanted a "make install" or "make installworld" or whatever deleting things, especially if it failed. > People like you and me who have our own simple and effective ways of > pruning stale files can just ignore it or hack it out. I do it manually, just like everyone else. Normally, I build a world, mount the image read-only, and do a full install onto a "pingpong" partition via NFS, which buys me a clean install, and the ability to go back to the previous root partition, if the new image is too broken to use. I used to have an extra target for "/bin/sysinstall" to be created on the CDROM image, so that I could do a full upgrade via NFS from a CDROM image (instead of booting from one, particularly on machines that didn't netboot and had no CDROM -- read: appliances), but that doesn't work if you have to actually delete files for things to not break on you (the source of the current controversy: "stale" files not removed). Personally, I have absolutley no objection to a mtree "stale file" removal script. I just think it will be nearly impossible to maintain... and if it's not active by default, it's not going to stop the people who post about problems, especially problems with ports. And since it *can't* be active by default... catch-22. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message