Date: Wed, 14 Feb 2018 18:04:55 -0600 From: Tim Daneliuk <tundra@tundraware.com> To: "Randal L. Schwartz" <merlyn@stonehenge.com>, Doug Hardie <bc979@lafn.org> Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: any problem going from 9.x (don't laugh) to 11 directly? Message-ID: <97406fe4-5ffb-c179-670b-47ade93bdf2a@tundraware.com> In-Reply-To: <37591333-593e-7c35-0cfb-a3ab02bddf55@tundraware.com> References: <86lgfvjk6c.fsf@red.stonehenge.com> <7F0B2921-9F04-4E15-BD0F-17A0EA8E953B@mail.sermon-archive.info> <86lgfvi20e.fsf@red.stonehenge.com> <37591333-593e-7c35-0cfb-a3ab02bddf55@tundraware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/14/2018 05:51 PM, Tim Daneliuk wrote: > On 02/14/2018 05:29 PM, Randal L. Schwartz wrote: > >> Doug> There are enough library changes that most services just will not >> Doug> start properly and tend to hang. You are left with a system that >> Doug> is non-responsive. The one approach I used successfully one time >> Doug> was to comment virtually everything other than sshd out in >> Doug> rc.conf. You have to make sure you have really killed sendmail >> Doug> though. Setting it to NO is not enough. Otherwise it will >> Doug> eventually give up and give you back service, but it takes a long >> Doug> time. >> >> Great advice! Thanks. >> > > Another strategy might be to put a second drive in the system and install > a clean version of 11 and all the needed packages/ports on that. Then - > since it can mount your existing 9.x disk, incrementally copy over your > data and custom configurations. In my experience, this turns out to be > a lot quicker and cleaner that trying to do in-place upgrades. Moreover, > when you are all done, you still have your original, untouched disk. > > Disks are cheap :) > Oh, another way I've done this in inside VMs. Once configured and built to my satisfaction, I just tarball off the entire contents of the VM's filesystem. Then, I pour it onto a bare "real" drive that's been partitioned and formatted appropriately. On Linux systems, I do some this with docker instances, although full OS imaging is a good use case for this approach. Some notes I've jotted down over the years: https://www.tundraware.com/TechnicalNotes/Baremetal -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?97406fe4-5ffb-c179-670b-47ade93bdf2a>