[install-guide/f21-branch] revhistory bump
by Pete Travis
commit 68106577b45dfa7e1d885ae391242d35ad69ab17
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Sun Dec 7 23:39:44 2014 -0700
revhistory bump
en-US/Revision_History.xml | 36 ++++++++++++++++++++++++++----------
1 files changed, 26 insertions(+), 10 deletions(-)
---
diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml
index fad7590..bb40d15 100644
--- a/en-US/Revision_History.xml
+++ b/en-US/Revision_History.xml
@@ -1,31 +1,47 @@
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
-%BOOK_ENTITIES;
]>
<appendix id="appe-Publican-Revision_History">
<title>Revision History</title>
- <para>
+ <para>
Note that revision numbers relate to the edition of this manual, not to version numbers of Fedora.
</para>
- <simpara>
+ <simpara>
<revhistory>
<revision>
- <revnumber>1.0-0</revnumber>
- <date>Tue Dec 17 2013</date>
+ <revnumber>1.0-1</revnumber>
+ <date>Mon Dec 8 2014</date>
<author>
- <firstname>Petr</firstname>
- <surname>Bokoč</surname>
- <email>pbokoc(a)redhat.com</email>
+ <firstname>Pete</firstname>
+ <surname>Travis</surname>
+ <email>immanetize(a)fedoraproject.org</email>
</author>
<revdescription>
<simplelist>
+ <member>added info on media types</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
+ <revnumber>1.0-0</revnumber>
+ <date>Tue Dec 17 2013</date>
+ <author>
+ <firstname>Petr</firstname>
+ <surname>Bokoč</surname>
+ <email>pbokoc(a)redhat.com</email>
+ </author>
+ <revdescription>
+ <simplelist>
<member>Publishing for Fedora 20</member>
+
</simplelist>
+
</revdescription>
+
</revision>
+
</revhistory>
+
</simpara>
</appendix>
-
9 years, 5 months
[release-notes: 2/3] adding revision
by Pete Travis
commit 5ed3c6758361cc2923f1c53556e42972c1069a16
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Sun Dec 7 18:56:18 2014 -0700
adding revision
en-US/Revision_History.xml | 14 +++++++++++++-
1 files changed, 13 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml
index bcec7b7..c578414 100644
--- a/en-US/Revision_History.xml
+++ b/en-US/Revision_History.xml
@@ -7,7 +7,19 @@
<title>Revision History</title>
<simpara>
<revhistory>
- <revision>
+ <revision>
+ <revnumber>21-09</revnumber>
+ <date>Sun 7 Dec 2014</date>
+ <author><firstname>Fedora</firstname><surname>Docs</surname><email>docs AT lists.fedoraproject.org</email></author>
+ <revdescription>
+ <simplelist>
+ <member>
+ Added a lot of content.
+ </member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
<revnumber>21-01</revnumber>
<date> Fri 29 August 2014</date>
<author><firstname>Fedora</firstname><surname>Docs</surname><email>docs AT lists.fedoraproject.org</email></author>
9 years, 5 months
[release-notes: 1/3] varieties of Cloud images
by Pete Travis
commit 7b5c47b7fb92810e40a3a224811a09614e83f1b8
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Tue Nov 25 00:03:54 2014 -0700
varieties of Cloud images
en-US/Products-Cloud.xml | 22 +++++++++++++++++++++-
1 files changed, 21 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Products-Cloud.xml b/en-US/Products-Cloud.xml
index 65a6b99..560b39e 100644
--- a/en-US/Products-Cloud.xml
+++ b/en-US/Products-Cloud.xml
@@ -6,7 +6,27 @@
<section id="Products-Cloud">
<title>Fedora Cloud</title>
- <para />
+ <para>
+ Fedora Cloud is the base building block of the Fedora flavors, ready to be deployed on the fly to meet your changing needs. These small images are backed by the vast set of applications and utilities available in the Fedora package repositories.
+ </para>
+ <para>
+ Cloud images are available in two varieties:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Base</term>
+ <listitem><para>
+ Just the basics, this image is ready to be customized for your needs.
+ </para></listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Atomic</term>
+ <listitem><para>
+ Cutting edge <ulink url="http://www.projectatomic.io/">Project Atomic</ulink> tools make this image the ideal host for Docker containers.
+ </para></listitem>
+ </varlistentry>
+ </variablelist>
+
<!-- ImageFactory Builds? -->
<!-- Official Docker Image -->
9 years, 5 months
[install-guide/f21-branch] bump zt project version
by Pete Travis
commit aff15d446994950d60e4ff48c5887be5094468f2
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Sun Dec 7 18:40:36 2014 -0700
bump zt project version
zanata.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/zanata.xml b/zanata.xml
index aa47a67..9a2e532 100644
--- a/zanata.xml
+++ b/zanata.xml
@@ -2,7 +2,7 @@
<config xmlns="http://zanata.org/namespace/config/">
<url>https://translate.zanata.org/zanata/</url>
<project>fedora-installation-guide</project>
- <project-version>f17</project-version>
+ <project-version>f21</project-version>
<project-type>podir</project-type>
<locales>
9 years, 5 months
[install-guide/f21-branch] flavors, spins, and isos
by Pete Travis
commit ebac0a7642c0a3cd100b7888d1c68b074e4511b9
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Sun Dec 7 18:32:08 2014 -0700
flavors, spins, and isos
en-US/Downloading_Fedora.xml | 88 ++++++++++++++++++++++++++++++++-
en-US/Preparing_for_Installation.xml | 2 +-
2 files changed, 86 insertions(+), 4 deletions(-)
---
diff --git a/en-US/Downloading_Fedora.xml b/en-US/Downloading_Fedora.xml
index a8ce5bc..fdb1026 100644
--- a/en-US/Downloading_Fedora.xml
+++ b/en-US/Downloading_Fedora.xml
@@ -5,7 +5,89 @@
]>
<chapter id="chap-downloading-fedora">
<title>Downloading Fedora</title>
- <para>
- text
- </para>
+ <bridgehead>Fedora Flavors</bridgehead>
+ <para>
+ Fedora provides three primary flavors tailored for some specific use cases. <ulink url="https://getfedora.org" /> offers Fedora Cloud for scalable infrastructure, Fedora Server for organizational infrastructure, and Fedora Workstation for the developer and desktop user.
+ </para>
+ <para>
+ For alternative desktop environments or media built for more niche purposes, check out <ulink url="https://spins.fedoraproject.org">Fedora Spins</ulink>.
+ </para>
+ <para>
+ Each of these downloads provides a different set of default packages, but you can add to your system after the initial installation to customize it for your needs. The installation process is the same for all spins and flavors, so you can use this guide for any choice you make.
+ </para>
+ <bridgehead>Media Types</bridgehead>
+ <para>
+ Several media types are available. Choose the one that best suits your requirements.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Live Image</term>
+ <listitem>
+ <para>
+ Live images allow you to preview Fedora before installing it. Instead of booting directly into the installer, a live image loads the same environment you'll get after installation. Fedora Workstation and Fedora Spins are live images.
+ </para>
+ <para>
+ Use a live image to install your favorite system, test Fedora on new hardware, troubleshoot, or share with friends.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>DVD Image</term>
+ <listitem>
+ <para>
+ DVD images boot directly into the installation enviroment, and allow you to choose from a variety of packages that are provided with it. In Fedora 21, the DVD option is only available in the <productname>Fedora Server</productname> flavor.
+ </para>
+ <para>
+ Use the Fedora Server DVD image when you want customized Fedora Server installations using an offline installation source.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>netinstall Image</term>
+ <listitem>
+ <para>
+ The netinstall image boots directly into the installation environment, and uses the online Fedora package repositories as the installation source. With a netinstall image, you can select a wide variety of packages to create a customized installation of Fedora.
+ </para>
+ <para>
+ The Fedora Server netinstall image is a universal one, and can be used to install any Fedora flavor or your own set of favorite packages.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>ARM images</term>
+ <listitem>
+ <para>
+ For many ARM systems, Fedora provides preconfigured filesystem images. Write the image to removable media and boot directly into a Fedora installation that's ready to use.
+ </para>
+ <para>
+ ARM devices often require special setup procedures that aren't covered in this guide. Start learning about Fedora ARM at <ulink url="https://fedoraproject.org/wiki/Architectures/ARM" />
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Cloud Images</term>
+ <listitem>
+ <para>
+ Fedora Cloud images are preconfigured filesystem images with very few packages installed by default. They include special tools for interacting with cloud platforms, and are not intended to be used outside of cloud environments.
+ </para>
+ <para>
+ Fedora Cloud comes in several varieties. The Fedora Cloud Base image is a minimal base for cloud deployments. The Fedora Cloud Atomic image is a Docker container host that uses <ulink url="http://www.projectatomic.io/">Project Atomic</ulink> technology for updates. A Docker base image for Fedora is also available.
+ </para>
+ <para>
+ Cloud images are preconfigured and do not require installation as described in this guide. Get started using Fedora Cloud at <ulink url="http://fedoraproject.org/wiki/Cloud" />
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Boot Images</term>
+ <listitem>
+ <para>
+ The tiny images at <ulink url="https://boot.fedoraproject.org/" /> are written to CDs, USB drives, or even floppy disks. The BFO image loads installation media from Fedora's servers and directly loads an installation environment, like the netinstall ISO.
+ </para>
+ <para>
+ BFO images work like PXE deployments, without having to set up a server.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</chapter>
diff --git a/en-US/Preparing_for_Installation.xml b/en-US/Preparing_for_Installation.xml
index 68d9f4b..d3d9b51 100644
--- a/en-US/Preparing_for_Installation.xml
+++ b/en-US/Preparing_for_Installation.xml
@@ -59,7 +59,7 @@
The Fedora Project offers different flavors for tailored for some specific use cases. Choose the Fedora flavor best for you, or you can build your own by customizing after the installation, or by using a kickstart file as described in <xref linkend="sect-kickstart-file-create" />.
</para>
<para>
- Learn more about Fedora Workstation, Fedora Cloud, and Fedora Server at <ulink url="http://getfedora.org" />.
+ Read more about Fedora Workstation, Fedora Cloud, Fedora Server and the available media types in <xref linkend="chap-downloading-fedora" />.
</para>
<para>
You can also choose a Fedora <literal>Spin</literal> featuring favorite alternative desktops or tools for specialized tasks at <ulink url="http://spins.fedoraproject.org" />
9 years, 5 months
[install-guide/f21-branch] Adding the Downloading Fedora chapter
by pbokoc
commit d66b62d69f9b7bafa594ecfb2c8bb5491b1b8768
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Sun Dec 7 21:08:19 2014 +0100
Adding the Downloading Fedora chapter
en-US/Downloading_Fedora.xml | 11 +++++++++++
en-US/Installation_Guide.xml | 1 +
2 files changed, 12 insertions(+), 0 deletions(-)
---
diff --git a/en-US/Downloading_Fedora.xml b/en-US/Downloading_Fedora.xml
new file mode 100644
index 0000000..a8ce5bc
--- /dev/null
+++ b/en-US/Downloading_Fedora.xml
@@ -0,0 +1,11 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<chapter id="chap-downloading-fedora">
+ <title>Downloading Fedora</title>
+ <para>
+ text
+ </para>
+</chapter>
diff --git a/en-US/Installation_Guide.xml b/en-US/Installation_Guide.xml
index f5e4cdf..df7a254 100644
--- a/en-US/Installation_Guide.xml
+++ b/en-US/Installation_Guide.xml
@@ -7,6 +7,7 @@
<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Downloading_Fedora.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<part id="part-installing-fedora">
<title>Installing &PRODUCT;</title>
9 years, 5 months
[install-guide/f21-branch] Fixing a broken build
by pbokoc
commit daf06e012daa206db2a7023940949f542397bc34
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Sun Dec 7 21:08:08 2014 +0100
Fixing a broken build
en-US/Kickstart_Installations.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Kickstart_Installations.xml b/en-US/Kickstart_Installations.xml
index f124930..89ddc9f 100644
--- a/en-US/Kickstart_Installations.xml
+++ b/en-US/Kickstart_Installations.xml
@@ -151,7 +151,7 @@
Normally, a Kickstart file is copied to removable media or a hard drive, or made available on the network. Placing the file in a network location complements the usual approach to Kickstart installations, which is also network-based: the system is booted using a PXE server, the Kickstart file is downloaded from a network share, and software packages specified in the file are downloaded from remote repositories.
</para>
<para>
- <xref linkend=chap-pxe-server-setup"" /> offers some additional information about preparing for a network-based installation.
+ <xref linkend="chap-pxe-server-setup" /> offers some additional information about preparing for a network-based installation.
</para>
</section>
9 years, 5 months
[install-guide/f21-branch] Adding a screenshot to text mode + removing additional TODOs
by pbokoc
commit aa925b7ccea1ed2f306560ca9f2c0f62ea58891f
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Sun Dec 7 20:54:26 2014 +0100
Adding a screenshot to text mode + removing additional TODOs
en-US/CustomSpoke_PartitioningAdvice.xml | 2 +-
en-US/Installing_Using_Anaconda.xml | 16 +++++++++++++---
en-US/Kickstart_Installations.xml | 2 +-
en-US/images/anaconda/SummaryHub_TextMode.png | Bin 0 -> 64809 bytes
4 files changed, 15 insertions(+), 5 deletions(-)
---
diff --git a/en-US/CustomSpoke_PartitioningAdvice.xml b/en-US/CustomSpoke_PartitioningAdvice.xml
index b453371..4e8c6ca 100644
--- a/en-US/CustomSpoke_PartitioningAdvice.xml
+++ b/en-US/CustomSpoke_PartitioningAdvice.xml
@@ -66,7 +66,7 @@
</listitem>
<listitem>
<para>
- If you need to make any changes to your storage configuration after the installation, &PRODUCT; repositories offer several different tools which can help you do this. If you prefer a command line tool, try <package>system-storage-manager</package>. <remark>TODO: recommend a GUI tool? blivet-gui, maybe?</remark>
+ If you need to make any changes to your storage configuration after the installation, &PRODUCT; repositories offer several different tools which can help you do this. If you prefer a command line tool, try <package>system-storage-manager</package>.
</para>
</listitem>
</itemizedlist>
diff --git a/en-US/Installing_Using_Anaconda.xml b/en-US/Installing_Using_Anaconda.xml
index f3924b3..47dbae5 100644
--- a/en-US/Installing_Using_Anaconda.xml
+++ b/en-US/Installing_Using_Anaconda.xml
@@ -154,9 +154,19 @@
<para>
There are two alternatives to text mode which can both be used even if the installation system does not have a graphical display. You can either connect to the installation system using VNC and perform an interactive graphical installation remotely (see <xref linkend="chap-vnc-installations" />), or you can create a Kickstart file to perform the installation automatically (see <xref linkend="chap-kickstart-installations" />).
</para>
- <para>
- <remark>TODO: screen of text mode hub</remark>
- </para>
+ <figure>
+ <title>Text Mode Installation</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/anaconda/SummaryHub_TextMode.png" format="PNG" scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>
+ The main menu in during a text-based installation.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
<para>
Installation in text mode follows a pattern similar to the graphical installation: There is no single fixed progression; you can configure many settings in any order you want using the main status screen. Screens which have already been configured, either automatically or by you, are marked as <literal>[x]</literal>, and screens which require your attention before the installation can begin are marked with <literal>[!]</literal>. Available commands are displayed below the list of available options.
</para>
diff --git a/en-US/Kickstart_Installations.xml b/en-US/Kickstart_Installations.xml
index 2fc9c5f..f124930 100644
--- a/en-US/Kickstart_Installations.xml
+++ b/en-US/Kickstart_Installations.xml
@@ -151,7 +151,7 @@
Normally, a Kickstart file is copied to removable media or a hard drive, or made available on the network. Placing the file in a network location complements the usual approach to Kickstart installations, which is also network-based: the system is booted using a PXE server, the Kickstart file is downloaded from a network share, and software packages specified in the file are downloaded from remote repositories.
</para>
<para>
- <remark>TODO: link this with the PXE chapter, and maybe provide a procedure about how to create a new partition on a bootable USB with a netinst iso and put a Kickstart on it</remark>
+ <xref linkend=chap-pxe-server-setup"" /> offers some additional information about preparing for a network-based installation.
</para>
</section>
diff --git a/en-US/images/anaconda/SummaryHub_TextMode.png b/en-US/images/anaconda/SummaryHub_TextMode.png
new file mode 100644
index 0000000..be0ea51
Binary files /dev/null and b/en-US/images/anaconda/SummaryHub_TextMode.png differ
9 years, 5 months