No offense intended but everything which is somewhat unknown or obscure to you might seem complicated at first. But FreeBSD is also a very extensively documented environment. And well, you know the saying: practice makes perfectIt used to be complicated to upgrade FreeBSD. So because of that, I stayed away from it.
# make menuconfig
you actually had to manually edit a config file Indeed, once you've done it a few times it's actually quite easy.It honestly isn't as complicated as it might seem.
Apart from what SirDice said above:
No offense intended but everything which is somewhat unknown or obscure to you might seem complicated at first. But FreeBSD is also a very extensively documented environment. And well, you know the saying: practice makes perfect
Reason I mention this is because your comment brought back some memories from when I first tried to upgrade FreeBSD using the source code (I was used to Linux back then). In comparison it seemed extremely complex. Instead of simply running# make menuconfig
you actually had to manually edit a config file
But now, a few years later, it became normal for me, second nature if you will. It takes effort, but it's hardly as complex anymore.
But yeah, freebsd-update is a thing. Also see its freebsd-update(8) manualpage and there's also a whole chapter about updating FreeBSD in the handbook.
It honestly isn't as complicated as it might seem.
freebsd-update
has been more reliable than flipping the light switch in my bedroom.It used to be complicated to upgrade FreeBSD. So because of that, I stayed away from it. But now it only takes? I want to be sure before I take this big step. I have locked myself out in the past with other issues and I want to avoid that. And I assume a reboot?Code:freebsd-update
I would strongly suggest the use of IPMI or ILO during upgrades regardless of the method. I have been upgrading systems for years and I never perform an upgrade anymore if I don't have some sort of access to the server.I agree, but updating freebsd is a different story and a big one. If update apache fails, I can redo it. If this update fails, I have the change of not having access to my server anymore. Sites are down, mail is down. Can take days before I can solve this. An expert can solve it pretty easy because he knows what to do. I can handle things, but it is limited. My server is thousands of miles away from me, so console access is out of the question. So this is a big step for me.
You will find that sysutils/screen or sysutils/tmux can save you from broken ssh sessions.I tried it the other day and found that I could not upgrade a CURRENT version to a RELEASE version of FreeBSD, so check what you are trying to upgrade. I ended up having to Rebuild World via ssh and the process stalled before it finished.
When I flip the light switch in my bedroom, the light comes on every single time. There have been times when it didn't. Either the light bulb was burned out or the switch broke or a fuse blew but, otherwise, it's extremely reliable and expected to work all the time.
freebsd-update
has been more reliable than flipping the light switch in my bedroom.
I tried it the other day and found that I could not upgrade a CURRENT version to a RELEASE version of FreeBSD, so check what you are trying to upgrade. I ended up having to Rebuild World via ssh and the process stalled before it finished.
Let me reiterate as there seems to be some confusion, freebsd-update(8) can only update/upgrade from one -RELEASE version to another, i.e. 11.0-RELEASE-p1 to 11.0-RELEASE-p4, or 10.3-RELEASE-p2 to 11.0-RELEASE-p4. Updating/upgrading any other version (i.e. 11-STABLE, 11-CURRENT, 12-CURRENT) requires building world using the source.