BSD Cafe Billboard

FreeBSD: After the First Boot https://www.dwarmstrong.org/freebsd-after-install/ ping: https://framapiaf.org/@dwarmstrong@fosstodon.org/116530466697991937

Spun off from (Linux) Fedora Verified: Help Shape a New Way to Recognize Fedora Contributors | BSD Cafe Billboard FreeBSD Project https://framapiaf.org/@tubsta@bsdlab.au/116478621827645455 – redirects to https://social.bsdlab.au/notice/B5jMI1FY3WtTTWqvNA: Something the #FreeBSD core team could consider. This is something that has probably been needed for a while @dch@bsd.network My initial thoughts: it's an awful lot to think about for a project, or team (Core, for example), that already has, I think, too much to think about. Fedora Project From the Proposal: Unanswered Questions for the Fedora Community While we have a framework, there are several major questions we need the community to answer before we move forward. Specifically, we want to know: Validation: Should applicants be approved by grassroots peer vouches, or an elected committee? Fairness: Does this model truly value non-code contributions equally? Progression: How strictly structured should the path to becoming “Verified” be? Maintenance: Should the status expire after 12 months of inactivity? Of those four questions, the first two are huge. https://mastodon.social/@mxenbionix/116478348932821730: … I do have to echo some of the concerns people seem to be raising about being unclear to what this is actually solving. … Also, the commentary at and under https://discussion.fedoraproject.org/t/188603/3.

RE: https://mastodon.social/@allaboutsecurity/116516280099667572CHERI memory safety mitigates LLM-discovered vulnerability in FreeBSD – CHERI Alliance<https://cheri-alliance.org/cheri-memory-safety-mitigates-llm-discovered-vulnerability-in-freebsd/>＂… CHERI trivially blocks this attack and likely many others. As LLM-driven discovery accelerates, the case for memory safety by design becomes stronger.＂@freebsd #FreeBSD @FreeBSDFoundation

Why the Best Systems Are the Ones You Don't Notice FreeBSD, from philosophy to practice. https://vivianvoss.net/print/integrated-by-design From Integrated by Design — Launch Day (23rd April): … Five months of writing. Three weeks of final proofs. Then the last 72 hours, dedicated entirely to problems one does not anticipate. In the interest of transparency, and in the hope that it spares somebody else a week of the same, here are the four of them. … https://news.ycombinator.com/item?id=47928554 – please note the author's comments. Vivian Voss — System Architect & Software Developer https://www.linkedin.com/in/vvoss/ Also in Reddit: https://redd.it/1t1u1os

Setting up a WireGuard Tunnel on FreeBSD 15 https://ianwwagner.com//setting-up-a-wireguard-tunnel-on-freebsd-15.html Overview of my New Homelab Setup https://ianwwagner.com//overview-of-my-new-homelab-setup.html A TLS Terminating Reverse Proxy with OpenBSD https://ianwwagner.com//a-tls-terminating-reverse-proxy-with-openbsd.html ping: https://framapiaf.org/@ianthetechie@fosstodon.org/116499327407801906

See: https://www.phoronix.com/news/Servo-Embed-Crates-LTS https://www.phoronix.com/news/Servo-On-FreeBSD ping: https://framapiaf.org/@jbz@indieweb.social/116498971896054525

No response to https://forums.theregister.com/forum/all/2026/04/22/anthropic_mythos_hype_nothingburger/#c_5266893 after five days (and no correction to the article); that's disappointing. I'll respectfully request a correction. I refrained from sending an email, because @bigsneakyduck had already done so (mentioned in Reddit: "… I've tried reducing this to the bare minimum and sent an email to corrections at theregister dot com.").

The FreeBSD User Groups page has got quite outdated so crowdsourcing some replies has helped update a few things. Mostly group closures unfortunately but also some changes of contact details. For people who don't have a Reddit user account, I also started a FreeBSD Forums thread that found a few more updates, including a change to a long-standing venue. So feel free to reply there too: forums.freebsd.org/threads/102512/ I don't check for replies quite so regularly here - but if you don't have a FreeBSD Forums or Reddit account then leave a reply here and I'll get back to you at some point.

See: Part 1: https://bev.is/posts/2026-04-17-freebsd-on-hetzner-cloud/ Part 2: https://bev.is/posts/2026-04-22-freebsd-on-hetzner-2-cloud-init-boogaloo/ ping: https://framapiaf.org/@gront@mastodon.social/116450160136477517

See: https://blog.feld.me/posts/2026/02/using-new-bridges-freebsd-15/ ping: https://framapiaf.org/@ricardo@bsd.cafe/116453396670728593

