The EMI.CONF method provides access to the EMI configuration subsystem. It does not do anything by itself, but provides methods which can be used for this purpose. The EMI.CONF can be used by working with configuration keys and data, and executing EMI.CONF Methods. EMI.CONF uses EMI.CONF Modules to do the actual configuration work.

Configuration Keys and Data

The EMI.CONF configuration data is represented as a key/value pairs, where each key is a tree represented in plain dotted notation. There is no limit for the depth of configuration key tree.

Example of a single EMI.CONF key/value pair, where key is represented in plain dotted notation:

element1.element2.element3=value

|________________________| |___|
             |               |
             |               |
        EMI.CONF key    EMI.CONF key value

The real configuration consisting of multiple keys might look something like this:

if.eth0.up=true
if.eth0.ip=192.168.0.100
if.eth0.netmask=255.255.255.0
if.eth0.gateway=192.168.0.1
.
.
.

NOTE! See EmbedOne Linux EMI Configuration Keys document for more information about the supported configuration keys in EmbedOne Linux.

Save / Commit Logic

EMI.CONF manages internal configuration tree. It supports 2 or more state trees that contain a set of configuration keys. These keys are registered by EMI.CONF Modules. The two obligatory trees are “current” and “new”. The “current” state represents the active configuration. The “new” state represents the modified configuration that should take effect, when committed. Other states are temporal and used only inside EMI.CONFIG Modules.