Always blaming security bullshit. I anxiously await a community fork.
Next step is requiring a subscription.
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.
Looks like no zfs support?
It's not in there by default, you have to install the omv extras plugin, from there you can install zfs: https://wiki.omv-extras.org/doku.php?id=omv8%3Aomv8_plugins%3Azfs
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.
ZFS is in the omv extras repo: https://wiki.omv-extras.org/doku.php?id=omv8%3Aomv8_plugins%3Azfs
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.
Ahhh that is good to know. Thank you.
I found a post on the forum:
https://forums.truenas.com/t/scale-build-git-repo-going-closed-source/64313
This is only their old build system which they weren't using themselves, the rest of the OS will remain open source. However they also said some worrying stuff about including "proprietary pieces of the OS".
XigmaNAS is still being developed and is a fork of the original FreeNAS code before iX acquired the name.
There are alternatives
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.
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.
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
So glad I went with OpenMediaVault so many years ago
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)
Odd choice of timing… I wonder if they are sitting on a cache of hard drives.
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?
@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.
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.
Damn man. Technology kinda fucking sucks now. Everything I use is imploding in on itself. Yay!
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
Why are they always coming up with some kind of bullshit excuse? :D
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 10 acronyms.
[Thread #153 for this comm, first seen 10th Mar 2026, 00:40] [FAQ] [Full list] [Contact] [Source code]
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!