Tux Machines

BSD Leftovers

Posted by Roy Schestowitz on Sep 13, 2023

=> today's leftovers | Slowroll: openSUSE’s New Take on the Rolling Release Model (UPDATED)

Which BSD did you start on?

=> ↺ Which BSD did you start on?

This post is dedicated to Benedict Reuschling, who encouraged me to write about this again! Danke :).

I saw this question floating around the socials recently, and it got me thinking where I started. It was tricker to answer than I thought, though I was able to trawl through the archives to find some info.

My first BSD was Red Hat Linux. You read that right: practically every Linux distribution has BSD-licenced code, and they depend on tooling like OpenSSH from the OpenBSD project for secured administration. I like to point out examples like this whenever a GPL advocate claims their licences are necessary to ensure freedom. Pity that importing into a GPL’d project is a one-way transaction.

p2k23 Hackathon Report: Landry Breuil (landry@) on chasing memory corruptions

=> ↺ p2k23 Hackathon Report: Landry Breuil (landry@) on chasing memory corruptions

Next up in the series of p2k23 hackathon reports is this from Landry Breuil (landry@), who writes, [...]

Unlocking Infrastructure Sovereignty: Harnessing the Power of Open Source Solutions for Business Flexibility and Cost-Effectiveness

=> ↺ Unlocking Infrastructure Sovereignty: Harnessing the Power of Open Source Solutions for Business Flexibility and Cost-Effectiveness

[...]

Software as a Service (SaaS) and recurring revenue models have become prevalent, often leading to vendor lock-in. This constrains businesses from seamlessly transitioning to alternative solutions, trapping them and keeping them reliant on their vendors. Regaining (or simply maintaining) infrastructure sovereignty protects freedom of choice, which in turn eliminates the restrictions of vendor lock-in.

=> gemini.tuxmachines.org