The FreeBSD project announces the availability of FreeBSD 12.0-RELEASE. It is the first release of the stable/12 branch. The new version comes with updated software and features for a wild variety of architectures. The latest release provides performance improvements and better support for FreeBSD jails and more. One can benefit greatly using an upgraded version of FreeBSD.
FreeBSD 12.0 supports amd64, i386, powerpc, powerpc64, powerpcspe, sparc64, armv6, armv7, and aarch64 architectures. One can run it on a standalone server or desktop system. Another option is to run it on Raspberry PI computer. FreeBSD 12 also runs on popular cloud service providers such as AWS EC2/Lightsail or Google compute VM.
FreeBSD 12 released – What’s new?
New features and highlights:
- OpenSSL version 1.1.1a (LTS)
- OpenSSH server 7.8p1
- Unbound server 1.8.1
- Clang and co 6.0.1
- The FreeBSD installer supports EFI+GELI as an installation option
- VIMAGE FreeBSD kernel configuration option has been enabled by default. VIMAGE was the main reason I custom compiled FreeBSD for the last few years. No more custom compile for me.
- Graphics drivers for modern ATI/AMD and Intel graphics cards are now available in the FreeBSD ports collection
- ZFS has been updated to include new sysctl(s), vfs.zfs.arc_min_prefetch_ms and vfs.zfs.arc_min_prescient_prefetch_ms, which improve performance of the zpool scrub subcommand
- The pf packet filter is now usable within a jail using vnet
- KDE updated to version 5.12.5
- The NFS version 4.1 includes pNFS server support
- Perl 5.26.2
- The default PAGER now defaults to less for most commands
- The dd utility has been updated to add the status=progress option to match GNU/Linux dd command to show progress bar while running dd
- FreeBSD now supports ext4 for read/write operation
- Python 2.7 and more
First note down the FreeBSD version by running the following commands:
Make sure both FreeBSD base OS:
freebsd-update fetch install
11.3-RELEASE-p3: /boot/kernel/kernel /boot/kernel/mqueuefs.ko /boot/kernel/sound.ko /boot/kernel/vmm.ko /usr/lib/debug/boot/kernel/kernel.debug /usr/lib/debug/boot/kernel/mqueuefs.ko.debug /usr/lib/debug/boot/kernel/sound.ko.debug /usr/lib/debug/boot/kernel/vmm.ko.debug Installing updates... done.
Next update packages too, run the pkg command
pkg update && pkg upgrade
See FreeBSD Applying Security Updates Using pkg/freebsd-update for more info.
WARNING: Make sure you backup all important data, config files, and database tables/DBS. The author is not responsible for any data loss and upgrading FreeBSD should only be attempted after backing up all data.
Upgrading from previous releases of FreeBSD 11.3 to 12.0 using binary method
Type the following freebsd-update command:
freebsd-update -r 12.0-RELEASE upgrade
Does this look reasonable (y/n) y .... ... /bin/rmail /bin/rmdir /bin/setfacl /bin/sh /bin/sleep /bin/stty /bin/sync /bin/tcsh /bin/test /bin/unlink /bin/uuidgen /boot To install the downloaded upgrades, run "/usr/sbin/freebsd-update install".
Once everything downloaded, merged in a directory, it is time to commit changes to the disk, run:
Installing updates... Kernel updates have been installed. Please reboot and run "/usr/sbin/freebsd-update install" again to finish installing updates.
Therefore, reboot the FreeBSD box:
Once the system has come back online, restart freebsd-update using the following command to remove all old shared libraries and object files:
Installing updates... Completing this upgrade requires removing old shared object files. Please rebuild all installed 3rd party software (e.g., programs installed from the ports tree) and then run "/usr/sbin/freebsd-update install" again to finish installing updates.
Now base system has been updated. It is time to update all binary packages too. Simply run the following pkg command:
pkg-static install -f pkg
Updating FreeBSD repository catalogue... FreeBSD repository is up to date. All repositories are up to date. Checking for upgrades (39 candidates): 100% Processing candidates (39 candidates): 100% The following 42 package(s) will be affected (of 0 checked): New packages to be INSTALLED: gdb: 8.2 expat: 2.2.6_1 libiconv: 1.14_11 Installed packages to be UPGRADED: ca_root_nss: 3.40.1 -> 3.41 Installed packages to be REINSTALLED: sudo-1.8.25p1 (ABI changed: 'freebsd:11:x86:64' -> 'freebsd:12:x86:64') sqlite3-3.25.1 (ABI changed: 'freebsd:11:x86:64' -> 'freebsd:12:x86:64') readline-7.0.3_1 (ABI changed: 'freebsd:11:x86:64' -> 'freebsd:12:x86:64') ..... ... .... binutils-2.30_5,1 (ABI changed: 'freebsd:11:x86:64' -> 'freebsd:12:x86:64') Number of packages to be installed: 3 Number of packages to be upgraded: 1 Number of packages to be reinstalled: 38 The process will require 53 MiB more space. 145 MiB to be downloaded. Proceed with this action? [y/N]: y [1/42] Fetching sudo-1.8.25p1.txz: 100% 682 KiB 698.3kB/s 00:01 [2/42] Fetching sqlite3-3.25.1.txz: 100% 1 MiB 266.6kB/s 00:05 .... .. ... [42/42] Fetching libiconv-1.14_11.txz: 100% 601 KiB 615.9kB/s 00:01 Checking integrity... done (0 conflicting) [1/42] Reinstalling indexinfo-0.3.1... [1/42] Extracting indexinfo-0.3.1: 100% [2/42] Reinstalling readline-7.0.3_1... [2/42] Extracting readline-7.0.3_1: 100% [3/42] Reinstalling libffi-3.2.1_2... .... .. ... By default panic reports will be sent to root with instructions to forward them if they do not contain any sensitive information. To automatically submit panic reports directly, add panicmail_autosubmit="YES" to your /etc/rc.conf in addition. Message from gcc6-6.4.0_8: To ensure binaries built with this toolchain find appropriate versions of the necessary run-time libraries, you may want to link using -Wl,-rpath=/usr/local/lib/gcc6 For ports leveraging USE_GCC, USES=compiler, or USES=fortran this happens transparently.
One more last time and you are done:
Please note that it is also possible to upgrade the system using source based method. You need to read the information provided in /usr/src/UPDATING file.
How to verify FreeBSD 11 to 12 upgrade
Make sure all services are running:
netstat -a -n | grep LISTEN
Check out for errors in log file using the cat command/grep command/egrep command and other tools:
tail -f /var/log/messages
grep error /path/to/app
egrep -i 'err|warn|cri' /var/log/messages
Do I need to upgrade FreeBSD to 12 ASAP?
Not really. FreeBSD 11.2 continues to support. There is no need to rush. You can wait for some time and apply updates when you are free.
Overall FreeBSD 12 lead an even more robust BSD family of the operating system for end users, and it would benefit significantly for FreeBSD based open source projects such as FreeNAS, pfSense and others. For more information see FreeBSD download page here and release note here.
🐧 Get the latest tutorials on Linux, Open Source & DevOps via:
|Category||List of Unix and Linux commands|
|Firewall||Alpine Awall • CentOS 8 • OpenSUSE • RHEL 8 • Ubuntu 16.04 • Ubuntu 18.04 • Ubuntu 20.04|
|Network Utilities||dig • host • ip • nmap|
|OpenVPN||CentOS 7 • CentOS 8 • Debian 10 • Debian 8/9 • Ubuntu 18.04 • Ubuntu 20.04|
|Package Manager||apk • apt|
|Processes Management||bg • chroot • cron • disown • fg • jobs • killall • kill • pidof • pstree • pwdx • time|
|Searching||grep • whereis • which|
|User Information||groups • id • lastcomm • last • lid/libuser-lid • logname • members • users • whoami • who • w|
|WireGuard VPN||Alpine • CentOS 8 • Debian 10 • Firewall • Ubuntu 20.04|