[readme-burning-isos/f19: 1/2] pulling new changes to f19 release branch

Pete Travis immanetize at fedoraproject.org
Sat Jul 6 03:34:56 UTC 2013


commit 615a01fdb415e1dabfd48ffa2a670b37a6d13b16
Author: Pete Travis <immanetize at fedoraproject.org>
Date:   Fri Jul 5 21:28:51 2013 -0600

    pulling new changes to f19 release branch

 en-US/Article_Info.xml               |    2 +-
 en-US/Burning.xml                    |   12 ++--
 en-US/Burning_ISO_images_to_disc.ent |    4 +-
 en-US/Downloading.xml                |  114 +++++++++++++++++++++++++++++++---
 en-US/Revision_History.xml           |   21 ++++++
 en-US/Validating.xml                 |   23 +++----
 6 files changed, 147 insertions(+), 29 deletions(-)
---
diff --git a/en-US/Article_Info.xml b/en-US/Article_Info.xml
index 47b8995..41ea5fe 100644
--- a/en-US/Article_Info.xml
+++ b/en-US/Article_Info.xml
@@ -6,7 +6,7 @@
 	<title>Burning ISO images to disc</title>
 	<subtitle>How to download ISO images and create CD and DVD media</subtitle>
 	<productname>Fedora</productname>
-	<productnumber>17</productnumber>
+	<productnumber>19</productnumber>
 	<edition>1</edition>
 	<pubsnumber>0</pubsnumber>
 	<abstract>
diff --git a/en-US/Burning.xml b/en-US/Burning.xml
index fce6b06..898d4d3 100644
--- a/en-US/Burning.xml
+++ b/en-US/Burning.xml
@@ -40,7 +40,7 @@
 		<section id="sect-Burning_ISO_images_to_disc-Burning-Windows-old">
 			<title>Burning discs with older Windows operating systems</title>
 			<para>
-				The CD burning feature built into Windows XP and Windows&nbsp;Vista cannot burn CDs from images and Windows operating systems before Windows&nbsp;XP did not have any built-in CD burning capability at all. Therefore, to turn an ISO image files into a CD or DVD on Windows operating systems prior to Windows&nbsp;7, you need separate disc burning software that can handle ISO image files.  Although this is true of most disc burning software, exceptions exist.
+				The CD burning feature built into Windows XP and Windows&nbsp;Vista cannot burn CDs from images and Windows operating systems before Windows&nbsp;XP did not have any built-in CD burning capability at all. Therefore, to turn an ISO image files into a CD or DVD on Windows operating systems prior to Windows&nbsp;7, you need separate disc burning software that can handle ISO image files.
 			</para>
 			<para>
 				Examples of popular CD burning software for Windows that you might already have on your computer include <application>InfraRecorder</application>, <application>Nero Burning ROM</application>, and <application>Roxio Creator</application>. If you use a Windows operating system on your computer and do not have disc burning software installed (or you are not sure that the software can burn discs from image files) <application>InfraRecorder</application> is a suitable solution available from <ulink url="http://www.infrarecorder.org/"></ulink>, and is free and open-source. 
@@ -51,12 +51,12 @@
 			<section id="sect-Burning_ISO_images_to_disc-Burning-Using_InfraRecorder">
 				<title>Using InfraRecorder</title>
 				<para>
-					Obtain and install InfraRecorder from the <ulink url="http://infrarecorder.org"></ulink> web site.
+					Obtain and install <application>InfraRecorder</application> from the <ulink url="http://infrarecorder.org"></ulink> web site.
 				</para>
 				<procedure>
 					<step>
 						<para>
-                                                        Start <guilabel>InfraRecorder</guilabel>.
+                                                        Start <application>InfraRecorder</application>.
                                                 </para>
                                         </step>
                                         <step>
@@ -76,7 +76,7 @@
                                         </step>
 					<step>
 						<para>
-							Select 4X as the write speed.
+							Select <literal>4X</literal> as the write speed.
 						</para>
 					</step>
 					<step>
@@ -351,12 +351,12 @@ wodim: Overview of accessible drives (1 found) :
 			       Using the output from above identify your drive location. In this example it would be /dev/scd0, and issue the following command to burn the cd. 
 			     </para>
 			     <para>
