home.social

#freebsd15 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #freebsd15, aggregated by home.social.

fetched live
  1. Woot, FINALLY!

    rld@Intrepid:~$ uname -a
    FreeBSD Intrepid 15.1-RELEASE-p2 FreeBSD 15.1-RELEASE-p2 releng/15.1-n283596-aadd58dddcbc GENERIC amd64
    

    No more networking issues, and drm (graphics) didn't work at first, but then sorted itself out.

    🤷‍♂️ Mmmmmkay!!! 😄

    #FreeBSD #FreeBSD15 #Upgrade

  2. Woot, FINALLY!

    rld@Intrepid:~$ uname -a
    FreeBSD Intrepid 15.1-RELEASE-p2 FreeBSD 15.1-RELEASE-p2 releng/15.1-n283596-aadd58dddcbc GENERIC amd64
    

    No more networking issues, and drm (graphics) didn't work at first, but then sorted itself out.

    🤷‍♂️ Mmmmmkay!!! 😄

    #FreeBSD #FreeBSD15 #Upgrade

  3. Woot, FINALLY!

    rld@Intrepid:~$ uname -a
    FreeBSD Intrepid 15.1-RELEASE-p2 FreeBSD 15.1-RELEASE-p2 releng/15.1-n283596-aadd58dddcbc GENERIC amd64
    

    No more networking issues, and drm (graphics) didn't work at first, but then sorted itself out.

    🤷‍♂️ Mmmmmkay!!! 😄

    #FreeBSD #FreeBSD15 #Upgrade

  4. Woot, FINALLY!

    rld@Intrepid:~$ uname -a
    FreeBSD Intrepid 15.1-RELEASE-p2 FreeBSD 15.1-RELEASE-p2 releng/15.1-n283596-aadd58dddcbc GENERIC amd64
    

    No more networking issues, and drm (graphics) didn't work at first, but then sorted itself out.

    🤷‍♂️ Mmmmmkay!!! 😄

    #FreeBSD #FreeBSD15 #Upgrade

  5. Woot, FINALLY!

    rld@Intrepid:~$ uname -a
    FreeBSD Intrepid 15.1-RELEASE-p2 FreeBSD 15.1-RELEASE-p2 releng/15.1-n283596-aadd58dddcbc GENERIC amd64
    

    No more networking issues, and drm (graphics) didn't work at first, but then sorted itself out.

    🤷‍♂️ Mmmmmkay!!! 😄

    #FreeBSD #FreeBSD15 #Upgrade

  6. 🛡️🌐 OPNsense 26.7 „Xenial Xenops” a fost lansat: Trecere istorică la FreeBSD 15.1 și API-uri complet reproiectateOPNsense, una dintre cele mai populare și de încredere platforme open-source de tip firewall și routing din lume, a lansat oficial versiunea OPNsense 26.7, purtând numele de cod „Xenial Xenops”. Aceasta este o actualizare de anvergură, marcând tranziția fundamentală la noul sistem de operare de bază FreeBSD 15.1 și aducând optimizări structurale majore care pregătesc platforma pentru viitor. Sub sloganul modernizării continue, OPNsense 26.7 înlocuiește treptat codul vechi cu noi mecanisme bazate pe arhitectura MVC (Model-View-Controller) și API-uri flexibile, oferind în același timp un plus masiv de performanță la nivelul rețelei.Iată principalele noutăți ale acestei versiuni de top:🔹 FreeBSD 15.1: Fundația de ultimă generație Trecerea la sistemul de operare FreeBSD 15.1 reprezintă nucleul acestei lansări. Utilizatorii vor beneficia de: Drivere de rețea mult îmbunătățite și compatibilitate extinsă cu plăci de rețea moderne (inclusiv suport optimizat pentru virtualizare).Actualizări de securitate direct din upstream, un kernel mult mai stabil și un subsistem de filtrare a pachetelor (pf) optimizat pentru viteze Gigabit și multi-Gigabit. 🔹 Migrare masivă la MVC / APIPentru a face administrarea firewall-ului mai simplă, mai sigură și ușor de automatizat (ideal pentru integrări cu unelte precum Ansible sau Terraform), OPNsense a migrat mai multe componente cheie către noul cadru tehnic:Asignările de interfețe și grupurile de gateway-uri au fost reproiectate complet prin MVC/API.Regulile de firewall implicite folosesc acum, în mod nativ, noua interfață grafică bazată pe API.🔹 Asistent de migrare către Source NATAceastă versiune aduce un utilitar de migrare extrem de util, conceput să asiste administratorii de rețea în transferul regulilor din vechiul format Outbound NAT către noul format Source NAT (SNAT), mult mai curat și conform cu standardele moderne de rutare.🔹 Servicii și Protocoale Actualizate:Kea DHCP: DHCP-ul modern dezvoltat de ISC primește opțiuni personalizate extinse, suport DDNS (Dynamic DNS) și delegare dinamică de prefixe (Prefix Delegation).Captive Portal: Adaugă un suport extins și mult mai robust pentru conexiunile IPv6. Sursă software de ultimă oră: Sub capotă, OPNsense 26.7 rulează acum cu OpenVPN 2.7, PHP 8.5 și Python 3.13, asigurând timpi de execuție mai rapizi pentru interfața web și o securitate sporită a criptării.🔹 Un nou widget pentru ServiciiInterfața grafică (Dashboard) a primit un nou widget pentru monitorizarea serviciilor active, cu un layout compact, plat (flat tile). Acest lucru permite monitorizarea vizuală rapidă a stării serviciilor DHCP, Unbound, VPN etc., fără a încărca inutil pagina principală.#OpenSource #OPNsense #OPNsense267 #FreeBSD15 #Firewall #NetworkSecurity #SysAdmin #TechNews #Linuxiac

  7. 🛡️🌐 OPNsense 26.7 „Xenial Xenops” a fost lansat: Trecere istorică la FreeBSD 15.1 și API-uri complet reproiectateOPNsense, una dintre cele mai populare și de încredere platforme open-source de tip firewall și routing din lume, a lansat oficial versiunea OPNsense 26.7, purtând numele de cod „Xenial Xenops”. Aceasta este o actualizare de anvergură, marcând tranziția fundamentală la noul sistem de operare de bază FreeBSD 15.1 și aducând optimizări structurale majore care pregătesc platforma pentru viitor. Sub sloganul modernizării continue, OPNsense 26.7 înlocuiește treptat codul vechi cu noi mecanisme bazate pe arhitectura MVC (Model-View-Controller) și API-uri flexibile, oferind în același timp un plus masiv de performanță la nivelul rețelei.Iată principalele noutăți ale acestei versiuni de top:🔹 FreeBSD 15.1: Fundația de ultimă generație Trecerea la sistemul de operare FreeBSD 15.1 reprezintă nucleul acestei lansări. Utilizatorii vor beneficia de: Drivere de rețea mult îmbunătățite și compatibilitate extinsă cu plăci de rețea moderne (inclusiv suport optimizat pentru virtualizare).Actualizări de securitate direct din upstream, un kernel mult mai stabil și un subsistem de filtrare a pachetelor (pf) optimizat pentru viteze Gigabit și multi-Gigabit. 🔹 Migrare masivă la MVC / APIPentru a face administrarea firewall-ului mai simplă, mai sigură și ușor de automatizat (ideal pentru integrări cu unelte precum Ansible sau Terraform), OPNsense a migrat mai multe componente cheie către noul cadru tehnic:Asignările de interfețe și grupurile de gateway-uri au fost reproiectate complet prin MVC/API.Regulile de firewall implicite folosesc acum, în mod nativ, noua interfață grafică bazată pe API.🔹 Asistent de migrare către Source NATAceastă versiune aduce un utilitar de migrare extrem de util, conceput să asiste administratorii de rețea în transferul regulilor din vechiul format Outbound NAT către noul format Source NAT (SNAT), mult mai curat și conform cu standardele moderne de rutare.🔹 Servicii și Protocoale Actualizate:Kea DHCP: DHCP-ul modern dezvoltat de ISC primește opțiuni personalizate extinse, suport DDNS (Dynamic DNS) și delegare dinamică de prefixe (Prefix Delegation).Captive Portal: Adaugă un suport extins și mult mai robust pentru conexiunile IPv6. Sursă software de ultimă oră: Sub capotă, OPNsense 26.7 rulează acum cu OpenVPN 2.7, PHP 8.5 și Python 3.13, asigurând timpi de execuție mai rapizi pentru interfața web și o securitate sporită a criptării.🔹 Un nou widget pentru ServiciiInterfața grafică (Dashboard) a primit un nou widget pentru monitorizarea serviciilor active, cu un layout compact, plat (flat tile). Acest lucru permite monitorizarea vizuală rapidă a stării serviciilor DHCP, Unbound, VPN etc., fără a încărca inutil pagina principală.#OpenSource #OPNsense #OPNsense267 #FreeBSD15 #Firewall #NetworkSecurity #SysAdmin #TechNews #Linuxiac

  8. Our projects now officially support FreeBSD 15.1

    FreeBSD 15.1 was released earlier today, and it provided security bug fixes and other general improvements for the whole FreeBSD system, which was an improvement over last year’s FreeBSD 15.0 release. One of the notable improvements were the inclusion of the updated Wi-Fi drivers that are now based on Linux v7.0 released this year.

    We have earlier conducted our experiments with FreeBSD 15.1 and .NET 10.0, and our experiments have proven to be successful. So, we’ve decided to announce the below great news today.

    Starting from the release day, we’re very excited to announce that we’re now providing official support for running our projects on FreeBSD 15.1! Those who are running our projects on FreeBSD can now obtain official support until March 31st, 2027, through our support timeline.

    To learn more, consult the Aptivi Newsroom article.

    Learn more #Aptivi #FreeBSD #FreeBSD15 #FreeBSD150 #FreeBSD151 #news #Tech #Technology #update
  9. Our projects now officially support FreeBSD 15.1

    FreeBSD 15.1 was released earlier today, and it provided security bug fixes and other general improvements for the whole FreeBSD system, which was an improvement over last year’s FreeBSD 15.0 release. One of the notable improvements were the inclusion of the updated Wi-Fi drivers that are now based on Linux v7.0 released this year.

    We have earlier conducted our experiments with FreeBSD 15.1 and .NET 10.0, and our experiments have proven to be successful. So, we’ve decided to announce the below great news today.

    Starting from the release day, we’re very excited to announce that we’re now providing official support for running our projects on FreeBSD 15.1! Those who are running our projects on FreeBSD can now obtain official support until March 31st, 2027, through our support timeline.

    To learn more, consult the Aptivi Newsroom article.

    Learn more #Aptivi #FreeBSD #FreeBSD15 #FreeBSD150 #FreeBSD151 #news #Tech #Technology #update
  10. Our projects now officially support FreeBSD 15.1

    FreeBSD 15.1 was released earlier today, and it provided security bug fixes and other general improvements for the whole FreeBSD system, which was an improvement over last year’s FreeBSD 15.0 release. One of the notable improvements were the inclusion of the updated Wi-Fi drivers that are now based on Linux v7.0 released this year.

    We have earlier conducted our experiments with FreeBSD 15.1 and .NET 10.0, and our experiments have proven to be successful. So, we’ve decided to announce the below great news today.

    Starting from the release day, we’re very excited to announce that we’re now providing official support for running our projects on FreeBSD 15.1! Those who are running our projects on FreeBSD can now obtain official support until March 31st, 2027, through our support timeline.

    To learn more, consult the Aptivi Newsroom article.

    Learn more #Aptivi #FreeBSD #FreeBSD15 #FreeBSD150 #FreeBSD151 #news #Tech #Technology #update
  11. Our projects now officially support FreeBSD 15.1

    FreeBSD 15.1 was released earlier today, and it provided security bug fixes and other general improvements for the whole FreeBSD system, which was an improvement over last year’s FreeBSD 15.0 release. One of the notable improvements were the inclusion of the updated Wi-Fi drivers that are now based on Linux v7.0 released this year.

    We have earlier conducted our experiments with FreeBSD 15.1 and .NET 10.0, and our experiments have proven to be successful. So, we’ve decided to announce the below great news today.

    Starting from the release day, we’re very excited to announce that we’re now providing official support for running our projects on FreeBSD 15.1! Those who are running our projects on FreeBSD can now obtain official support until March 31st, 2027, through our support timeline.

    To learn more, consult the Aptivi Newsroom article.

    Learn more #Aptivi #FreeBSD #FreeBSD15 #FreeBSD150 #FreeBSD151 #news #Tech #Technology #update
  12. Our projects now officially support FreeBSD 15.1

    FreeBSD 15.1 was released earlier today, and it provided security bug fixes and other general improvements for the whole FreeBSD system, which was an improvement over last year’s FreeBSD 15.0 release. One of the notable improvements were the inclusion of the updated Wi-Fi drivers that are now based on Linux v7.0 released this year.

    We have earlier conducted our experiments with FreeBSD 15.1 and .NET 10.0, and our experiments have proven to be successful. So, we’ve decided to announce the below great news today.

    Starting from the release day, we’re very excited to announce that we’re now providing official support for running our projects on FreeBSD 15.1! Those who are running our projects on FreeBSD can now obtain official support until March 31st, 2027, through our support timeline.

    To learn more, consult the Aptivi Newsroom article.

    Learn more #Aptivi #FreeBSD #FreeBSD15 #FreeBSD150 #FreeBSD151 #news #Tech #Technology #update
  13. Upgrading FreeBSD PKGBASE system from FreeBSD v15.0 to v15.1

    FreeBSD 15.1 was released today, and it brought some of the security fixes that were essential to keep your system secure, as well as introducing other improvements to the operating system to improve your user experience.

    Our first test system was upgraded earlier to FreeBSD 15.1 BETA2 from FreeBSD 15.0, and it was using the EFI boot method that we’ve converted from BIOS using this method. Now, we’ve upgraded our second test system, which used to run FreeBSD 15.0, to the stable version of FreeBSD 15.1, and it’s using the UFS file system.

    To perform this upgrade, we’ve followed the steps from the official FreeBSD documentation. Here’s our experience in upgrading this test system.

    WARNING: The first step that talks about taking a recursive snapshot of the FreeBSD installation, which is sudo bectl create -r pre-15.1, doesn’t work with UFS. In our case, it immediately failed with libbe_init("") failed. If you’re running into the same error message, and your FreeBSD file system is UFS, ignore this error.

    First, we’ve upgraded the package manager, which was essential to allow the upgrade to start.

     aptivi@fbsd-apt:~ $ sudo pkg upgrade -yr FreeBSD-ports pkg  Updating FreeBSD-ports repository catalogue...  Fetching data: 100%    10 MiB  60.3 kB/s    03:02  Processing entries: 100%  FreeBSD-ports repository update completed. 37064 packages processed.  FreeBSD-ports is up to date.  Checking integrity... done (0 conflicting)  Your packages are up to date. 

    The package manager is already up to date! So, we’ve decided to upgrade the base system like this. Please note that both the ABI and the OSVERSION options are necessary so that we can tell the package manager that we’re upgrading the base system packages (-r FreeBSD-base) to FreeBSD version 15.1.

     aptivi@fbsd-apt:~ $ sudo pkg -oABI=FreeBSD:15:$(uname -p) -oOSVERSION=1501000 upgrade -r FreeBSD-base  Updating FreeBSD-base repository catalogue...  pkg: Repository FreeBSD-base has a wrong packagesite, need to re-create database  Fetching meta.conf: 100%     179 B   0.2 kB/s    00:01  Fetching data: 100%    82 KiB  83.8 kB/s    00:01  Processing entries: 100%  FreeBSD-base repository update completed. 509 packages processed.  FreeBSD-base is up to date.  Checking for upgrades (308 candidates): 100%  Processing candidates (308 candidates): 100%  The following 318 package(s) will be affected (of 0 checked):   New packages to be INSTALLED:          FreeBSD-pam: 15.1 [FreeBSD-base]          FreeBSD-pam-dev: 15.1 [FreeBSD-base]          FreeBSD-pam-dev-lib32: 15.1 [FreeBSD-base]          FreeBSD-pam-lib: 15.1 [FreeBSD-base]          FreeBSD-pam-lib32: 15.1 [FreeBSD-base]          FreeBSD-zstd: 15.1 [FreeBSD-base]          FreeBSD-zstd-dev: 15.1 [FreeBSD-base]          FreeBSD-zstd-dev-lib32: 15.1 [FreeBSD-base]          FreeBSD-zstd-lib: 15.1 [FreeBSD-base]          FreeBSD-zstd-lib32: 15.1 [FreeBSD-base]   Installed packages to be UPGRADED:          FreeBSD-acct: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-acpi: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-apm: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-at: 15.0 -> 15.1 [FreeBSD-base]   [...]           FreeBSD-zlib-dev-lib32: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-zlib-lib32: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-zoneinfo: 15.0 -> 15.1 [FreeBSD-base]   Number of packages to be installed: 10  Number of packages to be upgraded: 308   The operation will free 1 MiB.  285 MiB to be downloaded.   Proceed with this action? [y/N]: y  [  1/318] Fetching FreeBSD-ctf-dev-15.1: 100%   138 KiB 141.1 kB/s    00:01  [  2/318] Fetching FreeBSD-nvme-tools-15.1: 100%    84 KiB  85.9 kB/s    00:01    [  3/318] Fetching FreeBSD-ntp-15.1: 100%  1904 KiB   2.0 MB/s    00:01  [  4/318] Fetching FreeBSD-bsdconfig-15.1: 100%   184 KiB 188.8 kB/s    00:01     [  5/318] Fetching FreeBSD-tcpd-dev-15.1: 100%    65 KiB  67.0 kB/s    00:01  [  6/318] Fetching FreeBSD-atf-lib-15.1: 100%    67 KiB  68.8 kB/s    00:01  [  7/318] Fetching FreeBSD-netmap-15.1: 100%    18 KiB  17.9 kB/s    00:01   [...]   [318/323] Upgrading FreeBSD-set-minimal from 15.0 to 15.1...  [319/323] Upgrading FreeBSD-xz-lib32 from 15.0 to 15.1...  [319/323] Extracting FreeBSD-xz-lib32-15.1: 100%  [320/323] Upgrading FreeBSD-set-lib32 from 15.0 to 15.1...  [321/323] Upgrading FreeBSD-yp from 15.0 to 15.1...  [321/323] Extracting FreeBSD-yp-15.1: 100%  [322/323] Installing FreeBSD-set-optional-15.1...  [323/323] Installing FreeBSD-set-base-15.1...  ==> Running trigger: mandoc.ucl  Generating apropos(1) database for /usr/share/man...  Generating apropos(1) database for /usr/share/openssl/man...  =====  Message from FreeBSD-local-unbound-15.1:   --  After upgrading local-unbound, the configuration file should be regenerated  by running "service local_unbound setup" before restarting the service. 

    The upgrade has finished successfully with no errors. At this point, all base packages are now upgraded to version 15.1, including the kernel and the base system packages. However, we need to upgrade the third-party kernel modules so that they become compatible with the newer kernel.

     aptivi@fbsd-apt:~ $ sudo pkg upgrade -r FreeBSD-ports-kmods  Password:  Updating FreeBSD-ports-kmods repository catalogue...  pkg: Repository FreeBSD-ports-kmods has a wrong packagesite, need to re-create database  Fetching meta.conf: 100%     179 B   0.2 kB/s    00:01  Fetching data: 100%    35 KiB  35.6 kB/s    00:01  Processing entries: 100%  FreeBSD-ports-kmods repository update completed. 239 packages processed.  FreeBSD-ports-kmods is up to date.  Checking for upgrades (3 candidates): 100%  Processing candidates (3 candidates): 100%  The following 3 package(s) will be affected (of 0 checked):   Installed packages to be UPGRADED:          open-vm-kmod: 13.0.10.1500068,2 -> 13.0.10.1501000,2 [FreeBSD-ports-kmods]          sysctlbyname-improved-kmod: 20221211.1500068 -> 20221211.1501000 [FreeBSD-ports-kmods]          sysctlinfo-kmod: 20221211.1500068_1 -> 20221211.1501000_1 [FreeBSD-ports-kmods]   Number of packages to be upgraded: 3   44 KiB to be downloaded.   Proceed with this action? [y/N]: y  [1/3] Fetching sysctlbyname-improved-kmod-20221211.1501000: 100%    6481 B   6.5 kB/s    00:01  [2/3] Fetching open-vm-kmod-13.0.10.1501000,2: 100%    23 KiB  23.7 kB/s    00:01  [3/3] Fetching sysctlinfo-kmod-20221211.1501000_1: 100%    14 KiB  14.8 kB/s    00:01  Checking integrity... done (0 conflicting)  [1/3] Upgrading open-vm-kmod from 13.0.10.1500068,2 to 13.0.10.1501000,2...  [1/3] Extracting open-vm-kmod-13.0.10.1501000,2: 100%  [2/3] Upgrading sysctlbyname-improved-kmod from 20221211.1500068 to 20221211.1501000...  [2/3] Extracting sysctlbyname-improved-kmod-20221211.1501000: 100%  [3/3] Upgrading sysctlinfo-kmod from 20221211.1500068_1 to 20221211.1501000_1...  [3/3] Extracting sysctlinfo-kmod-20221211.1501000_1: 100% 

    We’ve verified that there are no .pkgnew files in both /etc and /usr/local/etc directories during the upgrade. Those files are created when the package manager is unable to merge the configuration files safely.

     aptivi@fbsd-apt:~ $ sudo find /etc /usr/local/etc -name '*.pkgnew' -ls  aptivi@fbsd-apt:~ $ 

    Now, we can update the bootloader. First, we’ve verified that the UEFI boot method is used by querying machdep.bootmethod using the sysctl command, which returned UEFI. Then, checked both the boot entry and the primary disk to ensure that we’ve found the correct EFI partition to mount.

     aptivi@fbsd-apt:~ $ sysctl machdep.bootmethod  machdep.bootmethod: UEFI  aptivi@fbsd-apt:~ $ sudo efibootmgr -v  Boot to FW : false  BootCurrent: 0000  BootOrder  : 0000, 0001, 0002, 0003  +Boot0000* EFI VMware Virtual SCSI Hard Drive (0.0) PciRoot(0x0)/Pci(0x10,0x0)/Scsi(0x0,0x0)  aptivi@fbsd-apt:~ $ sudo gpart show da0  =>       40  524287920  da0  GPT  (250G)           40       1024    1  freebsd-boot  (512K)         1064  515898368    2  freebsd-ufs  (246G)    515899432    7168000    3  freebsd-swap  (3.4G)    523067432    1220528    4  efi  (596M) 

    Since we’ve already set up /etc/fstab to automatically mount the EFI partition on startup under the /boot/efi mountpoint, we can update the bootloader easily. If your EFI partition isn’t automatically mounted, you can mount it by running sudo mount_msdosfs /dev/da0p4 /boot/efi, assuming that da0p4 is the correct partition.

     aptivi@fbsd-apt:~ $ mount  /dev/da0p2 on / (ufs, local, soft-updates, journaled soft-updates)  devfs on /dev (devfs)  /dev/da0p4 on /boot/efi (msdosfs, local) 

    Afterwards, we’ve copied the bootloader EFI file to the correct destination, which was /boot/efi/EFI/BOOT/ in our case, and verified that the copy went through. We have no /boot/efi/EFI/FreeBSD directory, so we’ve skipped that.

     aptivi@fbsd-apt:~ $ sudo cp /boot/loader.efi /boot/efi/EFI/BOOT/BOOTX64.EFI  aptivi@fbsd-apt:~ $ ls -l /boot/loader.efi /boot/efi/EFI/BOOT/BOOTX64.EFI  -rwxr-xr-x  1 root wheel 665600 Jun 16 18:05 /boot/efi/EFI/BOOT/BOOTX64.EFI  -r-xr-xr-x  2 root wheel 665600 Jun 12 03:37 /boot/loader.efi 

    Finally, we’ve rebooted the FreeBSD system. If everything went fine, you should be able to see that it’s now running FreeBSD 15.1 instead of 15.0:

     aptivi@fbsd-apt:~ $ uname -a ; freebsd-version  FreeBSD fbsd-apt.aptivi.net 15.1-RELEASE FreeBSD 15.1-RELEASE releng/15.1-n283562-96841ea08dcf GENERIC amd64  15.1-RELEASE 

    We’ve experimented a little with this newly-upgraded FreeBSD 15.1 system, which has .NET 10.0 installed, and the basic console app building and running still works:

     aptivi@fbsd-apt:~ $ cd dotnet_test/  aptivi@fbsd-apt:~/dotnet_test $ mkdir hello  aptivi@fbsd-apt:~/dotnet_test $ cd hello  aptivi@fbsd-apt:~/dotnet_test/hello $ dotnet new console --use-program-main  The template "Console App" was created successfully.   Processing post-creation actions...  Restoring /home/aptivi/dotnet_test/hello/hello.csproj:  Restore succeeded.    aptivi@fbsd-apt:~/dotnet_test/hello $ dotnet run  Hello, World! 
    #FreeBSD #FreeBSD15 #FreeBSD150 #FreeBSD151 #news #Tech #Technology #update
  14. Upgrading FreeBSD PKGBASE system from FreeBSD v15.0 to v15.1

    FreeBSD 15.1 was released today, and it brought some of the security fixes that were essential to keep your system secure, as well as introducing other improvements to the operating system to improve your user experience.

    Our first test system was upgraded earlier to FreeBSD 15.1 BETA2 from FreeBSD 15.0, and it was using the EFI boot method that we’ve converted from BIOS using this method. Now, we’ve upgraded our second test system, which used to run FreeBSD 15.0, to the stable version of FreeBSD 15.1, and it’s using the UFS file system.

    To perform this upgrade, we’ve followed the steps from the official FreeBSD documentation. Here’s our experience in upgrading this test system.

    WARNING: The first step that talks about taking a recursive snapshot of the FreeBSD installation, which is sudo bectl create -r pre-15.1, doesn’t work with UFS. In our case, it immediately failed with libbe_init("") failed. If you’re running into the same error message, and your FreeBSD file system is UFS, ignore this error.

    First, we’ve upgraded the package manager, which was essential to allow the upgrade to start.

     aptivi@fbsd-apt:~ $ sudo pkg upgrade -yr FreeBSD-ports pkg  Updating FreeBSD-ports repository catalogue...  Fetching data: 100%    10 MiB  60.3 kB/s    03:02  Processing entries: 100%  FreeBSD-ports repository update completed. 37064 packages processed.  FreeBSD-ports is up to date.  Checking integrity... done (0 conflicting)  Your packages are up to date. 

    The package manager is already up to date! So, we’ve decided to upgrade the base system like this. Please note that both the ABI and the OSVERSION options are necessary so that we can tell the package manager that we’re upgrading the base system packages (-r FreeBSD-base) to FreeBSD version 15.1.

     aptivi@fbsd-apt:~ $ sudo pkg -oABI=FreeBSD:15:$(uname -p) -oOSVERSION=1501000 upgrade -r FreeBSD-base  Updating FreeBSD-base repository catalogue...  pkg: Repository FreeBSD-base has a wrong packagesite, need to re-create database  Fetching meta.conf: 100%     179 B   0.2 kB/s    00:01  Fetching data: 100%    82 KiB  83.8 kB/s    00:01  Processing entries: 100%  FreeBSD-base repository update completed. 509 packages processed.  FreeBSD-base is up to date.  Checking for upgrades (308 candidates): 100%  Processing candidates (308 candidates): 100%  The following 318 package(s) will be affected (of 0 checked):   New packages to be INSTALLED:          FreeBSD-pam: 15.1 [FreeBSD-base]          FreeBSD-pam-dev: 15.1 [FreeBSD-base]          FreeBSD-pam-dev-lib32: 15.1 [FreeBSD-base]          FreeBSD-pam-lib: 15.1 [FreeBSD-base]          FreeBSD-pam-lib32: 15.1 [FreeBSD-base]          FreeBSD-zstd: 15.1 [FreeBSD-base]          FreeBSD-zstd-dev: 15.1 [FreeBSD-base]          FreeBSD-zstd-dev-lib32: 15.1 [FreeBSD-base]          FreeBSD-zstd-lib: 15.1 [FreeBSD-base]          FreeBSD-zstd-lib32: 15.1 [FreeBSD-base]   Installed packages to be UPGRADED:          FreeBSD-acct: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-acpi: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-apm: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-at: 15.0 -> 15.1 [FreeBSD-base]   [...]           FreeBSD-zlib-dev-lib32: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-zlib-lib32: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-zoneinfo: 15.0 -> 15.1 [FreeBSD-base]   Number of packages to be installed: 10  Number of packages to be upgraded: 308   The operation will free 1 MiB.  285 MiB to be downloaded.   Proceed with this action? [y/N]: y  [  1/318] Fetching FreeBSD-ctf-dev-15.1: 100%   138 KiB 141.1 kB/s    00:01  [  2/318] Fetching FreeBSD-nvme-tools-15.1: 100%    84 KiB  85.9 kB/s    00:01    [  3/318] Fetching FreeBSD-ntp-15.1: 100%  1904 KiB   2.0 MB/s    00:01  [  4/318] Fetching FreeBSD-bsdconfig-15.1: 100%   184 KiB 188.8 kB/s    00:01     [  5/318] Fetching FreeBSD-tcpd-dev-15.1: 100%    65 KiB  67.0 kB/s    00:01  [  6/318] Fetching FreeBSD-atf-lib-15.1: 100%    67 KiB  68.8 kB/s    00:01  [  7/318] Fetching FreeBSD-netmap-15.1: 100%    18 KiB  17.9 kB/s    00:01   [...]   [318/323] Upgrading FreeBSD-set-minimal from 15.0 to 15.1...  [319/323] Upgrading FreeBSD-xz-lib32 from 15.0 to 15.1...  [319/323] Extracting FreeBSD-xz-lib32-15.1: 100%  [320/323] Upgrading FreeBSD-set-lib32 from 15.0 to 15.1...  [321/323] Upgrading FreeBSD-yp from 15.0 to 15.1...  [321/323] Extracting FreeBSD-yp-15.1: 100%  [322/323] Installing FreeBSD-set-optional-15.1...  [323/323] Installing FreeBSD-set-base-15.1...  ==> Running trigger: mandoc.ucl  Generating apropos(1) database for /usr/share/man...  Generating apropos(1) database for /usr/share/openssl/man...  =====  Message from FreeBSD-local-unbound-15.1:   --  After upgrading local-unbound, the configuration file should be regenerated  by running "service local_unbound setup" before restarting the service. 

    The upgrade has finished successfully with no errors. At this point, all base packages are now upgraded to version 15.1, including the kernel and the base system packages. However, we need to upgrade the third-party kernel modules so that they become compatible with the newer kernel.

     aptivi@fbsd-apt:~ $ sudo pkg upgrade -r FreeBSD-ports-kmods  Password:  Updating FreeBSD-ports-kmods repository catalogue...  pkg: Repository FreeBSD-ports-kmods has a wrong packagesite, need to re-create database  Fetching meta.conf: 100%     179 B   0.2 kB/s    00:01  Fetching data: 100%    35 KiB  35.6 kB/s    00:01  Processing entries: 100%  FreeBSD-ports-kmods repository update completed. 239 packages processed.  FreeBSD-ports-kmods is up to date.  Checking for upgrades (3 candidates): 100%  Processing candidates (3 candidates): 100%  The following 3 package(s) will be affected (of 0 checked):   Installed packages to be UPGRADED:          open-vm-kmod: 13.0.10.1500068,2 -> 13.0.10.1501000,2 [FreeBSD-ports-kmods]          sysctlbyname-improved-kmod: 20221211.1500068 -> 20221211.1501000 [FreeBSD-ports-kmods]          sysctlinfo-kmod: 20221211.1500068_1 -> 20221211.1501000_1 [FreeBSD-ports-kmods]   Number of packages to be upgraded: 3   44 KiB to be downloaded.   Proceed with this action? [y/N]: y  [1/3] Fetching sysctlbyname-improved-kmod-20221211.1501000: 100%    6481 B   6.5 kB/s    00:01  [2/3] Fetching open-vm-kmod-13.0.10.1501000,2: 100%    23 KiB  23.7 kB/s    00:01  [3/3] Fetching sysctlinfo-kmod-20221211.1501000_1: 100%    14 KiB  14.8 kB/s    00:01  Checking integrity... done (0 conflicting)  [1/3] Upgrading open-vm-kmod from 13.0.10.1500068,2 to 13.0.10.1501000,2...  [1/3] Extracting open-vm-kmod-13.0.10.1501000,2: 100%  [2/3] Upgrading sysctlbyname-improved-kmod from 20221211.1500068 to 20221211.1501000...  [2/3] Extracting sysctlbyname-improved-kmod-20221211.1501000: 100%  [3/3] Upgrading sysctlinfo-kmod from 20221211.1500068_1 to 20221211.1501000_1...  [3/3] Extracting sysctlinfo-kmod-20221211.1501000_1: 100% 

    We’ve verified that there are no .pkgnew files in both /etc and /usr/local/etc directories during the upgrade. Those files are created when the package manager is unable to merge the configuration files safely.

     aptivi@fbsd-apt:~ $ sudo find /etc /usr/local/etc -name '*.pkgnew' -ls  aptivi@fbsd-apt:~ $ 

    Now, we can update the bootloader. First, we’ve verified that the UEFI boot method is used by querying machdep.bootmethod using the sysctl command, which returned UEFI. Then, checked both the boot entry and the primary disk to ensure that we’ve found the correct EFI partition to mount.

     aptivi@fbsd-apt:~ $ sysctl machdep.bootmethod  machdep.bootmethod: UEFI  aptivi@fbsd-apt:~ $ sudo efibootmgr -v  Boot to FW : false  BootCurrent: 0000  BootOrder  : 0000, 0001, 0002, 0003  +Boot0000* EFI VMware Virtual SCSI Hard Drive (0.0) PciRoot(0x0)/Pci(0x10,0x0)/Scsi(0x0,0x0)  aptivi@fbsd-apt:~ $ sudo gpart show da0  =>       40  524287920  da0  GPT  (250G)           40       1024    1  freebsd-boot  (512K)         1064  515898368    2  freebsd-ufs  (246G)    515899432    7168000    3  freebsd-swap  (3.4G)    523067432    1220528    4  efi  (596M) 

    Since we’ve already set up /etc/fstab to automatically mount the EFI partition on startup under the /boot/efi mountpoint, we can update the bootloader easily. If your EFI partition isn’t automatically mounted, you can mount it by running sudo mount_msdosfs /dev/da0p4 /boot/efi, assuming that da0p4 is the correct partition.

     aptivi@fbsd-apt:~ $ mount  /dev/da0p2 on / (ufs, local, soft-updates, journaled soft-updates)  devfs on /dev (devfs)  /dev/da0p4 on /boot/efi (msdosfs, local) 

    Afterwards, we’ve copied the bootloader EFI file to the correct destination, which was /boot/efi/EFI/BOOT/ in our case, and verified that the copy went through. We have no /boot/efi/EFI/FreeBSD directory, so we’ve skipped that.

     aptivi@fbsd-apt:~ $ sudo cp /boot/loader.efi /boot/efi/EFI/BOOT/BOOTX64.EFI  aptivi@fbsd-apt:~ $ ls -l /boot/loader.efi /boot/efi/EFI/BOOT/BOOTX64.EFI  -rwxr-xr-x  1 root wheel 665600 Jun 16 18:05 /boot/efi/EFI/BOOT/BOOTX64.EFI  -r-xr-xr-x  2 root wheel 665600 Jun 12 03:37 /boot/loader.efi 

    Finally, we’ve rebooted the FreeBSD system. If everything went fine, you should be able to see that it’s now running FreeBSD 15.1 instead of 15.0:

     aptivi@fbsd-apt:~ $ uname -a ; freebsd-version  FreeBSD fbsd-apt.aptivi.net 15.1-RELEASE FreeBSD 15.1-RELEASE releng/15.1-n283562-96841ea08dcf GENERIC amd64  15.1-RELEASE 

    We’ve experimented a little with this newly-upgraded FreeBSD 15.1 system, which has .NET 10.0 installed, and the basic console app building and running still works:

     aptivi@fbsd-apt:~ $ cd dotnet_test/  aptivi@fbsd-apt:~/dotnet_test $ mkdir hello  aptivi@fbsd-apt:~/dotnet_test $ cd hello  aptivi@fbsd-apt:~/dotnet_test/hello $ dotnet new console --use-program-main  The template "Console App" was created successfully.   Processing post-creation actions...  Restoring /home/aptivi/dotnet_test/hello/hello.csproj:  Restore succeeded.    aptivi@fbsd-apt:~/dotnet_test/hello $ dotnet run  Hello, World! 
    #FreeBSD #FreeBSD15 #FreeBSD150 #FreeBSD151 #news #Tech #Technology #update
  15. Upgrading FreeBSD PKGBASE system from FreeBSD v15.0 to v15.1

    FreeBSD 15.1 was released today, and it brought some of the security fixes that were essential to keep your system secure, as well as introducing other improvements to the operating system to improve your user experience.

    Our first test system was upgraded earlier to FreeBSD 15.1 BETA2 from FreeBSD 15.0, and it was using the EFI boot method that we’ve converted from BIOS using this method. Now, we’ve upgraded our second test system, which used to run FreeBSD 15.0, to the stable version of FreeBSD 15.1, and it’s using the UFS file system.

    To perform this upgrade, we’ve followed the steps from the official FreeBSD documentation. Here’s our experience in upgrading this test system.

    WARNING: The first step that talks about taking a recursive snapshot of the FreeBSD installation, which is sudo bectl create -r pre-15.1, doesn’t work with UFS. In our case, it immediately failed with libbe_init("") failed. If you’re running into the same error message, and your FreeBSD file system is UFS, ignore this error.

    First, we’ve upgraded the package manager, which was essential to allow the upgrade to start.

     aptivi@fbsd-apt:~ $ sudo pkg upgrade -yr FreeBSD-ports pkg  Updating FreeBSD-ports repository catalogue...  Fetching data: 100%    10 MiB  60.3 kB/s    03:02  Processing entries: 100%  FreeBSD-ports repository update completed. 37064 packages processed.  FreeBSD-ports is up to date.  Checking integrity... done (0 conflicting)  Your packages are up to date. 

    The package manager is already up to date! So, we’ve decided to upgrade the base system like this. Please note that both the ABI and the OSVERSION options are necessary so that we can tell the package manager that we’re upgrading the base system packages (-r FreeBSD-base) to FreeBSD version 15.1.

     aptivi@fbsd-apt:~ $ sudo pkg -oABI=FreeBSD:15:$(uname -p) -oOSVERSION=1501000 upgrade -r FreeBSD-base  Updating FreeBSD-base repository catalogue...  pkg: Repository FreeBSD-base has a wrong packagesite, need to re-create database  Fetching meta.conf: 100%     179 B   0.2 kB/s    00:01  Fetching data: 100%    82 KiB  83.8 kB/s    00:01  Processing entries: 100%  FreeBSD-base repository update completed. 509 packages processed.  FreeBSD-base is up to date.  Checking for upgrades (308 candidates): 100%  Processing candidates (308 candidates): 100%  The following 318 package(s) will be affected (of 0 checked):   New packages to be INSTALLED:          FreeBSD-pam: 15.1 [FreeBSD-base]          FreeBSD-pam-dev: 15.1 [FreeBSD-base]          FreeBSD-pam-dev-lib32: 15.1 [FreeBSD-base]          FreeBSD-pam-lib: 15.1 [FreeBSD-base]          FreeBSD-pam-lib32: 15.1 [FreeBSD-base]          FreeBSD-zstd: 15.1 [FreeBSD-base]          FreeBSD-zstd-dev: 15.1 [FreeBSD-base]          FreeBSD-zstd-dev-lib32: 15.1 [FreeBSD-base]          FreeBSD-zstd-lib: 15.1 [FreeBSD-base]          FreeBSD-zstd-lib32: 15.1 [FreeBSD-base]   Installed packages to be UPGRADED:          FreeBSD-acct: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-acpi: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-apm: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-at: 15.0 -> 15.1 [FreeBSD-base]   [...]           FreeBSD-zlib-dev-lib32: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-zlib-lib32: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-zoneinfo: 15.0 -> 15.1 [FreeBSD-base]   Number of packages to be installed: 10  Number of packages to be upgraded: 308   The operation will free 1 MiB.  285 MiB to be downloaded.   Proceed with this action? [y/N]: y  [  1/318] Fetching FreeBSD-ctf-dev-15.1: 100%   138 KiB 141.1 kB/s    00:01  [  2/318] Fetching FreeBSD-nvme-tools-15.1: 100%    84 KiB  85.9 kB/s    00:01    [  3/318] Fetching FreeBSD-ntp-15.1: 100%  1904 KiB   2.0 MB/s    00:01  [  4/318] Fetching FreeBSD-bsdconfig-15.1: 100%   184 KiB 188.8 kB/s    00:01     [  5/318] Fetching FreeBSD-tcpd-dev-15.1: 100%    65 KiB  67.0 kB/s    00:01  [  6/318] Fetching FreeBSD-atf-lib-15.1: 100%    67 KiB  68.8 kB/s    00:01  [  7/318] Fetching FreeBSD-netmap-15.1: 100%    18 KiB  17.9 kB/s    00:01   [...]   [318/323] Upgrading FreeBSD-set-minimal from 15.0 to 15.1...  [319/323] Upgrading FreeBSD-xz-lib32 from 15.0 to 15.1...  [319/323] Extracting FreeBSD-xz-lib32-15.1: 100%  [320/323] Upgrading FreeBSD-set-lib32 from 15.0 to 15.1...  [321/323] Upgrading FreeBSD-yp from 15.0 to 15.1...  [321/323] Extracting FreeBSD-yp-15.1: 100%  [322/323] Installing FreeBSD-set-optional-15.1...  [323/323] Installing FreeBSD-set-base-15.1...  ==> Running trigger: mandoc.ucl  Generating apropos(1) database for /usr/share/man...  Generating apropos(1) database for /usr/share/openssl/man...  =====  Message from FreeBSD-local-unbound-15.1:   --  After upgrading local-unbound, the configuration file should be regenerated  by running "service local_unbound setup" before restarting the service. 

    The upgrade has finished successfully with no errors. At this point, all base packages are now upgraded to version 15.1, including the kernel and the base system packages. However, we need to upgrade the third-party kernel modules so that they become compatible with the newer kernel.

     aptivi@fbsd-apt:~ $ sudo pkg upgrade -r FreeBSD-ports-kmods  Password:  Updating FreeBSD-ports-kmods repository catalogue...  pkg: Repository FreeBSD-ports-kmods has a wrong packagesite, need to re-create database  Fetching meta.conf: 100%     179 B   0.2 kB/s    00:01  Fetching data: 100%    35 KiB  35.6 kB/s    00:01  Processing entries: 100%  FreeBSD-ports-kmods repository update completed. 239 packages processed.  FreeBSD-ports-kmods is up to date.  Checking for upgrades (3 candidates): 100%  Processing candidates (3 candidates): 100%  The following 3 package(s) will be affected (of 0 checked):   Installed packages to be UPGRADED:          open-vm-kmod: 13.0.10.1500068,2 -> 13.0.10.1501000,2 [FreeBSD-ports-kmods]          sysctlbyname-improved-kmod: 20221211.1500068 -> 20221211.1501000 [FreeBSD-ports-kmods]          sysctlinfo-kmod: 20221211.1500068_1 -> 20221211.1501000_1 [FreeBSD-ports-kmods]   Number of packages to be upgraded: 3   44 KiB to be downloaded.   Proceed with this action? [y/N]: y  [1/3] Fetching sysctlbyname-improved-kmod-20221211.1501000: 100%    6481 B   6.5 kB/s    00:01  [2/3] Fetching open-vm-kmod-13.0.10.1501000,2: 100%    23 KiB  23.7 kB/s    00:01  [3/3] Fetching sysctlinfo-kmod-20221211.1501000_1: 100%    14 KiB  14.8 kB/s    00:01  Checking integrity... done (0 conflicting)  [1/3] Upgrading open-vm-kmod from 13.0.10.1500068,2 to 13.0.10.1501000,2...  [1/3] Extracting open-vm-kmod-13.0.10.1501000,2: 100%  [2/3] Upgrading sysctlbyname-improved-kmod from 20221211.1500068 to 20221211.1501000...  [2/3] Extracting sysctlbyname-improved-kmod-20221211.1501000: 100%  [3/3] Upgrading sysctlinfo-kmod from 20221211.1500068_1 to 20221211.1501000_1...  [3/3] Extracting sysctlinfo-kmod-20221211.1501000_1: 100% 

    We’ve verified that there are no .pkgnew files in both /etc and /usr/local/etc directories during the upgrade. Those files are created when the package manager is unable to merge the configuration files safely.

     aptivi@fbsd-apt:~ $ sudo find /etc /usr/local/etc -name '*.pkgnew' -ls  aptivi@fbsd-apt:~ $ 

    Now, we can update the bootloader. First, we’ve verified that the UEFI boot method is used by querying machdep.bootmethod using the sysctl command, which returned UEFI. Then, checked both the boot entry and the primary disk to ensure that we’ve found the correct EFI partition to mount.

     aptivi@fbsd-apt:~ $ sysctl machdep.bootmethod  machdep.bootmethod: UEFI  aptivi@fbsd-apt:~ $ sudo efibootmgr -v  Boot to FW : false  BootCurrent: 0000  BootOrder  : 0000, 0001, 0002, 0003  +Boot0000* EFI VMware Virtual SCSI Hard Drive (0.0) PciRoot(0x0)/Pci(0x10,0x0)/Scsi(0x0,0x0)  aptivi@fbsd-apt:~ $ sudo gpart show da0  =>       40  524287920  da0  GPT  (250G)           40       1024    1  freebsd-boot  (512K)         1064  515898368    2  freebsd-ufs  (246G)    515899432    7168000    3  freebsd-swap  (3.4G)    523067432    1220528    4  efi  (596M) 

    Since we’ve already set up /etc/fstab to automatically mount the EFI partition on startup under the /boot/efi mountpoint, we can update the bootloader easily. If your EFI partition isn’t automatically mounted, you can mount it by running sudo mount_msdosfs /dev/da0p4 /boot/efi, assuming that da0p4 is the correct partition.

     aptivi@fbsd-apt:~ $ mount  /dev/da0p2 on / (ufs, local, soft-updates, journaled soft-updates)  devfs on /dev (devfs)  /dev/da0p4 on /boot/efi (msdosfs, local) 

    Afterwards, we’ve copied the bootloader EFI file to the correct destination, which was /boot/efi/EFI/BOOT/ in our case, and verified that the copy went through. We have no /boot/efi/EFI/FreeBSD directory, so we’ve skipped that.

     aptivi@fbsd-apt:~ $ sudo cp /boot/loader.efi /boot/efi/EFI/BOOT/BOOTX64.EFI  aptivi@fbsd-apt:~ $ ls -l /boot/loader.efi /boot/efi/EFI/BOOT/BOOTX64.EFI  -rwxr-xr-x  1 root wheel 665600 Jun 16 18:05 /boot/efi/EFI/BOOT/BOOTX64.EFI  -r-xr-xr-x  2 root wheel 665600 Jun 12 03:37 /boot/loader.efi 

    Finally, we’ve rebooted the FreeBSD system. If everything went fine, you should be able to see that it’s now running FreeBSD 15.1 instead of 15.0:

     aptivi@fbsd-apt:~ $ uname -a ; freebsd-version  FreeBSD fbsd-apt.aptivi.net 15.1-RELEASE FreeBSD 15.1-RELEASE releng/15.1-n283562-96841ea08dcf GENERIC amd64  15.1-RELEASE 

    We’ve experimented a little with this newly-upgraded FreeBSD 15.1 system, which has .NET 10.0 installed, and the basic console app building and running still works:

     aptivi@fbsd-apt:~ $ cd dotnet_test/  aptivi@fbsd-apt:~/dotnet_test $ mkdir hello  aptivi@fbsd-apt:~/dotnet_test $ cd hello  aptivi@fbsd-apt:~/dotnet_test/hello $ dotnet new console --use-program-main  The template "Console App" was created successfully.   Processing post-creation actions...  Restoring /home/aptivi/dotnet_test/hello/hello.csproj:  Restore succeeded.    aptivi@fbsd-apt:~/dotnet_test/hello $ dotnet run  Hello, World! 
    #FreeBSD #FreeBSD15 #FreeBSD150 #FreeBSD151 #news #Tech #Technology #update
  16. Upgrading FreeBSD PKGBASE system from FreeBSD v15.0 to v15.1

    FreeBSD 15.1 was released today, and it brought some of the security fixes that were essential to keep your system secure, as well as introducing other improvements to the operating system to improve your user experience.

    Our first test system was upgraded earlier to FreeBSD 15.1 BETA2 from FreeBSD 15.0, and it was using the EFI boot method that we’ve converted from BIOS using this method. Now, we’ve upgraded our second test system, which used to run FreeBSD 15.0, to the stable version of FreeBSD 15.1, and it’s using the UFS file system.

    To perform this upgrade, we’ve followed the steps from the official FreeBSD documentation. Here’s our experience in upgrading this test system.

    WARNING: The first step that talks about taking a recursive snapshot of the FreeBSD installation, which is sudo bectl create -r pre-15.1, doesn’t work with UFS. In our case, it immediately failed with libbe_init("") failed. If you’re running into the same error message, and your FreeBSD file system is UFS, ignore this error.

    First, we’ve upgraded the package manager, which was essential to allow the upgrade to start.

     aptivi@fbsd-apt:~ $ sudo pkg upgrade -yr FreeBSD-ports pkg  Updating FreeBSD-ports repository catalogue...  Fetching data: 100%    10 MiB  60.3 kB/s    03:02  Processing entries: 100%  FreeBSD-ports repository update completed. 37064 packages processed.  FreeBSD-ports is up to date.  Checking integrity... done (0 conflicting)  Your packages are up to date. 

    The package manager is already up to date! So, we’ve decided to upgrade the base system like this. Please note that both the ABI and the OSVERSION options are necessary so that we can tell the package manager that we’re upgrading the base system packages (-r FreeBSD-base) to FreeBSD version 15.1.

     aptivi@fbsd-apt:~ $ sudo pkg -oABI=FreeBSD:15:$(uname -p) -oOSVERSION=1501000 upgrade -r FreeBSD-base  Updating FreeBSD-base repository catalogue...  pkg: Repository FreeBSD-base has a wrong packagesite, need to re-create database  Fetching meta.conf: 100%     179 B   0.2 kB/s    00:01  Fetching data: 100%    82 KiB  83.8 kB/s    00:01  Processing entries: 100%  FreeBSD-base repository update completed. 509 packages processed.  FreeBSD-base is up to date.  Checking for upgrades (308 candidates): 100%  Processing candidates (308 candidates): 100%  The following 318 package(s) will be affected (of 0 checked):   New packages to be INSTALLED:          FreeBSD-pam: 15.1 [FreeBSD-base]          FreeBSD-pam-dev: 15.1 [FreeBSD-base]          FreeBSD-pam-dev-lib32: 15.1 [FreeBSD-base]          FreeBSD-pam-lib: 15.1 [FreeBSD-base]          FreeBSD-pam-lib32: 15.1 [FreeBSD-base]          FreeBSD-zstd: 15.1 [FreeBSD-base]          FreeBSD-zstd-dev: 15.1 [FreeBSD-base]          FreeBSD-zstd-dev-lib32: 15.1 [FreeBSD-base]          FreeBSD-zstd-lib: 15.1 [FreeBSD-base]          FreeBSD-zstd-lib32: 15.1 [FreeBSD-base]   Installed packages to be UPGRADED:          FreeBSD-acct: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-acpi: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-apm: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-at: 15.0 -> 15.1 [FreeBSD-base]   [...]           FreeBSD-zlib-dev-lib32: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-zlib-lib32: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-zoneinfo: 15.0 -> 15.1 [FreeBSD-base]   Number of packages to be installed: 10  Number of packages to be upgraded: 308   The operation will free 1 MiB.  285 MiB to be downloaded.   Proceed with this action? [y/N]: y  [  1/318] Fetching FreeBSD-ctf-dev-15.1: 100%   138 KiB 141.1 kB/s    00:01  [  2/318] Fetching FreeBSD-nvme-tools-15.1: 100%    84 KiB  85.9 kB/s    00:01    [  3/318] Fetching FreeBSD-ntp-15.1: 100%  1904 KiB   2.0 MB/s    00:01  [  4/318] Fetching FreeBSD-bsdconfig-15.1: 100%   184 KiB 188.8 kB/s    00:01     [  5/318] Fetching FreeBSD-tcpd-dev-15.1: 100%    65 KiB  67.0 kB/s    00:01  [  6/318] Fetching FreeBSD-atf-lib-15.1: 100%    67 KiB  68.8 kB/s    00:01  [  7/318] Fetching FreeBSD-netmap-15.1: 100%    18 KiB  17.9 kB/s    00:01   [...]   [318/323] Upgrading FreeBSD-set-minimal from 15.0 to 15.1...  [319/323] Upgrading FreeBSD-xz-lib32 from 15.0 to 15.1...  [319/323] Extracting FreeBSD-xz-lib32-15.1: 100%  [320/323] Upgrading FreeBSD-set-lib32 from 15.0 to 15.1...  [321/323] Upgrading FreeBSD-yp from 15.0 to 15.1...  [321/323] Extracting FreeBSD-yp-15.1: 100%  [322/323] Installing FreeBSD-set-optional-15.1...  [323/323] Installing FreeBSD-set-base-15.1...  ==> Running trigger: mandoc.ucl  Generating apropos(1) database for /usr/share/man...  Generating apropos(1) database for /usr/share/openssl/man...  =====  Message from FreeBSD-local-unbound-15.1:   --  After upgrading local-unbound, the configuration file should be regenerated  by running "service local_unbound setup" before restarting the service. 

    The upgrade has finished successfully with no errors. At this point, all base packages are now upgraded to version 15.1, including the kernel and the base system packages. However, we need to upgrade the third-party kernel modules so that they become compatible with the newer kernel.

     aptivi@fbsd-apt:~ $ sudo pkg upgrade -r FreeBSD-ports-kmods  Password:  Updating FreeBSD-ports-kmods repository catalogue...  pkg: Repository FreeBSD-ports-kmods has a wrong packagesite, need to re-create database  Fetching meta.conf: 100%     179 B   0.2 kB/s    00:01  Fetching data: 100%    35 KiB  35.6 kB/s    00:01  Processing entries: 100%  FreeBSD-ports-kmods repository update completed. 239 packages processed.  FreeBSD-ports-kmods is up to date.  Checking for upgrades (3 candidates): 100%  Processing candidates (3 candidates): 100%  The following 3 package(s) will be affected (of 0 checked):   Installed packages to be UPGRADED:          open-vm-kmod: 13.0.10.1500068,2 -> 13.0.10.1501000,2 [FreeBSD-ports-kmods]          sysctlbyname-improved-kmod: 20221211.1500068 -> 20221211.1501000 [FreeBSD-ports-kmods]          sysctlinfo-kmod: 20221211.1500068_1 -> 20221211.1501000_1 [FreeBSD-ports-kmods]   Number of packages to be upgraded: 3   44 KiB to be downloaded.   Proceed with this action? [y/N]: y  [1/3] Fetching sysctlbyname-improved-kmod-20221211.1501000: 100%    6481 B   6.5 kB/s    00:01  [2/3] Fetching open-vm-kmod-13.0.10.1501000,2: 100%    23 KiB  23.7 kB/s    00:01  [3/3] Fetching sysctlinfo-kmod-20221211.1501000_1: 100%    14 KiB  14.8 kB/s    00:01  Checking integrity... done (0 conflicting)  [1/3] Upgrading open-vm-kmod from 13.0.10.1500068,2 to 13.0.10.1501000,2...  [1/3] Extracting open-vm-kmod-13.0.10.1501000,2: 100%  [2/3] Upgrading sysctlbyname-improved-kmod from 20221211.1500068 to 20221211.1501000...  [2/3] Extracting sysctlbyname-improved-kmod-20221211.1501000: 100%  [3/3] Upgrading sysctlinfo-kmod from 20221211.1500068_1 to 20221211.1501000_1...  [3/3] Extracting sysctlinfo-kmod-20221211.1501000_1: 100% 

    We’ve verified that there are no .pkgnew files in both /etc and /usr/local/etc directories during the upgrade. Those files are created when the package manager is unable to merge the configuration files safely.

     aptivi@fbsd-apt:~ $ sudo find /etc /usr/local/etc -name '*.pkgnew' -ls  aptivi@fbsd-apt:~ $ 

    Now, we can update the bootloader. First, we’ve verified that the UEFI boot method is used by querying machdep.bootmethod using the sysctl command, which returned UEFI. Then, checked both the boot entry and the primary disk to ensure that we’ve found the correct EFI partition to mount.

     aptivi@fbsd-apt:~ $ sysctl machdep.bootmethod  machdep.bootmethod: UEFI  aptivi@fbsd-apt:~ $ sudo efibootmgr -v  Boot to FW : false  BootCurrent: 0000  BootOrder  : 0000, 0001, 0002, 0003  +Boot0000* EFI VMware Virtual SCSI Hard Drive (0.0) PciRoot(0x0)/Pci(0x10,0x0)/Scsi(0x0,0x0)  aptivi@fbsd-apt:~ $ sudo gpart show da0  =>       40  524287920  da0  GPT  (250G)           40       1024    1  freebsd-boot  (512K)         1064  515898368    2  freebsd-ufs  (246G)    515899432    7168000    3  freebsd-swap  (3.4G)    523067432    1220528    4  efi  (596M) 

    Since we’ve already set up /etc/fstab to automatically mount the EFI partition on startup under the /boot/efi mountpoint, we can update the bootloader easily. If your EFI partition isn’t automatically mounted, you can mount it by running sudo mount_msdosfs /dev/da0p4 /boot/efi, assuming that da0p4 is the correct partition.

     aptivi@fbsd-apt:~ $ mount  /dev/da0p2 on / (ufs, local, soft-updates, journaled soft-updates)  devfs on /dev (devfs)  /dev/da0p4 on /boot/efi (msdosfs, local) 

    Afterwards, we’ve copied the bootloader EFI file to the correct destination, which was /boot/efi/EFI/BOOT/ in our case, and verified that the copy went through. We have no /boot/efi/EFI/FreeBSD directory, so we’ve skipped that.

     aptivi@fbsd-apt:~ $ sudo cp /boot/loader.efi /boot/efi/EFI/BOOT/BOOTX64.EFI  aptivi@fbsd-apt:~ $ ls -l /boot/loader.efi /boot/efi/EFI/BOOT/BOOTX64.EFI  -rwxr-xr-x  1 root wheel 665600 Jun 16 18:05 /boot/efi/EFI/BOOT/BOOTX64.EFI  -r-xr-xr-x  2 root wheel 665600 Jun 12 03:37 /boot/loader.efi 

    Finally, we’ve rebooted the FreeBSD system. If everything went fine, you should be able to see that it’s now running FreeBSD 15.1 instead of 15.0:

     aptivi@fbsd-apt:~ $ uname -a ; freebsd-version  FreeBSD fbsd-apt.aptivi.net 15.1-RELEASE FreeBSD 15.1-RELEASE releng/15.1-n283562-96841ea08dcf GENERIC amd64  15.1-RELEASE 

    We’ve experimented a little with this newly-upgraded FreeBSD 15.1 system, which has .NET 10.0 installed, and the basic console app building and running still works:

     aptivi@fbsd-apt:~ $ cd dotnet_test/  aptivi@fbsd-apt:~/dotnet_test $ mkdir hello  aptivi@fbsd-apt:~/dotnet_test $ cd hello  aptivi@fbsd-apt:~/dotnet_test/hello $ dotnet new console --use-program-main  The template "Console App" was created successfully.   Processing post-creation actions...  Restoring /home/aptivi/dotnet_test/hello/hello.csproj:  Restore succeeded.    aptivi@fbsd-apt:~/dotnet_test/hello $ dotnet run  Hello, World! 
    #FreeBSD #FreeBSD15 #FreeBSD150 #FreeBSD151 #news #Tech #Technology #update
  17. Upgrading FreeBSD PKGBASE system from FreeBSD v15.0 to v15.1

    FreeBSD 15.1 was released today, and it brought some of the security fixes that were essential to keep your system secure, as well as introducing other improvements to the operating system to improve your user experience.

    Our first test system was upgraded earlier to FreeBSD 15.1 BETA2 from FreeBSD 15.0, and it was using the EFI boot method that we’ve converted from BIOS using this method. Now, we’ve upgraded our second test system, which used to run FreeBSD 15.0, to the stable version of FreeBSD 15.1, and it’s using the UFS file system.

    To perform this upgrade, we’ve followed the steps from the official FreeBSD documentation. Here’s our experience in upgrading this test system.

    WARNING: The first step that talks about taking a recursive snapshot of the FreeBSD installation, which is sudo bectl create -r pre-15.1, doesn’t work with UFS. In our case, it immediately failed with libbe_init("") failed. If you’re running into the same error message, and your FreeBSD file system is UFS, ignore this error.

    First, we’ve upgraded the package manager, which was essential to allow the upgrade to start.

     aptivi@fbsd-apt:~ $ sudo pkg upgrade -yr FreeBSD-ports pkg  Updating FreeBSD-ports repository catalogue...  Fetching data: 100%    10 MiB  60.3 kB/s    03:02  Processing entries: 100%  FreeBSD-ports repository update completed. 37064 packages processed.  FreeBSD-ports is up to date.  Checking integrity... done (0 conflicting)  Your packages are up to date. 

    The package manager is already up to date! So, we’ve decided to upgrade the base system like this. Please note that both the ABI and the OSVERSION options are necessary so that we can tell the package manager that we’re upgrading the base system packages (-r FreeBSD-base) to FreeBSD version 15.1.

     aptivi@fbsd-apt:~ $ sudo pkg -oABI=FreeBSD:15:$(uname -p) -oOSVERSION=1501000 upgrade -r FreeBSD-base  Updating FreeBSD-base repository catalogue...  pkg: Repository FreeBSD-base has a wrong packagesite, need to re-create database  Fetching meta.conf: 100%     179 B   0.2 kB/s    00:01  Fetching data: 100%    82 KiB  83.8 kB/s    00:01  Processing entries: 100%  FreeBSD-base repository update completed. 509 packages processed.  FreeBSD-base is up to date.  Checking for upgrades (308 candidates): 100%  Processing candidates (308 candidates): 100%  The following 318 package(s) will be affected (of 0 checked):   New packages to be INSTALLED:          FreeBSD-pam: 15.1 [FreeBSD-base]          FreeBSD-pam-dev: 15.1 [FreeBSD-base]          FreeBSD-pam-dev-lib32: 15.1 [FreeBSD-base]          FreeBSD-pam-lib: 15.1 [FreeBSD-base]          FreeBSD-pam-lib32: 15.1 [FreeBSD-base]          FreeBSD-zstd: 15.1 [FreeBSD-base]          FreeBSD-zstd-dev: 15.1 [FreeBSD-base]          FreeBSD-zstd-dev-lib32: 15.1 [FreeBSD-base]          FreeBSD-zstd-lib: 15.1 [FreeBSD-base]          FreeBSD-zstd-lib32: 15.1 [FreeBSD-base]   Installed packages to be UPGRADED:          FreeBSD-acct: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-acpi: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-apm: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-at: 15.0 -> 15.1 [FreeBSD-base]   [...]           FreeBSD-zlib-dev-lib32: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-zlib-lib32: 15.0 -> 15.1 [FreeBSD-base]          FreeBSD-zoneinfo: 15.0 -> 15.1 [FreeBSD-base]   Number of packages to be installed: 10  Number of packages to be upgraded: 308   The operation will free 1 MiB.  285 MiB to be downloaded.   Proceed with this action? [y/N]: y  [  1/318] Fetching FreeBSD-ctf-dev-15.1: 100%   138 KiB 141.1 kB/s    00:01  [  2/318] Fetching FreeBSD-nvme-tools-15.1: 100%    84 KiB  85.9 kB/s    00:01    [  3/318] Fetching FreeBSD-ntp-15.1: 100%  1904 KiB   2.0 MB/s    00:01  [  4/318] Fetching FreeBSD-bsdconfig-15.1: 100%   184 KiB 188.8 kB/s    00:01     [  5/318] Fetching FreeBSD-tcpd-dev-15.1: 100%    65 KiB  67.0 kB/s    00:01  [  6/318] Fetching FreeBSD-atf-lib-15.1: 100%    67 KiB  68.8 kB/s    00:01  [  7/318] Fetching FreeBSD-netmap-15.1: 100%    18 KiB  17.9 kB/s    00:01   [...]   [318/323] Upgrading FreeBSD-set-minimal from 15.0 to 15.1...  [319/323] Upgrading FreeBSD-xz-lib32 from 15.0 to 15.1...  [319/323] Extracting FreeBSD-xz-lib32-15.1: 100%  [320/323] Upgrading FreeBSD-set-lib32 from 15.0 to 15.1...  [321/323] Upgrading FreeBSD-yp from 15.0 to 15.1...  [321/323] Extracting FreeBSD-yp-15.1: 100%  [322/323] Installing FreeBSD-set-optional-15.1...  [323/323] Installing FreeBSD-set-base-15.1...  ==> Running trigger: mandoc.ucl  Generating apropos(1) database for /usr/share/man...  Generating apropos(1) database for /usr/share/openssl/man...  =====  Message from FreeBSD-local-unbound-15.1:   --  After upgrading local-unbound, the configuration file should be regenerated  by running "service local_unbound setup" before restarting the service. 

    The upgrade has finished successfully with no errors. At this point, all base packages are now upgraded to version 15.1, including the kernel and the base system packages. However, we need to upgrade the third-party kernel modules so that they become compatible with the newer kernel.

     aptivi@fbsd-apt:~ $ sudo pkg upgrade -r FreeBSD-ports-kmods  Password:  Updating FreeBSD-ports-kmods repository catalogue...  pkg: Repository FreeBSD-ports-kmods has a wrong packagesite, need to re-create database  Fetching meta.conf: 100%     179 B   0.2 kB/s    00:01  Fetching data: 100%    35 KiB  35.6 kB/s    00:01  Processing entries: 100%  FreeBSD-ports-kmods repository update completed. 239 packages processed.  FreeBSD-ports-kmods is up to date.  Checking for upgrades (3 candidates): 100%  Processing candidates (3 candidates): 100%  The following 3 package(s) will be affected (of 0 checked):   Installed packages to be UPGRADED:          open-vm-kmod: 13.0.10.1500068,2 -> 13.0.10.1501000,2 [FreeBSD-ports-kmods]          sysctlbyname-improved-kmod: 20221211.1500068 -> 20221211.1501000 [FreeBSD-ports-kmods]          sysctlinfo-kmod: 20221211.1500068_1 -> 20221211.1501000_1 [FreeBSD-ports-kmods]   Number of packages to be upgraded: 3   44 KiB to be downloaded.   Proceed with this action? [y/N]: y  [1/3] Fetching sysctlbyname-improved-kmod-20221211.1501000: 100%    6481 B   6.5 kB/s    00:01  [2/3] Fetching open-vm-kmod-13.0.10.1501000,2: 100%    23 KiB  23.7 kB/s    00:01  [3/3] Fetching sysctlinfo-kmod-20221211.1501000_1: 100%    14 KiB  14.8 kB/s    00:01  Checking integrity... done (0 conflicting)  [1/3] Upgrading open-vm-kmod from 13.0.10.1500068,2 to 13.0.10.1501000,2...  [1/3] Extracting open-vm-kmod-13.0.10.1501000,2: 100%  [2/3] Upgrading sysctlbyname-improved-kmod from 20221211.1500068 to 20221211.1501000...  [2/3] Extracting sysctlbyname-improved-kmod-20221211.1501000: 100%  [3/3] Upgrading sysctlinfo-kmod from 20221211.1500068_1 to 20221211.1501000_1...  [3/3] Extracting sysctlinfo-kmod-20221211.1501000_1: 100% 

    We’ve verified that there are no .pkgnew files in both /etc and /usr/local/etc directories during the upgrade. Those files are created when the package manager is unable to merge the configuration files safely.

     aptivi@fbsd-apt:~ $ sudo find /etc /usr/local/etc -name '*.pkgnew' -ls  aptivi@fbsd-apt:~ $ 

    Now, we can update the bootloader. First, we’ve verified that the UEFI boot method is used by querying machdep.bootmethod using the sysctl command, which returned UEFI. Then, checked both the boot entry and the primary disk to ensure that we’ve found the correct EFI partition to mount.

     aptivi@fbsd-apt:~ $ sysctl machdep.bootmethod  machdep.bootmethod: UEFI  aptivi@fbsd-apt:~ $ sudo efibootmgr -v  Boot to FW : false  BootCurrent: 0000  BootOrder  : 0000, 0001, 0002, 0003  +Boot0000* EFI VMware Virtual SCSI Hard Drive (0.0) PciRoot(0x0)/Pci(0x10,0x0)/Scsi(0x0,0x0)  aptivi@fbsd-apt:~ $ sudo gpart show da0  =>       40  524287920  da0  GPT  (250G)           40       1024    1  freebsd-boot  (512K)         1064  515898368    2  freebsd-ufs  (246G)    515899432    7168000    3  freebsd-swap  (3.4G)    523067432    1220528    4  efi  (596M) 

    Since we’ve already set up /etc/fstab to automatically mount the EFI partition on startup under the /boot/efi mountpoint, we can update the bootloader easily. If your EFI partition isn’t automatically mounted, you can mount it by running sudo mount_msdosfs /dev/da0p4 /boot/efi, assuming that da0p4 is the correct partition.

     aptivi@fbsd-apt:~ $ mount  /dev/da0p2 on / (ufs, local, soft-updates, journaled soft-updates)  devfs on /dev (devfs)  /dev/da0p4 on /boot/efi (msdosfs, local) 

    Afterwards, we’ve copied the bootloader EFI file to the correct destination, which was /boot/efi/EFI/BOOT/ in our case, and verified that the copy went through. We have no /boot/efi/EFI/FreeBSD directory, so we’ve skipped that.

     aptivi@fbsd-apt:~ $ sudo cp /boot/loader.efi /boot/efi/EFI/BOOT/BOOTX64.EFI  aptivi@fbsd-apt:~ $ ls -l /boot/loader.efi /boot/efi/EFI/BOOT/BOOTX64.EFI  -rwxr-xr-x  1 root wheel 665600 Jun 16 18:05 /boot/efi/EFI/BOOT/BOOTX64.EFI  -r-xr-xr-x  2 root wheel 665600 Jun 12 03:37 /boot/loader.efi 

    Finally, we’ve rebooted the FreeBSD system. If everything went fine, you should be able to see that it’s now running FreeBSD 15.1 instead of 15.0:

     aptivi@fbsd-apt:~ $ uname -a ; freebsd-version  FreeBSD fbsd-apt.aptivi.net 15.1-RELEASE FreeBSD 15.1-RELEASE releng/15.1-n283562-96841ea08dcf GENERIC amd64  15.1-RELEASE 

    We’ve experimented a little with this newly-upgraded FreeBSD 15.1 system, which has .NET 10.0 installed, and the basic console app building and running still works:

     aptivi@fbsd-apt:~ $ cd dotnet_test/  aptivi@fbsd-apt:~/dotnet_test $ mkdir hello  aptivi@fbsd-apt:~/dotnet_test $ cd hello  aptivi@fbsd-apt:~/dotnet_test/hello $ dotnet new console --use-program-main  The template "Console App" was created successfully.   Processing post-creation actions...  Restoring /home/aptivi/dotnet_test/hello/hello.csproj:  Restore succeeded.    aptivi@fbsd-apt:~/dotnet_test/hello $ dotnet run  Hello, World! 
    #FreeBSD #FreeBSD15 #FreeBSD150 #FreeBSD151 #news #Tech #Technology #update
  18. Upgrading FreeBSD 15.0-STABLE to 15.1-BETA2 (PKGBASE system)

    Recently, an article about upgrading the FreeBSD 15.0-STABLE system to the 15.1-BETA2 version has been posted, because the PKGBASE system installations of FreeBSD are still in experimental stages. One of the biggest missing features is the ability to reliably upgrade the FreeBSD system to newer versions, such as from 15.0 to 15.1.

    The release engineering team stated that this part was overlooked, and that they were working on it for PKGBASE systems. A solution has then been posted in the linked article, as discovered by vermaden, involving ZFS boot environments for those who are using ZFS on their FreeBSD installation.

    https://vermaden.wordpress.com/2026/05/10/freebsd-pkgbase-minor-upgrades/

    The solution above involved ZFS boot environments, administered by the beadm tool. The older freebsd-update tool had the ability to upgrade your FreeBSD installation to new minor releases, but the PKGBASE world didn’t benefit from this convenience. Therefore, we have adapted the solution to use the commands similar to what was listed in this message posted to the mailing list.

    WARNING: Before you attempt to do this, please make sure that you take a complete backup of your system, in case something goes wrong during the upgrade. The steps were done on a test machine where no crucial data was stored, therefore, no ZFS snapshots or boot environments were made, so please proceed at your own risk. Beta software is unstable and may contain more bugs than the final version.

    First of all, you’ll have to either use sudo or to log in as root. In this article, we have chosen sudo as it not only runs a single command as a super user, but it’s also a good practice in general to avoid logging in as root for everyday activities.

    After that, make sure that pkg is up to date before you continue. You’ll need to run sudo pkg upgrade pkg to upgrade the package manager itself.

    Once the upgrade of the package manager succeeds, run the below command to upgrade all packages from the FreeBSD-ports-kmods repository catalog.

     aptivi@apt-freebsd-01:~ $ sudo pkg -o ABI=FreeBSD:15:$(sysctl -n hw.machine_arch) -o OSVERSION=1501000 upgrade -yr FreeBSD-ports-kmods  Password:  Updating FreeBSD-ports-kmods repository catalogue...  pkg: Repository FreeBSD-ports-kmods has a wrong packagesite, need to re-create database  Fetching meta.conf: 100%     179 B   0.2 kB/s    00:01  Fetching data: 100%    36 KiB  36.4 kB/s    00:01  Processing entries: 100%  FreeBSD-ports-kmods repository update completed. 239 packages processed.  FreeBSD-ports-kmods is up to date.  Checking for upgrades (0 candidates): 100%  Processing candidates (0 candidates): 100%  Checking integrity... done (0 conflicting)  Your packages are up to date. 

    Please note that we have added the following switches:

    • -o ABI=FreeBSD:15:$(sysctl -n hw.machine_arch): Specifies the FreeBSD ABI version and architecture. (Before upgrade)
    • -o OSVERSION=1501000: Specifies the explicit operating system version ID (for example, 1501000 resolves to FreeBSD 15.1) (Very important, before upgrade)
    • -y: Runs the upgrade automatically (After upgrade)
    • -r FreeBSD-ports-kmods: Specifies the repository catalog name (Very important, After upgrade)

    After the package upgrades from the above repository catalog succeed, it’s time to upgrade the base system. The output below is truncated because it was very long as all packages needed to be upgraded to 15.1.b2 from 15.0.

     aptivi@apt-freebsd-01:~ $ sudo pkg -o ABI=FreeBSD:15:$(sysctl -n hw.machine_arch) -o OSVERSION=1501000 upgrade -yr FreeBSD-base  Updating FreeBSD-base repository catalogue...  pkg: Repository FreeBSD-base has a wrong packagesite, need to re-create database  Fetching meta.conf: 100%     179 B   0.2 kB/s    00:01  Fetching data: 100%    82 KiB  84.4 kB/s    00:01  Processing entries: 100%  FreeBSD-base repository update completed. 509 packages processed.  FreeBSD-base is up to date.  Checking for upgrades (208 candidates): 100%  Processing candidates (208 candidates): 100%  The following 214 package(s) will be affected (of 0 checked):   New packages to be INSTALLED:          FreeBSD-pam: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-pam-dev: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-pam-lib: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-zstd: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-zstd-dev: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-zstd-lib: 15.1.b2.20260508031850 [FreeBSD-base]   Installed packages to be UPGRADED:          FreeBSD-acct: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-acpi: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-apm: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-at: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-atf: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-atf-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-atf-lib: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-audit: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-audit-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-audit-lib: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-autofs: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bhyve: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-blocklist: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-blocklist-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bluetooth: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bluetooth-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bluetooth-lib: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bmake: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bootloader: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bootloader-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bsdconfig: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bsdinstall: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]  [...]  [206/218] Extracting FreeBSD-ssh-dev-15.1.b2.20260508031850: 100%  [207/218] Upgrading FreeBSD-syscons-data from 15.0 to 15.1.b2.20260508031850...  [207/218] Extracting FreeBSD-syscons-data-15.1.b2.20260508031850: 100%  [208/218] Upgrading FreeBSD-tcpd from 15.0 to 15.1.b2.20260508031850...  [208/218] Extracting FreeBSD-tcpd-15.1.b2.20260508031850: 100%  [209/218] Upgrading FreeBSD-tcpd-dev from 15.0 to 15.1.b2.20260508031850...  [209/218] Extracting FreeBSD-tcpd-dev-15.1.b2.20260508031850: 100%  [210/218] Upgrading FreeBSD-telnet from 15.0 to 15.1.b2.20260508031850...  [210/218] Extracting FreeBSD-telnet-15.1.b2.20260508031850: 100%  [211/218] Upgrading FreeBSD-xz from 15.0 to 15.1.b2.20260508031850...  [211/218] Extracting FreeBSD-xz-15.1.b2.20260508031850: 100%  [212/218] Upgrading FreeBSD-xz-dev from 15.0 to 15.1.b2.20260508031850...  [212/218] Extracting FreeBSD-xz-dev-15.1.b2.20260508031850: 100%  [213/218] Installing FreeBSD-set-devel-15.1.b2.20260508031850...  [214/218] Upgrading FreeBSD-xz-lib from 15.0 to 15.1.b2.20260508031850...  [214/218] Extracting FreeBSD-xz-lib-15.1.b2.20260508031850: 100%  [215/218] Upgrading FreeBSD-set-minimal from 15.0 to 15.1.b2.20260508031850...  [216/218] Upgrading FreeBSD-yp from 15.0 to 15.1.b2.20260508031850...  [216/218] Extracting FreeBSD-yp-15.1.b2.20260508031850: 100%  [217/218] Installing FreeBSD-set-optional-15.1.b2.20260508031850...  [218/218] Installing FreeBSD-set-base-15.1.b2.20260508031850...  ==> Running trigger: mandoc.ucl  Generating apropos(1) database for /usr/share/man...  Generating apropos(1) database for /usr/share/openssl/man...  =====  Message from FreeBSD-local-unbound-15.1.b2.20260508031850:   --  After upgrading local-unbound, the configuration file should be regenerated  by running "service local_unbound setup" before restarting the service.  aptivi@apt-freebsd-01:~ $ 

    One last step is to examine and update the UEFI bootblock, assuming that the FreeBSD system is using UEFI as the boot method. Let’s confirm that the bootloader files have been updated in the /boot directory.

     aptivi@apt-freebsd-01:~ $ ls -l /boot/*.efi  -r-xr-xr-x  1 root wheel 158720 May  8 03:00 /boot/boot1.efi  -r-xr-xr-x  1 root wheel 109568 May  8 03:00 /boot/gptboot.efi  -r-xr-xr-x  2 root wheel 665600 May  8 03:00 /boot/loader.efi  -r--r--r--  1 root wheel  13653 May  8 03:00 /boot/loader.help.efi  -r-xr-xr-x  1 root wheel 580608 May  8 03:00 /boot/loader_4th.efi  -r-xr-xr-x  1 root wheel 622080 May  8 03:00 /boot/loader_ia32.efi  -r-xr-xr-x  2 root wheel 665600 May  8 03:00 /boot/loader_lua.efi  -r-xr-xr-x  1 root wheel 521728 May  8 03:00 /boot/loader_simp.efi  aptivi@apt-freebsd-01:~ $ ls -l /boot/efi/EFI/BOOT/  total 656  -rwxr-xr-x  1 root wheel 665088 May  5 15:24 BOOTX64.EFI 

    Now, we have the updated bootloader files, but the changes didn’t reflect in the ESP partition. So, we’ll need to manually copy the /boot/loader.efi file to overwrite /boot/efi/EFI/BOOT/BOOTX64.EFI, assuming that the ESP partition is automatically mounted via /etc/fstab (or manually sudo mount -t msdosfs /dev/da0p4 /mnt, assuming that da0p4 is the ESP partition) to /boot/efi. You can refer to our past article for more info.

    Execute the below commands:

     aptivi@apt-freebsd-01:~ $ sudo cp /boot/loader.efi /boot/efi/EFI/BOOT/BOOTX64.EFI  Password:  aptivi@apt-freebsd-01:~ $ ls -l /boot/efi/EFI/BOOT/  total 656  -rwxr-xr-x  1 root wheel 665600 May 10 21:51 BOOTX64.EFI 

    Verify that the updated BOOTX64.EFI file has been copied to the ESP.

    Once done, reboot the system using sudo reboot.

    After that, verify that you’re running FreeBSD 15.1-BETA2:

     aptivi@apt-freebsd-01:~ $ uname -a  FreeBSD apt-freebsd-01 15.1-BETA2 FreeBSD 15.1-BETA2 releng/15.1-n283486-b3f9be4f9437 GENERIC amd64 

    …compared to what we had earlier.

     aptivi@apt-freebsd-01:~ $ uname -a  FreeBSD apt-freebsd-01 15.0-RELEASE FreeBSD 15.0-RELEASE releng/15.0-n280995-7aedc8de6446 GENERIC amd64 

    Now, we’re running FreeBSD 15.1 Beta 2! Make sure that pkg is able to install packages afterwards. For example, we’ll install the rsync program in the upgraded system:

     aptivi@apt-freebsd-01:~ $ sudo pkg install rsync  Updating FreeBSD-ports repository catalogue...  FreeBSD-ports repository is up to date.  Updating FreeBSD-ports-kmods repository catalogue...  FreeBSD-ports-kmods repository is up to date.  Updating FreeBSD-base repository catalogue...  FreeBSD-base repository is up to date.  All repositories are up to date.  The following 5 package(s) will be affected (of 0 checked):   New packages to be INSTALLED:          libiconv: 1.18_1 [FreeBSD-ports]          liblz4: 1.10.0_2,1 [FreeBSD-ports]          rsync: 3.4.1_6 [FreeBSD-ports]          xxhash: 0.8.3 [FreeBSD-ports]          zstd: 1.5.7_1 [FreeBSD-ports]   Number of packages to be installed: 5   The process will require 8 MiB more space.  2 MiB to be downloaded.   Proceed with this action? [y/N]: y  [1/5] Fetching libiconv-1.18_1: 100%   741 KiB 252.8 kB/s    00:03  [2/5] Fetching xxhash-0.8.3: 100%   103 KiB 105.4 kB/s    00:01  [3/5] Fetching rsync-3.4.1_6: 100%   396 KiB 202.5 kB/s    00:02  [4/5] Fetching liblz4-1.10.0_2,1: 100%   178 KiB 182.5 kB/s    00:01  [5/5] Fetching zstd-1.5.7_1: 100%   509 KiB 520.9 kB/s    00:01  Checking integrity... done (0 conflicting)  [1/5] Installing libiconv-1.18_1...  [1/5] Extracting libiconv-1.18_1: 100%  [2/5] Installing liblz4-1.10.0_2,1...  [2/5] Extracting liblz4-1.10.0_2,1: 100%  [3/5] Installing xxhash-0.8.3...  [3/5] Extracting xxhash-0.8.3: 100%  [4/5] Installing zstd-1.5.7_1...  [4/5] Extracting zstd-1.5.7_1: 100%  [5/5] Installing rsync-3.4.1_6...  [5/5] Extracting rsync-3.4.1_6: 100% 
    #FreeBSD #FreeBSD15 #FreeBSD150 #FreeBSD151 #news #Tech #Technology #update
  19. Upgrading FreeBSD 15.0-STABLE to 15.1-BETA2 (PKGBASE system)

    Recently, an article about upgrading the FreeBSD 15.0-STABLE system to the 15.1-BETA2 version has been posted, because the PKGBASE system installations of FreeBSD are still in experimental stages. One of the biggest missing features is the ability to reliably upgrade the FreeBSD system to newer versions, such as from 15.0 to 15.1.

    The release engineering team stated that this part was overlooked, and that they were working on it for PKGBASE systems. A solution has then been posted in the linked article, as discovered by vermaden, involving ZFS boot environments for those who are using ZFS on their FreeBSD installation.

    https://vermaden.wordpress.com/2026/05/10/freebsd-pkgbase-minor-upgrades/

    The solution above involved ZFS boot environments, administered by the beadm tool. The older freebsd-update tool had the ability to upgrade your FreeBSD installation to new minor releases, but the PKGBASE world didn’t benefit from this convenience. Therefore, we have adapted the solution to use the commands similar to what was listed in this message posted to the mailing list.

    WARNING: Before you attempt to do this, please make sure that you take a complete backup of your system, in case something goes wrong during the upgrade. The steps were done on a test machine where no crucial data was stored, therefore, no ZFS snapshots or boot environments were made, so please proceed at your own risk. Beta software is unstable and may contain more bugs than the final version.

    First of all, you’ll have to either use sudo or to log in as root. In this article, we have chosen sudo as it not only runs a single command as a super user, but it’s also a good practice in general to avoid logging in as root for everyday activities.

    After that, make sure that pkg is up to date before you continue. You’ll need to run sudo pkg upgrade pkg to upgrade the package manager itself.

    Once the upgrade of the package manager succeeds, run the below command to upgrade all packages from the FreeBSD-ports-kmods repository catalog.

     aptivi@apt-freebsd-01:~ $ sudo pkg -o ABI=FreeBSD:15:$(sysctl -n hw.machine_arch) -o OSVERSION=1501000 upgrade -yr FreeBSD-ports-kmods  Password:  Updating FreeBSD-ports-kmods repository catalogue...  pkg: Repository FreeBSD-ports-kmods has a wrong packagesite, need to re-create database  Fetching meta.conf: 100%     179 B   0.2 kB/s    00:01  Fetching data: 100%    36 KiB  36.4 kB/s    00:01  Processing entries: 100%  FreeBSD-ports-kmods repository update completed. 239 packages processed.  FreeBSD-ports-kmods is up to date.  Checking for upgrades (0 candidates): 100%  Processing candidates (0 candidates): 100%  Checking integrity... done (0 conflicting)  Your packages are up to date. 

    Please note that we have added the following switches:

    • -o ABI=FreeBSD:15:$(sysctl -n hw.machine_arch): Specifies the FreeBSD ABI version and architecture. (Before upgrade)
    • -o OSVERSION=1501000: Specifies the explicit operating system version ID (for example, 1501000 resolves to FreeBSD 15.1) (Very important, before upgrade)
    • -y: Runs the upgrade automatically (After upgrade)
    • -r FreeBSD-ports-kmods: Specifies the repository catalog name (Very important, After upgrade)

    After the package upgrades from the above repository catalog succeed, it’s time to upgrade the base system. The output below is truncated because it was very long as all packages needed to be upgraded to 15.1.b2 from 15.0.

     aptivi@apt-freebsd-01:~ $ sudo pkg -o ABI=FreeBSD:15:$(sysctl -n hw.machine_arch) -o OSVERSION=1501000 upgrade -yr FreeBSD-base  Updating FreeBSD-base repository catalogue...  pkg: Repository FreeBSD-base has a wrong packagesite, need to re-create database  Fetching meta.conf: 100%     179 B   0.2 kB/s    00:01  Fetching data: 100%    82 KiB  84.4 kB/s    00:01  Processing entries: 100%  FreeBSD-base repository update completed. 509 packages processed.  FreeBSD-base is up to date.  Checking for upgrades (208 candidates): 100%  Processing candidates (208 candidates): 100%  The following 214 package(s) will be affected (of 0 checked):   New packages to be INSTALLED:          FreeBSD-pam: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-pam-dev: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-pam-lib: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-zstd: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-zstd-dev: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-zstd-lib: 15.1.b2.20260508031850 [FreeBSD-base]   Installed packages to be UPGRADED:          FreeBSD-acct: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-acpi: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-apm: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-at: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-atf: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-atf-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-atf-lib: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-audit: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-audit-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-audit-lib: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-autofs: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bhyve: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-blocklist: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-blocklist-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bluetooth: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bluetooth-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bluetooth-lib: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bmake: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bootloader: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bootloader-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bsdconfig: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bsdinstall: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]  [...]  [206/218] Extracting FreeBSD-ssh-dev-15.1.b2.20260508031850: 100%  [207/218] Upgrading FreeBSD-syscons-data from 15.0 to 15.1.b2.20260508031850...  [207/218] Extracting FreeBSD-syscons-data-15.1.b2.20260508031850: 100%  [208/218] Upgrading FreeBSD-tcpd from 15.0 to 15.1.b2.20260508031850...  [208/218] Extracting FreeBSD-tcpd-15.1.b2.20260508031850: 100%  [209/218] Upgrading FreeBSD-tcpd-dev from 15.0 to 15.1.b2.20260508031850...  [209/218] Extracting FreeBSD-tcpd-dev-15.1.b2.20260508031850: 100%  [210/218] Upgrading FreeBSD-telnet from 15.0 to 15.1.b2.20260508031850...  [210/218] Extracting FreeBSD-telnet-15.1.b2.20260508031850: 100%  [211/218] Upgrading FreeBSD-xz from 15.0 to 15.1.b2.20260508031850...  [211/218] Extracting FreeBSD-xz-15.1.b2.20260508031850: 100%  [212/218] Upgrading FreeBSD-xz-dev from 15.0 to 15.1.b2.20260508031850...  [212/218] Extracting FreeBSD-xz-dev-15.1.b2.20260508031850: 100%  [213/218] Installing FreeBSD-set-devel-15.1.b2.20260508031850...  [214/218] Upgrading FreeBSD-xz-lib from 15.0 to 15.1.b2.20260508031850...  [214/218] Extracting FreeBSD-xz-lib-15.1.b2.20260508031850: 100%  [215/218] Upgrading FreeBSD-set-minimal from 15.0 to 15.1.b2.20260508031850...  [216/218] Upgrading FreeBSD-yp from 15.0 to 15.1.b2.20260508031850...  [216/218] Extracting FreeBSD-yp-15.1.b2.20260508031850: 100%  [217/218] Installing FreeBSD-set-optional-15.1.b2.20260508031850...  [218/218] Installing FreeBSD-set-base-15.1.b2.20260508031850...  ==> Running trigger: mandoc.ucl  Generating apropos(1) database for /usr/share/man...  Generating apropos(1) database for /usr/share/openssl/man...  =====  Message from FreeBSD-local-unbound-15.1.b2.20260508031850:   --  After upgrading local-unbound, the configuration file should be regenerated  by running "service local_unbound setup" before restarting the service.  aptivi@apt-freebsd-01:~ $ 

    One last step is to examine and update the UEFI bootblock, assuming that the FreeBSD system is using UEFI as the boot method. Let’s confirm that the bootloader files have been updated in the /boot directory.

     aptivi@apt-freebsd-01:~ $ ls -l /boot/*.efi  -r-xr-xr-x  1 root wheel 158720 May  8 03:00 /boot/boot1.efi  -r-xr-xr-x  1 root wheel 109568 May  8 03:00 /boot/gptboot.efi  -r-xr-xr-x  2 root wheel 665600 May  8 03:00 /boot/loader.efi  -r--r--r--  1 root wheel  13653 May  8 03:00 /boot/loader.help.efi  -r-xr-xr-x  1 root wheel 580608 May  8 03:00 /boot/loader_4th.efi  -r-xr-xr-x  1 root wheel 622080 May  8 03:00 /boot/loader_ia32.efi  -r-xr-xr-x  2 root wheel 665600 May  8 03:00 /boot/loader_lua.efi  -r-xr-xr-x  1 root wheel 521728 May  8 03:00 /boot/loader_simp.efi  aptivi@apt-freebsd-01:~ $ ls -l /boot/efi/EFI/BOOT/  total 656  -rwxr-xr-x  1 root wheel 665088 May  5 15:24 BOOTX64.EFI 

    Now, we have the updated bootloader files, but the changes didn’t reflect in the ESP partition. So, we’ll need to manually copy the /boot/loader.efi file to overwrite /boot/efi/EFI/BOOT/BOOTX64.EFI, assuming that the ESP partition is automatically mounted via /etc/fstab (or manually sudo mount -t msdosfs /dev/da0p4 /mnt, assuming that da0p4 is the ESP partition) to /boot/efi. You can refer to our past article for more info.

    Execute the below commands:

     aptivi@apt-freebsd-01:~ $ sudo cp /boot/loader.efi /boot/efi/EFI/BOOT/BOOTX64.EFI  Password:  aptivi@apt-freebsd-01:~ $ ls -l /boot/efi/EFI/BOOT/  total 656  -rwxr-xr-x  1 root wheel 665600 May 10 21:51 BOOTX64.EFI 

    Verify that the updated BOOTX64.EFI file has been copied to the ESP.

    Once done, reboot the system using sudo reboot.

    After that, verify that you’re running FreeBSD 15.1-BETA2:

     aptivi@apt-freebsd-01:~ $ uname -a  FreeBSD apt-freebsd-01 15.1-BETA2 FreeBSD 15.1-BETA2 releng/15.1-n283486-b3f9be4f9437 GENERIC amd64 

    …compared to what we had earlier.

     aptivi@apt-freebsd-01:~ $ uname -a  FreeBSD apt-freebsd-01 15.0-RELEASE FreeBSD 15.0-RELEASE releng/15.0-n280995-7aedc8de6446 GENERIC amd64 

    Now, we’re running FreeBSD 15.1 Beta 2! Make sure that pkg is able to install packages afterwards. For example, we’ll install the rsync program in the upgraded system:

     aptivi@apt-freebsd-01:~ $ sudo pkg install rsync  Updating FreeBSD-ports repository catalogue...  FreeBSD-ports repository is up to date.  Updating FreeBSD-ports-kmods repository catalogue...  FreeBSD-ports-kmods repository is up to date.  Updating FreeBSD-base repository catalogue...  FreeBSD-base repository is up to date.  All repositories are up to date.  The following 5 package(s) will be affected (of 0 checked):   New packages to be INSTALLED:          libiconv: 1.18_1 [FreeBSD-ports]          liblz4: 1.10.0_2,1 [FreeBSD-ports]          rsync: 3.4.1_6 [FreeBSD-ports]          xxhash: 0.8.3 [FreeBSD-ports]          zstd: 1.5.7_1 [FreeBSD-ports]   Number of packages to be installed: 5   The process will require 8 MiB more space.  2 MiB to be downloaded.   Proceed with this action? [y/N]: y  [1/5] Fetching libiconv-1.18_1: 100%   741 KiB 252.8 kB/s    00:03  [2/5] Fetching xxhash-0.8.3: 100%   103 KiB 105.4 kB/s    00:01  [3/5] Fetching rsync-3.4.1_6: 100%   396 KiB 202.5 kB/s    00:02  [4/5] Fetching liblz4-1.10.0_2,1: 100%   178 KiB 182.5 kB/s    00:01  [5/5] Fetching zstd-1.5.7_1: 100%   509 KiB 520.9 kB/s    00:01  Checking integrity... done (0 conflicting)  [1/5] Installing libiconv-1.18_1...  [1/5] Extracting libiconv-1.18_1: 100%  [2/5] Installing liblz4-1.10.0_2,1...  [2/5] Extracting liblz4-1.10.0_2,1: 100%  [3/5] Installing xxhash-0.8.3...  [3/5] Extracting xxhash-0.8.3: 100%  [4/5] Installing zstd-1.5.7_1...  [4/5] Extracting zstd-1.5.7_1: 100%  [5/5] Installing rsync-3.4.1_6...  [5/5] Extracting rsync-3.4.1_6: 100% 
    #FreeBSD #FreeBSD15 #FreeBSD150 #FreeBSD151 #news #Tech #Technology #update
  20. Upgrading FreeBSD 15.0-STABLE to 15.1-BETA2 (PKGBASE system)

    Recently, an article about upgrading the FreeBSD 15.0-STABLE system to the 15.1-BETA2 version has been posted, because the PKGBASE system installations of FreeBSD are still in experimental stages. One of the biggest missing features is the ability to reliably upgrade the FreeBSD system to newer versions, such as from 15.0 to 15.1.

    The release engineering team stated that this part was overlooked, and that they were working on it for PKGBASE systems. A solution has then been posted in the linked article, as discovered by vermaden, involving ZFS boot environments for those who are using ZFS on their FreeBSD installation.

    https://vermaden.wordpress.com/2026/05/10/freebsd-pkgbase-minor-upgrades/

    The solution above involved ZFS boot environments, administered by the beadm tool. The older freebsd-update tool had the ability to upgrade your FreeBSD installation to new minor releases, but the PKGBASE world didn’t benefit from this convenience. Therefore, we have adapted the solution to use the commands similar to what was listed in this message posted to the mailing list.

    WARNING: Before you attempt to do this, please make sure that you take a complete backup of your system, in case something goes wrong during the upgrade. The steps were done on a test machine where no crucial data was stored, therefore, no ZFS snapshots or boot environments were made, so please proceed at your own risk. Beta software is unstable and may contain more bugs than the final version.

    First of all, you’ll have to either use sudo or to log in as root. In this article, we have chosen sudo as it not only runs a single command as a super user, but it’s also a good practice in general to avoid logging in as root for everyday activities.

    After that, make sure that pkg is up to date before you continue. You’ll need to run sudo pkg upgrade pkg to upgrade the package manager itself.

    Once the upgrade of the package manager succeeds, run the below command to upgrade all packages from the FreeBSD-ports-kmods repository catalog.

     aptivi@apt-freebsd-01:~ $ sudo pkg -o ABI=FreeBSD:15:$(sysctl -n hw.machine_arch) -o OSVERSION=1501000 upgrade -yr FreeBSD-ports-kmods  Password:  Updating FreeBSD-ports-kmods repository catalogue...  pkg: Repository FreeBSD-ports-kmods has a wrong packagesite, need to re-create database  Fetching meta.conf: 100%     179 B   0.2 kB/s    00:01  Fetching data: 100%    36 KiB  36.4 kB/s    00:01  Processing entries: 100%  FreeBSD-ports-kmods repository update completed. 239 packages processed.  FreeBSD-ports-kmods is up to date.  Checking for upgrades (0 candidates): 100%  Processing candidates (0 candidates): 100%  Checking integrity... done (0 conflicting)  Your packages are up to date. 

    Please note that we have added the following switches:

    • -o ABI=FreeBSD:15:$(sysctl -n hw.machine_arch): Specifies the FreeBSD ABI version and architecture. (Before upgrade)
    • -o OSVERSION=1501000: Specifies the explicit operating system version ID (for example, 1501000 resolves to FreeBSD 15.1) (Very important, before upgrade)
    • -y: Runs the upgrade automatically (After upgrade)
    • -r FreeBSD-ports-kmods: Specifies the repository catalog name (Very important, After upgrade)

    After the package upgrades from the above repository catalog succeed, it’s time to upgrade the base system. The output below is truncated because it was very long as all packages needed to be upgraded to 15.1.b2 from 15.0.

     aptivi@apt-freebsd-01:~ $ sudo pkg -o ABI=FreeBSD:15:$(sysctl -n hw.machine_arch) -o OSVERSION=1501000 upgrade -yr FreeBSD-base  Updating FreeBSD-base repository catalogue...  pkg: Repository FreeBSD-base has a wrong packagesite, need to re-create database  Fetching meta.conf: 100%     179 B   0.2 kB/s    00:01  Fetching data: 100%    82 KiB  84.4 kB/s    00:01  Processing entries: 100%  FreeBSD-base repository update completed. 509 packages processed.  FreeBSD-base is up to date.  Checking for upgrades (208 candidates): 100%  Processing candidates (208 candidates): 100%  The following 214 package(s) will be affected (of 0 checked):   New packages to be INSTALLED:          FreeBSD-pam: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-pam-dev: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-pam-lib: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-zstd: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-zstd-dev: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-zstd-lib: 15.1.b2.20260508031850 [FreeBSD-base]   Installed packages to be UPGRADED:          FreeBSD-acct: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-acpi: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-apm: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-at: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-atf: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-atf-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-atf-lib: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-audit: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-audit-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-audit-lib: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-autofs: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bhyve: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-blocklist: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-blocklist-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bluetooth: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bluetooth-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bluetooth-lib: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bmake: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bootloader: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bootloader-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bsdconfig: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bsdinstall: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]  [...]  [206/218] Extracting FreeBSD-ssh-dev-15.1.b2.20260508031850: 100%  [207/218] Upgrading FreeBSD-syscons-data from 15.0 to 15.1.b2.20260508031850...  [207/218] Extracting FreeBSD-syscons-data-15.1.b2.20260508031850: 100%  [208/218] Upgrading FreeBSD-tcpd from 15.0 to 15.1.b2.20260508031850...  [208/218] Extracting FreeBSD-tcpd-15.1.b2.20260508031850: 100%  [209/218] Upgrading FreeBSD-tcpd-dev from 15.0 to 15.1.b2.20260508031850...  [209/218] Extracting FreeBSD-tcpd-dev-15.1.b2.20260508031850: 100%  [210/218] Upgrading FreeBSD-telnet from 15.0 to 15.1.b2.20260508031850...  [210/218] Extracting FreeBSD-telnet-15.1.b2.20260508031850: 100%  [211/218] Upgrading FreeBSD-xz from 15.0 to 15.1.b2.20260508031850...  [211/218] Extracting FreeBSD-xz-15.1.b2.20260508031850: 100%  [212/218] Upgrading FreeBSD-xz-dev from 15.0 to 15.1.b2.20260508031850...  [212/218] Extracting FreeBSD-xz-dev-15.1.b2.20260508031850: 100%  [213/218] Installing FreeBSD-set-devel-15.1.b2.20260508031850...  [214/218] Upgrading FreeBSD-xz-lib from 15.0 to 15.1.b2.20260508031850...  [214/218] Extracting FreeBSD-xz-lib-15.1.b2.20260508031850: 100%  [215/218] Upgrading FreeBSD-set-minimal from 15.0 to 15.1.b2.20260508031850...  [216/218] Upgrading FreeBSD-yp from 15.0 to 15.1.b2.20260508031850...  [216/218] Extracting FreeBSD-yp-15.1.b2.20260508031850: 100%  [217/218] Installing FreeBSD-set-optional-15.1.b2.20260508031850...  [218/218] Installing FreeBSD-set-base-15.1.b2.20260508031850...  ==> Running trigger: mandoc.ucl  Generating apropos(1) database for /usr/share/man...  Generating apropos(1) database for /usr/share/openssl/man...  =====  Message from FreeBSD-local-unbound-15.1.b2.20260508031850:   --  After upgrading local-unbound, the configuration file should be regenerated  by running "service local_unbound setup" before restarting the service.  aptivi@apt-freebsd-01:~ $ 

    One last step is to examine and update the UEFI bootblock, assuming that the FreeBSD system is using UEFI as the boot method. Let’s confirm that the bootloader files have been updated in the /boot directory.

     aptivi@apt-freebsd-01:~ $ ls -l /boot/*.efi  -r-xr-xr-x  1 root wheel 158720 May  8 03:00 /boot/boot1.efi  -r-xr-xr-x  1 root wheel 109568 May  8 03:00 /boot/gptboot.efi  -r-xr-xr-x  2 root wheel 665600 May  8 03:00 /boot/loader.efi  -r--r--r--  1 root wheel  13653 May  8 03:00 /boot/loader.help.efi  -r-xr-xr-x  1 root wheel 580608 May  8 03:00 /boot/loader_4th.efi  -r-xr-xr-x  1 root wheel 622080 May  8 03:00 /boot/loader_ia32.efi  -r-xr-xr-x  2 root wheel 665600 May  8 03:00 /boot/loader_lua.efi  -r-xr-xr-x  1 root wheel 521728 May  8 03:00 /boot/loader_simp.efi  aptivi@apt-freebsd-01:~ $ ls -l /boot/efi/EFI/BOOT/  total 656  -rwxr-xr-x  1 root wheel 665088 May  5 15:24 BOOTX64.EFI 

    Now, we have the updated bootloader files, but the changes didn’t reflect in the ESP partition. So, we’ll need to manually copy the /boot/loader.efi file to overwrite /boot/efi/EFI/BOOT/BOOTX64.EFI, assuming that the ESP partition is automatically mounted via /etc/fstab (or manually sudo mount -t msdosfs /dev/da0p4 /mnt, assuming that da0p4 is the ESP partition) to /boot/efi. You can refer to our past article for more info.

    Execute the below commands:

     aptivi@apt-freebsd-01:~ $ sudo cp /boot/loader.efi /boot/efi/EFI/BOOT/BOOTX64.EFI  Password:  aptivi@apt-freebsd-01:~ $ ls -l /boot/efi/EFI/BOOT/  total 656  -rwxr-xr-x  1 root wheel 665600 May 10 21:51 BOOTX64.EFI 

    Verify that the updated BOOTX64.EFI file has been copied to the ESP.

    Once done, reboot the system using sudo reboot.

    After that, verify that you’re running FreeBSD 15.1-BETA2:

     aptivi@apt-freebsd-01:~ $ uname -a  FreeBSD apt-freebsd-01 15.1-BETA2 FreeBSD 15.1-BETA2 releng/15.1-n283486-b3f9be4f9437 GENERIC amd64 

    …compared to what we had earlier.

     aptivi@apt-freebsd-01:~ $ uname -a  FreeBSD apt-freebsd-01 15.0-RELEASE FreeBSD 15.0-RELEASE releng/15.0-n280995-7aedc8de6446 GENERIC amd64 

    Now, we’re running FreeBSD 15.1 Beta 2! Make sure that pkg is able to install packages afterwards. For example, we’ll install the rsync program in the upgraded system:

     aptivi@apt-freebsd-01:~ $ sudo pkg install rsync  Updating FreeBSD-ports repository catalogue...  FreeBSD-ports repository is up to date.  Updating FreeBSD-ports-kmods repository catalogue...  FreeBSD-ports-kmods repository is up to date.  Updating FreeBSD-base repository catalogue...  FreeBSD-base repository is up to date.  All repositories are up to date.  The following 5 package(s) will be affected (of 0 checked):   New packages to be INSTALLED:          libiconv: 1.18_1 [FreeBSD-ports]          liblz4: 1.10.0_2,1 [FreeBSD-ports]          rsync: 3.4.1_6 [FreeBSD-ports]          xxhash: 0.8.3 [FreeBSD-ports]          zstd: 1.5.7_1 [FreeBSD-ports]   Number of packages to be installed: 5   The process will require 8 MiB more space.  2 MiB to be downloaded.   Proceed with this action? [y/N]: y  [1/5] Fetching libiconv-1.18_1: 100%   741 KiB 252.8 kB/s    00:03  [2/5] Fetching xxhash-0.8.3: 100%   103 KiB 105.4 kB/s    00:01  [3/5] Fetching rsync-3.4.1_6: 100%   396 KiB 202.5 kB/s    00:02  [4/5] Fetching liblz4-1.10.0_2,1: 100%   178 KiB 182.5 kB/s    00:01  [5/5] Fetching zstd-1.5.7_1: 100%   509 KiB 520.9 kB/s    00:01  Checking integrity... done (0 conflicting)  [1/5] Installing libiconv-1.18_1...  [1/5] Extracting libiconv-1.18_1: 100%  [2/5] Installing liblz4-1.10.0_2,1...  [2/5] Extracting liblz4-1.10.0_2,1: 100%  [3/5] Installing xxhash-0.8.3...  [3/5] Extracting xxhash-0.8.3: 100%  [4/5] Installing zstd-1.5.7_1...  [4/5] Extracting zstd-1.5.7_1: 100%  [5/5] Installing rsync-3.4.1_6...  [5/5] Extracting rsync-3.4.1_6: 100% 
    #FreeBSD #FreeBSD15 #FreeBSD150 #FreeBSD151 #news #Tech #Technology #update
  21. Upgrading FreeBSD 15.0-STABLE to 15.1-BETA2 (PKGBASE system)

    Recently, an article about upgrading the FreeBSD 15.0-STABLE system to the 15.1-BETA2 version has been posted, because the PKGBASE system installations of FreeBSD are still in experimental stages. One of the biggest missing features is the ability to reliably upgrade the FreeBSD system to newer versions, such as from 15.0 to 15.1.

    The release engineering team stated that this part was overlooked, and that they were working on it for PKGBASE systems. A solution has then been posted in the linked article, as discovered by vermaden, involving ZFS boot environments for those who are using ZFS on their FreeBSD installation.

    https://vermaden.wordpress.com/2026/05/10/freebsd-pkgbase-minor-upgrades/

    The solution above involved ZFS boot environments, administered by the beadm tool. The older freebsd-update tool had the ability to upgrade your FreeBSD installation to new minor releases, but the PKGBASE world didn’t benefit from this convenience. Therefore, we have adapted the solution to use the commands similar to what was listed in this message posted to the mailing list.

    WARNING: Before you attempt to do this, please make sure that you take a complete backup of your system, in case something goes wrong during the upgrade. The steps were done on a test machine where no crucial data was stored, therefore, no ZFS snapshots or boot environments were made, so please proceed at your own risk. Beta software is unstable and may contain more bugs than the final version.

    First of all, you’ll have to either use sudo or to log in as root. In this article, we have chosen sudo as it not only runs a single command as a super user, but it’s also a good practice in general to avoid logging in as root for everyday activities.

    After that, make sure that pkg is up to date before you continue. You’ll need to run sudo pkg upgrade pkg to upgrade the package manager itself.

    Once the upgrade of the package manager succeeds, run the below command to upgrade all packages from the FreeBSD-ports-kmods repository catalog.

     aptivi@apt-freebsd-01:~ $ sudo pkg -o ABI=FreeBSD:15:$(sysctl -n hw.machine_arch) -o OSVERSION=1501000 upgrade -yr FreeBSD-ports-kmods  Password:  Updating FreeBSD-ports-kmods repository catalogue...  pkg: Repository FreeBSD-ports-kmods has a wrong packagesite, need to re-create database  Fetching meta.conf: 100%     179 B   0.2 kB/s    00:01  Fetching data: 100%    36 KiB  36.4 kB/s    00:01  Processing entries: 100%  FreeBSD-ports-kmods repository update completed. 239 packages processed.  FreeBSD-ports-kmods is up to date.  Checking for upgrades (0 candidates): 100%  Processing candidates (0 candidates): 100%  Checking integrity... done (0 conflicting)  Your packages are up to date. 

    Please note that we have added the following switches:

    • -o ABI=FreeBSD:15:$(sysctl -n hw.machine_arch): Specifies the FreeBSD ABI version and architecture. (Before upgrade)
    • -o OSVERSION=1501000: Specifies the explicit operating system version ID (for example, 1501000 resolves to FreeBSD 15.1) (Very important, before upgrade)
    • -y: Runs the upgrade automatically (After upgrade)
    • -r FreeBSD-ports-kmods: Specifies the repository catalog name (Very important, After upgrade)

    After the package upgrades from the above repository catalog succeed, it’s time to upgrade the base system. The output below is truncated because it was very long as all packages needed to be upgraded to 15.1.b2 from 15.0.

     aptivi@apt-freebsd-01:~ $ sudo pkg -o ABI=FreeBSD:15:$(sysctl -n hw.machine_arch) -o OSVERSION=1501000 upgrade -yr FreeBSD-base  Updating FreeBSD-base repository catalogue...  pkg: Repository FreeBSD-base has a wrong packagesite, need to re-create database  Fetching meta.conf: 100%     179 B   0.2 kB/s    00:01  Fetching data: 100%    82 KiB  84.4 kB/s    00:01  Processing entries: 100%  FreeBSD-base repository update completed. 509 packages processed.  FreeBSD-base is up to date.  Checking for upgrades (208 candidates): 100%  Processing candidates (208 candidates): 100%  The following 214 package(s) will be affected (of 0 checked):   New packages to be INSTALLED:          FreeBSD-pam: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-pam-dev: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-pam-lib: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-zstd: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-zstd-dev: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-zstd-lib: 15.1.b2.20260508031850 [FreeBSD-base]   Installed packages to be UPGRADED:          FreeBSD-acct: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-acpi: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-apm: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-at: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-atf: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-atf-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-atf-lib: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-audit: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-audit-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-audit-lib: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-autofs: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bhyve: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-blocklist: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-blocklist-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bluetooth: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bluetooth-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bluetooth-lib: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bmake: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bootloader: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bootloader-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bsdconfig: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bsdinstall: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]  [...]  [206/218] Extracting FreeBSD-ssh-dev-15.1.b2.20260508031850: 100%  [207/218] Upgrading FreeBSD-syscons-data from 15.0 to 15.1.b2.20260508031850...  [207/218] Extracting FreeBSD-syscons-data-15.1.b2.20260508031850: 100%  [208/218] Upgrading FreeBSD-tcpd from 15.0 to 15.1.b2.20260508031850...  [208/218] Extracting FreeBSD-tcpd-15.1.b2.20260508031850: 100%  [209/218] Upgrading FreeBSD-tcpd-dev from 15.0 to 15.1.b2.20260508031850...  [209/218] Extracting FreeBSD-tcpd-dev-15.1.b2.20260508031850: 100%  [210/218] Upgrading FreeBSD-telnet from 15.0 to 15.1.b2.20260508031850...  [210/218] Extracting FreeBSD-telnet-15.1.b2.20260508031850: 100%  [211/218] Upgrading FreeBSD-xz from 15.0 to 15.1.b2.20260508031850...  [211/218] Extracting FreeBSD-xz-15.1.b2.20260508031850: 100%  [212/218] Upgrading FreeBSD-xz-dev from 15.0 to 15.1.b2.20260508031850...  [212/218] Extracting FreeBSD-xz-dev-15.1.b2.20260508031850: 100%  [213/218] Installing FreeBSD-set-devel-15.1.b2.20260508031850...  [214/218] Upgrading FreeBSD-xz-lib from 15.0 to 15.1.b2.20260508031850...  [214/218] Extracting FreeBSD-xz-lib-15.1.b2.20260508031850: 100%  [215/218] Upgrading FreeBSD-set-minimal from 15.0 to 15.1.b2.20260508031850...  [216/218] Upgrading FreeBSD-yp from 15.0 to 15.1.b2.20260508031850...  [216/218] Extracting FreeBSD-yp-15.1.b2.20260508031850: 100%  [217/218] Installing FreeBSD-set-optional-15.1.b2.20260508031850...  [218/218] Installing FreeBSD-set-base-15.1.b2.20260508031850...  ==> Running trigger: mandoc.ucl  Generating apropos(1) database for /usr/share/man...  Generating apropos(1) database for /usr/share/openssl/man...  =====  Message from FreeBSD-local-unbound-15.1.b2.20260508031850:   --  After upgrading local-unbound, the configuration file should be regenerated  by running "service local_unbound setup" before restarting the service.  aptivi@apt-freebsd-01:~ $ 

    One last step is to examine and update the UEFI bootblock, assuming that the FreeBSD system is using UEFI as the boot method. Let’s confirm that the bootloader files have been updated in the /boot directory.

     aptivi@apt-freebsd-01:~ $ ls -l /boot/*.efi  -r-xr-xr-x  1 root wheel 158720 May  8 03:00 /boot/boot1.efi  -r-xr-xr-x  1 root wheel 109568 May  8 03:00 /boot/gptboot.efi  -r-xr-xr-x  2 root wheel 665600 May  8 03:00 /boot/loader.efi  -r--r--r--  1 root wheel  13653 May  8 03:00 /boot/loader.help.efi  -r-xr-xr-x  1 root wheel 580608 May  8 03:00 /boot/loader_4th.efi  -r-xr-xr-x  1 root wheel 622080 May  8 03:00 /boot/loader_ia32.efi  -r-xr-xr-x  2 root wheel 665600 May  8 03:00 /boot/loader_lua.efi  -r-xr-xr-x  1 root wheel 521728 May  8 03:00 /boot/loader_simp.efi  aptivi@apt-freebsd-01:~ $ ls -l /boot/efi/EFI/BOOT/  total 656  -rwxr-xr-x  1 root wheel 665088 May  5 15:24 BOOTX64.EFI 

    Now, we have the updated bootloader files, but the changes didn’t reflect in the ESP partition. So, we’ll need to manually copy the /boot/loader.efi file to overwrite /boot/efi/EFI/BOOT/BOOTX64.EFI, assuming that the ESP partition is automatically mounted via /etc/fstab (or manually sudo mount -t msdosfs /dev/da0p4 /mnt, assuming that da0p4 is the ESP partition) to /boot/efi. You can refer to our past article for more info.

    Execute the below commands:

     aptivi@apt-freebsd-01:~ $ sudo cp /boot/loader.efi /boot/efi/EFI/BOOT/BOOTX64.EFI  Password:  aptivi@apt-freebsd-01:~ $ ls -l /boot/efi/EFI/BOOT/  total 656  -rwxr-xr-x  1 root wheel 665600 May 10 21:51 BOOTX64.EFI 

    Verify that the updated BOOTX64.EFI file has been copied to the ESP.

    Once done, reboot the system using sudo reboot.

    After that, verify that you’re running FreeBSD 15.1-BETA2:

     aptivi@apt-freebsd-01:~ $ uname -a  FreeBSD apt-freebsd-01 15.1-BETA2 FreeBSD 15.1-BETA2 releng/15.1-n283486-b3f9be4f9437 GENERIC amd64 

    …compared to what we had earlier.

     aptivi@apt-freebsd-01:~ $ uname -a  FreeBSD apt-freebsd-01 15.0-RELEASE FreeBSD 15.0-RELEASE releng/15.0-n280995-7aedc8de6446 GENERIC amd64 

    Now, we’re running FreeBSD 15.1 Beta 2! Make sure that pkg is able to install packages afterwards. For example, we’ll install the rsync program in the upgraded system:

     aptivi@apt-freebsd-01:~ $ sudo pkg install rsync  Updating FreeBSD-ports repository catalogue...  FreeBSD-ports repository is up to date.  Updating FreeBSD-ports-kmods repository catalogue...  FreeBSD-ports-kmods repository is up to date.  Updating FreeBSD-base repository catalogue...  FreeBSD-base repository is up to date.  All repositories are up to date.  The following 5 package(s) will be affected (of 0 checked):   New packages to be INSTALLED:          libiconv: 1.18_1 [FreeBSD-ports]          liblz4: 1.10.0_2,1 [FreeBSD-ports]          rsync: 3.4.1_6 [FreeBSD-ports]          xxhash: 0.8.3 [FreeBSD-ports]          zstd: 1.5.7_1 [FreeBSD-ports]   Number of packages to be installed: 5   The process will require 8 MiB more space.  2 MiB to be downloaded.   Proceed with this action? [y/N]: y  [1/5] Fetching libiconv-1.18_1: 100%   741 KiB 252.8 kB/s    00:03  [2/5] Fetching xxhash-0.8.3: 100%   103 KiB 105.4 kB/s    00:01  [3/5] Fetching rsync-3.4.1_6: 100%   396 KiB 202.5 kB/s    00:02  [4/5] Fetching liblz4-1.10.0_2,1: 100%   178 KiB 182.5 kB/s    00:01  [5/5] Fetching zstd-1.5.7_1: 100%   509 KiB 520.9 kB/s    00:01  Checking integrity... done (0 conflicting)  [1/5] Installing libiconv-1.18_1...  [1/5] Extracting libiconv-1.18_1: 100%  [2/5] Installing liblz4-1.10.0_2,1...  [2/5] Extracting liblz4-1.10.0_2,1: 100%  [3/5] Installing xxhash-0.8.3...  [3/5] Extracting xxhash-0.8.3: 100%  [4/5] Installing zstd-1.5.7_1...  [4/5] Extracting zstd-1.5.7_1: 100%  [5/5] Installing rsync-3.4.1_6...  [5/5] Extracting rsync-3.4.1_6: 100% 
    #FreeBSD #FreeBSD15 #FreeBSD150 #FreeBSD151 #news #Tech #Technology #update
  22. Upgrading FreeBSD 15.0-STABLE to 15.1-BETA2 (PKGBASE system)

    Recently, an article about upgrading the FreeBSD 15.0-STABLE system to the 15.1-BETA2 version has been posted, because the PKGBASE system installations of FreeBSD are still in experimental stages. One of the biggest missing features is the ability to reliably upgrade the FreeBSD system to newer versions, such as from 15.0 to 15.1.

    The release engineering team stated that this part was overlooked, and that they were working on it for PKGBASE systems. A solution has then been posted in the linked article, as discovered by vermaden, involving ZFS boot environments for those who are using ZFS on their FreeBSD installation.

    https://vermaden.wordpress.com/2026/05/10/freebsd-pkgbase-minor-upgrades/

    The solution above involved ZFS boot environments, administered by the beadm tool. The older freebsd-update tool had the ability to upgrade your FreeBSD installation to new minor releases, but the PKGBASE world didn’t benefit from this convenience. Therefore, we have adapted the solution to use the commands similar to what was listed in this message posted to the mailing list.

    WARNING: Before you attempt to do this, please make sure that you take a complete backup of your system, in case something goes wrong during the upgrade. The steps were done on a test machine where no crucial data was stored, therefore, no ZFS snapshots or boot environments were made, so please proceed at your own risk. Beta software is unstable and may contain more bugs than the final version.

    First of all, you’ll have to either use sudo or to log in as root. In this article, we have chosen sudo as it not only runs a single command as a super user, but it’s also a good practice in general to avoid logging in as root for everyday activities.

    After that, make sure that pkg is up to date before you continue. You’ll need to run sudo pkg upgrade pkg to upgrade the package manager itself.

    Once the upgrade of the package manager succeeds, run the below command to upgrade all packages from the FreeBSD-ports-kmods repository catalog.

     aptivi@apt-freebsd-01:~ $ sudo pkg -o ABI=FreeBSD:15:$(sysctl -n hw.machine_arch) -o OSVERSION=1501000 upgrade -yr FreeBSD-ports-kmods  Password:  Updating FreeBSD-ports-kmods repository catalogue...  pkg: Repository FreeBSD-ports-kmods has a wrong packagesite, need to re-create database  Fetching meta.conf: 100%     179 B   0.2 kB/s    00:01  Fetching data: 100%    36 KiB  36.4 kB/s    00:01  Processing entries: 100%  FreeBSD-ports-kmods repository update completed. 239 packages processed.  FreeBSD-ports-kmods is up to date.  Checking for upgrades (0 candidates): 100%  Processing candidates (0 candidates): 100%  Checking integrity... done (0 conflicting)  Your packages are up to date. 

    Please note that we have added the following switches:

    • -o ABI=FreeBSD:15:$(sysctl -n hw.machine_arch): Specifies the FreeBSD ABI version and architecture. (Before upgrade)
    • -o OSVERSION=1501000: Specifies the explicit operating system version ID (for example, 1501000 resolves to FreeBSD 15.1) (Very important, before upgrade)
    • -y: Runs the upgrade automatically (After upgrade)
    • -r FreeBSD-ports-kmods: Specifies the repository catalog name (Very important, After upgrade)

    After the package upgrades from the above repository catalog succeed, it’s time to upgrade the base system. The output below is truncated because it was very long as all packages needed to be upgraded to 15.1.b2 from 15.0.

     aptivi@apt-freebsd-01:~ $ sudo pkg -o ABI=FreeBSD:15:$(sysctl -n hw.machine_arch) -o OSVERSION=1501000 upgrade -yr FreeBSD-base  Updating FreeBSD-base repository catalogue...  pkg: Repository FreeBSD-base has a wrong packagesite, need to re-create database  Fetching meta.conf: 100%     179 B   0.2 kB/s    00:01  Fetching data: 100%    82 KiB  84.4 kB/s    00:01  Processing entries: 100%  FreeBSD-base repository update completed. 509 packages processed.  FreeBSD-base is up to date.  Checking for upgrades (208 candidates): 100%  Processing candidates (208 candidates): 100%  The following 214 package(s) will be affected (of 0 checked):   New packages to be INSTALLED:          FreeBSD-pam: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-pam-dev: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-pam-lib: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-zstd: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-zstd-dev: 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-zstd-lib: 15.1.b2.20260508031850 [FreeBSD-base]   Installed packages to be UPGRADED:          FreeBSD-acct: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-acpi: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-apm: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-at: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-atf: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-atf-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-atf-lib: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-audit: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-audit-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-audit-lib: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-autofs: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bhyve: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-blocklist: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-blocklist-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bluetooth: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bluetooth-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bluetooth-lib: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bmake: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bootloader: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bootloader-dev: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bsdconfig: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]          FreeBSD-bsdinstall: 15.0 -> 15.1.b2.20260508031850 [FreeBSD-base]  [...]  [206/218] Extracting FreeBSD-ssh-dev-15.1.b2.20260508031850: 100%  [207/218] Upgrading FreeBSD-syscons-data from 15.0 to 15.1.b2.20260508031850...  [207/218] Extracting FreeBSD-syscons-data-15.1.b2.20260508031850: 100%  [208/218] Upgrading FreeBSD-tcpd from 15.0 to 15.1.b2.20260508031850...  [208/218] Extracting FreeBSD-tcpd-15.1.b2.20260508031850: 100%  [209/218] Upgrading FreeBSD-tcpd-dev from 15.0 to 15.1.b2.20260508031850...  [209/218] Extracting FreeBSD-tcpd-dev-15.1.b2.20260508031850: 100%  [210/218] Upgrading FreeBSD-telnet from 15.0 to 15.1.b2.20260508031850...  [210/218] Extracting FreeBSD-telnet-15.1.b2.20260508031850: 100%  [211/218] Upgrading FreeBSD-xz from 15.0 to 15.1.b2.20260508031850...  [211/218] Extracting FreeBSD-xz-15.1.b2.20260508031850: 100%  [212/218] Upgrading FreeBSD-xz-dev from 15.0 to 15.1.b2.20260508031850...  [212/218] Extracting FreeBSD-xz-dev-15.1.b2.20260508031850: 100%  [213/218] Installing FreeBSD-set-devel-15.1.b2.20260508031850...  [214/218] Upgrading FreeBSD-xz-lib from 15.0 to 15.1.b2.20260508031850...  [214/218] Extracting FreeBSD-xz-lib-15.1.b2.20260508031850: 100%  [215/218] Upgrading FreeBSD-set-minimal from 15.0 to 15.1.b2.20260508031850...  [216/218] Upgrading FreeBSD-yp from 15.0 to 15.1.b2.20260508031850...  [216/218] Extracting FreeBSD-yp-15.1.b2.20260508031850: 100%  [217/218] Installing FreeBSD-set-optional-15.1.b2.20260508031850...  [218/218] Installing FreeBSD-set-base-15.1.b2.20260508031850...  ==> Running trigger: mandoc.ucl  Generating apropos(1) database for /usr/share/man...  Generating apropos(1) database for /usr/share/openssl/man...  =====  Message from FreeBSD-local-unbound-15.1.b2.20260508031850:   --  After upgrading local-unbound, the configuration file should be regenerated  by running "service local_unbound setup" before restarting the service.  aptivi@apt-freebsd-01:~ $ 

    One last step is to examine and update the UEFI bootblock, assuming that the FreeBSD system is using UEFI as the boot method. Let’s confirm that the bootloader files have been updated in the /boot directory.

     aptivi@apt-freebsd-01:~ $ ls -l /boot/*.efi  -r-xr-xr-x  1 root wheel 158720 May  8 03:00 /boot/boot1.efi  -r-xr-xr-x  1 root wheel 109568 May  8 03:00 /boot/gptboot.efi  -r-xr-xr-x  2 root wheel 665600 May  8 03:00 /boot/loader.efi  -r--r--r--  1 root wheel  13653 May  8 03:00 /boot/loader.help.efi  -r-xr-xr-x  1 root wheel 580608 May  8 03:00 /boot/loader_4th.efi  -r-xr-xr-x  1 root wheel 622080 May  8 03:00 /boot/loader_ia32.efi  -r-xr-xr-x  2 root wheel 665600 May  8 03:00 /boot/loader_lua.efi  -r-xr-xr-x  1 root wheel 521728 May  8 03:00 /boot/loader_simp.efi  aptivi@apt-freebsd-01:~ $ ls -l /boot/efi/EFI/BOOT/  total 656  -rwxr-xr-x  1 root wheel 665088 May  5 15:24 BOOTX64.EFI 

    Now, we have the updated bootloader files, but the changes didn’t reflect in the ESP partition. So, we’ll need to manually copy the /boot/loader.efi file to overwrite /boot/efi/EFI/BOOT/BOOTX64.EFI, assuming that the ESP partition is automatically mounted via /etc/fstab (or manually sudo mount -t msdosfs /dev/da0p4 /mnt, assuming that da0p4 is the ESP partition) to /boot/efi. You can refer to our past article for more info.

    Execute the below commands:

     aptivi@apt-freebsd-01:~ $ sudo cp /boot/loader.efi /boot/efi/EFI/BOOT/BOOTX64.EFI  Password:  aptivi@apt-freebsd-01:~ $ ls -l /boot/efi/EFI/BOOT/  total 656  -rwxr-xr-x  1 root wheel 665600 May 10 21:51 BOOTX64.EFI 

    Verify that the updated BOOTX64.EFI file has been copied to the ESP.

    Once done, reboot the system using sudo reboot.

    After that, verify that you’re running FreeBSD 15.1-BETA2:

     aptivi@apt-freebsd-01:~ $ uname -a  FreeBSD apt-freebsd-01 15.1-BETA2 FreeBSD 15.1-BETA2 releng/15.1-n283486-b3f9be4f9437 GENERIC amd64 

    …compared to what we had earlier.

     aptivi@apt-freebsd-01:~ $ uname -a  FreeBSD apt-freebsd-01 15.0-RELEASE FreeBSD 15.0-RELEASE releng/15.0-n280995-7aedc8de6446 GENERIC amd64 

    Now, we’re running FreeBSD 15.1 Beta 2! Make sure that pkg is able to install packages afterwards. For example, we’ll install the rsync program in the upgraded system:

     aptivi@apt-freebsd-01:~ $ sudo pkg install rsync  Updating FreeBSD-ports repository catalogue...  FreeBSD-ports repository is up to date.  Updating FreeBSD-ports-kmods repository catalogue...  FreeBSD-ports-kmods repository is up to date.  Updating FreeBSD-base repository catalogue...  FreeBSD-base repository is up to date.  All repositories are up to date.  The following 5 package(s) will be affected (of 0 checked):   New packages to be INSTALLED:          libiconv: 1.18_1 [FreeBSD-ports]          liblz4: 1.10.0_2,1 [FreeBSD-ports]          rsync: 3.4.1_6 [FreeBSD-ports]          xxhash: 0.8.3 [FreeBSD-ports]          zstd: 1.5.7_1 [FreeBSD-ports]   Number of packages to be installed: 5   The process will require 8 MiB more space.  2 MiB to be downloaded.   Proceed with this action? [y/N]: y  [1/5] Fetching libiconv-1.18_1: 100%   741 KiB 252.8 kB/s    00:03  [2/5] Fetching xxhash-0.8.3: 100%   103 KiB 105.4 kB/s    00:01  [3/5] Fetching rsync-3.4.1_6: 100%   396 KiB 202.5 kB/s    00:02  [4/5] Fetching liblz4-1.10.0_2,1: 100%   178 KiB 182.5 kB/s    00:01  [5/5] Fetching zstd-1.5.7_1: 100%   509 KiB 520.9 kB/s    00:01  Checking integrity... done (0 conflicting)  [1/5] Installing libiconv-1.18_1...  [1/5] Extracting libiconv-1.18_1: 100%  [2/5] Installing liblz4-1.10.0_2,1...  [2/5] Extracting liblz4-1.10.0_2,1: 100%  [3/5] Installing xxhash-0.8.3...  [3/5] Extracting xxhash-0.8.3: 100%  [4/5] Installing zstd-1.5.7_1...  [4/5] Extracting zstd-1.5.7_1: 100%  [5/5] Installing rsync-3.4.1_6...  [5/5] Extracting rsync-3.4.1_6: 100% 
    #FreeBSD #FreeBSD15 #FreeBSD150 #FreeBSD151 #news #Tech #Technology #update
  23. GhostBSD 26.1 is officially released. Runs on FreeBSD 15, drops Xorg for XLibre, ships Zsh as default shell and adds WireGuard support.

    Full details here: ostechnix.com/ghostbsd-26-1-re

    #Ghostbsd261 #Freebsd15 #BSD #Unix #Releases #Opensource

  24. GhostBSD 26.1 is officially released. Runs on FreeBSD 15, drops Xorg for XLibre, ships Zsh as default shell and adds WireGuard support.

    Full details here: ostechnix.com/ghostbsd-26-1-re

    #Ghostbsd261 #Freebsd15 #BSD #Unix #Releases #Opensource

  25. GhostBSD 26.1 is officially released. Runs on FreeBSD 15, drops Xorg for XLibre, ships Zsh as default shell and adds WireGuard support.

    Full details here: ostechnix.com/ghostbsd-26-1-re

    #Ghostbsd261 #Freebsd15 #BSD #Unix #Releases #Opensource

  26. GhostBSD 26.1 is officially released. Runs on FreeBSD 15, drops Xorg for XLibre, ships Zsh as default shell and adds WireGuard support.

    Full details here: ostechnix.com/ghostbsd-26-1-re

    #Ghostbsd261 #Freebsd15 #BSD #Unix #Releases #Opensource

  27. GhostBSD 26.1 is officially released. Runs on FreeBSD 15, drops Xorg for XLibre, ships Zsh as default shell and adds WireGuard support.

    Full details here: ostechnix.com/ghostbsd-26-1-re

    #Ghostbsd261 #Freebsd15 #BSD #Unix #Releases #Opensource

  28. SpecProbe 3.8.1 is now available for FreeBSD support

    As we have completed our initial implementation of the platform support for FreeBSD in SpecProbe, we have finished our implementation of the initial hardware support for FreeBSD in the library.

    SpecProbe v3.8.1 is now available to download from NuGet! This version of SpecProbe focuses explicitly on adding initial support for FreeBSD systems, which provides both software platform and hardware parsing support for this platform.

    SpecProbe’s implementation for FreeBSD’s code path relies on common tools that were used to get system information, such as a list of connected hardware drives, which is fetched mostly from gpart(8) and sysctl(8).

    You can find more information about this release here.

    Learn more #FreeBSD #FreeBSD15 #FreeBSD150 #news #specprobe #Tech #Technology #update
  29. SpecProbe 3.8.1 is now available for FreeBSD support

    As we have completed our initial implementation of the platform support for FreeBSD in SpecProbe, we have finished our implementation of the initial hardware support for FreeBSD in the library.

    SpecProbe v3.8.1 is now available to download from NuGet! This version of SpecProbe focuses explicitly on adding initial support for FreeBSD systems, which provides both software platform and hardware parsing support for this platform.

    SpecProbe’s implementation for FreeBSD’s code path relies on common tools that were used to get system information, such as a list of connected hardware drives, which is fetched mostly from gpart(8) and sysctl(8).

    You can find more information about this release here.

    Learn more #FreeBSD #FreeBSD15 #FreeBSD150 #news #specprobe #Tech #Technology #update
  30. SpecProbe 3.8.1 is now available for FreeBSD support

    As we have completed our initial implementation of the platform support for FreeBSD in SpecProbe, we have finished our implementation of the initial hardware support for FreeBSD in the library.

    SpecProbe v3.8.1 is now available to download from NuGet! This version of SpecProbe focuses explicitly on adding initial support for FreeBSD systems, which provides both software platform and hardware parsing support for this platform.

    SpecProbe’s implementation for FreeBSD’s code path relies on common tools that were used to get system information, such as a list of connected hardware drives, which is fetched mostly from gpart(8) and sysctl(8).

    You can find more information about this release here.

    Learn more #FreeBSD #FreeBSD15 #FreeBSD150 #news #specprobe #Tech #Technology #update
  31. SpecProbe 3.8.1 is now available for FreeBSD support

    As we have completed our initial implementation of the platform support for FreeBSD in SpecProbe, we have finished our implementation of the initial hardware support for FreeBSD in the library.

    SpecProbe v3.8.1 is now available to download from NuGet! This version of SpecProbe focuses explicitly on adding initial support for FreeBSD systems, which provides both software platform and hardware parsing support for this platform.

    SpecProbe’s implementation for FreeBSD’s code path relies on common tools that were used to get system information, such as a list of connected hardware drives, which is fetched mostly from gpart(8) and sysctl(8).

    You can find more information about this release here.

    Learn more #FreeBSD #FreeBSD15 #FreeBSD150 #news #specprobe #Tech #Technology #update
  32. SpecProbe 3.8.1 is now available for FreeBSD support

    As we have completed our initial implementation of the platform support for FreeBSD in SpecProbe, we have finished our implementation of the initial hardware support for FreeBSD in the library.

    SpecProbe v3.8.1 is now available to download from NuGet! This version of SpecProbe focuses explicitly on adding initial support for FreeBSD systems, which provides both software platform and hardware parsing support for this platform.

    SpecProbe’s implementation for FreeBSD’s code path relies on common tools that were used to get system information, such as a list of connected hardware drives, which is fetched mostly from gpart(8) and sysctl(8).

    You can find more information about this release here.

    Learn more #FreeBSD #FreeBSD15 #FreeBSD150 #news #specprobe #Tech #Technology #update
  33. 🚧 Ah, FreeBSD 15's new "bridging" act—brought to you by the same innovators who think deprecating features without a plan is a cool party trick. 🎩 VLAN support? Check. Confusing sysctls? Check. Of course, they graciously leave future headaches to sort out the whole router-on-a-stick mess. 🎉✨
    blog.feld.me/posts/2026/02/usi #FreeBSD15 #Bridging #VLANs #Sysctls #Innovation #Networking #HackerNews #ngated

  34. 🚧 Ah, FreeBSD 15's new "bridging" act—brought to you by the same innovators who think deprecating features without a plan is a cool party trick. 🎩 VLAN support? Check. Confusing sysctls? Check. Of course, they graciously leave future headaches to sort out the whole router-on-a-stick mess. 🎉✨
    blog.feld.me/posts/2026/02/usi #FreeBSD15 #Bridging #VLANs #Sysctls #Innovation #Networking #HackerNews #ngated

  35. 🚧 Ah, FreeBSD 15's new "bridging" act—brought to you by the same innovators who think deprecating features without a plan is a cool party trick. 🎩 VLAN support? Check. Confusing sysctls? Check. Of course, they graciously leave future headaches to sort out the whole router-on-a-stick mess. 🎉✨
    blog.feld.me/posts/2026/02/usi #FreeBSD15 #Bridging #VLANs #Sysctls #Innovation #Networking #HackerNews #ngated

  36. 🚧 Ah, FreeBSD 15's new "bridging" act—brought to you by the same innovators who think deprecating features without a plan is a cool party trick. 🎩 VLAN support? Check. Confusing sysctls? Check. Of course, they graciously leave future headaches to sort out the whole router-on-a-stick mess. 🎉✨
    blog.feld.me/posts/2026/02/usi #FreeBSD15 #Bridging #VLANs #Sysctls #Innovation #Networking #HackerNews #ngated

  37. Installed and running FreeBSD 15p1 on a Thinkpad X200. Was concerned about it being just a core 2 duo and equipped only with 4GB RAM. But to my delight it is actually quite usable for typical mild use. XFCE Desktop. Even Firefox runs ok. Just 5GB of 256GB SSD used. 👍️ 😊
    #freebsd #freebsd15 #x200 #thinkpad

  38. Installed and running FreeBSD 15p1 on a Thinkpad X200. Was concerned about it being just a core 2 duo and equipped only with 4GB RAM. But to my delight it is actually quite usable for typical mild use. XFCE Desktop. Even Firefox runs ok. Just 5GB of 256GB SSD used. 👍️ 😊
    #freebsd #freebsd15 #x200 #thinkpad

  39. Installed and running FreeBSD 15p1 on a Thinkpad X200. Was concerned about it being just a core 2 duo and equipped only with 4GB RAM. But to my delight it is actually quite usable for typical mild use. XFCE Desktop. Even Firefox runs ok. Just 5GB of 256GB SSD used. 👍️ 😊
    #freebsd #freebsd15 #x200 #thinkpad

  40. Installed and running FreeBSD 15p1 on a Thinkpad X200. Was concerned about it being just a core 2 duo and equipped only with 4GB RAM. But to my delight it is actually quite usable for typical mild use. XFCE Desktop. Even Firefox runs ok. Just 5GB of 256GB SSD used. 👍️ 😊
    #freebsd #freebsd15 #x200 #thinkpad

  41. Installed and running FreeBSD 15p1 on a Thinkpad X200. Was concerned about it being just a core 2 duo and equipped only with 4GB RAM. But to my delight it is actually quite usable for typical mild use. XFCE Desktop. Even Firefox runs ok. Just 5GB of 256GB SSD used. 👍️ 😊
    #freebsd #freebsd15 #x200 #thinkpad

  42. #FreeBSD15 erkennt jetzt offenbar schon Hardware bei der Installation und installiert die benötigten Treiber. Cool.

    #FreeBSD #BSD
  43. #FreeBSD15 erkennt jetzt offenbar schon Hardware bei der Installation und installiert die benötigten Treiber. Cool.

    #FreeBSD #BSD
  44. #FreeBSD15 erkennt jetzt offenbar schon Hardware bei der Installation und installiert die benötigten Treiber. Cool.

    #FreeBSD #BSD
  45. #FreeBSD15 erkennt jetzt offenbar schon Hardware bei der Installation und installiert die benötigten Treiber. Cool.

    #FreeBSD #BSD