xml-normalize desktop-up2date-en.xml,NONE,1.1

Stuart Ellis (elliss) fedora-docs-commits at redhat.com
Fri Jul 8 20:31:32 UTC 2005


Author: elliss

Update of /cvs/docs/xml-normalize
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9275

Added Files:
	desktop-up2date-en.xml 
Log Message:

Added as test 



--- NEW FILE desktop-up2date-en.xml ---
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;

<!ENTITY BOOKID "desktop-up2date-0.3 (2005-06-05)"> <!-- change version of manual and date here -->

<!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-en.xml">

<!-- Bugzilla bug number for the draft notice -->
<!ENTITY BUG-NUM "155180">
<!ENTITY FCLOCALVER "3">
<!ENTITY DRAFTNOTICE SYSTEM "../docs-common/common/draftnotice-en.xml">

]>

<article id="desktop-up2date" lang="en">
  <articleinfo>
    <title>Updating Your Desktop with <application>up2date</application></title>
    <copyright>
      <year>2005</year>
      <holder>Stuart Ellis</holder>
    </copyright>
    <authorgroup>
      <author>
        <surname>Ellis</surname>
        <firstname>Stuart</firstname>
      </author>
    </authorgroup>
    <revhistory>
      <revision>
        <revnumber>0.3</revnumber>
        <date>2005-06-05</date>
        <authorinitials>StuartEllis</authorinitials>
        <revdescription>
          <para>
            Initial CVS commit.
          </para>
        </revdescription>
      </revision>
    </revhistory>
    &LEGALNOTICE;
  </articleinfo>

  &DRAFTNOTICE;

   <section id="sn-desktop-up2date-audience">
    <title>Audience</title>

    <para>
      This tutorial is intended for new users. It explains how to use
      the supplied graphical tools to keep a &FED; desktop system
      updated. Experienced users may still find this software useful,
      but are likely to use <command>yum</command> to both update their
      systems and install new software.
    </para>
  </section>

  <section id="sn-desktop-up2date-intro">
    <title>Introduction</title>

    <para>
      &FC; provides a pair of utilities that work together to enable
      desktop users to update their systems. The <application>Alert
      Icon</application> on your desktop keeps you informed about
      package updates. Until your system is updated this appears as a
      red circle with a flashing exclamation mark. The
      <application>Alert Icon</application> is integrated with
      <application>up2date</application>, which enables you to easily
      install updates for your system.
    </para>

    <para>
      In addition to these tools, &FC; also includes
      <command>yum</command>, a command-line utility that is the current
      recommmended option for software administration. The
      <command>yum</command> utility enables you to automatically
      locate, install and update any software with the latest version.
    </para>

    <note>
      <title>Command-Line Version of <application>up2date</application></title>

      <para>
        This tutorial does not document the command-line version of
        <command>up2date</command>, which provides some of the features
        of <command>yum</command>.
      </para>
    </note>

    <section id="sn-about-packages">
      <title>About Packages</title>
      <indexterm>
        <primary>packages, defined</primary>
      </indexterm>
      <para>
        All of the software and documentation prepared for use with
        &FED; is supplied in the form of files called RPM
        <firstterm>packages</firstterm>. Each package is a compressed
        archive containing product information, program files, icons,
        documentation and management scripts. Packages also include a
        digital signature to prove their source. These files are used by
        management applications to safely locate, install, update and
        remove software. For example, the &FED; installation process
        uses the packages supplied with &FC; to build or upgrade a
        system to your requirements.
      </para>

      <important>
        <title>Verifying Packages</title>

        <para>
          The <application>up2date</application> application
          automatically downloads the &FP; public keys used to verify
          the digital signatures of updated packages.
        </para>
      </important>
    </section>

    <section id="sn-about-channels">
      <title>About Channels</title>
      <indexterm>
        <primary>channels, defined</primary>
      </indexterm>
      <para>
        The <application>up2date</application> application uses
        <firstterm>repositories</firstterm>, specially prepared Web and
        FTP sites that hold software packages. Whatever their type, they
        are all described as <firstterm>channels</firstterm> within
        <application>up2date</application>.
      </para>

      <para>
        These repositories are also used by software management systems
        like <command>yum</command> to install and update software. If
        you configure <command>yum</command> to use additional
        repositories then you should add these to
        <command>up2date</command> as well.
      </para>
    </section>
  </section>

  <section id="sn-applet-managing">
    <title>Enabling and Disabling the <application>Alert Icon</application></title>
    <indexterm>
      <primary><application>Alert Icon</application>, enabling</primary>
    </indexterm>
    <para>
      To enable the <application>Alert Icon</application>, either
      double-click it, or right-click it and select
      <guilabel>Configuration</guilabel>. Click
      <guibutton>Forward</guibutton>
      to move to the <guilabel>Terms of Service</guilabel>. Click
      <guibutton>Forward</guibutton>
      once more to agree to the terms and move on to the <guilabel>Proxy
      Configuration</guilabel>.
    </para>
    <indexterm>
      <primary>proxy server, with the <application>Alert Icon</application>
      </primary>
    </indexterm>
    <para>
      To use a Web proxy server, enter the settings in the
      <guilabel>Proxy Configuration</guilabel>. Select the check-box
      next to <guilabel>Enable HTTP Proxy</guilabel> and enter the name
      of your proxy server. If your proxy server requires a username and
      password to access the Internet select the check-box next to
      <guilabel>Use Authentication</guilabel> and enter the relevant
      <guilabel>Username</guilabel> and <guilabel>Password</guilabel>.
    </para>

    <para>
      Click
      <guibutton>Forward</guibutton>
      a third time to complete the configuration. Select
      <guibutton>Apply</guibutton>
      to confirm the settings and immediately start an update.
    </para>

    <section id="sn-applet-disabling">
      <title>Disabling the Update <application>Alert Icon</application></title>
      <indexterm>
        <primary><application>Alert Icon</application>, disabling</primary>
      </indexterm>
      <para>
        To disable the <application>Alert Icon</application>, follow
        these steps:
        <orderedlist>
          <listitem>
            <para>
              Right-click it and select
              <guilabel>Configuration</guilabel>.
            </para>
          </listitem>
          <listitem>
            <para>
              Click
              <guibutton>Forward</guibutton>
              to move to the next screen.
            </para>
          </listitem>
          <listitem>
            <para>
              Click
              <guibutton>Remove From Panel</guibutton>
              .
            </para>
          </listitem>
        </orderedlist>
      </para>
      <tip>
        <title>Re-enabling The <application>Alert Icon</application></title>
        <para>
          You can re-enable the <application>Alert Icon</application> by
          selecting <menuchoice><guimenu>System
          Tools</guimenu><guimenuitem>Red Hat Network Alert
          Icon</guimenuitem></menuchoice> from the main menu.
        </para>
      </tip>
    </section>
  </section>

  <section id="sn-applet-using">
    <title>Using the <application>Alert Icon</application></title>
    <indexterm>
      <primary><application>Alert Icon</application>, using</primary>
    </indexterm>
    <para>
      Once the <application>Alert Icon</application> is configured the
      <command>rhnsd</command> service on your system periodically
      checks for updates, and changes the icon to reflect the status of
      your system. The default period is every two hours. You may check
      for updates at any time by either double-clicking the icon, or by
      right-clicking it and selecting <guilabel>Check for
      updates</guilabel>.
    </para>

    <para>
      The icon displays the status of your system by showing one of four
      states:
      <itemizedlist>
        <listitem>
          <para>
            Grey with a check mark: the first check is in progress.
          </para>
        </listitem>
        <listitem>
          <para>
            Blue with a check mark: your system is up to date.
          </para>
        </listitem>
        <listitem>
          <para>
            Green with double arrows: currently checking for updates.
          </para>
        </listitem>
        <listitem>
          <para>
            Red with a flashing exclamation mark: there are newer
            packages available for the software installed on your
            system.
          </para>
        </listitem>
      </itemizedlist>
    </para>

    <para>
      Rest your mouse pointer over the icon to show the number of
      outstanding updates for your system.
    </para>

    <note>
      <title>Only &FED; Updates are Shown</title>

      <para>
        The <application>Alert Icon</application> can only inform you of
        updates for the packages provided by the &FP;. To update all of
        the packages on your system, use <command>yum</command>.
      </para>
    </note>
  </section>

  <section id="sn-up2date-configuring">
    <title>Configuring <application>up2date</application></title>
    <indexterm>
      <primary>up2date, configuring</primary>
    </indexterm>
    <para>
      If you select <guilabel>Check for updates</guilabel> you are shown
      a list of available updates, and can
      <guibutton>Launch Up2date</guibutton>
      by clicking the button. Alternatively, you can right-click the
      <application>Alert Icon</application> and select <guilabel>Launch
      Up2date</guilabel>. You are prompted for the root password before
      the application continues.
    </para>
    <indexterm>
      <primary>proxy server, with up2date</primary>
    </indexterm>
    <para>
      The configuration screen is displayed the first time that you run
      <application>up2date</application>. This has the same proxy server
      options as the <application>Alert Icon</application>. If you use a
      proxy server you should enter the same settings again.
    </para>

    <para>
      By default <application>up2date</application> has two safety
      restrictions that you may wish to remove. The first is that it
      will not update any package where the configuration files have
      been modified. To remove this safety restriction, click on the
      <guilabel>Retrieval/Installation</guilabel> tab and clear the
      check-box for <guilabel>Do not upgrade packages where the local
      configuration file has been modified</guilabel>. The other safety
      measure is that it will not automatically update the kernel on
      your system. Click on the <guilabel>Package exceptions</guilabel>
      tab, select <guilabel>kernel*</guilabel> and then click
      <guibutton>Remove</guibutton>
      to enable kernel updates.
    </para>

    <para>
      Click
      <guibutton>OK</guibutton>
      when you have finished configuring
      <application>up2date</application>.
    </para>

    <para>
      If this is the first time that you have run
      <application>up2date</application> the &FED; public key is
      downloaded. Click
      <guibutton>Yes</guibutton>
      .
    </para>
  </section>

  <section id="sn-up2date-usage">
    <title>Updating Your System with <application>up2date</application></title>
    <indexterm>
      <primary>up2date, using</primary>
    </indexterm>
    <para>
      However you launched <application>up2date</application>, you begin
      with the <guilabel>Welcome to Red Hat Update Agent</guilabel>
      screen. Click
      <guibutton>Forward</guibutton>
      to move to the <guilabel>Channels</guilabel> screen. You may
      choose not to check a channel for updates by clearing the
      check-box next to the channel name.
    </para>

    <para>
      Click
      <guibutton>Forward</guibutton>
      to continue, or
      <guibutton>Cancel</guibutton>
      to abort. If you continue all of the chosen channels are checked
      for updates to the packages installed on your system, and a list
      of packages is displayed.
    </para>

    <para>
      Click the check-box next to the name of the package to select it
      for updating. To select all of the packages on the list, click
      <guilabel>Select all packages</guilabel>.
    </para>

    <para>
      Click
      <guibutton>Forward</guibutton>
      to begin the update process. This may take some time as the new
      packages are downloaded. The <guilabel>Retrieving
      Packages</guilabel> screen displays the progress of the downloads.
    </para>

    <para>
      Once the downloads have completed, click
      <guibutton>Forward</guibutton>
      . Your updates are then installed in the correct sequence,
      replacing older versions of the same packages.
    </para>

    <para>
      Click
      <guibutton>Forward</guibutton>
      to move on to the <guilabel>Finish Page</guilabel>. This lists all
      of the updates that have been installed.
    </para>
  </section>

  <section id="sn-up2date-managing-channels">
    <title>Managing <application>up2date</application> Channels</title>

    <para>
      You may add or remove channels from
      <application>up2date</application> by editing
      <filename>/etc/sysconfig/rhn/sources</filename>. Each channel is
      defined by a line in this file. The &FP; repositories are already
      listed, with standard repositories enabled, and the package
      repositories for test versions of packages disabled.
    </para>
    <tip>
      <title>Software Repository Types</title>
      <para>
        Any software repository that supports <command>apt</command> or
        <command>yum</command> can be used as an
        <application>up2date</application> channel.
      </para>
    </tip>
    <section id="sn-up2date-toggling-channels">
      <title>Enabling and Disabling Channels</title>
      <indexterm>
        <primary>channels, enabling</primary>
      </indexterm>
      <indexterm>
        <primary>channels, disabling</primary>
      </indexterm>
      <para>
        Channels are disabled by placing a comment marker at the
        beginning of the line. To re-enable a channel, remove the #
        character at the beginning of the line.
      </para>
    </section>

    <section id="sn-up2date-changing-channels">
      <title>Adding and Removing Channels</title>
      <indexterm>
        <primary>channels, adding</primary>
      </indexterm>
      <indexterm>
        <primary>channels, removing</primary>
      </indexterm>
      <para>
        To add a new channel, add a new line to
        <filename>/etc/sysconfig/rhn/sources</filename>.
      </para>

      <para>
        You must specify three settings for each channel. The
        <command>type</command> should be <command>yum</command> unless
        the provider is using an alternate system. The
        <command>channel-label</command> is the name that the channel
        will be known by. The <command>url</command> is the full URL to
        the directory holding the RPM packages.
      </para>

      <para>
        This is an example channel listing, for a repository hosted on
        the server <wordasword>fedora.multikabel.nl</wordasword>:
      </para>

      <example id="up2date-channel-format">
        <title>Format of <application>up2date</application> Channels</title>