Thank you! I blocked five of the respondents in the Fediverse https://mastodon.bsd.cafe/@grahamperrin/116462528458368843 ＂Power is the ability to do good things for others.＂ … https://mstdn.social/@happinessbot/116461840153065036 Think of the last person you interacted with. How happy do you think you are relative to them? (I ask this question every day to gauge how happy the Fediverse is.) #happiness #poll #mentalhealth #psychology

One of my biggest "frustrations" when migrating from OpenBSD to FreeBSD as my daily driver, was the loss of of working media keys on my Das Keyboard - especially the very convenient volume jog wheel. After some poking around i confirmed that the usbhid driver was working - and also default enabled in FreeBSD15 kernel. Xev tool printed the correct keycode events keycode 122 = XF86AudioLowerVolume keycode 123 = XF86AudioRaiseVolume keycode 172 = XF86AudioPlay The problem narrowed down to how to map these event to something useful I found a working solution in this discussion thread, by using the x11/sxhkd daemon to pass the events to mixer(8) https://forums.freebsd.org/threads/howto-enabling-multimedia-keys-gamepads-joysticks-for-desktop-usbhid.84464/ I had to tweak the sxhkd config a bit to work properly with mixer ~/.config/sxhkd/sxhkdrc XF86Audio{Play,LowerVolume,RaiseVolume} mixer {vol.mute="toggle",vol="-3%", vol="+3%"} Then I invoke the sxhkd daemon from my ~/.xsession file sxhkd & exec /usr/local/bin/fvwm3 Viola! #FreeBSD #Solved #X11 #FVWM3 #Xorg #AskFedi

Part1: Running Your Own AS: BGP on FreeBSD with FRR, GRE Tunnels, and Policy Routing: https://blog.hofstede.it/running-your-own-as-bgp-on-freebsd-with-frr-gre-tunnels-and-policy-routing/ Part2: Running Your Own AS: Going Multi-Homed with iBGP and three Transits: https://blog.hofstede.it/running-your-own-as-going-multi-homed-with-ibgp-and-three-transits/ Part3: Running Your Own AS: Joining an IXP with a Third Edge Router: https://blog.hofstede.it/running-your-own-as-joining-an-ixp-with-a-third-edge-router/ Part4: Running Your Own AS: Direct Hetzner Peering, a Fourth Edge, and Bringing the Home LAN into the Fabric: https://blog.hofstede.it/running-your-own-as-direct-hetzner-peering-a-fourth-edge-and-bringing-the-home-lan-into-the-fabric/

@rl_dane @raster @darth I really like #NomadBSD, but I think it's dead. No releases in 2025 and 2026.

See: https://interfacecraft.online/blog/2026/desktop-phone-connected-to-freebsd-server/

@philvuchetich , you bring up a good point and a problem we have solved at other conferences. For OpenZFS Portland 2025 myself, @dexter and additional AV volunteers put together a very smooth solution and had very happy Europeans and an Aussie fully participating to the point that it felt like they were in the room with us. We had break out sessions led by an offsite person and it was all very effective. It also takes lots of management,setup time, hardware, and effort however. While I am not at all opposed to the idea of streaming the tutorial(s), we would Need to have a full (er)AV team onsite days earlier than we have already have planned and purchased tickets for and we would certainly need additional hardware. Especially since we are supporting 2 Dev Summits @bsdcan this year: @FreeBSDFoundation and @netbsd @oxyhyxo @pitrh #runbsd #netbsd #freebsd

See: https://blog.hofstede.it/automating-freebsd-jails-with-cdist-zero-dependencies-inside-the-jail/

https://www.daemonology.net/blog/2026-04-11-20-years-on-AWS-and-never-not-my-job.html I created my first AWS account at 10:31 PM on April 10th, 2006. I had seen the announcement of Amazon S3 and had been thinking vaguely about the problem of secure backups — even though I didn't start Tarsnap until several months later — and the idea of an online storage service appealed to me. The fact that it was a web service made it even more appealing; I had been building web services since 1998, … – 24–30 minutes reading time, according to Firefox. Time well spent, IMHO, especially with security vulnerabilities for various operating systems recently in a spotlight. Also: to Mastodon @cperciva@mastodon.social @stefano and to Lobsters. Background: Colin Percival was, for many years, the FreeBSD Security Officer. He is now the FreeBSD Release Engineering Lead. You can show your appreciation for today's blog post at his shares in Reddit, in Hacker News, or in LinkedIn. A thought: AWS has its heroes. Tarsnap has given 2^18 dollars to open source – for this, and for what's described in today's blog post, it's probably fair to describe Colin as a hero in more ways than one.