From owner-freebsd-stable@FreeBSD.ORG Sat Dec 4 19:39:07 2004 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 53CCA16A552 for ; Sat, 4 Dec 2004 19:39:07 +0000 (GMT) Received: from smtp.servingpeace.com (servingpeace.com [69.55.225.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3030C43D5E for ; Sat, 4 Dec 2004 19:39:07 +0000 (GMT) (envelope-from sam@servingpeace.com) Received: from [10.0.0.2] (adsl-68-122-12-222.dsl.pltn13.pacbell.net [68.122.12.222]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.servingpeace.com (Postfix) with ESMTP id A8FCDBA6AF for ; Sat, 4 Dec 2004 11:39:06 -0800 (PST) Message-ID: <41B2125A.5080401@servingpeace.com> Date: Sat, 04 Dec 2004 11:39:06 -0800 From: Sam Nilsson User-Agent: Mozilla Thunderbird 1.0RC1 (Macintosh/20041201) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <41B1F89B.5050501@frenchsuballiance.cjb.net> <20041204182852.GA17775@falcon.midgard.homeip.net> In-Reply-To: <20041204182852.GA17775@falcon.midgard.homeip.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Mergemaster on a distant system 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: Sat, 04 Dec 2004 19:39:07 -0000 Erik Trulsson wrote: > It is not necessary to reboot or go into single user mode in order to > run mergemaster, and I doubt the handbook says it is necessary. > > It is sometimes necessary to reboot with a new kernel to let > installworld work properly, but most of the time rebooting is not > needed. > > It is usually a good idea to boot into single-user mode to make sure > that there is no programs running in the background that can disrupt/be > disrupted by the upgrade process, but it is rarely necessary. That's right. Just to chime in, I did the whole make buildworld ... buildkernel ... installworld ... mergemaster all over ssh yesterday. For me it wasn't much of a risk because the computer was in the same room. The biggest risk is that the new kernel doesn't boot up. I don't know how often that happens, but that is what I would worry about if I didn't have access to the boot prompt. Anyway, my upgade went flawlessly. Just shut down all services except for sshd that are running before you installworld and mergemaster. - Sam Nilsson