@Uncle-Frank said:
Yes, the installer script creates a new empty (overwrites) exports-file. It’s not easy to write fail-proof script code that checks to see if other entries (or old FOG entries) are in that file. So we better create a clean new one. If you have a good idea how to better do this you are more than welcome to give us a hint.
Please make a backup copy of your file before running the installer. @Tom-Elliott Well, maybe we should do that like we do with /tftpboot…
Maybe use comments before/after the fog exports, like that :
/custom/config1
#FOG settings
/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)
#END FOG settings
/custom/config2
On each update store all other lines not in these comments