From owner-freebsd-questions Wed Feb 26 7: 0:33 2003 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 1CA8137B401 for ; Wed, 26 Feb 2003 07:00:31 -0800 (PST) Received: from apollo.laserfence.net (apollo.laserfence.net [196.44.69.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD96143F93 for ; Wed, 26 Feb 2003 07:00:26 -0800 (PST) (envelope-from will@unfoldings.net) Received: from localhost ([127.0.0.1]) by apollo.laserfence.net with esmtp (Exim 4.10) id 18o32e-0001uc-00; Wed, 26 Feb 2003 17:00:16 +0200 Received: from prometheus-p0.datel.laserfence.net ([192.168.255.1] helo=prometheus.home.laserfence.net) by apollo.laserfence.net with esmtp (Exim 4.10) id 18o32M-0001u1-00; Wed, 26 Feb 2003 16:59:59 +0200 Received: from phoenix.home.laserfence.net ([192.168.0.2]) by prometheus.home.laserfence.net with esmtp (Exim 4.10) id 18o32I-0006xS-00; Wed, 26 Feb 2003 16:59:54 +0200 Received: from will by phoenix.home.laserfence.net with local (Exim 4.10) id 18o32H-0005HH-00; Wed, 26 Feb 2003 16:59:53 +0200 From: Willie Viljoen To: dan@slightlystrange.org, "freebsd-questions@FreeBSD.ORG " Subject: Re: 4.7 Upgrade issue Date: Wed, 26 Feb 2003 16:59:53 +0200 User-Agent: KMail/1.5 References: <20030226144352.5202D43FBD@mx1.FreeBSD.org> <20030226145024.GE55640@catflap.home.slightlystrange.org> In-Reply-To: <20030226145024.GE55640@catflap.home.slightlystrange.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200302261659.53407.will@unfoldings.net> X-Spam-Score: (/) X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/) *18o32M-0001u1-00*MTBNoTmtZaA* X-Virus-Scanned: by AMaViS snapshot-20020422 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wednesday 26 February 2003 16:50, someone, possibly Daniel Bye, typed: > Yes, but how is that so different from installing a new world for an old > kernel? The problem with a new world on an old kernel is that libraries in your world may have changed with the upgrade. If a library that interfaces directly with some feature in the kernel is changed, and is expecting the change to be present in the kernel, you will almost certainly have trouble with it. > When you have built a new kernel, you must reboot to start using it. > After running make installworld with the new kernel, you have the new > world installed as well. Your new kernel will only be running for a few > minutes with the old world, until the new one is fully installed. That is exactly how it should be. The tried and trusted method, that works for me, and is the official method listed in the UPDATING file: cd /usr/src/sys/i386/conf && vi YOURCONFIG cd /usr/src/ && make buildworld kernel KERNCONF=YOURCONFIG The kernel target is a combination of buildkernel and installkernel. These targets are built in order and rely on the previous target making it. Thus, buildworld must succeed for buildkernel to begin, and after buildkernel has worked, installkernel will run. Once this is completed, continue with: shutdown now You will now have dropped to single user mode, then, pick /bin/sh for your shell (this is easier to use in single user than csh), and run: cd /usr/src mergemaster -p make installworld mergemaster reboot You will now have a properly functioning and fully upgraded system. Will -- Willie Viljoen Freelance IT Consultant 214 Paul Kruger Avenue, Universitas Bloemfontein 9321 South Africa +27 51 522 15 60 +27 51 522 44 36 (after hours) +27 82 404 03 27 (mobile) will@unfoldings.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message