<appendix id = "installation">
<!-- **********************************************************************
                               installation.sgml
                            +++++++++++++++++++++++
  copyright            : (C) 2000, 2001, 2002, 2003, 2004
                          Rafi Yanai, Shie Erlich, Frank Schoolmeesters
                          & the Krusader Krew
  e-mail               : krusader@users.sourceforge.net
  web site             : http://krusader.sourceforge.net
  description          : a Krusader Documentation File

***************************************************************************
* Permission is granted to copy, distribute and/or modify this            *
* document under the terms of the GNU Free Documentation License,         *
* 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.  A copy of the license is available on the         *
* GNU site http://www.gnu.org/licenses/fdl.html or by writing to:         *
* Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston,    *
* MA 02111-1307, USA.                                                     *
*********************************************************************** -->
<title>Installation</title>

<sect1 id = "getting-krusader">
<title>How to obtain &krusader;</title>

<sect2 id="krusader_stable">
<title>Stable version</title>
<para><filename>krusader-x.xx.tar.gz</filename></para>
<note><para>&krusader; is released under the
      <link linkend="credits">GNU General Public License (GPL)</link>, this means that
      THE PROGRAM IS PROVIDED "AS IS" WITH NO WARRANTY OF ANY KIND,
      even when it is marked as a stable release.</para></note>

<para>
  The latest stable version can be found on the &krudownload_url;.
  It contains the source tarballs and RPM packages to whatever distro we are currently
  using. There might be some other packages on the site, but that depends on
  other users contributions.</para>

<para>You may also find copies on &Linux; software archives such as
   &freshmeat_url; or &kde_apps_url;.
   If you can't find a RPM package for your &Linux; distribution,
   we recommend searching for it with &rpmfind_url; or &rpmpbone_url;.</para>

<para>A &krufreebsd_port_url; of &krusader; is maintained, the <guibutton>"Search"</guibutton> button will
      lead you to the latest BSD version.
       Many thanks to <link linkend="credits">Heiner Eichmann</link> !</para>

<para>If you can't find a RPM package, don't wurry.
      We provide a verry detailled installation procedure. This will allow that even newcomers will be able
      to compile &krusader; from source, even when you dit never before a compilation from source.
      Please continue reading this chapter.</para>

</sect2>


<sect2 id="krusader_devel">
<title>Development version (beta release)</title>
<para><filename>krusader-x.xx-betax.tar.gz</filename></para>
<para>
  The latest development version can be found on the &krudownload_url;.
  It contains the source tarballs and sometimes even RPM packages to whatever distro we are currently
  using. Before every stable release we release at least one development version, so that we can hunt down
  the bugs.</para>

<warning><para>This releases are beta releases and will probably contain some bugs.</para></warning>

<para>This version has 3 goals:
  <itemizedlist>
	<listitem>
	   <para>Apply a feature-freeze until the stable is released, only bugs will be fixed.
	         New features have to wait until the stable is released.</para>
	</listitem>
	<listitem>
	   <para>Have feedback from &krusader; users so that we can fix the bugs.</para>
	</listitem>
	<listitem>
	   <para>Give translators the time to update the translations, for the comming stable.
	         Please read the &i18nhowto_url;</para>
	</listitem>
  </itemizedlist>
</para>

</sect2>


<sect2 id="krusader_cvs">
<title>CVS builds</title>
<para><filename>krusader-cvs-yyyy-mm-dd.tar.gz</filename></para>

<warning><para>These builds are untested and come without any warranty.
               They may contain bugfixes, new features or new bugs!</para></warning>

<para>
  We provide daily builds of &krusader;'s CVS version.
  For those who are interested. The <emphasis role="bold">nightly tarball</emphasis> can be found on the
  &krucutedge_url;.
  Depending on the development progress this version will either be stable or unstable. Just before a stable release, the CVS version
  is almost stable. After a stable release new features will be added in CVS, which might lead to
  some unfortunate bugs. In some rare cases the build will even not compile if we make a mistake, in that case
  we try to fix the mistake as soon as possible.</para>

