From owner-freebsd-current Sat Oct 2 10:43: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 83EDC1501D for ; Sat, 2 Oct 1999 10:42:48 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id KAA58557; Sat, 2 Oct 1999 10:39:59 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Sat, 2 Oct 1999 10:39:59 -0700 (PDT) From: Doug White To: "Rodney W. Grimes" Cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: new sigset_t and upgrading: a proposal In-Reply-To: <199910021645.JAA30398@gndrsh.dnsmgr.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 2 Oct 1999, Rodney W. Grimes wrote: > > Read my lips: *NEVER* do a 'make world' until you've got a new bootable > > kernel. You can go back to a 'kernel.old' in 5 seconds. Undoing a 'make > > world' because a new kernel doesn't workd is a major drama. > > These folks are 100% correct, some place some where we made a mistake > and are telling users to do things in the wrong order. It might have > even been myself that caused this, I just can't recall when and who > said to build the world before building the kernel. But now looking > at it in hindsight, this is plainly the wrong sequence, and we should > correct that error as soon as possible. What happens if we version-bump the kernel conf files so a new version of config is required? You'd have to hand-build and install config first. Or is this what we want? Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message