TrueNAS build system will become closed source

I don't know what your requirements are, but I built me my NAS completely myself:
Old hardware, a couple of storage drives into it (a PCI card to provide more SATA slots) but you already have the hardware. Then just a FreeBSD-RELEASE default "vanilla" installation (No GUI). Configured NFS, and SSH access. Installed & configured only a few packages for my individual situation: vim, samba (to have anybody not using a BSD login to our LAN can have access to it), rsync, svn, wrote some small scripts for doing redundancy backups - voilá - worx.
When you're not a total noob on FreeBSD and sh scripting, it's no rocketscience, but a weekend's job.
Personally, I don't know what people need TrueNAS for at all.
 
Maturin said:
Old hardware, a couple of storage drives into it (a PCI card to provide more SATA slots) but you already have the hardware. Then just a FreeBSD-RELEASE default "vanilla" installation (No GUI). Configured NFS, and SSH access. Installed & configured only a few packages for my individual situation: vim, samba (to have anybody not using a BSD login to our LAN can have access to it), rsync, svn, wrote some small scripts for doing redundancy backups - voilá - worx.
Click to expand...

Ya - I did (similar) with PCI/SATA. THIS is why one installs FreeBSD because all the "parts" are there and/or the missing parts can easily be obtained and bolted on the O/S.

Agree - Not sure what the "value add" is for TrueNAS.
 
mer said:
Pretty web interface?
Click to expand...
Yeah, all right. I give you this. I also thought: "For commercial reasons - to sell turn keys NAS."
Apart from you can do it yourself - maybe not so nice looking without some effort - but what for?
All those shiny nice looking indication display things providing masses of information like e.g. conky to me are just useless toys, because many believe in those info may good to know, but in fact they are useless.
Your system either provides enough power/storage, or it does not. Having this shown constantly in several forms of floating point numbers, percentages, and trend graphs does neither provide more power/storage, nor are useful, when the utilization of your system is within single digit percentages anyway. :cool:
 
I don't know what "docker applications" implies exactly. It sounds like a linux distribution could be convenient as an alternative. As for FreeBSD, all can be done with it, except maybe docker apps, though there are jails for that purpose.
 
Many applications that are in docker containers have no real way of running on FreeBSD unless built from source. And many do not have docs for that. One example is Audiobookshelf.

Apps like Immich are fairly difficult to get working, though some people have done it. It just takes time.

Personally I use XigmaNAS for now (though I’m considering stock BSD) and it’s working fairly well for me. Bastille makes jail management incredibly easy.

I’ve also created a repo with some popular apps you can install at https://github.com/tschettervictor/bsd-apps
 
In FreeBSD you create a jail. In one jail you can run firefox in other jail a webserver in an other a database.
Which applications are you thinking of that need "docker" type features ? The freebsd way of working is you install a server and you edit yourself the config file.
 
"Functionally" a single executable running in a docker container is a "static executable, sandboxed". I think you can really limit a docker container interaction with host. maybe some hardware passthrus but mostly networking exposed.

So is that functionally different from a jail/bhyve? Not really. As sko says "lots of wishful thinking". Toss in the ever present docker vs kubernetes vs snapd vs everything else and what really matters.

bgavin cool. Sometimes a well designed UI/UX makes a product easier to use. Think all the threads on "CLI vs DE"
 
You could run an Ubuntu on Bhyve , and run Linux-Docker-Containers in it. And even have, video-card & usb passthrough.
But that looks more virtualization of Linux on FreeBSD.
It's not my knowledge but "downloadable linux-docker-files" don't exist for FreeBSD OS.
 
I saw this:

daemonless.io

daemonless

Run Docker-like containers natively on FreeBSD using Podman and ocijail. 30+ pre-built images for Radarr, Sonarr, Plex, Immich and more. No Linux VM required.
daemonless.io daemonless.io

Here (note that there TWO heres):

M

Post in thread 'Help me ! I'm going to make a mistake... migrate to GNU/Linux ...'

AlfredoLlaquet said:
But the question remains: have you or have you not migrated to that other OS?
Click to expand...

Of course not, I'm not going to migrate on a temporary whim after so many time with FreeBSD.

1772271465114.png


Especially after having something that works with https://daemonless.io/ I tested immich with several dozen gigabytes of photos, and it works perfectly, even with data in an NFS mount.

Of course, it's much less integrated than jails, that's obvious, and podman seems really bloated... but immich is really excellent (until now I was using Nextcloud/Memorize) and wow, what a difference. It's a...
  • Like

D

Post in thread 'Help me ! I'm going to make a mistake... migrate to GNU/Linux ...'

Quote from MetaOxy: "Of course, it's much less integrated than jails, that's obvious, and podman seems really bloated... but immich is really excellent... It's a real shame that it's so complicated to install in jail format with FreeBSD."
Click to expand...

Hey there! As the creator of daemonless.io, I’m thrilled to hear that the project helped you get Immich running!

I completely agree with your frustrations regarding Podman, but here is the wonderful thing about OCI images: you are not required to use Podman to run them. Because these images follow the open specifications defined by...
  • Thanks
  • Like
 
Not going to watch a youtube vid on "closed source build decision" but didn't they move to GPL3 a little bit ago after they switched to linux? But if I try to care a little bit: A closed build might/would/should put them in violation (they should have stayed BSD). That build may open up again.
 
Quote from CTO (30 second search) below. So, (s)he better speak to a company lawyer (or a better one) because I'm pretty sure a GPL3 requires a release of source AND build (but I aint no lawyer; they give me a hard enough time as it is).

I do love some of the irony here. Some of the same folks making hay about this change also didn’t understand when we moved from BSD → GPLv3 licensing on our source code. That was literally in the defense of keeping things open when it could have been closed at any moment :D
Click to expand...
 
Last quote, this time from the gpl3:
The “Corresponding Source” for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.
Click to expand...
 
Yeaah,
BSD 2-Clause License, often referred to as the "Simplified BSD License" or "FreeBSD License," is a permissive open-source license widely used in software development, including projects associated with Google. It permits almost unlimited freedom to use, modify, and distribute software—including for proprietary commercial purposes—provided that the copyright notice and disclaimers are retained
 
This was the rationale, apparently:

forums.truenas.com

Clearing the Air on Build Scripts

Hey everyone, I’ve seen the concerns in the Community about us moving the build scripts internal for TrueNAS 27, so I want to address this directly. Why we did it: We had a growing problem with bad actors forking TrueNAS, selling closed-source commercial derivatives under their own brands, and...
forums.truenas.com forums.truenas.com

(As with many of their previous public statements, it's probably worth taking it with a pinch of salt.)
 
You must log in or register to reply here.
Back
Top