<para>&krusader; provides 2 nightly builds (snapshots):
  <orderedlist numeration="arabic">
	<listitem>
	   <para><filename>krusader-cvs-yyyy-mm-dd.tar.gz</filename>: <command>make -f Makefile.cvs</command> must be run before the <command>./configure</command>
	    script is available</para>
	</listitem>
	<listitem>
	   <para><filename>krusader-cvs2-yyyy-mm-dd.tar.gz</filename>: for users who have problems with the <command>make -f Makefile.cvs</command> command,
	   we have already done this for you and the <command>./configure</command> script is included
	   in the tarball (This tarball is a bit bigger then the first one).
           </para>
	</listitem>
  </orderedlist>
</para>

<para><emphasis role="bold">Checkout from CVS</emphasis>.
  &krusader; can be checked out through anonymous (pserver) CVS with the following instruction set.
  The module you wish to check out must be specified as the modulename.
  When prompted for a password for anonymous, simply press the Enter key.</para>
  <para>Currently there are two module options:
  <itemizedlist>
  <listitem><para>krusader_kde2: the KDE2 branch, stable but it's basically v1.01 and there are no
                  planned changes</para></listitem>
  <listitem><para>krusader_kde3: the KDE3 branch, that we currently use</para></listitem>
  </itemizedlist></para>

<para>To checkout &krusader; from CVS:
  <screen><prompt>$</prompt> <userinput><command>cvs</command> <option>-d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/krusader login</option></userinput></screen>
  <screen><prompt>$</prompt> <userinput><command>cvs</command> <option>-z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/krusader co krusader_kde3</option></userinput></screen>
  (note: updates from within the modules directory do not need the -d parameter)</para>

<para>We provide also &viewcvs_url; to browse the CVS repository.</para>

</sect2>


<sect2 id="krusader_old">
<title>Older releases</title>
<para>Looking for older releases? Try the &sfmirrors_url; available from our project page.</para>
</sect2>

</sect1>


<sect1 id="requirements">
<title>Requirements</title>

<para>In order to successfully use &krusader;, you need &kde; 3.x.x.</para>

<para><remark>For &kde; 2.x.x there is &krusader; v1.01, stable but there are no planned changes.</remark></para>

<para>Note: all &krusader; versions >=1.02 are &kde; 3.x.x only.</para>

<para>A FreeBSD port of &krusader; is available.</para>

<para>&krusader; uses about 3-4 MByte of memory to run 
      (and about 15 Mbyte shared memory which is also used by more processes), 
      but this may vary depending on your platform and configuration.
      In order to handle archives the archivers must be configured <link linkend="konfig-dependencies">here</link>.</para>

<para>A package of popular (un)packers, &krusader; itself and addons can be found on the &krudownload_url;.</para>

<para>
    You can find a list of changes in the &online_changelog_url; file or in the <filename>ChangeLog</filename>
    file of the &krusader; sources.</para>

</sect1>



<sect1 id="compilation">
<title>Compilation and installation</title>

<sect2 id="sourcedownload">
<title>I have downloaded the sources for &krusader;. What now?</title>

<para>Check the environment variables &kdeqtdir_lnk;.</para>

<para>In order to compile and install &krusader; on your system, type the
      following in the base directory of the &krusader; package:</para>

<screen><prompt>$</prompt> <userinput><command>./configure</command></userinput>
<prompt>$</prompt> <userinput><command>make</command></userinput>
<prompt>$</prompt> <userinput><command>su -c 'make</command> <option>install'</option></userinput></screen>

&krusaderui_rc_text;

<para>Since &krusader; uses <command>autoconf</command> and
     <command>automake</command> you should have no trouble compiling it.
     Should you run into problems please read the detailed installation instructions below.</para>

</sect2>


<sect2 id="detailinstall">
<title>Detailed installation instructions</title>

<para>The next section will explain step by step in detail how to install &krusader;.
      This question has been asked many times and especially users new to &Linux; often have
      problems compiling software from source. Therefore we are trying to keep the explanations as
      detailed as possible even if they are mostly not &krusader; specific.
      Experienced users may easily skip most of the steps.</para>

<para>If you encounter problems installing &krusader;, please read this installation procedure first
      and then the &faq_lnk;, if this does not solve the problem then
      feel free to ask for help with an &help_request_lnk;.</para>

<orderedlist>
<listitem>
   <para>Open your favourite terminal emulator (&eg; &konsole;).</para>
   <para> </para> <!-- Empty line to make it more readable -->
</listitem>