-			       <command>wodim -v dev=/dev/xxx speed=4 -eject /path/to/Fedora.iso</command>.
+			       <command>wodim -v <replaceable>dev=/dev/xxx</replaceable> speed=4 -eject <replaceable>/path/to/Fedora.iso</replaceable></command>.
 			     </para>
 			       <note>
 				 <title>Replace values</title>
 				 <para>
-				   Be sure to replace the dev=/dev/xxx with your drive path, and /path/to/Fedora.iso to the actual path and name of the ISO file
+				   Be sure to replace the <replaceable>dev=/dev/xxx</replaceable> with your drive path, and <replaceable>/path/to/Fedora.iso</replaceable> to the actual path and name of the ISO file.
 				 </para>
 			       </note>
 			   </step>
diff --git a/en-US/Burning_ISO_images_to_disc.ent b/en-US/Burning_ISO_images_to_disc.ent
index 3a63cc1..0b15fc8 100644
--- a/en-US/Burning_ISO_images_to_disc.ent
+++ b/en-US/Burning_ISO_images_to_disc.ent
@@ -1,6 +1,6 @@
 <!ENTITY PRODUCT "Fedora Documentation">
 <!ENTITY BOOKID "readme-burning-isos">
-<!ENTITY YEAR "2012">
+<!ENTITY YEAR "2013">
 <!ENTITY HOLDER "Fedora Project Contributors">
-<!ENTITY PRODVER "17">
+<!ENTITY PRODVER "19">
 
diff --git a/en-US/Downloading.xml b/en-US/Downloading.xml
index ec000d2..5dcd870 100644
--- a/en-US/Downloading.xml
+++ b/en-US/Downloading.xml
@@ -19,7 +19,18 @@
 		<para>
 			The ISO files are large, so it might take a long time to download them, especially using a dial-up modem. If you have a slow connection to the Internet, consider using a download manager. Download managers typically enable you to pause and recommence the download at convenient times and to resume a download that was interrupted.
 		</para>
-	</section>
+		<example>
+		  <title>Resuming a download with <command>wget</command></title>
+		  <para>The linux utility <command>wget</command> can resume interrupted downloads. A command such as the one below will download a Fedora image, and can be executed again to continue the download if needed.
+                  </para>
+                  <screen>
+<command>
+wget --continue http://download.fedoraproject.org/pub/fedora/linux/releases/19/Fedora/x86_64/Fedora-19-x86_64-netinst.iso
+</command>
+                  </screen>
+                </example>
+        </section>
+        <!-- This section doesn't transition well with the change to USB media target sizes, and seems targeted for a past audience. The table and information in the next chapter should carry the intent over.
 	<section id="sect-Burning_ISO_images_to_disc-Downloading-Choosing_CD_or_DVD">
 		<title>Choosing CD or DVD</title>
 		<para>
@@ -54,21 +65,108 @@
 		<para>
 			Create a new directory where you can download the files that you need. You need approximately 700&nbsp;MB of free space available for each CD-sized ISO file, or approximately 3.5&nbsp;GB for the DVD-sized ISO file.
 		</para>
-	</section>
+	</section> -->
 	<section id="sect-Burning_ISO_images_to_disc-Downloading-Choosing_the_ISO_Files">
 		<title>Choosing the ISO Files</title>
