@CiotBSD said: OpenShift For people who never heard of it (there's no link in the article …) r/openshift in old and new Reddit: The OpenShift Application Platform is Red Hat's enterprise-ready Kubernetes distribution, optimized for continuous application development and multi-tenant deployment. A professional community to discuss OpenShift and OKD, Red Hat's auto-scaling Platform as a Services (PaaS) for applications. Red Hat OpenShift Build, accelerate, and scale with an application platform that’s built for today's workloads and tomorrow's innovation. Deliver a comprehensive experience to modernize and build new applications, accelerate AI adoption, and fuel growth. Red Hat’s OpenShift vs FreeBSD Jails - Klara Systems (2022) Kubernetes has become a hot technology for managing clusters of applications, but it is famously difficult technology to use and understand. RedShift is an Enterprise cloud platform for running and managing Kubes without tying you into a single platform. FreeBSD is our favorite platform for running applications here at Klara, how does RedShift relate to the technologies that FreeBSD provides and can we create similar environments on top of FreeBSD?

Hey, thanks! Now I know to keep them cooler.

...and it was an idiot error. I had to enable wg in the host kernel. I knew it was built into the kernel these days...I just hadn't realised I needed to enable it. -->facepalm<--

@grahamperrin Optimus is a trademark of NVIDIA for their implementation of hybrid graphics.And other manufacturers like AMD calls almost the same thing differently.From the CPU-side of the view, PRIME is the underlying interface for iGPU and dGPU (not limited with NVIDIA) to offload heavy graphics tasks to mighty dGPU, mainly using efficient (but poor in performance) iGPU.Before Austin's port of nvidia-drm.ko appears, the only "working" way to achieve hybrid graphics was to use VirtualGL, with configuring individual "screen" for iGPU and dGPU respectively, and screen rendered by dGPU was needed to be transferred to another (for iGPU) with software BitBlt, as physical framebuffer cannot be shared with this method.And current implementation of nvidia-drm.ko relies on PRIME to work. Without PRIME, there's no way (arbitrations) for dGPU to access (part of) physical framebuffer of iGPU.See detailed and precise info by Austin here. https://badland.io/prime-configuration.md

@CiotBSD said: ⇒ FreeBSD 16 Retires The Last Of Its GPL Code From Its Base System Via @governa@fosstodon.org at https://fosstodon.org/@governa/117006685536082407 FreeBSD's Kernel Still Has A Bit Of GPL Code While Its Base User-Space Is GPL-Free - Phoronix

26/07/26 ⇒ All my FreeBSD boxes are now on 15.1 Jason asked me on a recent BSD Now if I’d made the switch to FreeBSD 15.1-RELEASE. I said that I had, and that the upgrade was entirely uneventful! Which is my favourite kind of upgrade. https://www.rubenerd.au/all-my-freebsd-boxes-are-now-on-15-1/

The Wine 11.14 development release is officially out now bringing with it an assortment of new features to improve Windows apps / games on other platforms. https://www.gamingonlinux.com/2026/07/wine-11-14-brings-improvements-for-directsound-bcrypt-freebsd/ https://www.phoronix.com/news/Wine-11.14-Released https://gitlab.winehq.org/wine/wine/-/releases/wine-11.14 New WoW64 mode supported on FreeBSD.

chvt(or whatever is analogous in bsdland) works as intended?

An example root@freebsd-15-amd64-qemu:~ # pkg upgrade -Fqy root@freebsd-15-amd64-qemu:~ # pkg upgrade -U New version of pkg detected; it needs to be installed first. Checking integrity... done (0 conflicting) The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pkg: 2.7.5 -> 2.8.0_1 [FreeBSD-ports] Number of packages to be upgraded: 1 The process will require 25 MiB more space. Proceed with this action? [y/N]: y [1/1] Upgrading pkg from 2.7.5 to 2.8.0_1... [1/1] Extracting pkg-2.8.0_1: 100% pkg: need to re-create repo FreeBSD-ports to upgrade schema version pkg: Repository FreeBSD-ports cannot be opened. 'pkg update' required pkg: need to re-create repo FreeBSD-ports-kmods to upgrade schema version pkg: Repository FreeBSD-ports-kmods cannot be opened. 'pkg update' required Checking for upgrades (0 candidates): 100% Processing candidates (0 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. root@freebsd-15-amd64-qemu:~ # pkg update Updating FreeBSD-ports repository catalogue... pkg: need to re-create repo FreeBSD-ports to upgrade schema version Fetching meta.conf: 100% 168 B 0.2 kB/s 00:01 Fetching data: 100% 12 MiB 907.0 kB/s 00:14 Processing entries: 100% FreeBSD-ports repository update completed. 38008 packages processed. Fetching files: 100% 41 MiB 1.3 MB/s 00:33 Processing file entries: 100% Updating FreeBSD-ports-kmods repository catalogue... pkg: need to re-create repo FreeBSD-ports-kmods to upgrade schema version Fetching meta.conf: 100% 179 B 0.2 kB/s 00:01 Fetching data: 100% 35 KiB 36.0 kB/s 00:01 Processing entries: 100% FreeBSD-ports-kmods repository update completed. 240 packages processed. All repositories are up to date. root@freebsd-15-amd64-qemu:~ # pkg upgrade -Fqy root@freebsd-15-amd64-qemu:~ # pkg upgrade -U Checking for upgrades (124 candidates): 100% Processing candidates (124 candidates): 100% Checking integrity... done (0 conflicting) The following 123 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: boost-libs: 1.89.0_2 -> 1.89.0_3 [FreeBSD-ports] … xwud: 1.0.7 -> 1.0.8 [FreeBSD-ports] Installed packages to be REINSTALLED: xorg-docs-1.7.3,1 [FreeBSD-ports] (ABI changed: 'FreeBSD:15:amd64' -> 'FreeBSD:15:*') Number of packages to be upgraded: 122 Number of packages to be reinstalled: 1 The operation will free 5 MiB. Proceed with this action? [y/N]: y [ 1/123] Upgrading boost-libs from 1.89.0_2 to 1.89.0_3... [ 1/123] Extracting boost-libs-1.89.0_3: 100% … [123/123] Upgrading xwud from 1.0.7 to 1.0.8... [123/123] Extracting xwud-1.0.8: 100% ==> Running trigger: desktop-file-utils.ucl Building cache database of MIME types ==> Running trigger: gtk-update-icon-cache.ucl Generating GTK icon cache for /usr/local/share/icons/oxygen Generating GTK icon cache for /usr/local/share/icons/breeze-dark Generating GTK icon cache for /usr/local/share/icons/breeze Generating GTK icon cache for /usr/local/share/icons/hicolor ==> Running trigger: gdk-pixbuf-query-loaders.ucl Generating gdk-pixbuf modules cache ==> Running trigger: shared-mime-info.ucl Building the Shared MIME-Info database cache ==> Running trigger: glib-schemas.ucl Compiling glib schemas Warning: Schema “org.gnome.crypto.cache” has path “/desktop/gnome/crypto/cache/”. Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated. Warning: Schema “org.gnome.crypto.pgp” has path “/desktop/gnome/crypto/pgp/”. Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated. Warning: Schema “org.gnome.system.locale” has path “/system/locale/”. Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated. Warning: Schema “org.gnome.system.proxy” has path “/system/proxy/”. Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated. Warning: Schema “org.gnome.system.proxy.http” has path “/system/proxy/http/”. Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated. Warning: Schema “org.gnome.system.proxy.https” has path “/system/proxy/https/”. Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated. Warning: Schema “org.gnome.system.proxy.ftp” has path “/system/proxy/ftp/”. Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated. Warning: Schema “org.gnome.system.proxy.socks” has path “/system/proxy/socks/”. Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated. root@freebsd-15-amd64-qemu:~ # history 7 363 19:03 exit 364 7:17 pkg upgrade -Fqy 365 7:22 pkg upgrade -U 366 7:23 pkg update 367 7:27 pkg upgrade -Fqy 368 7:27 pkg upgrade -U 369 7:31 history 7 root@freebsd-15-amd64-qemu:~ # exit logout blah@freebsd-15-amd64-qemu:~ % freebsd-version -kru ; uname -mvKU 15.1-RELEASE-p1 15.1-RELEASE-p1 15.1-RELEASE-p1 FreeBSD 15.1-RELEASE-p1 releng/15.1-n283582-0f691888dc56 GENERIC amd64 1501000 1501000 blah@freebsd-15-amd64-qemu:~ % pkg repos -el | sort -f ; sleep 5 ; pkg repos -e | grep -B 1 -e url FreeBSD-ports FreeBSD-ports-kmods FreeBSD-ports: { url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/latest", -- FreeBSD-ports-kmods: { url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/kmods_latest_1", blah@freebsd-15-amd64-qemu:~ % date Sun Jul 26 07:32:34 BST 2026 blah@freebsd-15-amd64-qemu:~ % Note: … [1/1] Extracting pkg-2.8.0_1: 100% pkg: need to re-create repo FreeBSD-ports to upgrade schema version pkg: Repository FreeBSD-ports cannot be opened. 'pkg update' required pkg: need to re-create repo FreeBSD-ports-kmods to upgrade schema version pkg: Repository FreeBSD-ports-kmods cannot be opened. 'pkg update' required Checking for upgrades (0 candidates): 100% Processing candidates (0 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. …

redbsd@redbsd:~ $ pkg leaf 7-zip-26.02 ImageMagick7-7.1.2.25_1 aircrack-ng-1.5.2_4 apache-ant-1.10.15_2 apache24-2.4.68 automake-1.18.1 bind-tools-9.20.24_1 ca_root_nss-3.125 cherrytree-1.7.0 cmake-3.31.12 crunch-3.6_1 doas-6.4 dotnet-9.0.14 dotnet8-8.0.27 engrampa-1.28.2_1 firefox-esr-153.0,2 freerdp3-3.30.0 gcc-14_5 gdb-15.1_5 geany-2.1 git-2.54.0 go-1.25_20,2 gradle-9.6.1 hashcat-7.1.2_11,1 hs-pandoc-3.10 htop-3.5.1 john-1.9.0.j.1_1 kismet-2016.07.r1_2,1 kubectl-1.36.1_2 libtool-2.5.4_1 lighttpd-1.4.84_1 linux-rl9-libxkbcommon-1.0.3_2 linux-rl9-xcb-util-0.4.0_2 llvm-19_1,1 lsof-4.99.5,8 mariadb1011-client-10.11.18 maven-3.8.9_3 mercurial-7.1.2 nano-9.0 nginx-1.30.4,3 ninja-1.13.2,4 nmap-7.99_1 node-24.18.0_3 noto-basic-2.0_4 npm-11.18.0 open-vm-tools-13.1.0,2 openjdk17-17.0.18+8.1 openjdk21-21.0.10+7.1_1 openssl-3.0.21,1 papirus-icon-theme-20250501 pavucontrol-6.1 php83-curl-8.3.32_1 php83-mbstring-8.3.32_1 php83-mysqli-8.3.32_1 php83-pdo_sqlite-8.3.32_1 php83-zip-8.3.32_1 pixiewps-1.4.1 podman-5.8.4_1 postgresql16-client-16.14 proxychains-ng-4.17 py312-certbot-4.2.0,1 py312-podman-compose-1.5.0 py312-pwntools-4.15.0_1 py312-virtualenv-21.2.3 python3-3_4 radare2-6.1.4 reaver-1.6.6_1 redis-8.8.0 ripgrep-15.1.0_6 ristretto-0.14.0 rizin-0.9.1 rsync-3.4.4_1 ruby-3.4.9_2,1 rust-1.96.1 screen-5.0.1_6 sddm-0.21.0.36_3 socat-1.8.1.3 sqlitebrowser-3.13.1 subversion-1.14.5_1 sudo-1.9.17p2_2 tcpdump-4.99.6 thunar-archive-plugin-0.6.0 tmux-3.7b tree-2.3.2 trivy-0.72.0_1 vim-9.2.0738 virtualbox-ose-additions-72-7.2.14.1500068 vscode-1.127.0_1 wget-1.25.0 whois-5.5.7_1 xf86-video-vmware-13.4.0 xfce-4.20_2 xfce4-screenshooter-plugin-1.11.3 xmlstarlet-1.6.1_5 xorg-7.7_3 yq-4.1.1 zig-0.16.0 zip-3.0_5 zsh-5.9.1 redbsd@redbsd:~ $

Thanks! Comments from Kyle Evans (FreeBSD Core Team) and others: FreeBSD Ports Repository Freeze : r/freebsd Action Required: Recent ports history has been rewritten : r/freebsd

Thanks, Jails, Not Containers: FreeBSD Isolation Done Right Posted separately in Mastodon, https://mastodon.bsd.cafe/@grahamperrin/116976955869878432 (https://mastodon.bsd.cafe/search?q=Jails%2C Not Containers%3A FreeBSD Isolation Done Right) can not find your https://mastodon.bsd.cafe/@ciotbsd@billboard.bsd.cafe/116913345978489881.)

⇒ BSDCan 2026 Travel Report – Novković Bojan Novković, I assume. From their report: … two “Have/Need/Want” planning sessions, … FreeBSD 16.0 Planning – devsummit/16.0/planning.md ⋯ bsdjhb/devsummit : r/freebsd

...and at long last: it wasn't a bug, it wasn't bad documentation, it wasn't BSD's fault in any way. The 540 in the 12+2 configuration has 12 drive slots on the front and 2 on the rear. Turns out that something, I have no idea what, means that while a SATA drive is recognised for boot (with UEFI) in the rear 2 plane, a SAS drive is not. It's a Weird Hardware Thing, and not something FreeBSD or the excellent handbook could, or should, ever have known about. Now I'm off sorting out VNET jails to run Nextcloud.

26/07/17 ⇒ Updating FreeBSD 15.0 to FreeBSD 15.1 (via pkgbase) I decided that Thursday morning at 8:27 AM was the right time to start my first update from FreeBSD 15.0 to 15.1 – all my hosts are now on pkgbase. I used the pgkbasify script. Now it’s time to update again. https://dan.langille.org/2026/07/17/updating-freebsd-15-0-to-freebsd-15-1-via-pkgbase/

I have requested deletion of my Bugzilla accounts. Done For posterity, my first report and the last of my open reports: 203271 (September 2015) 295197 (May 2026). … I expect my name to change to devnull – not to be confused with other devnull users, … The expectation was based on devnull's Delete account case (271795) – seeking a Delete account report from devnull finds nothing.

https://klarasystems.com/articles/native-inotify-in-freebsd/ – Mark Johnston A seemingly simple file monitoring problem exposed deep limitations in FreeBSD’s traditional EVFILT_VNODE approach. This article explores how race conditions, scalability issues, and Linux compatibility challenges ultimately led to the development of a native inotify implementation for FreeBSD 15. … @klarainc@bird.makeup (automated)

@grahamperrin Thanks! I read both the comment and the reply. It looks like, conceptually, we came up with the same solution. The main question is what data he used to generate the JSON file and under what license that data is distributed.

Code That Built the Internet: The Impact of BSD, Part 2 - Linux Professional Institute (LPI)