install-guide/devel/en_US nextsteps.xml, 1.6, 1.7 rpm-info.xml, 1.15, 1.16 upgrading.xml, 1.3, 1.4

[Paul W. Frields (pfrields)]

Author: pfrields

Update of /cvs/docs/install-guide/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv30091/en_US

Modified Files:
	nextsteps.xml rpm-info.xml upgrading.xml 
Log Message:
Add information on upgrading a distribution


Index: nextsteps.xml
===================================================================
RCS file: /cvs/docs/install-guide/devel/en_US/nextsteps.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- nextsteps.xml	23 May 2007 02:23:07 -0000	1.6
+++ nextsteps.xml	12 Oct 2007 00:45:38 -0000	1.7
@@ -123,6 +123,47 @@
 	url="http://docs.fedoraproject.org/yum/sn-updating-your-system.html"/>.
     </para>
   </section>
+  <section id="sn-finishing-upgrade">
+    <title>Finishing an Upgrade</title>
+    <para>If you chose to upgrade your system from a previous release rather
+      than perform a fresh installation, you may want to examine the
+      differences in the package set.  <xref
+	linkend="sn-upgrade-tree"/> advised you to create a package
+      listing for your original system.  You can now use that listing to
+      determine how to bring your new system close to the original
+      system state.</para>
+    <para>Most software repository configurations are stored in packages
+      that end with the term <literal>release</literal>.  Check the old
+      package list for the repositories that were installed:</para>
+    <screen><command><![CDATA[awk '{print $1}' ~/old-pkglist.txt | grep 'release$']]></command></screen>
+    <para>If necessary, retrieve and install these software repository
+      packages from their original sources on the Internet.  Follow the
+      instructions at the originating site to install the repository
+      configuration packages for use by <command>yum</command> and other
+      software management tools on your &DISTRO; system.</para>
+    <para>Then run the following commands to make a list of other
+      missing software packages:</para>
+
+    <screen><command><![CDATA[awk '{print $1}' ~/old-pkglist.txt | sort | uniq > ~/old-pkgnames.txt
+rpm -qa --qf '%{NAME}\n' | sort | uniq > ~/new-pkgnames.txt
+diff -u ~/old-pkgnames.txt ~/new-pkgnames.txt | grep '^-' | sed 's/^-//' > /tmp/pkgs-to-install.txt]]></command></screen>
+
+    <para>Now use the file <filename>/tmp/pkgs-to-install.txt</filename> with
+      the <command>yum</command> command to restore most or all of your
+      old software:</para>
+
+    <screen><command><![CDATA[su -c 'yum install `cat /tmp/pkgs-to-install.txt`']]></command></screen>
+
+    <important>
+      <title>Missing Software</title>
+      <para>Due to changes in package complements between &DISTRO;
+	releases, it is possible this method may not restore all the
+	software on your system.  You can use the routines above to
+	again compare the software on your system, and remedy any
+	problems you find.</para>
+    </important>
+
+  </section>
   <section id="sn-news-subscriptions">
     <title>Subscribing to &FED; Announcements and News</title>
 


Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/install-guide/devel/en_US/rpm-info.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- rpm-info.xml	6 Oct 2007 14:21:51 -0000	1.15
+++ rpm-info.xml	12 Oct 2007 00:45:38 -0000	1.16
@@ -23,6 +23,10 @@
   <title>Fedora 8 Installation Guide</title>
   <desc>Provides documentation for the installation process.</desc>
   <changelog order="newest-first">
+    <revision date="2007-10-11" number="7.92.3">
+      <author worker="PaulWFrields"/>
+      <details>Add information on upgrading a distribution</details>
+    </revision>
     <revision date="2007-10-06" number="7.92.2">
       <author worker="PaulWFrields"/>
       <details>Add cobbler information for install servers</details>


Index: upgrading.xml
===================================================================
RCS file: /cvs/docs/install-guide/devel/en_US/upgrading.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- upgrading.xml	6 May 2007 21:20:46 -0000	1.3
+++ upgrading.xml	12 Oct 2007 00:45:38 -0000	1.4
@@ -46,9 +46,55 @@
 	ensure it performs correctly on the updated system.
       </para>
     </note>
-
   </section>
 
+  <section id="sn-upgrade-tree">
+    <title>Upgrading Using the Installer</title>
+    <tip>
+      <title>Installations are Recommended</title>
+      <para>In general, the &FP; recommends that you keep user data on a
+	separate <filename class="partition">/home</filename> partition
+	and perform a fresh installation.  For more information on
+	partitions and how to set them up, refer to <xref
+	linkend="ch-disk-partitioning"/>.</para>
+    </tip>
+    <para>If you choose to upgrade your system using the installation
+      program, any software not provided by &DISTRO; that conflicts with
+      &DISTRO; software is overwritten.  Before you begin an upgrade
+      this way, make a list of your system's current packages for later
+      reference:</para>
+
+    <screen><command><![CDATA[rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH} > ~/old-pkglist.txt']]></command></screen>
+
+    <para>After installation, consult this list to discover which
+      packages you may need to rebuild or retrieve from non-&DISTRO;
+      software repositories.</para>
+    <para>Next, make a backup of any system configuration data:</para>
+
+    <screen><command><![CDATA[su -c 'tar czf /tmp/etc-`date +%F`.tar.gz	/etc'
+mv /tmp/etc-*.tar.gz ~]]></command></screen>
+
+    <para>You should also make a complete backup of any important data
+      before performing an upgrade.  Important data may include the
+      contents of your entire <filename
+	class="directory">/home</filename> directory as well as content
+      from services such as an Apache, FTP, or SQL server, or a source
+      code management system. Although upgrades are not destructive, if
+      you perform one improperly there is a small possibility of data
+      loss.</para>
+    <warning>
+      <title>Storing Backups</title>
+      <para>Note that the above examples store backup materials in a
+	<filename class="directory">/home</filename> directory.  If your
+	<filename class="directory">/home</filename> directory is not a
+	separate partition, <emphasis>you should not follow these
+	  examples verbatim!</emphasis>  Store your backups on another
+	device such as CD or DVD discs or an external hard disk.</para>
+    </warning>
+    <para>For more information on completing the upgrade process later,
+      refer to <xref linkend="sn-finishing-upgrade"/>.</para>
+    </section>
+
   <section id="sn-upgrading-bootloader">
     <title>Upgrading Boot Loader Configuration</title>