Date: Wed, 09 Sep 2020 15:41:28 +0200 From: rainer@ultra-secure.de To: matthew@freebsd.org Cc: freebsd-pkg@freebsd.org Subject: Re: Exploring the updateability of FreeBSD 8.2 -> 12.1 Message-ID: <e3f3105d4ca4651f06161494521e073b@ultra-secure.de> In-Reply-To: <6b2eea23-5ac1-73a2-1c3a-7cece6efebc6@infracaninophile.co.uk> References: <2a78c4416eaa4bb90665075743ba7e7a@ultra-secure.de> <20200909130242.GA90890@freefall.freebsd.org> <6b2eea23-5ac1-73a2-1c3a-7cece6efebc6@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 2020-09-09 15:27, schrieb matthew@FreeBSD.org: > For such a large jump in versions, it would probably be a good idea to > obtain a new hard drive and do a complete fresh install of FreeBSD > from scratch, install all the necessary packages, copy over data and > add any local configuration to replicate the functionality of the old > system. This has several advantages: > > * You will still have the original 8.2 system available to revert > back > to in case of problems > * You can adapt the disk partitioning to suit what current FreeBSD > needs, or you change low level things like switching from UFS to > ZFS > if desired. > * It takes the pressure off -- you can in principle work on > installing > the new system off-line, apply whatever acceptance tests you need > and then only have as much downtime as it takes to swap in the new > drive. It's principally a VM, so I could create a snapshot. I'm now considering doing a parallel, fresh install, though. Thanks for the input. Rainer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e3f3105d4ca4651f06161494521e073b>