Skip to content

World

Topics from outside of this forum. Views and opinions represented here may not reflect those of this forum and its members.

A world of content at your fingertips…

Think of this as your global discovery feed. It brings together interesting discussions from across the web and other communities, all in one place.

While you can browse what's trending now, the best way to use this feed is to make it your own. By creating an account, you can follow specific creators and topics to filter out the noise and see only what matters to you.

Ready to dive in? Create an account to start following others, get notified when people reply to you, and save your favorite finds.

Register Login
  • CiotBSDC

    FreeBSD 15.2 Will Aim For The Nice KDE Desktop Installation Experience

    FreeBSD 15.0 had aimed to provide a KDE desktop install option from its text-based OS installer to make for a more compelling FreeBSD out-of-the-box desktop experience. That was then delayed to FreeBSD 15.1 but that didn't end up materializing. Now the KDE desktop install option is diverted to FreeBSD 15.2...


    @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
  • grahamperrinG

    A follow-up to https://mastodon.bsd.cafe/@82mhz/117002938483503805 @82mhz

    The linked article (June 2026) began:

    The work at Include Security has us working with AI day in and day out (hacking it, using it, training it, etc). ..

    – 18–23 minutes, according to Firefox Reader.

    I used AI to get a concise timeline. The text below is taken from Claude's response.


    The general practice: 2015

    The root of it all is Hola VPN / Luminati (Bright Data's predecessor). In May 2015, it was discovered that Hola — a free "VPN" — was quietly turning users' devices into paid exit nodes sold through a sibling brand, Luminati, at up to $20/GB. The discovery came after 8chan's admin, Frederick Brennan, traced a wave of DDoS/spam attacks against his site back to Hola users being abused as a botnet, and outlets like The Register, Fortune/Motherboard, and TechRadar covered it within days. Hola's Luminati brand was described as "the world's largest VPN network," routing HTTP, HTTPS, or TLS requests through millions of idling end-user devices. Luminati (founded 2014) was Hola's mechanism for selling access to its userbase as exit nodes, charging $20 per gigabyte for bandwidth from its free VPN users, and it later rebranded as Bright Data. So the general "your free app is secretly selling your connection as a proxy" pattern is a 2015 story, not a 2026 one.

    The smart-TV-specific angle: February 2026

    The TV angle specifically is much newer, and predates the IncludeSecurity teardown by about three and a half months. Independent tech journalist Janko Roettgers broke it in his Lowpass newsletter (syndicated by The Verge) in late February 2026: with Bright's SDK, a viewer's smart TV becomes part of a massive global proxy network that crawls and scrapes the web, alongside apps on desktop PCs and mobile devices, with the company claiming roughly 150 million such residential proxies worldwide, gathering data later resold to train AI models. Multiple later write-ups explicitly credit this as the origin point: "Lowpass, syndicated by The Verge, first surfaced the smart-TV angle in February, and this is the technical teardown."

    The AI-scraping tie-in and platform response: 2025–early 2026

    Around the same period, the broader AI-scraping-via-residential-proxy story was already building: Krebs reported in October 2025 on botnets like Aisuru fueling large-scale AI data harvesting, and Google dismantled the criminal IPIDEA proxy network in January 2026. By April 2026, FlatpanelsHD was reporting that Amazon, Google and Roku had restricted Bright Data and similar residential proxy networks from their app SDKs (Fire TV, Google TV, Roku OS), while Bright Data continued listing LG's webOS and Samsung's Tizen as partners, with over 200 apps on webOS alone.

    Your June 2026 post: the deep technical teardown

    The IncludeSecurity/Buchodi post you linked was the first to actually reverse-engineer the SDK rather than just report on the business model — documenting the peer channel's weak authentication and the iOS VPN bypass — which is why it got picked up so widely (Hacker News, Krebs, CyberSecurityNews, etc.) even though the underlying phenomenon was already known.

    Aftermath

    A follow-up Spur.us platform scan in June 2026 quantified the scale: Bright Data, Bright Data Ltd, and Bright SDK accounted for 367 proxy-flagged apps in their dataset, with residential proxy SDKs found in nearly half of scanned LG webOS apps and over a quarter of Samsung Tizen apps. And just last week, Krebs on Security reported LG moving to ban these SDKs from its smart TV apps entirely.

    So the short answer: the general practice (apps quietly monetizing users' devices as residential proxy exit nodes) was first exposed in 2015 with Hola/Luminati; the smart-TV-specific version of that story broke in February 2026 via Lowpass/The Verge; and your June 2026 link is the deep technical forensic follow-up, not the original discovery.


  • grahamperrinG

    @tomaoki

    Perhaps the title is difficult to perceive when, for example, the screen is busy.

    I had this difficulty more than once in the past.

    An example:

    407fd625-b6a2-44a6-a5d2-d75ec3807994-image.jpeg


    Here's the title: [image: 1785202914963-dad79b73-5dbc-4b83-ac05-c3326b52f602-image.jpeg] above the editing toolbar. The position is unexpected.
  • grahamperrinG

    https://daniel.haxx.se/blog/2026/04/22/high-quality-chaos/ via https://mastodon.social/@bagder/116448188069484288 (2026-04-22) – not recent, but it's news to me.

    From today's post about last month's Ottawa FreeBSD Developer Summit:

    Michael Winser – Alpha Omega – The Changing Landscape of Open Source Software Security

    AI has entered the chat

    A frame from Winser's presentation:

    9a762f41-ee1e-471a-9e56-b4100b9d01a5-image.jpeg

    Daniel Stenberg on AI in security ― sentiment over time

    From Stenberg's blog post:

    Everything is AI now

    Almost every security report now uses AI to various degrees. You can tell by the way they are worded, how the report is phrased and also by the fact that they now easily get very detailed duplicates in ways that can’t be done had they been written by humans.

    The difference now compared to before however, is that they are mostly very high quality.

    The reporters rarely mention exactly which AI tool or model they used (and really, we don’t care), but the evidence is strong that they used such help.

    We are not unique

    I did a quick unscientific poll on Mastodon to see if other Open Source projects see the same trends and man, do they! Friends from the following projects confirmed that they too see this trend. …

    Additional tag: AI

    #ai is currently not possible in (NodeBB) BSD Cafe Billboard.


  • CiotBSDC

    Call to undefined function filter_var() on FreeBSD


    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/
  • CiotBSDC

    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.

    New WoW64 mode supported on FreeBSD.


  • grahamperrinG

    No response to normal keyboard or mouse input at ttyv8, so login to a desktop environment is impossible.

    Using Virtual Machine Manager to key Ctrl+Alt+F2 (pictured below) does not switch to ttyv1.

    4fb46dea-e1b2-4562-88ca-40cf4c8d99b4-image.jpeg

    Weird.

    This machine did previously work.

    Comparison

    I'm reminded of a bug that sometimes prevents use of vt(4) in VirtualBox, however I doubt that the root causes are the same:


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

    True enlightment only comes from a truly free computing experience, probably! And while there is no nerd who lacks an opinion on Richard Stallman personally, likewise let none claim he does not practice what he preaches. Why, the very laptop in front of him was selected deliberately because it can operate with no binary blobs and no firmware you couldn't examine or replace with your own, and runs his choice of fully libre operating systems. The fact it has a Chinese MIPS64 derivative in it was undoubtedly just more compound on the heat spreader.


    @CiotBSD OT = off topic
  • grahamperrinG

    A sequence of commands:

    1. pkg upgrade -Fqy
    2. pkg upgrade -U
    3. pkg update
    4. pkg upgrade -Fqy
    5. pkg upgrade -U

    Normally

    If updates are available – and if there are no solver conflicts in response to the first command:

    • all updates will be listed following the second command.

    With the upgrade of pkg from 2.7.5 to 2.8.0_1

    The second command is followed by:

    • a prompt to run pkg update
    • "Your packages are up to date."

    – and the packages are not necessarily up-to-date.

    For the truth, you must run pkg update and then again pkg upgrade


    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. …
  • grahamperrinG

    https://www.redbsd.org/

    … a FreeBSD-based distribution loaded with a curated red team and penetration testing toolkit, an XFCE-derived desktop, and VMware-ready images — built for operators who want a fast, stable alternative to Linux-based distros. …

    f38152f6-9314-4558-bb86-b355630c9ca7-image.jpeg

    https://greyprotocolsecurity.com/

    RTFMv2 is the offensive security operations platform that combines structured checklists, automated scan integrations, and AI-assisted reporting—everything you need to finish assessments faster and with zero gaps.

    This is neither an advertisement nor an endorsement.

    I used RedBSD-1.20260713-amd64-installer.iso with Oracle VirtualBox 7.2.14 r174565 on Kubuntu 26.04:

    1. allowed the default set of RedBSD packages
    2. shutdown -r now
    3. installed emulators/virtualbox-ose-additions-72 and enabled its two services
    4. edited /boot/loader.conf and /etc/rc.conf to make SDDM and the desktop environment work with VirtualBox instead of VMware
    5. enabled and started the two services for VirtualBox
    6. service sddm restart

    Security notes

    RedBSD's provisioning scripts make choices that are convenient for an isolated lab but are not safe on an untrusted or internet-facing network:

    Additional background

    Six Reddit posts:

    1. Red Team Oriented BSD OS : r/BSD (2026-06-15)
    2. Red BSD scam or real? : r/BSD (2026-06-16)
    3. RedBSD : r/freebsd (2026-07-10)
    4. RedBSD: Um FreeBSD para cyberseguranca : r/FreeBSD_BR (2026-07-10)
    5. RedBSD seems like only FreeBSD 15.1 : r/freebsd (2026-07-23)
    6. RedBSD continued. First Run. : r/freebsd (2026-07-24)

    Thanks to @jbz@indieweb.social for the Mastodon post that sparked my interest in RedBSD.


    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:~ $
  • T

    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
  • CiotBSDC

    26/07/11

    Jails, Not Containers: FreeBSD Isolation Done Right

    Containers play a major role in modern infrastructure, but they are not the right answer for every workload. This article explores how FreeBSD jails provide purpose-built isolation, predictable security boundaries, and deep ZFS integration—making them ideal infrastructure-grade services where stability is essential.


    read more →
    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.)
  • CiotBSDC

    FreeBSD becoming NIST FIPS 140-3 compliant

    A key component for FreeBSD becoming NIST FIPS 140-3 compliant was completed when FreeBSD upgraded from OpenSSL 3.0 to 3.5. One of the other requirements for FIPS 140-3 (and post-quantum cryptography) is having sufficient random entropy in the system to generate sufficiently random numbers. NIST SP800-90B provides some guidelines on how to achieve that…


    PS: This strikes me as a significant development, which is why I am posting it here 😉


    ⇒ 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
  • CiotBSDC

    (06/04)

    Linux 7.2 Will Be Able To Boot On Apple M3 Macs - But Far From Useful For End-Users

    The upcoming Linux 7.2 mainline kernel is expected to be able to boot on Apple M3 devices including the M3-powered iMac and MacBook products. But before getting too excited it's still a long ways to go before it will actually be useful for any Apple M3 daily usage under Linux with the overall support at this stage still being very limited for these 2~3 year old Apple Macs…


    (06/05)

    Linux 7.2 Continues Improving AMDGPU Support On POWER, ARM

    In addition to AMDGPU finally seeing HDMI 2.1 FRL support in Linux 7.2, another change worth noting in this week's AMDGPU pull request is the continued work on enhancing the AMDGPU/AMDKFD kernel driver support for non-4K page size kernel builds. In particular this helps out with AMD graphics and ROCm for the likes of ARM and POWER…

    NVIDIA's Nova Driver Continues Being Built Up In Linux 7.2 Along With Other DRM Rust Code

    Danilo Krummrich sent out the main set of DRM Rust subsystem changes on Thursday that are targeting the Linux 7.2 kernel. NVIDIA's open-source Nova driver continues seeing a bulk of the DRM Rust work as this modern successor to Nouveau continues taking shape.

    More SpacemiT K3 & K1 Support Landing In Upstream Linux 7.2

    In addition to Apple M3 Device Trees for Linux 7.2, the SpacemiT RISC-V SoCs are seeing some notable Device Tree improvements with this next version of the Linux kernel.


    26/07/20 ⇒ Linux 7.2 Improves Intel Panther Lake Xe3 Arc B390 Graphics Performance My testing of the in-development Linux 7.2 kernel continues in the lab. One of the latest promising findings from this kernel that will be released as stable in August is faster Intel Xe3 graphics performance on Core Ultra Series 3 "Panther Lake" hardware. https://www.phoronix.com/review/linux-72-panther-lake
  • Y

    Gentlefolk,

    I brought myself back up to speed on FreeBSD by installing it on a T430 - ZFS and pkg install worked beautifully. Got Wayfire working, set up a jail to run a Luanti (Minetest) server. So far so good.

    Now I'm working on the real challenge, bringing up a Poweredge R540 which will have raid-3 ZFS and many jails. And my first problem is right at the very beginning. I can install FreeBSD (15.0) from a USB stick just fine, but when I try to get the machine to boot...

    (1) If I configure the 540 to boot from UEFI it cannot find the boot disk.
    (2) If I configure the 540 to boot from BIOS, it finds the disk and boots just fine.

    The Handbook is perhaps a bit out of date on this as it assumes BIOS, with a nod towards the possibility of UEFI. I'm guessing this problem has been solved many times over - could someone point me towards the solution?

    Many thanks,

    ---WBTD.


    ...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.
  • CiotBSDC

    26/07/18

    NextBSD returns to dollop Apple source on FreeBSD

    New maintainer revives the project with Darwin components, Gershwin, and Claude Code


  • CiotBSDC

    06/29

    Running pkgbasify on FreeBSD 15.1

    At BSDCan 2026, I attended the pkgbase in Production: A Practical Overview talk. What impressed me was the ease with which one could upgrade from 15.0 to 15.1 etc. Included in the demonstration was pkgbasify (“Automatically convert a FreeBSD system to use pkgbase”).


    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/
  • naltunN

    I recently visited a local YMCA branch and spotted a treadmill booting up... powered by OpenBSD.

    A crazy discovery xD If I can power a treadmill with OpenBSD then I'll attempt any embedded project with it.

    abe42f93-9f03-41c8-8ccd-e0bfc017b6de-image.jpeg
    0e924423-d9b1-450c-9cba-9b6e157c6fac-image.jpeg


    read more →
    Thanks to everyone who pointed out Linux. Now that I'm paying attention this is clearly the systemd startup logging.
  • grahamperrinG

    I have requested deletion of my Bugzilla accounts. I expect my name to change to devnull – not to be confused with other devnull users, at least one of whom has devnull in their email address.


    In the Lounge in April:

    … We're pro, not against. Supporters, not haters. Builders, not destroyers. …

    With the same spirit of positivity, in May I wrote:

    I'll continue to support users of FreeBSD in Mastodon, in r/freebsd, and elsewhere.


    read more →
    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.