Difference between pages "GNOME First Steps" and "Xfce"

(Difference between pages)
(gnome-light)
 
(Power Group)
 
Line 1: Line 1:
== What is GNOME? ==
+
== About Xfce ==
"GNOME 3 is an easy and elegant way to use your computer. It is designed to put you in control and bring freedom to everybody. GNOME 3 is developed by the GNOME community, a diverse, international group of contributors that is supported by an independent, non-profit foundation." [http://gnome.org GNOME]
+
  
== Prerequisites ==
+
''Xfce is a lightweight desktop environment for UNIX-like operating systems. It aims to be fast and low on system resources, while still being visually appealing and user friendly.
  
Before installing GNOME, ensure that the [[X Window System]] has been installed.
+
''Xfce embodies the traditional UNIX philosophy of modularity and re-usability. It consists of a number of components that provide the full functionality one can expect of a modern desktop environment. They are packaged separately and you can pick among the available packages to create the optimal personal working environment.
  
{{fancywarning|1=
+
''Another priority of Xfce is adhereance to standards, specifically those defined at [http://freedesktop.org/ freedesktop.org]. <ref>http://www.xfce.org/about/</ref>
Please note that Linux kernel 3.15.* may still have serious incompatibility with various graphics drivers. If you like to use <tt>gentoo-sources</tt> or <tt>vanilla-sources</tt>, please use a 3.14.* kernel. This is of particular importance if you plan to run GNOME, and want to use NVIDIA (commercial or nouveau) or ATI (ati-drivers) graphics drivers.}}
+
  
== Preparing to emerge ==
+
== Installation ==
  
To get your system ready to emerge gnome, it is recommended that you first set the gnome profile mix-in. To accomplish this, do the following:
+
Before emerging Xfce you need to:
<console>
+
##r### ##b## eselect profile list
+
##g##Currently available mix-ins profiles: 
+
  [11]  funtoo/1.0/linux-gnu/mix-ins/audio 
+
  [12]  funtoo/1.0/linux-gnu/mix-ins/console-extras 
+
  [13]  funtoo/1.0/linux-gnu/mix-ins/dvd 
+
  [14]  funtoo/1.0/linux-gnu/mix-ins/gnome 
+
  [15]  funtoo/1.0/linux-gnu/mix-ins/kde 
+
  [16]  funtoo/1.0/linux-gnu/mix-ins/mate 
+
  [17]  funtoo/1.0/linux-gnu/mix-ins/media 
+
  [18]  funtoo/1.0/linux-gnu/mix-ins/print 
+
  [19]  funtoo/1.0/linux-gnu/mix-ins/python3-only
+
  [20]  funtoo/1.0/linux-gnu/mix-ins/rhel5-compat
+
  [21]  funtoo/1.0/linux-gnu/mix-ins/server-db 
+
  [22]  funtoo/1.0/linux-gnu/mix-ins/server-mail
+
  [23]  funtoo/1.0/linux-gnu/mix-ins/server-web
+
  [24]  funtoo/1.0/linux-gnu/mix-ins/X
+
  [25]  funtoo/1.0/linux-gnu/mix-ins/xfce
+
  [26]  funtoo/1.0/linux-gnu/mix-ins/vmware-guest
+
  [27]  funtoo/1.0/linux-gnu/mix-ins/hardened
+
</console>
+
After seeing a list of available profiles, we want to add in the appropriate number for the gnome mix-in. To do this, run the following:
+
<console>
+
##r### ##b##eselect profile add 14
+
</console>
+
 
+
By enabling the gnome mix-in, various USE and other settings will be optimized to provide you with a pain-free GNOME installation experience.
+
 
+
== Emerging ==
+
 
+
You are provided with two packages that will pull in this desktop environment:
+
 
+
* ''gnome''
+
 
+
{{fancynote|This is the "whole shabang" - pulls in a range of applications made for the gnome desktop environment including a few games, an archive manager, a system monitor, a web browser, a terminal, etc.}}
+
 
+
* ''gnome-light''
+
 
+
{{fancynote|As the name implies, this pulls in the base minimal you need to get a functioning GNOME Desktop Environment.}}
+
 
+
=== GNOME 3.12 from a clean install ===
+
 
+
==== gnome ====
+
  
To emerge ''gnome'' run the following command
+
* Check that you have enabled the USE flags necessary for a XFCE desktop environment. [[Funtoo_Linux_First_Steps#Changing_profile|Set your profile to "xfce" via mix-ins]], as follows:
  
 
<console>
 
<console>
# ##i## emerge gnome
+
# ##i## eselect profile add funtoo/1.0/linux-gnu/mix-ins/xfce
 
</console>
 
</console>
  
==== gnome-light ====
+
* Verify that you have [[Funtoo_Linux_First_Steps#X.Org|X.Org Server]] configured properly.
  
To emerge ''gnome-light'' run the following command
+
We are now ready to install Xfce. Install the meta-package, which pulls in all of the components you need for a minimal Xfce installation:
  
 
<console>
 
<console>
# ##i## emerge gnome-light
+
# ##i##emerge xfce4-meta
 
</console>
 
</console>
  
=== Upgrading from GNOME 3.6 ===
+
== Running Xfce ==
  
==== gnome ====
+
There are several different ways to start Xfce:
  
To emerge ''gnome'', remove nautilus-open-terminal if it is installed as it now bundled into gnome-terminal
+
* Editing the <tt>.xinitrc</tt> file in your user's home directory and using <tt>startx</tt> from a text console.
 +
* Using a display manager (e.g. SLiM, GDM, and KDM).
 +
* Configuring your shell profile to automatically start Xfce upon a successful login.
  
<console>
+
=== .xinitrc ===
# ##i## emerge -C nautilus-open-terminal
+
</console>
+
  
Then, run the following command
+
The most common way to start the environment is to configure <tt>~/.xinitrc</tt> to launch an Xfce session. The proper way to launch Xfce from the terminal is by using <tt>startxfce4</tt> combined with <tt>ck-launch-session</tt>.
  
 
<console>
 
<console>
# ##i## emerge -vauDN world
+
$ ##i##echo "exec startxfce4 --with-ck-launch" > ~/.xinitrc
 
</console>
 
</console>
  
==== gnome-light ====
+
Note that <tt>--with-ck-launch</tt> (from ConsoleKit) is required by Xfce for important tasks such as shutting down, suspending, and automatically mounting removable storage media. Some applications will not work properly without it. Therefore we need to add ConsoleKit to the <tt>default</tt> runlevel, executing the following command as root:
 
+
To emerge ''gnome-light'' remove the following packages as there have been changes since 3.6 (you will have up reinstall any packages that have been renamed after gnome-light completes).
+
  
 
<console>
 
<console>
# ##i## emerge -C gnome-fallback gnome-panel gnome-screensaver metacity gnome-games gcalctool nautilus-open-terminal
+
# ##i##rc-update add consolekit default
 
</console>
 
</console>
  
Then, run the following command
+
Finally, to start the graphical environment, run <tt>startx</tt> from a login shell:
 
+
 
<console>
 
<console>
# ##i## emerge -vauDN world
+
$ ##i##startx
 
</console>
 
</console>
  
Finally, restore any applications that have been renamed (such as gcalctool => gnome-calculator)
+
== Display Manager ==
  
<console>
+
A display manager is a program that manages sessions and acts as a login screen. Here's a short list of a few of the display managers available in Funtoo:
# ##i## emerge gnome-calculator
+
</console>
+
 
+
== Subsystems ==
+
  
=== Bluetooth ===
+
* XDM (<tt>x11-apps/xdm</tt>): X.Org's standard display manager.
  
For bluetooth support, ensure that:
+
* LightDM (<tt>x11-misc/lightdm</tt>): A lightweight, but highly configurable display manager.
  
# Bluetooth support is enabled in your kernel (using modules is fine).
+
* SLiM (<tt>x11-misc/slim</tt>): Simple Login Manager -- a lightweight display manager. Not very configurable.
# Your bluetooth hardware is turned on.
+
# Add the <code>bluetooth</code> startup script to the default runlevel, and start it.
+
  
This can be done as follows:
+
Any of these would make a fine choice. After you've chosen which display manager to use, install it:
  
 
<console>
 
<console>
# ##i##rc-update add bluetooth default
+
# ##i##emerge lightdm
# ##i##rc
+
 
</console>
 
</console>
  
Once this is done, you should now be able to navigate to ''Settings'' -> ''Bluetooth'' and turn bluetooth on. The icon next to devices should now animate and you should be able to discover and add devices such as keyboards.
+
All that's left to do now is to add the name of the display manager to <tt>/etc/conf.d/xdm</tt>, add the <tt>xdm</tt> service to the <tt>default</tt> runlevel, and start the service:
  
=== Printing ===
+
<pre>
 
+
DISPLAYMANAGER="lightdm"
To enable printing support, add <code>cupsd</code> to the default runlevel:
+
</pre>
  
 
<console>
 
<console>
# ##i##rc-update add cupsd default
+
# ##i##rc-update add xdm default
# ##i##rc
+
# ##i##/etc/init.d/xdm start
 
</console>
 
</console>
  
You should now be able to navigate to ''Settings'' -> ''Printers'' and add printers to your system, and print.
+
==Power Group==
  
=== Scanning ===
+
If you wish to be able to shutdown/reboot/suspend/hibernate using xfce4-logout-session then you will need to add yourself or the user to the power group by:
 
+
To enable scanning support, add your user account to the <code>lp</code> group. This will allow your user to access the USB scanner.
+
 
+
Then, <code>emerge xsane</code>, and run it. It should be able to access your scanner.
+
 
+
== Finishing Touches ==
+
 
+
=== X ===
+
 
+
==== Setting up xdm (GUI log-in) ====
+
 
+
Typically, you will want to use <tt>gdm</tt>, the GNOME display manager, to log in to GNOME. This will allow you to log in graphically, rather than using the text console.
+
 
+
To enable gdm, edit <tt>/etc/conf.d/xdm</tt> and set <tt>DISPLAYMANAGER</tt> to <tt>gdm</tt> instead of <tt>xdm</tt>. Then, perform the following steps to add <tt>xdm</tt> to the default runlevel, and have it start automatically from now on when your system starts:
+
  
 
<console>
 
<console>
# ##i##rc-update add xdm default
+
# ##i##gpasswd -a <username> power
 
</console>
 
</console>
  
Then, if you want to start it now do
+
If the group does not exist then execute the following and try again:
  
 
<console>
 
<console>
# ##i##rc
+
# ##i##groupadd power
 
</console>
 
</console>
  
But you should reboot to avoid having an open login terminal
+
Now you need to add the following to /usr/share/polkit-1/actions/org.freedesktop.upower.policy:
  
==== Setting up xinitrc (text log-in) ====
+
{{file|lang=xml|name=/usr/share/polkit-1/actions/org.freedesktop.upower.policy|desc=|body=
 +
<?xml version="1.0" encoding="UTF-8"?>
 +
<!DOCTYPE policyconfig PUBLIC
 +
"-//freedesktop//DTD PolicyKit Policy Configuration 1.0//EN"
 +
"http://www.freedesktop.org/standards/PolicyKit/1.0/policyconfig.dtd">
 +
<policyconfig>
 +
  <vendor>The UPower Project</vendor>
 +
  <vendor_url>http://upower.freedesktop.org/</vendor_url>
 +
  <icon_name>system-suspend</icon_name>
  
Adding the following to your <tt>~/.xinitrc</tt> file is sufficient:
+
  <action id="org.freedesktop.upower.suspend">
 +
    <description>Suspend the system</description>
 +
    <description xml:lang="fr">Mettre le système en veille</description>
 +
    <description xml:lang="it">Sospende il sistema</description>
 +
    <description xml:lang="pl">Wstrzymanie systemu</description>
 +
    <description xml:lang="sv">Försätt systemet i vänteläge</description>
 +
    <message>Authentication is required to suspend the system</message>
 +
    <message xml:lang="fr">Vous devez vous identifier pour mettre le système en veille</message>
 +
    <message xml:lang="it">È richiesto autenticarsi per sospendere il sistema</message>
 +
    <message xml:lang="pl">Wymagane jest uwierzytelnienie, aby wstrzymać system</message>
 +
    <message xml:lang="sv">Autentisering krävs för att försätta systemet i vänteläge</message>
 +
    <defaults>
 +
      <allow_any>yes</allow_any>
 +
      <allow_inactive>no</allow_inactive>
 +
      <allow_active>yes</allow_active>
 +
    </defaults>
 +
  </action>
  
<pre>
+
  <action id="org.freedesktop.upower.hibernate">
# Fix Missing Applications in Gnome
+
    <description>Hibernate the system</description>
export XDG_MENU_PREFIX=gnome-
+
    <description xml:lang="fr">Mettre le système en hibernation</description>
 
+
    <description xml:lang="it">Iberna il sistema</description>
# Properly Launch the Desired X Session
+
    <description xml:lang="pl">Hibernacja systemu</description>
exec ck-launch-session gnome-session
+
    <description xml:lang="sv">Försätt systemet i viloläge</description>
</pre>
+
    <message>Authentication is required to hibernate the system</message>
 
+
    <message xml:lang="fr">Vous devez vous identifier pour mettre le système en hibernation</message>
Additionaly, if you need support for different input sources, there is no longer a need to configure ibus or scrim in your <tt>.xinitrc</tt> file as GNOME uses ibus natively. Simply configure it in the Control Center under Region & Langauge.
+
    <message xml:lang="it">È richiesto autenticarsi per ibernare il sistema</message>
 +
    <message xml:lang="pl">Wymagane jest uwierzytelnienie, aby zahibernować system</message>
 +
    <message xml:lang="sv">Autentisering krävs för att försätta systemet i viloläge</message>
 +
    <defaults>
 +
      <allow_any>yes</allow_any>
 +
      <allow_inactive>no</allow_inactive>
 +
      <allow_active>yes</allow_active>
 +
    </defaults>
 +
  </action>
  
=== Disable Adwaita Dark Theme ===
+
</policyconfig>
 +
}}
  
If you do not like the Adwaita Dark Theme it can be disabled by copying then modifying it like so:
+
and also add the following to /usr/share/polkit-1/actions/org.freedesktop.consolekit.policy:
  
 
<console>
 
<console>
mkdir -p ~/.themes/Adwaita-NoDark
+
<?xml version="1.0" encoding="UTF-8"?>
cp -r /usr/share/themes/Adwaita/gtk-* ~/.themes/Adwaita-NoDarkhttp://www.funtoo.org/Category:Ebuild_Category
+
<!DOCTYPE policyconfig PUBLIC
rm ~/.themes/Adwaita-NoDark/gtk-3.0/gtk-dark.css
+
"-//freedesktop//DTD PolicyKit Policy Configuration 1.0//EN"
ln -s gtk.css ~/.themes/Adwaita-NoDark/gtk-3.0/gtk-dark.css
+
"http://www.freedesktop.org/standards/PolicyKit/1.0/policyconfig.dtd">
</console>
+
  
Then, run gnome-tweak-tool and select select Theme -> GTK+ Theme -> Adwaita-NoDark.
+
<!--
 +
Policy definitions for ConsoleKit
 +
-->
  
{{fancynote|If you run GUI programs with the sudo command, then the above steps (excluding running gnome-tweak-tool) must be repeated for the root account.}}
+
<policyconfig>
  
[https://ask.fedoraproject.org/en/question/10304/how-do-i-ban-apps-from-using-gnome-3-adwaita-dark-theme/ Reference]
+
  <action id="org.freedesktop.consolekit.system.stop">
 +
    <description>Stop the system</description>
 +
    <message>System policy prevents stopping the system</message>
 +
    <defaults>
 +
      <allow_any>yes</allow_any>
 +
      <allow_inactive>no</allow_inactive>
 +
      <allow_active>yes</allow_active>
 +
    </defaults>
 +
  </action>
  
=== Verify the inode/directory MimeType Handler ===
+
  <action id="org.freedesktop.consolekit.system.stop-multiple-users">
 +
    <description>Stop the system when multiple users are logged in</description>
 +
    <message>System policy prevents stopping the system when other users are logged in</message>
 +
    <defaults>
 +
      <allow_any>yes</allow_any>
 +
      <allow_inactive>no</allow_inactive>
 +
      <allow_active>yes</allow_active>
 +
    </defaults>
 +
  </action>
  
In some odd instances, baobab might take priority over nautilus when handling the inode/directory MimeType. If this behavior is not desired, add the following to /home/~/.local/share/applications/mimeapps.list:
+
  <action id="org.freedesktop.consolekit.system.restart">
 +
    <description>Restart the system</description>
 +
    <message>System policy prevents restarting the system</message>
 +
    <defaults>
 +
      <allow_any>yes</allow_any>
 +
      <allow_inactive>no</allow_inactive>
 +
      <allow_active>yes</allow_active>
 +
    </defaults>
 +
  </action>
  
<pre>
+
  <action id="org.freedesktop.consolekit.system.restart-multiple-users">
[Added Associations]
+
    <description>Restart the system when multiple users are logged in</description>
inode/directory=nautilus.desktop;baobab.desktop;
+
    <message>System policy prevents restarting the system when other users are logged in</message>
</pre>
+
    <defaults>
 +
      <allow_any>yes</allow_any>
 +
      <allow_inactive>no</allow_inactive>
 +
      <allow_active>yes</allow_active>
 +
    </defaults>
 +
  </action>
  
=== Automatically Starting Applications at Login ===
+
</policyconfig>  
 
+
</console>
When using an old-fashioned <tt>.xinitrc</tt>, starting up applications when X starts is relatively easy. When using GDM, this can still be accomplished, by using the <tt>~/.xprofile</tt> file. Here's my sample <tt>.xprofile</tt> to start <tt>xflux</tt> to dim the screen at night:
+
 
+
<pre>
+
xflux -z 87107
+
</pre>
+
 
+
Remember to add a <tt>&</tt> at the end of any command that doesn't return to the shell prompt after running.
+
  
 
[[Category:Desktop]]
 
[[Category:Desktop]]
 
[[Category:First Steps]]
 
[[Category:First Steps]]
 
[[Category:Official Documentation]]
 
[[Category:Official Documentation]]

Revision as of 23:20, 18 September 2014

About Xfce

Xfce is a lightweight desktop environment for UNIX-like operating systems. It aims to be fast and low on system resources, while still being visually appealing and user friendly.

Xfce embodies the traditional UNIX philosophy of modularity and re-usability. It consists of a number of components that provide the full functionality one can expect of a modern desktop environment. They are packaged separately and you can pick among the available packages to create the optimal personal working environment.

Another priority of Xfce is adhereance to standards, specifically those defined at freedesktop.org. <ref>http://www.xfce.org/about/</ref>

Installation

Before emerging Xfce you need to:

#  eselect profile add funtoo/1.0/linux-gnu/mix-ins/xfce

We are now ready to install Xfce. Install the meta-package, which pulls in all of the components you need for a minimal Xfce installation:

# emerge xfce4-meta

Running Xfce

There are several different ways to start Xfce:

  • Editing the .xinitrc file in your user's home directory and using startx from a text console.
  • Using a display manager (e.g. SLiM, GDM, and KDM).
  • Configuring your shell profile to automatically start Xfce upon a successful login.

.xinitrc

The most common way to start the environment is to configure ~/.xinitrc to launch an Xfce session. The proper way to launch Xfce from the terminal is by using startxfce4 combined with ck-launch-session.

$ echo "exec startxfce4 --with-ck-launch" > ~/.xinitrc

Note that --with-ck-launch (from ConsoleKit) is required by Xfce for important tasks such as shutting down, suspending, and automatically mounting removable storage media. Some applications will not work properly without it. Therefore we need to add ConsoleKit to the default runlevel, executing the following command as root:

# rc-update add consolekit default

Finally, to start the graphical environment, run startx from a login shell:

$ startx

Display Manager

A display manager is a program that manages sessions and acts as a login screen. Here's a short list of a few of the display managers available in Funtoo:

  • XDM (x11-apps/xdm): X.Org's standard display manager.
  • LightDM (x11-misc/lightdm): A lightweight, but highly configurable display manager.
  • SLiM (x11-misc/slim): Simple Login Manager -- a lightweight display manager. Not very configurable.

Any of these would make a fine choice. After you've chosen which display manager to use, install it:

# emerge lightdm

All that's left to do now is to add the name of the display manager to /etc/conf.d/xdm, add the xdm service to the default runlevel, and start the service:

DISPLAYMANAGER="lightdm"
# rc-update add xdm default
# /etc/init.d/xdm start

Power Group

If you wish to be able to shutdown/reboot/suspend/hibernate using xfce4-logout-session then you will need to add yourself or the user to the power group by:

# gpasswd -a <username> power

If the group does not exist then execute the following and try again:

# groupadd power

Now you need to add the following to /usr/share/polkit-1/actions/org.freedesktop.upower.policy:

/usr/share/polkit-1/actions/org.freedesktop.upower.policy (xml source code)
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE policyconfig PUBLIC
 "-//freedesktop//DTD PolicyKit Policy Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/PolicyKit/1.0/policyconfig.dtd">
<policyconfig>
  <vendor>The UPower Project</vendor>
  <vendor_url>http://upower.freedesktop.org/</vendor_url>
  <icon_name>system-suspend</icon_name>
 
  <action id="org.freedesktop.upower.suspend">
    <description>Suspend the system</description>
    <description xml:lang="fr">Mettre le système en veille</description>
    <description xml:lang="it">Sospende il sistema</description>
    <description xml:lang="pl">Wstrzymanie systemu</description>
    <description xml:lang="sv">Försätt systemet i vänteläge</description>
    <message>Authentication is required to suspend the system</message>
    <message xml:lang="fr">Vous devez vous identifier pour mettre le système en veille</message>
    <message xml:lang="it">È richiesto autenticarsi per sospendere il sistema</message>
    <message xml:lang="pl">Wymagane jest uwierzytelnienie, aby wstrzymać system</message>
    <message xml:lang="sv">Autentisering krävs för att försätta systemet i vänteläge</message>
    <defaults>
      <allow_any>yes</allow_any>
      <allow_inactive>no</allow_inactive>
      <allow_active>yes</allow_active>
    </defaults>
  </action>
 
  <action id="org.freedesktop.upower.hibernate">
    <description>Hibernate the system</description>
    <description xml:lang="fr">Mettre le système en hibernation</description>
    <description xml:lang="it">Iberna il sistema</description>
    <description xml:lang="pl">Hibernacja systemu</description>
    <description xml:lang="sv">Försätt systemet i viloläge</description>
    <message>Authentication is required to hibernate the system</message>
    <message xml:lang="fr">Vous devez vous identifier pour mettre le système en hibernation</message>
    <message xml:lang="it">È richiesto autenticarsi per ibernare il sistema</message>
    <message xml:lang="pl">Wymagane jest uwierzytelnienie, aby zahibernować system</message>
    <message xml:lang="sv">Autentisering krävs för att försätta systemet i viloläge</message>
    <defaults>
      <allow_any>yes</allow_any>
      <allow_inactive>no</allow_inactive>
      <allow_active>yes</allow_active>
    </defaults>
  </action>
 
</policyconfig>

and also add the following to /usr/share/polkit-1/actions/org.freedesktop.consolekit.policy:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE policyconfig PUBLIC
 "-//freedesktop//DTD PolicyKit Policy Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/PolicyKit/1.0/policyconfig.dtd">

<!--
Policy definitions for ConsoleKit
-->

<policyconfig>

  <action id="org.freedesktop.consolekit.system.stop">
    <description>Stop the system</description>
    <message>System policy prevents stopping the system</message>
    <defaults>
      <allow_any>yes</allow_any>
      <allow_inactive>no</allow_inactive>
      <allow_active>yes</allow_active>
    </defaults>
  </action>

  <action id="org.freedesktop.consolekit.system.stop-multiple-users">
    <description>Stop the system when multiple users are logged in</description>
    <message>System policy prevents stopping the system when other users are logged in</message>
    <defaults>
      <allow_any>yes</allow_any>
      <allow_inactive>no</allow_inactive>
      <allow_active>yes</allow_active>
    </defaults>
  </action>

  <action id="org.freedesktop.consolekit.system.restart">
    <description>Restart the system</description>
    <message>System policy prevents restarting the system</message>
    <defaults>
      <allow_any>yes</allow_any>
      <allow_inactive>no</allow_inactive>
      <allow_active>yes</allow_active>
    </defaults>
  </action>

  <action id="org.freedesktop.consolekit.system.restart-multiple-users">
    <description>Restart the system when multiple users are logged in</description>
    <message>System policy prevents restarting the system when other users are logged in</message>
    <defaults>
      <allow_any>yes</allow_any>
      <allow_inactive>no</allow_inactive>
      <allow_active>yes</allow_active>
    </defaults>
  </action>

</policyconfig>