[install-guide/F21-rewrite] get the kernel and initrd from the mirrors. No need to download the whole installation image.

Pete Travis immanetize at fedoraproject.org
Sun Sep 7 01:12:55 UTC 2014


commit bc29285836d9f93e1c4854058cd4dd87d6e8e910
Author: Pete Travis <immanetize at fedoraproject.org>
Date:   Sat Sep 6 19:12:50 2014 -0600

    get the kernel and initrd from the mirrors. No need to download the whole installation image.
    
    the os/images/pxeboot path is new; this should be tested. Also a good idea to ask releng about it, for context.

 en-US/Network_based_Installations.xml |   45 +++++++++++++++++++++-----------
 1 files changed, 29 insertions(+), 16 deletions(-)
---
diff --git a/en-US/Network_based_Installations.xml b/en-US/Network_based_Installations.xml
index d42def6..21df376 100644
--- a/en-US/Network_based_Installations.xml
+++ b/en-US/Network_based_Installations.xml
@@ -265,29 +265,42 @@ label local
 
                   menuentry 'Rescue installed system'  --class fedora --class gnu-linux --class gnu --class os {
                     kernel f&PRODVER;/vmlinuz
-                    append f&PRODVER;/initrd=initrd.img rescue root=live:http://dl.fedoraproject.org/pub/fedora/linux/releases/&PRODVER;/Fedora/x86_64/os/LiveOS/squashfs.img rescue
+                    append f&PRODVER;/initrd=initrd.img rescue root=live:http://download.fedoraproject.org/pub/fedora/linux/releases/&PRODVER;/Fedora/x86_64/os/LiveOS/squashfs.img rescue
                     }
                 </programlisting>
               </step>
             </procedure>
           </section>
-
-                        <para>
-                            Copy the boot images into your <command>uefi/</command> directory:
-                        </para>
-                        <screen>
-<prompt>#</prompt> <command>cp /<replaceable>path/to</replaceable>/x86_64/os/images/pxeboot/{vmlinuz,initrd.img} /var/lib/tftpboot/uefi/</command>
-                        </screen>
-                    </step>
-               </procedure>
+          <section id="pxe-kernel">
+            <title>Getting the kernel and initrd</title>
+            <procedure>
+              <title>Downloading the kernel and initrd</title>
+              <step>
                 <para>
-                    After finishing this procedure, the PXE server is ready to start the network installation. You can now start the system you want to install &PRODUCT; on, select PXE Boot when prompted to specify a boot source, and start the network installation.
+                  Create a directory for the files.
                 </para>
-            </section>
-
-        </section>
-
-    </section>
+                <screen>
+                  <command>mkdir -p <filename class="directory" >/var/lib/tftpboot/f&PRODVER;</filename></command>
+                </screen>
+              </step>
+              <step>
+                <para>Download the kernel.</para>
+                <screen>
+                  <command> 
+                    wget http://download.fedoraproject.org/pub/fedora/linux/releases/&PRODVER;/Fedora/x86_64/os/images/pxeboot/vmlinuz -o <filename>/var/lib/tftpboot/f&PRODVER;/vmlinuz</filename>
+                  </command>
+                </screen>
+              </step>
+              <step>
+                <para>Download the initrd</para>
+                <screen>
+                  <command>
+                    wget http://download.fedoraproject.org/pub/fedora/linux/releases/&PRODVER;/Fedora/x86_64/os/images/pxeboot/initrd.img -o <filename>/var/lib/tftpboot/f&PRODVER;/initrd.img</filename>
+                  </command>
+                </screen>
+              </step>
+            </procedure>
+          </section>
     <section id="sect-install-server-cobbler">
       <para>
         For more complex environments, &PRODUCT; offers the <package>cobbler</package> installation server.   Tasks like managing kickstart configurtations, coordinating repositories, maintaining dns records, dhcp servers, and even puppet manifests are effectively automated by <package>cobbler</package>.


More information about the docs-commits mailing list