From owner-freebsd-stable@FreeBSD.ORG  Tue May  9 10:56:11 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
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 49CA516A404
	for <freebsd-stable@freebsd.org>; Tue,  9 May 2006 10:56:11 +0000 (UTC)
	(envelope-from hans@lambermont.dyndns.org)
Received: from lambermont.dyndns.org (lambermont.dyndns.org [82.93.47.245])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B6F5943D53
	for <freebsd-stable@freebsd.org>; Tue,  9 May 2006 10:56:10 +0000 (GMT)
	(envelope-from hans@lambermont.dyndns.org)
Received: by lambermont.dyndns.org (Postfix, from userid 1001)
	id 58E4D22DDD3; Tue,  9 May 2006 12:56:09 +0200 (CEST)
Date: Tue, 9 May 2006 12:56:09 +0200
To: David Wolfskill <david@catwhisker.org>,
	Scott Harrison <scott@mithrandir.com>, freebsd-stable@freebsd.org
Message-ID: <20060509105609.GC66029@leia.lambermont.dyndns.org>
References: <372C34B7-18BC-4061-99ED-8321E8109CF7@mithrandir.com>
	<20060508231759.GC545@bunrab.catwhisker.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060508231759.GC545@bunrab.catwhisker.org>
User-Agent: Mutt/1.4.2.1i
From: hans@lambermont.dyndns.org (Hans Lambermont)
Cc: 
Subject: Re: Best practices for remote upgrade?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 May 2006 10:56:11 -0000

David Wolfskill wrote:

> On Mon, May 08, 2006 at 02:29:23PM +0200, Scott Harrison wrote:
>> 	I have some 4.x servers that I would like to upgrade to 5.x, and  
>> perhaps 6.x.  However, I do not have any local access to these  
>> machines.  I can ssh into them only.  I would like to know whether it  
>> is possible for me to upgrade the machines with only ssh access, and  
>> what one should do to go about upgrading them.
...
> I then have little shell scripts to use "dump | restore" to "clone" the
> file systems from one slice to the other.
...
> * Reboot from the "other" slice (the target of the above operation).
> * Upgrade in place.
> * Reboot (without changing active slice).

I do almost the same; I do not reboot to the other slice to upgrade it,
instead I use the current slice to upgrade, and if that fails reboot to
the other slice (the backup slice). It's the same idea, with one less
reboot.

This dual-boot-slice (or disk :) setup also allows for the UFS->UFS2
transition.

regards,
   Hans Lambermont