<listitem>
<para>We recommend to create a separate directory to keep all the sources you compile in.
      This will give you a better overview of installed programs and makes it easier to uninstall them later.
      <screen><prompt>$</prompt> <userinput><command>mkdir</command> ~/source</userinput></screen>
      The chosen directory is just an example, any other will work.</para>
     <para> </para> <!-- Empty line to make it more readable -->
     <para> </para> <!-- Empty line to make it more readable (second line is needed) -->
</listitem>


<listitem>
  <para>Copy the sources to the <filename>~/source</filename> directory and unpack them.
  <screen><prompt>$</prompt> <userinput><command>cp</command> /<replaceable>"your_dir"</replaceable>/krusader-x.xx.tar.gz ~/source</userinput></screen>
  <screen><prompt>$</prompt> <userinput><command>cd</command> ~/source</userinput></screen>
  <screen><prompt>$</prompt> <userinput><command>tar</command> <option>-xzvf</option> krusader-x.xx.tar.gz</userinput></screen></para>
  <para> </para> <!-- Empty line to make it more readable -->
</listitem>


<listitem>
<para>Optional step: the tarball is no longer needed at this point, you can delete it if you want.
      <screen><prompt>$</prompt> <userinput><command>rm</command>  krusader-x.xx.tar.gz</userinput></screen></para>
      <para> </para> <!-- Empty line to make it more readable -->
</listitem>


<listitem>
 <para>Change to the directory containing the sources.
 <screen><prompt>$</prompt> <userinput><command>cd</command>  krusader-x.xx</userinput></screen></para>
 <para> </para> <!-- Empty line to make it more readable -->
</listitem>


<listitem id="kde_qt_dir">
<para>Check the environment variables <envar>QTDIR</envar> and <envar>KDEDIR</envar>.
      &krusader;'s <command>./configure</command> script needs to know where the &Qt; and &kde; directories are.
      </para>

<para><envar>QTDIR</envar>  : <replaceable>&lt;path to your Qt installation&gt;</replaceable>
&eg; <filename>/usr/lib/qt3</filename> or <filename>/usr/qt3</filename></para>

<para><envar>KDEDIR</envar> : <replaceable>&lt;path to your KDE installation&gt;</replaceable>
&eg; <filename>/usr</filename> or <filename>/opt/kde3</filename></para>

<para>Normally your distribution will set them for you, but experience has shown that some don't.
       You can easily check the values with the <command>echo</command> command.
<screen><prompt>$</prompt> <userinput><command>echo</command> $QTDIR</userinput>
/usr/lib/qt3
<prompt>$</prompt> <userinput><command>echo</command> $KDEDIR</userinput>
/usr</screen>

  If both commands give an output, the enviroment variables are set (the above example are the settings of Mandrake).
  In case you just receive empty lines, the variables are not set and you have to set them it manually.
  If you have no idea what to set the variables to, or if you want to check if the variables are right set,
  ask your distributor or use the <command>find</command> command.

<informalexample>
<screen><prompt>$</prompt> <userinput><command>find</command> <option>/usr /opt -name</option> qtconfig <option>-type f -perm +111</option></userinput>
/usr/lib/qt3/bin/qtconfig
<prompt>$</prompt> <userinput><command>find </command> <option>/usr /opt -name</option> startkde <option>-type f -perm +111</option></userinput>
/usr/bin/startkde</screen>
</informalexample>

In this case <filename>/usr/lib/qt3</filename> is your <envar>QTDIR</envar> and  <filename>/usr</filename> is your <envar>KDEDIR</envar>. The installed binaries will go to <filename>/usr/bin</filename>.
Now we will set the enviroment variables with the <command>export</command> command.

<screen><prompt>$</prompt> <userinput><command>export</command> QTDIR=<replaceable>&lt;replace with your QTDIR&gt;</replaceable></userinput></screen>
<screen><prompt>$</prompt> <userinput><command>export</command> KDEDIR=<replaceable>&lt;replace with your KDEDIR&gt;</replaceable></userinput></screen>
  </para>

  <note><para>These enviroment variables are only set for the lifetime of your current shell.
              if you close your terminal and open a new one they will be gone.
              Assuming &krusader; is not the only &Qt;/&kde; program you want to compile, we recommend to make these
              settings permanent (&eg; append both export commands to your
              <filename class="directory">/etc/profile</filename>) file.</para></note>

   <para> </para> <!-- Empty line to make it more readable -->
   <para> </para> <!-- Empty line to make it more readable (second line is needed) -->

