From owner-freebsd-current@FreeBSD.ORG Tue Jul 13 19:09:59 2004 Return-Path: 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 621F716A4CE for ; Tue, 13 Jul 2004 19:09:59 +0000 (GMT) Received: from serv01.divms.uiowa.edu (serv01.divms.uiowa.edu [128.255.44.134]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A2B043D39 for ; Tue, 13 Jul 2004 19:09:59 +0000 (GMT) (envelope-from jason-dusek@uiowa.edu) Received: from [128.255.35.104] ([128.255.35.104]) by serv01.divms.uiowa.edu with id i6DJ9nGW022679; Tue, 13 Jul 2004 14:09:49 -0500 (CDT) Message-ID: <40F433E4.2090001@uiowa.edu> Date: Tue, 13 Jul 2004 14:11:32 -0500 From: Jason Dusek User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040706 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Barney Wolff , current@freebsd.org References: <20040713182351.GA72492@pit.databus.com> <22138.1089743312@critter.freebsd.dk> <20040713185200.GA74359@pit.databus.com> In-Reply-To: <20040713185200.GA74359@pit.databus.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.9 () BAYES_00 X-Scanned-By: MIMEDefang 2.43 Subject: Re: CVSUP and 5.2.1 RELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jul 2004 19:09:59 -0000 Well, my system is fine actually. I am running GNOME and Mozilla on it right now. I think the only *good* solution to hosing one's system is to insist on having two bootable partitions - an 'old' one and a 'test' one. They would have everything but /usr and /home in them. Then have a 'make everything-and-i-mean-everything' target that mounts the test partition as /test, and puts the new system - kernel and all - into it. When you reboot, use the test kernel and system. If they work, then run 'make update', which causes the test system to mount the other partition and simpy copy itself over. Then you wouldn't find yourself in the situation of not knowing whether your kernel works till it doesn't. And you could run a sort of 'make everything-and-i-mean-everything' tinderbox in the /test partition. If CURRENT was really sucking one day, you just try again next week. My two cents, - Jason Barney Wolff wrote: > On Tue, Jul 13, 2004 at 08:28:32PM +0200, Poul-Henning Kamp wrote: > >>In message <20040713182351.GA72492@pit.databus.com>, Barney Wolff writes: >> >>>On Tue, Jul 13, 2004 at 01:05:45PM -0500, Jason Dusek wrote: >>> >>>>I ran make world this morning. I ran make kernel as well, but the kernel is >>>>broken, so I kept my old kernel. Does this mean that I have a RELEASE >>>>kernel but a CURRENT world? Am I headed for trouble? >>> >>>To core: >>>How many users do we have to sabotage with "make world" before it gets >>>removed from the make targets? Is it really that hard in the very rare >>>case when "make buildworld && make installworld" is what's wanted to >>>type exactly that? >> >>And your argument here is that people are reciprocally less likely >>to hose (or as it may be: not hose) their systems because the have >>to type 27 characters more to do so ? > > > Yes. That's why there are safeties on guns. Or, since I'm using US > metaphors, "make world" could be considered an attractive nuisance, > like an unfenced swimming pool. >