.TH "md_doc_help_kdb-mount" 3elektra "Sun May 29 2016" "Version 0.8.14" "Elektra" \" -*- nroff -*-
.ad l
.nh
.SH NAME
md_doc_help_kdb-mount \- kdb-mount(1) - Mount a file to the key database 
\fCkdb mount [<path> <mountpoint>] [<plugin> [<config>] [\&.\&.]]\fP
.PP
.IP "\(bu" 2
Where \fCpath\fP is the path to the file the user wants to mount\&. See \fCkdb info resolver\fP for details what an absolute and relative path means\&.
.IP "\(bu" 2
\fCmountpoint\fP is where in the key database the new backend should be mounted\&. (For a cascading mount pount, \fCmountpoint\fP should start with \fC/\fP)
.IP "\(bu" 2
\fCplugin\fP should be an Elektra plugin\&. A list of such plugins with configuration can be given\&.
.IP "\(bu" 2
Plugins may be followed by a \fC,\fP separated list of keys and their corresponding values which will be written below the backend configuration\&.
.PP
.PP
.SS "DESCRIPTION"
.PP
This command allows a user to mount a new \fIbackend\fP\&.
.PP
The idea of mounting is explained \fBin elektra-mounting(7)\fP\&.
.PP
Mounting in Elektra allows the user to mount a file into the current key database like a user may mount a parition into the current filesystem by creating a \fIbackend\fP\&. This functionality is key to Elektra as it allows users to build a global key database comprised of many different conifguration files\&. A backend acts as a worker to allow Elektra to interpret configuration files as keys in the central key database such that any edits to the keys are reflected in the file and vice versa\&. Additionally, the user can use this command to list the currently mounted backends by running the command with no arguments\&.
.PP
.SS "IMPORTANT"
.PP
This command writes into the \fC/etc\fP directory and as such it requires root permissions\&. Use \fCkdb file system/elektra/mountpoints\fP to find out where exactly it will write to\&.
.PP
.SS "OPTIONS"
.PP
.IP "\(bu" 2
\fC-H\fP, \fC--help\fP: Show the man page\&.
.IP "\(bu" 2
\fC-V\fP, \fC--version\fP: Print version info\&.
.IP "\(bu" 2
\fC-d\fP, \fC--debug\fP: Give debug information or ask debug questions (in interactive mode)\&.
.IP "\(bu" 2
\fC-i\fP, \fC--interactive\fP: Instead of passing all mounting information by parameters ask the user interactively\&.
.IP "\(bu" 2
\fC-R\fP, \fC--resolver <name>\fP: Specify the resolver plugin to use if no resolver is given, the default resolver is used\&. See also \fC/sw/kdb/current/resolver\fP \fCbelow\fP\&.
.IP "\(bu" 2
\fC-0\fP, \fC--null\fP: Use binary 0 termination\&.
.IP "\(bu" 2
\fC-1\fP, \fC--first\fP: Suppress the first column\&.
.IP "\(bu" 2
\fC-2\fP, \fC--second\fP: Suppress the second column\&.
.IP "\(bu" 2
\fC-3\fP, \fC--third\fP: Suppress the third column\&.
.IP "\(bu" 2
\fC-c\fP, \fC--plugins-config\fP: Add a plugin configuration for all plugins\&.
.PP
.PP
.SS "KDB"
.PP
.IP "\(bu" 2
\fC/sw/kdb/current/resolver\fP: The resolver that will be added automatically, if \fC-R\fP is not given\&.
.IP "\(bu" 2
\fC/sw/kdb/current/plugins\fP: It contains a space-separated list of plugins which are added automatically (by default sync)\&.
.PP
.PP
.SS "EXAMPLES"
.PP
To list the currently mounted backends: \fCkdb mount\fP
.PP
To mount a system configuration file using the ini format: \fCkdb mount /etc/configuration\&.ini system/example ini\fP
.PP
Print a null-terminated output of paths and backend names: \fCkdb mount -02 | xargs -0n 2 echo\fP
.PP
To mount the /etc/file system file with two plugins with a respective configuration option each: \fCkdb mount /etc/file system/file plugin1 plugin1config=config1 plugin2 plugin2config=config2\fP
.PP
To mount the /etc/file system file with two plugins and setting both to be verbose: \fCkdb mount -c verbose=1 /etc/file system/file plugin1 plugin2\fP
.PP
To recode and rename a configuration file using Elektra: \fCkdb mount s\&.ini recode\&.txt ni rename cut=path iconv recode=utf8\&.\&.latin1\fP
.PP
.SS "SEE ALSO"
.PP
.IP "\(bu" 2
\fBkdb-umount(7)\fP\&.
.IP "\(bu" 2
\fBelektra-mounting(7)\fP\&.
.IP "\(bu" 2
\fBelektra-plugins(7)\fP\&. 
.PP