FOG 1.5.7 Officially Released
-
@NTLINUX Yes right, fresh installs are not affected by this! Fresh installs on Ubuntu with 1.5.7 work perfectly fine.
-
What is the lowest version kernel that is compatible with 1.5.7 ?
-
@sudburr Good question… kernel version is bound to init version more closely than to the rest of FOG. For a long time kernel and init needed to “match” quite closely and therefore I’d advice you to use those “as package”. Download https://fogproject.org/binaries1.5.7.zip, https://fogproject.org/binaries1.5.6.zip, … https://fogproject.org/binaries1.3.0.zip
I can’t promise you 1.3.0 kernel and inits will work with 1.5.7 but I think we have not changed much of what is interacting between FOG webserver and FOS system.
Though I am still wondering why you want to go back? So many things have been fixed within the inits and added hardware compatibility. You only loose going back.
-
Things can break from time to time, and given the sheer variety of … variety, it’s good to know for testing purposes if there is a cutoff for how far back one can go for testing before you reach incompatibility.
That also goes for going forward, using for example a 1.4.4 system, how far up the food chain can one go with the kernels for testing?
-
@sudburr said in FOG 1.5.7 Officially Released:
That also goes for going forward, using for example a 1.4.4 system, how far up the food chain can one go with the kernels for testing?
Pretty much the same answer as I gave you before!
Please be aware that DB-wise going forward/upgrading is supported but going back is NOT!!! Not even a single version. While it should work for some version steps it surely causes issues that are really hard to track down. I suggest, never downgrade unless you have a backup of the old version DB and really know what you do. Snapshot is a save was to Go though.
-
What is the error on Ubuntu? I’m running on 18.04.3 LTSB and upgraded a while back and haven’t been having issues. What should I be looking out for?
-
@astrugatch https://github.com/FOGProject/fogproject/commit/29af4df767775e08fc102ea1cf61b4da789b61d5
Fixed on dev as far as I’m aware, but essentially the issue was that moving from Mysql to Mariadb caused the database to not be moved properly and thus it would appear as if the database is gone to the end user.
If you’re already on the dev branch or if you already had Mariadb installed then you’re likely fine.
-
That’s weird. I’m definitely on master branch (at least according to #git branch) but I’m still running MySQL.
-
@astrugatch Looks like there would be an edge case if you answered ‘no’ to php/apache reinstall during update where it would just carry on with the ‘packages’ line from .fogsettings and thus cause no problems.
-
@astrugatch Quazz is spot on with what he says.
