TrueNAS build system going closed source
from Ek-Hou-Van-Braai@piefed.social to selfhosted@lemmy.world on 09 Mar 23:47
https://piefed.social/c/selfhosted/p/1860178/truenas-build-system-going-closed-source
from Ek-Hou-Van-Braai@piefed.social to selfhosted@lemmy.world on 09 Mar 23:47
https://piefed.social/c/selfhosted/p/1860178/truenas-build-system-going-closed-source
Readme updated today:
This repository is no longer actively maintained.
The TrueNAS build system previously hosted here has been moved to an internal infrastructure. This transition was necessary to meet new security requirements, including support for Secure Boot and related platform integrity features that require tighter control over the build and signing pipeline.
No further updates, pull requests, or issues will be accepted. Existing content is preserved here for historical reference only.
https://github.com/truenas/scale-build
Wondering if this is just the first step towards doing a minio in the future.
threaded - newest
Always blaming security bullshit. I anxiously await a community fork.
Next step is requiring a subscription.
Volker Theile (lead dev of FreeNAS 2006-2009) maintaines OpenMediaVault, based on debian, version 8 was released recently. Not a drop in replacement, and it has its own quirks, but no evil company in the background
I’m running an early version of that on a 16 year old ARM board NAS, the NAS has 256MB of RAM and OpenMediaVault runs great on it.
I love it so much that I donaged twice to the project. There are also some easter-eggs hidden in the software, like quotes from Dune.
Security through obscurity isn’t security.
There goes my excuse for not giving up and just paying for Unraid.
Unraid pay system switch made me never want to use them
you can always just bypass their security.
Huh
Unraid uses a pretty whacky "license" checking system. There's cracks for it out there that hook into the core license system and use it to generate a valid one for the current version.
One key note is that you HAVE to update the crack before updating Unraid itself.
Odd choice of timing… I wonder if they are sitting on a cache of hard drives.
Truenas went to shit when they killed BSD support, the OS it was founded on
TIL. Now it’s based on Debian.
I ordered a TrueNAS system from iXsystems a few years ago, and the reasoning they gave me is that Linux has better driver support, especially for home users.
Whether that was actually the reason, I have no clue. But that’s what they said.
The reason they gave me is people can run apps with docker on Linux, and docker isn’t compatible with FreeBSD jails…
And yet they went with K3s at first, a crappy implementation at that, and refused to even consider adding Docker for like a year, then suddenly it became super important to replace their k3s stack with docker in the next release, barely giving people 2-3 months to get all their apps updated.
Not only that but there wasn’t even a notification on the dashboard for me after updating the OS that k3s were being replaced, I found out after updating when my apps wouldn’t work. When did I update? About 2 weeks after the migration deadline. Had to rebuild my Plex, Jellyfin and Immich apps.
Don’t get me wrong, I don’t like notifications from the OS developer in my system, but that would’ve been a great heads up and a worthy exception. “Hey migrate your apps now or your shit will break” would’ve worked.
They are very hostile to users and I moved to a pure FreeBSD self managed storage and deployment solution
TrueNAS doesn’t add anything to ZFS or what the OS can do. There’s a couple graphs and reporting features but the rest just adds more work
K3S sorta makes sense in an enterprise environment but for the small one box use case it’s overkill and a pain to work with for little extra gain.
Postgres is used by highly secure environments and has a public build pipeline.
This is bullshit and/or they are lazy.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
5 acronyms in this thread; the most compressed thread commented on today has 15 acronyms.
[Thread #153 for this comm, first seen 10th Mar 2026, 00:40] [FAQ] [Full list] [Contact] [Source code]
Are they lying about secure boot being a reason or can I go back to thinking SB is part of Microsoft’s EEE attack on software freedom?
It can be a bit of both.
I don’t think secureboot is an attack on freedom exactly (and it’s certainly not an instance of EEE), but I definitely think it shouldn’t be Microsoft holding the keys.
Literally today Chris Titus released a video where he emphasized that no one should be using secure boot because the default backend is Microsoft and no one changes their secure boot config.
If that’s true there’s an argument that the name “secure boot” is hardly detachable from the defaults and thus that name is kid of burnt and shouldn’t be recommended out of an abundance of caution for new users.
@tabular @Ek-Hou-Van-Braai They are lying. Debian supports Secure Boot and remains open.
Although "related platform integrity" stuff might be something they're being forced to include by a government agency or paid to include by another company.
XigmaNAS is still being developed and is a fork of the original FreeNAS code before iX acquired the name.
There are alternatives