desktop-up2date desktop-up2date-en.xml,1.4,1.5
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/desktop-up2date
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17286
Modified Files:
desktop-up2date-en.xml
Log Message:
Minor edits.
Index: desktop-up2date-en.xml
===================================================================
RCS file: /cvs/docs/desktop-up2date/desktop-up2date-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- desktop-up2date-en.xml 14 Jun 2005 22:30:42 -0000 1.4
+++ desktop-up2date-en.xml 12 Jul 2005 00:11:33 -0000 1.5
@@ -4,13 +4,13 @@
<!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 BOOKID "desktop-up2date-0.4 (2005-07-10)"> <!-- 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 FCLOCALVER "4">
<!ENTITY DRAFTNOTICE SYSTEM "../docs-common/common/draftnotice-en.xml">
]>
@@ -24,20 +24,30 @@
</copyright>
<authorgroup>
<author>
- <surname>Ellis</surname>
- <firstname>Stuart</firstname>
+ <surname>Ellis</surname>
+ <firstname>Stuart</firstname>
</author>
</authorgroup>
<revhistory>
<revision>
- <revnumber>0.3</revnumber>
- <date>2005-06-05</date>
- <authorinitials>StuartEllis</authorinitials>
- <revdescription>
- <para>
+ <revnumber>0.3</revnumber>
+ <date>2005-06-05</date>
+ <authorinitials>StuartEllis</authorinitials>
+ <revdescription>
+ <para>
Initial CVS commit.
</para>
- </revdescription>
+ </revdescription>
+ </revision>
+ <revision>
+ <revnumber>0.4</revnumber>
+ <date>2005-07-10</date>
+ <authorinitials>StuartEllis</authorinitials>
+ <revdescription>
+ <para>
+ Minor revisions.
+ </para>
+ </revdescription>
</revision>
</revhistory>
&LEGALNOTICE;
@@ -47,385 +57,468 @@
<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.
+ 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>
-
- <section id="sn-desktop-up2date-intro">
+ <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>
+ &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
+ recommended 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>
+ <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>
+ The <application>up2date</application> application
+ automatically downloads the &FP; public keys used to verify
+ the digital signatures of updated packages.
+ </para>
</important>
- </section>
-
+ </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-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">
+ <section id="sn-applet-managing">
<title>Enabling and Disabling the <application>Alert Icon</application></title>
<indexterm>
- <primary><application>Alert Icon</application>, enabling</primary>
+ <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>.
+ 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>
+ <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.
+ 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>
- <section id="sn-applet-disabling">
- <title>Disabling the Update <application>Alert Icon</application></title>
+
+ <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>, disabling</primary>
+ <primary><application>Alert Icon</application>, using</primary>
</indexterm>
- <para>
- To disable the <application>Alert Icon</application>, follow these steps:
- <orderedlist>
+ <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 six
+ states:
+ <itemizedlist>
<listitem>
- <para>Right-click it and select <guilabel>Configuration</guilabel>.
- </para>
+ <para>
+ Grey with a check mark: the first check is in progress.
+ </para>
</listitem>
<listitem>
- <para>Click <guibutton>Forward</guibutton> to move to the next screen.
- </para>
+ <para>
+ Blue with a check mark: your system is up to date.
+ </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>
+ Green with double arrows: currently checking for updates.
</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.
+ </listitem>
+ <listitem>
+ <para>
+ Red with a flashing exclamation mark: there are newer
+ packages available for the software installed on your
+ system.
</para>
- </listitem>
- <listitem>
- <para>Green with double arrows: currently checking for updates.
+ </listitem>
+ <listitem>
+ <para>
+ Grey with a question mark:
+ <application>up2date</application> is not able to obtain
+ update information from the server.
</para>
- </listitem>
- <listitem>
- <para>Red with a flashing exclamation mark: there are newer
- packages available for the software installed on your system.
+ </listitem>
+ <listitem>
+ <para>
+ Grey with double arrows, struck-through with a red line: No
+ network connection to the server.
</para>
- </listitem>
- </itemizedlist>
- </para>
+ </listitem>
+ </itemizedlist>
+ </para>
- <para>
- Rest your mouse pointer over the icon to show the number of outstanding updates for your system.
- </para>
+ <para>
+ Rest your mouse pointer over the icon to show the number of
+ outstanding updates for your system.
+ </para>
- <note>
+ <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>
+ <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>
+ <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>
+ </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
+ <systemitem class="username">root</systemitem> 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>.
+ </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>
- If this is the first time that you have run
- <application>up2date</application> the &FED; public key is downloaded. Click <guibutton>Yes</guibutton>.
+ Click
+ <guibutton>OK</guibutton>
+ when you have finished configuring
+ <application>up2date</application>.
</para>
- </section>
+ <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">
+ <section id="sn-up2date-usage">
<title>Updating Your System with <application>up2date</application></title>
<indexterm>
- <primary>up2date, using</primary>
+ <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.
+ 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.
+ 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>.
+ 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.
+ 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.
+ 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.
+ 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>
- <section id="sn-up2date-managing-channels">
+ <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>
+ 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>
-
-
+ <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>
+ <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>
+ <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
+ yum fedora-us-stable-2 http://fedora.multikabel.nl/fedora/fedora/4/$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>
+ </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>
+ <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>
+ 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>
- </section>
-
-
-<index id="generated-index"></index>
+ <index id="generated-index"></index>
</article>
18 years, 10 months
owners owners.list,1.1.1.1,1.2
by fedora-docs-commits@redhat.com
Author: sopwith
Update of /cvs/docs/owners
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10365
Modified Files:
owners.list
Log Message:
fix
Index: owners.list
===================================================================
RCS file: /cvs/docs/owners/owners.list,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -r1.1.1.1 -r1.2
--- owners.list 11 Jul 2005 19:25:58 -0000 1.1.1.1
+++ owners.list 11 Jul 2005 19:34:25 -0000 1.2
@@ -1,5 +1,5 @@
# Format:
-# product|component|initialowner|initialqacontact|initialcclist
+# product|component|description|initialowner|initialqacontact|initialcclist
#
# If you don't know what product & component are, ask someone who knows bugzilla :)
# initialowner is the initial owner of bugs on this component
@@ -7,4 +7,3 @@
# initialcclist is the list of people initially CC'd for bugs on this component
#
# All e-mail addresses used here MUST correspond to existing bugzilla accounts!
-
18 years, 10 months
owners - Imported sources
by fedora-docs-commits@redhat.com
Author: sopwith
Update of /cvs/docs/owners
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10315
Log Message:
Initial import
Status:
Vendor Tag: FEDORA
Release Tags: V0_0
N owners/owners.list
No conflicts created by this import
18 years, 10 months
yum-software-management Makefile, 1.3, 1.4 yum-software-management-en.xml, 1.5, 1.6
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv3215
Modified Files:
Makefile yum-software-management-en.xml
Log Message:
- Update Makefile to use Makefile.common
- Amended to cover auto GPG key import
- Added section on localinstall
Index: Makefile
===================================================================
RCS file: /cvs/docs/yum-software-management/Makefile,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- Makefile 29 Jun 2005 00:41:23 -0000 1.3
+++ Makefile 9 Jul 2005 15:06:36 -0000 1.4
@@ -1,30 +1,30 @@
###############################################################################
# Makefile for RHLP docs project
# Created by: Tammy Fox <tfox(a)redhat.com>
-# Last edited by: Stuart Ellis <stuart(a)elsn.org>
+# Last edited by: Tommy Reynolds <Tommy.Reynolds(a)MegaCoder.com>
# WARNING: need passivetex 1.24 for pdf generation to work
# License: GPL
# Copyright 2003 Tammy Fox, Red Hat, Inc.
+# Copyright 2005 Tommy Reynolds, MegaCoder.com
###############################################################################
-XSLPDF = ../docs-common/xsl/main-pdf.xsl
-XSLHTML = ../docs-common/xsl/main-html.xsl
-LANG = en
-DOCNAME = yum-software-management-$(LANG)
-XMLFILE = $(DOCNAME).xml
+XSLPDF = ../docs-common/xsl/main-pdf.xsl
+XSLHTML = ../docs-common/xsl/main-html.xsl
+XSLHTMLNOCHUNKS = ../docs-common/xsl/main-html-nochunks.xsl
+LANG = en
+DOCNAME = yum-software-management-$(LANG)
+XMLFILE = $(DOCNAME).xml
+XMLEXTRAFILES =
+
######################################################
include ../docs-common/Makefile.common
######################################################
-html:
- @xmlto html -x $(XSLHTML) -o $(DOCNAME) $(XMLFILE)
- @mkdir -p $(DOCNAME)/stylesheet-images
- @cp ../docs-common/stylesheet-images/*.png $(DOCNAME)/stylesheet-images
- @cp ../docs-common/css/fedora.css $(DOCNAME)
-
-
-pdf:
- @xmlto pdf -x $(XSLPDF) $(XMLFILE)
-######################################################
-clean:
- @rm -rfv *.html *.pdf *.tex $(DOCNAME) $(DOCNAME).tar.gz
+# If you want to add additional steps to any of the
+# targets defined in "Makefile.common", be sure to use
+# a double-colon in your rule here. For example, to
+# print the message "FINISHED AT LAST" after building
+# the HTML document version, uncomment the following
+# line:
+#${DOCNAME}/index.html::
+# echo FINISHED AT LAST
View full diff with command:
/usr/bin/cvs -f diff -kk -u -N -r 1.5 -r 1.6 yum-software-management-en.xml
Index: yum-software-management-en.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- yum-software-management-en.xml 22 Jun 2005 00:07:32 -0000 1.5
+++ yum-software-management-en.xml 9 Jul 2005 15:06:36 -0000 1.6
@@ -4,1139 +4,1318 @@
<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;
-<!ENTITY BOOKID "yum-software-management-0.4.4 (2005-06-14)"> <!-- change version of manual and date here -->
+<!ENTITY BOOKID "yum-software-management-0.5.0 (2005-07-09)"> <!-- 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 "155190">
-<!ENTITY FCLOCALVER "3">
+<!ENTITY FCLOCALVER "4">
<!ENTITY DRAFTNOTICE SYSTEM "../docs-common/common/draftnotice-en.xml">
]>
- <article id="yum-software-management" lang="en">
- <articleinfo>
- <title>Software Management with <command>yum</command></title>
- <copyright>
- <year>2005</year>
- <holder>Stuart Ellis</holder>
- </copyright>
- <authorgroup>
- <author>
- <surname>Ellis</surname>
- <firstname>Stuart</firstname>
- </author>
- </authorgroup>
+<article id="yum-software-management" lang="en">
+ <articleinfo>
+ <title>Software Management with <command>yum</command></title>
+ <copyright>
+ <year>2005</year>
+ <holder>Stuart Ellis</holder>
+ </copyright>
+ <authorgroup>
+ <author>
+ <surname>Ellis</surname>
+ <firstname>Stuart</firstname>
+ </author>
+ </authorgroup>
&LEGALNOTICE;
<revhistory>
<revision>
- <revnumber>0.4</revnumber>
- <date>2005-06-01</date>
- <authorinitials>StuartEllis</authorinitials>
- <revdescription>
- <para>
- Initial import into CVS.
+ <revnumber>0.4</revnumber>
+ <date>2005-06-01</date>
+ <authorinitials>StuartEllis</authorinitials>
+ <revdescription>
+ <para>
+ Initial import into CVS.
</para>
- </revdescription>
- </revision>
+ </revdescription>
+ </revision>
</revhistory>
- </articleinfo>
-
+ </articleinfo>
<section id="sn-introduction">
- <title>Introduction</title>
-
+ <title>Introduction</title>
&DRAFTNOTICE;
+ <section id="sn-software-management-audience">
+ <title>Audience</title>
- <section id="sn-software-management-audience">
- <title>Audience</title>
- <para>
- The <command>yum</command> utility is currently the recommended method for
- managing software on &FED; systems. All &FED; users responsible for
- maintaining their own systems will find <command>yum</command> an essential tool.
- </para>
- </section>
-
- <section id="sn-software-management-usingdoc">
- <title>Using This Document</title>
- <para>
- This document is a reference for using <command>yum</command>. You may
- wish to read some or all of the sections, depending upon your needs and
- level of experience.
- </para>
- <para>
- If you are a new user, read the <xref
- linkend="sn-software-management-concepts"/> before using
- <command>yum</command> for the first time.
- </para>
- <para>
- Experienced Linux users should start with <xref linkend="sn-authorizing-package-sources"/>.
- </para>
- <para>
- Anyone with several &FED; systems on a network may benefit from setting
- up their own software repositories to manage the process of installation and
- updates. The details of maintaining your own repositories are explained
- in <xref linkend="sn-managing-repositories"/>.
- </para>
- <para>
- Most of the examples use the package <filename>tsclient</filename>,
- which is included with &FC; to provide an application for remote desktop
- access. If it is installed successfully you may start the application
- by choosing
- <menuchoice><guimenu>Applications</guimenu><guisubmenu>Internet</guisubmenu><guimenuitem>Terminal
- Server Client</guimenuitem></menuchoice>. To use the examples,
- substitute the name of the relevant package for <filename>tsclient</filename>.
- </para>
- <important>
- <title>Avoid Logging in with the Root Account</title>
- <para>
- You do not need to log in with the root account in order to manage your
- &FC; system. All of the commands shown in this tutorial that require
- root access will prompt you for the root password. The example
- terminal commands use <command>su <option>-c</option></command> to
- provide this facility.
- </para>
- </important>
- </section>
+ <para>
+ The <command>yum</command> utility is currently the recommended
+ method for managing software on &FED; systems. All &FED; users
+ responsible for maintaining their own systems will find
+ <command>yum</command> an essential tool.
+ </para>
+ </section>
+ <section id="sn-software-management-usingdoc">
+ <title>Using This Document</title>
- <section id="sn-yum-additional-resources">
- <title>Additional Resources</title>
- <indexterm>
- <primary>yum, documentation</primary>
- </indexterm>
- <indexterm>
- <primary>yum, man pages</primary>
- </indexterm>
- <para>
- The <command>yum</command> utility has features and options that
- are not discussed in this document. Read the <command>man</command> pages
- for <command>yum(8)</command> and <filename>yum.conf(5)</filename> to
- learn more.
- </para>
- <indexterm>
- <primary>yum, Websites</primary>
- </indexterm>
- <para>
- The official Website for <command>yum</command> is:
- </para>
- <para>
- <ulink url="http://linux.duke.edu/projects/yum/">http://linux.duke.edu/projects/yum/</ulink>
- </para>
- <indexterm>
- <primary>Yum, mailing lists</primary>
- </indexterm>
- <para>
- The official mailing list for <command>yum</command> users is:
- </para>
- <para>
- <ulink url="https://lists.dulug.duke.edu/mailman/listinfo/yum">https://lists.dulug.duke.edu/mailman/listinfo/yum</ulink>
- </para>
- <para>
- The archive for the <command>yum</command> development mailing list is here:
- </para>
- <para>
- <ulink url="https://lists.dulug.duke.edu/pipermail/yum-devel/">https://lists.dulug.duke.edu/pipermail/yum-devel/</ulink>
- </para>
+ <para>
+ This document is a reference for using <command>yum</command>.
+ You may wish to read some or all of the sections, depending upon
+ your needs and level of experience.
+ </para>
+
+ <para>
+ If you are a new user, read the
+ <xref
+ linkend="sn-software-management-concepts"/> before
+ using <command>yum</command> for the first time.
+ </para>
+
+ <para>
+ Experienced Linux users should start with
+ <xref linkend="sn-updating-your-system"/>.
+ </para>
[...2082 lines suppressed...]
</section>
<section id="sn-updating-repository">
- <title>Updating a Repository</title>
- <indexterm>
- <primary>repositories, updating</primary>
- </indexterm>
- <para>
- Whenever a package is added, or replaced with a different version, you
- must run <command>createrepo</command> again for the index files to be updated.
- If you are mirroring an existing repository then you may assume that
- the site administrator updates the indexes, but for safety you should
- add this to your synchronization scripts. The
- <command>createrepo</command> utility can be run as frequently as you wish.
+ <title>Updating a Repository</title>
+ <indexterm>
+ <primary>repositories, updating</primary>
+ </indexterm>
+ <para>
+ Whenever a package is added, or replaced with a different
+ version, you must run <command>createrepo</command> again for
+ the index files to be updated. If you are mirroring an existing
+ repository then you may assume that the site administrator
+ updates the indexes, but for safety you should add this to your
+ synchronization scripts. The <command>createrepo</command>
+ utility can be run as frequently as you wish.
</para>
- </section>
-
+ </section>
</section>
-
- <section id="sn-yum-proxy-server">
- <title>Using <command>yum</command> with a Proxy Server</title>
- <indexterm>
+ <section id="sn-yum-proxy-server">
+ <title>Using <command>yum</command> with a Proxy Server</title>
+ <indexterm>
<primary>proxy server, with yum</primary>
- </indexterm>
- <indexterm>
+ </indexterm>
+ <indexterm>
<primary>yum, using a proxy server</primary>
- </indexterm>
- <para>
- Repositories may be accessed through standard proxy servers. If your
- system is connected to the Internet through a Web proxy server, specify
- the details of the server in <filename>/etc/yum.conf</filename>. The
- <command>proxy</command> setting must specify the proxy server as a
- complete URL, including the TCP port number. If your proxy server
- requires a username and password, specify these by adding
- <command>proxy_username</command> and <command>proxy_password</command> settings.
- </para>
-
- <para>
- For example, the settings below enable <command>yum</command> to use the
- proxy server <command>mycache.mydomain.com</command>, connecting to port
- <command>3128</command>, with the username <command>yum-user</command> and the password <command>qwerty</command>.
- </para>
+ </indexterm>
+ <para>
+ Repositories may be accessed through standard proxy servers. If
+ your system is connected to the Internet through a Web proxy
+ server, specify the details of the server in
+ <filename>/etc/yum.conf</filename>. The <command>proxy</command>
+ setting must specify the proxy server as a complete URL, including
+ the TCP port number. If your proxy server requires a username and
+ password, specify these by adding
+ <command>proxy_username</command> and
+ <command>proxy_password</command> settings.
+ </para>
+
+ <para>
+ For example, the settings below enable <command>yum</command> to
+ use the proxy server <command>mycache.mydomain.com</command>,
+ connecting to port <command>3128</command>, with the username
+ <command>yum-user</command> and the password
+ <command>qwerty</command>.
+ </para>
- <example id="config-file-httpproxy">
+ <example id="config-file-httpproxy">
<title>Configuration File Settings for Using A Proxy Server</title>
- <programlisting>
+<programlisting>
<![CDATA[
# The proxy server - proxy server:port number
proxy=http://mycache.mydomain.com:3128
@@ -1213,64 +1398,70 @@
proxy_password=qwerty
]]>
</programlisting>
- </example>
+ </example>
- <note>
+ <note>
<title>Global Settings</title>
+
<para>
- Defining a proxy server in <filename>/etc/yum.conf</filename> means that
- <emphasis>all</emphasis> users connect to the proxy server with those
- details when using <command>yum</command>.
- </para>
- </note>
-
- <para>
- To enable proxy access for a specific user, add the lines in the
- example box below to their shell profile. For the default
- <command>bash</command> shell, the profile is the file
- <filename>.bash_profile</filename>. The settings below enable <command>yum</command> to
- use the proxy server <command>mycache.mydomain.com</command>, connecting to port <command>3128</command>.
- </para>
- <example id="profile-script-httpproxy">
+ Defining a proxy server in <filename>/etc/yum.conf</filename>
+ means that <emphasis>all</emphasis> users connect to the proxy
+ server with those details when using <command>yum</command>.
+ </para>
+ </note>
+
+ <para>
+ To enable proxy access for a specific user, add the lines in the
+ example box below to their shell profile. For the default
+ <command>bash</command> shell, the profile is the file
+ <filename>.bash_profile</filename>. The settings below enable
+ <command>yum</command> to use the proxy server
+ <command>mycache.mydomain.com</command>, connecting to port
+ <command>3128</command>.
+ </para>
+
+ <example id="profile-script-httpproxy">
<title>Profile Settings for Using a Proxy Server</title>
- <programlisting>
+<programlisting>
<![CDATA[
# The Web proxy server used by this account
http_proxy="http://mycache.mydomain.com:3128"
export http_proxy
]]>
</programlisting>
- </example>
+ </example>
+
+ <para>
+ If the proxy server requires a username and password then add
+ these to the URL. For example, to include the username
+ <command>yum-user</command> and the password
+ <command>qwerty</command>:
+ </para>
- <para>
- If the proxy server requires a username and password then add these to the
- URL. For example, to include the username
- <command>yum-user</command> and the password <command>qwerty</command>:
- </para>
- <example id="profile-script-httpproxy-withpassword">
+ <example id="profile-script-httpproxy-withpassword">
<title>Profile Settings for a Secured Proxy Server</title>
- <programlisting>
+<programlisting>
<![CDATA[
# The Web proxy server, with the username and password for this account
http_proxy="http://yum-user:qwerty@mycache.mydomain.com:3128"
export http_proxy
]]>
</programlisting>
- </example>
- <note>
- <title><command>http_proxy</command> Variable with Other Utilities</title>
- <para>
- The <command>http_proxy</command> variable is also used by <command>curl</command> and
- other utilities. Although <command>yum</command> itself may use <command>http_proxy</command> in
- either upper-case or lower-case, <command>curl</command> requires
- the name of the variable to be in lower-case.
- </para>
- </note>
+ </example>
- </section>
+ <note>
+ <title><command>http_proxy</command> Variable with Other Utilities</title>
+ <para>
+ The <command>http_proxy</command> variable is also used by
+ <command>curl</command> and other utilities. Although
+ <command>yum</command> itself may use
+ <command>http_proxy</command> in either upper-case or
+ lower-case, <command>curl</command> requires the name of the
+ variable to be in lower-case.
+ </para>
+ </note>
+ </section>
-<index id="generated-index"></index>
+ <index id="generated-index"></index>
</article>
-
-
18 years, 10 months
xml-normalize desktop-up2date-en.xml,1.3,1.4
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/xml-normalize
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9412
Modified Files:
desktop-up2date-en.xml
Log Message:
Test
18 years, 10 months
xml-normalize desktop-up2date-en.xml,1.2,1.3
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/xml-normalize
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9380
Modified Files:
desktop-up2date-en.xml
Log Message:
Test commit 3.
18 years, 10 months
xml-normalize desktop-up2date-en.xml,1.1,1.2
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/xml-normalize
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9308
Modified Files:
desktop-up2date-en.xml
Log Message:
Test commit 2.
18 years, 10 months
xml-normalize desktop-up2date-en.xml,NONE,1.1
by fedora-docs-commits@redhat.com
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>
18 years, 10 months
desktop-up2date Makefile,1.3,1.4
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/desktop-up2date
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8993
Modified Files:
Makefile
Log Message:
Updated Makefile
Index: Makefile
===================================================================
RCS file: /cvs/docs/desktop-up2date/Makefile,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- Makefile 29 Jun 2005 00:45:22 -0000 1.3
+++ Makefile 7 Jul 2005 22:37:38 -0000 1.4
@@ -1,33 +1,30 @@
###############################################################################
# Makefile for RHLP docs project
# Created by: Tammy Fox <tfox(a)redhat.com>
-# Last edited by: Stuart Ellis <stuart(a)elsn.org>
+# Last edited by: Tommy Reynolds <Tommy.Reynolds(a)MegaCoder.com>
# WARNING: need passivetex 1.24 for pdf generation to work
# License: GPL
# Copyright 2003 Tammy Fox, Red Hat, Inc.
+# Copyright 2005 Tommy Reynolds, MegaCoder.com
###############################################################################
-XSLPDF = ../docs-common/xsl/main-pdf.xsl
-XSLHTML = ../docs-common/xsl/main-html.xsl
-LANG = en
-DOCNAME = desktop-up2date-$(LANG)
-XMLFILE = $(DOCNAME).xml
+XSLPDF = ../docs-common/xsl/main-pdf.xsl
+XSLHTML = ../docs-common/xsl/main-html.xsl
+XSLHTMLNOCHUNKS = ../docs-common/xsl/main-html-nochunks.xsl
+LANG = en
+DOCNAME = desktop-up2date-$(LANG)
+XMLFILE = $(DOCNAME).xml
+XMLEXTRAFILES =
######################################################
-
include ../docs-common/Makefile.common
-
-######################################################
-html:
- @xmlto html -x $(XSLHTML) -o $(DOCNAME) $(XMLFILE)
- @mkdir -p $(DOCNAME)/stylesheet-images
- @cp ../docs-common/stylesheet-images/*.png $(DOCNAME)/stylesheet-images
- @cp ../docs-common/css/fedora.css $(DOCNAME)
-
-
-pdf:
- @xmlto pdf -x $(XSLPDF) $(XMLFILE)
######################################################
-clean:
- @rm -rfv *.html *.pdf *.tex $(DOCNAME) $(DOCNAME).tar.gz
+# If you want to add additional steps to any of the
+# targets defined in "Makefile.common", be sure to use
+# a double-colon in your rule here. For example, to
+# print the message "FINISHED AT LAST" after building
+# the HTML document version, uncomment the following
+# line:
+#${DOCNAME}/index.html::
+# echo FINISHED AT LAST
18 years, 10 months
docs-common/bin xmlformat-fdp.conf,1.1,1.2
by fedora-docs-commits@redhat.com
Author: pfrields
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv30384/d/bin
Modified Files:
xmlformat-fdp.conf
Log Message:
Revise handling of <*name> and <abbrev> tagging
Index: xmlformat-fdp.conf
===================================================================
RCS file: /cvs/docs/docs-common/bin/xmlformat-fdp.conf,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- xmlformat-fdp.conf 27 Jun 2005 19:49:21 -0000 1.1
+++ xmlformat-fdp.conf 7 Jul 2005 16:22:38 -0000 1.2
@@ -30,6 +30,7 @@
firstname surname othername
entry-break = 0
exit-break = 0
+ normalize = yes
revnumber date authorinitials
entry-break = 0
@@ -55,7 +56,7 @@
exit-break = 0
normalize = yes
-emphasis literal
+emphasis literal abbrev
format = inline
trademark
18 years, 10 months