See: https://blog.hofstede.it/joining-dn42-a-mikrotik-border-three-wireguard-peerings-and-a-freebsd-jail-in-the-hobbyist-internet/ ping: https://framapiaf.org/@Larvitz@burningboard.net/116460532141910458

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

I apparently found your original post on Mastodon first: https://mastodon.bsd.cafe/@nuintari/116453958107402129

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

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/

I have to say, i really like the glassy orb logo. i don't really think it needs changing. i think much the same WRT the website redesign. i like the skeumorphic layout. it reminds me of a time when the web was much more approachable without cleanup software like adblockers. i like the current freebsd website for the same reasons i like the OpenBSD website.

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

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

@naltun said: This is an excellent post. Thank you for the share! e: It'd be cool to have this as a manual page, all of the syscalls laid out in a table with code references. I'm keeping this in mind as an OpenBSD user. It wouldn't be too hard to generate one, but it could lead to confusion for people if they use random internet manpages because the syscall codes are not guaranteed to be stable across versions on OpenBSD and syscalls get added/removed/deprecated sometimes.

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.

Egual, the FreeBSD Foundation Journal for the Q1 2026: https://freebsdfoundation.org/our-work/journal/browser-based-edition/laptop-desktop/

For convenience, from the toot in Mastodon: https://www.reddit.com/r/freebsd/comments/1sgmi14/claude_mythos_preview_fully_autonomously_finds/ … (plus Linux, OpenBSD, and others) – more concerning than calif.io story with known CVE and human prompting? …＂ – @bigsneakyduck (Sorry. I imagined that the original mention in Mastodon would have shared the whole of the toot as the opening post here.)

The Foundation's announcement: https://freebsdfoundation.org/blog/call-for-testing-introducing-the-laptop-integration-testing-project/ Thanks to u/anh0516: https://www.reddit.com/r/freebsd/comments/1seej1t/call_for_testing_introducing_the_laptop/ https://www.reddit.com/r/linux/comments/1seei3y/freebsd_call_for_testing_introducing_the_laptop/ In The FreeBSD Forums, maybe not open to discussion: https://forums.freebsd.org/threads/102265/

@ahze said: this post is a plant LOL, when do @nibori and I get our cheques?

Thank you!

fix the code location for the doc tree … It doesn't need fixing, we might need to contact them. What works for the src tree (in the first screenshot below) does not work for the doc tree (second shot). [image: 1775276658791-261d9e5a-1b05-4950-9bfd-1e03904d139f-image.jpeg] [image: 1775276700827-ab9776c2-f7cb-4c58-81a7-e0df05aa9caa-image.jpeg] The previous repo URL was the cgit URL. Before I removed it, today, IIRC there was the same red alert: Error: This Code Location is flagged as Do Not Fetch. Please contact us for assistance – with the same status: Step 1 of 3: Downloading source code history (Failed about 2 years ago.) There's an on-screen suggestion to wait twenty-four hours. I will wait, although given the failure about two years ago: I doubt that it'll make a difference. [image: 1775280296655-67daeab0-2790-4c4f-84b3-ed5dd0bf4460-image.jpeg] There's a suggestion of "special handling" in the help forum. There's also no response to a report that someone made more than five months ago, which is not particularly special

@hypostase The final version of the fix is now accepted and landed onto both main (aka latest) and 2026Q2. https://cgit.freebsd.org/ports/commit/?id=a92d927574fca313453ae266f4e78517eb406a33 https://cgit.freebsd.org/ports/commit/?h=2026Q2&id=1c9a29edad562f0650166239fba46dd8b2cc1fdd