No gitsync update option for NanoBSD?
-
I walked through all the steps to add IPv6 support to my 2.0 NanoBSD system at home last night and didn't notice until after I was done and running that the gitsync options were missing from the update page. Is this a bug or intentional? What is going to happen if I install a newer 2.0 snapshot?
-
Should have searched…
http://forum.pfsense.org/index.php/topic,32721.msg185721.html#msg185721
Ok, new question. I'm using SLC flash in my system so the issue of burning through the card doesn't exist. Any chance of a future revision of the code including the automatic gitsync options but having them disabled by default on nanobsd with a GIANT warning stating it would be unwise to enable on a standard MLC card?
Oh, and I'd still like to confirm that the automatic gitsync won't apply to my system if I update.
-
Given that most people would be harmed by that rather than helped, I'm not sure it would be a good idea to enable there even with a giant warning. The limit there is only a GUI limit. If you remove that, and get the option set, it would actually be used when the time comes, I believe.
Another problem is that on NanoBSD, it would have to reinstall git each time you do a firmware update, which will add quite a bit of time to the process.
-
Given that most people would be harmed by that rather than helped, I'm not sure it would be a good idea to enable there even with a giant warning. The limit there is only a GUI limit. If you remove that, and get the option set, it would actually be used when the time comes, I believe.
Another problem is that on NanoBSD, it would have to reinstall git each time you do a firmware update, which will add quite a bit of time to the process.
Ok, so if I ran an update now, I'd lose git and the IPv6 customizations, right? If after the update I reinstalled git and rebooted a second time, would everything come back up or would I have to reconfigure the GIF, interface, route, dhcp, firewall/nat rules, etc.?
-
It would be a mess for sure. You have to do the sync before the reboot or it would really freak out with a v6 config loaded on a normal system.
Now that I think on it more, I'm not sure if the gitsync-on-update code accounts for having to install the files on the second NanoBSD slice either, so that wouldn't work at all either way.
You might be better off waiting for databeestje to make new nanobsd snapshots, and then just gitsync from one of those manually after installing/upgrading using them.
