[Bug 1224964] New: Kickstart file is not defined. Suggest a rewarding as shown
bugzilla at redhat.com
bugzilla at redhat.com
Tue May 26 09:59:46 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1224964
Bug ID: 1224964
Summary: Kickstart file is not defined. Suggest a rewarding as
shown
Product: Fedora Documentation
Version: devel
Component: installation-quick-start-guide
Severity: low
Assignee: pbokoc at redhat.com
Reporter: lsatenstein at yahoo.com
QA Contact: docs-qa at lists.fedoraproject.org
CC: pbokoc at redhat.com, zach at oglesby.co
Description of problem:
PDF File Introduction reads
This manual explains how to boot the Fedora installation program,
Anaconda
, and how to install
Fedora 22 on 32 and 64-bit AMD and Intel systems. It also covers advanced
installation methods such
as automated Kickstart installations, booting the installation from a network
location, remote access
to the installation system using VNC, and system upgrades from previous
versions of Fedora. It also
describes common post-installation tasks and explains how to troubleshoot
common issues related to
the installation.
Version-Release number of selected component (if applicable):
How reproducible:
What is a Kickstart?
Expected results:
Add text "parameter file" following Kickstart as follows
This manual explains how to boot the Fedora installation program,
Anaconda
, and how to install
Fedora 22 on 32 and 64-bit AMD and Intel systems. It also covers advanced
installation methods such
as automated Kickstart parameter file installations, booting the installation
from a network location, remote access
to the installation system using VNC, and system upgrades from previous
versions of Fedora. It also
describes common post-installation tasks and explains how to troubleshoot
common issues related to
the installation.
Additional info:
Kickstart is not an industry term, it is specific to and an anaconda parameter
file
VNC is an industrial term so it needs no qualification.
--
You are receiving this mail because:
You are the QA Contact for the bug.
More information about the docs-qa
mailing list