From owner-freebsd-current@FreeBSD.ORG Tue Nov 25 20:51:19 2003 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 5E6A316A4CE for ; Tue, 25 Nov 2003 20:51:19 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7422443FBF for ; Tue, 25 Nov 2003 20:51:18 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.9/8.12.3) with ESMTP id hAQ4pFbf004281; Tue, 25 Nov 2003 20:51:15 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.9/8.12.3/Submit) id hAQ4pFwr004278; Tue, 25 Nov 2003 20:51:15 -0800 Date: Tue, 25 Nov 2003 20:51:15 -0800 From: Brooks Davis To: walt Message-ID: <20031126045114.GA17496@Odin.AC.HMC.Edu> References: <3FC41523.6060105@myrealbox.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FCuugMFkClbJLl1L" Content-Disposition: inline In-Reply-To: <3FC41523.6060105@myrealbox.com> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: freebsd-current@freebsd.org Subject: Re: How to fix this in 5.1-REL?? 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: Wed, 26 Nov 2003 04:51:19 -0000 --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 25, 2003 at 06:51:15PM -0800, walt wrote: > Brooks Davis answered: >=20 > walt asked: > >>What does 'buildworld' give us that the new kernel might need? >=20 > >The correct toolchain including the compiler and config(8). >=20 > Okay, thanks, that helps. >=20 > Just thinking out loud about worst-case examples for people who > do routinely use 'make world' (like I have for several years). >=20 > I found out first-hand why installworld quits halfway through > when the new executables won't run on the old kernel. I need no > further education on that point ;-) >=20 > I'm thinking, though, that doing 'make kernel' first has a much > lower potential for disaster than 'make world': if I reboot after > a 'make kernel' and the new kernel won't run on the old world, then > all I need to do to recover is to boot the old kernel again and > 'make buildworld'. Seems difficult to do any real harm this way. >=20 > Is this completely wrong-headed? Am I missing something important? If you don't build world before building a kernel you may not be able to build a kernel because you may not have toolchain features required to build it. If it builds, it's probably ok, but it may not build, so your should do a "make buildworld" first. As the statfs change demonstrates, you should install a new kernel before attempting to install a new world. These requirements lead to our recomended order. No other order will insure that you can recover at each step. It it worth noting, that neither the buildworld or buildkernel targets have any effect on the running system other then consuming resources so they are always safe. They may not work, but they won't break your install. It's the installation stage that can get you in trouble if you don't do it right. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --FCuugMFkClbJLl1L Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/xDFBXY6L6fI4GtQRAlu4AJ95oEywE4Xx5v1bEJZeq2lgwE3JggCfb93Z V0mprc50v80uY5DGCtVjcYc= =YZ3A -----END PGP SIGNATURE----- --FCuugMFkClbJLl1L--