<programlisting>
      <![CDATA[
       yum fedora-us-stable-2 http://fedora.multikabel.nl/fedora/fedora/3/$ARCH/RPMS.stable
      ]]>
    </programlisting>
      </example>

      <para>
        The &FC; channels use <command>yum-mirror</command>, rather than
        <command>yum</command>. This means that
        <application>up2date</application> automatically fetches a list
        of servers from the file specified by the
        <command>url</command>, and then randomly select a download
        server from the list. Another server is automatically chosen if
        the selected server fail to respond.
      </para>
      <tip>
        <title>Repositories for <command>apt</command></title>
        <para>
          Some third-party package providers use <command>apt</command>,
          rather than <command>yum</command>. Many support both types to
          ensure compatibility. If the provider requires
          <command>apt</command>, then substitute <command>apt</command>
          for <command>yum</command> in your channel definition.
        </para>
      </tip>
      <para>
        To remove a channel, delete the relevant line from
        <filename>/etc/sysconfig/rhn/sources</filename>.
      </para>

      <important>
        <title>Managing Public Keys</title>

        <para>
          Remember to add or remove the public key for the package
          provider from your software management system when adding or
          removing channels for third-party packages.
        </para>
      </important>
    </section>
  </section>

  <index id="generated-index"></index>
</article>




More information about the Fedora-docs-commits mailing list