+                <para>
+		  Fedora is distributed as a single DVD-sized ISO image file, smaller 1GB <literal>spin</literal> ISO image files, or as a <literal>netinstall</literal> image. Refer to the Fedora Live Images guide at <ulink url="http://docs.fedoraproject.org" /> to learn more about spins.
+                </para>
+ <table frame="all">
+                  <title>Comparing image types</title>
+                  <tgroup align="left" cols="2" colsep="1" rowsep="1">
+                    <colspec colname="image-type" colnum="1" />
+                    <colspec colname="image-attributes" colnum="2" />
+                    <thead>
+                      <row>
+                        <entry>Image type</entry>
+                        <entry>Features</entry>
+                      </row>
+                    </thead>
+                    <tbody>
+                      <row>
+                        <entry>
+                          DVD image
+                        </entry>
+                        <entry>
+                          <simplelist>
+                            <member>
+                              Sized for 3.5&nbsp;GB DVD media and 4&nbsp;GB or larger USB media.
+                            </member>
+                            <member>
+                              Offers the most flexible installation options. 
+                            </member>
+                            <member>
+                              Suited for customized installs, offline use, and low memory systems.
+                            </member>
+                          </simplelist>
+                        </entry>
+                      </row>
+                      <row>
+                        <entry>
+                          <literal>netinstall</literal> image
+                        </entry>
+                        <entry>
+                          <simplelist>
+                            <member>
+                              Sized for CD media and 512&nbsp;MB or larger USB media.
+                            </member>
+                            <member>
+                              Offers flexible installation options, downloads latest packages during installation.
+                            </member>
+                            <member>
+                              Suited for customized installs, network deployment, and metered bandwidth connections.
+                            </member>
+                          </simplelist>
+                        </entry>
+                      </row>
+                      <row>
+                        <entry>
+                          Spin images
+                        </entry>
+                        <entry>
+                          <simplelist>
+                            <member>
+                              Sized for 1&nbsp;GB USB media or larger optical media.
+                            </member>
+                            <member>
+                              Various spin images offer a live preview of the desktop environment they represent. They install only the features available from the spin, but can be added to after installation.
+                            </member>
+                            <member>
+                              Suitable for demonstrations or installing a specific desktop environment.
+                            </member>
+                          </simplelist>
+                        </entry>
+                      </row>
+                    </tbody>
+                  </tgroup>
+                </table>
+                <note>
+                  <title>File size limits</title>
+                  <para>	
+                    A <firstterm>file system</firstterm> is a method that your computer uses to organize the files and data on its storage devices. Older file systems, notably <systemitem class="filesystem">FAT32</systemitem>, cannot handle large files like the DVD image.  If downloading with such a system, you should choose a smaller image.
+                  </para>
+                </note>
 		<para>
-			The exact files you need from the download server depend upon your system and the version of Fedora you are downloading. The files you need are named in the form of <filename>Fedora-<replaceable>&lt;version&gt;</replaceable>-<replaceable>&lt;arch&gt;</replaceable>-disc<replaceable>&lt;count&gt;</replaceable>.iso</filename>, where "<replaceable>&lt;version&gt;</replaceable>" is the version of Fedora you wish to download, "<replaceable>&lt;arch&gt;</replaceable>" is your computer's processor architecture, and "<replaceable>&lt;count&gt;</replaceable>" is the disc number for each of the installation CDs. In the case of an installation DVD, <filename>DVD</filename> is used in the filename.
+			The exact files you need from the download server depend upon your system and the version of Fedora you are downloading. The file names will always contain <literal>Fedora</literal>, the release version, the image's target architecture, and the type of image.
 		</para>
+		<example>
+		  <title>Filenames</title>
+		  <para>Default live image</para>
+		  <screen><filename>Fedora-Live-Desktop-x86_64-19-1.iso</filename></screen>
+		  <para>32-bit KDE Spin</para>
+		  <screen><filename>Fedora-Live-Desktop-i686-19-1.iso</filename></screen>
+		  <para>64-bit netinstall image</para>
+		  <screen><filename>Fedora-19-x86_64-netinst.iso</filename></screen>
+		</example>
+		    
+                
+               
 		<para>
-			The computer processor architecture is usually <systemitem>i386</systemitem> for 32-bit PCs, including the Pentium and Athlon processor families. The architecture is usually <systemitem>x86_64</systemitem> for 64-bit PCs, including the Athlon 64 processor family. The architecture is usually <systemitem>ppc</systemitem> for PowerPC computers, including most of Apple's Macintosh offerings before they began using Intel chips in the MacBook. If in doubt, your system probably requires the <systemitem>i386</systemitem> versions.
+			The computer processor architecture is usually <systemitem>i386</systemitem> for 32-bit PCs, including the Pentium and Athlon processor families. The architecture is usually <systemitem>x86_64</systemitem> for 64-bit PCs, including the Athlon 64 processor family. The architecture is usually <systemitem>ppc</systemitem> for PowerPC computers, including most of Apple's Macintosh offerings before they began using Intel chips in the MacBook. If in doubt, your system probably requires the <systemitem>x86_64</systemitem> versions.
 		</para>
 		<para>
 			For example, if downloading Fedora &PRODVER; for a Pentium 4 computer, the correct file is <filename>Fedora-&PRODVER;-i386-DVD.iso</filename>. You may also need the <filename>CHECKSUM</filename> file to verify that the files you have downloaded are complete and correct.
 		</para>
