TrueNAS build system going closed source
from Ek-Hou-Van-Braai@piefed.social to selfhosted@lemmy.world on 09 Mar 16: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.

github.com/truenas/scale-build

Wondering if this is just the first step towards doing a minio in the future.

#open source #selfhosted #truenas

threaded - newest

yaroto98@lemmy.world on 09 Mar 17:03 next collapse

Always blaming security bullshit. I anxiously await a community fork.

Next step is requiring a subscription.

infeeeee@lemmy.zip on 09 Mar 17:18 collapse

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

BCsven@lemmy.ca on 09 Mar 18:06 next collapse

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.

skoell13@feddit.org on 10 Mar 00:44 next collapse

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.

quick_snail@feddit.nl on 10 Mar 06:18 collapse

Looks like no zfs support?

timbuck2themoon@sh.itjust.works on 10 Mar 06:45 next collapse

I question why this gets recommended so much when we discuss truenas.

Without a doubt zfs is one of if not THE reason to go truenas. It does so much more for you than other filesystems.

I guess OMV at least has btrfs but not the same thing.

infeeeee@lemmy.zip on 10 Mar 08:42 collapse

ZFS is in the omv extras repo: wiki.omv-extras.org/doku.php?id=omv8%3Aomv8_plugi…

As it’s just plain debian under the hood you can use any basic debian stuff, e.g. I use zfs-auto-snapshot from apt, and the zfs plugin can list and manage the snapshots perfectly.

timbuck2themoon@sh.itjust.works on 10 Mar 17:30 collapse

Ahhh that is good to know. Thank you.

Damage@feddit.it on 10 Mar 07:39 next collapse

I have it on my installation, you’ve got to replace the kernel with the proxmox one, it’s fairly easily done by installing a plugin

infeeeee@lemmy.zip on 10 Mar 08:32 collapse

Since omv 7 it works with the default kernel, you can install the proxmox one though if you want that.

Damage@feddit.it on 10 Mar 09:07 collapse

Weird, some time ago it booted with the default kernel by mistake and it couldn’t see my zfs pool

infeeeee@lemmy.zip on 10 Mar 13:47 collapse

From the docs:

The Standard Debian Kernel (selectable) can be used for ZFS. However, since ZFS kernel modules are not installed in the Debian kernel by default, they must be built by the ZFS plugin when it is installed. While this process works, building the modules is a long process that requires continuous access to online repos. Accordingly, the potential for a build error exists. For this reason, while the Standard Kernel is very usable for ZFS, it is not ideal.

infeeeee@lemmy.zip on 10 Mar 08:35 collapse

It’s not in there by default, you have to install the omv extras plugin, from there you can install zfs: wiki.omv-extras.org/doku.php?id=omv8%3Aomv8_plugi…

SnotFlickerman@lemmy.blahaj.zone on 09 Mar 17:07 next collapse

Security through obscurity isn’t security.

There goes my excuse for not giving up and just paying for Unraid.

ComradeMiao@lemmy.world on 09 Mar 18:22 next collapse

Unraid pay system switch made me never want to use them

fonix232@fedia.io on 09 Mar 20:36 collapse

you can always just bypass their security.

ComradeMiao@lemmy.world on 09 Mar 21:02 collapse

Huh

fonix232@fedia.io on 10 Mar 03:14 collapse

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.

Appoxo@lemmy.dbzer0.com on 10 Mar 05:17 collapse

And Unraid is OSS?
So my option are (potentially both) closed source storage software bjt one needs to be paid?

Well…I know what I’ll not choose.

DataCrime@lemmy.dbzer0.com on 09 Mar 17:16 next collapse

Odd choice of timing… I wonder if they are sitting on a cache of hard drives.

ryannathans@aussie.zone on 09 Mar 17:18 next collapse

Truenas went to shit when they killed BSD support, the OS it was founded on

lnxtx@sopuli.xyz on 09 Mar 18:24 next collapse

TIL. Now it’s based on Debian.

Technoguyfication@sh.itjust.works on 09 Mar 19:07 collapse

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.

ryannathans@aussie.zone on 09 Mar 19:44 collapse

The reason they gave me is people can run apps with docker on Linux, and docker isn’t compatible with FreeBSD jails…

fonix232@fedia.io on 09 Mar 20:35 collapse

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.

