Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1409016

Summary:	Errors in pxe-bootloader page
Product:	[Retired] Fedora Documentation	Reporter:	lf <redhat>
Component:	install-guide	Assignee:	Jaromir Hradilek <jhradile>
Status:	CLOSED EOL	QA Contact:	Fedora Docs QA <docs-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	devel	CC:	pbokoc, zach
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-05-21 09:21:52 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description lf 2016-12-29 00:01:54 UTC

Description of problem:
* `ks=https://git.fedorahosted.org/cgit/spin-kickstarts.git/plain/fedora-install-server.ks?h=f21` is in the uefi cmdline for Server. f21 should read f25.

* `append f25/initrd=initrd.img` is under the uefi rescue configuration. It should probably read `append initrd=f25/initrd.img`.

* inconsistent use of `linuxefi` vs `kernel`. In the section for the installation of Fedora server, it uses `kernel`, whereas for Workstation, it uses `linuxefi`. One of these is almost certainly an error.

Additional info:
Errors found on f25 page (https://docs.fedoraproject.org/en-US/Fedora/25/html/Installation_Guide/pxe-bootloader.html)

Comment 1 lf 2016-12-29 00:03:03 UTC

#1 actually looks like it isn't a problem, though it certainly is confusing to be using an f21 branch for f25 installation.

Comment 2 lf 2016-12-29 00:07:08 UTC

Typo in BIOS config:

`append initrd=f25initrd.img ip=dhcp` should read `append initrd=f25/initrd.img ip=dhcp`

Comment 4 Petr Bokoc 2024-05-21 09:21:52 UTC

The install guide has been retired, therefore I'm closing this bug. 

If you would like to report Fedora docs bugs in the future, please use the "bug" icon on the top right of the affected page, it will take you directly to the appropriate issue tracker.