From owner-freebsd-stable@FreeBSD.ORG Fri Mar 11 22:34:41 2005 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 9F88916A4CE for ; Fri, 11 Mar 2005 22:34:41 +0000 (GMT) Received: from smtp.servingpeace.com (servingpeace.com [69.55.225.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72CE943D39 for ; Fri, 11 Mar 2005 22:34:41 +0000 (GMT) (envelope-from sam@servingpeace.com) Received: from [10.0.0.2] (adsl-69-110-162-155.dsl.pltn13.pacbell.net [69.110.162.155]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.servingpeace.com (Postfix) with ESMTP id 005FBBA15F; Fri, 11 Mar 2005 14:34:40 -0800 (PST) Message-ID: <42321CE7.3060404@servingpeace.com> Date: Fri, 11 Mar 2005 14:34:15 -0800 From: Sam Nilsson User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bashar References: <422F250B.6030505@kuwaitnet.net> <20050309234141.L53915@carver.gumbysoft.com> <423040FE.8090305@kuwaitnet.net> <20050310225201.Y64217@carver.gumbysoft.com> <42324A79.6070302@kuwaitnet.net> <4231EE30.6010405@alumni.rice.edu> <4232142C.40407@kuwaitnet.net> In-Reply-To: <4232142C.40407@kuwaitnet.net> Content-Type: text/plain; charset=windows-1256; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: from 5.4-PRERELEASE -> 5.3-RELEASE-p5 error? 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: Fri, 11 Mar 2005 22:34:41 -0000 Bashar wrote: >> The Canonical Way to Update Your System (for 5.x): >> 1) make buildworld >> 2) make buildkernel KERNCONF=YOUR_KERNEL_HERE >> 3) make installkernel KERNCONF=YOUR_KERNEL_HERE >> 4) >> 5) /etc/rc.d/preseedrandom >> 6) mergemaster -p >> 7) make installworld >> 8) mergemaster >> 9) >> >> Jon > > > Jon, > Cant do this for remote system as you know Sorry if this is a bit off topic... Well, you can't reboot into single user on remote (unless you have a remote console setup), but I have done the above steps remotely except for that. The difference for me was that instead of rebooting into single user, I rebooted into normal system, then shut down each running service/daemon except for ssh before the mergemaster and installworld steps. I don't know how reliable this method is for others, but it always works well for me (with 5.3 Release and 5.3 Stable at least). - Sam