2.2.1 to 2.2.2 Trouble Free Upgrade
-
2.2.2-RELEASE (i386)
built on Mon Apr 13 20:10:33 CDT 2015FreeBSD 10.1-RELEASE-p9
DELL Inspiron 5100 bare metal running full install on USB Flash Drive with tmp and var on ram disk.
Upgrade Process
(no packages to remove first)
Backup Config
Restart existing system
Console option #13 upgrade (auto)
System rebooted automatically with new version -
I think that no packages to deinstall and simple hardware played an important part in your success.
-
Uncomplicated hardware is a plus usually as is uncomplicated configurations, but all of my updates went fine on both minimal and complicated installs.
-
I guess I am just unlucky. The last upgrade I did that didn't need starting again from ISO was upgrading to 2.1.5 . Since then, I have had to go back to ISO install and configure everything in the GUI each time. Fortunately for me, restoring from backup config works if I don't change version number.
-
I hate to post a "me, too" response, but me, too.
APU2 running nanoBSD. Upgrade went smooth. I have 5 more customer APUs to update today, and a SG-2440. I'll try the instance I have running on ESXi 5.5 shortly.
-
My instance on ESXi 5.5u2 upgraded just fine.
-
NanoBSD… hmm. You've got me thinking about trying this again.
-
Be brave. Take the leap.
-
NanoBSD has it's place. It's much more tolerant of abuse by the failings of your local electrical utility.
-
NanoBSD has it's place. It's much more tolerant of abuse by the failings of your local electrical utility.
So is a notebook (built-in UPS).
-
Also no trouble.
Intel Atom x64 hd install, squid3, squidguard, a few other packages, no problem. Haven't ssh'ed yet to check my loader.conf.
-
No problems here either.
2.2.1 (newinstall) x64, hyper-v guest
LAN, WAN, GUESTLAN(VLAN), OpenVPN-server and IPSEC lines, Squid, Squidfilter, Sarg, Lightsquid
Went smooth to up to 2.2.2 (gambled and did it remotely connected with VPN…) :oBrgs,