-		<para>
-			Note that a Fedora Live CD is also available. This disc does not contain all the software packages available on the DVD or set of CDs, but does allow you to try Fedora before you install it to your computer. Refer to the article <citetitle>Fedora Live Images</citetitle> available from <ulink url="http://docs.fedoraproject.org"></ulink> to learn more.
-		</para>
-	</section>
+	      </section>
 
 </section>
diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml
index 19530e4..1297173 100644
--- a/en-US/Revision_History.xml
+++ b/en-US/Revision_History.xml
@@ -6,6 +6,27 @@
 	<title>Revision History</title>
 	<simpara>
 		<revhistory>
+		  <revision>
+		    <revnumber>19</revnumber>
+		    <date>Wed Jul 3 2013</date>
+		    <author>
+		      <firstname>Pete</firstname>
+		      <surname>Travis</surname>
+		      <email>immanetize AT fedoraproject.org</email>
+		    </author>
+		    <revdescription>
+		      <simplelist>
+			<member>
+			  Updated content to reflect targeting of USB media sizes
+			</member>
+			<member>
+			  Added a table for comparing image types.
+			</member>
+		      </simplelist>
+		    </revdescription>
+		  </revision>
+		      
+		      
                          <revision>
                                 <revnumber>17</revnumber>
                                 <date>Mon May 28 2012</date>
diff --git a/en-US/Validating.xml b/en-US/Validating.xml
index 5820ae2..01bd688 100644
--- a/en-US/Validating.xml
+++ b/en-US/Validating.xml
@@ -5,7 +5,7 @@
 <section id="sect-Burning_ISO_images_to_disc-Validating_the_Files">
 	<title>Validating the Files</title>
 	<para>
-		Errors can occur during the download, even if your download manager reports none. Therefore it is <emphasis role="strong">very important</emphasis> to check that the files have not been corrupted in any way. This is the purpose of the <filename>CHECKSUM</filename> file. It contains one line for each of the available ISO files with a content verification code called a <firstterm>hash</firstterm> computed from the original ISO files.
+		Errors can occur during the download, even if your download manager reports none. Therefore it is <emphasis role="strong">very important</emphasis> to check that the files have not been corrupted in any way. This is the purpose of the <filename>CHECKSUM</filename> file. It contains one line for each of the available ISO files with a content verification code, called a <firstterm>hash</firstterm>, computed from the original ISO files.
 	</para>
 
 	<note>
@@ -52,7 +52,7 @@
 			Follow the instructions provided to install the program. When you run the program, use the file selection tools provided to select your downloaded ISO image files. Then select the SHA256 algorithm for calculation, and run the tool. The program takes some time to complete, since it must read the entire ISO file.
 		</para>
 		<para>
-			If you are using HashTab, you will need to enable the SHA256 checksum option. In order to do this you will to open the File Properties window (right click --> File Hashes tab --> Settings), then select the SHA256 option. It is advisable to uncheck any preselected hash options as they will only slow down the hash calculations.
+			If you are using HashTab, you will need to enable the SHA256 checksum option. In order to do this open the File Properties window (right click --> File Hashes tab --> Settings), then select the SHA256 option. It is advisable to uncheck any preselected hash options as they will only slow down the hash calculations.
 		</para>
 		<para>
 			Open the file <filename>CHECKSUM</filename> with a text editor, such as <application>Notepad</application>, to display its contents. Make sure the hash displayed by the hash tool for <emphasis role="strong">each</emphasis> of the downloaded ISO files <emphasis role="strong">exactly</emphasis> matches the corresponding hash in the <filename>CHECKSUM</filename> file.
@@ -65,15 +65,14 @@
 	<section id="sect-Burning_ISO_images_to_disc-Validating_the_Files-Validating_at_the_Windows_Command_Prompt">
 		<title>Validating at the Windows Command Prompt</title>
 		<para>
