Build install medi with preconfigured config?
-
On the nano images, one can directly integrate the config file in a new installation/media, therefore no classical upgrade needed. How about the full installations?
-
On any installation you can put a new config.xml in place, then reboot, and it comes up with all the settings from the new config, and not the old.
/boot/loader.conf.local might also contain "hardware"-related settings (console speed, disk subsystem settings, USB boot delay…) that are relevant to the particular hardware. That is preserved across upgrades separately to config.xml
Is that what you mean? -
Talking about pre configured images … any way I can make it so that when i hit "Factory Default" the interface assignment doesn't get reset ? I want people to factory default ( and possibly use the reset button on PC Engines APU ) without having to connect via serial and assign interfaces again. This is for a full install ( i can make an image of the install itself if i have to not a problem, then i can just write full image to media )
-
Talking about pre configured images … any way I can make it so that when i hit "Factory Default" the interface assignment doesn't get reset ? I want people to factory default ( and possibly use the reset button on PC Engines APU ) without having to connect via serial and assign interfaces again. This is for a full install ( i can make an image of the install itself if i have to not a problem, then i can just write full image to media )
No way to do that yet.
But I have thought about how to effectively achieve something similar - to make the factory default find whatever 2 likely-looking interfaces it can and use those for WAN and LAN. The "factory default" config could have a flag in it (or a flag file somewhere in /conf) to indicate that this is the first boot of a virgin factory default system. The system could then pick from some favourite device names in some hard-coded preferred order (em0/em1, re0/re1…) and when devices are found for real on the system the config can be automatically set to use those for WAN and LAN. Then clear the "virgin boot" flag so that process does not happen again!
That would be a way to have a varied list of hardware configurations that can boot factory default and run without the user being forced to do anything at the console. To me that is attractive at remote sites... -
I ended up with a new install of 2.2 and importing config. Worked fine and was done in a few minutes.