Can we expect that an upcoming update will move FreeNAS 9.10 onto FreeBSD 10.3-RELEASE?
Probably not, because FreeNAS 9.10 isn't based on 10.2-RELEASE. TrueOS seems to follow the STABLE branch, on an "as convenient to the developers" basis. They integrate in changes and patches that are significant to the product, which in some cases includes code that's from 11, or in stable but won't make it into release, etc. That means that there isn't actually a version of FreeBSD that TrueOS and FreeNAS are actually cut directly from.
[root@freenas] ~# cat /etc/version FreeNAS-9.10-MASTER-201604071730 (1e79048) [root@freenas] ~# uname -r 10.3-RELEASE
It's already been done. We're fully sync'd up.Can we expect that an upcoming update will move FreeNAS 9.10 onto FreeBSD 10.3-RELEASE?
This is also true. FreeNAS 9.10 is basically based on "FreeBSD 10.3++"Probably not, because FreeNAS 9.10 isn't based on 10.2-RELEASE. TrueOS seems to follow the STABLE branch, on an "as convenient to the developers" basis. They integrate in changes and patches that are significant to the product, which in some cases includes code that's from 11, or in stable but won't make it into release, etc. That means that there isn't actually a version of FreeBSD that TrueOS and FreeNAS are actually cut directly from.
I'm looking forward to the flame wars about FreeBSD 10.3++16's inclusion of container classes in the standard library.This is also true. FreeNAS 9.10 is basically based on "FreeBSD 10.3++"
No worries! STL stands for "Swivel Towards Linux" in the *BSD world, so no container classes to worry about!I'm looking forward to the flame wars about FreeBSD 10.3++16's inclusion of container classes in the standard library.
Looks like the latest 9.3.1-20160404 update has this ssh "enhancement" as well. Just updated, and the host key changed and the "disabled/none" cipher isn't valid.Unfortunately, the SSH folks have removed support for the None cipher in later revisions so when we updated our ports, we lost that. We're going to create some other mechanism for "zero overhead replication" in 10 and then back-port it to 9.10, but that's not going to happen right away, so for now, just consider the None cipher dead and use one of the "cheaper" ciphers SSH offers. Sorry, but this one was just outside our control!
Looks like the latest 9.3.1-20160404 update has this ssh "enhancement" as well. Just updated, and the host key changed and the "disabled/none" cipher isn't valid.
For replication?... enable rsh?
For replication?
The only options for the cipher in the replication task are "disabled, fast and standard". And disabled no longer works.
Rolling back to an earlier boot environment accomplishes almost exactly this. You just lose whatever config changes you'd made after the update you're rolling back to.Downgrades not supported. If you save a copy of your config file from before the upgrade, and you haven't made any changes, then you always have the option to reinstall and upload that config file.