</listitem>



<listitem>
  <para>If you have downloaded a stable version <filename>"krusader-x.xx.tar.gz"</filename>
        or a beta version <filename>"krusader-x.xx-betax.tar.gz"</filename>,
	you can skip this step, in this case the <filename>./configure</filename> script is provided.</para>

  <para>If you have downloaded a CVS build or nightly tarball <filename>"krusader-cvs-yyyy-mm-dd.tar.gz"</filename>",
        you will have to run the following command to create the <filename>./configure</filename> script:
        <screen><prompt>$</prompt> <userinput><command>make</command> <option>-f</option>  Makefile.cvs</userinput></screen></para>

  <para>If everything is ok you will see the following output on your screen:
<informalexample>
<screen><prompt>$</prompt> <userinput><command>make</command> <option>-f</option>  Makefile.cvs</userinput>
This Makefile is only for the CVS repository
This will be deleted before making the distribution
*** Creating acinclude.m4
*** Creating list of subdirectories
*** Creating configure.in
*** Creating aclocal.m4
*** Creating configure
*** Creating config.h template
*** Creating Makefile templates
*** Postprocessing Makefile templates
*** Creating date/time stamp
*** Finished
Don't forget to run ./configure
If you haven't done so in a while, run ./configure --help
<prompt>$</prompt></screen>
</informalexample>
</para>

   <note><para>You will need to have: <application>autoconf 2.52, 2.53 or 2.54</application> and
         <application>automake 1.6</application> (or higher) to run the <command>make -f Makefile.cvs</command>
         command</para></note>

   <tip><para>If you encounter problems with this command click
              <link linkend="krusader_cvs">here</link>. &krusader; provides 2 nightly builds (snapshots)
              one with a <filename>./configure</filename> script and one without.</para></tip>

   <para> </para> <!-- Empty line to make it more readable -->
   <para> </para> <!-- Empty line to make it more readable (second line is needed) -->
</listitem>


<listitem>
  <para>Now you are ready to run the <command>./configure</command> script.
       <screen><prompt>$</prompt> <userinput><command>./configure</command></userinput></screen></para>

  <para>This will take about 1 minute, if everything goes well it will &eg; end with the following messages:
        </para>

<para>
<informalexample>
<screen>
foo

Krusader Project:
-----------------
Source code location: .
C Compiler:           gcc
C Compiler flags:     -ansi -W -Wall -pedantic -Wchar-subscripts -Wshadow -Wpointer-arith
-Wmissing-prototypes -Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -O2
-Wformat-security -Wmissing-format-attribute
C++ Compiler:         g++
prefix:               /usr
kde_libraries:        /usr/include
kde_includes:         /usr/lib
kde_locale:           /usr/share/locale
qt_libraries:         /usr/lib/qt3/lib
qt_includes:          /usr/lib/qt3/include
KDEDIR:               /usr
QTDIR:                /usr/lib/qt3
Install path:         /usr/bin
krusader version:     1.30
krusader binary:      /usr/bin/krusader     (after 'make install')
Thank you for using Krusader

Good - your configure finished. Start make now
<prompt>bash$</prompt>
</screen>
</informalexample>
</para>

<para>This is the output for Mandrake 9.1, other distributions may give a different output.</para>

<tip><para>At the end of the <command>./configure</command> script you will find a summary of the most
           important settings, &eg; where the &krusader; binary will be installed (after the
           'make install' command).</para>
     <para>Usually the &krusader; binary will be installed in the <filename>KDEDIR/bin</filename>
           directory.
           If you would prefer to install &krusader; in a different directory, you can do this with the following
           command: <userinput><command>./configure</command>
           <option> --prefix=<replaceable>/usr/local</replaceable></option></userinput>.
           In this case the &krusader; binary will be installed in the
           <filename>/usr/local/bin</filename> directory.</para>
     <para>This part will also display a warning if the environment variables &kdeqtdir_lnk; are empty.</para>
</tip>

  <para> </para> <!-- Empty line to make it more readable -->
  <para>Use <userinput><command>./configure</command> <option>--help</option></userinput>
	to see more options or read the <filename>INSTALL</filename> file in the &krusader; sources.</para>

  <para>If <command>./configure</command> fails, take a look at &missing_libs_lnk;.</para>

  <para> </para> <!-- Empty line to make it more readable -->
