@onepict
Yep. It was only recently I properly understood why I was always reluctant to contribute to a permissive #FOSS project. I knew it was bad, but Redis have given the example I needed to explain it in one word.
All my own projects are GPL and I will never contribute to anything like #MIT, #Apache or #BSD licensed code. If I need a project I'll just fork and switch it to GPL. #Licensing
🐡 OpenBSD 7.5 Released - Faster Performance For Many-Core ARM Servers | Phoronix
「 Theo de Raadt has released OpenBSD 7.5 as the newest version of this security-focused BSD operating system. With OpenBSD 7.5 there is a number of improvements for ARM (AArch64) hardware, never-ending kernel optimizations and other tuning work, countless package updates, and other adjustments to this popular BSD platform 」
Cette histoire m'amuse beaucoup étant donné que l'essentiel de mon ordi est sauvegardé ailleurs et que je réinstalle un système d'exploitation en 15 minutes.
J'ai oublié de paniquer 😊
Je vais tout de même passer sous Bsd un de ces jours.
We don’t need Youtube for that:
Kali and Alpine :) The latter because small is beautiful, the former for it’s Debian hertsge and rolling release.
NetBSD is not Linux, but it’s also up there. #linux#bsd
「 Vector Packet Processing (VPP) is an open-source, high-performance user space networking stack that provides fast packet processing suitable for software-defined networking and network function virtualization applications. VPP aims to optimize packet processing through vectorized operations and parallelism, making it well-suited for high-speed networking applications 」
When I used to write for @osnews in the early 2000s, I was a proponent of the BSD-like licenses, where a user could decide not to open source back their changes. I still believe in that freedom, but I don't believe in all people anymore: corporations now have reached total #enshittification, so now I'm a believer of the AGPL, the most extreme version of the GPL3. Everything should be as open as possible, and remain so. No exceptions.
Sharing some technical details about how I'm setting up the hosted email service. It will not be a service of BSD Cafe but tied to my own business. It will run entirely on BSD systems and on bare metal, NOT on "cloud" VPS. It will use FreeBSD jails or OpenBSD or NetBSD VMs (but on bhyve, on a leased server - I do not want user data to be stored on disks managed by others). The services (opensmtpd and rspamd, dovecot, redis, mysql, etc.) will run on separate jails/VMs, so compromising one service will NOT put the others at risk. Emails will be stored on encrypted ZFS datasets - so all emails are encrypted at rest - and only dovecot will have access to the mail datasets. I'm also considering the possibility of encrypting individual emails with the user's login password - but I still have to thoroughly test this. The setup will be fully redundant (double mx for SMTP, a domain for external IMAP access that will be managed through smart DNS - which will distribute the connections on the DNS side and, in case of a server down, will stop resolving its IP, sending all the connections to the other. Obviously, everything will be accessible in both ipv4 and ipv6 and in two different European countries, on two different providers. Synchronization will occur through dovecot's native sync (extremely stable and tested). All technical choices will be clearly explained - the goal of this service is to provide maximum transparency to users on how things will be handled.
just me, I suspect the venn of #fountainpens and #linux is almost one circle, as both are things that while they are excellent for niche uses, they totally way to complex and fiddly for most users.
Fountain pens, unix (Linux, BSD, UNIX®) platforms, manual transmissions, safety and straight razors, and audio and video components are examples of tools which are chosen by and can be properly adapted to their owners' preferences.
While you are quite right that a steeper learning curve dissuades some potential users, the tyranny of the default seems to be the greatest influence, backed up by the threat of choice overload.
A massive thank-you from Linux Professional Institute (LPI) to all our global community members, passionate volunteers, and #opensource pros who have given their support. Because of you, this year we’re turning 25!
We’re excited to share offers and activities with you to celebrate. Keep an eye on #LPI socials for more details. 🐧🌍🥳🎂
This means that I won't attend, speak at, or promote conferences that do not have a robust #PublicHealthPolicy .
It's a hard line for me. Because if you cannot enforce public health measures, I have absolutely no faith that you will enforce your Codes of Conduct, to protect folks from harassment.
If you consider yourself an inclusive conference with a diverse community and you don't have a public health policy. You aren't as inclusive as you think you are.
@josh#BSDCan has maintained their strong policy, which is great. There have been other #BSD conferences with a strong #HealthPolicy, but has been patchy & organising teams have dropped the ball in subsequent years, like EuroBSDConf. Some leadership was needed, instead of leaving it to local organisers.
Likewise, #LinuxAustralia could have stepped in & set the tone for their events, but failed to.
#Python is the only large community I've noticed taking a consistently correct approach to this.
Wow, that was fast. People may remember my idea behind #BoxyBSD? Temporary jails for testing and debugging? It got immediately abused for spamming etc.!
Now, I’m running a friendly beta test within the #BSD Community (primary #BSDCafe & BSD fans) for free small sized hosted #VMs / #Jails (IPv6 only).
The first system is already full. Let’s see how this will be (ab)used?! Maybe, the next stack will start after Easter.
Puh, I haven’t used any #Linux for personal use since 2008 anymore and have just set up my firsts Linux based server after years. It’s the first time I’m cheating on #BSD (#FreeBSD)) after more than 15 years. That feels somehow crazy…