[install-guide/F21-rewrite] add an example syslinux config. Some remarks with todo in there...

Pete Travis immanetize at fedoraproject.org
Sat Sep 6 23:49:09 UTC 2014


commit 60759aab0279d7acba111f7cd70482a45d8b70ef
Author: Pete Travis <immanetize at fedoraproject.org>
Date:   Sat Sep 6 17:49:03 2014 -0600

    add an example syslinux config.  Some remarks with todo in there...

 en-US/Network_based_Installations.xml |   70 +++++++++++++--------------------
 1 files changed, 27 insertions(+), 43 deletions(-)
---
diff --git a/en-US/Network_based_Installations.xml b/en-US/Network_based_Installations.xml
index 708d528..ba30bff 100644
--- a/en-US/Network_based_Installations.xml
+++ b/en-US/Network_based_Installations.xml
@@ -203,61 +203,45 @@
               </step>
             </procedure>
 
-
-
-
-
-
-                   <step>
-                        <para>
-                            Add a configuration file to the <filename class="directory">pxelinux/</filename> directory. The file name should either be <literal>default</literal>, or based on the system's IP address. For example, if your machine's IP address is 10.0.0.1, the file name will be <filename>0A000001</filename>.
-                        </para>
-                        <para>
-                            A sample configuration file at <filename>/var/lib/tftpboot/pxelinux/default</filename> might look like:
-                        </para>
-                        <programlisting>
+            <procedure>
+              <title>Configuring client bootloaders</title>
+              <step>
+                <para>Create a boot menu for BIOS clients at <filename>/var/lib/tftpboot/pxelinux/default</filename>.</para>
+                <remark>needs adminition about kickstarts here somewhere, and testing of pulling .ks out of cgit</remark>
+                <remark>Need to check if the product media ships different or incompatible initramfsen</remark>
+                <programlisting>
 default vesamenu.c32
 prompt 1
 timeout 600
 
-display boot.msg
-
 label linux
-  menu label ^Install system
+  menu label ^Install Fedora &PRODVER; 64-bit
   menu default
-  kernel vmlinuz
-  append initrd=initrd.img ip=dhcp inst.repo=http://10.32.5.1/mnt/archive/Fedora/&PRODVER;/Server/x86_64/os/
-label vesa
-  menu label Install system with ^basic video driver
-  kernel vmlinuz
-  append initrd=initrd.img ip=dhcp inst.xdriver=vesa nomodeset inst.repo=http://10.32.5.1/mnt/archive/Fedora/&PRODVER;/Server/x86_64/os/
+  kernel f&PRODVER;/vmlinuz
+  append initrd=f&PRODVER;/initrd.img ip=dhcp inst.repo=http://download.fedoraproject.org/pub/fedora/linux/releases/&PRODVER;/Everything/x86_64/os/
+
+label server
+  menu label ^Install Fedora &PRODVER; Server
+  menu default
+  kernel f&PRODVER;/vmlinuz
+  append initrd=f&PRODVER;/initrd.img ip=dhcp ks=https://git.fedorahosted.org/cgit/spin-kickstarts.git/plain/fedora-install-server.ks?h=f21
+
 label rescue
   menu label ^Rescue installed system
   kernel vmlinuz
-  append initrd=initrd.img rescue
+  append initrd=initrd.img rescue root=live:http://dl.fedoraproject.org/pub/fedora/linux/releases/&PRODVER;/Fedora/x86_64/os/LiveOS/squashfs.img rescue
+
 label local
   menu label Boot from ^local drive
   localboot 0xffff
-                        </programlisting>
-                        <important>
-                            <para>
-                                The <option>inst.repo=</option> <application>Anaconda</application> option, shown in the example above, must always be used to specify the installation program's image as well as the installation source. Without this option, the installation program will be unable to boot. For more information about boot options for <application>Anaconda</application>, see <xref linkend="sect-boot-options-installer" />.
-                            </para>
-                        </important>
-                    </step>
-                    <step>
-                        <para>
-                            Copy the boot images into your <command>tftp/</command> root directory:
-                        </para>
-                        <screen>
-<prompt>#</prompt> <command>cp /<replaceable>path/to</replaceable>/x86_64/os/images/pxeboot/{vmlinuz,initrd.img} /var/lib/tftpboot/pxelinux/</command>
-                        </screen>
-                    </step>
-               </procedure>
-                <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.
-                </para>
-            </section>
+                </programlisting>
+              </step>
+                
+
+
+
+
+
 
                    <step>
                         <para>


More information about the docs-commits mailing list