The bastille convert sub-command will convert a thin jail to a thick jail if only the TARGET argument is given.
If a TARGET and RELEASE is specified, it will convert the jail into a custom release. The jail will remain intact, and you will have a duplicate of it to use a a release base for any new jails.
EXAMPLES
Convert myjail from thin to thick:
# bastille convert myjail
Create myrelease from myjail:
# bastille convert myjail myrelease
Current task: upgrading some FreeBSD hosts and jails from 14.3-RELEASE to 15.0-RELEASE.
Boring, as expected 🙂
@stefanoStefano Marinelli similarly boring, in a pleasant silent Sunday way:
– using pkgbase with FreeBSD 14 to work around a bug involving freebsd-update, which is not yet compatible with base packages.
Using pkgbase to put things right is the natural thing to do, when someone demands abandonment of pkgbase 😺
📦 https://lists.freebsd.org/archives/freebsd-hackers/2026-February/005736.html 🙄
Current task: upgrading some FreeBSD hosts and jails from 14.3-RELEASE to 15.0-RELEASE.
Boring, as expected 🙂
The #eurobsdcon 2026 Call for Papers is open!
https://2026.eurobsdcon.org/cfp/
Submit by June 20th, come to Brussels September 9-13 and mingle with #BSD people!
We also offer pre-submission guidance/mentoring, see within.
Wonder what BSD and the conferences are about? See https://nxdomain.no/~peter/what_is_bsd_come_to_a_conference_to_find_out.html
@EuroBSDCon #freebsd #netbsd #openbsd #freesoftware #libresoftware #brussels #bruxelles
one change in #FreeBSD pkgbase compared to freebsd-update is that when a kernel module is updated, you get an entire new kernel package (FreeBSD-kernel-generic) rather than just an updated module (foo.ko).
the downside is the update is larger, since the kernel package is about 45MB, but the upside is that because it updates /boot/kernel/kernel, the current patch level is always shown in uname -r after rebooting.
i think this is probably better overall, because a lot of people used to get confused about why they'd update to 15.0p3, but uname still showed 15.0p1, or whatever.
The #eurobsdcon call for papers is on!
https://2026.eurobsdcon.org/cfp/
We offer pre-submission mentoring, see within!
@EuroBSDCon #freebsd #netbsd #openbsd #freesoftware #libresoftware #brussels #bruxelles
epoll's handle-centric design is more composable than kqueue's filter-centric design (2021) via 
@RunxiYu https://lobste.rs/s/yixhnw #freebsd #linux #programming
https://ariadne.space/2021/06/05/actually-bsd-kqueue-is-a.html
Back in 2022, surrounded by colleagues who were infused with "open source scepticism", I wrote "Open Source in Enterprise Environments - Where Are We Now and What Is Our Way Forward?" https://nxdomain.no/~peter/opensource_enterprise_notes.html as an explainer.
Hopefully a useful thing for others too, with links therein #freesofware #opensource #enterprise #openbsd #freebsd #netbsd #linux
Conferences - #asiabsdcon is only a couple of weeks away, the call for papers for #eurobsdcon starts tomorrow, and #BSDCan is on for June.
Read more via "What is BSD? Come to a conference to find out!" https://nxdomain.no/~peter/what_is_bsd_come_to_a_conference_to_find_out.html #openbsd #netbsd #freebsd #freesoftware #development #networking #security
FreeBSD 14.4 release candidate – please test
<https://mail-archive.freebsd.org/cgi/mid.cgi?20260228000136.2C0F81F863>
– via <https://www.reddit.com/r/freebsd/comments/1rgs3mz/freebsd_144_release_candidate/>
Happy Friday #FreeBSD
#freebsd #runbsd enthusiasts, is this NOS (new) Sun Type 6 UNIX keyboard worth getting? looks nice and I love the novelty factor 
@vermaden 
@dexterMichael Dexter @stefanoStefano Marinelli
@mwlMichael W Lucas 
unpopular opinion: just create a separate mail account for the wiki and organize your categories with IMAP folders. people can write articles and can have their own offline copy. it should even work on every standard potato.
Cloud Native #FreeBSD talk @ #SCaLE20x round-up:
Talk: https://www.youtube.com/live/ReYon0HLj2k?feature=share&t=18035
Slides / talk notes / references: https://drive.google.com/drive/folders/1ewaoPhgSuWti35NOeRzsUIKHIQEhdqGK
My blog has lots of bhyve notes and how-tos: http://productionwithscissors.run/freebsd-virtualization-series/
We’ve published a new blog post outlining how we’re preparing for the European Union’s Cyber Resilience Act (CRA), and what it means for the FreeBSD ecosystem.
The CRA introduces new compliance expectations for products containing digital elements, including open source components.
Read the full post here:
https://freebsdfoundation.org/blog/getting-ready-for-the-cyber-resilience-act/
New to FreeBSD and not sure where to start? You’re not alone.
In this second video of the series, I'm walking through the FreeBSD Foundation's Getting Started page.
On this page, you’ll find:
— The official FreeBSD Handbook
— Installation guides for desktops and virtual machines
— Step-by-step written walkthroughs for common setup options
— Links to community spaces: forums, Discord, Reddit, and LinkedIn
https://freebsdfoundation.org/resource/getting-started-with-freebsd/
We can say that it was a great pleasure to meet Emmanuele ( 
@ebassiEmmanuele Bassi ), a developer behind the GNOME project.
Last year, we had the opportunity to meet the developer of Niri, a very personal project that it managed by himself. This episode is about a very large project, GNOME. With Emmanuele's help, we gained insights into GNOME and learned how an open-source project with several hundred developers works. https://www.trommelspeicher.de/podcast/special-the-gnome-project
#podcast #kuk #linux #gnome #freebsd
NEW VIDEO - Why Rust Is Causing Tension in the Linux Kernel.
#FreeBSD #Linux #Rust #opensource #garyhtech
https://youtu.be/-XLuGB0wZ1M?si=R3JBRFIYxUgunsMR via @YouTube
FreeBSD doesn't have Wi-Fi driver for my old MacBook. AI build one for me via 
@hongminhee洪 民憙 (Hong Minhee) 
https://lobste.rs/s/n6ybtt #freebsd #vibecoding
https://vladimir.varank.in/notes/2026/02/freebsd-brcmfmac/
Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟲/𝟬𝟮/𝟮𝟯 (Valuable News - 2026/02/23) available.
https://vermaden.wordpress.com/2026/02/23/valuable-news-2026-02-23/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
NAME
bastille jcp – Copy file(s)/directorie(s) from jail to jail(s).
SYNOPSIS
bastille jcp [-qx] SOURCE_JAIL JAIL_PATH DESTINATION_JAIL JAIL_PATH
DESCRIPTION
The bastille jcp sub-command will copy files and directories from a single jail to any targeted jail(s).
-q, --quiet : Suppress output.
-x, --debug : Enable debug mode.
EXAMPLES
Copy /etc/resolv.conf from myjail to yourjail:
# bastille jcp myjail /etc/resolv.conf yourjail /etc
The removal of TrueNAS legacy (CORE) leaves space for a tenth button.
What would you like?
The button need not be FreeBSD-specific. Discussions frequently attract users of other systems.
The sidebar of r/freebsd is crowded (very tall), and this cluster of buttons is relatively far down, so I doubt that it will gain much attention. Still, cafe community thoughts are welcome.
Three screenshots:
1. an overview of <https://www.reddit.com/r/freebsd/top/?sort=top&t=day> before removal of the TrueNAS button
2. the entire sidebar as represented at <https://sh.reddit.com/r/freebsd/about/>
3. focus on the other sub shortlist, and the other shortlist, within the sidebar.
Thanks.
RE: https://mastodon.bsd.cafe/@grahamperrin/115812989227244456
Background to the above:
1/ last year's change to the software status page for TrueNAS
2/ <https://github.com/freebsd/freebsd-doc/pull/607> (draft) for <https://www.freebsd.org/projects/newbies/>, suggested by 
@dgoodkindebgoodkin
＂A thoughtful walk through … FreeBSD 15.0—its design, discipline, and why composable systems still matter.
FreeBSD 15.0 quietly advances security, adapts to change with finesse, and reflects solid, intentional engineering. It powers some of the most flexible firewalls in use today and enables forward-looking filesystem design. It does not claim perfection, yet it consistently moves toward it. FreeBSD does not chase trends, influencers, or corporate fashion cycles. It focuses on doing essential work well, then stepping aside so the user remains in control. This release continues a long tradition of careful engineering, clarity of purpose, and architectural restraint. Some assume FreeBSD has faded away. Quality endures. Disorder eventually collapses. In this video, we take a slow walk through FreeBSD 15.0—its design goals, system requirements, storage footprint, shells, installation process, and the broader ecosystem that has grown around it. This is not a benchmark race or a feature checklist. It’s an exploration of why FreeBSD still matters, especially as operating systems increasingly reflect commercial priorities. If you’ve ever wondered what it feels like to use an operating system that understands its role and stays true to it, this tour is for you.＂
https://www.youtube.com/watch?v=gvJc5qHVLzg 
@djware
https://www.reddit.com/r/freebsd/comments/1q03ep3/freebsd_150_composable_by_design_dj_ware_the/
TrueNAS CORE finally disappeared from the software status page for TrueNAS.
For posterity, November and December 2025:
<https://web.archive.org/web/20251114033428/https://www.truenas.com/software-status/>
<https://web.archive.org/web/20251127043850/https://www.truenas.com/docs/softwarestatus/>
<https://web.archive.org/web/20251218152018/https://www.truenas.com/docs/softwarestatus/>
The removal of TrueNAS legacy (CORE) leaves space for a tenth button.
What would you like?
The button need not be FreeBSD-specific. Discussions frequently attract users of other systems.
The sidebar of r/freebsd is crowded (very tall), and this cluster of buttons is relatively far down, so I doubt that it will gain much attention. Still, cafe community thoughts are welcome.
Three screenshots:
1. an overview of <https://www.reddit.com/r/freebsd/top/?sort=top&t=day> before removal of the TrueNAS button
2. the entire sidebar as represented at <https://sh.reddit.com/r/freebsd/about/>
3. focus on the other sub shortlist, and the other shortlist, within the sidebar.
Thanks.
Y'know what? As an #opensource #advocate and #tech enthusiast, it's genuinely awesome to see increased mainstream coverage of #Linux and #FreeBSD. Unfortunately, a lot of these articles are riddled with mistakes, misinformation, clickbait, and overall low quality. A few minutes ago, while catching up on tech news I came across one #ZDNet author's frequent posts on Linux and FreeBSD.
To emphasize my point, I am only going to focus on one article titled, "After decades on Linux, FreeBSD finally gave me a reason to switch operating systems."
The following passages stuck out like sore thumb:
1.) "FreeBSD is more challenging than Linux."
-But is it really? Subjective, particularly if coming from a GUI-driven Linux distribution. Frankly I find FreeBSD easier because of the excellent documentation and coherent design.
2.) "FreeBSD is Unix-like" but further down he states, "Essentially, FreeBSD is Unix, where Linux is based on Unix."
-Contradictory, incorrect, and confusing for newcomers. FreeBSD is Unix. Linux (neither the kernel nor OS) is based on Unix.
3.) "Think of FreeBSD as a more challenging version of Linux. This operating system doesn't hold your hand, so you might learn a thing or two as you install it and the software you require. Even for a seasoned Linux veteran like me, FreeBSD can often be a head-scratcher."
-Challenging because it's *different than Linux*? FreeBSD doesn't hold your hand? What about #Debian, #Gentoo, #Arch, heck even #RHEL? Since the author didn't mention it, I'm going to assume he did not check the FreeBSD Handbook and his "seasoned Linux" experience has been using a Linux desktop for a couple years. Also, head-scratcher?! Being an experienced Debian user, I'd be scratching my head too if I just decided to use Gentoo on a whim. The trauma of hand-configuring the xorg.conf file was real.
Finally, contrary to the article's title, the author ended up not switching to FreeBSD.
-Clickbait.
I am all for more people exploring FreeBSD and Linux. They are great OSes but it is critical the information being reported is both accurate and consistent. For reference the article is linked below.
HTTP/3 on FreeBSD: Getting QUIC Working with nginx in a Bastille Jail | Larvitz Blog
https://blog.hofstede.it/http3-on-freebsd-getting-quic-working-with-nginx-in-a-bastille-jail/
HTTP/3 on FreeBSD: Getting QUIC Working with nginx in a Bastille Jail
What looked like a simple nginx config change turned into a tour through SSL library incompatibilities, pf firewall rules for a new protocol, and a multi-worker affinity problem that only shows up ...
blog.hofstede.it · Larvitz Blog
Link author: 
Larvitz 
@Larvitz@burningboard.net
HTTP/3 on FreeBSD: Getting QUIC Working with nginx in a Bastille Jail via 
@fanfTony Finch https://lobste.rs/s/kgatai #freebsd
https://blog.hofstede.it/http3-on-freebsd-getting-quic-working-with-nginx-in-a-bastille-jail/
Sometimes I need to find something.
Sometimes I fire up a search engine and search.
8 times out of 10 I end up on 
@joelJoel Carnat ♑ 🤪 's blog.
https://www.tumfatig.net/2024/running-web-browsers-in-freebsd-jail/
Seeking advice for FreeBSD as a daily driver on an ASUS X580VD
(Intel HD 630 + GTX 1050 Optimus)
Five questions at <https://www.reddit.com/r/freebsd/comments/1r9j67j/advice_for_running_freebsd_as_daily_driver_on_an/> (replies there, if you can – thanks).
The writer's use case and goals:
― web dev stack: Java, Node/React, Python, Go
― occasional virtualization and Linuxulator for Linux-only tooling
― prefer GNOME, but open to recommendations if another DE/DM is more reliable here
― Intel as primary + NVIDIA for on-demand/offload use (if possible).
The future of LPR and LPD in FreeBSD
<https://lists.freebsd.org/archives/freebsd-stable/2026-February/003857.html> | <https://mail-archive.freebsd.org/cgi/mid.cgi?86wm07xnre.fsf>
Related manual pages:
lp(1) <https://man.freebsd.org/cgi/man.cgi?query=lp&sektion=1&manpath=freebsd-current>
lpc(1) <https://man.freebsd.org/cgi/man.cgi?query=lpc&sektion=1&manpath=freebsd-current> does not exist, I guess it should be lpc(8) <https://man.freebsd.org/cgi/man.cgi?query=lpc&sektion=8&manpath=freebsd-current>
lpd(8) <https://man.freebsd.org/cgi/man.cgi?query=lpd&sektion=8&manpath=freebsd-current>
lpq(1) <https://man.freebsd.org/cgi/man.cgi?query=lpq&sektion=1&manpath=freebsd-current>
lpr(1) <https://man.freebsd.org/cgi/man.cgi?query=lpr&sektion=1&manpath=freebsd-current>
lprm(1) <https://man.freebsd.org/cgi/man.cgi?query=lprm&sektion=1&manpath=freebsd-current>
lptest(1) <https://man.freebsd.org/cgi/man.cgi?query=lptest&sektion=1&manpath=freebsd-current>
pac(8) <https://man.freebsd.org/cgi/man.cgi?query=pac&sektion=8&manpath=freebsd-current>
We’re excited to share that the FreeBSD Project has been accepted again as a mentoring organization for Google Summer of Code 2026.
This marks another year of supporting contributors who want to work on meaningful open source projects while learning from experienced FreeBSD developers.
Learn more about Google Summer of Code 2026:
https://summerofcode.withgoogle.com/programs/2026/organizations/the-freebsd-project
when do you usually use the man page for a complex command line tool to answer a question you have? (like git, openssl, rsync, curl, etc)
(edit: no need to say "i use --help then man")
@b0rkJulia Evans using #freebsd and having started on SCO Unix, I’m used to better than average man pages. And I learned sco before the web: so man and Usenet.
—help is my first stop these days.
Knowing how to use man means I can work offline too. So practicing that skill when a fallback is present is a worthy investment
The server doesn't boot natively.
It can boot in Linux rescue mode. So:
qemu-system-x86_64 -enable-kvm -m 65536 -smp 16 \
-bios /usr/share/ovmf/OVMF.fd \
-drive file=/dev/nvme0n1,format=raw,if=virtio \
-drive file=/dev/nvme1n1,format=raw,if=virtio \
-netdev user,id=net0,hostfwd=tcp::80-:80,hostfwd=tcp::443-:443 \
-device virtio-net-pci,netdev=net0 \
-vnc 127.0.0.1:0
A couple of lines modified in /etc/rc.conf and /etc/pf.conf
And the server is responding, while waiting for the KVM console.
The recording of the February 19th, 2026 #bhyve Production User Call is up:
We discussed LibVirt progress, a #FreeBSD CTLd regression, bhyve and iPXE, a Production User case study, EDK2 challenges and opportunities, bhyve ARM64, PXE boot, and more!
"Don't forget to slam those Like and Subscribe buttons."
You can support all Call For Testing efforts via BSD Fund: https://bsdfund.org
Fully functional installer for a usable Desktop config
https://github.com/alfonsosiciliano/kde-installer-dialogs/blob/main/cft.md
Exosphere:
― aggregated patch and security update reporting
― basic system status across multiple Unix-like hosts via SSH
<https://exosphere.readthedocs.io/> | <https://github.com/mrdaemon/exosphere>
<https://untrusted.website/@mr_daemon/114980024541462116> 
@mr_daemon
<https://mastodon.social/@terminaltrove/114977286773333343> 
@terminaltrove
#Unix #Linux #BSD #FreeBSD #OpenBSD #Debian #Ubuntu #RedHat #macOS #Windows #SSH
We built our entire startup infra on #FreeBSD in 2026. Now we need to talk.
Found #nvidia released new Production Branch of their #GPU #drivers 580.126.18.
For #FreeBSD: https://www.nvidia.com/en-us/drivers/details/264091/
For Linux: https://www.nvidia.com/en-us/drivers/details/264090/
Filed PR for FreeBSD #ports as Bug 293260 and opened corresponding review D55350 for this.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293260
https://reviews.freebsd.org/D55350
Reading Release Highlights, it seems to be Linux specific build fix and maybe FreeBSD version is just bumped to keep sync with Linux version.
Time Machine inside a FreeBSD jail // @stefanoStefano Marinelli
https://it-notes.dragas.net/2026/01/28/time-machine-freebsd-jail/
The GitHub Secure Open Source Fund helped #curl and others to beef up security https://github.blog/open-source/maintainers/securing-the-ai-software-supply-chain-security-results-across-67-open-source-projects/
I've read the article with keen interest. Keep up the great work on curl 
@bagderdaniel:// stenberg://
#curl #get #programming #technology #fetch #networking #https #http #ftp #OpenSource #POSIX #BSD #freeBSD #ghostBSD #openBSD #Linux #win64 #mac
🦋💙❤️💋#Lobi 💙💕🌹💐💙🦋
New 𝗡𝗮𝘁𝗶𝘃𝗲 𝗙𝗿𝗲𝗲𝗕𝗦𝗗 𝗞𝗲𝗿𝗯𝗲𝗿𝗼𝘀/𝗟𝗗𝗔𝗣 𝘄𝗶𝘁𝗵 𝗙𝗿𝗲𝗲𝗜𝗣𝗔/𝗜𝗗𝗠 article based on @LarvitzLarvitz work - credit goes to him.
https://vermaden.wordpress.com/2026/02/18/native-freebsd-kerberos-ldap-with-freeipa-idm/
These books are over 20 years old. Obviously much has changed since they were released but I still hang onto them since many of the concepts are still relevant.
On a side note: I'd probably find some masochist level of joy running these ancient OSes as daily drivers. 🤣
#linux #unix #freebsd #suse #solaris #vintage #sunos #ancienthistory #tech #books
NEW VIDEO - FreeBSD as a Domain Controller?! Microsoft Won’t Like This…
#Unix #FreeBSD #opensource #garyhtech
https://youtu.be/GrVDAu-Mcp0?si=X_z6mcUGuCKKFeUk via @YouTube
