Are configuration files architecture specific?
Can I save the configuration of an i386 installation, install an amd386 version of pfSense and restore the configuration and vice-versa, or are the configuration files CPU architecture specific, e.g. are the package names generic and the path from where they are downloaded is determined dynamically based on the type of system that tries to install the packages, or are the packages stored as architecture specific packages in the configuration, which would e.g. lead to an i386 install trying to install amd64 packages, if one restores an amd64 configuration on an i386 system?
Just thinking if it's an option for me to run an i386 version of pfSense once I'm done testing the issues with packages, until these issues are fixed, and then just restoring the i386 configuration once the amd64 package situation has been sorted out…
GruensFroeschli last edited by
I don't know about the packages, but for the rest of the system, the configuration is generic.
(I would assume it's generic for packages as well)
You can restore between i386 and amd64 (and full installs, nanobsd, etc) the config is standard.
The only bits that are architecture dependent (i386/amd64) are:
- RRD data
- Packages which are not available on certain architecture (Like Varnish which is amd64 only)
Great. RRD data I generally don't save anyway, certainly I wouldn't save it for migrating.
However, what happens if the configuration contains data for a package that's not available? Will it simply be ignored, or will it cause trouble?
The thing is, I don't see a means to selectively remove some package from the backup, plus it's easy to include by accident a package that shouldn't be there…
It should just skip the package and go on, though I can't say I've tried that lately. It will remove the fact that it's "installed" in the config but it should keep the settings.