Bug 191028

Summary:	Missing documentation on grub/lilo vmlinuz boot
Product:	[Fedora] Fedora Documentation	Reporter:	Sitsofe Wheeler <sitsofe>
Component:	install-guide	Assignee:	Stuart Ellis <stuart>
Status:	CLOSED NOTABUG	QA Contact:	Paul W. Frields <stickster>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	devel	CC:	stickster
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
URL:	http://fedora.redhat.com/docs/fedora-install-guide-en/fc5/ch-intro.html
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-05-08 19:53:56 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sitsofe Wheeler 2006-05-08 09:12:27 UTC

Description of problem:
I think it would be useful if the install guide talked about non-removable media
boots for systems already running grub or lilo. When doing updates of machines
the copying of the install's vmlinuz and initrd into the target machine's /boot
and the editing of grub's menu.1st provide enough to support a network install.

Version-Release number of selected component (if applicable):
Revision 1.28.1

How reproducible:
N/A

Steps to Reproduce:
1. Read
http://fedora.redhat.com/docs/fedora-install-guide-en/fc5/sn-before-begin.html ,
http://fedora.redhat.com/docs/fedora-install-guide-en/fc5/ch-beginninginstallation.html
,
http://fedora.redhat.com/docs/fedora-install-guide-en/fc5/sn-installing-from-harddrive.html
  
Actual results:
Discusson about CD/DVD/USB/PXE boots.

Expected results:
Discussion of grub/lilo hard disk boots too.

Additional info:

Comment 1 Sitsofe Wheeler 2006-05-08 09:14:25 UTC

I forgot to say that it is probably worth mentioning the "graphical" kernel
option on such boots too.

Comment 2 Stuart Ellis 2006-05-08 19:53:56 UTC

I would be a fairly cautious about this - the current text basically documents
the supported functions of Anaconda, i.e. features that developers would accept
bug reports on if they failed to work correctly.

What you seem to be describing is patching an existing install to bootstrap the
install process, which is pretty cool but not a formally supported feature.

I'd suggest two things: offering a short HOWTO to Fedora Unity, Fedora News, or
another site that carries informal Fedora information; and perhaps filing an RFE
about incorporating an "upgrade mode" into the standard Fedora boot options.