Novell LINUX ENTERPRISE DESKTOP 10 SP2 - DEPLOYMENT GUIDE 08-05-2008 Deployment Manual page 237

10.1.1 GConf Repository
Each preference in the GConf repository is expressed as a key-value pair. A GConf
preference key is an element in the repository that corresponds to an application prefer-
ence. For example, the
/apps/gnome-session/options/show_splash_screen preference key
corresponds to the Show Splash Screen on Login option in the Sessions preference tool.
The GNOME Desktop user interface does not contain all of the preference keys in the
GConf repository. For example, the Panel preference tool does not contain an option
that corresponds to the /apps/panel/global/tooltips_enabled key.
The repository is structured like a simple hierarchical file system. The repository contains
the following:
• Directories that correspond to applications that use the GConf repository. For ex-
ample, the file system contains the directory /apps/metacity.
• Subdirectories that correspond to categories of preferences. For example, the file
system contains the directory /apps/metacity/general.
• Special files that list the preference keys in the directory and contain information
about the keys. For example, a file that contains information about the keys that
relate to the HTTP proxy preferences is in the directory /system/http_proxy.
• A /schemas directory that contains files that describe all of the preference keys.
Preference keys typically have simple values such as strings, integers, or lists of strings
and integers. The format of the preference key in the repository depends on the backend
module that is used to read the repository. The following is an example of the /desk-
top/gnome/interface/font_name preference key when an Extensible Markup Language
(XML) backend module is used to read the repository:
<entry name="font_name" mtime="1038323555" muser="user123" type="string">
<stringvalue>Sans 10</stringvalue>
</entry>
GNOME Configuration for Administrators 221