I have some SSDs that require driver that does not include in the TrueNAS img. Currently, to enable the ability to install any apt require to install the dev tool kit. However, this action cannot be undone.
If there is a way to tempurary allow apt/deb installation, then turn the setting off after would be great.
If you read the 2nd sentence, I already stated that out. The developer mode cannot be completely reverted, which is the issue.
The feature request is for a mode that sits between the full dev mode and full locked production mode that only allows apt for driver installation purposes.
@Dango
While I, and others understand why this would be nice, the fact that TrueNAS is considered an Appliance, and not an OS, it a key factor. And to be honest, as a company, I would not want to take on that burden of troubleshooting drivers that cause all kinds of problems. You have to see it from their perspective.
For argument sake, say they allow this to happen. Oh the nightmare of upgrading TrueNAS! Right now Developer Mode changes are lost, of course. How many complaints will there be from users who say “My XYZ was working fine, then the latest TrueNAS update messed it all up.” You know it will happen. I certainly do.
At least they give us the Developer Mode, I and very thankful for that.
That was just my two cents (while cents still exist).
Yeah, I switch to dev mode and away we go on testing and installing whatever is needed.
I do wish certain things could carry over between upgrades, like settings in /etc. I’ve spent a bunch of time figuring out how to autoload NVMEoF targets to my three TrueNAS VM’s (still working on getting ZFS to import them), and updated a couple of them last night only to realize all my NVME settings were gone. And I also found that trying to mount the /etc directory from the other boot environment isn’t an easy task without messing up the current environment.
I guess the plus side is that once you find a version that works for you, you can stick with it and leave things alone.