</listitem>



<listitem>
  <para>Start the compilation process with the <command>make</command> command.
        <screen><prompt>$</prompt> <userinput><command>make</command></userinput></screen>
        This will take about 5 minutes, if everything goes well it will &eg; end with the following messages:

<informalexample>
<screen>
foo
make[2]: Leaving directory `/foo/krusader-cvs-YYYY-MM-DD/krArc'
make[2]: Entering directory `/foo/krusader-cvs-YYYY-MM-DD'
make[2]: Nothing to be done for `all-am'.
make[2]: Leaving directory `/foo/krusader-cvs-YYYY-MM-DD'
make[1]: Leaving directory `/foo/krusader-cvs-YYYY-MM-DD'
<prompt>bash$</prompt>
</screen>
</informalexample>
</para>

  <para> </para> <!-- Empty line to make it more readable -->

  <para>If <command>./configure</command> was successful and <command>make</command> failed for some
	reason, continue to read this page. If you can't find any solution for your problem then feel free
        to post a help request at our &forum_lnk;.</para>

  <para> </para> <!-- Empty line to make it more readable -->
</listitem>


<listitem>
 <para>If nothing went wrong, you can now install &krusader;.

   <screen><prompt>$</prompt> <userinput><command>su -c 'make</command> <option>install'</option></userinput>
   </screen> You will be asked to enter your root password.</para>

  <para> </para> <!-- Empty line to make it more readable -->
  <para> </para> <!-- Empty line to make it more readable (second line is needed) -->
</listitem>


<listitem>
  &krusaderui_rc_text;
  <para></para> <!-- Empty line to make it more readable -->
</listitem>

<listitem>
  <para>Now you can <link linkend="starting-krusader">start</link> &krusader;.</para>
  <para></para> <!-- Empty line to make it more readable -->
</listitem>



<listitem>
 <para>Optional step: if you want you can clean up to save some diskspace.
       Note: in this case all the compiled files created with the <command>make</command> command will be deleted.
       <screen><prompt>$</prompt> <userinput><command>make</command> <option>clean</option></userinput></screen>
       </para>

  <para> </para> <!-- Empty line to make it more readable -->
  <para> </para> <!-- Empty line to make it more readable (second line is needed) -->
</listitem>


<listitem>
  <para>If you ever want to uninstall &krusader;, just use
  <screen><prompt>$</prompt> <userinput><command>su -c 'make</command> <option>uninstall'</option></userinput>
  </screen>
  You will be asked to enter your root password.</para>

  <para></para> <!-- Empty line to make it more readable -->
</listitem>

</orderedlist>


<para>If you encounter problems with installing &krusader; please read first the &faq_lnk;.
      If this installation procedure and the FAQ does not solve the problem,
      feel free to ask for help with an &help_request_lnk;.</para>

</sect2>


</sect1>




<sect1 id="starting-krusader">
<title>Starting &krusader;</title>

<para>Type <userinput><command>krusader</command></userinput> at a command prompt.
      You can create shortcut on your desktop or create an entry in the (&kde;) menu.
      Read the previous page and the &faq_lnk; if &krusader; doesn't start.</para>

<para>When &krusader; is started from the command-line, various options can be specified to modify
      its behavior.</para>

<informalexample>
<screen><prompt>$</prompt> <userinput><command>krusader</command></userinput>
WARNING: Mt.Man: Born, looking around to get familiar.
foo</screen>
</informalexample>


<note><para>Don't worry about the messages you get in the &konsole;. These messages are log messages,
      they can be used for debugging &krusader;.</para></note>

<para>If &krusader; is installed by an RPM (and if the packager dit use the <filename>krusader.spec</filename> file that
      we provide), than &krusader; can be started at <emphasis role="bold"><menuchoice><guimenu>KDE menu</guimenu>
      <guimenuitem>Applications</guimenuitem><guimenuitem>File tools</guimenuitem>
      <guimenuitem>&krusader;</guimenuitem></menuchoice></emphasis>.</para>

<para><option>--left</option>
     <replaceable>&lt;path&gt;</replaceable> start left panel at
     <replaceable>&lt;path&gt;</replaceable></para>

<para><option>--right</option>
      <replaceable>&lt;path&gt;</replaceable> start right panel at
      <replaceable>&lt;path&gt;</replaceable></para>

<para>Example:
<screen><prompt>$</prompt> <userinput><command>krusader</command> <replaceable>--left=/mnt/cdrom --right=ftp://downloads@myserver.net</replaceable></userinput></screen>
</para>

<para>The standard &Qt; and &kde; command-line options are available, and can be listed by entering
      <userinput><command>krusader</command> <option>--help</option></userinput> .</para>

<variablelist><title>Other command-line options:</title>
	<varlistentry>
		<term><option>--help-qt</option></term>
		<listitem><para><action>List Qt-specific options</action></para></listitem>
	</varlistentry>
	<varlistentry>
		<term><option>--help-kde</option></term>
		<listitem><para><action>List KDE-specific options</action></para></listitem>
	</varlistentry>
	<varlistentry>
		<term><option>--help-all</option></term>
		<listitem><para><action>List all options</action></para></listitem>
	</varlistentry>
	<varlistentry>
		<term><option>--author</option></term>
		<listitem><para><action>Show the authors names</action></para>
		          <para>NOTE: If you wish to send &faqbugreports_lnk;,
		                 please do not use &kde;'s bugzilla.</para></listitem>
	</varlistentry>
	<varlistentry>
		<term><option>-v,--version</option></term>
		<listitem><para><action>Show the version number</action></para></listitem>
	</varlistentry>
	<varlistentry>
		<term><option>--license</option></term>
		<listitem><para><action>Show license information</action></para></listitem>
	</varlistentry>
  </variablelist>

</sect1>

<sect1 id="configuration">
<title>Configurate &krusader;</title>

<para>When your run &krusader; for the first time the &krusader; configuration module
      <link linkend="konfigurator">Konfigurator</link> will show up and allow you to
      configure &krusader; as well as detect installed packers and tools. You can always run
      Konfigurator again from the &settingsmenu_lnk;.</para>
  
</sect1>

</appendix>


<appendix id="config_files">
<title>Configuration files</title>
<para>This appendix gives an overview of the configuration files used by &krusader;.</para>


<para><emphasis role="bold">krusaderui.rc</emphasis></para>
<para>This file stores the users toolbar settings and the menu structure.
      Tip: read also the <link linkend="krusaderui_rc">&FAQ;'s</link>.</para>
<para>Location: <filename>$KDEDIR/share/apps/krusader/krusaderui.rc</filename> or
      <filename>~/.kde/share/apps/krusader/krusaderui.rc</filename></para>



<para><emphasis role="bold">krusaderrc</emphasis></para>
<para>This file stores the &krusader; configuration.</para>
<para>Location: <filename>~/.kde/share/config/krusaderrc</filename></para>

<para>The following settings are stored:</para>
<itemizedlist>
    <listitem><para>Advanced</para></listitem>
    <listitem><para>Archives</para></listitem>
    <listitem><para>Dependencies</para></listitem>
    <listitem><para>General</para></listitem>
    <listitem><para>KFileDialog</para></listitem>
    <listitem><para>KFileDialog Speedbar</para></listitem>
    <listitem><para>KrDetailedViewLeft</para></listitem>
    <listitem><para>KrDetailedViewRight</para></listitem>
    <listitem><para>KrViewerWindow</para></listitem>
    <listitem><para>KrViewerWindow Toolbar edit_toolbar</para></listitem>
    <listitem><para>KrViewerWindow Toolbar extraToolBar</para></listitem>
    <listitem><para>KrViewerWindow Toolbar mainToolBar</para></listitem>
    <listitem><para>Look&amp;Feel</para></listitem>
    <listitem><para>Open-with</para></listitem>
    <listitem><para>Private</para></listitem>
    <listitem><para>RemoteMan</para></listitem>
    <listitem><para>Search</para></listitem>
    <listitem><para>Startup</para></listitem>
    <listitem><para>Synchronize</para></listitem>
</itemizedlist>


<para><emphasis role="bold">krbookmarks.xml</emphasis></para>
<para>This file stores the &krusader; bookmarks and uses the &xbel_url; standard.</para>
<para>Location: <filename>~/.kde/share/apps/krusader/krbookmarks.xml</filename></para>


<para><emphasis role="bold">krusermenu.dat</emphasis></para>
<para>This file stores the user menu configuration.</para>
<para>Location: <filename>~/.kde/share/apps/krusader/krusermenu.dat</filename></para>


</appendix>
