From owner-freebsd-stable@FreeBSD.ORG Sun Sep 21 04:30:10 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA45416A4BF for ; Sun, 21 Sep 2003 04:30:09 -0700 (PDT) Received: from mta05-svc.ntlworld.com (mta05-svc.ntlworld.com [62.253.162.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25A2E43FCB for ; Sun, 21 Sep 2003 04:29:55 -0700 (PDT) (envelope-from scott@fishballoon.org) Received: from llama.fishballoon.org ([81.104.195.124]) by mta05-svc.ntlworld.comESMTP <20030921112954.WRPF13360.mta05-svc.ntlworld.com@llama.fishballoon.org>; Sun, 21 Sep 2003 12:29:54 +0100 Received: from scott by llama.fishballoon.org with local (Exim 4.20) id 1A12Op-000EFZ-Ih; Sun, 21 Sep 2003 12:29:07 +0100 Date: Sun, 21 Sep 2003 12:29:07 +0100 From: Scott Mitchell To: Alban Hertroys Message-ID: <20030921112907.GB41350@llama.fishballoon.org> References: <20030921104920.GB47741@happy-idiot-talk.infracaninophile.co.uk> <20030921111334.94A6A410@solfertje.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030921111334.94A6A410@solfertje.student.utwente.nl> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.8-RELEASE i386 Sender: Scott Mitchell cc: Jacob cc: stable@freebsd.org Subject: Re: upgrading X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2003 11:30:10 -0000 On Sun, Sep 21, 2003 at 01:13:11PM +0200, Alban Hertroys wrote: > On 21 Sep, Matthew Seaman hit a keyboard in the following places: > > # shutdown -r now > > Hmm, I usually prefer to do just: #shutdown now > so that I end up in single user mode immedately. I usually check 'ps' to see > whether no daemons are running (fleeing?) that should have died. > This method has the effect that you're still running the same kernel, > but I'm now unsure whether that's a good or a bad thing. > > If you reboot (with '-r'), you are booting a system where the kernel is > upgraded, but the rest of the system isn't. That could cause startup > scripts to fail and the like. You *want* to boot the new kernel, to make sure that it will actually boot before installing the rest of the upgraded system. Obviously you'll boot into single-user mode for the reason you state - mixing a new kernel with an old useland is generally a bad idea. If you just go ahead and installworld without testing the new kernel first, you increase your risk of completely breaking your system. Up to the point where you run installworld, you can still back out and boot your old system with the old kernel. This is all documented pretty well in the Handbook - the safest method is probably to follow the steps listed there, in that order. There *are* good reasons for it being documented that way. Obviously there are exceptions - building on one machine and installing on another over NFS, for instance - but I would suggest following the Handbook procedure at least the first few times, until you're confident you understand everything that's going on. > OTOH, if you don't, are you using the installed install tools or the > upgraded ones (which may require the new kernel) when running > installworld? Installworld uses the tools built during buildworld. Cheers, Scott