5 File formats

3,927 pages in section 5.

e2

e2fsck.conf Configuration file for e2fsck

ec

ecasoundrc ecasound rcfile

ed

ee

ef

eg

eg25-manager

ei

eigrpd.conf EIGRP routing daemon configuration file

ej

ejabberd.yml main configuration file for ejabberd.

ek

ekeyd.conf entropy key configuration

el

elektra A framework to store configuration atoms hierarchically Elektra Key Storage Strategy.PP Elektra implements a very simple way to store the key-value pairs. The value (and some metainfo) for each key is stored in a single file. The key name (and some of its context) is sufficient to find the file name that stores the value. The system/* keys are stored under /etc/kdb/, and the user/* keys can be found under each user's $HOME/.kdb/. Here are some examples of key names, and where Elektra goes to look for them in the disk. system/sw/XFree86/screen0/driver user/env/PATH user:luciana/env/PATH system/mime.types/some.mime Some may think that one file per key will consume many filesystem i-nodes. Actually, when not using Reiser4 filesystem, it may consume some more disk space, and it may also be not so efficient than reading one single text file, as KConfig does. But Elektra's nature lets applications load their keys on demand; so it is possible to avoid the read-all-use-some approach. Writing updated keys back to disk is also more robust, because unchanged keys won't be touched, different from a single file approach, that must be entirelly rewritten. Besides that, big applications (like Mozilla, Konqueror, KDE, Gnome) key gathering time is a very small part of what they have to do to start up. And the benefits of an homogeneous key database to the entire system are much bigger then these issues. Think about a common integration between everything, flexibility, security granularity and openness. XML, Storage Backends and Elektra.PP This document you are just reading was written in DocBook XML. XML is a wonderfull technology, but brings no value to this software. Two main goals of the Elektra Project are to be lightweight, and to be accessible by early boot stage programs like /sbin/init and the /etc/rc.d scripts. XML parsing libraries are memory eaters, not so fast as we can expect, and they are usually located under /usr/lib, which may be unavailable to these early boot stage needs. Some discussions asked for a sort of plugin architecture to let user decide the format to store keys content. Well, the info that goes into the key file is not big deal as you'll see, and sometimes, too many options is bad business, and not the path for the Elektra Project. So no XML, no plugin architecture, no sophistication. Lets keep it simple and generic. A very straight forward text based file format was defined to store a single key value. Key Files Format.PP Inside Elektra key database, each key is a file, and every file is a key. So most of the key's metainformation are actually its file attributes, as you can see in a regular ls(1) command output. So what needs to be stored inside the key file is the data type (binary or text), key comment and the actual data. The format of each key file is: So if we set the key system/hw/eth0/driver as type String and value "3com", and comment "The driver for my network interface", we'll find the file /etc/kdb/system/hw/eth0/driver containing: Other example: setting user/tmp/proprietary as Binary, and value "A groovy data I want to hide", and comment "Stay away from here", you'll get in ~$USER/.kdb/user/tmp/proprietary the following: The current data types are: Between 20 and 39 40 up to 254 Types between 0 and 19 are used only internaly in the API, and will never appear into a key file. They are used to define meta keys as directory, link, etc.
elf format of Executable and Linking Format (ELF) files
elinks.conf ELinks configuration file
elinkskeys keybindings for ELinks
elza.def elza(1) configuration file

em

emil.cf configuration file for emil(1)

en

ep

er

es

esmtprc esmtp configuration file.

et

eu

ex

ey

eyefiserver.conf Settings file for eyefiserver

ez