Tag Archives: cvsup

How to upgrade to FreeBSD 7.1

With 7.1 around the corner it might be handy to tell what you need to do in order to upgrade.

First of all you need to understand that I am in no way responsible for the actions you are doing on your system. I can give an advise, but if there is one typo somewhere it could trash your system. That is the case now, and it will forever be as long as there are computers :)

That said: Do you know what kind of user you are?

Did you install via the CD and never heared about CVSup? SVN? and things like that?

Then FreeBSD-update (/usr/sbin/freebsd-update) is the thing for you!
It’s the most simple way to upgrade from a previous -RELEASE (or Security branch) to the current one. Do note that -STABLE or -RC’s are not taken into account and cannot be used to upgrade to 7.1-RELEASE.

In order for you to upgrade please use : /usr/sbin/freebsd-update -r 7.1-RELEASE upgrade && /usr/sbin/freebsd-update -r 7.1-RELEASE install

After this the system will tell you:

Kernel updates have been installed. Please reboot and run
“/usr/sbin/freebsd-update install” again to finish installing updates.

(Thanks richard for the information):

Voila, you will be running 7.1 now!

For people using CVSup: replace the RELENG_7_0 part with RELENG_7_1 (it’s ok if there are other things behind it, as long as you change the zero to a one (0 -> 1)).

Rebuild your kernel as you probably did many times before (cd /usr/src && make buildworld && make buildkernel && make installkernel [reboot in single user mode] mergemaster -p && make installworld && make delete-old && mergemaster [reboot] make delete-old-libs (be careful that ports and things do not depend on older versions. I have been bitten by an account that used the bash shell, with libreadline, which was deleted by make delete-old-libs.. no more bash shell for me!)

If you are doing CVS checkouts you should probably do something with -r RELENG_7_1 or RELENG_7_1_RELEASE to get things going, I would advise the first one since patches will be installed there as well, the _RELEASE branch is static. Then do the tricks like above as well.

If you are a subversion user you should checkout the 7.1 release (all subversion users know how to do this) and perform a bit of magic.