Elektra Initiative

The Elektra Initiative provides an alternative back-end for text configuration files for the Linux operating system.
Instead of each program having its own text configuration files, with a variety of formats, Elektra tries to provide a universal, hierarchical, fast and consistent namespace and infrastructure to access configuration parameters through a key-value pair mechanism inspired by the Windows Registry. This way any software can read/save its configuration/state using a consistent API.
Being a common infrastructure, it also lets other applications be aware of this application configurations, leveraging easy software integration.
It is designed to be lightweight, with no dependencies, ready to be used also by early boot stage programs.
Using Elektra, configuration file's syntax and handling will not be a rework for each software.
Elektra lets system administrators control security in a more fine grained manner. With the current flat file paradigm it is impossible to control permissions and access times on each of the <tt>/etc/passwd</tt> or <tt>/etc/shadow</tt> atoms. Elektra lets you do that because each information atom stored in it (key) has a unique name (key name) and access properties.
The first name for the Elektra Initiative was the Linux Registry Project, which caused controversy due to its similarities to the Windows registry.
The mains concepts, documentation, architecture and implementation of the Elektra Initiative was created by Avi Alkalay.
Backends
* dconf
*file system
*Berkeley DB

Main Menu

See Also

Main Menu