Unix Digest

Because those type of people are actually some type of narcissist powerpoint bots. Only interested in their "journey" and putting that next to a picture (of herself probably) climbing a mountain. Here is what should worry everybody who care about FreeBSD and the "foundation", it seems it is being run into the ground [0] > The board has said the deficit spending is intentional. They are drawing on reserves to invest more in the project, which makes sense in principle. > But at roughly the 2024 burn rate, the reserve fund might last about 4 to 5 years. > One thing that caught my attention is that the EU Cyber Resilience Act starts in September 2026, and the Foundation already has six workstreams running to prepare for it. That kind of work costs money, and right now a lot of it seems to be funded from the same reserves that are shrinking. This is also why you are hearing thing like FreeBSD "is investing in laptop support" or a KDE installer. But this is not what is gonna "save" FreeBSD. People get interested and choose FreeBSD because it a great server OS, because of the ZFS support, jails, PF, stability and the coherent system overall. They would do more for adoption by just making sure most VPS hosting services have it as an option along Linux than wasting infinite money on supporting "laptops". See also [1], people are getting tired of that level of hypocrisy and waste of money. - [0]…

Those that love it will fight for it. Those that hate it will simply avoid using it. There may be some commercial incentives for IBM/Redhat to push for it. Either way it will always be divisive. Some sysadmins will begrudgingly support it at work and some absolutely love to support it. I have supported it in the enterprise and I use it on gaming machines at home. (CachyOS / Bazzite). My daily drivers, servers both physical and VM will always be without it. (MX Linux / Void Linux / Alpine Linux). I only use mini-PC's these days and all the games I play work great on CachyOS. All the other daily stuff works great on MX/Void and of course running firewalls, NAS and servers on Alpine is about as simple as it gets. - Some discussion on the matter [1a][1b][1c]. - Operating systems without systemd [2] [1a] - https://unixdigest.com/articles/the-real-motivation-behind-systemd.htm… [1b] - https://nosystemd.org/ [1c] - https://without-systemd.org/wiki/index_php/Arguments_against_systemd/ [2] - https://without-systemd.org/wiki/index_php/Main_Page/

The main differences between OpenBSD, FreeBSD, NetBSD and DragonFly BSD https://unixdigest.com/articles/the-main-differences-between-openbsd-f…

It's weird to me that this is "suddenly" an issue. It has been known for decades that Red Hat Inc's largest customer is the U.S. Army[1]. It's a very large part of the reason why Red Hat took over development of SELinux and made it on by default in their distros. And the Army isn't exactly known for handing out cupcakes... [1] https://unixdigest.com/includes/files/Army-RedHat-Whitepaper-February-… [1] "Red Hat’s partnership with the U.S. Army spans 10 years starting with the deployment of Red Hat Enterprise Linux in 2002 and, to this day, the U.S. Army remains one of Red Hat’s largest customers by volume."

And much much more: https://unixdigest.com/articles/choose-your-browser-carefully.html#twe… Keep in mind that this isn't for everyone.

Some nice write up on this topic, although not the resolution of all discussion. But rather hints and guesses to keep it alive :) https://unixdigest.com/articles/battle-testing-php-fopen-sqlite-postgr… Has been on HN lately..

AFAIK NetFLix is a rare company that actively makes substantial contributions to open software, i.e. FreeBSD in their case. There are lots of Linux distros and thus you will never get the cohesion that you get with any of the BSDs. For a more detailed explanation: https://unixdigest.com/articles/why-you-should-migrate-everything-from…

Even the much-maligned raid5/6 is basically fine†. If you're concerned about the write hole, use -m DUP/raid1/raid1c2 instead of -m raid5. Plus raid-stripe-tree†† is coming - didn't check the status of it recently. Many horror stories are because, while btrfs is fine, the operational model and tooling have some footguns which can cause either straight up data loss (due to operator error, but arguably that's really due to bad UX) or possible-but-hard-to-get-out-of situations. I use btrfs because using zfs has been painful for me, for two reasons: - btrfs can "shapeshift": I progressively moved _live_ from 2hdd raid1 to 5hdd raid5 data + raid1c2 meta with varying experiments in between. Probably five or six rebalance to change its shape over the years. - the zfs module situation: when I tried it, the module silently failed to build properly and this resulted in a broken system til I fixed it; this happened twice over six months. Luckily I anticipated this failure mode and only the data array (not the root fs) was zfs, so I could still boot and login into a full system to fix. Compared to zfs, btrfs is slow to scrub and rebalance though. † https://unixdigest.com/articles/battle-testing-zfs-btrfs-and-mdadm-dm.… †† https://lore.kernel.org/linux-btrfs/cover.1698679287.git.dsterba@suse.…