diff options
| author | Eugene O'Connor <eoconnor@src.gnome.org> | 2002-12-12 16:37:04 +0000 |
|---|---|---|
| committer | Eugene O'Connor <eoconnor@src.gnome.org> | 2002-12-12 16:37:04 +0000 |
| commit | 087b89fae738da5106aa02cc875b6b7552974d3d (patch) | |
| tree | 4ffda9ae305cd6d51690a45a75e5ca209c657783 | |
| parent | 818285ff2b2e634dd690cc5414d71a256f70fb68 (diff) | |
| download | gnome-user-docs-087b89fae738da5106aa02cc875b6b7552974d3d.tar.gz gnome-user-docs-087b89fae738da5106aa02cc875b6b7552974d3d.tar.xz gnome-user-docs-087b89fae738da5106aa02cc875b6b7552974d3d.zip | |
First draft of GNOME 2.0 Desktop System Administration Guide.
| -rw-r--r-- | gnome2-system-admin-guide/C/ChangeLog | 4 | ||||
| -rw-r--r-- | gnome2-system-admin-guide/C/gconf.xml | 1297 | ||||
| -rw-r--r-- | gnome2-system-admin-guide/C/glossary.xml | 113 | ||||
| -rw-r--r-- | gnome2-system-admin-guide/C/l10n-readme.txt | 1 | ||||
| -rwxr-xr-x | gnome2-system-admin-guide/C/l10n-screenshots.txt | 1 | ||||
| -rw-r--r-- | gnome2-system-admin-guide/C/legal.xml | 76 | ||||
| -rw-r--r-- | gnome2-system-admin-guide/C/menustructure.xml | 736 | ||||
| -rwxr-xr-x | gnome2-system-admin-guide/C/system-admin-guide-C.omf | 37 | ||||
| -rw-r--r-- | gnome2-system-admin-guide/C/system-admin-guide.xml | 64 |
9 files changed, 2329 insertions, 0 deletions
diff --git a/gnome2-system-admin-guide/C/ChangeLog b/gnome2-system-admin-guide/C/ChangeLog new file mode 100644 index 0000000..b690144 --- /dev/null +++ b/gnome2-system-admin-guide/C/ChangeLog @@ -0,0 +1,4 @@ +2002-12-12 Eugene O'Connor <eugene.oconnor@sun.com> + + * First draft of System Administration Guide. + diff --git a/gnome2-system-admin-guide/C/gconf.xml b/gnome2-system-admin-guide/C/gconf.xml new file mode 100644 index 0000000..71d0964 --- /dev/null +++ b/gnome2-system-admin-guide/C/gconf.xml @@ -0,0 +1,1297 @@ +<!-- converted from Solbook 2.2 SGML to Docbook 4.2 XML +# Generator: s2d v1.4 2002-09-19 +--> +<chapter id="gconf-0"> + <title>Using GConf</title> + <highlights> + <para>The information in this chapter describes how to use <application>GConf</application> to manage user preferences.</para> + </highlights> + <sect1 id="gconf-1"> + <title>Introducing GConf</title> + <indexterm> + <primary>GConf</primary> + <secondary>introduction</secondary> + </indexterm> + <para><application>GConf</application> simplifies the administration of preferences +for users in the GNOME desktop environment. <application>GConf</application> +enables system administrators to do the following:</para> + <itemizedlist> + <listitem> + <para>Set mandatory values for particular preferences for all users. +In this way, system administrators can control whether users can update particular +preferences.</para> + </listitem> + <listitem> + <para>Set default values for particular preferences for all users. </para> + </listitem> + <listitem> + <para>Use suggested values for preferences that are specified in +definition files for the preferences.</para> + </listitem> + <listitem> + <para>Read documentation on each preference. </para> + </listitem> + </itemizedlist> + <para><application>GConf</application> also notifies applications when a preference +value changes, locally or across a network. In this way, when you change a +preference, all applications that use the preference are immediately updated.</para> + <para><application>GConf</application> has the following components: </para> + <itemizedlist> + <listitem> + <para>A repository of user preferences. </para> + </listitem> + <listitem> + <para>A daemon, <command>gconfd-2</command>.</para> + </listitem> + <listitem> + <para>A command line tool, <command>gconftool-2</command>.</para> + </listitem> + </itemizedlist> + </sect1> + <sect1 id="gconf-24"> + <title>GConf Repository</title> + <indexterm> + <primary>GConf</primary> + <secondary>repository</secondary> + </indexterm> + <para>Each preference in the <application>GConf</application> repository is +expressed as a key-value pair. A <firstterm>GConf preference key</firstterm> +is an element in the repository that corresponds to an application preference. +For example, the <literal>/apps/gnome-session/options/show_splash_screen</literal> +preference key corresponds to the <guilabel>Show splash screen on login</guilabel> +option in the <application>Sessions</application> preference tool. The GNOME +user interface does not contain all of the preference keys in the <application>GConf</application> repository. For example, the <application>Sessions</application> +preference tool does not contain an option that corresponds to the <literal>/apps/gnome-session/options/splash_screen_text</literal> key.</para> + <para>The repository is structured like a simple hierarchical file system. +The repository contains the following:</para> + <itemizedlist> + <listitem> + <para>Directories that correspond to applications that use the <application>GConf</application> repository. For example, the file system contains the +directory <filename>/apps/metacity</filename>. </para> + </listitem> + <listitem> + <para>Subdirectories that correspond to categories of preferences. +For example, the file system contains the directory <filename>/apps/metacity/general</filename>.</para> + </listitem> + <listitem> + <para>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 <filename>/system/http_proxy</filename>. </para> + </listitem> + <listitem> + <para>A <filename>/schemas</filename> directory that contains files +that describe all of the preference keys.</para> + </listitem> + </itemizedlist> + <para>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 <literal>/desktop/gnome/interface/font_name</literal> preference key when an Extensible Markup Language (XML) backend +module is used to read the repository:</para> + <literallayout><entry name="font_name" mtime="1038323555" muser="user123" type="string"> +<stringvalue>avantgarde 10</stringvalue></entry></literallayout> + <note> + <para>When this guide refers to a preference key, the path to the key +is added to the name of the key. For example, the <literal>font_name</literal> +preference key in the <filename>/desktop/gnome/interface</filename> subdirectory +is referred to as <literal>/desktop/gnome/interface/font_name</literal>.</para> + </note> + <sect2 id="gconf-26"> + <title>GConf Configuration Sources</title> + <indexterm> + <primary>GConf</primary> + <secondary>configuration sources</secondary> + </indexterm> + <para>The <application>GConf</application> repository contains +a series of storage locations that are called <firstterm>configuration sources</firstterm>. The configuration sources are listed in the <firstterm>GConf +path file</firstterm>. The location of the <application>GConf</application> +path file is <filename>/etc/gconf/<replaceable>version_number</replaceable>/path</filename>. Each user has a path file. Each line in the path file specifies +the following information:</para> + <itemizedlist> + <listitem> + <para>The backend module to use to read the repository. </para> + </listitem> + <listitem> + <para>The permissions on the repository.</para> + </listitem> + <listitem> + <para>The location of the repository.</para> + </listitem> + </itemizedlist> + <para>By default, the contents of the <application>GConf</application> path +file are as follows: </para> + <literallayout>xml:readonly:/etc/gconf/gconf.xml.mandatory +include "$(HOME)/.gconf.path" +xml:readwrite:$(HOME)/.gconf +xml:readonly:/etc/gconf/gconf.xml.defaults</literallayout> + <para>When <application>GConf</application> searches for a preference value, <application>GConf</application> reads the configuration sources in the order specified +in the path file. The following table describes the configuration sources +in the path file:</para> + <informaltable frame="topbot"> + <tgroup cols="2" colsep="0" rowsep="0"> + <colspec colwidth="31.29*"/> + <colspec colwidth="68.71*"/> + <thead> + <row rowsep="1"> + <entry valign="top"> + <para>Configuration Source</para> + </entry> + <entry valign="top"> + <para>Description</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry valign="top"> + <para>Mandatory</para> + </entry> + <entry valign="top"> + <para>The permissions on this configuration source are set to read only. Users cannot +overwrite the values in this source, so the preferences in the source are +mandatory.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para>User</para> + </entry> + <entry valign="top"> + <para>This configuration source is stored in the <filename>.gconf</filename> directory +in the home directory of the user. When the user sets a preference, the new +preference information is added to this location. </para> + </entry> + </row> + <row> + <entry valign="top"> + <para>Default</para> + </entry> + <entry valign="top"> + <para>This configuration source contains the default preference settings.</para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para>The sequence of the configuration sources in the path file ensures that +mandatory preference settings override user preference settings. The sequence +also ensures that user preference settings override default preference settings. +That is, <application>GConf</application> applies preferences in the following +order of priority:</para> + <orderedlist> + <listitem> + <para>Mandatory preferences </para> + </listitem> + <listitem> + <para>User-specified preferences </para> + </listitem> + <listitem> + <para>Default preferences</para> + </listitem> + </orderedlist> + <para>The <literal>include</literal> instruction in the <application>GConf</application> path file enables users to use another configuration source. +To use another configuration source, the user must specify the location of +the configuration source. The user specifies the location of the configuration +source in the home directory, in a file that is called <filename>.gconf.path</filename>.</para> + </sect2> + <sect2 id="gconf-27"> + <title>GConf Schemas</title> + <indexterm> + <primary>GConf</primary> + <secondary>schemas</secondary> + </indexterm> + <indexterm> + <primary>GConf</primary> + <secondary>schema keys</secondary> + </indexterm> + <indexterm> + <primary>GConf</primary> + <secondary>schema objects</secondary> + </indexterm> + <para>A <firstterm>GConf schema</firstterm> is a collective term for a <firstterm>GConf schema key</firstterm> and a <firstterm>GConf schema object</firstterm>. +The following table describes schema keys and schema objects and the relationship +of these items to preference keys:</para> + <informaltable frame="topbot"> + <tgroup cols="2" colsep="0" rowsep="0"> + <colspec colname="colspec0" colwidth="24.31*"/> + <colspec colname="colspec1" colwidth="75.69*"/> + <thead> + <row rowsep="1"> + <entry valign="top"> + <para>Item</para> + </entry> + <entry valign="top"> + <para>Description</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry colname="colspec0" valign="top"> + <para>Preference key</para> + </entry> + <entry colname="colspec1" valign="top"> + <para>An element in the <application>GConf</application> repository that corresponds to an application preference.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para>Schema key</para> + </entry> + <entry valign="top"> + <para>A key that stores a schema object for a preference key. </para> + </entry> + </row> + <row> + <entry valign="top"> + <para>Schema object</para> + </entry> + <entry valign="top"> + <para>An element in a configuration source that contains information for a preference +key, such as the following:</para> + <itemizedlist> + <listitem> + <para>The name of the application that uses the preference key.</para> + </listitem> + <listitem> + <para>The type of value required for the preference key, for example +integer, boolean, and so on.</para> + </listitem> + <listitem> + <para>A default value for the preference key. </para> + </listitem> + <listitem> + <para>Brief documentation on the preference key.</para> + </listitem> + </itemizedlist> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para>The following table gives examples of a preference key, a schema key, +and a schema object:</para> + <informaltable frame="topbot"> + <tgroup cols="2" colsep="0" rowsep="0"> + <colspec colname="colspec0" colwidth="24.31*"/> + <colspec colname="colspec1" colwidth="75.69*"/> + <thead> + <row rowsep="1"> + <entry valign="top"> + <para>Item</para> + </entry> + <entry valign="top"> + <para>Example</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry colname="colspec0" valign="top"> + <para>Preference key</para> + </entry> + <entry colname="colspec1" valign="top"> + <para> + <literal>/desktop/gnome/interface/font_name</literal> + </para> + </entry> + </row> + <row> + <entry colname="colspec0" valign="top"> + <para>Schema key</para> + </entry> + <entry colname="colspec1" valign="top"> + <para> + <literal>/schemas/desktop/gnome/interface/font_name</literal> + </para> + </entry> + </row> + <row> + <entry valign="top"> + <para>Schema object</para> + </entry> + <entry valign="top"> + <literallayout><schema> + <applyto>/desktop/gnome/interface/font_name</applyto> + <key>/schemas/desktop/gnome/interface/font_name</key> + <owner>gnome</owner> + <type>string</type> + <default>Sans 10</default> + <locale name="C"> + <short>Default font</short> + <long>Name of the default font used by gtk+.</long> + </locale> +</schema></literallayout> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para>You can associate a schema key with a preference key. For example, the +following <literal>/desktop/gnome/interface/font_name</literal> key includes +a schema key:</para> + <literallayout><entry name="font_name" mtime="1034873859" +schema="/schemas/desktop/gnome/interface/font_name"/></literallayout> + <para>When you associate a schema key with a preference key, the preference +uses the suggested value that is specified in the schema object of the schema +key. The suggested value is contained in the <literal><default></literal> +element in the schema object. By default, all the preference keys in the default +configuration source are associated with schema keys.</para> + <para>Typically, schemas are stored in the default configuration source. </para> + </sect2> + <sect2 id="gconf-2"> + <title>GConf Schema Definition Files</title> + <indexterm> + <primary>GConf</primary> + <secondary>schema definition files</secondary> + <tertiary>introduction</tertiary> + </indexterm> + <para>Schemas are generated from <firstterm>schema definition files</firstterm>. A schema definition file defines the +characteristics of all of the keys in a particular application. Schema definition +files have a <filename>.schemas</filename> extension.</para> + <para>The schema definition files are included in the <filename>/etc/gconf/schemas</filename> directory. You can use the schema definition files to create a +new configuration source.</para> + <para>Some schema definition files correspond closely to a part of the GNOME +user interface. For example, <filename>system_http_proxy.schemas</filename> +corresponds to the <application>Network Proxy</application> preference tool. +Other schema definition files contain preference keys that are not present +in the GNOME user interface. For example, the <literal>/apps/gnome-session/options/splash_screen_text</literal> key is not present in the user interface. </para> + <para>Some parts of the GNOME user interface contain preferences that represent +preference keys from more than one schema definition file. For example, the <application>Keyboard Shortcuts</application> preference tool contains preferences that +represent keys from the <filename>panel-global-config.schemas</filename> and <filename>metacity.schemas</filename> files.</para> + </sect2> + </sect1> + <sect1 id="gconf-25"> + <title>GConf Daemon</title> + <indexterm> + <primary>gconfd</primary> + <see>GConf daemon</see> + </indexterm> + <indexterm> + <primary>GConf</primary> + <secondary>daemon</secondary> + </indexterm> + <para>The <application>GConf</application> daemon is called <command>gconfd-2</command>. The <application>GConf</application> daemon notifies applications when a preference value changes. +For example, you might select to show only icons in toolbars in the <application>Menus & Toolbars</application> preference tool. When you select this option +in the preference tool, the toolbars on all open applications are updated +instantly. The <application>GConf</application> daemon can operate locally, +or across a network.</para> + <para>An instance of the <application>GConf</application> daemon is started +for each user. The <application>GConf</application> daemon does not have to +deal with complex problems such as authentication and data security. When +the <application>GConf</application> daemon starts, the daemon loads the <application>GConf</application> path file. The <application>GConf</application> daemon +manages all access between applications and the configuration sources.</para> + <para>When an application requests the value of a preference key, the daemon +searches the configuration sources as follows:</para> + <orderedlist> + <listitem> + <para>Search for the value of the preference key in each configuration +source, in the order specified in the path file. If the value is found, return +the value.</para> + </listitem> + <listitem> + <para>If a value is not found, search for the schema key that corresponds +to the preference key in each configuration source, in the order specified +in the path file.</para> + </listitem> + <listitem> + <para>If the schema key is found, check the value of the schema +key.</para> + </listitem> + <listitem> + <para>If the value of the schema key is a schema object, return +the suggested value in the <literal><default></literal> element of the +schema object.</para> + </listitem> + </orderedlist> + <para>The <application>GConf</application> daemon also caches preference key +values. All applications use this cache, so applications only need to access +the configuration sources once.</para> + <para>To terminate the <application>GConf</application> daemon, run the following +command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --shutdown</userinput></para> + </sect1> + <sect1 id="gconf-6"> + <title>GConf Command Line Tool</title> + <indexterm> + <primary>GConf</primary> + <secondary>command line tool</secondary> + </indexterm> + <para><application>GConf</application> includes a command line +tool, <command>gconftool-2</command>. You can use the <command>gconftool–2</command> command to perform the following tasks: </para> + <itemizedlist> + <listitem> + <para>Set the values of keys.</para> + </listitem> + <listitem> + <para>Display the values of keys.</para> + </listitem> + <listitem> + <para>Install schemas from schema definition files when you install +an application.</para> + </listitem> + </itemizedlist> + <para>For example, use the following command to display the values of all +keys in the <filename>/desktop/gnome</filename> directory and subdirectories.</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --recursive-list +/desktop/gnome</userinput></para> + <para><xref linkend="gconf-TBL-7"/> lists some of the options that you can +use with the <command>gconftool-2</command> command.</para> + <table frame="topbot" id="gconf-TBL-7"> + <title>gconftool-2 Command Options</title> + <tgroup cols="2" colsep="0" rowsep="0"> + <colspec colname="colspec0" colwidth="35.52*"/> + <colspec colname="colspec1" colwidth="64.48*"/> + <thead> + <row rowsep="1"> + <entry valign="top"> + <para>Option</para> + </entry> + <entry valign="top"> + <para>Function</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry colname="colspec0" valign="top"> + <para> + <literal>--all-dirs</literal> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Lists all subdirectories in a +directory that you specify.</para> + </entry> + </row> + <row> + <entry colname="colspec0" valign="top"> + <para> + <literal>--all-entries</literal> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Displays the values of all keys +in a directory that you specify.</para> + </entry> + </row> + <row> + <entry colname="colspec0" valign="top"> + <para> + <literal>--config-source=<replaceable>configuration_source</replaceable></literal> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Use this option with the <literal>--direct</literal> option +to specify a configuration source to use. If you do not specify a configuration +source with this option, the command runs on all configuration sources in +the path file.</para> + </entry> + </row> + <row> + <entry colname="colspec0" valign="top"> + <para> + <literal>--direct</literal> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Use this option with the <literal>--config-source</literal> option to access a configuration source directly. +When you use this option, <application>GConf</application> bypasses the server. +Ensure that the <application>GConf</application> daemon, <command>gconfd-2</command>, is not running before you use this option.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>--get</literal> + </para> + </entry> + <entry valign="top"> + <para>Displays the value of a preference key that you specify. +Also displays the values of the elements in the schema object for a schema +key that you specify.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>--help</literal> + </para> + </entry> + <entry valign="top"> + <para>Displays a help message about the <command>gconftool-2</command> command, and the options that you can use with the <command>gconftool-2</command> command.</para> + </entry> + </row> + <row> + <entry colname="colspec0" valign="top"> + <para> + <literal>--long-desc=<replaceable>description</replaceable></literal> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Use this option with the <literal>--set-schema</literal> +option to specify a long description for a schema key. </para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>--makefile-install-rule</literal> + </para> + </entry> + <entry valign="top"> + <para>Installs schema definition files to applications.</para> + </entry> + </row> + <row> + <entry colname="colspec0" valign="top"> + <para> + <literal>--owner=<replaceable>owner</replaceable></literal> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Use this option with the <literal>--set-schema</literal> option to specify +an owner for a schema key. </para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>--recursive-list</literal> + </para> + </entry> + <entry valign="top"> + <para>Displays the value of all preference keys in all +subdirectories in a directory that you specify.</para> + </entry> + </row> + <row> + <entry colname="colspec0" valign="top"> + <para> + <literal>--recursive-unset</literal> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Resets +the values of all preference keys, in all subdirectories in a directory, from +the user setting to the setting in the default configuration source.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>--set</literal> + </para> + </entry> + <entry valign="top"> + <para>Sets the value of a preference key, and writes the value +to the user configuration source. Use the <literal>--type</literal> option +with the <literal>--set</literal> option to specify the data type of the value +that you want to set. For example, the following command sets the value of +the <literal>/apps/gnome-terminal/profiles/Default/background_color</literal> +key in the user configuration source:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --set "/apps/gnome-terminal/profiles/Default/background_color" +--type string "#000000"</userinput></para> + <para>You can also use the <literal>--direct</literal> option and the <literal>--config-source</literal> option +with the <literal>--set</literal> option to write a value to another configuration +source.</para> + </entry> + </row> + <row> + <entry colname="colspec0" valign="top"> + <para> + <literal>--set-schema</literal> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Sets the value of an attribute +in a schema key, and writes the value to the default configuration source.</para> + <para>Use the following options with the <literal>--set-schema</literal> +option to specify the attribute that you want to update:</para> + <itemizedlist> + <listitem> + <para> + <literal>--type</literal> + </para> + </listitem> + <listitem> + <para> + <literal>--short-desc</literal> + </para> + </listitem> + <listitem> + <para> + <literal>--long-desc</literal> + </para> + </listitem> + <listitem> + <para> + <literal>--owner</literal> + </para> + </listitem> + </itemizedlist> + <para>For example, the following command sets the short description +in the schema key for the <literal>/apps/gnome-terminal/profiles/Default/background_color</literal> key:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --set-schema "/schemas/apps/gnome-terminal/profiles/Default/background_color" +--short-desc "Default background color of terminal"</userinput></para> + </entry> + </row> + <row> + <entry colname="colspec0" valign="top"> + <para> + <literal>--short-desc=<replaceable>description</replaceable></literal> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Use this option with the <literal>--set-schema</literal> +option to specify a short description for a schema key. </para> + </entry> + </row> + <row> + <entry colname="colspec0" valign="top"> + <para> + <literal>--shutdown</literal> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Terminates the <application>GConf</application> daemon.</para> + </entry> + </row> + <row> + <entry colname="colspec0" valign="top"> + <para> + <literal>--type=<replaceable>data_type</replaceable></literal> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Use this option to specify the data type when you set a +value of a preference key. You can also use this option when you set the value +of an attribute in a schema key. The following is a list of valid data types:</para> + <itemizedlist> + <listitem> + <para> + <literal>bool</literal> + </para> + </listitem> + <listitem> + <para> + <literal>float</literal> + </para> + </listitem> + <listitem> + <para> + <literal>int</literal> + </para> + </listitem> + <listitem> + <para> + <literal>list</literal> + </para> + </listitem> + <listitem> + <para> + <literal>pair</literal> + </para> + </listitem> + <listitem> + <para> + <literal>string</literal> + </para> + </listitem> + </itemizedlist> + </entry> + </row> + <row> + <entry colname="colspec0" valign="top"> + <para> + <literal>--unset</literal> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Resets the value of a preference +key from the user setting to the setting in the default configuration source.</para> + </entry> + </row> + <row> + <entry colname="colspec0" valign="top"> + <para> + <literal>--usage</literal> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Displays a brief help message +about the <command>gconftool-2</command> command, and the options that you +can use with the <command>gconftool-2</command> command.</para> + </entry> + </row> + </tbody> + </tgroup> + </table> + </sect1> + <sect1 id="gconf-7"> + <title>To Set Preference Values</title> + <indexterm> + <primary>GConf</primary> + <secondary>setting preference values</secondary> + </indexterm> + <para>You can set a mandatory value or a default value for a preference +key. Before you change mandatory preference values or default preference values +for users, you must ensure that the <application>GConf</application> daemon +is not running for any user. Ensure that all users are logged out before you +change preference values for users.</para> + <para>To set a mandatory value or a default value for a preference key, use +the <command>gconftool-2</command> command, as follows:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --direct --config-source <replaceable>configuration_source</replaceable> --type <replaceable>data_type</replaceable> +--set <replaceable>preference_key</replaceable> <replaceable>value</replaceable></userinput></para> + <para>For example, to set <literal>wwwproxy.xyz.com</literal> as the mandatory +HTTP proxy host, run the following command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --direct --config-source +xml:readwrite:/etc/gconf/gconf.xml.mandatory --type string --set /system/http_proxy/host +wwwproxy.xyz.com</userinput></para> + <para>The user cannot override this preference value.</para> + <para>You can also use the <command>gconftool-2</command> command to set default +values. For example, to set the default number of workspaces to five, run +the following command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --direct --config-source +xml:readwrite:/etc/gconf/gconf.xml.defaults --type int --set /apps/metacity/general/num_workspaces +5</userinput></para> + <para>The user can override this preference value.</para> + <caution> + <para>Before you change mandatory preference values or default preference +values for users, you must ensure that all users are logged out.</para> + </caution> + </sect1> + <sect1 id="gconf-8"> + <title>Setting General Preferences</title> + <para>The following sections describe how to assign mandatory or default values +to general preferences.</para> + <sect2 id="gconf-10"> + <title>To Set HTTP Proxy Preferences</title> + <indexterm> + <primary>GConf</primary> + <secondary>setting HTTP proxy</secondary> + </indexterm> + <para>To set HTTP proxy preferences, you modify the values of +the preference keys in the <filename>/system/http_proxy/</filename> location. +For example, to set a mandatory value for the HTTP proxy host, run the following +command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --direct --config-source +xml:readwrite:/etc/gconf/gconf.xml.mandatory --type string --set /system/http_proxy/host <replaceable>proxy_name</replaceable></userinput></para> + <para>To set a default value for the HTTP proxy host, run the following command: </para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --direct --config-source +xml:readwrite:/etc/gconf/gconf.xml.defaults --type string --set /system/http_proxy/host <replaceable>proxy_name</replaceable></userinput></para> + <para>You can also set other HTTP proxy-related preferences. For information +on the other HTTP proxy preferences, see the <filename>system_http_proxy.schemas</filename> schema definition file.</para> + </sect2> + <sect2 id="gconf-11"> + <title>To Set Print Manager Preferences</title> + <para>To set print manager preferences, you modify the values of the preference +keys in the <filename>/apps/gnome-print-manager</filename> location. For example, +if you do not want users to view the print jobs of other users, set a mandatory +value as follows: </para> + <indexterm> + <primary>GConf</primary> + <secondary>setting print manager</secondary> + </indexterm> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 +--direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type +bool --set /apps/gnome-print-manager/show_all_jobs false</userinput></para> + <para>To set a default value for this preference, run the following command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --direct --config-source +xml:readwrite:/etc/gconf/gconf.xml.defaults --type bool --set /apps/gnome-print-manager/show_all_jobs +false</userinput></para> + <para>You can also set other print manager preferences. For information on +the other print manager preferences, see the <filename>gnome-print-manager.schemas</filename> schema definition file.</para> + </sect2> + <sect2 id="gconf-12"> + <title>To Set the Number of Workspaces</title> + <indexterm> + <primary>GConf</primary> + <secondary>setting number of workspaces</secondary> + </indexterm> + <para>To set a mandatory number of workspaces, use +the following command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --direct --config-source +xml:readwrite:/etc/gconf/gconf.xml.mandatory --type int --set /apps/metacity/general/num_workspaces <replaceable>integer</replaceable></userinput></para> + <para>To set a default number of workspaces, use the following command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --direct --config-source +xml:readwrite:/etc/gconf/gconf.xml.defaults --type int --set /apps/metacity/general/num_workspaces <replaceable>integer</replaceable></userinput></para> + <para>You can also set other window manager preferences. For information on +the other window manager preferences, see the <filename>metacity.schemas</filename> +schema definition file.</para> + </sect2> + <sect2 id="gconf-16"> + <title>To Set Keyboard Accessibility Preferences</title> + <indexterm> + <primary>GConf</primary> + <secondary>setting keyboard accessibility</secondary> + </indexterm> + <para>To set keyboard accessibility preferences, you +modify the values of the preference keys in the <filename>/desktop/gnome/accessibility/keyboard</filename> location. For example, if you want to set a mandatory value so +that keyboard accessibility features are enabled, run the following command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --direct --config-source +xml:readwrite:/etc/gconf/gconf.xml.mandatory --type bool --set /desktop/gnome/accessibility/keyboard/enable +true</userinput></para> + <para>To set a default value for this preference, run the following command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --direct --config-source +xml:readwrite:/etc/gconf/gconf.xml.defaults --type bool --set desktop/gnome/accessibility/keyboard/enable +false</userinput></para> + <para>You can also set other keyboard accessibility preferences. For information +on the other keyboard accessibility preferences, see the <filename>desktop_gnome_accessibility_keyboard.schemas</filename> schema definition file.</para> + </sect2> + <sect2 id="gconf-18"> + <title>To Set Keyboard Shortcut Preferences</title> + <indexterm> + <primary>GConf</primary> + <secondary>setting keyboard shortcuts</secondary> + </indexterm> + <para>To set keyboard shortcut preferences, you modify the values +of preference keys in two locations. The following table shows the locations +to modify, and the part of the user interface to which the locations correspond:</para> + <informaltable frame="topbot"> + <tgroup cols="2" colsep="0" rowsep="0"> + <colspec colwidth="50*"/> + <colspec colwidth="50*"/> + <thead> + <row rowsep="1"> + <entry valign="top"> + <para>GConf Location</para> + </entry> + <entry valign="top"> + <para>User Interface Component</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry valign="top"> + <para> + <filename>/apps/panel/global</filename> + </para> + </entry> + <entry valign="top"> + <para><application>Keyboard Shortcuts</application> preference +tool, <guilabel>Desktop</guilabel> section</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <filename>/apps/metacity/general</filename> + </para> + </entry> + <entry valign="top"> + <para><application>Keyboard Shortcuts</application> preference +tool, <guilabel>Window Management</guilabel> section</para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para>For example, you might want users to use only the <keycombo><keycap>Alt</keycap><keycap>F3</keycap></keycombo> + keyboard shortcut to open the <guilabel>Run Program</guilabel> dialog. To set this mandatory value, run the following command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --direct --config-source +xml:readwrite:/etc/gconf/gconf.xml.mandatory --type string --set /apps/panel/global/run_key +'<Alt>F3'</userinput></para> + <para>You might want users to use <keycombo><keycap>Alt</keycap><keycap>F11</keycap></keycombo> +to maximize windows, by default. To set this default value, run the following +command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --direct --config-source +xml:readwrite:/etc/gconf/gconf.xml.defaults --type string --set /apps/metacity/window_keybindings/maximize +'<Alt>F11'</userinput></para> + <para>You can also set other keyboard shortcut preferences. For information +on the other keyboard shortcut preferences, see the <filename>panel-global-config.schemas</filename> and <filename>metacity.schemas</filename> schema definition files.</para> + </sect2> + <sect2 id="gconf-13"> + <title>To Set Global Panel Preferences</title> + <indexterm> + <primary>GConf</primary> + <secondary>setting global panel preferences</secondary> + </indexterm> + <para>To set global preferences for panels, you modify +the values of the preference keys in the <filename>/apps/panel/global</filename> +location. For example, if you do not want users to ever use panel animation, +set a mandatory value as follows:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --direct --config-source +xml:readwrite:/etc/gconf/gconf.xml.mandatory --type bool --set /apps/panel/global/enable_animations +false</userinput></para> + <para>To set a default value for this preference, run the following command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --direct --config-source +xml:readwrite:/etc/gconf/gconf.xml.defaults --type bool --set /apps/panel/global/enable_animations +false</userinput></para> + <para>You can also set other global panel preferences. For information on +the other global panel preferences, see the <filename>panel-global-config.schemas</filename> schema definition file.</para> + </sect2> + <sect2 id="gconf-14"> + <title>To Set Preferences for Individual Panels and Panel Objects</title> + <indexterm> + <primary>GConf</primary> + <secondary>setting panel object preferences</secondary> + </indexterm> + <indexterm> + <primary>GConf</primary> + <secondary>setting +individual panel preferences</secondary> + </indexterm> + <para>The <filename>panel-per-panel-config.schemas</filename> schema definition file specifies the following details of the +panels on the desktop:</para> + <itemizedlist> + <listitem> + <para>Number of panels.</para> + </listitem> + <listitem> + <para>Types of the panels.</para> + </listitem> + <listitem> + <para>Properties of the panels.</para> + </listitem> + <listitem> + <para>Contents of the panels.</para> + </listitem> + </itemizedlist> + <para>The configuration of individual panels and of panel objects is a complex +task. To configure individual panels and panel objects, you must first understand +the structure of the <filename>panel-per-panel-config.schemas</filename> schema +definition file. For more information on the <filename>panel-per-panel-config.schemas</filename> schema definition file, see the next section.</para> + <para>To set preferences for individual panels and panel objects, you must +set the values of many preferences in a configuration source. The easiest +way to set the values of many preferences is to use a script. For a sample +script that sets preferences for a panel and objects on the panel, see <xref linkend="gconf-3"/>.</para> + <sect3 id="gconf-23"> + <title>Schema Definition File for Individual Panels and Panel Objects</title> + <indexterm> + <primary>GConf</primary> + <secondary>schema definition files</secondary> + <tertiary>panel and panel object</tertiary> + </indexterm> + <para>The schema definition +file <filename>panel-per-panel-config.schemas</filename> contains sections +that specify panels and panel contents for small, medium, and large screens. +The section for small screens and the section for large screens are not functional +at the time of publication of this guide. To learn about preference keys for +panels or panel objects, read the section for medium screens only. </para> + <para>The medium section of the file <filename>panel-per-panel-config.schemas</filename> is structured as follows:</para> + <orderedlist> + <listitem> + <para>Preference keys that specify the general structure of panels, +applets, and other panel objects on the desktop. The following keys specify +the number of panels, applets, and other panel objects that appear on the +desktop:</para> + <itemizedlist> + <listitem> + <para> + <literal>/apps/panel/default_profiles/medium/general/panel_id_list</literal> + </para> + </listitem> + <listitem> + <para> + <literal>/apps/panel/default_profiles/medium/general/applet_id_list</literal> + </para> + </listitem> + <listitem> + <para> + <literal>/apps/panel/default_profiles/medium/general/object_id_list</literal> + </para> + </listitem> + </itemizedlist> + <para>The keys also assign identifiers to each panel, applet, and panel object. +For example, the following excerpt from <filename>panel-per-panel-config.schemas</filename> specifies that two panels appear on the desktop:</para> + <literallayout><key>/schemas/apps/panel/default_profiles/medium/ +general/panel_id_list</key> +. +. +. +<default>[00000001,00000002]</default></literallayout> + <para>In <filename>panel-per-panel-config.schemas</filename>, the identifier +00000001 identifies the bottom edge panel, and the identifier 00000002 identifies +the Menu Panel.</para> + </listitem> + <listitem> + <para>Preference keys that specify the properties of the panels. +The panel property keys are structured as follows:</para> + <literallayout>/apps/panel/default_profiles/medium/panels/<replaceable>panel_number</replaceable>/<replaceable>panel_property_key</replaceable></literallayout> + <para>For example, the key <literal>/apps/panel/default_profiles/medium/panels/00000001/screen_edge</literal> specifies the edge of the display on which the bottom edge panel +resides. </para> + <para>The keys that specify the properties of the bottom edge panel are listed +first. The keys that specify the properties of the Menu Panel are listed at +the end of the medium section in <filename>panel-per-panel-config.schemas</filename>. </para> + </listitem> + <listitem> + <para>Preference keys that list the panel objects, the panel object +properties, and the panels in which the objects reside. For example, the following +excerpt from <filename>panel-per-panel-config.schemas</filename> specifies +object 00000001:</para> + <literallayout><key>/schemas/apps/panel/default_profiles/medium/ +objects/00000001/object_type</key> +. +. +. +<default>launcher-object</default> +. +. +. +<key>/schemas/apps/panel/default_profiles/medium/ +objects/00000001/launcher_location</key> +. +. +. +<default>applications:///nautilus.desktop</default> +. +. +. +<key>/schemas/apps/panel/default_profiles/medium/ +objects/00000001/panel_id</key> +. +. +. +<default>00000002</default></literallayout> + <para>The object is a launcher that starts <application>Nautilus</application> +file manager. The launcher resides in the Menu Panel.</para> + </listitem> + <listitem> + <para>Preference keys that list the applets, the applet preferences, +and the panels in which the applets reside. For example, the following excerpt +from <filename>panel-per-panel-config.schemas</filename> specifies applet +00000001:</para> + <literallayout><key>/schemas/apps/panel/default_profiles/medium/ +applets/00000001/object_type</key> +. +. +. +<default>bonobo-applet</default> +. +. +. +<key>/schemas/apps/panel/default_profiles/medium/ +applets/00000001/panel_id</key> +. +. +. +<default>00000001</default> +. +. +. +<key>/schemas/apps/panel/default_profiles/medium/ +applets/00000001/bonobo_iid</key> +. +. +. +<default>OAFIID:GNOME_TasklistApplet</default></literallayout> + <para>The applet is the <application>Window List</application> applet. The +applet resides in the bottom edge panel.</para> + </listitem> + </orderedlist> + </sect3> + <sect3 id="gconf-3"> + <title>Sample Script for Setting Individual Panel Preferences</title> + <para>This section contains a sample script that sets the preferences for +a panel that has the following major characteristics:</para> + <itemizedlist> + <listitem> + <para>The panel is an edge panel, and resides at the bottom edge +of the screen.</para> + </listitem> + <listitem> + <para>The panel contains a file manager launcher and a <application>Terminal</application> launcher.</para> + </listitem> + <listitem> + <para>The panel contains a <application>Window List</application> +applet.</para> + </listitem> + </itemizedlist> + <para>The sample script also sets other minor preferences. All of the preferences +have default values, not mandatory values.</para> + <para>The sample script follows:</para> + <literallayout># Usage is: set_key <type> <key> <value> <extra options if any> + +function set_key() +{ + TYPE="$1" + shift + KEY="$1" + shift + VALUE="$1" + shift + OTHER_ARGS="$*" + gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.defaults +--owner=panel $OTHER_ARGS --type "$TYPE" --set "$KEY" "$VALUE" +} + +# Define the number of panels, the number of launchers, and the number of applets +set_key list /apps/panel/default_profiles/medium/general +/panel_id_list [00000001] --list-type string +set_key list /apps/panel/default_profiles/medium/general +/object_id_list [00000001,00000002] --list-type string +set_key list /apps/panel/default_profiles/medium/general +/applet_id_list [00000001] --list-type string + +# Define the characteristics of the panel +set_key string /apps/panel/default_profiles/medium/panels +/00000001/panel_type edge-panel +set_key string /apps/panel/default_profiles/medium/panels +/00000001/panel_size panel-size-x-small +set_key string /apps/panel/default_profiles/medium/panels +/00000001/screen_edge panel-edge-bottom +set_key bool /apps/panel/default_profiles/medium/panels +/00000001/hide_buttons_enabled false +set_key string /apps/panel/default_profiles/medium/panels +/00000001/panel_background_type no-background + +# Define the first launcher +set_key string /apps/panel/default_profiles/medium/objects +/00000001/object_type launcher-object +set_key string /apps/panel/default_profiles/medium/objects +/00000001/launcher_location 'applications:///nautilus.desktop' +set_key string /apps/panel/default_profiles/medium/objects +/00000001/panel_id 00000001 +set_key int /apps/panel/default_profiles/medium/objects +/00000001/position 20 + +# Define the second launcher +set_key string /apps/panel/default_profiles/medium/objects +/00000002/object_type launcher-object +set_key string /apps/panel/default_profiles/medium/objects +/00000002/launcher_location 'applications:///System/gnome-terminal.desktop' +set_key string /apps/panel/default_profiles/medium/objects +/00000002/panel_id 00000001 +set_key int /apps/panel/default_profiles/medium/objects +/00000002/position 25 + +# Define the applet +set_key string /apps/panel/default_profiles/medium/applets +/00000001/object_type bonobo-applet +set_key string /apps/panel/default_profiles/medium/applets +/00000001/bonobo_iid OAFIID:GNOME_TasklistApplet +set_key string /apps/panel/default_profiles/medium/applets +/00000001/panel_id 00000001 +set_key int /apps/panel/default_profiles/medium/applets +/00000001/position 25</literallayout> + </sect3> + </sect2> + </sect1> + <sect1 id="gconf-9"> + <title>Setting Look-and-Feel Preferences</title> + <para>The following sections describe how to assign mandatory or default values +to look-and-feel preferences.</para> + <sect2 id="gconf-19"> + <title>To Set Font Preferences</title> + <indexterm> + <primary>GConf</primary> + <secondary>setting fonts</secondary> + </indexterm> + <para>To set font preferences, you modify the values of two preference keys. +The following table shows the keys to modify, and the part of the user interface +to which the keys correspond:</para> + <informaltable frame="topbot"> + <tgroup cols="2" colsep="0" rowsep="0"> + <colspec colwidth="50*"/> + <colspec colwidth="50*"/> + <thead> + <row rowsep="1"> + <entry valign="top"> + <para>GConf Location</para> + </entry> + <entry valign="top"> + <para>User Interface Component</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry valign="top"> + <para>/desktop/gnome/interface/font_name</para> + </entry> + <entry valign="top"> + <para><application>Font</application> preference tool, <guilabel>Application font</guilabel> section</para> + </entry> + </row> + <row> + <entry valign="top"> + <para>/apps/nautilus/preferences/desktop_font</para> + </entry> + <entry valign="top"> + <para><application>Font</application> preference tool, <guilabel>Desktop font</guilabel> section</para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para>For example, to set <literal>Sans 12</literal> as the mandatory application +font, run the following command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --direct --config-source +xml:readwrite:/etc/gconf/gconf.xml.mandatory --type string --set /desktop/gnome/interface/font_name “Sans +12”</userinput></para> + <para>To set <literal>palatino 12</literal> as the default desktop background +object font, run the following command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --direct --config-source +xml:readwrite:/etc/gconf/gconf.xml.defaults --type string --set /apps/nautilus/preferences/desktop_font “palatino +12”</userinput></para> + </sect2> + <sect2 id="gconf-20"> + <title>To Set Desktop Background Preferences</title> + <indexterm> + <primary>GConf</primary> + <secondary>setting desktop background</secondary> + </indexterm> + <para>To set desktop background preferences, you modify the values +of the preference keys in the <filename>/desktop/gnome/background</filename> +location. For example, to set a mandatory image for the desktop background, +run the following command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --direct --config-source +xml:readwrite:/etc/gconf/gconf.xml.mandatory --type string --set /desktop/gnome/background/picture_filename <replaceable>filename.png</replaceable></userinput></para> + <para>To set a default value for this preference, run the following command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --direct --config-source +xml:readwrite:/etc/gconf/gconf.xml.defaults --type string --set /desktop/gnome/background/picture_filename <replaceable>filename.png</replaceable></userinput></para> + <para>You can also set other desktop background preferences. For information +on the other desktop background preferences, see the <filename>desktop_gnome_background.schemas</filename> schema definition file.</para> + </sect2> + <sect2 id="gconf-21"> + <title>To Set Splash Image Preferences</title> + <indexterm> + <primary>GConf</primary> + <secondary>setting splash image</secondary> + </indexterm> + <para>To set splash image preferences, you modify the value of +the preference keys in the <filename>/apps/gnome-session/options/</filename> +location. For example, if you do not want users ever to see a splash image, +set a mandatory value as follows:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --direct --config-source +xml:readwrite:/etc/gconf/gconf.xml.mandatory --type bool --set /apps/gnome-session/options/show_splash_screen +false</userinput></para> + <para>To set a default value for this preference, run the following command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --direct --config-source +xml:readwrite:/etc/gconf/gconf.xml.defaults --type bool --set /apps/gnome-session/options/show_splash_screen +false</userinput></para> + <para>You can also set other splash image preferences. For information on +the other splash image preferences, see the <filename>gnome-session.schemas</filename> schema definition file.</para> + </sect2> + </sect1> + <sect1 id="gconf-28"> + <title>To Restore Default Preference Values</title> + <indexterm> + <primary>GConf</primary> + <secondary>restoring default preference +values</secondary> + </indexterm> + <para>To restore the default preference values +for a user, perform the following steps:</para> + <orderedlist> + <listitem> + <para>Log in as the user whose default preference values you want +to restore.</para> + </listitem> + <listitem> + <para>Run the following command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --recursive-unset</userinput></para> + <para>This command resets the values of all preference keys, in all subdirectories, +from the user setting to the setting in the default configuration source.</para> + </listitem> + <listitem> + <para>Log out from the user account.</para> + </listitem> + </orderedlist> + </sect1> +</chapter> + + diff --git a/gnome2-system-admin-guide/C/glossary.xml b/gnome2-system-admin-guide/C/glossary.xml new file mode 100644 index 0000000..98b5b9d --- /dev/null +++ b/gnome2-system-admin-guide/C/glossary.xml @@ -0,0 +1,113 @@ +<!-- converted from Solbook 2.2 SGML to Docbook 4.2 XML +# Generator: s2d v1.4 2002-09-19 +--> +<glossary id="glossary-1"> + <title>Glossary</title> + <glossentry id="glossary-13"> + <glossterm><filename>.desktop</filename> file</glossterm> + <glosssee otherterm="glossary-11"/> + </glossentry> + <glossentry id="glossary-14"> + <glossterm><filename>.directory</filename> file</glossterm> + <glosssee otherterm="glossary-12"/> + </glossentry> + <glossentry id="glossary-11"> + <glossterm>desktop entry file</glossterm> + <glossdef> + <para>A data file that provides information about an item in a menu. +The desktop entry file specifies details such as a name for the item, the +command for the item to run, an icon to represent the item, and so on. Desktop +entry files have a <filename>.desktop</filename> file extension.</para> + </glossdef> + </glossentry> + <glossentry id="glossary-12"> + <glossterm>directory entry file</glossterm> + <glossdef> + <para>A data file that provides information about a menu. The directory +entry file specifies details such as a name for the menu, a tooltip for the +menu, and an icon to represent the menu. Directory entry files have a <filename>.directory</filename> file extension.</para> + </glossdef> + </glossentry> + <glossentry id="glossary-5"> + <glossterm>GConf configuration source</glossterm> + <glossdef> + <para>A storage location in the <application>GConf</application> +repository. For example, <literal>xml:readonly:/etc/gconf/gconf.xml.defaults</literal>.</para> + </glossdef> + </glossentry> + <glossentry id="glossary-2"> + <glossterm>GConf preference key</glossterm> + <glossdef> + <para>An element in the <application>GConf</application> repository +that corresponds to an application preference. For example, the <literal>/apps/gnome-session/options/show_splash_screen</literal> key corresponds to +the <guilabel>Show splash screen on login</guilabel> option in the <application>Sessions</application> preference tool.</para> + </glossdef> + </glossentry> + <glossentry id="glossary-6"> + <glossterm>GConf path file</glossterm> + <glossdef> + <para>A file that lists the GConf configuration sources, and the +order in which to search the sources.</para> + </glossdef> + </glossentry> + <glossentry id="glossary-3"> + <glossterm>GConf schema</glossterm> + <glossdef> + <para>A collective term for a schema key and a schema object.</para> + </glossdef> + </glossentry> + <glossentry id="glossary-4"> + <glossterm>GConf schema definition file</glossterm> + <glossdef> + <para>A <application>GConf</application> schema definition file +lists the keys in a particular application, and defines the characteristics +of the keys. <application>GConf</application> schemas are generated from schema +definition files. Schema definition files have a <filename>.schemas</filename> +extension.</para> + </glossdef> + </glossentry> + <glossentry id="glossary-7"> + <glossterm>GConf schema key</glossterm> + <glossdef> + <para>A key that stores a schema object for a preference key. For +example, <literal>/schemas/desktop/gnome/interface/font_name</literal> is +a schema key for the <literal>/desktop/gnome/interface/font_name</literal> +preference key.</para> + </glossdef> + </glossentry> + <glossentry id="glossary-8"> + <glossterm>GConf schema object</glossterm> + <glossdef> + <para>An element in a configuration source that contains information +about a preference key. The schema object contains information such as a default +value for the preference key, and documentation on the preference key. </para> + </glossdef> + </glossentry> + <glossentry id="glossary-15"> + <glossterm>Uniform Resource Identifier</glossterm> + <glossdef> + <para>A Uniform Resource Identifier (URI) is a string that identifies +a particular location in a file system or on the Web. For example, the address +of a web page is a URI.</para> + </glossdef> + </glossentry> + <glossentry id="glossary-9"> + <glossterm>vfolder</glossterm> + <glossdef> + <para>A virtual representation of items that reside in a physical +location or physical locations on your system. For example, a vfolder might +represent the contents of several directories. In terms of menus, a vfolder +is a representation in a menu of items that might be physically located in +several directories.</para> + </glossdef> + </glossentry> + <glossentry id="glossary-10"> + <glossterm>vfolder information file</glossterm> + <glossdef> + <para>A description of a vfolder, in XML format. Vfolder information +files specify the structure of your menus.</para> + </glossdef> + </glossentry> +</glossary> + + diff --git a/gnome2-system-admin-guide/C/l10n-readme.txt b/gnome2-system-admin-guide/C/l10n-readme.txt new file mode 100644 index 0000000..80a7b29 --- /dev/null +++ b/gnome2-system-admin-guide/C/l10n-readme.txt @@ -0,0 +1 @@ +This is the first release of this Guide.
\ No newline at end of file diff --git a/gnome2-system-admin-guide/C/l10n-screenshots.txt b/gnome2-system-admin-guide/C/l10n-screenshots.txt new file mode 100755 index 0000000..6006851 --- /dev/null +++ b/gnome2-system-admin-guide/C/l10n-screenshots.txt @@ -0,0 +1 @@ +There are no screenshots in this manual.
\ No newline at end of file diff --git a/gnome2-system-admin-guide/C/legal.xml b/gnome2-system-admin-guide/C/legal.xml new file mode 100644 index 0000000..ac97e1d --- /dev/null +++ b/gnome2-system-admin-guide/C/legal.xml @@ -0,0 +1,76 @@ + <legalnotice id="legalnotice"> + <para> + Permission is granted to copy, distribute and/or modify this + document under the terms of the GNU Free Documentation + License (GFDL), Version 1.1 or any later version published + by the Free Software Foundation with no Invariant Sections, + no Front-Cover Texts, and no Back-Cover Texts. You can find + a copy of the GFDL at this <ulink type="help" + url="ghelp:fdl">link</ulink> or in the file COPYING-DOCS + distributed with this manual. + </para> + <para> This manual is part of a collection of GNOME manuals + distributed under the GFDL. If you want to distribute this + manual separately from the collection, you can do so by + adding a copy of the license to the manual, as described in + section 6 of the license. + </para> + + <para> + Many of the names used by companies to distinguish their + products and services are claimed as trademarks. Where those + names appear in any GNOME documentation, and the members of + the GNOME Documentation Project are made aware of those + trademarks, then the names are in capital letters or initial + capital letters. + </para> + + <para> + DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED + UNDER THE TERMS OF THE GNU FREE DOCUMENTATION LICENSE + WITH THE FURTHER UNDERSTANDING THAT: + + <orderedlist> + <listitem> + <para>DOCUMENT IS PROVIDED ON AN "AS IS" BASIS, + WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR + IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES + THAT THE DOCUMENT OR MODIFIED VERSION OF THE + DOCUMENT IS FREE OF DEFECTS MERCHANTABLE, FIT FOR + A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE + RISK AS TO THE QUALITY, ACCURACY, AND PERFORMANCE + OF THE DOCUMENT OR MODIFIED VERSION OF THE + DOCUMENT IS WITH YOU. SHOULD ANY DOCUMENT OR + MODIFIED VERSION PROVE DEFECTIVE IN ANY RESPECT, + YOU (NOT THE INITIAL WRITER, AUTHOR OR ANY + CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY + SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER + OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS + LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED + VERSION OF THE DOCUMENT IS AUTHORIZED HEREUNDER + EXCEPT UNDER THIS DISCLAIMER; AND + </para> + </listitem> + <listitem> + <para>UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL + THEORY, WHETHER IN TORT (INCLUDING NEGLIGENCE), + CONTRACT, OR OTHERWISE, SHALL THE AUTHOR, + INITIAL WRITER, ANY CONTRIBUTOR, OR ANY + DISTRIBUTOR OF THE DOCUMENT OR MODIFIED VERSION + OF THE DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH + PARTIES, BE LIABLE TO ANY PERSON FOR ANY + DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR + CONSEQUENTIAL DAMAGES OF ANY CHARACTER + INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS + OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR + MALFUNCTION, OR ANY AND ALL OTHER DAMAGES OR + LOSSES ARISING OUT OF OR RELATING TO USE OF THE + DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT, + EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF + THE POSSIBILITY OF SUCH DAMAGES. + </para> + </listitem> + </orderedlist> + </para> + </legalnotice> + diff --git a/gnome2-system-admin-guide/C/menustructure.xml b/gnome2-system-admin-guide/C/menustructure.xml new file mode 100644 index 0000000..9b64ff8 --- /dev/null +++ b/gnome2-system-admin-guide/C/menustructure.xml @@ -0,0 +1,736 @@ +<!-- converted from Solbook 2.2 SGML to Docbook 4.2 XML +# Generator: s2d v1.4 2002-09-19 +--> +<chapter id="menustructure-0"> + <title>Customizing Menus</title> + <highlights> + <para>The information in this chapter describes how GNOME implements +menus and how you can customize menus.</para> + </highlights> + <sect1 id="menustructure-1"> + <title>Introduction to Menus</title> + <indexterm> + <primary>menus</primary> + <secondary>introduction</secondary> + </indexterm> + <para>The way in which GNOME implements menus in the desktop enables you to +do the following:</para> + <itemizedlist> + <listitem> + <para>Customize the menu hierarchy easily. The menu hierarchy is +not based on the file system hierarchy. You can edit a small number of files +to customize the menu hierarchy. You do not need to modify your applications +or move files.</para> + </listitem> + <listitem> + <para>Install applications easily. You do not need to provide information +about the menu hierarchy to applications when you install the applications.</para> + </listitem> + <listitem> + <para>Configure menus so that users cannot modify the menus.</para> + </listitem> + </itemizedlist> + <para>Menus in the GNOME desktop use the following components:</para> + <itemizedlist> + <listitem> + <para>File abstraction layer</para> + </listitem> + <listitem> + <para>Vfolders</para> + </listitem> + <listitem> + <para>Desktop entry files</para> + </listitem> + <listitem> + <para>Directory entry files</para> + </listitem> + </itemizedlist> + </sect1> + <sect1 id="menustructure-22"> + <title>File Abstraction Layer</title> + <indexterm> + <primary>menus</primary> + <secondary>file abstraction layer</secondary> + </indexterm> + <indexterm> + <primary>file abstraction layer, and menus</primary> + </indexterm> + <para>The <literal>gnome-vfs</literal> file abstraction layer +provides a simplified and generalized way for applications to interact with +files. The file abstraction layer also provides <firstterm>Uniform Resource +Identifier</firstterm> (URI) locations that map to particular menu configuration +files. To add a menu or a menu item for all users, you must add the menu or +menu item to one of the URI locations. <xref linkend="menustructure-TBL-12"/> +lists the menus to which you can add items, and the URI locations that correspond +to the menus.</para> + <table frame="topbot" id="menustructure-TBL-12"> + <title>Menus and URI Locations</title> + <tgroup cols="2" colsep="0" rowsep="0"> + <colspec colwidth="50*"/> + <colspec colwidth="50*"/> + <thead> + <row rowsep="1"> + <entry valign="top"> + <para>Menu</para> + </entry> + <entry valign="top"> + <para>URI Locations</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry valign="top"> + <para><guimenu>Applications</guimenu> menu for all +users</para> + </entry> + <entry valign="top"> + <para> + <literal>applications-all-users:///</literal> + </para> + </entry> + </row> + <row> + <entry valign="top"> + <para><guimenu>Desktop Preferences</guimenu> menu +for all users</para> + </entry> + <entry valign="top"> + <para> + <literal>preferences-all-users:///</literal> + </para> + </entry> + </row> + </tbody> + </tgroup> + </table> + </sect1> + <sect1 id="menustructure-13"> + <title>Vfolders</title> + <indexterm> + <primary>menus</primary> + <secondary>vfolders</secondary> + </indexterm> + <indexterm> + <primary>vfolders</primary> + <see>menus, vfolders</see> + </indexterm> + <para>In general terms, a <firstterm>vfolder</firstterm> is a virtual representation +of items that reside in a physical location or physical locations on your +system. For example, a vfolder might represent the contents of several directories. +A vfolder is an abstraction from one or more physical locations. In terms +of menus in the GNOME desktop, a vfolder is a representation in a menu of +items that might be physically located in several directories. </para> + <indexterm> + <primary>menus</primary> + <secondary>vfolder information files</secondary> + </indexterm> + <para>A <firstterm>vfolder information file</firstterm> is an +XML file that describes a vfolder. Vfolder information files specify the structure +of your menus. Vfolder information files specify the names of your menus, +and the order in which applications appear in your menus. Vfolder information +files have a <filename>.vfolder-info</filename> file extension. </para> + <para>The following is an excerpt from a vfolder information file:</para> + <literallayout><?xml version="1.0"?> +<VFolderInfo> +. +. +. + <Folder> + <Name>Applications</Name> + <Desktop>Applications.directory</Desktop> + <Folder> + <Name>Accessories</Name> + <DontShowIfEmpty/> + <Desktop>Accessories.directory</Desktop> + <Query> + <And> + <Keyword>Application</Keyword> + <Keyword>Utility</Keyword> + </And> + </Query> + </Folder> +. +. +. + </Folder> +</VFolderInfo></literallayout> + <para><xref linkend="menustructure-TBL-17"/> describes some of the elements +in vfolder information files.</para> + <table frame="topbot" id="menustructure-TBL-17"> + <title>Vfolder Information File Elements</title> + <tgroup cols="2" colsep="0" rowsep="0"> + <colspec colname="colspec2" colwidth="33.83*"/> + <colspec colname="colspec3" colwidth="66.17*"/> + <thead> + <row rowsep="1"> + <entry valign="top"> + <para>Element</para> + </entry> + <entry valign="top"> + <para>Description</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry colname="colspec2" valign="top"> + <para> + <literal><Folder></literal> + </para> + </entry> + <entry colname="colspec3" valign="top"> + <para>Contains the elements that define +the name, content, and structure of the menu.</para> + </entry> + </row> + <row> + <entry colname="colspec2" valign="top"> + <para> + <literal><Name></literal> + </para> + </entry> + <entry colname="colspec3" valign="top"> + <para>The name of the menu.</para> + </entry> + </row> + <row> + <entry colname="colspec2" valign="top"> + <para> + <literal><Desktop></literal> + </para> + </entry> + <entry colname="colspec3" valign="top"> + <para>The name of the directory entry +file that specifies the name, comment, and icon for the menu.</para> + </entry> + </row> + <row> + <entry colname="colspec2" valign="top"> + <para> + <literal><Query></literal> + </para> + </entry> + <entry colname="colspec3" valign="top"> + <para>A query to run on desktop entry +files. If a desktop entry file matches the requirements in the query, the +menu item is displayed in the menu. </para> + <para>The query in the excerpt +searches for desktop entry files that contain the keywords <literal>Application</literal> and <literal>Utility</literal> in the <literal>Categories</literal> +key. Desktop entry files that match are displayed in the <guimenu>Applications</guimenu> menu.</para> + <para>This element is optional.</para> + </entry> + </row> + <row> + <entry colname="colspec2" valign="top"> + <para> + <literal><DontShowIfEmpty/></literal> + </para> + </entry> + <entry colname="colspec3" valign="top"> + <para>If this +element is present, the menu is not displayed if the menu does not contain +any items.</para> + <para>This element is optional.</para> + </entry> + </row> + </tbody> + </tgroup> + </table> + </sect1> + <sect1 id="menustructure-6"> + <title>Desktop Entry Files</title> + <indexterm> + <primary>menus</primary> + <secondary>desktop entry files</secondary> + </indexterm> + <indexterm> + <primary>desktop entry files</primary> + <see>menus, desktop +entry files</see> + </indexterm> + <indexterm> + <primary>.desktop files</primary> + <see>menus, desktop entry files</see> + </indexterm> + <para>A <firstterm>desktop +entry file</firstterm> is a data file that provides information about an item +in a menu. The desktop entry file specifies the details for the item such +as a name, a command to run, an icon, and so on. The desktop entry file also +contains keywords which determine the location of the item in the menu hierarchy. +Desktop entry files have a <filename>.desktop</filename> file extension.</para> + <para>The following is a sample desktop entry file:</para> + <literallayout>[Desktop Entry] +Encoding=UTF-8 +Name=Calculator +Comment=Perform simple calculations +Exec=gnome-calculator +Icon=gnome-calc3.png +Terminal=false +Type=Application +X-GNOME-DocPath=gnome-calculator/gnome-calculator.xml +Categories=GNOME;Application;Utility;</literallayout> + <para><xref linkend="menustructure-TBL-7"/> describes the most important keys +in desktop entry files.</para> + <table frame="topbot" id="menustructure-TBL-7"> + <title>Desktop Entry Keys</title> + <tgroup cols="2" colsep="0" rowsep="0"> + <colspec colname="colspec0" colwidth="25.25*"/> + <colspec colname="colspec1" colwidth="74.75*"/> + <thead> + <row rowsep="1"> + <entry valign="top"> + <para>Desktop Entry Key</para> + </entry> + <entry valign="top"> + <para>Description</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry valign="top"> + <para> + <literal>Encoding</literal> + </para> + </entry> + <entry valign="top"> + <para>Enter the encoding of the desktop entry file. </para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>Name</literal> + </para> + </entry> + <entry valign="top"> + <para>Enter the name of the item. This name is displayed on the +item in the menu. </para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>Comment</literal> + </para> + </entry> + <entry valign="top"> + <para>Enter a short description of the item. The comment is displayed +as a tooltip when you point to the item in the menu. </para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>Exec</literal> + </para> + </entry> + <entry valign="top"> + <para>Enter a command to execute when you choose the item from +the menu. </para> + </entry> + </row> + <row> + <entry colname="colspec0" valign="top"> + <para> + <literal>Icon</literal> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Enter a path to an icon that +represents the item.</para> + </entry> + </row> + <row> + <entry colname="colspec0" valign="top"> + <para> + <literal>Terminal</literal> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Enter <literal>true</literal> +if you want the command in the <literal>Exec</literal> key to run in a terminal +window. Enter <literal>true</literal> in this key if the command does not +create a window in which to run.</para> + </entry> + </row> + <row> + <entry colname="colspec0" valign="top"> + <para> + <literal>Type</literal> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Enter the type of item. Enter +one of the following: </para> + <itemizedlist> + <listitem> + <para><literal>Application</literal>: Enter this option for an +item that starts an application.</para> + </listitem> + <listitem> + <para><literal>Link</literal>: Enter this option for an item that +links to a file, folder, or FTP site.</para> + </listitem> + </itemizedlist> + </entry> + </row> + <row> + <entry colname="colspec0" valign="top"> + <para> + <literal>X-GNOME-DocPath</literal> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Enter +the help file to display when you choose <guimenuitem>Help on <replaceable>application_name</replaceable></guimenuitem> from the menu item popup menu.</para> + </entry> + </row> + <row> + <entry colname="colspec0" valign="top"> + <para> + <literal>Categories</literal> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Enter the keywords that describe +the item. Separate the keywords with semicolons (;). To see a list of the +standard category keywords, see the following URL: </para> + <literallayout> + <ulink url="http://www.freedesktop.org/standards/VFolderDesktops.txt">http://www.freedesktop.org/standards/VFolderDesktops.txt</ulink> + </literallayout> + <para>The vfolder information files map the keywords +that you enter to menus.</para> + </entry> + </row> + </tbody> + </tgroup> + </table> + <para>For more information on the keys in desktop entry files, see the following +URL: </para> + <literallayout> + <ulink url="http://www.freedesktop.org/standards/desktop-entry-spec/desktop-entry-spec.html">http://www.freedesktop.org/standards/desktop-entry-spec/desktop-entry-spec.html</ulink> + </literallayout> + <note> + <para>Panel launchers and desktop background objects also use desktop +entry files. The desktop entry files for launchers and desktop background +objects provide the same information as for items in a menu. For example, +the desktop entry files provide the command to run when a user chooses the +launcher or object.</para> + </note> + </sect1> + <sect1 id="menustructure-14"> + <title>Directory Entry Files</title> + <indexterm> + <primary>menus</primary> + <secondary>directory entry files</secondary> + </indexterm> + <indexterm> + <primary>directory entry files</primary> + <see>menus, +directory entry files</see> + </indexterm> + <indexterm> + <primary>.directory files</primary> + <see>menus, directory entry files</see> + </indexterm> + <para>A <firstterm>directory entry file</firstterm> is a data file that provides information +about a menu. The directory entry file specifies the details for the menu +such as a name, a tooltip, and an icon. Directory entry files have a <filename>.directory</filename> file extension.</para> + <para>The following is a sample directory entry file:</para> + <literallayout>[Desktop Entry] +Name=Accessories +Comment=Accessories menu +Icon=gnome-util.png +Type=Directory</literallayout> + <para><xref linkend="menustructure-TBL-15"/> describes the most important keys +in directory entry files.</para> + <table frame="topbot" id="menustructure-TBL-15"> + <title>Directory Entry Keys</title> + <tgroup cols="2" colsep="0" rowsep="0"> + <colspec colname="colspec0" colwidth="27.07*"/> + <colspec colname="colspec1" colwidth="72.93*"/> + <thead> + <row rowsep="1"> + <entry valign="top"> + <para>Directory Entry Key</para> + </entry> + <entry valign="top"> + <para>Description</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry colname="colspec0" valign="top"> + <para> + <literal>Name</literal> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Enter the name of the menu. This +name is displayed on the menu. </para> + </entry> + </row> + <row> + <entry colname="colspec0" valign="top"> + <para> + <literal>Comment</literal> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Enter a short description of +the menu. The comment is displayed as a tooltip when you point to the menu. </para> + </entry> + </row> + <row> + <entry colname="colspec0" valign="top"> + <para> + <literal>Icon</literal> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Enter a path to an icon that +represents the menu.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>Type</literal> + </para> + </entry> + <entry valign="top"> + <para>The type of menu. The value of this key is always <literal>Directory</literal>.</para> + </entry> + </row> + </tbody> + </tgroup> + </table> + </sect1> + <sect1 id="menustructure-2"> + <title>Editing Menus</title> + <indexterm> + <primary>menus</primary> + <secondary>editing</secondary> + </indexterm> + <para>You use the following desktop components to edit menus:</para> + <itemizedlist> + <listitem> + <para><application>Nautilus</application> file manager</para> + </listitem> + <listitem> + <para>Menus on panels</para> + </listitem> + </itemizedlist> + <para>When you use the file manager to add menus or menu items for all users, +you must add the menu or menu item to a URI location. <xref linkend="menustructure-TBL-12"/> +lists the menus to which you can add items, and the URI locations that correspond +to the menus.</para> + <para>When you use panels to customize menus for all users, you use the menu +item popup menu. For more information, see <citetitle>Working With Menus</citetitle> +in the <citetitle>GNOME 2.0 Desktop User Guide</citetitle>.</para> + <para>You can also use menu configuration files and menu data files to customize +menus.</para> + <sect2 id="menustructure-3"> + <title>Adding Menus</title> + <para>You can add menus for all users in the following ways: </para> + <itemizedlist> + <listitem> + <para>Use the file manager.</para> + </listitem> + <listitem> + <para>Modify the menu configuration files and menu data files.</para> + </listitem> + </itemizedlist> + <sect3 id="menustructure-19"> + <title>To Add a Menu Using the File Manager</title> + <indexterm> + <primary>menus</primary> + <secondary>adding using file manager</secondary> + </indexterm> + <para>To add a menu for all users, perform the following steps:</para> + <orderedlist> + <listitem> + <para>In a file manager window, access the location where you want +to add the menu. For example, to add a menu to the <guimenu>Applications</guimenu> +menu, type <literal>applications-all-users:///</literal> in the <guilabel>Location</guilabel> field, then press <keycap>Return</keycap>.</para> + </listitem> + <listitem> + <para>Choose <menuchoice><guimenu>File</guimenu><guimenuitem>New Folder</guimenuitem></menuchoice>. An untitled folder is added to the +view pane. The name of the folder is selected.</para> + </listitem> + <listitem> + <para>Type a name for the folder, then press <keycap>Return</keycap>. +The vfolder information file for the location that you accessed in step 1 +is automatically updated with the details of the new menu. The name of the +folder is displayed as the name of the menu.</para> + </listitem> + </orderedlist> + <note> + <para>You might need to reload the display of the file manager window +before you can type the name for the folder.</para> + </note> + <para>The next time that users log in, the menu is in the assigned location.</para> + </sect3> + <sect3 id="menustructure-20"> + <title>To Add a Menu Using Menu Files</title> + <indexterm> + <primary>menus</primary> + <secondary>adding using menu files</secondary> + </indexterm> + <para>To add a menu for all users, perform the following steps:</para> + <orderedlist> + <listitem> + <para>Create a directory entry file for the item that you want to +add. Create the directory entry file in the <filename>/usr/gnome/share/gnome/vfolders</filename> directory. For more information on directory entry files, see <xref linkend="menustructure-14"/>. </para> + </listitem> + <listitem> + <para>Locate the vfolder information file for the location where +you want to add the menu. For example, to add a menu to the <guimenu>Applications</guimenu> menu, locate the file <filename>/usr/gnome/etc/gnome-vfs-2.0/vfolders/applications-all-users.vfolder-info</filename>. </para> + </listitem> + <listitem> + <para>In the vfolder information file, add a <literal><Folder></literal> element for the new menu. For more information on vfolder information +files, see <xref linkend="menustructure-13"/>.</para> + </listitem> + </orderedlist> + <para>The next time that users log in, the menu is in the assigned location.</para> + </sect3> + </sect2> + <sect2 id="menustructure-4"> + <title>To Add an Item to a Menu</title> + <indexterm> + <primary>menus</primary> + <secondary>adding items to</secondary> + </indexterm> + <para>To add an item to a menu for all users, perform the following +steps:</para> + <orderedlist> + <listitem> + <para>Create a desktop entry file for the item that you want to +add. For more information on desktop entry files, see <xref linkend="menustructure-6"/>. </para> + </listitem> + <listitem> + <para>Open a file manager window. Choose <menuchoice><guimenu>File</guimenu><guimenuitem>New Window</guimenuitem></menuchoice> to open a second +file manager window.</para> + </listitem> + <listitem> + <para>In one window, access the location where you want to add the +menu item. For example, to add a menu item to the <guimenu>Preferences</guimenu> +menu, type <literal>preferences-all-users:///</literal> in the <guilabel>Location</guilabel> field, then press <keycap>Return</keycap>.</para> + </listitem> + <listitem> + <para>In the other window, select the desktop entry file that you +created for the menu item. Drag the desktop entry file to the location where +you want to add the menu item.</para> + <para>Alternatively, you can copy the desktop entry file, then paste the file +into the location where you want to add the menu item.</para> + </listitem> + </orderedlist> + <para>The next time that users log in, the menu item is in the assigned location.</para> + </sect2> + <sect2 id="menustructure-9"> + <title>To Edit the Properties of a Menu</title> + <indexterm> + <primary>menus</primary> + <secondary>editing properties of</secondary> + </indexterm> + <para>To edit the properties of a menu for all users, perform +the following steps:</para> + <orderedlist> + <listitem> + <para>From a panel, open the menu that you want to edit. Right-click +on any item in the menu.</para> + </listitem> + <listitem> + <para>Choose <menuchoice><guimenu>Entire menu</guimenu><guimenuitem>Properties</guimenuitem></menuchoice>. A <guilabel>Launcher Properties</guilabel> dialog is displayed.</para> + </listitem> + <listitem> + <para>Modify the properties of the menu in the <guilabel>Launcher Properties</guilabel> dialog. For more information on the elements in the <guilabel>Launcher Properties</guilabel> dialog, see <citetitle>Working With Panels</citetitle> in the <citetitle>GNOME 2.0 Desktop User Guide</citetitle>.</para> + </listitem> + <listitem> + <para>Click <guibutton>OK</guibutton>.</para> + </listitem> + </orderedlist> + </sect2> + <sect2 id="menustructure-10"> + <title>To Edit a Menu Item</title> + <indexterm> + <primary>menus</primary> + <secondary>editing menu items</secondary> + </indexterm> + <para>To edit a menu item, perform the following steps:</para> + <orderedlist> + <listitem> + <para>From a panel, open the menu that contains the item that you +want to edit. Right-click on the item that you want to edit.</para> + </listitem> + <listitem> + <para>Choose <guimenuitem>Properties</guimenuitem>. A <guilabel>Launcher Properties</guilabel> dialog is displayed.</para> + </listitem> + <listitem> + <para>Modify the properties of the menu item in the <guilabel>Launcher Properties</guilabel> dialog. For more information on the elements in the <guilabel>Launcher Properties</guilabel> dialog, see <citetitle>Working With Panels</citetitle> in the <citetitle>GNOME 2.0 Desktop User Guide</citetitle>.</para> + </listitem> + <listitem> + <para>Click <guibutton>OK</guibutton>.</para> + </listitem> + </orderedlist> + </sect2> + <sect2 id="menustructure-11"> + <title>To Delete an Item from a Menu</title> + <indexterm> + <primary>menus</primary> + <secondary>deleting menu items</secondary> + </indexterm> + <para>To delete an item from a menu, from a panel, open the menu +that contains the item that you want to delete. Right-click on the item that +you want to delete. Choose <guimenuitem>Remove this item</guimenuitem>. </para> + <para>The next time that users log in, the menu item is not displayed in the +menu.</para> + </sect2> + </sect1> + <sect1 id="menustructure-23"> + <title>To Configure Menus That Users Cannot Modify</title> + <indexterm> + <primary>menus</primary> + <secondary>configuring menus that users +cannot modify</secondary> + </indexterm> + <para>Users cannot modify a menu if the +following conditions are true:</para> + <itemizedlist> + <listitem> + <para>A vfolder information file that corresponds to the menu is +present in the <filename>/etc/gnome-vfs-2.0/vfolder</filename> directory.</para> + </listitem> + <listitem> + <para>The vfolder information file has the same name as the URI +location that corresponds to the menu.</para> + </listitem> + <listitem> + <para>The user permissions for the vfolder information file are +set to read only. </para> + </listitem> + </itemizedlist> + <para>To configure a menu so that users cannot modify the menu, perform the +following steps:</para> + <orderedlist> + <listitem> + <para>Create a vfolder information file for the menu that you want +to configure in the <filename>/etc/gnome-vfs-2.0/vfolder</filename> directory.</para> + </listitem> + <listitem> + <para>Give the vfolder information file the name of the URI location +that corresponds to the menu that you want to configure. For example, to configure +the <guimenu>Applications</guimenu> menu, create a vfolder information called <filename>applications.vfolder-info</filename> in the <filename>/etc/gnome-vfs-2.0/vfolder</filename> directory.</para> + </listitem> + <listitem> + <para>Set the permissions on the vfolder information +file to read only.</para> + </listitem> + </orderedlist> + </sect1> +</chapter> + + diff --git a/gnome2-system-admin-guide/C/system-admin-guide-C.omf b/gnome2-system-admin-guide/C/system-admin-guide-C.omf new file mode 100755 index 0000000..c67d152 --- /dev/null +++ b/gnome2-system-admin-guide/C/system-admin-guide-C.omf @@ -0,0 +1,37 @@ +<?xml version="1.0" encoding="UTF-8"?>
+<omf>
+ <resource>
+ <creator>
+ gdocteam@sun.com (Sun Microsystems)
+ </creator>
+ <maintainer>
+ gdocteam@sun.com (Sun Microsystems) + </maintainer>
+<!-- + <title>
+ GNOME 2.0 Desktop System Administration Guide + </title> +--> + <title>
+ System Administration Guide + </title>
+ <date>
+ 2002-12-12 + </date>
+ <version identifier="2.0" date="2002-12-12" + description="First draft"/>
+ <subject category="GNOME|Desktop"/>
+ <description>
+ System Administration Guide for GNOME 2.0.
+ </description>
+ <type>
+ administrator's guide
+ </type>
+ <format mime="text/xml" dtd="-//OASIS//DTD DocBook XML V4.1.2//EN"/>
+ <identifier url="system-admin-guide.xml"/>
+ <language code="C"/>
+ <relation seriesid="f3da2c14-0dec-11d7-9efe-da71520b9d3f"/>
+ <rights type="GNU FDL" license.version="1.1" + holder="Sun Microsystems"/>
+ </resource>
+</omf>
\ No newline at end of file diff --git a/gnome2-system-admin-guide/C/system-admin-guide.xml b/gnome2-system-admin-guide/C/system-admin-guide.xml new file mode 100644 index 0000000..12a36b6 --- /dev/null +++ b/gnome2-system-admin-guide/C/system-admin-guide.xml @@ -0,0 +1,64 @@ +<?xml version="1.0"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" +"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [ + <!ENTITY gnomeversion "2.0">
+ <!ENTITY manrevision "2.0">
+ <!ENTITY date "December 2002">
+ <!ENTITY LEGAL SYSTEM "legal.xml">
+ <!ENTITY gconf SYSTEM "gconf.xml">
+ <!ENTITY menustructure SYSTEM "menustructure.xml"> + <!ENTITY gloss SYSTEM "glossary.xml"> +]>
+<book id="index">
+ <title>GNOME &gnomeversion; Desktop System Administration Guide</title>
+ <bookinfo>
+ <copyright>
+ <year>2002</year>
+ <holder>Sun Microsystems</holder>
+ </copyright>
+
+<!-- translators: uncomment this:
+ <copyright>
+ <year>2002</year>
+ <holder>ME-THE-TRANSLATOR (Latin translation)</holder>
+ </copyright>
+-->
+ <publisher>
+ <publishername> GNOME Documentation Project </publishername>
+ </publisher> &LEGAL;
+
+ <authorgroup>
+ <author>
+ <firstname>Sun</firstname>
+ <surname>GNOME Documentation Team</surname>
+ <affiliation>
+ <orgname>Sun Microsystems</orgname>
+ <address><email>gdocteam@sun.com</email> </address>
+ </affiliation>
+ </author>
+ </authorgroup>
+
+ <revhistory>
+ <revision>
+ <revnumber>GNOME &gnomeversion; Desktop System Administration Guide V&manrevision;</revnumber>
+ <date>&date;</date>
+ <revdescription>
+ <para role="author">Sun Microsystems + <email>gdocteam@sun.com</email></para> + <para role="publisher">GNOME Documentation Project</para> + </revdescription> + </revision>
+ </revhistory>
+ <releaseinfo> This manual describes version &gnomeversion; of the GNOME desktop.
+ </releaseinfo>
+ <legalnotice>
+ <title>Feedback</title>
+ <para> To report a bug or make a suggestion regarding the GNOME desktop or this
+ manual, follow the directions in the <ulink url="ghelp:gnome-feedback" + type="help">GNOME Feedback Page</ulink>. </para>
+ </legalnotice>
+ </bookinfo> +&gconf;
+&menustructure; +&gloss; +
</book>
|