Most scripts currently use the loadRunEnvConf() method (from platform-env) to load the environment variables from device.conf, boot.conf, and platform.conf. However, if any of the required variables aren't present, the system can fail to boot or fail to perform expected functionality.
It makes sense to provide defaults for all of these values inside the loadRunEnvConf() method in case a file or value can't be loaded (along with a warning message that the value wasn't found) so as to still allow some level of functionality in case a conf file is missing or in some way corrupted.
This would, for example, allow someone to boot their system after a distribution upgrade if they had forgotten to replace a necessary conf file.
Pull request #14 begins to address the issue, but is not yet ready for integration. Additional analysis of the issue is required, particularly in the case where a conf file with errors is encountered.
Most scripts currently use the
loadRunEnvConf()
method (fromplatform-env
) to load the environment variables fromdevice.conf
,boot.conf
, andplatform.conf
. However, if any of the required variables aren't present, the system can fail to boot or fail to perform expected functionality.It makes sense to provide defaults for all of these values inside the
loadRunEnvConf()
method in case a file or value can't be loaded (along with a warning message that the value wasn't found) so as to still allow some level of functionality in case a conf file is missing or in some way corrupted.This would, for example, allow someone to boot their system after a distribution upgrade if they had forgotten to replace a necessary conf file.