1 files changed, 63 insertions, 0 deletions
diff --git a/bootcd/isolinux-fedora.cfg b/bootcd/isolinux-fedora.cfg
new file mode 100644
index 0000000..2580b41
--- /dev/null
+++ b/bootcd/isolinux-fedora.cfg
@@ -0,0 +1,63 @@
+#default vesamenu.c32
+default auto
+# Now in 0.1s (i.e. 100 = 10s)
+timeout 100
+
+# Second port, 115200 baud
+#serial 1 115200
+
+
+label auto
+  menu label ^Kickstart Fedora 28
+  kernel vmlinuz
+  append initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-28 @EXTRA@ console=tty1 console=ttyS1,115200 earlyprint=serial,ttyS1,115200 ip=dhcp inst.vnc inst.vncpassword=ipepdv inst.ks=http://ufo.kit.edu/ands/kickstart/fedora/ inst.ks.sendsn inst.ks.sendmac
+
+label local
+  menu label ^Kickstart Locally  Fedora 28
+  kernel vmlinuz
+  append initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-28 @EXTRA@ console=tty1 console=ttyS1,115200 earlyprint=serial,ttyS1,115200 ip=dhcp inst.ks=http://ufo.kit.edu/ands/kickstart/fedora/ inst.ks.sendsn inst.ks.sendmac
+
+label linux
+  menu label ^Install Fedora 28
+  kernel vmlinuz
+  append initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-28 @EXTRA@
+
+label check
+  menu label Test this ^media & install Fedora 28
+  menu default
+  kernel vmlinuz
+  append initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-28 @EXTRA@ rd.live.check
+
+label vesa
+  menu indent count 5
+  menu label Install Fedora 28 in ^basic graphics mode
+  text help
+	Try this option out if you're having trouble installing
+	Fedora 28.
+  endtext
+  kernel vmlinuz
+  append initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-28 @EXTRA@ nomodeset
+
+label rescue
+  menu indent count 5
+  menu label ^Rescue a Fedora system
+  text help
+	If the system will not boot, this lets you access files
+	and edit config files to try to get it booting again.
+  endtext
+  kernel vmlinuz
+  append initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-28 @EXTRA@ rescue
+
+label memtest
+  menu label Run a ^memory test
+  text help
+	If your system is having issues, a problem with your
+	system's memory may be the cause. Use this utility to
+	see if the memory is working correctly.
+  endtext
+  kernel memtest
+
+label hdd
+  menu label Boot from ^local drive
+  localboot 0xffff
+