The previous values are edited by using gconftool 2. The following code disables 

the run_key:

gconftool 2   direct   config source 

xml:readwrite:/etc/gconf/gconf.xml.mandatory   type bool   set 

/apps/panel/global/run_key false

If the following command is issued to display all the global values, the change 

was made to the run key. It is now disabled for all users and they are unable to 

change it. This is because the gconf.xml.mandatory directory was used. If we 

used the gconf.xml.default directory, it would set a system default for all new 

users, but would be configurable by the users.

gconftool 2  R /apps/panel/global

screenshot_key = Print

panel_hide_delay = 500

enable_animations = true

drawer_autoclose = true

keep_menus_in_memory = true

window_screenshot_key = Print

panel_minimized_size = 3

tooltips_enabled = true

menu_key = F1

confirm_panel_remove = true

panel_animation_speed = panel speed medium

run_key = false

highlight_launchers_on_mouseover = true

enable_key_bindings = true

panel_show_delay = 300

While gconftool 2 is very useful for scripting there is of course also a graphical 

tool called gconf editor available. The gconf editor tool provides a graphical 

interface for managing the GNOME XML files. This tool lets you browse and 

modify GNOME settings. It is very useful for introducing you to the contents of 

the different XML schemas used to configure GNOME. 

5.2.3  Restricting the desktop

You can use the same method for the GNOME desktop icons. The only 

difference is the GNOME desktop directory structure. When a new user is 

created, their desktop structure is not created until they first log on. Again by 

manually creating this desktop structure, the default is not created.

mkdir /home/fiona/.gnome2

mkdir /home/fiona/.gnome2/Business Applications

The current directory structure for user Fiona is:

/home/fiona/.gnome2

 Chapter 5. Migration best practices 

107