Section 5

e2fsck.conf · Configuration file for e2fsck
ecasoundrc · ecasound rcfile
edit_list.conf · Configuration of privileges to edit list configuration
editorconfig-format · EditorConfig File Format
editrc · configuration file for editline library
editrc.lukem · configuration file for editline library
editrc.tn · configuration file for editline library
eegdev-biosemi · eegdev backend for Biosemi ActiveTwo hardware
eegdev-datafile · eegdev backend for reading from biosignal data file
eegdev-open-options · Device configuration format specification
eegdev-tobiia · eegdev backend for Tobi Interface A
eft_wuauth · authentication for eftp4linux Eurofile server based on wuftpd.
eft_xferlog · EFT server logfile
eftaccess · eftd configuration file
efthosts · eftd individual user host access file
eg25-manager
eigrpd.conf · EIGRP routing daemon configuration file
ejabberd.yml · main configuration file for ejabberd.
ekeyd.conf · entropy key configuration
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
emil.cf · configuration file for emil(1)
enchant · enchant language tags, ordering files and personal word lists
english · flag format for English ispell dictionaries
envelopes · sender/recipient lists attached to messages
environ · user environment
environment · the environment variables config files
environment.d · Definition of user service environment
epgsearch.conf · The searchtimers
epgsearchblacklists.conf · Blacklist
epgsearchcats.conf · Configuration of the additional EPG information
epgsearchchangrps.conf · Channel groups
epgsearchcmds.conf · EPG Commands
epgsearchdirs.conf · List of directories for selecting in epgsearch
epgsearchmenu.conf · Customizing the EPG menus
epgsearchswitchtimers.conf · The list of switchtimer
epgsearchtemplates.conf · Searchtimer templates
epgsearchuservars.conf · User defined variables
epm.list · epm list file format.
epn.conf · Expiring Password Notification configuration file
epylog-modules · epylog module cofiguration.
epylog.conf · epylog configuration
erbium.conf · Configuration for erbium
erofs · the Enhanced Read-Only File System
esmtprc · esmtp configuration file.
etc-aliases · Files in use by the Debian exim4 packages
etc-email-addresses · Files in use by the Debian exim4 packages
ethers · Ethernet address to IP number database
etter.conf · Ettercap configuration file
euc · EUC encoding of wide characters
euca2ools.ini · configuration for euca2ools
eui64 · IEEE EUI-64 address database
exa_colors · customising the file and UI colours of exa
exabgp.conf · Configuration file controlling the BGP configuration for exabgp(1).
exim4-config_files · Files in use by the Debian exim4 packages
exim4_exim_crt · Files in use by the Debian exim4 packages
exim4_exim_key · Files in use by the Debian exim4 packages
exim4_host_local_deny_exceptions · Files in use by the Debian exim4 packages
exim4_hubbed_hosts · Files in use by the Debian exim4 packages
exim4_local_domain_dnsbl_whitelist · Files in use by the Debian exim4 packages
exim4_local_host_blacklist · Files in use by the Debian exim4 packages
exim4_local_host_whitelist · Files in use by the Debian exim4 packages
exim4_local_rcpt_callout · Files in use by the Debian exim4 packages
exim4_local_sender_blacklist · Files in use by the Debian exim4 packages
exim4_local_sender_callout · Files in use by the Debian exim4 packages
exim4_local_sender_whitelist · Files in use by the Debian exim4 packages
exim4_passwd · Files in use by the Debian exim4 packages
exim4_passwd_client · Files in use by the Debian exim4 packages
exim4_sender_local_deny_exceptions · Files in use by the Debian exim4 packages
expire.ctl · Configuration file for article expiration
exports · NFS server export table
express.conf · configuration file for OpenShift
ext · format of .ext files produced by Magic's hierarchical extractor
ext2 · the second extended file system ext3 - the third extended file system ext4 - the fourth extended file system
ext3 · the second extended file system ext3 - the third extended file system ext4 - the fourth extended file system
ext4 · the second extended file system ext3 - the third extended file system ext4 - the fourth extended file system
ext_sensors.conf · Slurm configuration file for the external sensors plugin
extendedopacity · theory of netpbm interpolation and extrapolation
extension-release · Operating system identification
extmap.conf · Configuration file used by afpd to specify file name extension mappings
extsmail.conf · configure robust sending of e-mail to external commands
extsmail.externals · configure which external commands to robustly send e-mail via
eyefiserver.conf · Settings file for eyefiserver
eza_colors · customising the file and UI colours of eza
eza_colors-explanation · more details on customizing eza colors