Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 10 May 2006 14:25:35 +0100 (BST)
From:      Alex Hayward <xelah-freebsd@xelah.com>
To:        Scott Harrison <scott@mithrandir.com>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: Best practices for remote upgrade?
Message-ID:  <Pine.LNX.4.58.0605101416180.3463@sphinx.mythic-beasts.com>
In-Reply-To: <ECEE3367-C048-437F-B1D6-1156DB98C65E@mithrandir.com>
References:  <372C34B7-18BC-4061-99ED-8321E8109CF7@mithrandir.com> <20060508231759.GC545@bunrab.catwhisker.org> <20060509105609.GC66029@leia.lambermont.dyndns.org> <ECEE3367-C048-437F-B1D6-1156DB98C65E@mithrandir.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 9 May 2006, Scott Harrison wrote:

> 	This sounds nice except that I do not have my disk already
> partitioned like this.  Can I take a 4.7 machine (for example) and
> live repartition it to be like this?

It /is/ possible to upgrade from at least some versions of FreeBSD 4 to
some versions of FreeBSD 5 remotely without a spare partition (I've done
it a few times), but there's lots that can go wrong. See
http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2004-01/0033.html

Watch out, though, after the 'tar' step you may find your binaries don't
work (including binaries like 'reboot'). Keeping a copy is a good idea.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.58.0605101416180.3463>