summaryrefslogtreecommitdiffstats
path: root/bootcd/isolinux-fedora.cfg
blob: 962feda3641b5ce6aff9653e7bb88eb9e9885cb8 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
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=@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=@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