BigDaddySlim@lemmy.world on 09 Mar 21:19 next collapse

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.

ryannathans@aussie.zone on 09 Mar 23:17 collapse

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

tempest@lemmy.ca on 09 Mar 22:06 collapse

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.

[deleted] on 09 Mar 17:22 next collapse

.

Decronym@lemmy.decronym.xyz on 09 Mar 17:40 next collapse

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

Fewer Letters More Letters
Git Popular version control system, primarily for code
LTT Linus Tech Tips YouTube channel
NAS Network-Attached Storage
PIA Private Internet Access brand of VPN
VPN Virtual Private Network
ZFS Solaris/Linux filesystem focusing on data integrity

6 acronyms in this thread; the most compressed thread commented on today has 14 acronyms.

[Thread #153 for this comm, first seen 10th Mar 2026, 00:40] [FAQ] [Full list] [Contact] [Source code]

quick_snail@feddit.nl on 10 Mar 06:13 collapse

Good bot

tabular@lemmy.world on 09 Mar 17:45 next collapse

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?

frongt@lemmy.zip on 09 Mar 18:12 next collapse

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.

hoshikarakitaridia@lemmy.world on 09 Mar 19:26 collapse

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.

Saerana@lemmy.blahaj.zone on 10 Mar 07:34 next collapse

Do you know the name of this video? I keep trying to search for a secure boot video by Chris Titus released today/yesterday but I’m not finding anything.

d3lta19@lemmy.ca on 10 Mar 08:42 collapse

It was in his reaction video to LTT trying it Linux again

hoshikarakitaridia@lemmy.world on 10 Mar 19:13 collapse

yeah that’s the one

deafboy@lemmy.world on 10 Mar 08:08 collapse

So… nobody changes the default settings, therefore everyone should change the default settings… to the wrong option?

edit: Why is it that homo sapiens is always willing to go an extra mile just to hurt itself?

Andres4NY@social.ridetrans.it on 09 Mar 18:15 collapse

@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.

nixx@piefed.ca on 09 Mar 18:45 next collapse

XigmaNAS is still being developed and is a fork of the original FreeNAS code before iX acquired the name.

There are alternatives

quick_snail@feddit.nl on 10 Mar 06:09 next collapse

Link to article?

vodka@feddit.org on 10 Mar 09:21 collapse

There’s a link to the github page that has the depreciation notice right there…?

Damage@feddit.it on 10 Mar 07:41 next collapse

So glad I went with OpenMediaVault so many years ago

deafboy@lemmy.world on 10 Mar 08:01 next collapse

Why are they always coming up with some kind of bullshit excuse? :D

goferking0@lemmy.sdf.org on 10 Mar 08:34 next collapse

Oh so they are going to use the Puppet excuse to move away from open source?

we must move to have our code internal only for now. Totally just for security reasons nothing to do with us also changing licensing to make it harder for those building things for us

no don’t bring up the security incident we’re referring to that shows us as the issue not having code visible! (ie they cheaped out on people/set up and vendor had keys visible)

magic_smoke@lemmy.blahaj.zone on 10 Mar 08:43 next collapse

Been running my own storage boxes off of rocky w/ zfs, samba and nfs for years simply for the ease of integration of samba + freeipa.

Especially being able to use ipasam.so to allow password authentication for shares on machines that aren’t easy/reasonable to use kerberos keytabs from (think android clients, and off domain boxes)

Plus last time I tried truenas you couldn’t use a keyfile to encrypt drives unless it was stored on the root dataset which for some reason couldn’t be encrypted. Meaning each array had to have its own password instead.

I won’t lie I had to write several wiki articles to document this lol.

LucidNightmare@anarchist.nexus on 10 Mar 10:17 next collapse

Damn man. Technology kinda fucking sucks now. Everything I use is imploding in on itself. Yay!

Analog@lemmy.ml on 10 Mar 22:45 collapse

Not Proxmox! Use it for free at home, but buy it for your business if you can! (But they never force you to)

/hoping it doesn’t bite the dust too

[deleted] on 18 Mar 11:42 collapse

.

njordomir@lemmy.world on 10 Mar 10:51 collapse

Uggh, I just got to the point where I’m as familiar with TrueNAS as my old Synology, but I want to move towards more freedom. TrueNAS beats Synology, but where is this going?