How to FreeBSD: Upgrades: Minor Versions to Major Releases

[@jefflloyd5170]

Am new at FreeBSD, and thank you for this excellent tutorial to upgrade the OS.

[@sheridans]

Glad it was helpful. Thanks for the feedback

[@zhongj]

Have you also provide steps on rebuilding any packages that you build from port for the major upgrade?

[@NetScalerTrainer]

what about FreeBSD as a VMWare VM? how to get GUI to work? I just get a black screen.

[@sheridans]

Did you ask this on another video? Have you installed the VM tools I suggested? Also did you choose X11 from the login manager as opposed to Wayland?

[@diablobarcelona]

You should be really disabling the repo using echo "FreeBSD: { enabled: no }" > /usr/local/etc/pkg/repos/FreeBSD.conf , and setting up a new file like /usr/local/etc/pkg/repos/FreeBSD-Latest.conf and having that configuration enabled to pull the latest.

[@sheridans]

Good suggestion! Thanks for feedback.

[@davidshuman9366]

@@sheridans you may understand the above but considering the question I started to ask can I get this explained more completely? My initial question was: I like the idea of keeping the /etc/pkg configuration files unchanged files from the install. However; it would seem moving them to /usr/local/etc/pkg/repos places the responsibility on the administrator to diff the two files after the upgrade and make the appropriate changes (additions/modifications/deletions) to the /usr/local/etc/pkg/repos version of the file. Do I have this requirement correct? How does the suggestion affect that process? Are there limits to which files are appropriate for this treatment? I have a feeling /usr/local/etc/smartd.conf we considered during installation is not a candidate for this treatment.

[@sheridans]

@davidshuman9366 the file /etc/pkg/FreeBSD.conf rarely changes. Adding the necessary lines in /usr/local/etc/pkg/repos/FreeBSD.conf stops your changes being overwritten and stops freebsd-update pestering you about file changes.