-			To check the files using the command prompt, download the program <filename>sha256sum.exe</filename> available from <ulink url="http://www.labtestproject.com/files/win/sha256sum/sha256sum.exe"></ulink>. If you have any problems accessing sha256sum.exe, you can try to grab <filename>md5sum.exe</filename> from <ulink url="http://etree.org/software.html"></ulink>. If you have downloaded <filename>md5sum.exe</filename> be sure to substitute for the correct tool below.
+			To check the files using the command prompt, download the program <filename>sha256sum.exe</filename> available from <ulink url="http://www.labtestproject.com/files/win/sha256sum/sha256sum.exe"></ulink>. If you have any problems accessing <filename>sha256sum.exe</filename>, you can try to grab <filename>md5sum.exe</filename> from <ulink url="http://etree.org/software.html"></ulink>. If you have downloaded <filename>md5sum.exe</filename> be sure to substitute for the correct tool below.
 		</para>
 		<para>
 			The <filename>sha256sum.exe</filename> program computes and displays hashes. To use it, save <filename>sha256sum.exe</filename> to the same directory as the ISO files. Select <guilabel>Run...</guilabel> from the Start menu and then enter <userinput>cmd</userinput> for the name of the program to start a <application>Command Prompt</application> window. Then change into the download directory. Run <command>sha256sum</command> with each ISO file like this:
 		</para>
-		
-		<screen>cd "C:\Documents and Settings\Owner\My Documents\My Downloads\Fedora"
-		sha256sum.exe Fedora-&PRODVER;-i386-DVD.iso
-		</screen>
+<screen><command>cd "C:\Documents and Settings\Owner\My Documents\My Downloads\Fedora"</command>
+<command>sha256sum.exe Fedora-&PRODVER;-i386-DVD.iso</command>
+</screen>
 		<para>
 			The program takes some time to complete, since it must read the entire ISO file.
 		</para>
@@ -91,7 +90,7 @@
 			To check the files, download the program <application>HashTab</application> available from <ulink url="http://beeblebrox.org/"></ulink>.
 		</para>
 		<para>
-			Drag each Fedora image file that you want to validate, and drop it to <application>HashTab</application>. Take note of the SHA256 value that <application>HashTab</application> displays.
+			Drag each Fedora image file that you want to validate, and drop it onto <application>HashTab</application>. Take note of the SHA256 value that <application>HashTab</application> displays.
 		</para>
 		<para>
 			Open the file <filename>CHECKSUM</filename> with a text editor, such as <application>TextEdit</application>, to display its contents. Make sure the hash displayed by <application>HashTab</application> for <emphasis role="strong">each</emphasis> of the downloaded ISO files <emphasis role="strong">exactly</emphasis> matches the corresponding hash in the <filename>CHECKSUM</filename> file.
@@ -100,8 +99,8 @@
 			To validate the files from the command line, use the <command>shasum</command> command. In order to correctly validate the files, the 256-bit algorithm must be specified. Change into the directory that holds the ISO image files, then run <command>shasum</command>. For example:
 		</para>
 		<screen>
-			<command>cd Desktop</command>
-			<command>shasum -a 256 Fedora-&PRODVER;-i386-DVD.iso</command>
+<command>cd Desktop</command>
+<command>shasum -a 256 Fedora-&PRODVER;-i386-DVD.iso</command>
 		</screen>
 		<para>
 			If all of the hashes match, you can burn the ISO file to disc. If a file does not match, download it again.
@@ -119,8 +118,8 @@
 		<para>
 			Change into the directory that holds the ISO image files, then run <command>sha256sum</command>, for example:
 		</para>
-<screen>$ cd Downloads
-$ sha256sum Fedora-&PRODVER;-i386-DVD.iso
+    <screen>$ <command>cd Downloads</command>
+$ <command>sha256sum Fedora-&PRODVER;-i386-DVD.iso</command>
 </screen>
 		<para>
 			Open the file <filename>CHECKSUM</filename> with a text editor, such as <application>gedit</application> or <application>kwrite</application>, to display its contents. Make sure the hash displayed by <application>sha256sum</application> for <emphasis role="strong">each</emphasis> of the downloaded ISO files <emphasis role="strong">exactly</emphasis> matches the corresponding hash in the <filename>CHECKSUM</filename> file.


More information about the docs-commits mailing list