commit 64c5e147dce3f4dd35a8574682cc2e6b442c7200
Author: Guillermo Gómez <gomix(a)fedoraproject.org>
Date: Tue Dec 31 11:24:09 2013 -0430
Last updates
es-ES/Agradecimientos.xml | 6 +-
es-ES/Configuracion_de_YUM.xml | 14 +-
es-ES/Extensiones_Yum.xml | 60 +------
es-ES/Las_interfases_GUI_de_gnome-packagekit.xml | 6 +-
es-ES/PackageKit_CLI.xml | 18 +--
es-ES/Revision_History.xml | 15 ++
.../Technicas_para_administradores_de_sistemas.xml | 2 +-
es-ES/Utilidades_YUM.xml | 185 ++++----------------
.../Configuracion_de_YUM/yum.conf.prioridad.txt | 2 +-
.../.package-cleanup--oldkernel.txt.swp | Bin 12288 -> 0 bytes
.../.package-cleanup-no-problems.txt.swp | Bin 12288 -> 0 bytes
.../Gnome3-buscando-gpk-application.png | Bin 1164612 -> 857271 bytes
es-ES/yum-plugin/yum-langpacks.xml | 6 +-
lib/tasks/mock.rake | 8 +
14 files changed, 83 insertions(+), 239 deletions(-)
---
diff --git a/es-ES/Agradecimientos.xml b/es-ES/Agradecimientos.xml
index f4e6a9f..a9f1a1f 100644
--- a/es-ES/Agradecimientos.xml
+++ b/es-ES/Agradecimientos.xml
@@ -7,14 +7,14 @@
<title>Agradecimientos</title>
<section>
<title>Personales</title>
- <para>Trabajar para la comunidad implica un sacrificio importante, y a la primera persona que quiero agradecer su soporte, es a mi esposa Elba. Igualmente le pido a Miguel, mi hijo de seis años, que me disculpe por el tiempo que no estuve con él, pero estoy seguro que en el futuro sabrá entender que fué por una buena causa. A José Luis Wirkes mi socio y compañero, a Ricardo Fernández y Orlando Marquina por ser tan buenos compañeros de trabajo y amigos a la vez. A Jared Smith por haber rescatado mis ganas de seguir adelante y participar en Fedora durante FUDCon Chile 2010.</para>
+ <para>Trabajar para la comunidad implica un sacrificio importante, y a la primera persona que quiero agradecer su soporte, es a mi esposa Elba. Igualmente le pido a Miguel, mi hijo de seis años, que me disculpe por el tiempo que no estuve con él, pero estoy seguro que en el futuro sabrá entender que fué por una buena causa. A José Luis Wirkes mi socio y compañero, a Ricardo Fernández y Orlando Marquina por ser tan buenos compañeros de trabajo y amigos a la vez. A Jared Smith por haber rescatado mis ganas de seguir adelante y participar en Fedora durante FUDCon Chile 2010. A Eduardo Echeverría por ser una bujía para toda la comunidad.</para>
</section>
<section>
<title>Colaboradores</title>
<para>Especial mención a los siguientes colaboradores que han ayudado en la edición del manual.</para>
<simplelist type='horiz' columns='1'>
- <member>erivero , Apper, interfases GUI en KDE.</member>
+ <member>Edith Rivero (erivero) , Apper, interfases GUI en KDE.</member>
</simplelist>
</section>
<section>
@@ -29,6 +29,8 @@
<member>Diego Daguerre</member>
<member>Juan Carlos Herrero</member>
<member>Eduardo Echeverría</member>
+ <member>Kellerman Rivero</member>
+ <member>Emiliano Dalla Verde Marcozzi</member>
</simplelist>
</section>
diff --git a/es-ES/Configuracion_de_YUM.xml b/es-ES/Configuracion_de_YUM.xml
index 59fe177..2a2310a 100644
--- a/es-ES/Configuracion_de_YUM.xml
+++ b/es-ES/Configuracion_de_YUM.xml
@@ -16,17 +16,17 @@
<para><filename>/etc/yum.conf</filename></para>
<screen><xi:include parse="text" href="extras/Configuracion_de_YUM/yum.conf.default.txt" xmlns:xi="http://www.w3.org/2001/XInclude" /></screen>
- <para>El primer aspecto notable del archivo de configuración de yum es su estructura de bloques de secciones identificados por corchetes como <parameter>[sección]</parameter>. Esta estructura se repite al momento de configurar los repositorios. En este caso <filename>yum.conf</filename> en la sección <parameter>[main]</parameter> define el comportamiento general del sistema YUM y establece las directivas base, por ejemplo, de dónde se encuentra el cache. Se comentan abajo cada una de las directivas encontradas en el archivo de configuración encontradas en la configuración inicial.</para>
+ <para>El primer aspecto notable del archivo de configuración de yum es su estructura de bloques de secciones identificados por corchetes como <parameter>[sección]</parameter>. Esta estructura se repite al momento de configurar los repositorios. En este caso <filename>yum.conf</filename> en la sección <parameter>[main]</parameter> define el comportamiento general del sistema YUM y establece las directivas base, por ejemplo, de dónde se encuentra el almacén de datos temporales (cache). Se comentan abajo cada una de las directivas encontradas en el archivo de configuración encontradas en la configuración inicial.</para>
<variablelist>
<varlistentry><term>cachedir</term>
- <listitem><para>Directorio donde YUM debe almacenar su cache y archivos db. El valor por omisión es <filename>/var/cache/yum</filename>.</para></listitem></varlistentry>
+ <listitem><para>Directorio donde YUM debe almacenar su archivos temporales y archivos db. El valor por omisión es <filename>/var/cache/yum</filename>.</para></listitem></varlistentry>
<varlistentry><term>keepcache</term>
<listitem><para>Ya sea ‘1’ o ‘0’. Determina si YUM debe o no mantener el cache de los encabezados y paquetes después de una instalación exitosa. Valor por omisión es ’1’ (mantener los archivos).</para></listitem></varlistentry>
<varlistentry><term>debuglevel</term>
<listitem><para>Nivel de mensajes de depuración en la salida. El rango práctico es de 0-10. El valor por omisión es ‘2’.
.</para></listitem></varlistentry>
<varlistentry><term>logfile</term>
- <listitem><para>Ruta completa al nombre de archivo donde YUM debe escribir sus actividades.</para></listitem></varlistentry>
+ <listitem><para>Ruta completa al nombre de archivo donde YUM debe reportar sus actividades.</para></listitem></varlistentry>
<varlistentry><term>exactarch</term>
<listitem><para>Ya sea ‘1’ o ‘0’. Puesto a ‘1’ provoca que por ejemplo <command>yum update</command> solo actualice los paquete de arquitectura que haya instalado, es decir, con esta opción habilitada el comando <command>yum</command> no instalará un paquete i686 para actualizar un paquete i386. Por omisión el valor es ‘1’..</para></listitem></varlistentry>
<varlistentry><term>obsoletes</term>
@@ -92,7 +92,7 @@
<listitem><para>Puede copiar paquetes del cache y reusarlos a voluntad.</para></listitem>
</orderedlist>
- <para>Por omisión yum almacena los archivos temporales en <filename class="directory">/var/cache/yum/</filename> con un subdirectorio por repositorio configurado. El directorio <filename class="directory">packages/</filename> dentro de cada subdirectorio mantiene los paquetes puestos en el cache. Por ejemplo, <filename class="directory">/var/cache/yum/x86_64/13/fedora/packages</filename> mantiene los paquetes descargados del repositorio fedora.</para>
+ <para>Por omisión yum almacena los archivos temporales en <filename class="directory">/var/cache/yum/</filename> con un subdirectorio por repositorio configurado. El directorio <filename class="directory">packages/</filename> dentro de cada subdirectorio mantiene los paquetes puestos en el cache. Por ejemplo, <filename class="directory">/var/cache/yum/x86_64/13/fedora/packages</filename> mantiene los paquetes descargados del repositorio fedora 13 de arquitectura x86_64.</para>
<para>Para habilitar el uso del cache use la directiva <parameter>keepcache</parameter> en <filename>/etc/yum.conf</filename>.</para>
<para><filename>/etc/yum.conf</filename></para>
@@ -146,8 +146,8 @@ plugins=1
<section>
<title>Control de ancho de banda</title>
- <para>En redes gestionadas de estaciones o servidores existe la necesidad de controlar el uso del ancho de banda disponible para el uso de cada sistema YUM, también es útil para usuarios que desean mantener al sistema YUM bajo control en particular cuando están haciendo alguna otra cosa que requiere ancho de banda.</para>
- <para>La solución es simple, configurar yum para que se limite en el uso del ancho de banda, abajo se muestra un ejemplo de <filename>yum.conf</filename> con los parámetros relevantes. <parameter>throttle</parameter> puede ser un valor absoluto o un valor porcentual, en ese último caso, <parameter>bandwidth</parameter> especifica el 100% del ancho de banda disponible en bytes/seg.</para>
+ <para>En redes gestionadas de estaciones o servidores existe la necesidad de controlar el uso del ancho de banda disponible para el uso de cada sistema YUM, también es útil para usuarios que desean mantener al sistema YUM bajo control en particular cuando están haciendo alguna otra cosa que requiere ancho de banda en la red.</para>
+ <para>La solución es simple, configurar yum para que se limite en el uso del ancho de banda de red de red. Abajo se muestra un ejemplo de <filename>yum.conf</filename> con los parámetros relevantes. <parameter>throttle</parameter> puede ser un valor absoluto o un valor porcentual, en ese último caso, <parameter>bandwidth</parameter> especifica el 100% del ancho de banda disponible en bytes/seg.</para>
<para>Si desea deshabilitar el control, ponga <parameter>throttle=0</parameter>.
</para>
<screen># Ajustes para control de ancho de banda
@@ -418,7 +418,7 @@ $ su -c "yum install fedora-release-rawhide"
<para>En cuanto a la disponibilidad o no de cierto software en los repositorios Fedora, en general lo que se anima es a contribuir directamente con el Proyecto Fedora si se cumplen los lineamientos correspondientes.</para>
- <para>Cuando Proyecto Fedora desarrolla una nueva versión, no toma en cuenta los repositorios externos de terceros o personales y sólo ofrece soporte para los paquetes provistos oficialmente en sus repositorios oficiales.</para>
+ <para>Cuando Proyecto Fedora desarrolla una nueva versión, no toma en cuenta los repositorios externos de terceros o personales y sólo ofrece soporte para los paquetes provistos en sus repositorios oficiales.</para>
<para>En resumen, pueden existir repositorios de terceros con excelente calidad y compatibilidad con Fedora, y otros que no y que sólo le crearán problemas. Use con cuidado, a su riesgo y con habilitación de dicho repositorio al momento y para asuntos puntuales.</para>
diff --git a/es-ES/Extensiones_Yum.xml b/es-ES/Extensiones_Yum.xml
index c862b2d..5341718 100644
--- a/es-ES/Extensiones_Yum.xml
+++ b/es-ES/Extensiones_Yum.xml
@@ -6,62 +6,18 @@
<chapter id="Extensiones_Yum">
<title>Extensiones yum</title>
<para>La aplicación <application>yum</application> soporta lo que se denominan <emphasis>extensiones</emphasis> o <emphasis>plugins</emphasis>. Dichas extensiones permiten agregar funcionalidad a <application>yum</application> que no forman parte del núcleo de funcionalidades. La mayoría de ellas están disponibles en Fedora, abajo un listado breve y luego una revisión de cada una de ellas haciendo énfasis en su uso y aplicabilidad.</para>
- <screen>yum-plugin-aliases
-yum-plugin-changelog
-yum-plugin-fastestmirror
-yum-plugin-filter-data
-yum-plugin-list-data
-yum-plugin-verify
-yum-presto
-yum-plugin-auto-update-debug-info
-yum-plugin-basearchonly
-yum-plugin-downloadonly
-yum-plugin-fs-snapshot
-yum-plugin-keys
-yum-plugin-local
-yum-plugin-merge-conf
-yum-plugin-post-transaction-actions
-yum-plugin-priorities
-yum-plugin-protect-packages
-yum-plugin-protectbase
-yum-plugin-refresh-updatesd
-yum-plugin-remove-with-leaves
-yum-plugin-rpm-warm-cache
-yum-plugin-security
-yum-plugin-show-leaves
-yum-plugin-tmprepo
-yum-plugin-tsflags
-yum-plugin-upgrade-helper
-yum-plugin-versionlock
-yum-rhn-plugin
-PackageKit-yum-plugin
-anaconda-yum-plugins</screen>
+
+ <screen><xi:include parse="text" href="extras/Extensiones_Yum/yum-extensions-available.txt" xmlns:xi="http://www.w3.org/2001/XInclude" /></screen>
+
<para>En este manual documentaremos algunas extensiones, para más información acerca de otras extensiones vea <ulink url="http://yum.baseurl.org/wiki/YumUtils">http://yum.baseurl.org/wiki/YumUtils</ulink>.</para>
<section><title>Instalación y configuración general de las extensiones</title>
<para>Para instalar, y en general para no repetir este procedimiento con cada documentación específica a la extensión, recuerde que la instalación de una extensión se realiza simplemente con el comando <command>yum install nombre-de-la-extensión</command>, por ejemplo:</para>
- <screen>$ su -c "yum install yum-plugin-downloadonly"
-...
-Dependencies Resolved
-=================================================================
-Package Arch Version Repository Size
-=================================================================
-Installing:
-
-yum-plugin-downloadonly noarch 1.1.24-2.fc12 updates 8.8 k
-
-Transaction Summary
-=================================================================
-Install 1 Package(s)
-Update 0 Package(s)
-Remove 0 Package(s)
-Total download size: 5.9 k
-Is this ok [y/N] : y
-</screen>
+ <screen><xi:include parse="text" href="extras/Extensiones_Yum/yum-install-extension-sample.txt" xmlns:xi="http://www.w3.org/2001/XInclude" /></screen>
<para>El nombre de cada sección subsiguiente indicará el nombre de la extensión/paquete a instalar tal cual y de acuerdo a su nombre en la versión actual de Fedora para el momento de redacción de este manual.</para>
-<para>El sitio para la centralización de configuración de las extensiones en Fedora es el directorio <filename class="directory">/etc/yum/pluginconf.d</filename>. </para>
+<para>El sitio para la centralización de la configuración de las extensiones en Fedora es el directorio <filename class="directory">/etc/yum/pluginconf.d</filename>. </para>
</section>
<xi:include href="yum-plugin/yum-plugin-aliases.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
@@ -70,8 +26,6 @@ Is this ok [y/N] : y
<xi:include href="yum-plugin/yum-plugin-changelog.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-<xi:include href="yum-plugin/yum-plugin-downloadonly.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-
<xi:include href="yum-plugin/yum-plugin-fastestmirror.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="yum-plugin/yum-plugin-filter-data.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
@@ -92,6 +46,8 @@ Is this ok [y/N] : y
<xi:include href="yum-plugin/yum-plugin-protectbase.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+<xi:include href="yum-plugin/yum-plugin-ps.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+
<xi:include href="yum-plugin/yum-plugin-refresh-updatesd.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="yum-plugin/yum-plugin-remove-with-leaves.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
@@ -112,8 +68,6 @@ Is this ok [y/N] : y
<xi:include href="yum-plugin/yum-plugin-versionlock.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-<xi:include href="yum-plugin/yum-plugin-presto.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-
<xi:include href="yum-plugin/PackageKit-yum-plugin.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="yum-plugin/yum-langpacks.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
diff --git a/es-ES/Las_interfases_GUI_de_gnome-packagekit.xml b/es-ES/Las_interfases_GUI_de_gnome-packagekit.xml
index 566aebd..274b5de 100644
--- a/es-ES/Las_interfases_GUI_de_gnome-packagekit.xml
+++ b/es-ES/Las_interfases_GUI_de_gnome-packagekit.xml
@@ -7,9 +7,7 @@
<title>Las interfases GUI de gnome-packagekit</title>
<para><application>gnome-software</application> es un aplicativo dedicado a gestionar las aplicaciones, no paquetes, por lo que si usted es un usuario un poco más avanzado, y desea gestionar paquetes entonces podrá optar por los aplicativos <application>gpk-application</application> y <application>gpk-update-viewer</application>.</para>
- <para>Este capítulo es acerca de las interfases GUI que ofrecen PackageKit para gestionar paquetes para este entorno de escritorio.</para>
-
- <para>Normalmente las interfases GUI gnome-packagekit se instalan por omisión en Fedora como escritorio, de todas formas, en el caso de que no sea así, para su instalación haga con privilegios de root:</para>
+ <para>Normalmente las interfases GUI de gnome-packagekit para gestionar paquetes no se instalan por omisión en Fedora, para ello deberá instalar ejecutando en un terminal:</para>
<screen>$ su -c "yum install gnome-packagekit-installer"</screen>
<screen>$ su -c "yum install gnome-packagekit-updater"</screen>
@@ -28,7 +26,7 @@
</mediaobject>
</figure>
- <para>En GNOME3, la mejor forma de invocar esta aplicación es buscándola y luego tal vez agregándola como favorita. Para buscar <application>gpk-application</application> presione la tecla Win, la combinación Alt-F1 o vaya al menú de actividades en la esquina izquierda superior de su escritorio. Tipee "sof" y obtendrá un resultado similar al pantallazo siguiente. En el pantallazo también se muestra el menú contextual que se obtiene de presionar clic derecho sobre el icono para agregar como aplicación favorita.</para>
+ <para>En GNOME3, la mejor forma de invocar esta aplicación es buscándola y luego tal vez agregándola como favorita. Para buscar <application>gpk-application</application> presione la tecla Win, la combinación Alt-F1 o vaya al menú de actividades en la esquina izquierda superior de su escritorio. Tipee "paquetes" y obtendrá un resultado similar al pantallazo siguiente. En el pantallazo también se muestra el menú contextual que se obtiene de presionar clic derecho sobre el icono para agregar como aplicación favorita.</para>
<figure><title>Buscando gpk-application en GNOME3</title>
<mediaobject>
<imageobject>
diff --git a/es-ES/PackageKit_CLI.xml b/es-ES/PackageKit_CLI.xml
index 35ca5f8..3aca955 100644
--- a/es-ES/PackageKit_CLI.xml
+++ b/es-ES/PackageKit_CLI.xml
@@ -122,24 +122,8 @@
<para><application>gpk-install-catalog</application> lee un archivo de entrada .catalog que provoca que los paquetes listados adecuadamente en él sean instalados si es que ya no lo están. Esta opción de PackageKit puede ser muy útil a los distribuidores y desarrolladores de software ya que permite por ejemplo al usuario bajar un catálogo e instalar en su distribución sin tener que preocuparse de identificar los componentes.</para>
<para>Es una especie de equivalente a los grupos yum pero más específico. ¿Cómo luce un archivo .catalog?</para>
-<screen>
-[PackageKit Catalog]
+<screen><xi:include parse="text" href="extras/PackageKit_CLI/gpk/gpk-install-catalog-file.txt" xmlns:xi="http://www.w3.org/2001/XInclude" /></screen>
-# Simplemente el paquete en Fedora que provee la dependencia
-# Si hay múltiples paquetes, se le pregunta al usuario
-InstallProvides(fedora)=audio/QCELP
-
-# Específico para Fedora 9, instala dos paquetes de desarrollo
-InstallPackages(fedora;9)=glib2-devel;PolicyKit-gnome-devel
-
-# En cualquier distro, instala el paquete con el archivo indicado
-InstallFiles=/usr/bin/fontinst
-
-# Para cada arquitectura en Fedora 8, instala uno de los dos diferentes
-# archivos compat
-InstallFiles(fedora;8;i686)=/usr/lib/pango/1.6.0/modules/pango-arabic-fc.so
-InstallFiles(fedora;8;x64)=/usr/lib64/pango/1.6.0/modules/pango-arabic-fc.so
-</screen>
<para>Note el distro-id entre paréntesis (), esto le permite al empaquetador entonar el nombre de paquete, donde por ejemplo en Fedora es PolicyKit, en Debian es policykit. Se puede ser granular con la distribución, versión de la distrinución y la arquitectura.</para>
<para>Note que no hay verificación de versiones. Se debe especificar la distribución y ésta tener los datos correctos.</para>
diff --git a/es-ES/Revision_History.xml b/es-ES/Revision_History.xml
index 8f66918..6c877f4 100644
--- a/es-ES/Revision_History.xml
+++ b/es-ES/Revision_History.xml
@@ -8,6 +8,21 @@
<simpara>
<revhistory>
<revision>
+ <revnumber>4</revnumber>
+ <date>Mon Dec 2013</date>
+ <author>
+ <firstname>Guillermo J.</firstname>
+ <surname>Gómez Savino</surname>
+ <email>guillermo.gomez(a)gmail.com</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Fedora 20 revision</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+
+ <revision>
<revnumber>3</revnumber>
<date>Mon May 7 2012</date>
<author>
diff --git a/es-ES/Technicas_para_administradores_de_sistemas.xml b/es-ES/Technicas_para_administradores_de_sistemas.xml
index d58a555..33ab88d 100644
--- a/es-ES/Technicas_para_administradores_de_sistemas.xml
+++ b/es-ES/Technicas_para_administradores_de_sistemas.xml
@@ -5,7 +5,7 @@
]>
<chapter id="Técnicas_para_administradores_de_sistemas">
<title>Técnicas para administradores de sistemas</title>
- <para>Los siguientes son introducción a tópicos suplementarios que pueden ser considerados de uso más avanzado que el material que se ha presentado hasta ahora en este manual y que puede ser de utilidad en entornos más complejos de gestión de sofware Fedora, en particular, en redes de estaciones de trabajo o servidores, centros de computo, etc.</para>
+ <para>Las siguientes son introducciones a tópicos suplementarios que pueden ser considerados de uso más avanzado que el material que se ha presentado hasta ahora en este manual y que puede ser de utilidad en entornos más complejos de gestión de sofware Fedora, en particular, en redes de estaciones de trabajo o servidores, centros de computo, etc.</para>
<section><title>Configuración remota</title>
<para>Es posible centralizar todas las configuraciones <application>yum</application> en un servidor externo y hacer que <application>yum</application> obtenga dichas configuraciones al momento de su ejecución. Entonces el administrador puede incluso tener varias configuraciones para el mismo servidor y dada la circunstancia específica, usar una u otra configuración a voluntad.</para>
diff --git a/es-ES/Utilidades_YUM.xml b/es-ES/Utilidades_YUM.xml
index 307dc54..5f889f0 100644
--- a/es-ES/Utilidades_YUM.xml
+++ b/es-ES/Utilidades_YUM.xml
@@ -5,8 +5,8 @@
]>
<chapter id="Utilidades_YUM">
<title>Utilidades YUM</title>
- <para>Existen una serie de utilidades que están disponibles en Fedora en el paquete denominado <package>yum-utils</package> y algunas otras en paquetes separados. Esta sección está dedicada a dicho paquetes y los programas que allí se incluyen.</para>
- <para>Instale con <command>yum install yum-utils</command> si el programa es provisto por este paquete, si no, utilice el comando <command>yum install</command> con el nombre del programa correspondiente, los nombres de paquetes corresponden en todos esos casos.</para>
+ <para>Existen una serie de utilidades que están disponibles en Fedora en el paquete denominado <package>yum-utils</package> y algunas otras en paquetes separados. Esta sección está dedicada a dichos paquetes y los programas que allí se incluyen.</para>
+ <para>Instale con <command>yum install yum-utils</command> si el programa es provisto por este paquete, si no, utilice el comando <command>yum install</command> con el nombre del programa correspondiente, los nombres de paquetes corresponden en todos los casos aquí documentados.</para>
<section><title>Autocompletado Bash</title>
<para>Tanto <application>yum</application> como <package>yum-utils</package> incluyen archivos de configuración para agregar la funcionalidad de autocompletado en Bash. Para poder hacer uso de esta funcionalidad debe instalar el paquete <package>bash-completion</package>.</para>
@@ -15,26 +15,7 @@ $ su -c "yum install bash-completion"
</screen>
<para>Use la tecla <tab> una vez para autocompletar,o dos veces para listar las opciones del autocompletado si no hay una selección única. Abajo le presentamos algunos ejemplos simples de su uso:</para>
-<screen>
-$ yum ins<tab>
-$ yum install
-$ yum install bas<tab><tab>
- bashdb.noarch basket-libs.i686 bastet.x86_64
- bash-doc.x86_64 basket-libs.x86_64
- BasiliskII.x86_64 basket.x86_64
-</screen>
-
-<screen>
-$ repoquery --repo<tab>
- --repofrompath --repoid
-$ repoquery --repoid fedora<tab><tab>
- fedora fedora-debuginfo
- fedora-appmarket fedora-latam
- fedora-chromium fedora-latam-debuginfo
- fedora-chromium-source fedora-latam-source
- fedora-chromium-stable fedora-source
- fedora-chromium-stable-source
-</screen>
+ <screen><xi:include parse="text" href="extras/Utilidades_YUM/yum-autocompletado.txt" xmlns:xi="http://www.w3.org/2001/XInclude" /></screen>
</section>
<section>
@@ -45,26 +26,8 @@ $ repoquery --repoid fedora<tab><tab>
<title>Configuración</title>
<para><filename>/etc/sysconfig/yum-updateonboot</filename></para>
+ <screen><xi:include parse="text" href="extras/Utilidades_YUM/yum-updateonboot.txt" xmlns:xi="http://www.w3.org/2001/XInclude" /></screen>
-<screen>
-# Si cualquiera de estos rpms son actualizados, yum-updateonboot mandará a
-# reiniciar el equipo inmediatamente después de yum udpate.
-# Para evitar que yum-updateonoot reinicie su máquina , comente la
-# siguiente línea
-#REBOOT_RPMS="kernel kernel-smp"
-
-# Lista de grupos que deben ser actualizados al inicio.
-# Para cada grupo mencionado
-# yum-updateonboot llamará 'yum -y groupupdate'
-# Ya que los grupos tienden a tener espacios en sus nombres,
-# use punto y coma para separarlos
-#GROUPLIST="My Group;MyOtherGroup;Some_Group;My Group 4"
-
-# Silencioso al actualizar, por omisión es así
-# Estas opciones son pasadas a yum, por omisión es "-q"
-#OPTIONS="-q"
-</screen>
-
<para>Como todo servicio en Fedora, éste viene deshabilitado por omisión, por lo que debe configurar que se inicie en los niveles de ejecución deseados.</para>
<screen>
$ chkconfig yum-updateonboot on
@@ -75,34 +38,23 @@ $ chkconfig yum-updateonboot on
<section>
<title>yumdownloader</title>
- <para>Este utilitario provisto por el paquete <package>yum-utils</package> complementa al plugin <application>downloadonly</application> ya que dicho plugin sólo funciona si el software deseado no está instalado. Vea como falla y cómo puede resolver con <command>yumdownloader</command>.</para>
- <screen>
-$ yum --downloadonly install openssh-server
-Loading "downloadonly" plugin
-Setting up Install Process
-Setting up repositories
-Reading repository metadata in from local files
-Parsing package install arguments
-Nothing to do
-</screen>
-<para>No hay nada que instalar, ya está instalado, no se descarga nada. Intente ahora con <command>yumdownloader</command>.</para>
+ <para>Este utilitario provisto por el paquete <package>yum-utils</package> complementa la opcion <application>--downloadonly</application> ya que ella solo funciona si el software deseado no está instalado o si tiene una actualización existente. Vea como falla y cómo puede resolver con <command>yumdownloader</command>.</para>
+ <screen><xi:include parse="text" href="extras/Utilidades_YUM/yum-install--downloadonly-falla.txt" xmlns:xi="http://www.w3.org/2001/XInclude" /></screen>
-<screen>
-$ yumdownloader openssh-server
-Complementos cargados:presto, refresh-packagekit
-openssh-server-5.6p1-31.fc15.1.x86_64.rpm | 299 kB 00:04
-</screen>
+<para>No hay nada que instalar, ya está instalado, no se descarga nada. Intentando con <command>yum update</command> tampoco tenemos suerte, no hay actualizaciones.</para>
+
+ <screen><xi:include parse="text" href="extras/Utilidades_YUM/yum-update--downloadonly-falla.txt" xmlns:xi="http://www.w3.org/2001/XInclude" /></screen>
+
+<para>Intente ahora con <command>yumdownloader</command>.</para>
+
+ <screen><xi:include parse="text" href="extras/Utilidades_YUM/yumdownloader-screen.txt" xmlns:xi="http://www.w3.org/2001/XInclude" /></screen>
<para>Hecho, ya tiene el rpm que quería.</para>
<para>Otra opción de uso frecuente es especificar que se desea descargar los fuentes rpms:</para>
-<screen>
-$ yumdownloader --source zsh
-...
-Enabling fedora-source repository
-fedora-source/metalink | 1.7 kB 00:00
-zsh-4.3.11-2.fc15.src.rpm | 2.6 MB 00:30
-</screen>
+
+<screen><xi:include parse="text" href="extras/Utilidades_YUM/yumdownloader--source-screen.txt" xmlns:xi="http://www.w3.org/2001/XInclude" /></screen>
+
<note>
<title>Habilitación automática de repositorio</title>
<para>Note que <command>yumdownloader</command> ha habilitado los repositorios de fuentes "source" para poder hacer la descarga.</para>
@@ -110,11 +62,8 @@ zsh-4.3.11-2.fc15.src.rpm | 2.6 MB 00:30
<para>Otra funcionalidad que ofrece <application>yumdownloader</application> es la identificación de los fuentes para un paquete rpm dado. Esto es útil ya que un fuente RPM puede producir múltiples paquetes RPM.</para>
-<screen>
-$ yumdownloader --urls --source ruby-gtk2
-...
-http://fedora.c3sl.ufpr.br/linux/updates/13/SRPMS//ruby-gnome2-0.90.2-1.fc13.src.rpm
-</screen>
+<screen><xi:include parse="text" href="extras/Utilidades_YUM/yumdownloader--urls-source-ruby-gtk2.txt" xmlns:xi="http://www.w3.org/2001/XInclude" /></screen>
+
</section>
<section>
@@ -126,84 +75,31 @@ http://fedora.c3sl.ufpr.br/linux/updates/13/SRPMS//ruby-gnome2-0.90.2-1.fc1…
<para>Listar los paquetes huérfanos, aquellos paquetes que no son provistos por ninguno de los repositorios configurados, "son huérfanos de repositorio", use la opción <option>--orphans</option>.</para>
-<screen>
-# package-cleanup --orphans
-...
-NetworkManager-0.8.9997-1.git20110531.fc15.x86_64
-NetworkManager-glib-0.8.9997-1.git20110531.fc15.x86_64
-NetworkManager-gnome-0.8.9997-1.git20110531.fc15.x86_64
-adobe-release-i386-1.0-1.noarch
-control-center-3.0.1.1-6.fc15.x86_64
-control-center-filesystem-3.0.1.1-6.fc15.x86_64
-cpp-4.6.0-7.fc15.x86_64
-dbus-qt-0.70-7.fc12.x86_64
-...
-</screen>
+<screen><xi:include parse="text" href="extras/Utilidades_YUM/package-cleanup--orphans.txt" xmlns:xi="http://www.w3.org/2001/XInclude" /></screen>
+
+<para>Debido a la forma en como se maneja las actualizaciones, <application>package-cleanup</application> sólo considera la última versión del paquete, los paquetes no actualizados pero provistos por repositorios configurados aparecerán como huérfanos, es decir, el repositorio Updates, por ejemplo, no continúa suministrando la versión anterior para efectos de <application>package-cleanup</application>. Es decir, antes de hacer un <command>package-cleanup --orphans</command>, se recomienda hacer una actualización completa si es posible, tenga cuidado de no remover estos paquetes a la ligera, ya que también pueden ser paquetes instalados manualmente y que funcionan perfectamente, o simplemente se deshabilitó el repositorio desde el cual se hizo la instalación.</para>
<para><emphasis>Paquetes duplicados</emphasis></para>
<para>Para listar los paquetes con duplicados en la base de datos RPM use la opción <option>--dupes</option>.</para>
-<screen>
-$ package-cleanup --dupes
-...
-samba-3.2.8-0.27.fc10.i386
-samba-3.2.8-0.26.fc10.i386
-libtalloc-1.2.0-26.fc10.i386
-libtalloc-1.2.0-27.fc10.i386
-wireshark-gnome-1.0.6-1.fc10.i386
-wireshark-gnome-1.0.5-1.fc10.i386
-</screen>
+<screen><xi:include parse="text" href="extras/Utilidades_YUM/package-cleanup--dupes.txt" xmlns:xi="http://www.w3.org/2001/XInclude" /></screen>
<para><emphasis>Problemas de dependencias</emphasis></para>
<para>Para listar los problemas de dependencias en la base de datos RPM use la opción <option>--problems</option>.</para>
-<screen>
-$ package-cleanup --problems
-...
-Package compiz-0.9.5.92.1-0.2.gite676f1b12eb8db3a76978eed5bfc7c2cf9a0b6ce.fc16.x86_64 no se encuentran necesita de libboost_serialization-mt.so.1.47.0()(64bit)
-Package compiz-gtk-0.9.5.92.1-0.2.gite676f1b12eb8db3a76978eed5bfc7c2cf9a0b6ce.fc16.x86_64 no se encuentran necesita de libboost_serialization-mt.so.1.47.0()(64bit)
-Package compiz-plugins-main-0.9.5.92-1.fc16.x86_64 no se encuentran necesita de libboost_serialization-mt.so.1.47.0()(64bit)
-Package libcompizconfig-0.9.5.92-1.fc16.x86_64 no se encuentran necesita de libboost_serialization-mt.so.1.47.0()(64bit)
-</screen>
+<screen><xi:include parse="text" href="extras/Utilidades_YUM/package-cleanup--problems.txt" xmlns:xi="http://www.w3.org/2001/XInclude" /></screen>
<para>Felizmente usted no tendrá problemas, lo que esperaría ver es:</para>
-<screen>
-$ package-cleanup --problems
-Complementos cargados:presto, refresh-packagekit
-No Problems Found
-</screen>
+<screen><xi:include parse="text" href="extras/Utilidades_YUM/package-cleanup-no-problems.txt" xmlns:xi="http://www.w3.org/2001/XInclude" /></screen>
<para><emphasis>Remoción de kernels antiguos</emphasis></para>
<para><command>package-cleanup</command> también es útil para remover instalaciones de kernel antiguos y paquetes relacionados a dichos kernel antiguos, ue la opción <option>--oldkernel</option>:</para>
-<screen>
-# package-cleanup --oldkernel
-Setting up yum
-Loaded plugins: dellsysidplugin2, fastestmirror, kernel-module, presto,
- : priorities, protectbase, upgrade-helper, versionlock
-Loading mirror speeds from cached hostfile
-I will remove the following 3 kernel related packages:
-kernel-2.6.30.5-43.fc11.i586
-kernel-devel-2.6.29.6-217.2.16.fc11.i586
-kernel-devel-2.6.30.5-43.fc11.i586
-Is this ok [y/N]: y
-
-# rpm -qa kernel*
-[root@movix ~]# rpm -qa kernel*
-kernel-headers-2.6.30.9-90.fc11.i586
-kernel-2.6.30.8-64.fc11.i586
-kernel-devel-2.6.30.8-64.fc11.i586
-kernel-2.6.30.9-90.fc11.i586
-kernel-devel-2.6.30.9-90.fc11.i586
-kernel-doc-2.6.30.9-90.fc11.noarch
-kernel-firmware-2.6.30.9-90.fc11.noarch
-# uname -r
-2.6.30.9-90.fc11.i586
-</screen>
+ <screen><xi:include parse="text" href="extras/Utilidades_YUM/package-cleanup--oldkernel.txt" xmlns:xi="http://www.w3.org/2001/XInclude" /></screen>
<warning>
<title>No interpreta installonly_limit</title>
@@ -211,18 +107,6 @@ kernel-firmware-2.6.30.9-90.fc11.noarch
<para>Note que se ha dejado un kernel antiguo de acuerdo a la práctica común de <application>yum</application> de mantener dos kernels máximo instalados. Tenga cuidado que este comando no interpreta la opción en <filename>yum.conf</filename> <parameter>installonly_limit</parameter>.</para>
</warning>
-<section><title>Ejemplos de uso</title>
-<screen>
-# package-cleanup --orphans
-Setting up yum
-libsndfile-1.0.14-1.fc5.i386
-grisbi-0.5.8-2.fc5.i386
-gedit-2.14.1-1.i386
-...
-</screen>
-
-<para>Debido a la forma en como se maneja las actualizaciones, <application>package-cleanup</application> sólo considera la última versión del paquete, los paquetes no actualizados pero provistos por repositorios configurados aparecerán como huérfanos, es decir, el repositorio Updates, por ejemplo, no continúa suministrando la versión anterior para efectos de <application>package-cleanup</application>. Es decir, antes de hacer un <command>package-cleanup --orphans</command>, se recomienda hacer una actualización completa si es posible, tenga cuidado de no remover estos paquetes a la ligera, ya que también pueden ser paquetes instalados manualmente y que funcionan perfectamente, o simplemente se deshabilitó el repositorio desde el cual se hizo la instalación.</para>
-
<para>Con <command>package-cleanup</command> y el uso de la opción <option>--dupes</option>, se puede detectar los paquetes duplicados en la base de datos RPM, en este ejemplo <package>gedit-2.14.1-1.i386</package>.</para>
<screen>
# package-cleanup --dupes
@@ -265,7 +149,6 @@ Running Transaction Test
<para>Después de realizar esta operación se ha recuperado cierto espacio en disco, se ha limpiado, al menos en parte, la base de datos rpm que representa al software instalado en el sistema Fedora. Para más detalles de uso revise el manual, <command>man package-cleanup</command>.</para>
</section>
-</section>
<section>
<title>yum-complete-transaction</title>
@@ -359,18 +242,18 @@ Getting requirements for fox-1.6.33-1.rf.src
Dependencias resueltas
-===========================================================================================
-Paquete Arquitectura Versión Repositorio Tamaño
-===========================================================================================
+=======================================================================================
+Paquete Arquitectura Versión Repositorio Tamaño
+=======================================================================================
Instalando:
-bzip2-devel x86_64 1.0.6-1.fc13 updates 217 k
-libpng-devel x86_64 2:1.2.44-1.fc1 updates 111 k
-zlib-devel x86_64 1.2.3-23.fc12 fedora 40 k
-Actualizando para las dependencias:
- bzip2-libs x86_64 1.0.6-1.fc13 updates 36 k
+bzip2-devel x86_64 1.0.6-1.fc13 updates 217 k
+libpng-devel x86_64 2:1.2.44-1.fc1 updates 111 k
+zlib-devel x86_64 1.2.3-23.fc12 fedora 40 k
+Actualizando para las dependencias
+ bzip2-libs x86_64 1.0.6-1.fc13 updates 36 k
Resumen de la transacción
-===========================================================================================
+=======================================================================================
Install 3 Package(s)
Upgrade 1 Package(s)
diff --git a/es-ES/extras/Configuracion_de_YUM/yum.conf.prioridad.txt b/es-ES/extras/Configuracion_de_YUM/yum.conf.prioridad.txt
index bc70ebc..b5f2e44 100644
--- a/es-ES/extras/Configuracion_de_YUM/yum.conf.prioridad.txt
+++ b/es-ES/extras/Configuracion_de_YUM/yum.conf.prioridad.txt
@@ -4,7 +4,7 @@ failovermethod=priority
baseurl=http://mirepo.org/$releasever/$basearch/os/
http://otrorepo.org/$releasever/$basearch/os/
-mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-$releasever&arch=$basear
+mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-$releasever&arch=$basearch
enabled=1
metadata_expire=7d
diff --git a/es-ES/images/gnome-packagekit/Gnome3-buscando-gpk-application.png b/es-ES/images/gnome-packagekit/Gnome3-buscando-gpk-application.png
index 4c4dc60..873c398 100644
Binary files a/es-ES/images/gnome-packagekit/Gnome3-buscando-gpk-application.png and b/es-ES/images/gnome-packagekit/Gnome3-buscando-gpk-application.png differ
diff --git a/es-ES/yum-plugin/yum-langpacks.xml b/es-ES/yum-plugin/yum-langpacks.xml
index f9ab6d0..60a51c4 100644
--- a/es-ES/yum-plugin/yum-langpacks.xml
+++ b/es-ES/yum-plugin/yum-langpacks.xml
@@ -5,9 +5,9 @@
]>
<section><title>yum-langpacks</title>
- <para>Extensión langpacks para <application>yum</application>. <application>yum-langpacks</application> es una extensión para YUM que busca langpacks para su idioma nativo para que los instale.</para>
-
- <para>Con esta extensión instalada y configurada para es_ES, si el usuario instala <application>libreoffice</application>, automáticamente se instalará también <application>libreoffice-langpack-es</application>.</para>
+ <para>Extensión langpacks para <application>yum</application>. <application>yum-langpacks</application> es una extensión para YUM que busca langpacks para su idioma nativo para los paquetes que instale.</para>
+
+ <para>Con esta extensión instalada y configurada para es_ES, por ejemplo, si el usuario instala <application>libreoffice</application>, automáticamente se instalará también <application>libreoffice-langpack-es</application>.</para>
<section><title>Configuración</title>
<para><filename>/etc/yum/pluginconf.d/langpacks.conf</filename></para>
diff --git a/lib/tasks/mock.rake b/lib/tasks/mock.rake
index 0c187f1..42a3e22 100644
--- a/lib/tasks/mock.rake
+++ b/lib/tasks/mock.rake
@@ -46,6 +46,14 @@ task :setf20 do
`mock -r fedora-20-SMG-x86-64 --install yum`
`mock -r fedora-20-SMG-x86-64 --install vim`
`mock -r fedora-20-SMG-x86-64 --install man`
+ `mock -r fedora-20-SMG-x86-64 --install rubygem-rake`
+ `mock -r fedora-20-SMG-x86-64 --copyin Rakefile /`
+ `mock -r fedora-20-SMG-x86-64 --copyin lib/mockscripts/* /lib/tasks/`
+end
+
+desc "Copiar salidas generadas en mock"
+task :copyout do
+ `mock -r fedora-20-SMG-x86-64 --copyout /builddir/build/extras/Extensiones_Yum/yum-extensions-available.txt es-Es/extras/Extensiones_Yum/`
end
end
1
0
31 Dec '13
commit 0b1847f4f8728f598d81285b0ccdf5d88282c70c
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Tue Dec 31 00:32:57 2013 -0700
added workflow SOP for creating a patch with git
en-US/workflow-patching.xml | 321 +++++++++++++++++++++++++++++++++++++++++++
en-US/workflow.xml | 9 +-
2 files changed, 328 insertions(+), 2 deletions(-)
---
diff --git a/en-US/workflow-patching.xml b/en-US/workflow-patching.xml
new file mode 100644
index 0000000..d2e194a
--- /dev/null
+++ b/en-US/workflow-patching.xml
@@ -0,0 +1,321 @@
+<?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 "documentation-guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-workflow-patching" >
+ <title>Creating a patch</title>
+ <para>
+ Patches are files that show changes between two versions of a file. The patch file can be shared via email or in a bug report, easily reviewed, and applied without requiring additional manual editing. This section details the procedure for creating a patch for a Fedora Guide.
+ </para>
+ <example>
+ <title>An example of a patch file</title>
+ <para>
+ A patch file might look like this one.
+ </para>
+ <para>
+ <![CDATA[From a6419e00b515765085cc4e646c3822ebdda607df Mon Sep 17 00:00:00 2001
+From: Pete Travis <immanetize(a)fedoraproject.org>
+Date: Mon, 30 Dec 2013 21:52:57 -0700
+Subject: [PATCH] Update commands for starting, stopping, and checking the
+ status of abrtd to use systemctl instead of service/chkconfig
+
+---
+ en-US/Automatic_Bug_Reporting_Tool_ABRT.xml | 20 ++++++++++----------
+ 1 file changed, 10 insertions(+), 10 deletions(-)
+
+diff --git a/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml b/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml
+index 1093dc8..f01bb33 100644
+--- a/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml
++++ b/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml
+@@ -88,18 +88,18 @@
+ Your next step should be to verify that <systemitem
+ class="daemon">abrtd</systemitem> is running. The daemon is typically configured to start up at boot time. You can use the following command as root to verify its current status:
+ </para>
+- <screen>~]# <command>service abrtd status</command>
++ <screen>~]# <command>systemctl status abrtd</command>
+ abrtd (pid 1535) is running...</screen>
+ <para>
+- If the <command>service</command> command returns the <computeroutput>abrt is stopped</computeroutput> message, the daemon is not running. It can be started for the current session by entering this command:
++ If the <command>systemctl</command> command returns the <computeroutput>Active: inactive (dead)</computeroutput> message, the daemon is not running. It can be started for the current session by entering this command:
+ </para>
+- <screen>~]# <command>service abrtd start</command>
++ <screen>~]# <command>systemctl start abrtd </command>
+ Starting abrt daemon: [ OK ]</screen>
+ <para>
+- You can run the following <command>chkconfig</command> command to ensure that the <systemitem
++ You can run the following <command>systemctl</command> command to ensure that the <systemitem
+ class="daemon">abrtd</systemitem> service initializes every time the system starts up:
+ </para>
+- <screen>~]# <command>chkconfig abrtd on</command></screen>
++ <screen>~]# <command>systemctl enable abrtd </command></screen>
+ <para>
+ Similarly, you can follow the same steps to check and configure the <systemitem
+ class="service">abrt-ccpp</systemitem> service if you want <application>ABRT</application> to catch C/C++ crashes. To set <application>ABRT</application> to detect kernel oopses, use the same steps for the <systemitem
+@@ -119,12 +119,12 @@ kernel.panic = 0</screen>
+ <para>
+ Finally, you can verify that the <systemitem
+ class="service">ABRT notification applet</systemitem> is running:
+- </para>
+- <screen>~]$ <command>ps -el | grep abrt-applet</command>
++ </para>
++ <screen>~]$ <command>ps -el | grep abrt-applet</command>
+ 0 S 500 2036 1824 0 80 0 - 61604 poll_s ? 00:00:00 abrt-applet</screen>
+- <para>
+- If the <application>ABRT</application> notification applet is not running, you can start it manually in your current desktop session by running the <systemitem
+- class="service">abrt-applet</systemitem> program:
++ <para>
++ If the <application>ABRT</application> notification applet is not running, you can start it manually in your current desktop session by running the <systemitem
++ class="service">abrt-applet</systemitem> program:
+ </para>
+ <screen>~]$ <command>abrt-applet &</command>
+ [1] 2261</screen>
+--
+1.8.4.2
+]]>
+
+</para>
+ </example>
+ <para>
+ Let us examine how this patch file was created. In the following procedure, we will create a patch to correct a line in the <citetitle>System Administrators Guide</citetitle> to update from the legacy <command>service</command> to the current <command>systemctl</command> command.
+ </para>
+ <procedure>
+ <title>Patch creation workflow</title>
+ <step>
+ <para>
+ First, find the guide you want to work on in the table at <ulink url="https://fedoraproject.org/wiki/Docs_Project_guides_table" />.
+ </para>
+ </step>
+ <step>
+ <para>
+ The <literal>repo</literal> column of the table has a link to the guide's git repository. Open the link, and you'll see the <literal>Clone</literal> section at the bottom of the page, listing the repository's URLs.
+ </para>
+ </step>
+ <step>
+ <para>
+ If you have set up ssh keys for your <ulink url="https://admin.fedoraproject.org/accounts">FAS</ulink> account, right click the URL that begins with <literal>ssh://</literal> and select <guilabel>Copy Link Location</guilabel>.
+ </para>
+ <para>
+ If you have not set up ssh keys in FAS, or simply want to clone anonymously, right click the url that begins with <literal>https://</literal> and select <guilabel>Copy Link Location</guilabel>.
+ </para>
+ <para>
+ It is a good idea to use the <literal>ssh://</literal> url, even if you do not currently have commit access. If you later gain commit access, you won't have to go back and change the upstream location of the repo.
+ </para>
+ </step>
+ <step>
+ <para>
+ In a terminal window, change to the directory you have chosen to store guides in and clone the repo. You can paste into the terminal window by right clicking it and selecting <guilabel>Paste</guilabel>. Some terminal applications will also paste with the key combination <keycombo><keycap>Shift</keycap><keycap>Insert</keycap></keycombo>.
+ </para>
+ <screen>
+ <command>cd ~/fedora-docs</command>
+ <command>
+ git clone ssh://git.fedorahosted.org/git/docs/system-administrators-guide.git
+ </command>
+ <command>cd system-administrators-guide</command>
+ </screen>
+ </step>
+ <step>
+ <para>
+ If you have already cloned the repo, it is important to make sure your local copy is updated and matches the remote copy.
+ </para>
+ <para>
+ Pull in new changes from remote:
+ <screen>
+ <command>git pull</command>
+ </screen>
+ </para>
+ <para>
+ If you have made changes in the master branch that aren't committed, you can <command>stash</command> them. The files will returned to the unchanged state, and you can come back to them later. For detailed information, refer to <command>man git-stash</command>.
+ <screen>
+ <command>git stash</command>
+ # continue with patch process, then bring back your stashed state with:
+ <command>git stash pop</command>
+ </screen>
+ </para>
+ <para>
+ If you have made <emphasis>and committed</emphasis> changes in the master branch, you should push your changes:
+ <screen>
+ <command>git push</command>
+ </screen>
+ </para>
+ <para>
+ If you don't have access to push commits, or you don't want to push them, you can reset your local copy to match remote:
+ <screen>
+ <command>git reset --hard origin/master</command>
+ </screen>
+ </para>
+ </step>
+ <step>
+ <para>
+ A new branch of the repository will allow you to make changes to the side, without affecting the master branch until we are ready to. For smaller patches, this branch is temporary and you won't have to share it. Name the branch something recognizable to help you keep track of its purpose, then check out the branch.
+ <screen>
+ <command>git branch abrt-systemctl-not-service</command>
+ <command>git checkout abrt-systemctl-not-service</command>
+ </screen>
+ </para>
+ </step>
+ <step>
+ <para>
+ Find the files you need to change. A bug report might say "The abrt section should use the systemctl command instead of service", but it will not tell you what file or section to edit. In DocBook, commands are usually wrapped in the <command> tag, so we can use that to help our search.
+ <screen>
+ <command>grep "<command>service" en-US/*.xml</command>
+ <filename>en-US/Automatic_Bug_Reporting_Tool_ABRT.xml</filename>: <screen>~]# <emphasis><command>service</emphasis> abrtd status</command>
+ <filename>en-US/Automatic_Bug_Reporting_Tool_ABRT.xml</filename>: If the <emphasis><command>service</emphasis></command> command returns the <computeroutput>abrt is stopped</computeroutput> message, the daemon is not running. It can be started for the current session by entering this command:
+ <filename>en-US/Automatic_Bug_Reporting_Tool_ABRT.xml</filename>: <screen>~]# <emphasis><command>service</emphasis> abrtd start</command>
+ </screen>
+ </para>
+ </step>
+ <step>
+ <para>
+ The <command>grep</command> command has found the file we want to edit, <filename>en-US/Automatic_Bug_Reporting_Tool_ABRT.xml</filename>. Open the file in your favorite editor and make the required changes:
+ <screen>
+ <command>vim <filename>en-US/Automatic_Bug_Reporting_Tool_ABRT.xml</filename></command>
+ </screen>
+ or:
+ <screen>
+ <command>emacs <filename>en-US/Automatic_Bug_Reporting_Tool_ABRT.xml</filename></command>
+ </screen>
+ or:
+ <screen>
+ <command>gedit <filename>en-US/Automatic_Bug_Reporting_Tool_ABRT.xml</filename></command>
+ </screen>
+ </para>
+ <para>
+ The editor you choose is not important, but the file must be saved in plain text format.
+ </para>
+ <para>
+ Change only the content you need to, so that the diff will be more readable. Resist the temptation to rephrase passages unless they are misleading, to avoid making more work for translators. Do not adjust sections to your preferred indentation depth; this changes no actual content and makes the patch more difficult to interpret.
+ </para>
+ </step>
+ <step>
+ <para>
+ Test your changes by building the document, and reviewing the section in the browser.
+ <screen>
+ <command>publican build --langs en-US --formats html</command>
+ <command>firefox tmp/en-US/html/index.html</command>
+ </screen>
+ </para>
+ </step>
+ <step>
+ <para>
+ After editing, if you want to check what files you have changed, use this command:
+ <screen>
+ <command>git status</command>
+ <computeroutput>
+# On branch abrt-systemctl-not-service
+# Changes not staged for commit:
+# (use "git add <file>..." to update what will be committed)
+# (use "git checkout -- <file>..." to discard changes in working directory)
+#
+# modified: en-US/Automatic_Bug_Reporting_Tool_ABRT.xml
+#
+no changes added to commit (use "git add" and/or "git commit -a")
+ </computeroutput>
+ </screen>
+ </para>
+ </step>
+ <step>
+ <para>
+ Commit your changes. If you only made a few changes, place them all in the same commit. If you make many changes, edit different files, or work on varied issues, spread your changes out into individual commits. This makes it easier for others to follow your work.
+ <screen>
+ <command>git commit en-US/Automatic_Bug_Reporting_Tool_ABRT.xml</command>
+ </screen>
+ </para>
+ <para>
+ After you run the command above, an editor will open for you to enter a commit message. Be descriptive, explain what sections you have updated and why, and provide references if available. If you are working on a specifig bug report, you should also cite the bug in the commit message. something like <literal>RHBZ#439858</literal> is enough but you can also cite the full URL if you prefer.
+ </para>
+ <note>
+ <title>Default Editor</title>
+ <para>
+ The default editor used by git is <application>vi</application>. You can change this setting by adding a line in <filename>~/.bashrc</filename>, such as:
+ <screen>
+ <command>export EDITOR="/usr/bin/emacs"</command>
+ </screen>
+ </para>
+ </note>
+ <para>
+ You can also bypass the editor and enter your message directly with the commit command, like this:
+ <screen>
+ <command>
+ git commit en-US/Automatic_Bug_Reporting_Tool_ABRT.xml \
+ -m "Update commands for starting, stopping, and checking the status \
+ of abrtd to use systemctl instead of service/chkconfig"
+ </command>
+ </screen>
+ </para>
+ </step>
+ <step>
+ <para>
+ Check the status of your repository again, and make sure all the indended changes have been committed.
+ <screen>
+ <command>git status</command>
+ <computeroutput>
+ # On branch abrt-systemctl-not-service
+ nothing to commit, working directory clean
+ </computeroutput>
+ </screen>
+ </para>
+ </step>
+ <step>
+ <para>
+ Now create your patches. Each commit will create one patch file, showing the differences between your changes and the master branch.
+ <screen>
+ <command>git format-patch master</command>
+ <computeroutput>
+ 0001-Update-commands-for-starting-stopping-and-checking-t.patch
+ </computeroutput>
+ </screen>
+ </para>
+ </step>
+ <step>
+ <para>
+ Now that you've created the patch, share it! Attach it to the bug ticket, send it to the mailing list, or share it with your mentor. The patch needs to get out for review and inclusion in the master branch.
+ </para>
+ <para>
+ If there isn't an existing bug, you can create a new one. The patch created when writing this section is attached to <ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=1047428" />
+ </para>
+ </step>
+ <step>
+ <para>
+ After you have shared your patch, you can clean up. Checking out the master branch will return the files to the unedited state:
+ <screen>
+ <command>
+ git checkout master
+ </command>
+ </screen>
+ </para>
+ <para>
+ Clean any files that git is not tracking from the directory. This will delete your patches, so make sure you have sent them off for review.
+ <screen>
+ <command>
+ git clean -xdf
+ </command>
+ </screen>
+ </para>
+ <para>
+ You can delete the local working branch as well. Again, make sure you have shared your patches, or your work will be lost.
+ <screen>
+ <command>git branch -D abrt-systemctl-not-service</command>
+ <computeroutput>Deleted branch abrt-systemctl-not-service (was a6419e0).</computeroutput>
+ </screen>
+ </para>
+ </step>
+ <step>
+ <para>
+ After review, the patch can be downloaded and then applied using <application>git</application>:
+ <screen>
+ <command>git apply 0001-Update-commands-for-starting-stopping-and-checking-t.patch</command>
+ </screen>
+ </para>
+ </step>
+ </procedure>
+</section>
+
+
+
+
+
+
+
+
+
diff --git a/en-US/workflow.xml b/en-US/workflow.xml
index 0624dac..dc392a9 100644
--- a/en-US/workflow.xml
+++ b/en-US/workflow.xml
@@ -10,7 +10,10 @@
</para>
<section>
<title>Write First, Format Later</title>
- <para/>
+ <para/>
+ <para>
+
+ </para>
</section>
<section>
<title>Formatting in DocBook</title>
@@ -35,7 +38,9 @@
<section>
<title>Building Packages from Documents</title>
<para>Building packages from documents is discussed in <xref linkend="sect-publican-packaging" />.</para>
- </section>
+ </section>
+ <!-- Section on creating a patch for a bug report or review -->
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="workflow-patching.xml"/>
</chapter>
<!--
Local variables:
1
0
[software-management-guide/f20] general improvements, closer to a release
by Guillermo Gómez 31 Dec '13
by Guillermo Gómez 31 Dec '13
31 Dec '13
commit bb909d66adda0eae22ce5eeb267499d9df3f37ea
Author: Guillermo Gómez <gomix(a)fedoraproject.org>
Date: Mon Dec 30 20:03:45 2013 -0430
general improvements, closer to a release
.../Extensiones_Yum/yum-extensions-available.txt | 30 +++++++++++
.../yum-install-extension-sample.txt | 17 ++++++
.../yum-plugin-ps/yum-plugin-ps-sample-1.txt | 39 ++++++++++++++
.../yum-plugin-ps/yum-plugin-ps-sample-2.txt | 34 +++++++++++++
.../yum-plugin-ps/yum-plugin-ps-sample-3.txt | 7 +++
.../.package-cleanup--oldkernel.txt.swp | Bin 0 -> 12288 bytes
.../.package-cleanup-no-problems.txt.swp | Bin 0 -> 12288 bytes
.../Utilidades_YUM/package-cleanup--dupes.txt | 9 +++
.../Utilidades_YUM/package-cleanup--oldkernel.txt | 19 +++++++
.../Utilidades_YUM/package-cleanup--orphans.txt | 11 ++++
.../Utilidades_YUM/package-cleanup--problems.txt | 6 ++
.../Utilidades_YUM/package-cleanup-no-problems.txt | 3 +
es-ES/extras/Utilidades_YUM/yum-autocompletado.txt | 17 ++++++
.../yum-install--downloadonly-falla.txt | 4 ++
.../yum-update--downloadonly-falla.txt | 3 +
es-ES/extras/Utilidades_YUM/yum-updateonboot.txt | 16 ++++++
.../yumdownloader--source-screen.txt | 5 ++
.../yumdownloader--urls-source-ruby-gtk2.txt | 3 +
.../extras/Utilidades_YUM/yumdownloader-screen.txt | 3 +
es-ES/yum-plugin/yum-plugin-ps.xml | 53 ++++++++++++++++++++
20 files changed, 279 insertions(+), 0 deletions(-)
---
diff --git a/es-ES/extras/Extensiones_Yum/yum-extensions-available.txt b/es-ES/extras/Extensiones_Yum/yum-extensions-available.txt
new file mode 100644
index 0000000..6d3543c
--- /dev/null
+++ b/es-ES/extras/Extensiones_Yum/yum-extensions-available.txt
@@ -0,0 +1,30 @@
+anaconda-yum-plugins.noarch : Installation-related yum plugins
+yum-rhn-plugin.noarch : Spacewalk support for yum
+PackageKit-yum-plugin.x86_64 : Tell PackageKit to check for updates when yum
+yum-dellsysid.x86_64 : YUM plugin to retrieve the Dell System ID
+yum-langpacks.noarch : Langpacks plugin for yum
+yum-plugin-aliases.noarch : Yum plugin to enable aliases filters
+yum-plugin-auto-update-debug-info.noarch : Yum plugin to enable automatic
+yum-plugin-changelog.noarch : Yum plugin for viewing package changelogs
+yum-plugin-fastestmirror.noarch : Yum plugin which chooses fastest repository
+yum-plugin-filter-data.noarch : Yum plugin to list filter based on package data
+yum-plugin-fs-snapshot.noarch : Yum plugin to automatically snapshot your
+yum-plugin-keys.noarch : Yum plugin to deal with signing keys
+yum-plugin-list-data.noarch : Yum plugin to list aggregate package data
+yum-plugin-local.noarch : Yum plugin to automatically manage a local repo. of
+yum-plugin-merge-conf.noarch : Yum plugin to merge configuration changes when
+yum-plugin-post-transaction-actions.noarch : Yum plugin to run arbitrary
+yum-plugin-protectbase.noarch : Yum plugin to protect packages from certain
+yum-plugin-ps.noarch : Yum plugin to look at processes, with respect to packages
+yum-plugin-puppetverify.noarch : Yum plugin to add puppet checksums to verify
+yum-plugin-refresh-updatesd.noarch : Tell yum-updatesd to check for updates when
+yum-plugin-remove-with-leaves.noarch : Yum plugin to remove dependencies which
+yum-plugin-rpm-warm-cache.noarch : Yum plugin to access the rpmdb files early to
+yum-plugin-security.noarch : Yum plugin to enable security filters
+yum-plugin-show-leaves.noarch : Yum plugin which shows newly installed leaf
+yum-plugin-tmprepo.noarch : Yum plugin to add temporary repositories
+yum-plugin-tsflags.noarch : Yum plugin to add tsflags by a commandline option
+yum-plugin-upgrade-helper.noarch : Yum plugin to help upgrades to the next
+yum-plugin-verify.noarch : Yum plugin to add verify command, and options
+yum-plugin-versionlock.noarch : Yum plugin to lock specified packages from being
+yum-plugin-priorities.noarch : plugin to give priorities to packages from
diff --git a/es-ES/extras/Extensiones_Yum/yum-install-extension-sample.txt b/es-ES/extras/Extensiones_Yum/yum-install-extension-sample.txt
new file mode 100644
index 0000000..384860b
--- /dev/null
+++ b/es-ES/extras/Extensiones_Yum/yum-install-extension-sample.txt
@@ -0,0 +1,17 @@
+$ su -c "yum install yum-plugin-downloadonly"
+...
+Dependencies Resolved
+=================================================================
+Package Arch Version Repository Size
+=================================================================
+Installing:
+
+yum-plugin-downloadonly noarch 1.1.24-2.fc12 updates 8.8 k
+
+Transaction Summary
+=================================================================
+Install 1 Package(s)
+Update 0 Package(s)
+Remove 0 Package(s)
+Total download size: 5.9 k
+Is this ok [y/N]:
diff --git a/es-ES/extras/Extensiones_Yum/yum-plugin-ps/yum-plugin-ps-sample-1.txt b/es-ES/extras/Extensiones_Yum/yum-plugin-ps/yum-plugin-ps-sample-1.txt
new file mode 100644
index 0000000..44bdcc7
--- /dev/null
+++ b/es-ES/extras/Extensiones_Yum/yum-plugin-ps/yum-plugin-ps-sample-1.txt
@@ -0,0 +1,39 @@
+$ su -c "yum ps all"
+
+Contraseña: *****
+
+ pid proc CPU RSS State uptime
+ConsoleKit-0.4.5-1.fc15.x86_64
+ 1227 console-kit-dae 0:00 1.9 MB Durmiendo: 1 day(s) 1:06:34
+GConf2-3.2.3-1.fc16.i686
+ 5602 gconfd-2 0:00 1.8 MB Durmiendo: 21:52:16
+GConf2-3.2.3-1.fc16.x86_64
+ 5602 gconfd-2 0:00 1.8 MB Durmiendo: 21:52:16
+ 5635 gnome-shell 12:06 70 MB Durmiendo: 21:52:13
+ 10170 e-calendar-fact 0:00 6.6 MB Durmiendo: 2:06:27
+...
+ModemManager-0.4-7.git20110201.fc15.i686 Upgrade 0.4.998-1.git20110706.fc15.i686
+ 977 modem-manager 0:00 2.3 MB Durmiendo: 02:15
+1:NetworkManager-0.8.999-2.git20110509.fc15.i686 Upgrade 1:0.9.1.90-3.git20110927.fc15.i686
+ 853 NetworkManager 0:00 5.6 MB Durmiendo: 02:18
+...
+
+xulrunner-8.0-1.fc16.x86_64
+ 7924 firefox 62:29 579 MB Durmiendo: 18:28:31
+xz-libs-5.1.1-1alpha.fc16.x86_64
+ 4924 nautilus 0:09 11 MB Durmiendo: 6:27:39
+ 12210 yum 0:05 97 MB Ejecutando: 00:07
+yum-3.4.3-5.fc16.noarch
+ 12210 yum 0:05 97 MB Ejecutando: 00:07
+yum-metadata-parser-1.1.4-5.fc16.x86_64
+ 12210 yum 0:05 97 MB Ejecutando: 00:07
+zlib-1.2.5-5.fc16.x86_64
+ 905 NetworkManager 0:05 3.0 MB Durmiendo: 1 day(s) 1:06:50
+ 951 rsyslogd 0:00 596 kB Durmiendo: 1 day(s) 1:06:49
+ 1008 polkitd 0:01 2.2 MB Durmiendo: 1 day(s) 1:06:45
+ ...
+ ...
+ 12171 ssh 0:00 3.7 MB Durmiendo: 03:36
+ 12205 gvim 0:00 15 MB Durmiendo: 00:29
+ 12210 yum 0:05 97 MB Ejecutando: 00:07
+ps
diff --git a/es-ES/extras/Extensiones_Yum/yum-plugin-ps/yum-plugin-ps-sample-2.txt b/es-ES/extras/Extensiones_Yum/yum-plugin-ps/yum-plugin-ps-sample-2.txt
new file mode 100644
index 0000000..3a2bb98
--- /dev/null
+++ b/es-ES/extras/Extensiones_Yum/yum-plugin-ps/yum-plugin-ps-sample-2.txt
@@ -0,0 +1,34 @@
+# yum ps updates
+...
+ pid proc CPU RSS State uptime
+ImageMagick-6.6.4.1-15.fc14.i686 Upgrade 6.6.4.1-16.fc14.i686
+ 12318 unicorn_rails 8:34 72 MB Sleeping: 4:24:23
+ 12327 unicorn_rails 8:33 80 MB Sleeping: 4:23:38
+ 15279 unicorn_rails 0:16 69 MB Running: 03:49
+ 15280 unicorn_rails 0:13 68 MB Sleeping: 03:49
+...
+...
+avahi-0.6.27-2.fc14.i686 Upgrade 0.6.27-8.fc14.i686
+ 1097 avahi-daemon 0:04 1.1 MB Sleeping: 17 day(s) 10:00:59
+ 1098 avahi-daemon 0:00 24 kB Sleeping: 17 day(s) 10:00:59
+...
+...
+12:dhclient-4.2.0-23.P2.fc14.i686
+ 18178 dhclient 0:00 3.1 MB Sleeping: *3 day(s) 7:26:16
+freetype-2.4.2-7.fc14.i686
+ 1007 sedispatch 0:00 1.1 MB Sleeping: *17 day(s) 10:10:00
+ 1973 Xorg 0:52 13 MB Sleeping: *17 day(s) 10:09:12
+ 2061 gnome-session 0:00 5.5 MB Sleeping: *17 day(s) 10:09:04
+...
+...
+7:squid-3.1.12-1.fc14.i686 Upgrade 7:3.1.16-1.fc14.i686
+ 1865 squid 0:00 2.2 MB Sleeping: 17 day(s) 10:09:21
+ 1868 squid 36:00 294 MB Sleeping: 17 day(s) 10:09:21
+ 1871 unlinkd 0:00 816 kB Sleeping: 17 day(s) 10:09:21
+udev-161-8.fc14.i686 Upgrade 161-10.fc14.i686
+ 437 udevd 0:00 516 kB Sleeping: 17 day(s) 10:10:16
+ 1959 udevd 0:00 480 kB Sleeping: 17 day(s) 10:09:17
+ 1960 udevd 0:00 464 kB Sleeping: 17 day(s) 10:09:17
+xorg-x11-server-Xorg-1.9.5-1.fc14.i686 Upgrade 1.9.5-2.fc14.i686
+ 1973 Xorg 0:52 13 MB Sleeping: 17 day(s) 10:09:16
+ps
diff --git a/es-ES/extras/Extensiones_Yum/yum-plugin-ps/yum-plugin-ps-sample-3.txt b/es-ES/extras/Extensiones_Yum/yum-plugin-ps/yum-plugin-ps-sample-3.txt
new file mode 100644
index 0000000..c815938
--- /dev/null
+++ b/es-ES/extras/Extensiones_Yum/yum-plugin-ps/yum-plugin-ps-sample-3.txt
@@ -0,0 +1,7 @@
+## Pendiente.. no tengo salida interesante aquí
+$ su -c "yum ps restart"
+
+Contraseña: ******
+
+ pid proc CPU RSS State uptime
+ps
diff --git a/es-ES/extras/Utilidades_YUM/.package-cleanup--oldkernel.txt.swp b/es-ES/extras/Utilidades_YUM/.package-cleanup--oldkernel.txt.swp
new file mode 100644
index 0000000..8a1c5dd
Binary files /dev/null and b/es-ES/extras/Utilidades_YUM/.package-cleanup--oldkernel.txt.swp differ
diff --git a/es-ES/extras/Utilidades_YUM/.package-cleanup-no-problems.txt.swp b/es-ES/extras/Utilidades_YUM/.package-cleanup-no-problems.txt.swp
new file mode 100644
index 0000000..ebde138
Binary files /dev/null and b/es-ES/extras/Utilidades_YUM/.package-cleanup-no-problems.txt.swp differ
diff --git a/es-ES/extras/Utilidades_YUM/package-cleanup--dupes.txt b/es-ES/extras/Utilidades_YUM/package-cleanup--dupes.txt
new file mode 100644
index 0000000..dd57511
--- /dev/null
+++ b/es-ES/extras/Utilidades_YUM/package-cleanup--dupes.txt
@@ -0,0 +1,9 @@
+$ package-cleanup --dupes
+...
+samba-3.2.8-0.27.fc10.i386
+samba-3.2.8-0.26.fc10.i386
+libtalloc-1.2.0-26.fc10.i386
+libtalloc-1.2.0-27.fc10.i386
+wireshark-gnome-1.0.6-1.fc10.i386
+wireshark-gnome-1.0.5-1.fc10.i386
+...
diff --git a/es-ES/extras/Utilidades_YUM/package-cleanup--oldkernel.txt b/es-ES/extras/Utilidades_YUM/package-cleanup--oldkernel.txt
new file mode 100644
index 0000000..8dc2228
--- /dev/null
+++ b/es-ES/extras/Utilidades_YUM/package-cleanup--oldkernel.txt
@@ -0,0 +1,19 @@
+# package-cleanup --oldkernel
+Setting up yum
+...
+I will remove the following 3 kernel related packages:
+kernel-2.6.30.5-43.fc11.i586
+kernel-devel-2.6.29.6-217.2.16.fc11.i586
+kernel-devel-2.6.30.5-43.fc11.i586
+Is this ok [y/N]: y
+
+# rpm -qa kernel*
+kernel-headers-2.6.30.9-90.fc11.i586
+kernel-2.6.30.8-64.fc11.i586
+kernel-devel-2.6.30.8-64.fc11.i586
+kernel-2.6.30.9-90.fc11.i586
+kernel-devel-2.6.30.9-90.fc11.i586
+kernel-doc-2.6.30.9-90.fc11.noarch
+kernel-firmware-2.6.30.9-90.fc11.noarch
+# uname -r
+2.6.30.9-90.fc11.i586
diff --git a/es-ES/extras/Utilidades_YUM/package-cleanup--orphans.txt b/es-ES/extras/Utilidades_YUM/package-cleanup--orphans.txt
new file mode 100644
index 0000000..428bb76
--- /dev/null
+++ b/es-ES/extras/Utilidades_YUM/package-cleanup--orphans.txt
@@ -0,0 +1,11 @@
+$ package-cleanup --orphans
+...
+NetworkManager-0.8.9997-1.git20110531.fc15.x86_64
+NetworkManager-glib-0.8.9997-1.git20110531.fc15.x86_64
+NetworkManager-gnome-0.8.9997-1.git20110531.fc15.x86_64
+adobe-release-i386-1.0-1.noarch
+control-center-3.0.1.1-6.fc15.x86_64
+control-center-filesystem-3.0.1.1-6.fc15.x86_64
+cpp-4.6.0-7.fc15.x86_64
+dbus-qt-0.70-7.fc12.x86_64
+...
diff --git a/es-ES/extras/Utilidades_YUM/package-cleanup--problems.txt b/es-ES/extras/Utilidades_YUM/package-cleanup--problems.txt
new file mode 100644
index 0000000..c6732ce
--- /dev/null
+++ b/es-ES/extras/Utilidades_YUM/package-cleanup--problems.txt
@@ -0,0 +1,6 @@
+$ package-cleanup --problems
+...
+Package compiz-0.9.5.92.1-0.2.gite676f1b12eb8db3a76978eed5bfc7c2cf9a0b6ce.fc16.x86_64 no se encuentran necesita de libboost_serialization-mt.so.1.47.0()(64bit)
+Package compiz-gtk-0.9.5.92.1-0.2.gite676f1b12eb8db3a76978eed5bfc7c2cf9a0b6ce.fc16.x86_64 no se encuentran necesita de libboost_serialization-mt.so.1.47.0()(64bit)
+Package compiz-plugins-main-0.9.5.92-1.fc16.x86_64 no se encuentran necesita de libboost_serialization-mt.so.1.47.0()(64bit)
+Package libcompizconfig-0.9.5.92-1.fc16.x86_64 no se encuentran necesita de libboost_serialization-mt.so.1.47.0()(64bit)
diff --git a/es-ES/extras/Utilidades_YUM/package-cleanup-no-problems.txt b/es-ES/extras/Utilidades_YUM/package-cleanup-no-problems.txt
new file mode 100644
index 0000000..c3eb3bc
--- /dev/null
+++ b/es-ES/extras/Utilidades_YUM/package-cleanup-no-problems.txt
@@ -0,0 +1,3 @@
+$ package-cleanup --problems
+Complementos cargados:presto, refresh-packagekit
+No Problems Found
diff --git a/es-ES/extras/Utilidades_YUM/yum-autocompletado.txt b/es-ES/extras/Utilidades_YUM/yum-autocompletado.txt
new file mode 100644
index 0000000..bb86382
--- /dev/null
+++ b/es-ES/extras/Utilidades_YUM/yum-autocompletado.txt
@@ -0,0 +1,17 @@
+$ yum ins<tab>
+$ yum install
+$ yum install bas<tab><tab>
+ bashdb.noarch basket-libs.i686 bastet.x86_64
+ bash-doc.x86_64 basket-libs.x86_64
+ BasiliskII.x86_64 basket.x86_64
+
+$ repoquery --repo<tab>
+ --repofrompath --repoid
+
+$ repoquery --repoid fedora<tab><tab>
+ fedora fedora-debuginfo
+ fedora-appmarket fedora-latam
+ fedora-chromium fedora-latam-debuginfo
+ fedora-chromium-source fedora-latam-source
+ fedora-chromium-stable fedora-source
+ fedora-chromium-stable-source
diff --git a/es-ES/extras/Utilidades_YUM/yum-install--downloadonly-falla.txt b/es-ES/extras/Utilidades_YUM/yum-install--downloadonly-falla.txt
new file mode 100644
index 0000000..73f49c8
--- /dev/null
+++ b/es-ES/extras/Utilidades_YUM/yum-install--downloadonly-falla.txt
@@ -0,0 +1,4 @@
+$ su -c "yum install --downloadonly screen"
+...
+El paquete screen-4.1.0-0.17.20120314git3c2946.fc20.x86_64 ya se encuentra instalado con su versión más reciente
+Nada para hacer
diff --git a/es-ES/extras/Utilidades_YUM/yum-update--downloadonly-falla.txt b/es-ES/extras/Utilidades_YUM/yum-update--downloadonly-falla.txt
new file mode 100644
index 0000000..f37ed79
--- /dev/null
+++ b/es-ES/extras/Utilidades_YUM/yum-update--downloadonly-falla.txt
@@ -0,0 +1,3 @@
+$ su -c "yum update --downloadonly screen"
+...
+No packages marked for update
diff --git a/es-ES/extras/Utilidades_YUM/yum-updateonboot.txt b/es-ES/extras/Utilidades_YUM/yum-updateonboot.txt
new file mode 100644
index 0000000..d6a2915
--- /dev/null
+++ b/es-ES/extras/Utilidades_YUM/yum-updateonboot.txt
@@ -0,0 +1,16 @@
+# Si cualquiera de estos rpms son actualizados, yum-updateonboot mandará a
+# reiniciar el equipo inmediatamente después de yum udpate.
+# Para evitar que yum-updateonoot reinicie su máquina , comente la
+# siguiente línea
+#REBOOT_RPMS="kernel kernel-smp"
+
+# Lista de grupos que deben ser actualizados al inicio.
+# Para cada grupo mencionado
+# yum-updateonboot llamará 'yum -y groupupdate'
+# Ya que los grupos tienden a tener espacios en sus nombres,
+# use punto y coma para separarlos
+#GROUPLIST="My Group;MyOtherGroup;Some_Group;My Group 4"
+
+# Silencioso al actualizar, por omisión es así
+# Estas opciones son pasadas a yum, por omisión es "-q"
+#OPTIONS="-q"
diff --git a/es-ES/extras/Utilidades_YUM/yumdownloader--source-screen.txt b/es-ES/extras/Utilidades_YUM/yumdownloader--source-screen.txt
new file mode 100644
index 0000000..38202df
--- /dev/null
+++ b/es-ES/extras/Utilidades_YUM/yumdownloader--source-screen.txt
@@ -0,0 +1,5 @@
+$ yumdownloader --source zsh
+...
+Enabling fedora-source repository
+fedora-source/metalink | 1.7 kB 00:00
+zsh-4.3.11-2.fc15.src.rpm | 2.6 MB 00:30
diff --git a/es-ES/extras/Utilidades_YUM/yumdownloader--urls-source-ruby-gtk2.txt b/es-ES/extras/Utilidades_YUM/yumdownloader--urls-source-ruby-gtk2.txt
new file mode 100644
index 0000000..d0cfdd0
--- /dev/null
+++ b/es-ES/extras/Utilidades_YUM/yumdownloader--urls-source-ruby-gtk2.txt
@@ -0,0 +1,3 @@
+$ yumdownloader --urls --source ruby-gtk2
+...
+http://fedora.c3sl.ufpr.br/linux/updates/13/SRPMS//ruby-gnome2-0.90.2-1.fc13.src.rpm
diff --git a/es-ES/extras/Utilidades_YUM/yumdownloader-screen.txt b/es-ES/extras/Utilidades_YUM/yumdownloader-screen.txt
new file mode 100644
index 0000000..9191994
--- /dev/null
+++ b/es-ES/extras/Utilidades_YUM/yumdownloader-screen.txt
@@ -0,0 +1,3 @@
+$ su -c "yumdownloader screen"
+...
+screen-4.1.0-0.17.20120314git3c2946.fc20.x86_64.rpm | 555 kB 00:00:04
diff --git a/es-ES/yum-plugin/yum-plugin-ps.xml b/es-ES/yum-plugin/yum-plugin-ps.xml
new file mode 100644
index 0000000..d15ef16
--- /dev/null
+++ b/es-ES/yum-plugin/yum-plugin-ps.xml
@@ -0,0 +1,53 @@
+<?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 "Manual_para_gestion_del_software.ent">
+%BOOK_ENTITIES;
+]>
+
+<section>
+ <title>yum-plugin-ps</title>
+ <para>Extensión yum que observa los procesos del sistema con respecto a los paquetes.</para>
+
+ <para>Cuando se instala esta extensión se agrega el comando yum "ps" que permite ver qué procesos están asociados con paquetes, y de si necesitan ser reiniciados o tienen actualizaciones, etc.</para>
+
+<para>Esta extensión agrega el comando <command>ps</command>.</para>
+ <variablelist>
+ <varlistentry>
+ <term><command>yum ps [all|updates|restart] [pkgs...]</command></term>
+ <listitem><para>Lista procesos, agrupados e identificados por paquetes.</para></listitem>
+ </varlistentry>
+ </variablelist>
+
+ <section>
+ <title>Configuración</title>
+ <para><filename>/etc/yum/pluginconf.d/ps.conf</filename></para>
+<screen>
+[main]
+enabled=1
+</screen>
+
+<variablelist>
+ <varlistentry>
+ <term><parameter>enabled = 0|1</parameter></term>
+ <listitem><para>Habilita la extensión a nivel general.</para></listitem>
+ </varlistentry>
+</variablelist>
+ </section>
+
+
+ <section><title>Ejemplos de uso</title>
+ <para><command>yum ps all</command>: lista todos los procesos en ejecución y mapeando dichos procesos a nombres de paquete. Incluye identificar entradas de paquetes que tienen actualizaciones.</para>
+
+ <screen><xi:include parse="text" href="../extras/Extensiones_Yum/yum-plugin-ps/yum-plugin-ps-sample-1.txt" xmlns:xi="http://www.w3.org/2001/XInclude" /></screen>
+
+ <para><command>yum ps updates</command> o <command>yum ps</command>: lista procesos y señala cuáles paquetes tienen actualizaciones disponibles.</para>
+
+ <screen><xi:include parse="text" href="../extras/Extensiones_Yum/yum-plugin-ps/yum-plugin-ps-sample-2.txt" xmlns:xi="http://www.w3.org/2001/XInclude" /></screen>
+
+ <para><command>yum ps restart</command>: lista procesos identificados a paquetes correspondientes que deben ser reiniciados.</para>
+
+ <screen><xi:include parse="text" href="../extras/Extensiones_Yum/yum-plugin-ps/yum-plugin-ps-sample-3.txt" xmlns:xi="http://www.w3.org/2001/XInclude" /></screen>
+
+ </section>
+</section>
+
1
0
[web] bumping install-guide available on docs.fp.o to publish updated fedup info
by Pete Travis 22 Dec '13
by Pete Travis 22 Dec '13
22 Dec '13
commit f3fcfdb1eea4488a60d320c325f338cf81c1644a
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Sun Dec 22 12:48:37 2013 -0700
bumping install-guide available on docs.fp.o to publish updated fedup info
fedoradocs.db | Bin 1024000 -> 1024000 bytes
public_html/Sitemap | 8 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/as-IN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/as-IN/opds-Fedora_Core.xml | 2 +-
public_html/as-IN/opds-Fedora_Documentation.xml | 2 +-
.../as-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/as-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/as-IN/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/bg-BG/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/bg-BG/opds-Fedora_Core.xml | 2 +-
public_html/bg-BG/opds-Fedora_Documentation.xml | 2 +-
.../bg-BG/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/bg-BG/opds-Fedora_Security_Team.xml | 2 +-
public_html/bg-BG/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/bn-IN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/bn-IN/opds-Fedora_Core.xml | 2 +-
public_html/bn-IN/opds-Fedora_Documentation.xml | 2 +-
.../bn-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/bn-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/bn-IN/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/bs-BA/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/bs-BA/opds-Fedora_Core.xml | 2 +-
public_html/bs-BA/opds-Fedora_Documentation.xml | 2 +-
.../bs-BA/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/bs-BA/opds-Fedora_Security_Team.xml | 2 +-
public_html/bs-BA/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ca-ES/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ca-ES/opds-Fedora_Core.xml | 2 +-
public_html/ca-ES/opds-Fedora_Documentation.xml | 2 +-
.../ca-ES/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ca-ES/opds-Fedora_Security_Team.xml | 2 +-
public_html/ca-ES/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/cs-CZ/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/cs-CZ/opds-Fedora_Core.xml | 2 +-
public_html/cs-CZ/opds-Fedora_Documentation.xml | 2 +-
.../cs-CZ/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/cs-CZ/opds-Fedora_Security_Team.xml | 2 +-
public_html/cs-CZ/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/da-DK/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/da-DK/opds-Fedora_Core.xml | 2 +-
public_html/da-DK/opds-Fedora_Documentation.xml | 2 +-
.../da-DK/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/da-DK/opds-Fedora_Security_Team.xml | 2 +-
public_html/da-DK/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/de-DE/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/de-DE/opds-Fedora_Core.xml | 2 +-
public_html/de-DE/opds-Fedora_Documentation.xml | 2 +-
.../de-DE/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/de-DE/opds-Fedora_Security_Team.xml | 2 +-
public_html/de-DE/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/el-GR/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/el-GR/opds-Fedora_Core.xml | 2 +-
public_html/el-GR/opds-Fedora_Documentation.xml | 2 +-
.../el-GR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/el-GR/opds-Fedora_Security_Team.xml | 2 +-
public_html/el-GR/opds.xml | 16 +-
.../Fedora-20-Installation_Guide-en-US.epub | Bin 5105134 -> 5173431 bytes
.../images/diskpartitioning/btrfs.png | Bin 25705 -> 34032 bytes
.../images/diskpartitioning/confirm.png | Bin 0 -> 57630 bytes
.../images/diskpartitioning/software-raid.png | Bin 28111 -> 37100 bytes
.../20/html-single/Installation_Guide/index.html | 1012 ++++++++++----------
.../Installation_Guide/Begin_installation-x86.html | 8 +-
.../20/html/Installation_Guide/Create_LVM-x86.html | 6 +-
.../Create_Software_RAID-x86.html | 2 +-
...ide-Creating_and_Saving_Backup_Passphrases.html | 2 +-
.../Disk_Encryption_Guide-Saving_Passphrases.html | 2 +-
.../Installation_Guide/Disk_Encryption_Guide.html | 2 +-
.../20/html/Installation_Guide/Disk_Space-x86.html | 6 +-
.../Installation-Guide-Preface.html | 8 +-
.../Trouble_After_Booting-GUI.html | 2 +-
.../html/Installation_Guide/ap-admin-options.html | 30 +-
.../20/html/Installation_Guide/ap-techref.html | 26 +-
.../Fedora/20/html/Installation_Guide/apcs02.html | 4 +-
.../20/html/Installation_Guide/apcs02s02.html | 2 +-
.../20/html/Installation_Guide/apcs02s03.html | 2 +-
.../Fedora/20/html/Installation_Guide/apcs03.html | 4 +-
.../Fedora/20/html/Installation_Guide/apcs04.html | 4 +-
.../20/html/Installation_Guide/apcs04s03.html | 2 +-
.../20/html/Installation_Guide/apcs04s04.html | 2 +-
.../20/html/Installation_Guide/apcs04s05.html | 2 +-
.../20/html/Installation_Guide/apcs04s06.html | 2 +-
.../20/html/Installation_Guide/apcs04s07.html | 2 +-
.../Fedora/20/html/Installation_Guide/apcs05.html | 6 +-
.../20/html/Installation_Guide/apcs05s02.html | 2 +-
.../20/html/Installation_Guide/apcs05s03.html | 2 +-
.../20/html/Installation_Guide/ch-Boot-x86.html | 28 +-
.../ch-Installation_Phase_2-x86.html | 14 +-
.../html/Installation_Guide/ch-Preparing-x86.html | 4 +-
.../20/html/Installation_Guide/ch-ent-table.html | 2 +-
.../20/html/Installation_Guide/ch-guimode-x86.html | 8 +-
.../20/html/Installation_Guide/ch-kickstart2.html | 2 +-
.../20/html/Installation_Guide/ch-new-users.html | 18 +-
.../20/html/Installation_Guide/ch-next-steps.html | 27 +-
.../html/Installation_Guide/ch-partitions-x86.html | 40 +-
.../ch-redhat-config-kickstart.html | 20 +-
.../20/html/Installation_Guide/ch-steps-x86.html | 2 +-
.../20/html/Installation_Guide/ch-trouble-x86.html | 6 +-
.../20/html/Installation_Guide/ch-upgrade-x86.html | 14 +-
.../html/Installation_Guide/ch-x86-uninstall.html | 4 +-
.../Fedora/20/html/Installation_Guide/ch04s06.html | 4 +-
.../Fedora/20/html/Installation_Guide/ch10s02.html | 2 +-
.../Fedora/20/html/Installation_Guide/ch10s04.html | 2 +-
.../20/html/Installation_Guide/ch10s04s04.html | 4 +-
.../20/html/Installation_Guide/ch10s04s05.html | 2 +-
.../20/html/Installation_Guide/ch10s04s06.html | 2 +-
.../20/html/Installation_Guide/ch10s04s08.html | 2 +-
.../20/html/Installation_Guide/ch10s04s09.html | 2 +-
.../20/html/Installation_Guide/ch13s05s03.html | 2 +-
.../Fedora/20/html/Installation_Guide/ch18s02.html | 51 +-
.../Fedora/20/html/Installation_Guide/ch18s03.html | 99 ++
.../images/diskpartitioning/btrfs.png | Bin 25705 -> 34032 bytes
.../images/diskpartitioning/confirm.png | Bin 0 -> 57630 bytes
.../images/diskpartitioning/software-raid.png | Bin 28111 -> 37100 bytes
.../Fedora/20/html/Installation_Guide/index.html | 6 +-
.../installation-source-x86.html | 2 +-
.../Fedora/20/html/Installation_Guide/ix01.html | 2 +-
.../Installation_Guide/language-selection-x86.html | 2 +-
.../Installation_Guide/language-support-x86.html | 2 +-
.../Installation_Guide/netboot-performing.html | 2 +-
.../Fedora/20/html/Installation_Guide/pr01s02.html | 2 +-
.../Fedora/20/html/Installation_Guide/pr01s03.html | 2 +-
.../pt-Advanced_installation_options.html | 2 +-
.../Installation_Guide/pt-After_installation.html | 4 +-
.../pt-Technical_appendixes.html | 4 +-
.../Installation_Guide/pt-install-info-x86.html | 4 +-
.../html/Installation_Guide/s1-complete-x86.html | 4 +-
.../s1-diskpartitioning-confirm.html | 13 +
.../s1-diskpartitioning-x86.html | 18 +-
.../Installation_Guide/s1-diskpartsetup-x86.html | 12 +-
.../s1-guimode-interface-x86.html | 4 +-
.../Installation_Guide/s1-installmethod-x86.html | 16 +-
.../Installation_Guide/s1-kickstart2-file.html | 2 +-
.../s1-kickstart2-install-tree.html | 4 +-
.../Installation_Guide/s1-kickstart2-options.html | 116 ++--
.../s1-kickstart2-packageselection.html | 2 +-
.../s1-kickstart2-postinstallconfig.html | 2 +-
.../s1-kickstart2-preinstallconfig.html | 2 +-
.../s1-kickstart2-putkickstarthere.html | 8 +-
.../s1-kickstart2-startinginstall.html | 6 +-
.../s1-netboot-pxe-config-efi.html | 2 +-
.../Installation_Guide/s1-netboot-pxe-config.html | 4 +-
.../Installation_Guide/s1-pkgselection-x86.html | 12 +-
.../Installation_Guide/s1-progresshub-x86.html | 14 +-
.../s1-redhat-config-kickstart-auth.html | 4 +-
.../s1-redhat-config-kickstart-bootloader.html | 4 +-
.../s1-redhat-config-kickstart-firewall.html | 4 +-
.../s1-redhat-config-kickstart-install.html | 2 +-
.../s1-redhat-config-kickstart-network.html | 4 +-
.../s1-redhat-config-kickstart-partitions.html | 4 +-
.../s1-redhat-config-kickstart-pkgs.html | 2 +-
.../s1-redhat-config-kickstart-postinstall.html | 2 +-
.../s1-redhat-config-kickstart-prescript.html | 2 +-
.../s1-redhat-config-kickstart-savefile.html | 2 +-
.../s1-redhat-config-kickstart-xconfig.html | 2 +-
.../s1-steps-hd-installs-x86.html | 2 +-
.../html/Installation_Guide/s1-timezone-x86.html | 2 +-
.../Installation_Guide/s1-trouble-install-x86.html | 2 +-
.../html/Installation_Guide/s1-x86-bootloader.html | 8 +-
.../s2-diskpartrecommend-x86.html | 32 +-
.../s2-kickstart2-networkbased.html | 2 +-
.../Installation_Guide/s2-netboot-custom-msg.html | 2 +-
.../s2-trouble-completeparts-x86.html | 2 +-
.../s2-trouble-grub-command-line.html | 2 +-
.../s2-trouble-part-tables-x86.html | 2 +-
.../20/html/Installation_Guide/s2-trouble-ram.html | 2 +-
.../Installation_Guide/s2-trouble-space-x86.html | 2 +-
.../s2-trouble-tracebacks-x86.html | 2 +-
.../sect-boot-options-maintenance.html | 2 +-
.../sect-boot-options-mediacheck.html | 2 +-
.../sect-boot-options-rescue.html | 2 +-
.../sect-other-initial-setup.html | 2 +-
.../sn-Is_Your_Hardware_Compatible-x86.html | 2 +-
.../html/Installation_Guide/sn-Netconfig-x86.html | 16 +-
.../sn-booting-from-pxe-x86.html | 2 +-
.../20/html/Installation_Guide/sn-community.html | 6 +-
.../Installation_Guide/sn-expert-download.html | 2 +-
.../html/Installation_Guide/sn-expert-prepare.html | 2 +-
.../sn-firstboot-systemuser.html | 6 +-
.../sn-guimode-virtual-consoles-x86.html | 2 +-
.../html/Installation_Guide/sn-keyboard-x86.html | 2 +-
.../html/Installation_Guide/sn-making-media.html | 2 +-
.../Installation_Guide/sn-news-subscriptions.html | 6 +-
.../Installation_Guide/sn-partitioning-lvm.html | 8 +-
.../sn-partitioning-raid-x86.html | 2 +-
.../Installation_Guide/sn-pxe-server-manual.html | 4 +-
.../sn-switching-to-gui-login.html | 112 +--
.../20/html/Installation_Guide/sn-web-help.html | 12 +-
.../Fedora-20-Installation_Guide-en-US.pdf | Bin 4124434 -> 4139969 bytes
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/en-US/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/en-US/opds-Fedora_Core.xml | 2 +-
public_html/en-US/opds-Fedora_Documentation.xml | 2 +-
.../en-US/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/en-US/opds-Fedora_Security_Team.xml | 2 +-
public_html/en-US/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/es-ES/opds-Fedora.xml | 4 +-
public_html/es-ES/opds-Fedora_15.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/es-ES/opds-Fedora_Core.xml | 2 +-
public_html/es-ES/opds-Fedora_Documentation.xml | 2 +-
.../es-ES/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/es-ES/opds-Fedora_Security_Team.xml | 2 +-
public_html/es-ES/opds.xml | 18 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/fa-IR/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/fa-IR/opds-Fedora_Core.xml | 2 +-
public_html/fa-IR/opds-Fedora_Documentation.xml | 2 +-
.../fa-IR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/fa-IR/opds-Fedora_Security_Team.xml | 2 +-
public_html/fa-IR/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/fi-FI/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/fi-FI/opds-Fedora_Core.xml | 2 +-
public_html/fi-FI/opds-Fedora_Documentation.xml | 2 +-
.../fi-FI/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/fi-FI/opds-Fedora_Security_Team.xml | 2 +-
public_html/fi-FI/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/fr-FR/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/fr-FR/opds-Fedora_Core.xml | 2 +-
public_html/fr-FR/opds-Fedora_Documentation.xml | 2 +-
.../fr-FR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/fr-FR/opds-Fedora_Security_Team.xml | 2 +-
public_html/fr-FR/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/gu-IN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/gu-IN/opds-Fedora_Core.xml | 2 +-
public_html/gu-IN/opds-Fedora_Documentation.xml | 2 +-
.../gu-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/gu-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/gu-IN/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/he-IL/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/he-IL/opds-Fedora_Core.xml | 2 +-
public_html/he-IL/opds-Fedora_Documentation.xml | 2 +-
.../he-IL/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/he-IL/opds-Fedora_Security_Team.xml | 2 +-
public_html/he-IL/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/hi-IN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/hi-IN/opds-Fedora_Core.xml | 2 +-
public_html/hi-IN/opds-Fedora_Documentation.xml | 2 +-
.../hi-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/hi-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/hi-IN/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/hu-HU/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/hu-HU/opds-Fedora_Core.xml | 2 +-
public_html/hu-HU/opds-Fedora_Documentation.xml | 2 +-
.../hu-HU/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/hu-HU/opds-Fedora_Security_Team.xml | 2 +-
public_html/hu-HU/opds.xml | 16 +-
.../ia/opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ia/opds-Fedora.xml | 4 +-
.../ia/opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ia/opds-Fedora_Core.xml | 2 +-
public_html/ia/opds-Fedora_Documentation.xml | 2 +-
public_html/ia/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ia/opds-Fedora_Security_Team.xml | 2 +-
public_html/ia/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/id-ID/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/id-ID/opds-Fedora_Core.xml | 2 +-
public_html/id-ID/opds-Fedora_Documentation.xml | 2 +-
.../id-ID/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/id-ID/opds-Fedora_Security_Team.xml | 2 +-
public_html/id-ID/opds.xml | 16 +-
public_html/index.html | 2 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/it-IT/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/it-IT/opds-Fedora_Core.xml | 2 +-
public_html/it-IT/opds-Fedora_Documentation.xml | 2 +-
.../it-IT/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/it-IT/opds-Fedora_Security_Team.xml | 2 +-
public_html/it-IT/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ja-JP/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ja-JP/opds-Fedora_Core.xml | 2 +-
public_html/ja-JP/opds-Fedora_Documentation.xml | 2 +-
.../ja-JP/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ja-JP/opds-Fedora_Security_Team.xml | 2 +-
public_html/ja-JP/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/kn-IN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/kn-IN/opds-Fedora_Core.xml | 2 +-
public_html/kn-IN/opds-Fedora_Documentation.xml | 2 +-
.../kn-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/kn-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/kn-IN/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ko-KR/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ko-KR/opds-Fedora_Core.xml | 2 +-
public_html/ko-KR/opds-Fedora_Documentation.xml | 2 +-
.../ko-KR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ko-KR/opds-Fedora_Security_Team.xml | 2 +-
public_html/ko-KR/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/lt-LT/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/lt-LT/opds-Fedora_Core.xml | 2 +-
public_html/lt-LT/opds-Fedora_Documentation.xml | 2 +-
.../lt-LT/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/lt-LT/opds-Fedora_Security_Team.xml | 2 +-
public_html/lt-LT/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ml-IN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ml-IN/opds-Fedora_Core.xml | 2 +-
public_html/ml-IN/opds-Fedora_Documentation.xml | 2 +-
.../ml-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ml-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/ml-IN/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/mr-IN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/mr-IN/opds-Fedora_Core.xml | 2 +-
public_html/mr-IN/opds-Fedora_Documentation.xml | 2 +-
.../mr-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/mr-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/mr-IN/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/nb-NO/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/nb-NO/opds-Fedora_Core.xml | 2 +-
public_html/nb-NO/opds-Fedora_Documentation.xml | 2 +-
.../nb-NO/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/nb-NO/opds-Fedora_Security_Team.xml | 2 +-
public_html/nb-NO/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/nl-NL/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/nl-NL/opds-Fedora_Core.xml | 2 +-
public_html/nl-NL/opds-Fedora_Documentation.xml | 2 +-
.../nl-NL/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/nl-NL/opds-Fedora_Security_Team.xml | 2 +-
public_html/nl-NL/opds.xml | 16 +-
public_html/opds.xml | 92 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/or-IN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/or-IN/opds-Fedora_Core.xml | 2 +-
public_html/or-IN/opds-Fedora_Documentation.xml | 2 +-
.../or-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/or-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/or-IN/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pa-IN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pa-IN/opds-Fedora_Core.xml | 2 +-
public_html/pa-IN/opds-Fedora_Documentation.xml | 2 +-
.../pa-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pa-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/pa-IN/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pl-PL/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pl-PL/opds-Fedora_Core.xml | 2 +-
public_html/pl-PL/opds-Fedora_Documentation.xml | 2 +-
.../pl-PL/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pl-PL/opds-Fedora_Security_Team.xml | 2 +-
public_html/pl-PL/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pt-BR/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pt-BR/opds-Fedora_Core.xml | 2 +-
public_html/pt-BR/opds-Fedora_Documentation.xml | 2 +-
.../pt-BR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pt-BR/opds-Fedora_Security_Team.xml | 2 +-
public_html/pt-BR/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pt-PT/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pt-PT/opds-Fedora_Core.xml | 2 +-
public_html/pt-PT/opds-Fedora_Documentation.xml | 2 +-
.../pt-PT/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pt-PT/opds-Fedora_Security_Team.xml | 2 +-
public_html/pt-PT/opds.xml | 16 +-
.../ro/opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ro/opds-Fedora.xml | 4 +-
.../ro/opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ro/opds-Fedora_Core.xml | 2 +-
public_html/ro/opds-Fedora_Documentation.xml | 2 +-
public_html/ro/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ro/opds-Fedora_Security_Team.xml | 2 +-
public_html/ro/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ru-RU/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ru-RU/opds-Fedora_Core.xml | 2 +-
public_html/ru-RU/opds-Fedora_Documentation.xml | 2 +-
.../ru-RU/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ru-RU/opds-Fedora_Security_Team.xml | 2 +-
public_html/ru-RU/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sk-SK/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sk-SK/opds-Fedora_Core.xml | 2 +-
public_html/sk-SK/opds-Fedora_Documentation.xml | 2 +-
.../sk-SK/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/sk-SK/opds-Fedora_Security_Team.xml | 2 +-
public_html/sk-SK/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sr-Latn-RS/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sr-Latn-RS/opds-Fedora_Core.xml | 2 +-
.../sr-Latn-RS/opds-Fedora_Documentation.xml | 2 +-
.../sr-Latn-RS/opds-Fedora_Draft_Documentation.xml | 2 +-
.../sr-Latn-RS/opds-Fedora_Security_Team.xml | 2 +-
public_html/sr-Latn-RS/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sr-RS/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sr-RS/opds-Fedora_Core.xml | 2 +-
public_html/sr-RS/opds-Fedora_Documentation.xml | 2 +-
.../sr-RS/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/sr-RS/opds-Fedora_Security_Team.xml | 2 +-
public_html/sr-RS/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sv-SE/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sv-SE/opds-Fedora_Core.xml | 2 +-
public_html/sv-SE/opds-Fedora_Documentation.xml | 2 +-
.../sv-SE/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/sv-SE/opds-Fedora_Security_Team.xml | 2 +-
public_html/sv-SE/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ta-IN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ta-IN/opds-Fedora_Core.xml | 2 +-
public_html/ta-IN/opds-Fedora_Documentation.xml | 2 +-
.../ta-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ta-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/ta-IN/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/te-IN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/te-IN/opds-Fedora_Core.xml | 2 +-
public_html/te-IN/opds-Fedora_Documentation.xml | 2 +-
.../te-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/te-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/te-IN/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/uk-UA/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/uk-UA/opds-Fedora_Core.xml | 2 +-
public_html/uk-UA/opds-Fedora_Documentation.xml | 2 +-
.../uk-UA/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/uk-UA/opds-Fedora_Security_Team.xml | 2 +-
public_html/uk-UA/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/zh-CN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/zh-CN/opds-Fedora_Core.xml | 2 +-
public_html/zh-CN/opds-Fedora_Documentation.xml | 2 +-
.../zh-CN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/zh-CN/opds-Fedora_Security_Team.xml | 2 +-
public_html/zh-CN/opds.xml | 16 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/zh-TW/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/zh-TW/opds-Fedora_Core.xml | 2 +-
public_html/zh-TW/opds-Fedora_Documentation.xml | 2 +-
.../zh-TW/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/zh-TW/opds-Fedora_Security_Team.xml | 2 +-
public_html/zh-TW/opds.xml | 16 +-
497 files changed, 1824 insertions(+), 1788 deletions(-)
---
diff --git a/fedoradocs.db b/fedoradocs.db
index 21b5c6e..0fb376d 100644
Binary files a/fedoradocs.db and b/fedoradocs.db differ
diff --git a/public_html/Sitemap b/public_html/Sitemap
index 75adb19..ab28d2b 100644
--- a/public_html/Sitemap
+++ b/public_html/Sitemap
@@ -1952,25 +1952,25 @@
</url>
<url>
<loc>http://docs.fedoraproject.org/en-US/Fedora/20/epub/Installation_Guide/Fedor…</loc>
- <lastmod>2013-12-18</lastmod>
+ <lastmod>2013-12-22</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>http://docs.fedoraproject.org/en-US/Fedora/20/html/Installation_Guide/index…</loc>
- <lastmod>2013-12-18</lastmod>
+ <lastmod>2013-12-22</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>http://docs.fedoraproject.org/en-US/Fedora/20/html-single/Installation_Guid…</loc>
- <lastmod>2013-12-18</lastmod>
+ <lastmod>2013-12-22</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>http://docs.fedoraproject.org/en-US/Fedora/20/pdf/Installation_Guide/Fedora…</loc>
- <lastmod>2013-12-18</lastmod>
+ <lastmod>2013-12-22</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
diff --git a/public_html/as-IN/opds-Community_Services_Infrastructure.xml b/public_html/as-IN/opds-Community_Services_Infrastructure.xml
index c6138da..53eced9 100644
--- a/public_html/as-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/as-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Community_Services_Infrastructure.…</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:50</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora.xml b/public_html/as-IN/opds-Fedora.xml
index 21587cd..cbed775 100644
--- a/public_html/as-IN/opds-Fedora.xml
+++ b/public_html/as-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:51</updated>
<!--author>
<name></name>
<uri></uri>
@@ -37,7 +37,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2013-12-18</updated>
+ <updated>2013-12-22</updated>
<dc:language>as-IN</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
index ce9bd7e..f02d77e 100644
--- a/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Contributor_Documentation.x…</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora_Core.xml b/public_html/as-IN/opds-Fedora_Core.xml
index 215a4a2..b456362 100644
--- a/public_html/as-IN/opds-Fedora_Core.xml
+++ b/public_html/as-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora_Documentation.xml b/public_html/as-IN/opds-Fedora_Documentation.xml
index b851b8e..3876581 100644
--- a/public_html/as-IN/opds-Fedora_Documentation.xml
+++ b/public_html/as-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora_Draft_Documentation.xml b/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
index ca337b6..ad1a81f 100644
--- a/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora_Security_Team.xml b/public_html/as-IN/opds-Fedora_Security_Team.xml
index df4f7cc..9e8e8ff 100644
--- a/public_html/as-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/as-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds.xml b/public_html/as-IN/opds.xml
index c241e42..3cff27e 100644
--- a/public_html/as-IN/opds.xml
+++ b/public_html/as-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/as-IN/opds.xml</id>
<title>Product List</title>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/as-IN/Community_Services_Infrastructure/opds-…</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:50</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora/opds-Fedora.xml</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:51</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Contributor_Documentation/opds-F…</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:51</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Documentation/opds-Fedora_Docume…</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Draft_Documentation/opds-Fedora_…</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Security_Team/opds-Fedora_Securi…</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/bg-BG/opds-Community_Services_Infrastructure.xml b/public_html/bg-BG/opds-Community_Services_Infrastructure.xml
index 1d2e3c4..2d6e136 100644
--- a/public_html/bg-BG/opds-Community_Services_Infrastructure.xml
+++ b/public_html/bg-BG/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Community_Services_Infrastructure.…</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora.xml b/public_html/bg-BG/opds-Fedora.xml
index a6a4d14..1ac7c01 100644
--- a/public_html/bg-BG/opds-Fedora.xml
+++ b/public_html/bg-BG/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<!--author>
<name></name>
<uri></uri>
@@ -37,7 +37,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2013-12-18</updated>
+ <updated>2013-12-22</updated>
<dc:language>bg-BG</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml b/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
index 86ffa8f..efddf97 100644
--- a/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Contributor_Documentation.x…</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Core.xml b/public_html/bg-BG/opds-Fedora_Core.xml
index 909cf9b..97fc1aa 100644
--- a/public_html/bg-BG/opds-Fedora_Core.xml
+++ b/public_html/bg-BG/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Documentation.xml b/public_html/bg-BG/opds-Fedora_Documentation.xml
index f30fc5c..518e9db 100644
--- a/public_html/bg-BG/opds-Fedora_Documentation.xml
+++ b/public_html/bg-BG/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml b/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
index 85d01a2..d6454c9 100644
--- a/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Security_Team.xml b/public_html/bg-BG/opds-Fedora_Security_Team.xml
index 80306f6..27403d9 100644
--- a/public_html/bg-BG/opds-Fedora_Security_Team.xml
+++ b/public_html/bg-BG/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds.xml b/public_html/bg-BG/opds.xml
index 311dedb..c8ad0e5 100644
--- a/public_html/bg-BG/opds.xml
+++ b/public_html/bg-BG/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/bg-BG/opds.xml</id>
<title>Product List</title>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/bg-BG/Community_Services_Infrastructure/opds-…</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora/opds-Fedora.xml</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Contributor_Documentation/opds-F…</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Documentation/opds-Fedora_Docume…</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Draft_Documentation/opds-Fedora_…</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Security_Team/opds-Fedora_Securi…</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/bn-IN/opds-Community_Services_Infrastructure.xml b/public_html/bn-IN/opds-Community_Services_Infrastructure.xml
index aa116d5..c8a4c57 100644
--- a/public_html/bn-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/bn-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Community_Services_Infrastructure.…</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora.xml b/public_html/bn-IN/opds-Fedora.xml
index a92c1f7..b1cc956 100644
--- a/public_html/bn-IN/opds-Fedora.xml
+++ b/public_html/bn-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<!--author>
<name></name>
<uri></uri>
@@ -37,7 +37,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2013-12-18</updated>
+ <updated>2013-12-22</updated>
<dc:language>bn-IN</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
index 083a2c6..dc1e388 100644
--- a/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Contributor_Documentation.x…</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora_Core.xml b/public_html/bn-IN/opds-Fedora_Core.xml
index 61b45d9..27683f3 100644
--- a/public_html/bn-IN/opds-Fedora_Core.xml
+++ b/public_html/bn-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora_Documentation.xml b/public_html/bn-IN/opds-Fedora_Documentation.xml
index 63ad81d..e7d685c 100644
--- a/public_html/bn-IN/opds-Fedora_Documentation.xml
+++ b/public_html/bn-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml b/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
index 9fbdd8b..f2a3517 100644
--- a/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora_Security_Team.xml b/public_html/bn-IN/opds-Fedora_Security_Team.xml
index 6de5504..7473a26 100644
--- a/public_html/bn-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/bn-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds.xml b/public_html/bn-IN/opds.xml
index a1454c4..bdce3f3 100644
--- a/public_html/bn-IN/opds.xml
+++ b/public_html/bn-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/bn-IN/opds.xml</id>
<title>Product List</title>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/bn-IN/Community_Services_Infrastructure/opds-…</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora/opds-Fedora.xml</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Contributor_Documentation/opds-F…</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Documentation/opds-Fedora_Docume…</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Draft_Documentation/opds-Fedora_…</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Security_Team/opds-Fedora_Securi…</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/bs-BA/opds-Community_Services_Infrastructure.xml b/public_html/bs-BA/opds-Community_Services_Infrastructure.xml
index 282c7fd..3405d34 100644
--- a/public_html/bs-BA/opds-Community_Services_Infrastructure.xml
+++ b/public_html/bs-BA/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Community_Services_Infrastructure.…</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora.xml b/public_html/bs-BA/opds-Fedora.xml
index 15a2097..909a88e 100644
--- a/public_html/bs-BA/opds-Fedora.xml
+++ b/public_html/bs-BA/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
@@ -37,7 +37,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2013-12-18</updated>
+ <updated>2013-12-22</updated>
<dc:language>bs-BA</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml b/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
index 45fbefb..cfb8585 100644
--- a/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Contributor_Documentation.x…</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora_Core.xml b/public_html/bs-BA/opds-Fedora_Core.xml
index 03f3c25..bbaa3a2 100644
--- a/public_html/bs-BA/opds-Fedora_Core.xml
+++ b/public_html/bs-BA/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora_Documentation.xml b/public_html/bs-BA/opds-Fedora_Documentation.xml
index 23dd7a5..bc87932 100644
--- a/public_html/bs-BA/opds-Fedora_Documentation.xml
+++ b/public_html/bs-BA/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml b/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
index c25b0e5..7ad68d2 100644
--- a/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora_Security_Team.xml b/public_html/bs-BA/opds-Fedora_Security_Team.xml
index 7add6a2..c6f7c48 100644
--- a/public_html/bs-BA/opds-Fedora_Security_Team.xml
+++ b/public_html/bs-BA/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds.xml b/public_html/bs-BA/opds.xml
index 3856da4..bfcd974 100644
--- a/public_html/bs-BA/opds.xml
+++ b/public_html/bs-BA/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/bs-BA/opds.xml</id>
<title>Product List</title>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/bs-BA/Community_Services_Infrastructure/opds-…</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:52</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora/opds-Fedora.xml</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Contributor_Documentation/opds-F…</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Documentation/opds-Fedora_Docume…</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Draft_Documentation/opds-Fedora_…</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Security_Team/opds-Fedora_Securi…</id>
- <updated>2013-12-20T21:09:55</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ca-ES/opds-Community_Services_Infrastructure.xml b/public_html/ca-ES/opds-Community_Services_Infrastructure.xml
index 6646c90..653eee4 100644
--- a/public_html/ca-ES/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ca-ES/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Community_Services_Infrastructure.…</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora.xml b/public_html/ca-ES/opds-Fedora.xml
index 71736d7..5e31c9c 100644
--- a/public_html/ca-ES/opds-Fedora.xml
+++ b/public_html/ca-ES/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
@@ -37,7 +37,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2013-12-18</updated>
+ <updated>2013-12-22</updated>
<dc:language>ca-ES</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml b/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
index 4de3d85..f857a0d 100644
--- a/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Contributor_Documentation.x…</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora_Core.xml b/public_html/ca-ES/opds-Fedora_Core.xml
index e0157af..42b5926 100644
--- a/public_html/ca-ES/opds-Fedora_Core.xml
+++ b/public_html/ca-ES/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora_Documentation.xml b/public_html/ca-ES/opds-Fedora_Documentation.xml
index c7c239c..7e28e42 100644
--- a/public_html/ca-ES/opds-Fedora_Documentation.xml
+++ b/public_html/ca-ES/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml b/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
index 93f2165..33d07ba 100644
--- a/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora_Security_Team.xml b/public_html/ca-ES/opds-Fedora_Security_Team.xml
index 747795f..e1529b6 100644
--- a/public_html/ca-ES/opds-Fedora_Security_Team.xml
+++ b/public_html/ca-ES/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds.xml b/public_html/ca-ES/opds.xml
index add4fc6..5db6416 100644
--- a/public_html/ca-ES/opds.xml
+++ b/public_html/ca-ES/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ca-ES/opds.xml</id>
<title>Product List</title>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ca-ES/Community_Services_Infrastructure/opds-…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora/opds-Fedora.xml</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Contributor_Documentation/opds-F…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Documentation/opds-Fedora_Docume…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Draft_Documentation/opds-Fedora_…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Security_Team/opds-Fedora_Securi…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/cs-CZ/opds-Community_Services_Infrastructure.xml b/public_html/cs-CZ/opds-Community_Services_Infrastructure.xml
index 5ec823a..8f63923 100644
--- a/public_html/cs-CZ/opds-Community_Services_Infrastructure.xml
+++ b/public_html/cs-CZ/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Community_Services_Infrastructure.…</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora.xml b/public_html/cs-CZ/opds-Fedora.xml
index 2154efa..91eaddb 100644
--- a/public_html/cs-CZ/opds-Fedora.xml
+++ b/public_html/cs-CZ/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
@@ -37,7 +37,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2013-12-18</updated>
+ <updated>2013-12-22</updated>
<dc:language>cs-CZ</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml b/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
index 668ac4b..299c444 100644
--- a/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Contributor_Documentation.x…</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora_Core.xml b/public_html/cs-CZ/opds-Fedora_Core.xml
index 4fb003a..2812f9c 100644
--- a/public_html/cs-CZ/opds-Fedora_Core.xml
+++ b/public_html/cs-CZ/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora_Documentation.xml b/public_html/cs-CZ/opds-Fedora_Documentation.xml
index 710db0f..1b6cdc1 100644
--- a/public_html/cs-CZ/opds-Fedora_Documentation.xml
+++ b/public_html/cs-CZ/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml b/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
index 2af2a7b..16670b8 100644
--- a/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora_Security_Team.xml b/public_html/cs-CZ/opds-Fedora_Security_Team.xml
index 04d58a5..ca3e5b3 100644
--- a/public_html/cs-CZ/opds-Fedora_Security_Team.xml
+++ b/public_html/cs-CZ/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds.xml b/public_html/cs-CZ/opds.xml
index 2e8af0a..ad5227e 100644
--- a/public_html/cs-CZ/opds.xml
+++ b/public_html/cs-CZ/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/cs-CZ/opds.xml</id>
<title>Product List</title>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/cs-CZ/Community_Services_Infrastructure/opds-…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora/opds-Fedora.xml</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Contributor_Documentation/opds-F…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Documentation/opds-Fedora_Docume…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Draft_Documentation/opds-Fedora_…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Security_Team/opds-Fedora_Securi…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/da-DK/opds-Community_Services_Infrastructure.xml b/public_html/da-DK/opds-Community_Services_Infrastructure.xml
index 841138b..a47adb2 100644
--- a/public_html/da-DK/opds-Community_Services_Infrastructure.xml
+++ b/public_html/da-DK/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Community_Services_Infrastructure.…</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora.xml b/public_html/da-DK/opds-Fedora.xml
index 5fc0231..a4053a5 100644
--- a/public_html/da-DK/opds-Fedora.xml
+++ b/public_html/da-DK/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
@@ -37,7 +37,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2013-12-18</updated>
+ <updated>2013-12-22</updated>
<dc:language>da-DK</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml b/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
index 366cfea..3265e4d 100644
--- a/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Contributor_Documentation.x…</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora_Core.xml b/public_html/da-DK/opds-Fedora_Core.xml
index 604effe..3c7c377 100644
--- a/public_html/da-DK/opds-Fedora_Core.xml
+++ b/public_html/da-DK/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora_Documentation.xml b/public_html/da-DK/opds-Fedora_Documentation.xml
index 069c110..3bd52d7 100644
--- a/public_html/da-DK/opds-Fedora_Documentation.xml
+++ b/public_html/da-DK/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora_Draft_Documentation.xml b/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
index 4e8eeac..79c5c23 100644
--- a/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora_Security_Team.xml b/public_html/da-DK/opds-Fedora_Security_Team.xml
index 76c27d5..f8d4784 100644
--- a/public_html/da-DK/opds-Fedora_Security_Team.xml
+++ b/public_html/da-DK/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds.xml b/public_html/da-DK/opds.xml
index d190df3..1b5898f 100644
--- a/public_html/da-DK/opds.xml
+++ b/public_html/da-DK/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/da-DK/opds.xml</id>
<title>Product List</title>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/da-DK/Community_Services_Infrastructure/opds-…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora/opds-Fedora.xml</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Contributor_Documentation/opds-F…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Documentation/opds-Fedora_Docume…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Draft_Documentation/opds-Fedora_…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Security_Team/opds-Fedora_Securi…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/de-DE/opds-Community_Services_Infrastructure.xml b/public_html/de-DE/opds-Community_Services_Infrastructure.xml
index a92a1a6..5c9e832 100644
--- a/public_html/de-DE/opds-Community_Services_Infrastructure.xml
+++ b/public_html/de-DE/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Community_Services_Infrastructure.…</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora.xml b/public_html/de-DE/opds-Fedora.xml
index 97000b3..52cc73c 100644
--- a/public_html/de-DE/opds-Fedora.xml
+++ b/public_html/de-DE/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<!--author>
<name></name>
<uri></uri>
@@ -37,7 +37,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2013-12-18</updated>
+ <updated>2013-12-22</updated>
<dc:language>de-DE</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml b/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
index e40aad6..284e11b 100644
--- a/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Contributor_Documentation.x…</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora_Core.xml b/public_html/de-DE/opds-Fedora_Core.xml
index b5e5033..3e8ad7f 100644
--- a/public_html/de-DE/opds-Fedora_Core.xml
+++ b/public_html/de-DE/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora_Documentation.xml b/public_html/de-DE/opds-Fedora_Documentation.xml
index 658fff8..0dd7483 100644
--- a/public_html/de-DE/opds-Fedora_Documentation.xml
+++ b/public_html/de-DE/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora_Draft_Documentation.xml b/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
index 5050f07..0ecec4d 100644
--- a/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora_Security_Team.xml b/public_html/de-DE/opds-Fedora_Security_Team.xml
index 53b84b1..079bda5 100644
--- a/public_html/de-DE/opds-Fedora_Security_Team.xml
+++ b/public_html/de-DE/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds.xml b/public_html/de-DE/opds.xml
index 367eddd..cc37565 100644
--- a/public_html/de-DE/opds.xml
+++ b/public_html/de-DE/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/de-DE/opds.xml</id>
<title>Product List</title>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/de-DE/Community_Services_Infrastructure/opds-…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:53</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora/opds-Fedora.xml</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Contributor_Documentation/opds-F…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Documentation/opds-Fedora_Docume…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Draft_Documentation/opds-Fedora_…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Security_Team/opds-Fedora_Securi…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/el-GR/opds-Community_Services_Infrastructure.xml b/public_html/el-GR/opds-Community_Services_Infrastructure.xml
index 18afc43..c4ebeab 100644
--- a/public_html/el-GR/opds-Community_Services_Infrastructure.xml
+++ b/public_html/el-GR/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Community_Services_Infrastructure.…</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora.xml b/public_html/el-GR/opds-Fedora.xml
index b905dbd..fa27fb5 100644
--- a/public_html/el-GR/opds-Fedora.xml
+++ b/public_html/el-GR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<!--author>
<name></name>
<uri></uri>
@@ -37,7 +37,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2013-12-18</updated>
+ <updated>2013-12-22</updated>
<dc:language>el-GR</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml b/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
index 6903f10..97e5c56 100644
--- a/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Contributor_Documentation.x…</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora_Core.xml b/public_html/el-GR/opds-Fedora_Core.xml
index de85da0..bca6db7 100644
--- a/public_html/el-GR/opds-Fedora_Core.xml
+++ b/public_html/el-GR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora_Documentation.xml b/public_html/el-GR/opds-Fedora_Documentation.xml
index 8d4ca51..1e58ed2 100644
--- a/public_html/el-GR/opds-Fedora_Documentation.xml
+++ b/public_html/el-GR/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora_Draft_Documentation.xml b/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
index dd1494c..631bf27 100644
--- a/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora_Security_Team.xml b/public_html/el-GR/opds-Fedora_Security_Team.xml
index 440c672..7e8c844 100644
--- a/public_html/el-GR/opds-Fedora_Security_Team.xml
+++ b/public_html/el-GR/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds.xml b/public_html/el-GR/opds.xml
index 101b367..1136cea 100644
--- a/public_html/el-GR/opds.xml
+++ b/public_html/el-GR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/el-GR/opds.xml</id>
<title>Product List</title>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/el-GR/Community_Services_Infrastructure/opds-…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora/opds-Fedora.xml</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Contributor_Documentation/opds-F…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Documentation/opds-Fedora_Docume…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Draft_Documentation/opds-Fedora_…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Security_Team/opds-Fedora_Securi…</id>
- <updated>2013-12-20T21:09:56</updated>
+ <updated>2013-12-22T19:27:54</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/en-US/Fedora/20/epub/Installation_Guide/Fedora-20-Installation_Guide-en-US.epub b/public_html/en-US/Fedora/20/epub/Installation_Guide/Fedora-20-Installation_Guide-en-US.epub
index 7cdf3d4..7b6f1c1 100644
Binary files a/public_html/en-US/Fedora/20/epub/Installation_Guide/Fedora-20-Installation_Guide-en-US.epub and b/public_html/en-US/Fedora/20/epub/Installation_Guide/Fedora-20-Installation_Guide-en-US.epub differ
diff --git a/public_html/en-US/Fedora/20/html-single/Installation_Guide/images/diskpartitioning/btrfs.png b/public_html/en-US/Fedora/20/html-single/Installation_Guide/images/diskpartitioning/btrfs.png
index d4861d7..85a1384 100644
Binary files a/public_html/en-US/Fedora/20/html-single/Installation_Guide/images/diskpartitioning/btrfs.png and b/public_html/en-US/Fedora/20/html-single/Installation_Guide/images/diskpartitioning/btrfs.png differ
diff --git a/public_html/en-US/Fedora/20/html-single/Installation_Guide/images/diskpartitioning/confirm.png b/public_html/en-US/Fedora/20/html-single/Installation_Guide/images/diskpartitioning/confirm.png
new file mode 100644
index 0000000..34b29d8
Binary files /dev/null and b/public_html/en-US/Fedora/20/html-single/Installation_Guide/images/diskpartitioning/confirm.png differ
diff --git a/public_html/en-US/Fedora/20/html-single/Installation_Guide/images/diskpartitioning/software-raid.png b/public_html/en-US/Fedora/20/html-single/Installation_Guide/images/diskpartitioning/software-raid.png
index 7110aaa..6f4b8db 100644
Binary files a/public_html/en-US/Fedora/20/html-single/Installation_Guide/images/diskpartitioning/software-raid.png and b/public_html/en-US/Fedora/20/html-single/Installation_Guide/images/diskpartitioning/software-raid.png differ
diff --git a/public_html/en-US/Fedora/20/html-single/Installation_Guide/index.html b/public_html/en-US/Fedora/20/html-single/Installation_Guide/index.html
index 142cc91..33b7756 100644
--- a/public_html/en-US/Fedora/20/html-single/Installation_Guide/index.html
+++ b/public_html/en-US/Fedora/20/html-single/Installation_Guide/index.html
@@ -6,10 +6,10 @@
addID('Fedora.20.books');
addID('Fedora.20.Installation_Guide');
- </script></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><div xml:lang="en-US" class="book" id="idm225434763792" lang="en-US"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><span class="productname">Fedora</span> <span class="productnumber">20</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="idm225434763792" class="title">Installation Guide</h1
></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h2 class="subtitle">Installing Fedora 20 on AMD64 and Intel 64 architectures</h2></div><p class="edition">Edition 1</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
+ </script></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><div xml:lang="en-US" class="book" id="idm219169745504" lang="en-US"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><span class="productname">Fedora</span> <span class="productnumber">20</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="idm219169745504" class="title">Installation Guide</h1
></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h2 class="subtitle">Installing Fedora 20 on AMD64 and Intel 64 architectures</h2></div><p class="edition">Edition 1</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
<span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> Fedora Documentation Team</object></span>
- </h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="en-US" class="authorgroup" lang="en-US"><div class="author"><h3 class="author"><span class="firstname">Fedora</span> <span class="surname">Documentation Project</span></h3></div></div></div><hr /><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="idm225448604608" class="legalnotice"><h1 class="legalnotice">Legal Notice</h1><div class="para">
+ </h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="en-US" class="authorgroup" lang="en-US"><div class="author"><h3 class="author"><span class="firstname">Fedora</span> <span class="surname">Documentation Project</span></h3></div></div></div><hr /><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="idm219136060928" class="legalnotice"><h1 class="legalnotice">Legal Notice</h1><div class="para">
Copyright <span class="trademark"></span>© 2013 Red Hat, Inc. and others.
</div><div class="para">
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at <a href="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</a>. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
@@ -31,11 +31,11 @@
All other trademarks are the property of their respective owners.
</div></div></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div class="abstract"><h6>Abstract</h6><div class="para">
Provides documentation for the installation process.
- </div></div></div></div><hr /></div><div class="toc"><dl class="toc"><dt><span class="preface"><a href="#Installation-Guide-Preface">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="#idm225502180544">1. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="#idm225460099600">1.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="#idm225447066752">1.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="#idm225451942256">1.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="section"><a href="#idm225425781152">2. We Need Feedback!</a></span></dt><dt><span class="section"><a href="#idm225439471072">3. Acknowledgments</a></span></dt></dl></dd><dt><span class="preface"><a href="#ch-introduction">Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-background">1. Background</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-about-fedora">1.1. About F
edora</a></span></dt><dt><span class="section"><a href="#sn-additional-help">1.2. Getting Additional Help</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-about-document">2. About This Document</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-goals">2.1. Goals</a></span></dt><dt><span class="section"><a href="#sn-audience">2.2. Audience</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-experts-quickstart">1. Quick Start for Experts</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-expert-overview">1.1. Overview</a></span></dt><dt><span class="section"><a href="#sn-expert-download">1.2. Download Files</a></span></dt><dt><span class="section"><a href="#sn-expert-prepare">1.3. Prepare for Installation</a></span></dt><dt><span class="section"><a href="#sn-expert-install">1.4. Install Fedora</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-new-users">2. Obtaining Fedora</a></span></dt><dd><dl><dt><span
class="section"><a href="#sect-Obtaining_Fedora-Downloading_Fedora">2.1. Downloading Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-howto-download">2.1.1. How Do I Download Installation Files?</a></span></dt><dt><span class="section"><a href="#sn-which-arch">2.1.2. Which Architecture Is My Computer?</a></span></dt><dt><span class="section"><a href="#sn-which-files">2.1.3. Which Files Do I Download?</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Obtaining_Fedora-Obtaining_Fedora_on_CD_or_DVD">2.2. Obtaining Fedora on CD or DVD</a></span></dt></dl></dd><dt><span class="chapter"><a href="#sn-making-media">3. Making Media</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-making-disc-media">3.1. Making an installation DVD</a></span></dt><dt><span class="section"><a href="#Making_USB_Media">3.2. Preparing a USB flash drive as an installation source</a></span></dt><dd><dl><dt><span class="section"><a href="#Making_USB_Media-Wind
ows">3.2.1. Making Fedora USB Media on a Windows Operating System</a></span></dt><dt><span class="section"><a href="#Making_USB_Media-UNIX_Linux">3.2.2. Making Fedora USB Media in UNIX, Linux, and Similar Operating Systems</a></span></dt></dl></dd><dt><span class="section"><a href="#Making_Minimal_Boot_Media">3.3. Making Minimal Boot Media</a></span></dt></dl></dd><dt><span class="part"><a href="#pt-install-info-x86">I. Installation and Booting</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ch-steps-x86">4. Planning for Installation on the x86 Architecture</a></span></dt><dd><dl><dt><span class="section"><a href="#idm225426577696">4.1. Upgrade or Install?</a></span></dt><dt><span class="section"><a href="#sn-Is_Your_Hardware_Compatible-x86">4.2. Is Your Hardware Compatible?</a></span></dt><dt><span class="section"><a href="#sn-partitioning-raid-x86">4.3. RAID and Other Disk Devices </a></span></dt><dd><dl><dt><span class="section"><a href="#sn-partitioning-raid-
hw-x86">4.3.1. Hardware RAID </a></span></dt><dt><span class="section"><a href="#sn-partitioning-raid-sw-x86">4.3.2. Software RAID </a></span></dt><dt><span class="section"><a href="#sn-partitioning-fw-usb-x86">4.3.3. FireWire and USB Disks </a></span></dt></dl></dd><dt><span class="section"><a href="#Disk_Space-x86">4.4. Do You Have Enough Disk Space?</a></span></dt><dt><span class="section"><a href="#s1-installmethod-x86">4.5. Selecting an Installation Method</a></span></dt><dt><span class="section"><a href="#idm225451342128">4.6. Choose a boot method</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Preparing-x86">5. Preparing for Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-steps-network-installs-x86">5.1. Preparing for a Network Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-steps-network-installs-x86-ftp-http">5.1.1. Preparing for FTP and HTTP installation</a></span></dt><dt><span class="section
"><a href="#s1-steps-network-installs-x86-nfs">5.1.2. Preparing for an NFS installation</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-steps-hd-installs-x86">5.2. Preparing for a Hard Drive Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-ent-table">6. System Specifications List</a></span></dt><dt><span class="chapter"><a href="#ch-Boot-x86">7. Booting the Installer</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-x86-starting">7.1. Starting the Installation Program</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x86-starting-booting">7.1.1. Booting the Installation Program on x86, AMD64, and Intel 64 Systems</a></span></dt><dt><span class="section"><a href="#sn-boot-menu-x86">7.1.2. The Boot Menu</a></span></dt><dt><span class="section"><a href="#s2-x86-starting-bootopts">7.1.3. Additional Boot Options</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-booting-from-pxe-x86">7.2. Booting fr
om the Network using PXE </a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Installation_Phase_2-x86">8. Configuring Installation Source</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-installationmethod-x86">8.1. Installation Method</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-begininstall-cd-inst-x86">8.1.1. Installing from DVD</a></span></dt><dt><span class="section"><a href="#s1-begininstall-hd-x86">8.1.2. Installing from a Hard Drive</a></span></dt><dt><span class="section"><a href="#s1-begininstall-nfs-x86">8.1.3. Installing via NFS</a></span></dt><dt><span class="section"><a href="#s1-begininstall-url-x86">8.1.4. Installing via FTP or HTTP</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-guimode-x86">9. Using the Fedora installer</a></span></dt><dd><dl><dt><span class="section"><a href="#idm225495428512">9.1. The Text Mode Installation Program User Interface</a></span></dt><dd><dl><dt><span class="s
ection"><a href="#idm225456935312">9.1.1. Using the Keyboard to Navigate</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-guimode-interface-x86">9.2. The Graphical Installation Program User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-adminoptions-screenshots">9.2.1. Screenshots during installation</a></span></dt><dt><span class="section"><a href="#sn-guimode-virtual-consoles-x86">9.2.2. A Note about Virtual Consoles</a></span></dt></dl></dd><dt><span class="section"><a href="#language-selection-x86">9.3. Language Selection</a></span></dt><dt><span class="section"><a href="#install-hub-x86">9.4. The Installation Summary Menu </a></span></dt><dt><span class="section"><a href="#s1-timezone-x86">9.5. Date and time</a></span></dt><dt><span class="section"><a href="#sn-keyboard-x86">9.6. Keyboard Configuration</a></span></dt><dt><span class="section"><a href="#language-support-x86">9.7. Language Support</a></span></dt><dt><span class="
section"><a href="#installation-source-x86">9.8. Installation Source</a></span></dt><dd><dl><dt><span class="section"><a href="#idm225473537472">9.8.1. Installing from Additional Repositories</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-Netconfig-x86">9.9. Network Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-Netconfig-x86-edit">9.9.1. Edit Network Connections</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-pkgselection-x86">9.10. Software Selection</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-mandatory-services-x86">9.10.1. Core Network Services </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-diskpartsetup-x86">9.11. Storage and partitioning</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Storage_Device_Selection_Screen-x86">9.11.1. Specialized and Networked Disks</a></span></dt><dt><span class="section"><a href="#s1-x86-bootloader">9.11.2. x86, AMD64, and Int
el 64 Boot Loader Installation</a></span></dt></dl></dd><dt><span class="section"><a href="#encrypt-x86">9.12. Encrypt Partitions </a></span></dt><dt><span class="section"><a href="#reclaim_space-x86">9.13. Reclaim disk space</a></span></dt><dt><span class="section"><a href="#s1-diskpartitioning-x86">9.14. Creating a Custom Partition Layout</a></span></dt><dd><dl><dt><span class="section"><a href="#Adding_Partitions-x86">9.14.1. Adding and Configuring Partitions</a></span></dt><dt><span class="section"><a href="#Create_Software_RAID-x86">9.14.2. Create Software RAID </a></span></dt><dt><span class="section"><a href="#Create_LVM-x86">9.14.3. Create LVM Logical Volume </a></span></dt><dt><span class="section"><a href="#Create_Btrfs-x86">9.14.4. Create a Btrfs subvolume</a></span></dt><dt><span class="section"><a href="#s2-diskpartrecommend-x86">9.14.5. Recommended Partitioning Scheme</a></span></dt></dl></dd><dt><span class="section"><a href="#Begin_installation-x86">9.15.
Begin installation</a></span></dt><dt><span class="section"><a href="#s1-progresshub-x86">9.16. The Configuration Menu and Progress Screen</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-account_configuration-x86">9.16.1. Set the Root Password</a></span></dt><dt><span class="section"><a href="#sn-firstboot-systemuser">9.16.2. User Creation</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-complete-x86">9.17. Installation Complete</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-gnome-initial-setup">9.17.1. GNOME Initial Setup</a></span></dt><dt><span class="section"><a href="#sect-other-initial-setup">9.17.2. Initial Setup in Other Desktop Environments</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-trouble-x86">10. Troubleshooting Installation on an Intel or AMD System</a></span></dt><dd><dl><dt><span class="section"><a href="#idm225499886064">10.1. You are unable to boot Fedora</a></span></dt><dd><dl><dt
><span class="section"><a href="#idm225419970064">10.1.1. Are You Unable to Boot With Your RAID Card?</a></span></dt><dt><span class="section"><a href="#idm225452658560">10.1.2. Is Your System Displaying Signal 11 Errors?</a></span></dt></dl></dd><dt><span class="section"><a href="#idm225471283760">10.2. Trouble Beginning the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#idm225464520544">10.2.1. Problems with Booting into the Graphical Installation</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-trouble-install-x86">10.3. Trouble During the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-trouble-nodevicefound-x86">10.3.1. <code class="computeroutput">No devices found to install Fedora </code> Error Message</a></span></dt><dt><span class="section"><a href="#s2-trouble-tracebacks-x86">10.3.2. Reporting traceback messages</a></span></dt><dt><span class="section"><a href="#s2-trouble-part-tables-x86">10.3.3. Tr
ouble with Partition Tables</a></span></dt><dt><span class="section"><a href="#s2-trouble-space-x86">10.3.4. Using Remaining Space</a></span></dt><dt><span class="section"><a href="#s2-trouble-completeparts-x86">10.3.5. Other Partitioning Problems</a></span></dt></dl></dd><dt><span class="section"><a href="#idm225448803200">10.4. Problems After Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-trouble-grub">10.4.1. Trouble With the Graphical GRUB Screen on an x86-based System?</a></span></dt><dt><span class="section"><a href="#s2-trouble-grub-command-line">10.4.2. Blocked by a GRUB command line after upgrading?</a></span></dt><dt><span class="section"><a href="#Trouble_After_Booting-GUI">10.4.3. Booting into a Graphical Environment</a></span></dt><dt><span class="section"><a href="#idm225460054624">10.4.4. Problems with the X Window System (GUI)</a></span></dt><dt><span class="section"><a href="#idm225503142160">10.4.5. Problems with the X Server Cra
shing and Non-Root Users</a></span></dt><dt><span class="section"><a href="#idm225461616880">10.4.6. Problems When You Try to Log In</a></span></dt><dt><span class="section"><a href="#s2-trouble-ram">10.4.7. Is Your RAM Not Being Recognized?</a></span></dt><dt><span class="section"><a href="#idm225465817296">10.4.8. Your Printer Does Not Work</a></span></dt><dt><span class="section"><a href="#idm225447278528">10.4.9. Apache HTTP Server or Sendmail stops responding during startup</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="#pt-Advanced_installation_options">II. Advanced installation options</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ap-admin-options">11. Boot Options</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-bootoptions-installer">11.1. Configuring the Installation System at the Boot Menu</a></span></dt><dt><span class="section"><a href="#sn-bootoptions-hardware">11.2. Enhancing Hardware Support</a></span></
dt><dd><dl><dt><span class="section"><a href="#sn-bootoptions-hwdetection">11.2.1. Overriding Automatic Hardware Detection</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-boot-options-maintenance">11.3. Using the Maintenance Boot Modes</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-boot-options-memtest">11.3.1. Loading the Memory (RAM) Testing Mode</a></span></dt><dt><span class="section"><a href="#sect-boot-options-mediacheck">11.3.2. Verifying Boot Media</a></span></dt><dt><span class="section"><a href="#sect-boot-options-rescue">11.3.3. Booting Your Computer in Rescue Mode</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ap-medialess-install">12. Installing Without Media</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-medialess-getting-files">12.1. Retrieving Boot Files</a></span></dt><dt><span class="section"><a href="#sn-medialess-editing-grub-conf">12.2. Editing the <span class="application"><strong
>GRUB</strong></span> Configuration</a></span></dt><dt><span class="section"><a href="#sn-medialess-booting">12.3. Booting to Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ap-install-server">13. Setting Up an Installation Server</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-install-cobbler">13.1. Setting Up <span class="package">cobbler</span></a></span></dt><dt><span class="section"><a href="#sn-cobbler-setup-distro">13.2. Setting Up the Distribution</a></span></dt><dt><span class="section"><a href="#sn-cobbler-mirror">13.3. Mirroring a Network Location</a></span></dt><dt><span class="section"><a href="#sn-cobbler-import">13.4. Importing the Distribution</a></span></dt><dt><span class="section"><a href="#sn-pxe-server-manual">13.5. Manually configure a PXE server</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-netboot-netserver">13.5.1. Setting up the Network Server</a></span></dt><dt><span class="section"><a href="#
s1-netboot-pxe-config">13.5.2. PXE Boot Configuration</a></span></dt><dt><span class="section"><a href="#idm225434414752">13.5.3. Starting the <code class="command">tftp</code> Server</a></span></dt><dt><span class="section"><a href="#s2-netboot-custom-msg">13.5.4. Adding a Custom Boot Message</a></span></dt><dt><span class="section"><a href="#netboot-performing">13.5.5. Performing the PXE Installation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#vncwhitepaperadded">14. Installing Through VNC</a></span></dt><dd><dl><dt><span class="section"><a href="#VNC_Whitepaper-vnc-viewer">14.1. VNC Viewer</a></span></dt><dt><span class="section"><a href="#VNC_Whitepaper-vnc-modes-in-anaconda">14.2. VNC Modes in Anaconda</a></span></dt><dd><dl><dt><span class="section"><a href="#VNC_Whitepaper-vnc-direct-mode">14.2.1. Direct Mode</a></span></dt><dt><span class="section"><a href="#VNC_Whitepaper-vnc-connect-mode">14.2.2. Connect Mode</a></span></dt></dl></dd><dt>
<span class="section"><a href="#VNC_Whitepaper-installation">14.3. Installation Using VNC</a></span></dt><dd><dl><dt><span class="section"><a href="#VNC_Whitepaper-installation-example">14.3.1. Installation Example</a></span></dt><dt><span class="section"><a href="#VNC_Whitepaper-kickstart-installation">14.3.2. Kickstart Considerations</a></span></dt><dt><span class="section"><a href="#VNC_Whitepaper-firewall-considerations">14.3.3. Firewall Considerations</a></span></dt></dl></dd><dt><span class="section"><a href="#VNC_Whitepaper-references">14.4. References</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-kickstart2">15. Kickstart Installations</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-kickstart2-whatis">15.1. What are Kickstart Installations?</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-howuse">15.2. How Do You Perform a Kickstart Installation?</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-file">15.
3. Creating the Kickstart File</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-options">15.4. Kickstart Options</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kickstart2-options-part-examples">15.4.1. Advanced Partitioning Example</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-packageselection">15.5. Package Selection</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-preinstallconfig">15.6. Pre-installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kickstart2-prescript-example">15.6.1. Example</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-postinstallconfig">15.7. Post-installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kickstart2-post-examples">15.7.1. Example</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-putkickstarthere">15.8. Making the Kickstart File Available</a></span></dt><dd><dl><
dt><span class="section"><a href="#s2-kickstart2-boot-media">15.8.1. Creating Kickstart Boot Media</a></span></dt><dt><span class="section"><a href="#s2-kickstart2-networkbased">15.8.2. Making the Kickstart File Available on the Network</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-install-tree">15.9. Making the Installation Tree Available</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-startinginstall">15.10. Starting a Kickstart Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-redhat-config-kickstart">16. <span class="application"><strong>Kickstart Configurator</strong></span></a></span></dt><dd><dl><dt><span class="section"><a href="#s1-redhat-config-kickstart-basic">16.1. Basic Configuration</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-install">16.2. Installation Method</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-bootloader">16.3. B
oot Loader Options</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-partitions">16.4. Partition Information</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-kickstart-create-part">16.4.1. Creating Partitions</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-redhat-config-kickstart-network">16.5. Network Configuration</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-auth">16.6. Authentication</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-firewall">16.7. Firewall Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-kickstart-firewall-selinux">16.7.1. SELinux Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-redhat-config-kickstart-xconfig">16.8. Display Configuration</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-pkgs">16.9. Package Selection</a></span><
/dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-prescript">16.10. Pre-Installation Script</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-postinstall">16.11. Post-Installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-kickstart-nochroot">16.11.1. Chroot Environment</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-kickstart-interpreter">16.11.2. Use an Interpreter</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-redhat-config-kickstart-savefile">16.12. Saving the File</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="#pt-After_installation">III. After installation</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ch-next-steps">17. Your Next Steps</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-system-updating">17.1. Updating Your System</a></span></dt><dt><span class="section"><a href="#sn-finishing-upgrade">17.2.
Finishing an Upgrade</a></span></dt><dt><span class="section"><a href="#sn-switching-to-gui-login">17.3. Switching to a Graphical Login</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-enabling-repos">17.3.1. Enabling Access to Software Repositories from the Command Line</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-news-subscriptions">17.4. Subscribing to Fedora Announcements and News</a></span></dt><dt><span class="section"><a href="#sn-web-help">17.5. Finding Documentation and Support</a></span></dt><dt><span class="section"><a href="#sn-community">17.6. Joining the Fedora Community</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-upgrade-x86">18. Upgrading Your Current System</a></span></dt><dd><dl><dt><span class="section"><a href="#idm225453497328">18.1. Determining Whether to Upgrade or Re-Install</a></span></dt><dt><span class="section"><a href="#idm225494883408">18.2. Upgrading Your System</a></span></dt></dl></dd><dt><
span class="chapter"><a href="#ch-x86-uninstall">19. Removing Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-x86-uninstall-single">19.1. Fedora is the only operating system on the computer</a></span></dt><dt><span class="section"><a href="#sn-x86-uninstall-dual">19.2. Your computer dual-boots Fedora and another operating system</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-x86-uninstall-dual-windows">19.2.1. Your computer dual-boots Fedora and a Microsoft Windows operating system</a></span></dt><dt><span class="section"><a href="#sn-x86-uninstall-dual-mac">19.2.2. Your computer dual-boots Fedora and Mac OS X</a></span></dt><dt><span class="section"><a href="#sn-x86-uninstall-dual-linux">19.2.3. Your computer dual-boots Fedora and a different Linux distribution</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-x86-uninstall-legacy">19.3. Replacing Fedora with MS-DOS or legacy versions of Microsoft Windows</a></span></dt></dl
></dd></dl></dd><dt><span class="part"><a href="#pt-Technical_appendixes">IV. Technical appendixes</a></span></dt><dd><dl><dt><span class="appendix"><a href="#ch-partitions-x86">A. An Introduction to Disk Partitions</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-partitions-concepts-x86">A.1. Hard Disk Basic Concepts</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-partitions-filesystem-x86">A.1.1. It is Not What You Write, it is How You Write It</a></span></dt><dt><span class="section"><a href="#s2-partitions-partitioning-x86">A.1.2. Partitions: Turning One Drive Into Many</a></span></dt><dt><span class="section"><a href="#s2-partitions-overview-extended-x86">A.1.3. Partitions within Partitions — An Overview of Extended Partitions</a></span></dt><dt><span class="section"><a href="#s2-partitions-make-room-x86">A.1.4. Making Room For Fedora</a></span></dt><dt><span class="section"><a href="#s2-partitions-part-name-x86">A.1.5. Partition Naming Sche
me</a></span></dt><dt><span class="section"><a href="#s2-partitions-other-os-x86">A.1.6. Disk Partitions and Other Operating Systems</a></span></dt><dt><span class="section"><a href="#s2-partitions-mt-points-x86">A.1.7. Disk Partitions and Mount Points</a></span></dt><dt><span class="section"><a href="#s2-partitions-how-many-x86">A.1.8. How Many Partitions?</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#ISCSI_disks">B. ISCSI disks</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-iSCSI_disks_in_anaconda">B.1. iSCSI disks in <span class="application"><strong>anaconda</strong></span></a></span></dt><dt><span class="section"><a href="#sn-iSCSI_disks_during_start_up">B.2. iSCSI disks during start up</a></span></dt></dl></dd><dt><span class="appendix"><a href="#Disk_Encryption_Guide">C. Disk Encryption</a></span></dt><dd><dl><dt><span class="section"><a href="#idm225502088720">C.1. What is block device encryption? </a></span></dt><dt><span cla
ss="section"><a href="#idm225462258400">C.2. Encrypting block devices using dm-crypt/LUKS </a></span></dt><dd><dl><dt><span class="section"><a href="#idm225429006656">C.2.1. Overview of LUKS </a></span></dt><dt><span class="section"><a href="#idm225434777936">C.2.2. How will I access the encrypted devices after installation? (System Startup) </a></span></dt><dt><span class="section"><a href="#idm225442125392">C.2.3. Choosing a Good Passphrase </a></span></dt></dl></dd><dt><span class="section"><a href="#idm225502718000">C.3. Creating Encrypted Block Devices in Anaconda </a></span></dt><dd><dl><dt><span class="section"><a href="#idm225434372512">C.3.1. What Kinds of Block Devices Can Be Encrypted? </a></span></dt><dt><span class="section"><a href="#Disk_Encryption_Guide-Saving_Passphrases">C.3.2. Saving Passphrases</a></span></dt><dt><span class="section"><a href="#Disk_Encryption_Guide-Creating_and_Saving_Backup_Passphrases">C.3.3. Creating and Saving Backup Passphrases</a><
/span></dt></dl></dd><dt><span class="section"><a href="#idm225441315072">C.4. Creating Encrypted Block Devices on the Installed System After Installation </a></span></dt><dd><dl><dt><span class="section"><a href="#idm225464181648">C.4.1. Create the block devices </a></span></dt><dt><span class="section"><a href="#randomize_device">C.4.2. Optional: Fill the device with random data</a></span></dt><dt><span class="section"><a href="#idm225466939104">C.4.3. Format the device as a dm-crypt/LUKS encrypted device </a></span></dt><dt><span class="section"><a href="#idm225417672528">C.4.4. Create a mapping to allow access to the device's decrypted contents </a></span></dt><dt><span class="section"><a href="#idm225415688192">C.4.5. Create filesystems on the mapped device, or continue to build complex storage structures using the mapped device </a></span></dt><dt><span class="section"><a href="#idm225434076144">C.4.6. Add the mapping information to <code class="filename">/etc/crypttab
</code></a></span></dt><dt><span class="section"><a href="#idm225452694560">C.4.7. Add an entry to <code class="filename">/etc/fstab</code></a></span></dt></dl></dd><dt><span class="section"><a href="#idm225461127056">C.5. Common Post-Installation Tasks </a></span></dt><dd><dl><dt><span class="section"><a href="#new_key">C.5.1. Set a randomly generated key as an additional way to access an encrypted block device</a></span></dt><dt><span class="section"><a href="#idm225464998144">C.5.2. Add a new passphrase to an existing device </a></span></dt><dt><span class="section"><a href="#idm225445283760">C.5.3. Remove a passphrase or key from a device </a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#sn-partitioning-lvm">D. Understanding LVM</a></span></dt><dt><span class="appendix"><a href="#anaconda_logging">E. Logging the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#anaconda_logging-logformats">E.1. Log files and formats </a></spa
n></dt><dd><dl><dt><span class="section"><a href="#anaconda_logging-logformats-files">E.1.1. Logging on the installed system </a></span></dt></dl></dd><dt><span class="section"><a href="#anaconda_logging-rsyslog">E.2. Remote logging with rsyslog </a></span></dt><dt><span class="section"><a href="#anaconda_logging-virtio">E.3. Remote logging via <code class="function">virtio</code> </a></span></dt><dd><dl><dt><span class="section"><a href="#anaconda_logging-virtio_new">E.3.1. <code class="function">virtio</code> logging with <code class="command">virt-install</code> </a></span></dt><dt><span class="section"><a href="#anaconda_logging-virtio_add">E.3.2. Adding a <code class="function">virtio</code> log channel with <code class="command">virsh edit</code> </a></span></dt><dt><span class="section"><a href="#anaconda_logging-virtio_listening">E.3.3. Listening for <code class="function">virtio</code> logs </a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href
="#ap-techref">F. Other Technical Documentation</a></span></dt></dl></dd><dt><span class="appendix"><a href="#ch-Contributors_and_production_methods">G. Contributors and production methods</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-Contributors">G.1. Contributors</a></span></dt><dt><span class="section"><a href="#sn-Production_methods">G.2. Production methods</a></span></dt></dl></dd><dt><span class="appendix"><a href="#appe-Publican-Revision_History">H. Revision History</a></span></dt><dt><span class="index"><a href="#idm225450782128">Index</a></span></dt></dl></div><div xml:lang="en-US" class="preface" id="Installation-Guide-Preface" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Preface</h1></div></div></div><div xml:lang="en-US" class="section" id="idm225502180544" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm225502180544">1. Document Conventions</h2></div></div></div><div
class="para">
+ </div></div></div></div><hr /></div><div class="toc"><dl class="toc"><dt><span class="preface"><a href="#Installation-Guide-Preface">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="#idm219171226752">1. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="#idm219181119200">1.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="#idm219143427776">1.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="#idm219166662592">1.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="section"><a href="#idm219173567568">2. We Need Feedback!</a></span></dt><dt><span class="section"><a href="#idm219206020704">3. Acknowledgments</a></span></dt></dl></dd><dt><span class="preface"><a href="#ch-introduction">Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-background">1. Background</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-about-fedora">1.1. About F
edora</a></span></dt><dt><span class="section"><a href="#sn-additional-help">1.2. Getting Additional Help</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-about-document">2. About This Document</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-goals">2.1. Goals</a></span></dt><dt><span class="section"><a href="#sn-audience">2.2. Audience</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-experts-quickstart">1. Quick Start for Experts</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-expert-overview">1.1. Overview</a></span></dt><dt><span class="section"><a href="#sn-expert-download">1.2. Download Files</a></span></dt><dt><span class="section"><a href="#sn-expert-prepare">1.3. Prepare for Installation</a></span></dt><dt><span class="section"><a href="#sn-expert-install">1.4. Install Fedora</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-new-users">2. Obtaining Fedora</a></span></dt><dd><dl><dt><span
class="section"><a href="#sect-Obtaining_Fedora-Downloading_Fedora">2.1. Downloading Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-howto-download">2.1.1. How Do I Download Installation Files?</a></span></dt><dt><span class="section"><a href="#sn-which-arch">2.1.2. Which Architecture Is My Computer?</a></span></dt><dt><span class="section"><a href="#sn-which-files">2.1.3. Which Files Do I Download?</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Obtaining_Fedora-Obtaining_Fedora_on_CD_or_DVD">2.2. Obtaining Fedora on CD or DVD</a></span></dt></dl></dd><dt><span class="chapter"><a href="#sn-making-media">3. Making Media</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-making-disc-media">3.1. Making an installation DVD</a></span></dt><dt><span class="section"><a href="#Making_USB_Media">3.2. Preparing a USB flash drive as an installation source</a></span></dt><dd><dl><dt><span class="section"><a href="#Making_USB_Media-Wind
ows">3.2.1. Making Fedora USB Media on a Windows Operating System</a></span></dt><dt><span class="section"><a href="#Making_USB_Media-UNIX_Linux">3.2.2. Making Fedora USB Media in UNIX, Linux, and Similar Operating Systems</a></span></dt></dl></dd><dt><span class="section"><a href="#Making_Minimal_Boot_Media">3.3. Making Minimal Boot Media</a></span></dt></dl></dd><dt><span class="part"><a href="#pt-install-info-x86">I. Installation and Booting</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ch-steps-x86">4. Planning for Installation on the x86 Architecture</a></span></dt><dd><dl><dt><span class="section"><a href="#idm219208671296">4.1. Upgrade or Install?</a></span></dt><dt><span class="section"><a href="#sn-Is_Your_Hardware_Compatible-x86">4.2. Is Your Hardware Compatible?</a></span></dt><dt><span class="section"><a href="#sn-partitioning-raid-x86">4.3. RAID and Other Disk Devices </a></span></dt><dd><dl><dt><span class="section"><a href="#sn-partitioning-raid-
hw-x86">4.3.1. Hardware RAID </a></span></dt><dt><span class="section"><a href="#sn-partitioning-raid-sw-x86">4.3.2. Software RAID </a></span></dt><dt><span class="section"><a href="#sn-partitioning-fw-usb-x86">4.3.3. FireWire and USB Disks </a></span></dt></dl></dd><dt><span class="section"><a href="#Disk_Space-x86">4.4. Do You Have Enough Disk Space?</a></span></dt><dt><span class="section"><a href="#s1-installmethod-x86">4.5. Selecting an Installation Method</a></span></dt><dt><span class="section"><a href="#idm219139957120">4.6. Choose a boot method</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Preparing-x86">5. Preparing for Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-steps-network-installs-x86">5.1. Preparing for a Network Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-steps-network-installs-x86-ftp-http">5.1.1. Preparing for FTP and HTTP installation</a></span></dt><dt><span class="section
"><a href="#s1-steps-network-installs-x86-nfs">5.1.2. Preparing for an NFS installation</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-steps-hd-installs-x86">5.2. Preparing for a Hard Drive Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-ent-table">6. System Specifications List</a></span></dt><dt><span class="chapter"><a href="#ch-Boot-x86">7. Booting the Installer</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-x86-starting">7.1. Starting the Installation Program</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x86-starting-booting">7.1.1. Booting the Installation Program on x86, AMD64, and Intel 64 Systems</a></span></dt><dt><span class="section"><a href="#sn-boot-menu-x86">7.1.2. The Boot Menu</a></span></dt><dt><span class="section"><a href="#s2-x86-starting-bootopts">7.1.3. Additional Boot Options</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-booting-from-pxe-x86">7.2. Booting fr
om the Network using PXE </a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Installation_Phase_2-x86">8. Configuring Installation Source</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-installationmethod-x86">8.1. Installation Method</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-begininstall-cd-inst-x86">8.1.1. Installing from DVD</a></span></dt><dt><span class="section"><a href="#s1-begininstall-hd-x86">8.1.2. Installing from a Hard Drive</a></span></dt><dt><span class="section"><a href="#s1-begininstall-nfs-x86">8.1.3. Installing via NFS</a></span></dt><dt><span class="section"><a href="#s1-begininstall-url-x86">8.1.4. Installing via FTP or HTTP</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-guimode-x86">9. Using the Fedora installer</a></span></dt><dd><dl><dt><span class="section"><a href="#idm219199222144">9.1. The Text Mode Installation Program User Interface</a></span></dt><dd><dl><dt><span class="s
ection"><a href="#idm219174347776">9.1.1. Using the Keyboard to Navigate</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-guimode-interface-x86">9.2. The Graphical Installation Program User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-adminoptions-screenshots">9.2.1. Screenshots during installation</a></span></dt><dt><span class="section"><a href="#sn-guimode-virtual-consoles-x86">9.2.2. A Note about Virtual Consoles</a></span></dt></dl></dd><dt><span class="section"><a href="#language-selection-x86">9.3. Language Selection</a></span></dt><dt><span class="section"><a href="#install-hub-x86">9.4. The Installation Summary Menu </a></span></dt><dt><span class="section"><a href="#s1-timezone-x86">9.5. Date and time</a></span></dt><dt><span class="section"><a href="#sn-keyboard-x86">9.6. Keyboard Configuration</a></span></dt><dt><span class="section"><a href="#language-support-x86">9.7. Language Support</a></span></dt><dt><span class="
section"><a href="#installation-source-x86">9.8. Installation Source</a></span></dt><dd><dl><dt><span class="section"><a href="#idm219180754816">9.8.1. Installing from Additional Repositories</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-Netconfig-x86">9.9. Network Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-Netconfig-x86-edit">9.9.1. Edit Network Connections</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-pkgselection-x86">9.10. Software Selection</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-mandatory-services-x86">9.10.1. Core Network Services </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-diskpartsetup-x86">9.11. Storage and partitioning</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Storage_Device_Selection_Screen-x86">9.11.1. Specialized and Networked Disks</a></span></dt><dt><span class="section"><a href="#s1-x86-bootloader">9.11.2. x86, AMD64, and Int
el 64 Boot Loader Installation</a></span></dt></dl></dd><dt><span class="section"><a href="#encrypt-x86">9.12. Encrypt Partitions </a></span></dt><dt><span class="section"><a href="#reclaim_space-x86">9.13. Reclaim disk space</a></span></dt><dt><span class="section"><a href="#s1-diskpartitioning-x86">9.14. Creating a Custom Partition Layout</a></span></dt><dd><dl><dt><span class="section"><a href="#Adding_Partitions-x86">9.14.1. Adding and Configuring Partitions</a></span></dt><dt><span class="section"><a href="#Create_Software_RAID-x86">9.14.2. Create Software RAID </a></span></dt><dt><span class="section"><a href="#Create_LVM-x86">9.14.3. Create LVM Logical Volume </a></span></dt><dt><span class="section"><a href="#Create_Btrfs-x86">9.14.4. Create a Btrfs subvolume</a></span></dt><dt><span class="section"><a href="#s2-diskpartrecommend-x86">9.14.5. Recommended Partitioning Scheme</a></span></dt><dt><span class="section"><a href="#s1-diskpartitioning-confirm">9.14.6. Re
view and Confirm Custom Partition Layout</a></span></dt></dl></dd><dt><span class="section"><a href="#Begin_installation-x86">9.15. Begin installation</a></span></dt><dt><span class="section"><a href="#s1-progresshub-x86">9.16. The Configuration Menu and Progress Screen</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-account_configuration-x86">9.16.1. Set the Root Password</a></span></dt><dt><span class="section"><a href="#sn-firstboot-systemuser">9.16.2. User Creation</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-complete-x86">9.17. Installation Complete</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-gnome-initial-setup">9.17.1. GNOME Initial Setup</a></span></dt><dt><span class="section"><a href="#sect-other-initial-setup">9.17.2. Initial Setup in Other Desktop Environments</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-trouble-x86">10. Troubleshooting Installation on an Intel or AMD System</a></sp
an></dt><dd><dl><dt><span class="section"><a href="#idm219175807424">10.1. You are unable to boot Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="#idm219168676576">10.1.1. Are You Unable to Boot With Your RAID Card?</a></span></dt><dt><span class="section"><a href="#idm219174625744">10.1.2. Is Your System Displaying Signal 11 Errors?</a></span></dt></dl></dd><dt><span class="section"><a href="#idm219168475296">10.2. Trouble Beginning the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#idm219139851008">10.2.1. Problems with Booting into the Graphical Installation</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-trouble-install-x86">10.3. Trouble During the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-trouble-nodevicefound-x86">10.3.1. <code class="computeroutput">No devices found to install Fedora </code> Error Message</a></span></dt><dt><span class="section"><a href="#s2-trouble-tracebacks-
x86">10.3.2. Reporting traceback messages</a></span></dt><dt><span class="section"><a href="#s2-trouble-part-tables-x86">10.3.3. Trouble with Partition Tables</a></span></dt><dt><span class="section"><a href="#s2-trouble-space-x86">10.3.4. Using Remaining Space</a></span></dt><dt><span class="section"><a href="#s2-trouble-completeparts-x86">10.3.5. Other Partitioning Problems</a></span></dt></dl></dd><dt><span class="section"><a href="#idm219181583248">10.4. Problems After Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-trouble-grub">10.4.1. Trouble With the Graphical GRUB Screen on an x86-based System?</a></span></dt><dt><span class="section"><a href="#s2-trouble-grub-command-line">10.4.2. Blocked by a GRUB command line after upgrading?</a></span></dt><dt><span class="section"><a href="#Trouble_After_Booting-GUI">10.4.3. Booting into a Graphical Environment</a></span></dt><dt><span class="section"><a href="#idm219179265600">10.4.4. Problems with t
he X Window System (GUI)</a></span></dt><dt><span class="section"><a href="#idm219157531344">10.4.5. Problems with the X Server Crashing and Non-Root Users</a></span></dt><dt><span class="section"><a href="#idm219150647984">10.4.6. Problems When You Try to Log In</a></span></dt><dt><span class="section"><a href="#s2-trouble-ram">10.4.7. Is Your RAM Not Being Recognized?</a></span></dt><dt><span class="section"><a href="#idm219173233792">10.4.8. Your Printer Does Not Work</a></span></dt><dt><span class="section"><a href="#idm219114810544">10.4.9. Apache HTTP Server or Sendmail stops responding during startup</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="#pt-Advanced_installation_options">II. Advanced installation options</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ap-admin-options">11. Boot Options</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-bootoptions-installer">11.1. Configuring the Installation System at the
Boot Menu</a></span></dt><dt><span class="section"><a href="#sn-bootoptions-hardware">11.2. Enhancing Hardware Support</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-bootoptions-hwdetection">11.2.1. Overriding Automatic Hardware Detection</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-boot-options-maintenance">11.3. Using the Maintenance Boot Modes</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-boot-options-memtest">11.3.1. Loading the Memory (RAM) Testing Mode</a></span></dt><dt><span class="section"><a href="#sect-boot-options-mediacheck">11.3.2. Verifying Boot Media</a></span></dt><dt><span class="section"><a href="#sect-boot-options-rescue">11.3.3. Booting Your Computer in Rescue Mode</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ap-medialess-install">12. Installing Without Media</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-medialess-getting-files">12.1. Retrieving Boot Files</a>
</span></dt><dt><span class="section"><a href="#sn-medialess-editing-grub-conf">12.2. Editing the <span class="application"><strong>GRUB</strong></span> Configuration</a></span></dt><dt><span class="section"><a href="#sn-medialess-booting">12.3. Booting to Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ap-install-server">13. Setting Up an Installation Server</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-install-cobbler">13.1. Setting Up <span class="package">cobbler</span></a></span></dt><dt><span class="section"><a href="#sn-cobbler-setup-distro">13.2. Setting Up the Distribution</a></span></dt><dt><span class="section"><a href="#sn-cobbler-mirror">13.3. Mirroring a Network Location</a></span></dt><dt><span class="section"><a href="#sn-cobbler-import">13.4. Importing the Distribution</a></span></dt><dt><span class="section"><a href="#sn-pxe-server-manual">13.5. Manually configure a PXE server</a></span></dt><dd><dl><dt><span class=
"section"><a href="#s1-netboot-netserver">13.5.1. Setting up the Network Server</a></span></dt><dt><span class="section"><a href="#s1-netboot-pxe-config">13.5.2. PXE Boot Configuration</a></span></dt><dt><span class="section"><a href="#idm219163541472">13.5.3. Starting the <code class="command">tftp</code> Server</a></span></dt><dt><span class="section"><a href="#s2-netboot-custom-msg">13.5.4. Adding a Custom Boot Message</a></span></dt><dt><span class="section"><a href="#netboot-performing">13.5.5. Performing the PXE Installation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#vncwhitepaperadded">14. Installing Through VNC</a></span></dt><dd><dl><dt><span class="section"><a href="#VNC_Whitepaper-vnc-viewer">14.1. VNC Viewer</a></span></dt><dt><span class="section"><a href="#VNC_Whitepaper-vnc-modes-in-anaconda">14.2. VNC Modes in Anaconda</a></span></dt><dd><dl><dt><span class="section"><a href="#VNC_Whitepaper-vnc-direct-mode">14.2.1. Direct Mode</a>
</span></dt><dt><span class="section"><a href="#VNC_Whitepaper-vnc-connect-mode">14.2.2. Connect Mode</a></span></dt></dl></dd><dt><span class="section"><a href="#VNC_Whitepaper-installation">14.3. Installation Using VNC</a></span></dt><dd><dl><dt><span class="section"><a href="#VNC_Whitepaper-installation-example">14.3.1. Installation Example</a></span></dt><dt><span class="section"><a href="#VNC_Whitepaper-kickstart-installation">14.3.2. Kickstart Considerations</a></span></dt><dt><span class="section"><a href="#VNC_Whitepaper-firewall-considerations">14.3.3. Firewall Considerations</a></span></dt></dl></dd><dt><span class="section"><a href="#VNC_Whitepaper-references">14.4. References</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-kickstart2">15. Kickstart Installations</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-kickstart2-whatis">15.1. What are Kickstart Installations?</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-ho
wuse">15.2. How Do You Perform a Kickstart Installation?</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-file">15.3. Creating the Kickstart File</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-options">15.4. Kickstart Options</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kickstart2-options-part-examples">15.4.1. Advanced Partitioning Example</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-packageselection">15.5. Package Selection</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-preinstallconfig">15.6. Pre-installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kickstart2-prescript-example">15.6.1. Example</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-postinstallconfig">15.7. Post-installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kickstart2-post-examples">15.7.1. Example</a></span></dt></dl></dd><dt
><span class="section"><a href="#s1-kickstart2-putkickstarthere">15.8. Making the Kickstart File Available</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kickstart2-boot-media">15.8.1. Creating Kickstart Boot Media</a></span></dt><dt><span class="section"><a href="#s2-kickstart2-networkbased">15.8.2. Making the Kickstart File Available on the Network</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-install-tree">15.9. Making the Installation Tree Available</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-startinginstall">15.10. Starting a Kickstart Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-redhat-config-kickstart">16. <span class="application"><strong>Kickstart Configurator</strong></span></a></span></dt><dd><dl><dt><span class="section"><a href="#s1-redhat-config-kickstart-basic">16.1. Basic Configuration</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-i
nstall">16.2. Installation Method</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-bootloader">16.3. Boot Loader Options</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-partitions">16.4. Partition Information</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-kickstart-create-part">16.4.1. Creating Partitions</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-redhat-config-kickstart-network">16.5. Network Configuration</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-auth">16.6. Authentication</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-firewall">16.7. Firewall Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-kickstart-firewall-selinux">16.7.1. SELinux Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-redhat-config-kickstart-xconfig">16.8. Display Co
nfiguration</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-pkgs">16.9. Package Selection</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-prescript">16.10. Pre-Installation Script</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-postinstall">16.11. Post-Installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-kickstart-nochroot">16.11.1. Chroot Environment</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-kickstart-interpreter">16.11.2. Use an Interpreter</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-redhat-config-kickstart-savefile">16.12. Saving the File</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="#pt-After_installation">III. After installation</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ch-next-steps">17. Your Next Steps</a></span></dt><dd><dl><dt><span class="section"><a h
ref="#sn-system-updating">17.1. Updating Your System</a></span></dt><dt><span class="section"><a href="#sn-switching-to-gui-login">17.2. Switching to a Graphical Login</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-enabling-repos-disc">17.2.1. Using a Fedora Installation DVD as a Software Repository</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-news-subscriptions">17.3. Subscribing to Fedora Announcements and News</a></span></dt><dt><span class="section"><a href="#sn-web-help">17.4. Finding Documentation and Support</a></span></dt><dt><span class="section"><a href="#sn-community">17.5. Joining the Fedora Community</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-upgrade-x86">18. Upgrading Your Current System</a></span></dt><dd><dl><dt><span class="section"><a href="#idm219184024384">18.1. Determining Whether to Upgrade or Re-Install</a></span></dt><dt><span class="section"><a href="#idm219206137712">18.2. Upgrading Your System<
/a></span></dt><dt><span class="section"><a href="#idm219140741808">18.3. Troubleshooting and Cleanup</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-x86-uninstall">19. Removing Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-x86-uninstall-single">19.1. Fedora is the only operating system on the computer</a></span></dt><dt><span class="section"><a href="#sn-x86-uninstall-dual">19.2. Your computer dual-boots Fedora and another operating system</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-x86-uninstall-dual-windows">19.2.1. Your computer dual-boots Fedora and a Microsoft Windows operating system</a></span></dt><dt><span class="section"><a href="#sn-x86-uninstall-dual-mac">19.2.2. Your computer dual-boots Fedora and Mac OS X</a></span></dt><dt><span class="section"><a href="#sn-x86-uninstall-dual-linux">19.2.3. Your computer dual-boots Fedora and a different Linux distribution</a></span></dt></dl></dd><dt><span class="sectio
n"><a href="#sn-x86-uninstall-legacy">19.3. Replacing Fedora with MS-DOS or legacy versions of Microsoft Windows</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="#pt-Technical_appendixes">IV. Technical appendixes</a></span></dt><dd><dl><dt><span class="appendix"><a href="#ch-partitions-x86">A. An Introduction to Disk Partitions</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-partitions-concepts-x86">A.1. Hard Disk Basic Concepts</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-partitions-filesystem-x86">A.1.1. It is Not What You Write, it is How You Write It</a></span></dt><dt><span class="section"><a href="#s2-partitions-partitioning-x86">A.1.2. Partitions: Turning One Drive Into Many</a></span></dt><dt><span class="section"><a href="#s2-partitions-overview-extended-x86">A.1.3. Partitions within Partitions — An Overview of Extended Partitions</a></span></dt><dt><span class="section"><a href="#s2-partitions-make-room-x86">A.1.4.
Making Room For Fedora</a></span></dt><dt><span class="section"><a href="#s2-partitions-part-name-x86">A.1.5. Partition Naming Scheme</a></span></dt><dt><span class="section"><a href="#s2-partitions-other-os-x86">A.1.6. Disk Partitions and Other Operating Systems</a></span></dt><dt><span class="section"><a href="#s2-partitions-mt-points-x86">A.1.7. Disk Partitions and Mount Points</a></span></dt><dt><span class="section"><a href="#s2-partitions-how-many-x86">A.1.8. How Many Partitions?</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#ISCSI_disks">B. ISCSI disks</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-iSCSI_disks_in_anaconda">B.1. iSCSI disks in <span class="application"><strong>anaconda</strong></span></a></span></dt><dt><span class="section"><a href="#sn-iSCSI_disks_during_start_up">B.2. iSCSI disks during start up</a></span></dt></dl></dd><dt><span class="appendix"><a href="#Disk_Encryption_Guide">C. Disk Encryption</a></span><
/dt><dd><dl><dt><span class="section"><a href="#idm219176445440">C.1. What is block device encryption? </a></span></dt><dt><span class="section"><a href="#idm219206257264">C.2. Encrypting block devices using dm-crypt/LUKS </a></span></dt><dd><dl><dt><span class="section"><a href="#idm219134347392">C.2.1. Overview of LUKS </a></span></dt><dt><span class="section"><a href="#idm219129450128">C.2.2. How will I access the encrypted devices after installation? (System Startup) </a></span></dt><dt><span class="section"><a href="#idm219116056096">C.2.3. Choosing a Good Passphrase </a></span></dt></dl></dd><dt><span class="section"><a href="#idm219116105440">C.3. Creating Encrypted Block Devices in Anaconda </a></span></dt><dd><dl><dt><span class="section"><a href="#idm219208196016">C.3.1. What Kinds of Block Devices Can Be Encrypted? </a></span></dt><dt><span class="section"><a href="#Disk_Encryption_Guide-Saving_Passphrases">C.3.2. Saving Passphrases</a></span></dt><dt><span class=
"section"><a href="#Disk_Encryption_Guide-Creating_and_Saving_Backup_Passphrases">C.3.3. Creating and Saving Backup Passphrases</a></span></dt></dl></dd><dt><span class="section"><a href="#idm219148297488">C.4. Creating Encrypted Block Devices on the Installed System After Installation </a></span></dt><dd><dl><dt><span class="section"><a href="#idm219138025824">C.4.1. Create the block devices </a></span></dt><dt><span class="section"><a href="#randomize_device">C.4.2. Optional: Fill the device with random data</a></span></dt><dt><span class="section"><a href="#idm219179013536">C.4.3. Format the device as a dm-crypt/LUKS encrypted device </a></span></dt><dt><span class="section"><a href="#idm219207924288">C.4.4. Create a mapping to allow access to the device's decrypted contents </a></span></dt><dt><span class="section"><a href="#idm219174378624">C.4.5. Create filesystems on the mapped device, or continue to build complex storage structures using the mapped device </a></span>
</dt><dt><span class="section"><a href="#idm219169785200">C.4.6. Add the mapping information to <code class="filename">/etc/crypttab</code></a></span></dt><dt><span class="section"><a href="#idm219178747168">C.4.7. Add an entry to <code class="filename">/etc/fstab</code></a></span></dt></dl></dd><dt><span class="section"><a href="#idm219170566064">C.5. Common Post-Installation Tasks </a></span></dt><dd><dl><dt><span class="section"><a href="#new_key">C.5.1. Set a randomly generated key as an additional way to access an encrypted block device</a></span></dt><dt><span class="section"><a href="#idm219182245776">C.5.2. Add a new passphrase to an existing device </a></span></dt><dt><span class="section"><a href="#idm219153459472">C.5.3. Remove a passphrase or key from a device </a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#sn-partitioning-lvm">D. Understanding LVM</a></span></dt><dt><span class="appendix"><a href="#anaconda_logging">E. Logging the Instal
lation</a></span></dt><dd><dl><dt><span class="section"><a href="#anaconda_logging-logformats">E.1. Log files and formats </a></span></dt><dd><dl><dt><span class="section"><a href="#anaconda_logging-logformats-files">E.1.1. Logging on the installed system </a></span></dt></dl></dd><dt><span class="section"><a href="#anaconda_logging-rsyslog">E.2. Remote logging with rsyslog </a></span></dt><dt><span class="section"><a href="#anaconda_logging-virtio">E.3. Remote logging via <code class="function">virtio</code> </a></span></dt><dd><dl><dt><span class="section"><a href="#anaconda_logging-virtio_new">E.3.1. <code class="function">virtio</code> logging with <code class="command">virt-install</code> </a></span></dt><dt><span class="section"><a href="#anaconda_logging-virtio_add">E.3.2. Adding a <code class="function">virtio</code> log channel with <code class="command">virsh edit</code> </a></span></dt><dt><span class="section"><a href="#anaconda_logging-virtio_listening">E.
3.3. Listening for <code class="function">virtio</code> logs </a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#ap-techref">F. Other Technical Documentation</a></span></dt></dl></dd><dt><span class="appendix"><a href="#ch-Contributors_and_production_methods">G. Contributors and production methods</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-Contributors">G.1. Contributors</a></span></dt><dt><span class="section"><a href="#sn-Production_methods">G.2. Production methods</a></span></dt></dl></dd><dt><span class="appendix"><a href="#appe-Publican-Revision_History">H. Revision History</a></span></dt><dt><span class="index"><a href="#idm219145944096">Index</a></span></dt></dl></div><div xml:lang="en-US" class="preface" id="Installation-Guide-Preface" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Preface</h1></div></div></div><div xml:lang="en-US" class="section" id="idm219171226752" lang="en-US"><div class="titlepage"><div>
<div keep-together.within-column="always"><h2 class="title" id="idm219171226752">1. Document Conventions</h2></div></div></div><div class="para">
This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information.
</div><div class="para">
In PDF and paper editions, this manual uses typefaces drawn from the <a href="https://fedorahosted.org/liberation-fonts/">Liberation Fonts</a> set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Liberation Fonts set by default.
- </div><div class="section" id="idm225460099600"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225460099600">1.1. Typographic Conventions</h3></div></div></div><div class="para">
+ </div><div class="section" id="idm219181119200"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm219181119200">1.1. Typographic Conventions</h3></div></div></div><div class="para">
Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows.
</div><div class="para">
<code class="literal">Mono-spaced Bold</code>
@@ -83,7 +83,7 @@
Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example:
</div><div class="blockquote"><blockquote class="blockquote"><div class="para">
Publican is a <em class="firstterm">DocBook</em> publishing system.
- </div></blockquote></div></div><div class="section" id="idm225447066752"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225447066752">1.2. Pull-quote Conventions</h3></div></div></div><div class="para">
+ </div></blockquote></div></div><div class="section" id="idm219143427776"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm219143427776">1.2. Pull-quote Conventions</h3></div></div></div><div class="para">
Terminal output and source code listings are set off visually from the surrounding text.
</div><div class="para">
Output sent to a terminal is set in <code class="computeroutput">mono-spaced roman</code> and presented thus:
@@ -108,7 +108,7 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
System.<span class="perl_Function">out</span>.<span class="perl_Function">println</span>(<span class="perl_String">"Echo.echo('Hello') = "</span> + echo.<span class="perl_Function">echo</span>(<span class="perl_String">"Hello"</span>));
}
-}</pre></div><div class="section" id="idm225451942256"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225451942256">1.3. Notes and Warnings</h3></div></div></div><div class="para">
+}</pre></div><div class="section" id="idm219166662592"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm219166662592">1.3. Notes and Warnings</h3></div></div></div><div class="para">
Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.
</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier.
@@ -116,13 +116,13 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring a box labeled 'Important' will not cause data loss but may cause irritation and frustration.
</div></div></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
- </div></div></div></div></div><div xml:lang="en-US" class="section" id="idm225425781152" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm225425781152">2. We Need Feedback!</h2></div></div></div><a id="idm225425780000" class="indexterm"></a><div class="para">
+ </div></div></div></div></div><div xml:lang="en-US" class="section" id="idm219173567568" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm219173567568">2. We Need Feedback!</h2></div></div></div><a id="idm219166649648" class="indexterm"></a><div class="para">
If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in Bugzilla: <a href="http://bugzilla.redhat.com/bugzilla/">http://bugzilla.redhat.com/bugzilla/</a> against the product <span class="application"><strong>Fedora.</strong></span>
</div><div class="para">
When submitting a bug report, be sure to mention the manual's identifier: <em class="citetitle">install-guide</em>
</div><div class="para">
If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.
- </div></div><div class="section" id="idm225439471072"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm225439471072">3. Acknowledgments</h2></div></div></div><div class="para">
+ </div></div><div class="section" id="idm219206020704"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm219206020704">3. Acknowledgments</h2></div></div></div><div class="para">
Certain portions of this text first appeared in the <em class="citetitle">Red Hat Enterprise Linux Installation Guide</em>, copyright © 2011 Red Hat, Inc. and others, published by Red Hat at <a href="https://access.redhat.com/site/documentation/">https://access.redhat.com/site/documentation/</a>.
</div></div></div><div xml:lang="en-US" class="preface" id="ch-introduction" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Introduction</h1></div></div></div><div class="para">
This guide covers installation of Fedora, a Linux distribution built on free and open source software. This manual helps you install Fedora on desktops, laptops, and servers. The installation system is easy to use even if you lack previous knowledge of Linux or computer networks. If you select default options, Fedora provides a complete desktop operating system, including productivity applications, Internet utilities, and desktop tools.
@@ -164,7 +164,7 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
Do any one of the following:
</div><div class="note"><div class="admonition_header"><h2>Verify your downloads</h2></div><div class="admonition"><div class="para">
Downloads may fail for any number of reasons. Always verify the sha256sum of the downloaded files.
- </div></div></div><div class="orderedlist"><ol><li class="listitem"><a id="idm225377764176" class="indexterm"></a><div class="para">
+ </div></div></div><div class="orderedlist"><ol><li class="listitem"><a id="idm219115792160" class="indexterm"></a><div class="para">
Download the ISO image for a Live image. Create CD media from the ISO file using your preferred application. You may also use the <span class="package">livecd-tools</span> package to write the image to other bootable media such as a USB flash disk. To install the distribution to your hard disk, use the shortcut on the desktop after you log in.
</div></li><li class="listitem"><div class="para">
Download the ISO images for the full distribution on DVD. Create DVD media from the ISO files using your preferred application, or put the images on a Windows FAT32 or Linux ext2, ext3, or ext4 partition.
@@ -176,7 +176,7 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
For information on setting up a network boot server from which you can install Fedora, refer to <a class="xref" href="#ap-install-server">Chapter 13, <em>Setting Up an Installation Server</em></a>.
</div></li></ol></div><div class="para">
To learn how to turn ISO images into CD or DVD media, refer to <em class="citetitle">Making Fedora Discs</em> available from <a href="http://docs.fedoraproject.org/readme-burning-isos/">http://docs.fedoraproject.org/readme-burning-isos/</a>.
- </div></div><div class="section" id="sn-expert-prepare"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.3. Prepare for Installation</h2></div></div></div><a id="idm225460249888" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="sn-expert-prepare"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.3. Prepare for Installation</h2></div></div></div><a id="idm219203375232" class="indexterm"></a><div class="para">
Back up any user data you need to preserve.
</div><div class="note"><div class="admonition_header"><h2>Resizing Partitions</h2></div><div class="admonition"><div class="para">
The installation program provides functions for resizing ext2, ext3, ext4, and NTFS formatted partitions. Refer to <a class="xref" href="#s1-diskpartitioning-x86">Section 9.14, “Creating a Custom Partition Layout”</a> for more information.
@@ -184,7 +184,7 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
Boot from the desired media, with any options appropriate for your hardware and installation mode. Refer to <a class="xref" href="#ap-admin-options">Chapter 11, <em>Boot Options</em></a> for more information about boot options. If you boot from the Live CD, select the <span class="guilabel"><strong>Install to Hard Disk</strong></span> option from the desktop to run the installation program. (Alternatively, the option can be found in <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span>.) If you boot from minimal media or a downloaded kernel, select a network or hard disk resource from which to install.
</div><div class="para">
Proceed through all the steps of the installation program. The installation program does not change your system until you make a final confirmation to proceed. When installation is finished, reboot your system.
- </div></div></div><div xml:lang="en-US" class="chapter" id="ch-new-users" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Chapter 2. Obtaining Fedora</h1></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#sect-Obtaining_Fedora-Downloading_Fedora">2.1. Downloading Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-howto-download">2.1.1. How Do I Download Installation Files?</a></span></dt><dt><span class="section"><a href="#sn-which-arch">2.1.2. Which Architecture Is My Computer?</a></span></dt><dt><span class="section"><a href="#sn-which-files">2.1.3. Which Files Do I Download?</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Obtaining_Fedora-Obtaining_Fedora_on_CD_or_DVD">2.2. Obtaining Fedora on CD or DVD</a></span></dt></dl></div><a id="idm225428361744" class="indexterm"></a><a id="idm225450766640" class="indexterm"></a><a id="idm225468350048" class="indexterm"></a><div class="para"
>
+ </div></div></div><div xml:lang="en-US" class="chapter" id="ch-new-users" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Chapter 2. Obtaining Fedora</h1></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#sect-Obtaining_Fedora-Downloading_Fedora">2.1. Downloading Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-howto-download">2.1.1. How Do I Download Installation Files?</a></span></dt><dt><span class="section"><a href="#sn-which-arch">2.1.2. Which Architecture Is My Computer?</a></span></dt><dt><span class="section"><a href="#sn-which-files">2.1.3. Which Files Do I Download?</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Obtaining_Fedora-Obtaining_Fedora_on_CD_or_DVD">2.2. Obtaining Fedora on CD or DVD</a></span></dt></dl></div><a id="idm219170219056" class="indexterm"></a><a id="idm219176787488" class="indexterm"></a><a id="idm219133735584" class="indexterm"></a><div class="para"
>
This chapter explains how to get the files you need to install and run Fedora on your computer. Concepts in this chapter may be new, especially if this is your first free and open source operating system. If you have any trouble with this chapter, find help by visiting the Fedora Forums at <a href="http://www.fedoraforum.org/">http://www.fedoraforum.org/</a>.
</div><div class="para">
The Fedora Project distributes Fedora in many ways, mostly free of cost and downloaded over the Internet. The most common distribution method is CD and DVD media. There are several types of CD and DVD media available, including:
@@ -208,11 +208,11 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
To follow a Web-based guide to downloading, visit <a href="http://get.fedoraproject.org/">http://get.fedoraproject.org/</a>. For guidance on which architecture to download, refer to <a class="xref" href="#sn-which-arch">Section 2.1.2, “Which Architecture Is My Computer?”</a>.
</div></div></div><div class="para">
Fedora software is available for download at no cost in a variety of ways.
- </div><div class="section" id="sn-which-download-mirror"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.1.1. From a Mirror</h4></div></div></div><a id="idm225450971072" class="indexterm"></a><div class="para">
+ </div><div class="section" id="sn-which-download-mirror"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.1.1. From a Mirror</h4></div></div></div><a id="idm219156638624" class="indexterm"></a><div class="para">
The Fedora installation files are freely available from web servers located in many parts of the world. These servers <em class="firstterm">mirror</em> the files available from the Fedora Project. If you visit <a href="http://download.fedoraproject.org/">http://download.fedoraproject.org/</a>, you are redirected to a mirror, based on a calculation of which mirror is likely to offer you the best download speed. Alternatively, you can choose a mirror from the list maintained at <a href="http://mirrors.fedoraproject.org/publiclist">http://mirrors.fedoraproject.org/publiclist</a>. This page lists mirrors according to geographic location. The mirrors geographically closest to you are likely to provide you with the fastest downloads. If the company or organization that provides your internet access maintains a mirror, this mirror is likely to provide you with the fastest downloads of all.
</div><div class="para">
Mirrors publish Fedora software under a well-organized hierarchy of folders. For example, the Fedora 20 distribution normally appears in the directory <code class="filename">fedora/linux/releases/20/</code>. This directory contains a folder for each architecture supported inside that folder, in a folder called <code class="filename">iso/</code>. For example, you can find the file for the DVD distribution of Fedora 20 for x86_64 at <code class="filename">fedora/linux/releases/20/Fedora/x86_64/iso/Fedora-20-x86_64-DVD.iso</code>.
- </div></div><div class="section" id="sn-which-download-bt"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.1.2. From BitTorrent</h4></div></div></div><a id="idm225466770304" class="indexterm"></a><a id="idm225466769344" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="sn-which-download-bt"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.1.2. From BitTorrent</h4></div></div></div><a id="idm219087795104" class="indexterm"></a><a id="idm219153879104" class="indexterm"></a><div class="para">
BitTorrent is a way to download information in cooperation with other computers. Each computer cooperating in the group downloads pieces of the information in a particular torrent from other peers in the group. Computers that have finished downloading all the data in a torrent remain in the swarm to <em class="firstterm">seed</em>, or provide data to other peers. If you download using BitTorrent, as a courtesy you should seed the torrent at least until you have uploaded the same amount of data you downloaded.
</div><div class="para">
If your computer does not have software installed for BitTorrent, visit the BitTorrent home page at <a href="http://www.bittorrent.com/download/">http://www.bittorrent.com/download/</a> to download it. BitTorrent client software is available for Windows, Mac OS, Linux, and many other operating systems.
@@ -222,9 +222,9 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
Minimal boot CD and USB flash disk images are not available through BitTorrent.
</div></div></div><div class="important"><div class="admonition_header"><h2>Verify your download</h2></div><div class="admonition"><div class="para">
Once you have downloaded an ISO, verify it for security and integrity. To follow a web-based guide, visit <a href="https://fedoraproject.org/en/verify">https://fedoraproject.org/en/verify</a>.
- </div></div></div></div></div><div class="section" id="sn-which-arch"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.1.2. Which Architecture Is My Computer?</h3></div></div></div><a id="idm225475506688" class="indexterm"></a><div class="para">
+ </div></div></div></div></div><div class="section" id="sn-which-arch"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.1.2. Which Architecture Is My Computer?</h3></div></div></div><a id="idm219168839744" class="indexterm"></a><div class="para">
Releases are separated by <em class="firstterm">architecture</em>, or type of computer processor. Use the following table to determine the architecture of your computer according to the type of processor. Consult your manufacturer's documentation for details on your processor, if necessary.
- </div><a id="idm225429435936" class="indexterm"></a><div class="table" id="List-Processor_and_Architecture_Types"><h6>Table 2.1. Processor and architecture types</h6><div class="table-contents"><table summary="Processor and architecture types" border="1"><colgroup><col width="75%" align="left" /><col width="25%" align="left" /></colgroup><thead><tr><th class="" align="left">
+ </div><a id="idm219181346352" class="indexterm"></a><div class="table" id="List-Processor_and_Architecture_Types"><h6>Table 2.1. Processor and architecture types</h6><div class="table-contents"><table summary="Processor and architecture types" border="1"><colgroup><col width="75%" align="left" /><col width="25%" align="left" /></colgroup><thead><tr><th class="" align="left">
Processor manufacturer and model
</th><th class="" align="left">
Architecture type for Fedora
@@ -246,18 +246,18 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
You have several options to download Fedora. Read the options below to decide the best one for you.
</div><div class="para">
Each file available for download in a Fedora distribution includes the architecture type in the file name. For example, the file for the DVD distribution of Fedora 20 for x86_64 is named <code class="filename">Fedora-20-x86_64-DVD.iso</code>. Refer to <a class="xref" href="#sn-which-arch">Section 2.1.2, “Which Architecture Is My Computer?”</a> if you are unsure of your computer's architecture.
- </div><div class="orderedlist"><ol><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm225471658256">Full Distribution on DVD</h5>
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm219182184400">Full Distribution on DVD</h5>
If you have plenty of time, a fast Internet connection, and wish a broader choice of software on the install media, download the full DVD version. Once burned to DVD, the media is bootable and includes an installation program. The DVD version contains a mode to perform rescue operations on your Fedora system in an emergency. You can download the DVD version directly from a mirror, or via BitTorrent.
- </div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm225471655968">Live Image</h5>
+ </div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm219162340224">Live Image</h5>
If you want to try Fedora before you install it on your computer, download the Live image version. If your computer supports booting from CD or USB, you can boot the operating system without making any changes to your hard disk. If you decide you like what you see, and want to install it, select <code class="literal">Install to Hard Drive</code> on the desktop to copy Fedora to your hard disk (alternatively, in GNOME, a shortcut can be found in the <span class="guimenu"><strong>Activities</strong></span> menu). You can download the Live image directly from a mirror, or using BitTorrent.
</div><div class="para">
For more detailed instructions on setting up a Live image installation, including selecting a language for the installation process, refer to the <em class="citetitle">Fedora Installation Quick Start Guide</em>.
- </div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm225444493216">Minimal Boot Media</h5>
+ </div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm219129923872">Minimal Boot Media</h5>
If you have a fast Internet connection but do not want to download the entire distribution, you can download a small boot image. Fedora offers images for a minimal boot environment on CD. Once you boot your system with the minimal media, you can install Fedora directly over the Internet. Although this method still involves downloading a significant amount of data over the Internet, it is almost always much less than the size of the full distribution media. Once you have finished installation, you can add or remove software to your system as desired.
</div><div class="note"><div class="admonition_header"><h2>Download Size</h2></div><div class="admonition"><div class="para">
Installing the default software for Fedora over the Internet requires more time than the Live image, but less time than the entire DVD distribution. Actual results depend on the software you select and network traffic conditions.
</div></div></div></li></ol></div><div class="para">
- The following table explains where to find the desired files on a mirror site. Replace <em class="replaceable"><code>arch</code></em> with the architecture of the computer being installed.
+ You can also download the images directly from a mirror, instead of browsing through<a href="http://fedoraproject.org/get-fedora">http://fedoraproject.org/get-fedora</a> The following table explains where to find the desired files on a mirror site. Replace <em class="replaceable"><code>arch</code></em> with the architecture of the computer being installed. If you don't have a preferred mirror, the url <code class="literal">http://download.fedoraproject.org</code> will automatically resolve one.
</div><div class="table" id="tb-Locating_Files"><h6>Table 2.2. Locating files</h6><div class="table-contents"><table summary="Locating files" border="1"><colgroup><col width="33%" align="left" /><col width="67%" align="left" /></colgroup><thead><tr><th class="" align="left">
Media type
</th><th class="" align="left">
@@ -276,7 +276,7 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
<code class="filename">fedora/linux/releases/20/Fedora/<em class="replaceable"><code>arch</code></em>/iso/Fedora-20-<em class="replaceable"><code>arch</code></em>-netinst.iso</code>
</td></tr></tbody></table></div></div><br class="table-break" /></div></div><div class="section" id="sect-Obtaining_Fedora-Obtaining_Fedora_on_CD_or_DVD"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.2. Obtaining Fedora on CD or DVD</h2></div></div></div><div class="para">
If you do not have a fast Internet connection, or if you have a problem creating boot media, downloading may not be an option. Fedora DVD and CD distribution media is available from a number of online sources around the world at a minimal cost. Use your favorite Web search engine to locate a vendor, or refer to <a href="http://fedoraproject.org/wiki/Distribution">http://fedoraproject.org/wiki/Distribution</a>.
- </div></div></div><div xml:lang="en-US" class="chapter" id="sn-making-media" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Chapter 3. Making Media</h1></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#sn-making-disc-media">3.1. Making an installation DVD</a></span></dt><dt><span class="section"><a href="#Making_USB_Media">3.2. Preparing a USB flash drive as an installation source</a></span></dt><dd><dl><dt><span class="section"><a href="#Making_USB_Media-Windows">3.2.1. Making Fedora USB Media on a Windows Operating System</a></span></dt><dt><span class="section"><a href="#Making_USB_Media-UNIX_Linux">3.2.2. Making Fedora USB Media in UNIX, Linux, and Similar Operating Systems</a></span></dt></dl></dd><dt><span class="section"><a href="#Making_Minimal_Boot_Media">3.3. Making Minimal Boot Media</a></span></dt></dl></div><a id="idm225444381376" class="indexterm"></a><a id="idm225441876832" class="indexterm"></a><div cl
ass="para">
+ </div></div></div><div xml:lang="en-US" class="chapter" id="sn-making-media" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Chapter 3. Making Media</h1></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#sn-making-disc-media">3.1. Making an installation DVD</a></span></dt><dt><span class="section"><a href="#Making_USB_Media">3.2. Preparing a USB flash drive as an installation source</a></span></dt><dd><dl><dt><span class="section"><a href="#Making_USB_Media-Windows">3.2.1. Making Fedora USB Media on a Windows Operating System</a></span></dt><dt><span class="section"><a href="#Making_USB_Media-UNIX_Linux">3.2.2. Making Fedora USB Media in UNIX, Linux, and Similar Operating Systems</a></span></dt></dl></dd><dt><span class="section"><a href="#Making_Minimal_Boot_Media">3.3. Making Minimal Boot Media</a></span></dt></dl></div><a id="idm219170886096" class="indexterm"></a><a id="idm219130434976" class="indexterm"></a><div cl
ass="para">
Use the methods described in this section to create the following types of installation and boot media:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
an installation DVD
@@ -516,17 +516,17 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
Download the ISO image file named <code class="filename">netinst.iso</code> that is available at the same location as the images of the Fedora 20 installation DVD — refer to <a class="xref" href="#ch-new-users">Chapter 2, <em>Obtaining Fedora</em></a>.
</div></li><li class="step"><div class="para">
Burn <code class="filename">netinst.iso</code> to a blank CD or DVD using the same procedure detailed in <a class="xref" href="#sn-making-disc-media">Section 3.1, “Making an installation DVD”</a> for the installation disc, or transfer the <code class="filename">netinst.iso</code> file to a USB device with the <span class="application"><strong>dd</strong></span> command as detailed in <a class="xref" href="#Making_USB_Media">Section 3.2, “Preparing a USB flash drive as an installation source”</a>. As the <code class="filename">netinst.iso</code> file is only around 300 MB in size, you do not need an especially large USB flash drive.
- </div></li></ol></div></div></div><div class="part" id="pt-install-info-x86"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part I. Installation and Booting</h1></div></div></div><div class="partintro" id="idm225475830048"><div></div><div class="para">
+ </div></li></ol></div></div></div><div class="part" id="pt-install-info-x86"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part I. Installation and Booting</h1></div></div></div><div class="partintro" id="idm219174394704"><div></div><div class="para">
This part of the <em class="citetitle">Fedora Installation Guide</em> details the installation process itself, from various methods of booting the installer up to the point where the computer must restart to finalize the installation. This part of the manual also includes a chapter on troubleshooting problems with the installation process.
- </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="#ch-steps-x86">4. Planning for Installation on the x86 Architecture</a></span></dt><dd><dl><dt><span class="section"><a href="#idm225426577696">4.1. Upgrade or Install?</a></span></dt><dt><span class="section"><a href="#sn-Is_Your_Hardware_Compatible-x86">4.2. Is Your Hardware Compatible?</a></span></dt><dt><span class="section"><a href="#sn-partitioning-raid-x86">4.3. RAID and Other Disk Devices </a></span></dt><dd><dl><dt><span class="section"><a href="#sn-partitioning-raid-hw-x86">4.3.1. Hardware RAID </a></span></dt><dt><span class="section"><a href="#sn-partitioning-raid-sw-x86">4.3.2. Software RAID </a></span></dt><dt><span class="section"><a href="#sn-partitioning-fw-usb-x86">4.3.3. FireWire and USB Disks </a></span></dt></dl></dd><dt><span class="section"><a href="#Disk_Space-x86">4.4. Do You Have Enough Disk Space?</a></span></dt><dt><span class=
"section"><a href="#s1-installmethod-x86">4.5. Selecting an Installation Method</a></span></dt><dt><span class="section"><a href="#idm225451342128">4.6. Choose a boot method</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Preparing-x86">5. Preparing for Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-steps-network-installs-x86">5.1. Preparing for a Network Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-steps-network-installs-x86-ftp-http">5.1.1. Preparing for FTP and HTTP installation</a></span></dt><dt><span class="section"><a href="#s1-steps-network-installs-x86-nfs">5.1.2. Preparing for an NFS installation</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-steps-hd-installs-x86">5.2. Preparing for a Hard Drive Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-ent-table">6. System Specifications List</a></span></dt><dt><span class="chapter"><a href="#ch-Boot-x86">
7. Booting the Installer</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-x86-starting">7.1. Starting the Installation Program</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x86-starting-booting">7.1.1. Booting the Installation Program on x86, AMD64, and Intel 64 Systems</a></span></dt><dt><span class="section"><a href="#sn-boot-menu-x86">7.1.2. The Boot Menu</a></span></dt><dt><span class="section"><a href="#s2-x86-starting-bootopts">7.1.3. Additional Boot Options</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-booting-from-pxe-x86">7.2. Booting from the Network using PXE </a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Installation_Phase_2-x86">8. Configuring Installation Source</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-installationmethod-x86">8.1. Installation Method</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-begininstall-cd-inst-x86">8.1.1. Installing from DVD</a></span></
dt><dt><span class="section"><a href="#s1-begininstall-hd-x86">8.1.2. Installing from a Hard Drive</a></span></dt><dt><span class="section"><a href="#s1-begininstall-nfs-x86">8.1.3. Installing via NFS</a></span></dt><dt><span class="section"><a href="#s1-begininstall-url-x86">8.1.4. Installing via FTP or HTTP</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-guimode-x86">9. Using the Fedora installer</a></span></dt><dd><dl><dt><span class="section"><a href="#idm225495428512">9.1. The Text Mode Installation Program User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="#idm225456935312">9.1.1. Using the Keyboard to Navigate</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-guimode-interface-x86">9.2. The Graphical Installation Program User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-adminoptions-screenshots">9.2.1. Screenshots during installation</a></span></dt><dt><span class="section"><a h
ref="#sn-guimode-virtual-consoles-x86">9.2.2. A Note about Virtual Consoles</a></span></dt></dl></dd><dt><span class="section"><a href="#language-selection-x86">9.3. Language Selection</a></span></dt><dt><span class="section"><a href="#install-hub-x86">9.4. The Installation Summary Menu </a></span></dt><dt><span class="section"><a href="#s1-timezone-x86">9.5. Date and time</a></span></dt><dt><span class="section"><a href="#sn-keyboard-x86">9.6. Keyboard Configuration</a></span></dt><dt><span class="section"><a href="#language-support-x86">9.7. Language Support</a></span></dt><dt><span class="section"><a href="#installation-source-x86">9.8. Installation Source</a></span></dt><dd><dl><dt><span class="section"><a href="#idm225473537472">9.8.1. Installing from Additional Repositories</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-Netconfig-x86">9.9. Network Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-Netconfig-x86-edit">9.9.1. Ed
it Network Connections</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-pkgselection-x86">9.10. Software Selection</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-mandatory-services-x86">9.10.1. Core Network Services </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-diskpartsetup-x86">9.11. Storage and partitioning</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Storage_Device_Selection_Screen-x86">9.11.1. Specialized and Networked Disks</a></span></dt><dt><span class="section"><a href="#s1-x86-bootloader">9.11.2. x86, AMD64, and Intel 64 Boot Loader Installation</a></span></dt></dl></dd><dt><span class="section"><a href="#encrypt-x86">9.12. Encrypt Partitions </a></span></dt><dt><span class="section"><a href="#reclaim_space-x86">9.13. Reclaim disk space</a></span></dt><dt><span class="section"><a href="#s1-diskpartitioning-x86">9.14. Creating a Custom Partition Layout</a></span></dt><dd><dl><dt><span class="secti
on"><a href="#Adding_Partitions-x86">9.14.1. Adding and Configuring Partitions</a></span></dt><dt><span class="section"><a href="#Create_Software_RAID-x86">9.14.2. Create Software RAID </a></span></dt><dt><span class="section"><a href="#Create_LVM-x86">9.14.3. Create LVM Logical Volume </a></span></dt><dt><span class="section"><a href="#Create_Btrfs-x86">9.14.4. Create a Btrfs subvolume</a></span></dt><dt><span class="section"><a href="#s2-diskpartrecommend-x86">9.14.5. Recommended Partitioning Scheme</a></span></dt></dl></dd><dt><span class="section"><a href="#Begin_installation-x86">9.15. Begin installation</a></span></dt><dt><span class="section"><a href="#s1-progresshub-x86">9.16. The Configuration Menu and Progress Screen</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-account_configuration-x86">9.16.1. Set the Root Password</a></span></dt><dt><span class="section"><a href="#sn-firstboot-systemuser">9.16.2. User Creation</a></span></dt></dl></dd><dt><sp
an class="section"><a href="#s1-complete-x86">9.17. Installation Complete</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-gnome-initial-setup">9.17.1. GNOME Initial Setup</a></span></dt><dt><span class="section"><a href="#sect-other-initial-setup">9.17.2. Initial Setup in Other Desktop Environments</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-trouble-x86">10. Troubleshooting Installation on an Intel or AMD System</a></span></dt><dd><dl><dt><span class="section"><a href="#idm225499886064">10.1. You are unable to boot Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="#idm225419970064">10.1.1. Are You Unable to Boot With Your RAID Card?</a></span></dt><dt><span class="section"><a href="#idm225452658560">10.1.2. Is Your System Displaying Signal 11 Errors?</a></span></dt></dl></dd><dt><span class="section"><a href="#idm225471283760">10.2. Trouble Beginning the Installation</a></span></dt><dd><dl><dt><span class="section"
><a href="#idm225464520544">10.2.1. Problems with Booting into the Graphical Installation</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-trouble-install-x86">10.3. Trouble During the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-trouble-nodevicefound-x86">10.3.1. <code class="computeroutput">No devices found to install Fedora </code> Error Message</a></span></dt><dt><span class="section"><a href="#s2-trouble-tracebacks-x86">10.3.2. Reporting traceback messages</a></span></dt><dt><span class="section"><a href="#s2-trouble-part-tables-x86">10.3.3. Trouble with Partition Tables</a></span></dt><dt><span class="section"><a href="#s2-trouble-space-x86">10.3.4. Using Remaining Space</a></span></dt><dt><span class="section"><a href="#s2-trouble-completeparts-x86">10.3.5. Other Partitioning Problems</a></span></dt></dl></dd><dt><span class="section"><a href="#idm225448803200">10.4. Problems After Installation</a></span></dt><dd><dl><dt><s
pan class="section"><a href="#s2-trouble-grub">10.4.1. Trouble With the Graphical GRUB Screen on an x86-based System?</a></span></dt><dt><span class="section"><a href="#s2-trouble-grub-command-line">10.4.2. Blocked by a GRUB command line after upgrading?</a></span></dt><dt><span class="section"><a href="#Trouble_After_Booting-GUI">10.4.3. Booting into a Graphical Environment</a></span></dt><dt><span class="section"><a href="#idm225460054624">10.4.4. Problems with the X Window System (GUI)</a></span></dt><dt><span class="section"><a href="#idm225503142160">10.4.5. Problems with the X Server Crashing and Non-Root Users</a></span></dt><dt><span class="section"><a href="#idm225461616880">10.4.6. Problems When You Try to Log In</a></span></dt><dt><span class="section"><a href="#s2-trouble-ram">10.4.7. Is Your RAM Not Being Recognized?</a></span></dt><dt><span class="section"><a href="#idm225465817296">10.4.8. Your Printer Does Not Work</a></span></dt><dt><span class="section"><a
href="#idm225447278528">10.4.9. Apache HTTP Server or Sendmail stops responding during startup</a></span></dt></dl></dd></dl></dd></dl></div></div><div xml:lang="en-US" class="chapter" id="ch-steps-x86" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 4. Planning for Installation on the x86 Architecture</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#idm225426577696">4.1. Upgrade or Install?</a></span></dt><dt><span class="section"><a href="#sn-Is_Your_Hardware_Compatible-x86">4.2. Is Your Hardware Compatible?</a></span></dt><dt><span class="section"><a href="#sn-partitioning-raid-x86">4.3. RAID and Other Disk Devices </a></span></dt><dd><dl><dt><span class="section"><a href="#sn-partitioning-raid-hw-x86">4.3.1. Hardware RAID </a></span></dt><dt><span class="section"><a href="#sn-partitioning-raid-sw-x86">4.3.2. Software RAID </a></span></dt><dt><span class="section"><a href="#sn-partitioning-fw-usb-x86">
4.3.3. FireWire and USB Disks </a></span></dt></dl></dd><dt><span class="section"><a href="#Disk_Space-x86">4.4. Do You Have Enough Disk Space?</a></span></dt><dt><span class="section"><a href="#s1-installmethod-x86">4.5. Selecting an Installation Method</a></span></dt><dt><span class="section"><a href="#idm225451342128">4.6. Choose a boot method</a></span></dt></dl></div><div xml:lang="en-US" class="section" id="idm225426577696" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm225426577696">4.1. Upgrade or Install?</h2></div></div></div><div class="para">
+ </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="#ch-steps-x86">4. Planning for Installation on the x86 Architecture</a></span></dt><dd><dl><dt><span class="section"><a href="#idm219208671296">4.1. Upgrade or Install?</a></span></dt><dt><span class="section"><a href="#sn-Is_Your_Hardware_Compatible-x86">4.2. Is Your Hardware Compatible?</a></span></dt><dt><span class="section"><a href="#sn-partitioning-raid-x86">4.3. RAID and Other Disk Devices </a></span></dt><dd><dl><dt><span class="section"><a href="#sn-partitioning-raid-hw-x86">4.3.1. Hardware RAID </a></span></dt><dt><span class="section"><a href="#sn-partitioning-raid-sw-x86">4.3.2. Software RAID </a></span></dt><dt><span class="section"><a href="#sn-partitioning-fw-usb-x86">4.3.3. FireWire and USB Disks </a></span></dt></dl></dd><dt><span class="section"><a href="#Disk_Space-x86">4.4. Do You Have Enough Disk Space?</a></span></dt><dt><span class=
"section"><a href="#s1-installmethod-x86">4.5. Selecting an Installation Method</a></span></dt><dt><span class="section"><a href="#idm219139957120">4.6. Choose a boot method</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Preparing-x86">5. Preparing for Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-steps-network-installs-x86">5.1. Preparing for a Network Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-steps-network-installs-x86-ftp-http">5.1.1. Preparing for FTP and HTTP installation</a></span></dt><dt><span class="section"><a href="#s1-steps-network-installs-x86-nfs">5.1.2. Preparing for an NFS installation</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-steps-hd-installs-x86">5.2. Preparing for a Hard Drive Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-ent-table">6. System Specifications List</a></span></dt><dt><span class="chapter"><a href="#ch-Boot-x86">
7. Booting the Installer</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-x86-starting">7.1. Starting the Installation Program</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x86-starting-booting">7.1.1. Booting the Installation Program on x86, AMD64, and Intel 64 Systems</a></span></dt><dt><span class="section"><a href="#sn-boot-menu-x86">7.1.2. The Boot Menu</a></span></dt><dt><span class="section"><a href="#s2-x86-starting-bootopts">7.1.3. Additional Boot Options</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-booting-from-pxe-x86">7.2. Booting from the Network using PXE </a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Installation_Phase_2-x86">8. Configuring Installation Source</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-installationmethod-x86">8.1. Installation Method</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-begininstall-cd-inst-x86">8.1.1. Installing from DVD</a></span></
dt><dt><span class="section"><a href="#s1-begininstall-hd-x86">8.1.2. Installing from a Hard Drive</a></span></dt><dt><span class="section"><a href="#s1-begininstall-nfs-x86">8.1.3. Installing via NFS</a></span></dt><dt><span class="section"><a href="#s1-begininstall-url-x86">8.1.4. Installing via FTP or HTTP</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-guimode-x86">9. Using the Fedora installer</a></span></dt><dd><dl><dt><span class="section"><a href="#idm219199222144">9.1. The Text Mode Installation Program User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="#idm219174347776">9.1.1. Using the Keyboard to Navigate</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-guimode-interface-x86">9.2. The Graphical Installation Program User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-adminoptions-screenshots">9.2.1. Screenshots during installation</a></span></dt><dt><span class="section"><a h
ref="#sn-guimode-virtual-consoles-x86">9.2.2. A Note about Virtual Consoles</a></span></dt></dl></dd><dt><span class="section"><a href="#language-selection-x86">9.3. Language Selection</a></span></dt><dt><span class="section"><a href="#install-hub-x86">9.4. The Installation Summary Menu </a></span></dt><dt><span class="section"><a href="#s1-timezone-x86">9.5. Date and time</a></span></dt><dt><span class="section"><a href="#sn-keyboard-x86">9.6. Keyboard Configuration</a></span></dt><dt><span class="section"><a href="#language-support-x86">9.7. Language Support</a></span></dt><dt><span class="section"><a href="#installation-source-x86">9.8. Installation Source</a></span></dt><dd><dl><dt><span class="section"><a href="#idm219180754816">9.8.1. Installing from Additional Repositories</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-Netconfig-x86">9.9. Network Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-Netconfig-x86-edit">9.9.1. Ed
it Network Connections</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-pkgselection-x86">9.10. Software Selection</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-mandatory-services-x86">9.10.1. Core Network Services </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-diskpartsetup-x86">9.11. Storage and partitioning</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Storage_Device_Selection_Screen-x86">9.11.1. Specialized and Networked Disks</a></span></dt><dt><span class="section"><a href="#s1-x86-bootloader">9.11.2. x86, AMD64, and Intel 64 Boot Loader Installation</a></span></dt></dl></dd><dt><span class="section"><a href="#encrypt-x86">9.12. Encrypt Partitions </a></span></dt><dt><span class="section"><a href="#reclaim_space-x86">9.13. Reclaim disk space</a></span></dt><dt><span class="section"><a href="#s1-diskpartitioning-x86">9.14. Creating a Custom Partition Layout</a></span></dt><dd><dl><dt><span class="secti
on"><a href="#Adding_Partitions-x86">9.14.1. Adding and Configuring Partitions</a></span></dt><dt><span class="section"><a href="#Create_Software_RAID-x86">9.14.2. Create Software RAID </a></span></dt><dt><span class="section"><a href="#Create_LVM-x86">9.14.3. Create LVM Logical Volume </a></span></dt><dt><span class="section"><a href="#Create_Btrfs-x86">9.14.4. Create a Btrfs subvolume</a></span></dt><dt><span class="section"><a href="#s2-diskpartrecommend-x86">9.14.5. Recommended Partitioning Scheme</a></span></dt><dt><span class="section"><a href="#s1-diskpartitioning-confirm">9.14.6. Review and Confirm Custom Partition Layout</a></span></dt></dl></dd><dt><span class="section"><a href="#Begin_installation-x86">9.15. Begin installation</a></span></dt><dt><span class="section"><a href="#s1-progresshub-x86">9.16. The Configuration Menu and Progress Screen</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-account_configuration-x86">9.16.1. Set the Root Password
</a></span></dt><dt><span class="section"><a href="#sn-firstboot-systemuser">9.16.2. User Creation</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-complete-x86">9.17. Installation Complete</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-gnome-initial-setup">9.17.1. GNOME Initial Setup</a></span></dt><dt><span class="section"><a href="#sect-other-initial-setup">9.17.2. Initial Setup in Other Desktop Environments</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-trouble-x86">10. Troubleshooting Installation on an Intel or AMD System</a></span></dt><dd><dl><dt><span class="section"><a href="#idm219175807424">10.1. You are unable to boot Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="#idm219168676576">10.1.1. Are You Unable to Boot With Your RAID Card?</a></span></dt><dt><span class="section"><a href="#idm219174625744">10.1.2. Is Your System Displaying Signal 11 Errors?</a></span></dt></dl></dd><dt><span c
lass="section"><a href="#idm219168475296">10.2. Trouble Beginning the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#idm219139851008">10.2.1. Problems with Booting into the Graphical Installation</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-trouble-install-x86">10.3. Trouble During the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-trouble-nodevicefound-x86">10.3.1. <code class="computeroutput">No devices found to install Fedora </code> Error Message</a></span></dt><dt><span class="section"><a href="#s2-trouble-tracebacks-x86">10.3.2. Reporting traceback messages</a></span></dt><dt><span class="section"><a href="#s2-trouble-part-tables-x86">10.3.3. Trouble with Partition Tables</a></span></dt><dt><span class="section"><a href="#s2-trouble-space-x86">10.3.4. Using Remaining Space</a></span></dt><dt><span class="section"><a href="#s2-trouble-completeparts-x86">10.3.5. Other Partitioning Problems</a></span>
</dt></dl></dd><dt><span class="section"><a href="#idm219181583248">10.4. Problems After Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-trouble-grub">10.4.1. Trouble With the Graphical GRUB Screen on an x86-based System?</a></span></dt><dt><span class="section"><a href="#s2-trouble-grub-command-line">10.4.2. Blocked by a GRUB command line after upgrading?</a></span></dt><dt><span class="section"><a href="#Trouble_After_Booting-GUI">10.4.3. Booting into a Graphical Environment</a></span></dt><dt><span class="section"><a href="#idm219179265600">10.4.4. Problems with the X Window System (GUI)</a></span></dt><dt><span class="section"><a href="#idm219157531344">10.4.5. Problems with the X Server Crashing and Non-Root Users</a></span></dt><dt><span class="section"><a href="#idm219150647984">10.4.6. Problems When You Try to Log In</a></span></dt><dt><span class="section"><a href="#s2-trouble-ram">10.4.7. Is Your RAM Not Being Recognized?</a></span></dt><
dt><span class="section"><a href="#idm219173233792">10.4.8. Your Printer Does Not Work</a></span></dt><dt><span class="section"><a href="#idm219114810544">10.4.9. Apache HTTP Server or Sendmail stops responding during startup</a></span></dt></dl></dd></dl></dd></dl></div></div><div xml:lang="en-US" class="chapter" id="ch-steps-x86" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 4. Planning for Installation on the x86 Architecture</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#idm219208671296">4.1. Upgrade or Install?</a></span></dt><dt><span class="section"><a href="#sn-Is_Your_Hardware_Compatible-x86">4.2. Is Your Hardware Compatible?</a></span></dt><dt><span class="section"><a href="#sn-partitioning-raid-x86">4.3. RAID and Other Disk Devices </a></span></dt><dd><dl><dt><span class="section"><a href="#sn-partitioning-raid-hw-x86">4.3.1. Hardware RAID </a></span></dt><dt><span class="section"><a href="#
sn-partitioning-raid-sw-x86">4.3.2. Software RAID </a></span></dt><dt><span class="section"><a href="#sn-partitioning-fw-usb-x86">4.3.3. FireWire and USB Disks </a></span></dt></dl></dd><dt><span class="section"><a href="#Disk_Space-x86">4.4. Do You Have Enough Disk Space?</a></span></dt><dt><span class="section"><a href="#s1-installmethod-x86">4.5. Selecting an Installation Method</a></span></dt><dt><span class="section"><a href="#idm219139957120">4.6. Choose a boot method</a></span></dt></dl></div><div xml:lang="en-US" class="section" id="idm219208671296" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm219208671296">4.1. Upgrade or Install?</h2></div></div></div><div class="para">
For information to help you determine whether to perform an upgrade or an installation refer to <a class="xref" href="#ch-upgrade-x86">Chapter 18, <em>Upgrading Your Current System</em></a>.
- </div></div><div xml:lang="en-US" class="section" id="sn-Is_Your_Hardware_Compatible-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.2. Is Your Hardware Compatible?</h2></div></div></div><a id="idm225467370880" class="indexterm"></a><a id="idm225468768320" class="indexterm"></a><div class="para">
+ </div></div><div xml:lang="en-US" class="section" id="sn-Is_Your_Hardware_Compatible-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.2. Is Your Hardware Compatible?</h2></div></div></div><a id="idm219146142976" class="indexterm"></a><a id="idm219146143488" class="indexterm"></a><div class="para">
Hardware compatibility is particularly important if you have an older system or a system that you built yourself. Fedora 20 should be compatible with most hardware in systems that were factory built within the last two years. However, hardware specifications change almost daily, so it is difficult to guarantee that your hardware is 100% compatible.
</div><div class="para">
If you have issues with your hardware, consider one of the following:
<table border="0" summary="Simple list" class="simplelist"><tr><td> <span class="emphasis"><em>Consult the release notes for minimum system requirements</em></span> at <a href="http://docs.fedoraproject.org/release-notes">http://docs.fedoraproject.org/release-notes</a> . </td></tr><tr><td> <span class="emphasis"><em>Seek Support</em></span> at <a href="http://fedoraproject.org/wiki/Communicating_and_getting_help">http://fedoraproject.org/wiki/Communicating_and_getting_help</a> </td></tr><tr><td> <span class="emphasis"><em>Check online compatibility lists,</em></span> such as <a href="http://www.fsf.org/resources/hw">http://www.fsf.org/resources/hw</a> and <a href="http://www.linux-drivers.org/">http://www.linux-drivers.org/</a> </td></tr></table>
- </div></div><div xml:lang="en-US" class="section" id="sn-partitioning-raid-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.3. RAID and Other Disk Devices </h2></div></div></div><a id="idm225475328080" class="indexterm"></a><a id="idm225474191888" class="indexterm"></a><a id="idm225472671728" class="indexterm"></a><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important — Systems with Intel BIOS RAID sets</h2></div><div class="admonition"><div class="para">
+ </div></div><div xml:lang="en-US" class="section" id="sn-partitioning-raid-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.3. RAID and Other Disk Devices </h2></div></div></div><a id="idm219138612560" class="indexterm"></a><a id="idm219150489920" class="indexterm"></a><a id="idm219178099200" class="indexterm"></a><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important — Systems with Intel BIOS RAID sets</h2></div><div class="admonition"><div class="para">
Fedora 20 uses <span class="application"><strong>mdraid</strong></span> instead of <span class="application"><strong>dmraid</strong></span> for installation onto Intel BIOS RAID sets. These sets are detected automatically, and devices with Intel ISW metadata are recognized as mdraid instead of dmraid. Note that the device node names of any such devices under <span class="application"><strong>mdraid</strong></span> are different from their device node names under <span class="application"><strong>dmraid</strong></span>. Therefore, special precautions are necessary when you migrate systems with Intel BIOS RAID sets.
</div><div class="para">
Local modifications to <code class="filename">/etc/fstab</code>, <code class="filename">/etc/crypttab</code> or other configuration files which refer to devices by their device node names will not work in Fedora 20. Before migrating these files, you must therefore edit them to replace device node paths with device UUIDs instead. You can find the UUIDs of devices with the <code class="command">blkid</code> command.
@@ -540,47 +540,47 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
Some FireWire and USB hard disks may not be recognized by the Fedora installation system. If configuration of these disks at installation time is not vital, disconnect them to avoid any confusion.
</div><div class="note" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Post-installation Usage</h2></div><div class="admonition"><div class="para">
You can connect and configure external FireWire and USB hard disks after installation. Most such devices are recognized by the kernel and available for use at that time.
- </div></div></div></div></div><div xml:lang="en-US" class="section" id="Disk_Space-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.4. Do You Have Enough Disk Space?</h2></div></div></div><a id="idm225458987744" class="indexterm"></a><a id="idm225449112848" class="indexterm"></a><a id="idm225451853440" class="indexterm"></a><div class="para">
+ </div></div></div></div></div><div xml:lang="en-US" class="section" id="Disk_Space-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.4. Do You Have Enough Disk Space?</h2></div></div></div><a id="idm219168009376" class="indexterm"></a><a id="idm219157477408" class="indexterm"></a><a id="idm219204980064" class="indexterm"></a><div class="para">
Nearly every modern-day operating system (OS) uses <em class="firstterm">disk partitions</em>, and Fedora is no exception. When you install Fedora, you may have to work with disk partitions. If you have not worked with disk partitions before (or need a quick review of the basic concepts), refer to <a class="xref" href="#ch-partitions-x86">Appendix A, <em>An Introduction to Disk Partitions</em></a> before proceeding.
</div><div class="para">
The disk space used by Fedora must be separate from the disk space used by other OSes you may have installed on your system, such as Windows, OS/2, or even a different version of Linux. For x86, AMD64, and Intel 64 systems, at least two partitions (<code class="filename">/</code> and <code class="filename">swap</code>) must be dedicated to Fedora.
</div><div class="para">
Before you start the installation process, you must
</div><div xml:lang="en-US" class="itemizedlist" lang="en-US"><ul><li class="listitem"><div class="para">
- have enough <span class="emphasis"><em>unpartitioned<a href="#ftn.idm225440949648" class="footnote"><sup class="footnote" id="idm225440949648">[1]</sup></a></em></span> disk space for the installation of Fedora, or
+ have enough <span class="emphasis"><em>unpartitioned<a href="#ftn.idm219142951728" class="footnote"><sup class="footnote" id="idm219142951728">[1]</sup></a></em></span> disk space for the installation of Fedora, or
</div></li><li class="listitem"><div class="para">
have one or more partitions that may be deleted, thereby freeing up enough disk space to install Fedora.
</div></li></ul></div><div class="para">
To gain a better sense of how much space you really need, refer to the recommended partitioning sizes discussed in <a class="xref" href="#s2-diskpartrecommend-x86">Section 9.14.5, “Recommended Partitioning Scheme”</a>.
</div><div class="para">
If you are not sure that you meet these conditions, or if you want to know how to create free disk space for your Fedora installation, refer to <a class="xref" href="#ch-partitions-x86">Appendix A, <em>An Introduction to Disk Partitions</em></a>.
- </div></div><div xml:lang="en-US" class="section" id="s1-installmethod-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.5. Selecting an Installation Method</h2></div></div></div><a id="idm225475678608" class="indexterm"></a><div class="para">
+ </div></div><div xml:lang="en-US" class="section" id="s1-installmethod-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.5. Selecting an Installation Method</h2></div></div></div><a id="idm219182015248" class="indexterm"></a><div class="para">
What type of installation method do you wish to use? The following installation methods are available:
- </div><a id="idm225501266064" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">DVD</span></dt><dd><div class="para">
+ </div><a id="idm219177059520" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">DVD</span></dt><dd><div class="para">
If you have a DVD drive and the Fedora DVD you can use this method. Refer to <a class="xref" href="#s1-begininstall-cd-inst-x86">Section 8.1.1, “Installing from DVD”</a>, for DVD installation instructions.
</div><div class="para">
If you booted the installation from a piece of media other than the installation DVD, you can specify the DVD as the installation source with the <code class="command">linux repo=cdrom:<em class="replaceable"><code>device</code></em>:/<em class="replaceable"><code>device</code></em></code> boot option, or by selecting <span class="guimenuitem"><strong>Local CD/DVD</strong></span> on the <span class="guimenu"><strong>Installation Method</strong></span> menu (refer to <a class="xref" href="#s1-installationmethod-x86">Section 8.1, “Installation Method”</a>).
- </div></dd><dt class="varlistentry"><span class="term">Live CD</span></dt><dd><div class="para">
- If you have a CD drive and the Fedora live CD you can use this method. The live CD desktop includes an icon labeled <span class="guilabel"><strong>Install to Hard Drive</strong></span>. Refer to <a class="xref" href="#s1-begininstall-cd-inst-x86">Section 8.1.1, “Installing from DVD”</a> for CD installation instructions.
- </div></dd><dt class="varlistentry"><span class="term">Hard Drive</span></dt><dd><a id="idm225466225616" class="indexterm"></a><div class="para">
- If you have copied the Fedora ISO images to a local hard drive, you can use this method. You need a boot CD-ROM (use the <code class="command">linux repo=hd:<em class="replaceable"><code>device</code></em>:/<em class="replaceable"><code>path</code></em></code> boot option), or by selecting <span class="guimenuitem"><strong>Hard drive</strong></span> on the <span class="guimenu"><strong>Installation Method</strong></span> menu (refer to <a class="xref" href="#s1-installationmethod-x86">Section 8.1, “Installation Method”</a>). Refer to <a class="xref" href="#s1-begininstall-hd-x86">Section 8.1.2, “Installing from a Hard Drive”</a>, for hard drive installation instructions.
- </div></dd><dt class="varlistentry"><span class="term">NFS</span></dt><dd><a id="idm225428360736" class="indexterm"></a><div class="para">
+ </div></dd><dt class="varlistentry"><span class="term">Live</span></dt><dd><div class="para">
+ If you have a optical or USB drive and the Fedora Live image you can use this method. The live CD desktop includes an icon labeled <span class="guilabel"><strong>Install to Hard Drive</strong></span>. Refer to <a class="xref" href="#s1-begininstall-cd-inst-x86">Section 8.1.1, “Installing from DVD”</a> for installation instructions.
+ </div></dd><dt class="varlistentry"><span class="term">Hard Drive</span></dt><dd><a id="idm219173332464" class="indexterm"></a><div class="para">
+ If you have copied the Fedora ISO images to a local hard drive, you can use this method. Add the boot option <code class="command">linux repo=hd:<em class="replaceable"><code>device</code></em>:/<em class="replaceable"><code>path</code></em></code> or you select <span class="guimenuitem"><strong>ISO file:</strong></span> from the <span class="guimenu"><strong>Installation Source</strong></span> menu after starting the installation. (refer to <a class="xref" href="#s1-installationmethod-x86">Section 8.1, “Installation Method”</a>). Refer to <a class="xref" href="#s1-begininstall-hd-x86">Section 8.1.2, “Installing from a Hard Drive”</a>, for hard drive installation instructions. If your system already has GRUB installed, you can set up a completely medialess installation with the instructions at <a class="xref" href="#ap-medialess-install">Chapter 12, <em>Installing Without Media</em></a>.
+ </div></dd><dt class="varlistentry"><span class="term">NFS</span></dt><dd><a id="idm219174871104" class="indexterm"></a><div class="para">
If you are installing from an NFS server using ISO images or a mirror image of Fedora, you can use this method. You need a boot CD-ROM (use the <code class="command">linux repo=nfs:<em class="replaceable"><code>server</code></em> <em class="replaceable"><code>:options</code></em>:/<em class="replaceable"><code>path</code></em></code> boot option, or the <span class="guimenuitem"><strong>NFS directory</strong></span> option on the <span class="guimenu"><strong>Installation Method</strong></span> menu described in <a class="xref" href="#s1-installationmethod-x86">Section 8.1, “Installation Method”</a>). Refer to <a class="xref" href="#s1-begininstall-nfs-x86">Section 8.1.3, “Installing via NFS”</a> for network installation instructions. Note that NFS installations may also be performed in GUI mode.
- </div></dd><dt class="varlistentry"><span class="term">URL</span></dt><dd><a id="idm225503301312" class="indexterm"></a><div class="para">
+ </div></dd><dt class="varlistentry"><span class="term">URL</span></dt><dd><a id="idm219132195088" class="indexterm"></a><div class="para">
If you are installing directly from an HTTP (Web) server or FTP server, use this method. You need a boot CD-ROM (use the <code class="command">linux repo=ftp://<em class="replaceable"><code>user</code></em>:<em class="replaceable"><code>password</code></em>@<em class="replaceable"><code>host</code></em>/<em class="replaceable"><code>path</code></em></code>, or <code class="command">linux repo=http://<em class="replaceable"><code>host</code></em>/<em class="replaceable"><code>path</code></em></code> boot option, or the <span class="guimenuitem"><strong>URL</strong></span> option on the <span class="guimenu"><strong>Installation Method</strong></span> menu described in <a class="xref" href="#s1-installationmethod-x86">Section 8.1, “Installation Method”</a>). Refer to <a class="xref" href="#s1-begininstall-url-x86">Section 8.1.4, “Installing via FTP or HTTP”</a>, for FTP and HTTP installation instructions.
- </div></dd></dl></div></div><div xml:lang="en-US" class="section" id="idm225451342128" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm225451342128">4.6. Choose a boot method</h2></div></div></div><a id="idm225493168720" class="indexterm"></a><div class="para">
+ </div></dd></dl></div></div><div xml:lang="en-US" class="section" id="idm219139957120" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm219139957120">4.6. Choose a boot method</h2></div></div></div><a id="idm219165658960" class="indexterm"></a><div class="para">
You can use several methods to boot Fedora.
</div><div class="para">
Installing from a CD-ROM or DVD requires that you have a Fedora 20 CD-ROM or DVD, and you have a DVD/CD-ROM drive on a system that supports booting from it.
</div><div class="para">
Your BIOS may need to be changed to allow booting from your DVD/CD-ROM drive. For more information about changing your BIOS, refer to <a class="xref" href="#s2-x86-starting-booting">Section 7.1.1, “Booting the Installation Program on x86, AMD64, and Intel 64 Systems”</a>.
</div><div class="para">
- Other than booting from an installation CD or DVD, you can also boot the Fedora installation program from <em class="firstterm">minimal boot media</em> in the form of a bootable CD or USB flash drive. After you boot the system with a piece of minimal boot media, you complete the installation from a different installation source, such as a local hard drive or a location on a network. Refer to <a class="xref" href="#Making_Minimal_Boot_Media">Section 3.3, “Making Minimal Boot Media”</a> for instructions on making boot CDs and USB flash drives.
+ Other than booting from an installation DVD or netinstall CD, you can also boot the Fedora installation program from a USB flash drive. Refer to <a class="xref" href="#Making_USB_Media">Section 3.2, “Preparing a USB flash drive as an installation source”</a> for instructions on making USB install media.
</div><div class="para">
Finally, you can boot the installer overthe network from a <em class="firstterm">preboot execution environment</em> (PXE) server. Refer to <a class="xref" href="#ap-install-server">Chapter 13, <em>Setting Up an Installation Server</em></a>. Again, after you boot the system, you complete the installation from a different installation source, such as a local hard drive or a location on a network.
- </div></div><div class="footnotes"><br /><hr width="100" align="left" /><div id="ftn.idm225440949648" class="footnote"><div class="para"><a href="#idm225440949648" class="para"><sup class="para">[1] </sup></a>
+ </div></div><div class="footnotes"><br /><hr width="100" align="left" /><div id="ftn.idm219142951728" class="footnote"><div class="para"><a href="#idm219142951728" class="para"><sup class="para">[1] </sup></a>
Unpartitioned disk space means that available disk space on the hard drives you are installing to has not been divided into sections for data. When you partition a disk, each partition behaves like a separate disk drive.
- </div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-Preparing-x86" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 5. Preparing for Installation</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-steps-network-installs-x86">5.1. Preparing for a Network Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-steps-network-installs-x86-ftp-http">5.1.1. Preparing for FTP and HTTP installation</a></span></dt><dt><span class="section"><a href="#s1-steps-network-installs-x86-nfs">5.1.2. Preparing for an NFS installation</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-steps-hd-installs-x86">5.2. Preparing for a Hard Drive Installation</a></span></dt></dl></div><div xml:lang="en-US" class="section" id="s1-steps-network-installs-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.1. Preparing for a Network
Installation</h2></div></div></div><a id="idm225459287424" class="indexterm"></a><a id="idm225461580384" class="indexterm"></a><a id="idm225468757264" class="indexterm"></a><a id="idm225477024080" class="indexterm"></a><a id="idm225471711648" class="indexterm"></a><a id="idm225459288032" class="indexterm"></a><a id="idm225444603168" class="indexterm"></a><a id="idm225448158544" class="indexterm"></a><div class="note" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ </div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-Preparing-x86" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 5. Preparing for Installation</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-steps-network-installs-x86">5.1. Preparing for a Network Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-steps-network-installs-x86-ftp-http">5.1.1. Preparing for FTP and HTTP installation</a></span></dt><dt><span class="section"><a href="#s1-steps-network-installs-x86-nfs">5.1.2. Preparing for an NFS installation</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-steps-hd-installs-x86">5.2. Preparing for a Hard Drive Installation</a></span></dt></dl></div><div xml:lang="en-US" class="section" id="s1-steps-network-installs-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.1. Preparing for a Network
Installation</h2></div></div></div><a id="idm219179294784" class="indexterm"></a><a id="idm219169740816" class="indexterm"></a><a id="idm219179292512" class="indexterm"></a><a id="idm219179293360" class="indexterm"></a><a id="idm219179294624" class="indexterm"></a><a id="idm219179295808" class="indexterm"></a><a id="idm219179297024" class="indexterm"></a><a id="idm219201224416" class="indexterm"></a><div class="note" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
Make sure no installation DVD (or any other type of DVD or CD) is in your system's CD or DVD drive if you are performing a network-based installation. Having a DVD or CD in the drive might cause unexpected errors.
</div></div></div><div class="para">
Ensure that you have boot media available on CD, DVD, or a USB storage device such as a flash drive.
@@ -624,11 +624,11 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
</div><pre xml:lang="en-US" class="screen" lang="en-US"><code class="command"><em class="replaceable"><code>/publicly_available_directory</code></em> * (ro)</code></pre></li><li class="step"><div class="para">
On the network server, start the NFS daemon (use <code class="command">systemctl start nfs</code>). If NFS is already running, reload the configuration file (use <code class="command">systemctl reload nfs</code>).
</div></li><li class="step"><div class="para">
- Be sure to test the NFS share following the directions in the <em class="citetitle">Fedora Deployment Guide</em>. Refer to your NFS documentation for details on starting and stopping the NFS server.
+ Be sure to test the NFS share following the directions in the <em class="citetitle">Fedora System Administrators Guide</em>. Refer to your NFS documentation for details on starting and stopping the NFS server.
</div></li></ol></div><div class="note" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
The Fedora installation program has the ability to test the integrity of the installation media. It works with the CD, DVD, hard drive ISO, and NFS ISO installation methods. We recommend that you test all installation media before starting the installation process, and before reporting any installation-related bugs (many of the bugs reported are actually due to improperly-burned discs). To use this test, type the following command at the <code class="prompt">boot:</code> prompt:
</div><pre class="screen">
-<strong class="userinput"><code>linux rd.live.check</code></strong></pre></div></div></div></div><div xml:lang="en-US" class="section" id="s1-steps-hd-installs-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.2. Preparing for a Hard Drive Installation</h2></div></div></div><a id="idm225455768464" class="indexterm"></a><a id="idm225419514336" class="indexterm"></a><div class="note" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Note — Not all file systems supported</h2></div><div class="admonition"><div class="para">
+<strong class="userinput"><code>linux rd.live.check</code></strong></pre></div></div></div></div><div xml:lang="en-US" class="section" id="s1-steps-hd-installs-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.2. Preparing for a Hard Drive Installation</h2></div></div></div><a id="idm219175555440" class="indexterm"></a><a id="idm219133803488" class="indexterm"></a><div class="note" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Note — Not all file systems supported</h2></div><div class="admonition"><div class="para">
Hard drive installations only work from ext2, ext3, ext4, or FAT file systems. You cannot use a hard drive formatted for any other file system as an installation source for Fedora.
</div><div class="para">
To check the file system of a hard drive partition on a Windows operating system, use the <span class="application"><strong>Disk Management</strong></span> tool. To check the file system of a hard drive partition on a Linux operating system, use the <span class="application"><strong>fdisk</strong></span> tool.
@@ -659,7 +659,7 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
</div></li></ol></div><div class="note" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
The Fedora installation program has the ability to test the integrity of the installation media. It works with the CD, DVD, hard drive ISO, and NFS ISO installation methods. We recommend that you test all installation media before starting the installation process, and before reporting any installation-related bugs (many of the bugs reported are actually due to improperly-burned discs). To use this test, type the following command at the <code class="prompt">boot:</code> prompt:
</div><pre class="screen">
-<strong class="userinput"><code>linux rd.live.check</code></strong></pre></div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-ent-table" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 6. System Specifications List</h2></div></div></div><a id="idm225478229792" class="indexterm"></a><a id="idm225503339888" class="indexterm"></a><div class="para">
+<strong class="userinput"><code>linux rd.live.check</code></strong></pre></div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-ent-table" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 6. System Specifications List</h2></div></div></div><a id="idm219162801568" class="indexterm"></a><a id="idm219141964752" class="indexterm"></a><div class="para">
The installation program automatically detects and installs your computer's hardware. Although you should make sure that your hardware meets the minimum requirements to install Fedora (refer to <a class="xref" href="#sn-Is_Your_Hardware_Compatible-x86">Section 4.2, “Is Your Hardware Compatible?”</a>) you do not usually need to supply the installation program with any specific details about your system.
</div><div class="para">
However, when performing certain types of installation, some specific details might be useful or even essential.
@@ -699,7 +699,7 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
If your computer is part of a domain:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
You should verify that the domain name will be supplied by the DHCP server. If not, you will need to input the domain name manually during installation.
- </div></li></ul></div></li></ul></div></div><div xml:lang="en-US" class="chapter" id="ch-Boot-x86" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 7. Booting the Installer</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-x86-starting">7.1. Starting the Installation Program</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x86-starting-booting">7.1.1. Booting the Installation Program on x86, AMD64, and Intel 64 Systems</a></span></dt><dt><span class="section"><a href="#sn-boot-menu-x86">7.1.2. The Boot Menu</a></span></dt><dt><span class="section"><a href="#s2-x86-starting-bootopts">7.1.3. Additional Boot Options</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-booting-from-pxe-x86">7.2. Booting from the Network using PXE </a></span></dt></dl></div><a id="idm225471092256" class="indexterm"></a><a id="idm225446590640" class="indexterm"></a><a id="idm225428532864" class="inde
xterm"></a><a id="idm225377788224" class="indexterm"></a><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important — UEFI for 32-bit x86 systems</h2></div><div class="admonition"><div class="para">
+ </div></li></ul></div></li></ul></div></div><div xml:lang="en-US" class="chapter" id="ch-Boot-x86" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 7. Booting the Installer</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-x86-starting">7.1. Starting the Installation Program</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x86-starting-booting">7.1.1. Booting the Installation Program on x86, AMD64, and Intel 64 Systems</a></span></dt><dt><span class="section"><a href="#sn-boot-menu-x86">7.1.2. The Boot Menu</a></span></dt><dt><span class="section"><a href="#s2-x86-starting-bootopts">7.1.3. Additional Boot Options</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-booting-from-pxe-x86">7.2. Booting from the Network using PXE </a></span></dt></dl></div><a id="idm219145572496" class="indexterm"></a><a id="idm219156819712" class="indexterm"></a><a id="idm219167394560" class="inde
xterm"></a><a id="idm219126684112" class="indexterm"></a><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important — UEFI for 32-bit x86 systems</h2></div><div class="admonition"><div class="para">
Fedora 20 does not support UEFI booting for 32-bit x86 systems. Only BIOS booting is supported.
</div></div></div><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important — UEFI for AMD64 and Intel 64</h2></div><div class="admonition"><div class="para">
Note that the boot configurations of UEFI and BIOS differ significantly from each other. Therefore, the installed system must boot using the same firmware that was used during installation. You cannot install the operating system on a system that uses BIOS and then boot this installation on a system that uses UEFI.
@@ -729,7 +729,7 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
Save your changes before exiting the BIOS. For more information, refer to the documentation that came with your system.
</div><div class="note" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Note — Aborting the Installation</h2></div><div class="admonition"><div class="para">
To abort the installation, either press <span class="keycap"><strong>Ctrl </strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Del</strong></span> or power off your computer with the power switch. You may abort the installation process without consequence at any time prior to selecting <span class="guibutton"><strong>Begin Installation</strong></span> on the Installation Summary Menu. Fedora makes no permanent changes to your computer until that point. Please be aware that stopping the installation after partitioning has begun can leave your computer unusable.
- </div></div></div><div xml:lang="en-US" class="section" id="s1-x86-starting" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.1. Starting the Installation Program</h2></div></div></div><a id="idm225434225440" class="indexterm"></a><a id="idm225465333936" class="indexterm"></a><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important — UEFI for 32-bit x86 systems</h2></div><div class="admonition"><div class="para">
+ </div></div></div><div xml:lang="en-US" class="section" id="s1-x86-starting" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.1. Starting the Installation Program</h2></div></div></div><a id="idm219167371920" class="indexterm"></a><a id="idm219085279040" class="indexterm"></a><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important — UEFI for 32-bit x86 systems</h2></div><div class="admonition"><div class="para">
Fedora 20 does not support UEFI booting for 32-bit x86 systems. Only BIOS booting is supported.
</div></div></div><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important — UEFI for AMD64 and Intel 64</h2></div><div class="admonition"><div class="para">
Note that the boot configurations of UEFI and BIOS differ significantly from each other. Therefore, the installed system must boot using the same firmware that was used during installation. You cannot install the operating system on a system that uses BIOS and then boot this installation on a system that uses UEFI.
@@ -737,7 +737,7 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
Fedora 20 supports version 2.2 of the UEFI specification. Hardware that supports version 2.3 of the UEFI specification or later should boot and operate with Fedora 20, but the additional functionality defined by these later specifications will not be available. The UEFI specifications are available from <a href="http://www.uefi.org/specs/agreement/">http://www.uefi.org/specs/agreement/</a>
</div></div></div><div class="para">
To start, first make sure that you have all necessary resources for the installation. If you have already read through <a class="xref" href="#ch-steps-x86">Chapter 4, <em>Planning for Installation on the x86 Architecture</em></a>, and followed the instructions, you should be ready to start the installation process. When you have verified that you are ready to begin, boot the installation program using the Fedora DVD or any boot media that you have created.
- </div><div class="section" id="s2-x86-starting-booting"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.1.1. Booting the Installation Program on x86, AMD64, and Intel 64 Systems</h3></div></div></div><a id="idm225440734048" class="indexterm"></a><a id="idm225464644960" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s2-x86-starting-booting"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.1.1. Booting the Installation Program on x86, AMD64, and Intel 64 Systems</h3></div></div></div><a id="idm219150645696" class="indexterm"></a><a id="idm219147119152" class="indexterm"></a><div class="para">
You can boot the installation program using any one of the following media (depending upon what your system can support):
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<span class="emphasis"><em>Fedora DVD</em></span> — Your machine supports a bootable DVD drive and you have the Fedora installation DVD.
@@ -791,7 +791,7 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
This option runs an exhaustive test on the memory on your system. For more information, refer to <a class="xref" href="#sect-boot-options-memtest">Section 11.3.1, “Loading the Memory (RAM) Testing Mode”</a>.
</div></dd><dt class="varlistentry"><span class="term">Boot from local drive</span></dt><dd><div class="para">
This option boots the system from the first installed disk. If you booted this disc accidentally, use this option to boot from the hard disk immediately without starting the installer.
- </div></dd></dl></div></div><div class="section" id="s2-x86-starting-bootopts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.1.3. Additional Boot Options</h3></div></div></div><a id="idm225464343120" class="indexterm"></a><div class="para">
+ </div></dd></dl></div></div><div class="section" id="s2-x86-starting-bootopts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.1.3. Additional Boot Options</h3></div></div></div><a id="idm219163866528" class="indexterm"></a><div class="para">
While it is easiest to boot using a DVD and perform a graphical installation, sometimes there are installation scenarios where booting in a different manner may be needed. This section discusses additional boot options available for Fedora.
</div><div class="para">
To pass options to the boot loader on an x86, AMD64, or Intel 64 system, press the <span class="keycap"><strong>Esc</strong></span> key at boot time. The <code class="prompt">boot:</code> prompt appears, at which you can use the boot loader options described below.
@@ -800,23 +800,23 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
</div><div class="note" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
Boot options are not available during live image installations.
</div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <a id="idm225435067664" class="indexterm"></a>
- <a id="idm225461041296" class="indexterm"></a>
+ <a id="idm219144924992" class="indexterm"></a>
+ <a id="idm219176141776" class="indexterm"></a>
To perform a text mode installation, at the installation boot prompt, type:
</div><pre class="screen">
<strong class="userinput"><code>linux text</code></strong></pre></li><li class="listitem"><div class="para">
- <a id="idm225463896048" class="indexterm"></a>
- <a id="idm225404889712" class="indexterm"></a>
- <a id="idm225475356480" class="indexterm"></a>
+ <a id="idm219175249104" class="indexterm"></a>
+ <a id="idm219134054976" class="indexterm"></a>
+ <a id="idm219140467648" class="indexterm"></a>
ISO images have an SHA256 checksum embedded in them. To test the checksum integrity of an ISO image, at the installation boot prompt, type:
</div><pre class="screen">
<strong class="userinput"><code>linux rd.live.check</code></strong></pre><div class="para">
This checksum operation can be performed on any Fedora DVD. It is strongly recommended to perform this operation on any Fedora DVD that was created from downloaded ISO images. This command works with the DVD, hard drive ISO, and NFS ISO installation methods.
</div></li><li class="listitem"><div class="para">
- <a id="idm225464581616" class="indexterm"></a>
- <a id="idm225447284192" class="indexterm"></a>
- <a id="idm225441127344" class="indexterm"></a>
- <a id="idm225460779088" class="indexterm"></a>
+ <a id="idm219115121888" class="indexterm"></a>
+ <a id="idm219140051920" class="indexterm"></a>
+ <a id="idm219176771152" class="indexterm"></a>
+ <a id="idm219201147024" class="indexterm"></a>
If you need to perform the installation in <em class="firstterm">serial mode</em>, type the following command:
</div><pre class="screen">
<strong class="userinput"><code>linux console=<em class="replaceable"><code><device></code></em></code></strong></pre><div class="para">
@@ -829,7 +829,7 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
</div><pre class="screen">
<code class="command">linux console=ttyS0 utf8</code></pre></li></ul></div><div class="section" id="s3-x86-starting-kernelopts"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.1.3.1. Kernel Options</h4></div></div></div><div class="para">
Options can also be passed to the kernel. For example, to apply updates for the anaconda installation program from a USB storage device enter:
- </div><a id="idm225477286128" class="indexterm"></a><pre class="screen">
+ </div><a id="idm219176973744" class="indexterm"></a><pre class="screen">
<strong class="userinput"><code>linux updates</code></strong></pre><div class="para">
For text mode installations, use:
</div><pre class="screen">
@@ -843,7 +843,7 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
For more information on kernel options refer to <a class="xref" href="#ap-admin-options">Chapter 11, <em>Boot Options</em></a>.
</div></div></div></div><div class="section" id="sn-booting-from-pxe-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.2. Booting from the Network using PXE </h2></div></div></div><div class="para">
To boot with
- <a id="idm225439538960" class="indexterm"></a>
+ <a id="idm219179719344" class="indexterm"></a>
PXE, you need a properly configured server, and a network interface in your computer that supports PXE. For information on how to configure a PXE server, refer to <a class="xref" href="#ap-install-server">Chapter 13, <em>Setting Up an Installation Server</em></a>.
</div><div class="para">
Configure the computer to boot from the network interface. This option is in the BIOS, and may be labeled <code class="option">Network Boot</code> or <code class="option">Boot Services</code>. Once you properly configure PXE booting, the computer can boot the Fedora installation system without any other media.
@@ -866,15 +866,15 @@ APPEND ksdevice=bootif</pre><div class="para">
This option causes the installer to use the first network device it finds that is linked to a network switch.
</div></div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-Installation_Phase_2-x86" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 8. Configuring Installation Source</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-installationmethod-x86">8.1. Installation Method</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-begininstall-cd-inst-x86">8.1.1. Installing from DVD</a></span></dt><dt><span class="section"><a href="#s1-begininstall-hd-x86">8.1.2. Installing from a Hard Drive</a></span></dt><dt><span class="section"><a href="#s1-begininstall-nfs-x86">8.1.3. Installing via NFS</a></span></dt><dt><span class="section"><a href="#s1-begininstall-url-x86">8.1.4. Installing via FTP or HTTP</a></span></dt></dl></dd></dl></div><div class="para">
Before the graphical installation program starts, you may need to configure the installation source depending on the method you are using.
-</div><div xml:lang="en-US" class="section" id="s1-installationmethod-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.1. Installation Method</h2></div></div></div><a id="idm225457069680" class="indexterm"></a><div class="para">
+</div><div xml:lang="en-US" class="section" id="s1-installationmethod-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.1. Installation Method</h2></div></div></div><a id="idm219169823104" class="indexterm"></a><div class="para">
If you are installing from DVD, additional configuration will not be required unless the DVD drive is not detected. If you booted the installation from minimal boot media, use a boot prompt to select an installation method.
- </div><div xml:lang="en-US" class="section" id="s1-begininstall-cd-inst-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.1.1. Installing from DVD</h3></div></div></div><a id="idm225494691408" class="indexterm"></a><a id="idm225471020720" class="indexterm"></a><a id="idm225435517712" class="indexterm"></a><a id="idm225445304496" class="indexterm"></a><a id="idm225448125056" class="indexterm"></a><a id="idm225464833024" class="indexterm"></a><div class="para">
+ </div><div xml:lang="en-US" class="section" id="s1-begininstall-cd-inst-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.1.1. Installing from DVD</h3></div></div></div><a id="idm219178270544" class="indexterm"></a><a id="idm219166799264" class="indexterm"></a><a id="idm219145516128" class="indexterm"></a><a id="idm219167631344" class="indexterm"></a><a id="idm219183081296" class="indexterm"></a><a id="idm219202989040" class="indexterm"></a><div class="para">
To install Fedora from a DVD, place the DVD in your DVD drive and boot your system from the DVD. Even if you booted from alternative media, you can still install Fedora from DVD media.
</div><div class="para">
The installation program then probes your system and attempts to identify your DVD drive. It starts by looking for an IDE (also known as an ATAPI) DVD drive.
- </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><a id="idm225452428944" class="indexterm"></a><a id="idm225451007680" class="indexterm"></a><div class="para">
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><a id="idm219173558624" class="indexterm"></a><a id="idm219173291200" class="indexterm"></a><div class="para">
To abort the installation process at this time, reboot your machine and then eject the boot media. You can safely cancel the installation at any point before you select <span class="guibutton"><strong>Begin Installation</strong></span> on the Installation Summary Menu. Refer to <a class="xref" href="#Begin_installation-x86">Section 9.15, “Begin installation”</a> for more information.
- </div></div></div><a id="idm225465528432" class="indexterm"></a><div class="para">
+ </div></div></div><a id="idm219177789680" class="indexterm"></a><div class="para">
If your DVD drive is not detected, and it is a SCSI DVD, the installation program prompts you to choose a SCSI driver. Choose the driver that most closely resembles your adapter. You may specify options for the driver if necessary; however, most drivers detect your SCSI adapter automatically.
</div><div class="para">
If you booted the installer from other media and wish to use a DVD as your installation source, use the following boot option:
@@ -882,7 +882,7 @@ APPEND ksdevice=bootif</pre><div class="para">
<strong class="userinput"><code>linux repo=cdrom:<em class="replaceable"><code>device</code></em></code></strong></pre>
</div><div class="para">
If you later encounter problems with the installer, you should reboot and perform the media check by running the boot option <code class="command">linux rd.live.check</code> before seeking support.
- </div></div><div xml:lang="en-US" class="section" id="s1-begininstall-hd-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.1.2. Installing from a Hard Drive</h3></div></div></div><a id="idm225448157472" class="indexterm"></a><a id="idm225412146656" class="indexterm"></a><a id="idm225492458688" class="indexterm"></a><a id="idm225445030688" class="indexterm"></a><a id="idm225458105648" class="indexterm"></a><a id="idm225445323408" class="indexterm"></a><a id="idm225439413920" class="indexterm"></a><a id="idm225455506272" class="indexterm"></a><a id="idm225463321952" class="indexterm"></a><a id="idm225462912896" class="indexterm"></a><div class="para">
+ </div></div><div xml:lang="en-US" class="section" id="s1-begininstall-hd-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.1.2. Installing from a Hard Drive</h3></div></div></div><a id="idm219152189536" class="indexterm"></a><a id="idm219128375232" class="indexterm"></a><a id="idm219173535008" class="indexterm"></a><a id="idm219180454480" class="indexterm"></a><a id="idm219176344992" class="indexterm"></a><a id="idm219088022752" class="indexterm"></a><a id="idm219183883424" class="indexterm"></a><a id="idm219198872368" class="indexterm"></a><a id="idm219182625600" class="indexterm"></a><a id="idm219184395264" class="indexterm"></a><div class="para">
To specify a partition from which to install Fedora, use the <code class="command">linux repo=</code> boot option:
<pre class="screen">
<strong class="userinput"><code>linux repo=hd:<em class="replaceable"><code>device</code></em></code></strong></pre>
@@ -920,7 +920,7 @@ APPEND ksdevice=bootif</pre><div class="para">
An entry without a leading slash may cause the installation to fail.
</div></div></div><div class="para">
After entering the <code class="command">linux repo=</code> boot command, proceed with <a class="xref" href="#ch-guimode-x86">Chapter 9, <em>Using the Fedora installer</em></a>.
- </div></div><div xml:lang="en-US" class="section" id="s1-begininstall-nfs-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.1.3. Installing via NFS</h3></div></div></div><a id="idm225429688480" class="indexterm"></a><a id="idm225455361680" class="indexterm"></a><a id="idm225472924928" class="indexterm"></a><a id="idm225430308576" class="indexterm"></a><div class="para">
+ </div></div><div xml:lang="en-US" class="section" id="s1-begininstall-nfs-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.1.3. Installing via NFS</h3></div></div></div><a id="idm219168575376" class="indexterm"></a><a id="idm219182321760" class="indexterm"></a><a id="idm219175609888" class="indexterm"></a><a id="idm219132222768" class="indexterm"></a><div class="para">
To specify an installation source for Fedora accessible by NFS, use the <code class="command">linux repo=</code> boot option. To specify an expanded tree of installation files, type:
<pre class="screen">
<strong class="userinput"><code>linux repo=nfs:<em class="replaceable"><code>options</code></em>:<em class="replaceable"><code>server</code></em>:/<em class="replaceable"><code>path</code></em></code></strong></pre>
@@ -942,7 +942,7 @@ APPEND ksdevice=bootif</pre><div class="para">
If you followed the setup described in <a class="xref" href="#s1-steps-network-installs-x86-nfs">Section 5.1.2, “Preparing for an NFS installation”</a>, the exported directory is the one that you specified as <code class="filename"><em class="replaceable"><code>publicly_available_directory</code></em></code>.
</div></li></ul></div><div class="para">
After entering the <code class="command">linux repo=</code> command, proceed with <a class="xref" href="#ch-guimode-x86">Chapter 9, <em>Using the Fedora installer</em></a>.
- </div></div><div xml:lang="en-US" class="section" id="s1-begininstall-url-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.1.4. Installing via FTP or HTTP</h3></div></div></div><a id="idm225458091632" class="indexterm"></a><a id="idm225469135232" class="indexterm"></a><a id="idm225476680080" class="indexterm"></a><a id="idm225377816448" class="indexterm"></a><a id="idm225466408624" class="indexterm"></a><a id="idm225440413984" class="indexterm"></a><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important — you must specify the protocol</h2></div><div class="admonition"><div class="para">
+ </div></div><div xml:lang="en-US" class="section" id="s1-begininstall-url-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.1.4. Installing via FTP or HTTP</h3></div></div></div><a id="idm219178160880" class="indexterm"></a><a id="idm219132137104" class="indexterm"></a><a id="idm219177855104" class="indexterm"></a><a id="idm219088275568" class="indexterm"></a><a id="idm219176590896" class="indexterm"></a><a id="idm219180418272" class="indexterm"></a><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important — you must specify the protocol</h2></div><div class="admonition"><div class="para">
When you provide a URL to an installation source, you must explicitly specify <code class="literal">http://</code> or <code class="literal">ftp://</code> as the protocol.
</div></div></div><div class="para">
To specify an installation source for Fedora that is available over the Internet, use the <code class="command">linux repo=</code> boot option:
@@ -962,9 +962,9 @@ APPEND ksdevice=bootif</pre><div class="para">
<code class="literal">http://install:fedora20pw@name.example.com/fedora/linux/releases/20/Fedora/…</code>
</div><div class="para">
After entering the <code class="command">linux repo=</code> command, proceed with <a class="xref" href="#ch-guimode-x86">Chapter 9, <em>Using the Fedora installer</em></a>.
- </div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-guimode-x86" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 9. Using the Fedora installer</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#idm225495428512">9.1. The Text Mode Installation Program User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="#idm225456935312">9.1.1. Using the Keyboard to Navigate</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-guimode-interface-x86">9.2. The Graphical Installation Program User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-adminoptions-screenshots">9.2.1. Screenshots during installation</a></span></dt><dt><span class="section"><a href="#sn-guimode-virtual-consoles-x86">9.2.2. A Note about Virtual Consoles</a></span></dt></dl></dd><dt><span class="section"><a href="#language-selection-x86">9.3. Language Selection</a></span></dt><dt><span
class="section"><a href="#install-hub-x86">9.4. The Installation Summary Menu </a></span></dt><dt><span class="section"><a href="#s1-timezone-x86">9.5. Date and time</a></span></dt><dt><span class="section"><a href="#sn-keyboard-x86">9.6. Keyboard Configuration</a></span></dt><dt><span class="section"><a href="#language-support-x86">9.7. Language Support</a></span></dt><dt><span class="section"><a href="#installation-source-x86">9.8. Installation Source</a></span></dt><dd><dl><dt><span class="section"><a href="#idm225473537472">9.8.1. Installing from Additional Repositories</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-Netconfig-x86">9.9. Network Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-Netconfig-x86-edit">9.9.1. Edit Network Connections</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-pkgselection-x86">9.10. Software Selection</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-mandatory-service
s-x86">9.10.1. Core Network Services </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-diskpartsetup-x86">9.11. Storage and partitioning</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Storage_Device_Selection_Screen-x86">9.11.1. Specialized and Networked Disks</a></span></dt><dt><span class="section"><a href="#s1-x86-bootloader">9.11.2. x86, AMD64, and Intel 64 Boot Loader Installation</a></span></dt></dl></dd><dt><span class="section"><a href="#encrypt-x86">9.12. Encrypt Partitions </a></span></dt><dt><span class="section"><a href="#reclaim_space-x86">9.13. Reclaim disk space</a></span></dt><dt><span class="section"><a href="#s1-diskpartitioning-x86">9.14. Creating a Custom Partition Layout</a></span></dt><dd><dl><dt><span class="section"><a href="#Adding_Partitions-x86">9.14.1. Adding and Configuring Partitions</a></span></dt><dt><span class="section"><a href="#Create_Software_RAID-x86">9.14.2. Create Software RAID </a></span></dt><dt><sp
an class="section"><a href="#Create_LVM-x86">9.14.3. Create LVM Logical Volume </a></span></dt><dt><span class="section"><a href="#Create_Btrfs-x86">9.14.4. Create a Btrfs subvolume</a></span></dt><dt><span class="section"><a href="#s2-diskpartrecommend-x86">9.14.5. Recommended Partitioning Scheme</a></span></dt></dl></dd><dt><span class="section"><a href="#Begin_installation-x86">9.15. Begin installation</a></span></dt><dt><span class="section"><a href="#s1-progresshub-x86">9.16. The Configuration Menu and Progress Screen</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-account_configuration-x86">9.16.1. Set the Root Password</a></span></dt><dt><span class="section"><a href="#sn-firstboot-systemuser">9.16.2. User Creation</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-complete-x86">9.17. Installation Complete</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-gnome-initial-setup">9.17.1. GNOME Initial Setup</a></span></dt><dt><sp
an class="section"><a href="#sect-other-initial-setup">9.17.2. Initial Setup in Other Desktop Environments</a></span></dt></dl></dd></dl></div><a id="idm225459333072" class="indexterm"></a><div class="para">
+ </div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-guimode-x86" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 9. Using the Fedora installer</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#idm219199222144">9.1. The Text Mode Installation Program User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="#idm219174347776">9.1.1. Using the Keyboard to Navigate</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-guimode-interface-x86">9.2. The Graphical Installation Program User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-adminoptions-screenshots">9.2.1. Screenshots during installation</a></span></dt><dt><span class="section"><a href="#sn-guimode-virtual-consoles-x86">9.2.2. A Note about Virtual Consoles</a></span></dt></dl></dd><dt><span class="section"><a href="#language-selection-x86">9.3. Language Selection</a></span></dt><dt><span
class="section"><a href="#install-hub-x86">9.4. The Installation Summary Menu </a></span></dt><dt><span class="section"><a href="#s1-timezone-x86">9.5. Date and time</a></span></dt><dt><span class="section"><a href="#sn-keyboard-x86">9.6. Keyboard Configuration</a></span></dt><dt><span class="section"><a href="#language-support-x86">9.7. Language Support</a></span></dt><dt><span class="section"><a href="#installation-source-x86">9.8. Installation Source</a></span></dt><dd><dl><dt><span class="section"><a href="#idm219180754816">9.8.1. Installing from Additional Repositories</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-Netconfig-x86">9.9. Network Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-Netconfig-x86-edit">9.9.1. Edit Network Connections</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-pkgselection-x86">9.10. Software Selection</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-mandatory-service
s-x86">9.10.1. Core Network Services </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-diskpartsetup-x86">9.11. Storage and partitioning</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Storage_Device_Selection_Screen-x86">9.11.1. Specialized and Networked Disks</a></span></dt><dt><span class="section"><a href="#s1-x86-bootloader">9.11.2. x86, AMD64, and Intel 64 Boot Loader Installation</a></span></dt></dl></dd><dt><span class="section"><a href="#encrypt-x86">9.12. Encrypt Partitions </a></span></dt><dt><span class="section"><a href="#reclaim_space-x86">9.13. Reclaim disk space</a></span></dt><dt><span class="section"><a href="#s1-diskpartitioning-x86">9.14. Creating a Custom Partition Layout</a></span></dt><dd><dl><dt><span class="section"><a href="#Adding_Partitions-x86">9.14.1. Adding and Configuring Partitions</a></span></dt><dt><span class="section"><a href="#Create_Software_RAID-x86">9.14.2. Create Software RAID </a></span></dt><dt><sp
an class="section"><a href="#Create_LVM-x86">9.14.3. Create LVM Logical Volume </a></span></dt><dt><span class="section"><a href="#Create_Btrfs-x86">9.14.4. Create a Btrfs subvolume</a></span></dt><dt><span class="section"><a href="#s2-diskpartrecommend-x86">9.14.5. Recommended Partitioning Scheme</a></span></dt><dt><span class="section"><a href="#s1-diskpartitioning-confirm">9.14.6. Review and Confirm Custom Partition Layout</a></span></dt></dl></dd><dt><span class="section"><a href="#Begin_installation-x86">9.15. Begin installation</a></span></dt><dt><span class="section"><a href="#s1-progresshub-x86">9.16. The Configuration Menu and Progress Screen</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-account_configuration-x86">9.16.1. Set the Root Password</a></span></dt><dt><span class="section"><a href="#sn-firstboot-systemuser">9.16.2. User Creation</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-complete-x86">9.17. Installation Complete</a><
/span></dt><dd><dl><dt><span class="section"><a href="#sect-gnome-initial-setup">9.17.1. GNOME Initial Setup</a></span></dt><dt><span class="section"><a href="#sect-other-initial-setup">9.17.2. Initial Setup in Other Desktop Environments</a></span></dt></dl></dd></dl></div><a id="idm219147184640" class="indexterm"></a><div class="para">
This chapter describes an installation using the graphical user interface of <span class="application"><strong>anaconda</strong></span>.
-</div><div xml:lang="en-US" class="section" id="idm225495428512" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm225495428512">9.1. The Text Mode Installation Program User Interface</h2></div></div></div><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important — Graphical installation recommended</h2></div><div class="admonition"><div class="para">
+</div><div xml:lang="en-US" class="section" id="idm219199222144" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm219199222144">9.1. The Text Mode Installation Program User Interface</h2></div></div></div><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important — Graphical installation recommended</h2></div><div class="admonition"><div class="para">
We recommend that you install Fedora using the graphical interface. If you are installing Fedora on a system that lacks a graphical display, consider performing the installation over a VNC connection – see <a class="xref" href="#vncwhitepaperadded">Chapter 14, <em>Installing Through VNC</em></a>. If <span class="application"><strong>anaconda</strong></span> detects that you are installing in text mode on a system where installation over a VNC connection might be possible, <span class="application"><strong>anaconda</strong></span> asks you to verify your decision to install in text mode even though your options during installation are limited.
</div><div class="para">
If your system has a graphical display, but graphical installation fails, try booting with the <code class="command">xdriver=vesa</code> option – refer to <a class="xref" href="#ap-admin-options">Chapter 11, <em>Boot Options</em></a>
@@ -990,12 +990,12 @@ APPEND ksdevice=bootif</pre><div class="para">
</div></li><li xml:lang="en-US" class="listitem" lang="en-US"><div class="para">
selecting packages during installation
</div></li></ul></div><div class="para">
- If you choose to install Fedora in text mode, you can still configure your system to use a graphical interface after installation. Refer to <a class="xref" href="#sn-switching-to-gui-login">Section 17.3, “Switching to a Graphical Login”</a> for instructions.
+ If you choose to install Fedora in text mode, you can still configure your system to use a graphical interface after installation. Refer to <a class="xref" href="#sn-switching-to-gui-login">Section 17.2, “Switching to a Graphical Login”</a> for instructions.
</div><div class="para">
To configure options not available in text mode, consider using a boot option. For example, the <code class="command">linux ip</code> option can be used to configure network settings. Refer to <a class="xref" href="#sn-bootoptions-installer">Section 11.1, “Configuring the Installation System at the Boot Menu”</a> for instructions. Alternatively, consider a kickstart installation. Refer to <a class="xref" href="#s1-kickstart2-options">Section 15.4, “Kickstart Options”</a> for available kickstart options.
</div><div class="note" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
Not every language supported in graphical installation mode is also supported in text mode. Specifically, languages written with a character set other than the Latin or Cyrillic alphabets are not available in text mode. If you choose a language written with a character set that is not supported in text mode, the installation program will present you with the English versions of the screens.
- </div></div></div><div xml:lang="en-US" class="section" id="idm225456935312" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225456935312">9.1.1. Using the Keyboard to Navigate</h3></div></div></div><a id="idm225460040368" class="indexterm"></a><a id="idm225453524208" class="indexterm"></a><div class="para">
+ </div></div></div><div xml:lang="en-US" class="section" id="idm219174347776" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm219174347776">9.1.1. Using the Keyboard to Navigate</h3></div></div></div><a id="idm219208410688" class="indexterm"></a><a id="idm219200242160" class="indexterm"></a><div class="para">
Navigation through the installation dialogs is performed through a simple set of keystrokes. To move the cursor, use the <span class="keycap"><strong>Left</strong></span>, <span class="keycap"><strong>Right</strong></span>, <span class="keycap"><strong>Up</strong></span>, and <span class="keycap"><strong>Down</strong></span> arrow keys. Use <span class="keycap"><strong>Tab</strong></span>, and <span class="keycap"><strong>Shift</strong></span>-<span class="keycap"><strong>Tab</strong></span> to cycle forward or backward through each widget on the screen. Along the bottom, most screens display a summary of available cursor positioning keys.
</div><div class="para">
To "press" a button, position the cursor over the button (using <span class="keycap"><strong>Tab</strong></span>, for example) and press <span class="keycap"><strong>Space</strong></span> or <span class="keycap"><strong>Enter</strong></span>. To select an item from a list of items, move the cursor to the item you wish to select and press <span class="keycap"><strong>Enter</strong></span>. To select an item with a checkbox, move the cursor to the checkbox and press <span class="keycap"><strong>Space</strong></span> to select an item. To deselect, press <span class="keycap"><strong>Space</strong></span> a second time.
@@ -1003,15 +1003,15 @@ APPEND ksdevice=bootif</pre><div class="para">
Pressing <span class="keycap"><strong>F12</strong></span> accepts the current values and proceeds to the next dialog; it is equivalent to pressing the <span class="guibutton"><strong>OK</strong></span> button.
</div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
Unless a dialog box is waiting for your input, do not press any keys during the installation process (doing so may result in unpredictable behavior).
- </div></div></div></div></div><div class="section" id="s1-guimode-interface-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.2. The Graphical Installation Program User Interface</h2></div></div></div><a id="idm225450437536" class="indexterm"></a><a id="idm225444506256" class="indexterm"></a><div class="para">
+ </div></div></div></div></div><div class="section" id="s1-guimode-interface-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.2. The Graphical Installation Program User Interface</h2></div></div></div><a id="idm219141659024" class="indexterm"></a><a id="idm219179287456" class="indexterm"></a><div class="para">
If you have used a <em class="firstterm">graphical user interface (GUI)</em> before, you are already familiar with this process; use your mouse to navigate the screens, click buttons, or enter text fields.
</div><div class="para">
You can also navigate through the installation using the keyboard. The <span class="keycap"><strong>Tab</strong></span> key allows you to move around the screen, the Up and Down arrow keys to scroll through lists, <span class="keycap"><strong>+</strong></span> and <span class="keycap"><strong>-</strong></span> keys expand and collapse lists, while <span class="keycap"><strong>Space</strong></span> and <span class="keycap"><strong>Enter</strong></span> selects or removes from selection a highlighted item. You can also use the <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong><em class="replaceable"><code>X</code></em></strong></span> key command combination as a way of clicking on buttons or making other screen selections, where <span class="keycap"><strong><em class="replaceable"><code>X</code></em></strong></span> is replaced with any underlined letter appearing within that screen.
-</div><div xml:lang="en-US" class="section" id="sect-adminoptions-screenshots" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.1. Screenshots during installation</h3></div></div></div><a id="idm225459769296" class="indexterm"></a><div class="para">
+</div><div xml:lang="en-US" class="section" id="sect-adminoptions-screenshots" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.1. Screenshots during installation</h3></div></div></div><a id="idm219165242432" class="indexterm"></a><div class="para">
<span class="application"><strong>Anaconda</strong></span> allows you to take screenshots during the installation process. At any time during installation, press <span class="keycap"><strong>Shift</strong></span>+<span class="keycap"><strong>Print Screen</strong></span> and <span class="application"><strong>anaconda</strong></span> will save a screenshot to <code class="filename">/root/anaconda-screenshots</code>.
</div><div class="para">
If you are performing a Kickstart installation, use the <code class="option">autostep --autoscreenshot</code> option to generate a screenshot of each step of the installation automatically. Refer to <a class="xref" href="#s1-kickstart2-file">Section 15.3, “Creating the Kickstart File”</a> for details of configuring a Kickstart file.
- </div></div><div class="section" id="sn-guimode-virtual-consoles-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.2. A Note about Virtual Consoles</h3></div></div></div><a id="idm225473443936" class="indexterm"></a><a id="idm225424208000" class="indexterm"></a><a id="idm225454240208" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="sn-guimode-virtual-consoles-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.2. A Note about Virtual Consoles</h3></div></div></div><a id="idm219162431520" class="indexterm"></a><a id="idm219183228224" class="indexterm"></a><a id="idm219141642528" class="indexterm"></a><div class="para">
The Fedora installation program offers more than the dialog boxes of the installation process. Several kinds of diagnostic messages are available to you, as well as a way to enter commands from a shell prompt. The installation program displays these messages on five <em class="firstterm">virtual consoles</em>, among which you can switch using a single keystroke combination.
</div><div class="para">
A virtual console is a shell prompt in a non-graphical environment, accessed from the physical machine, not remotely. Multiple virtual consoles can be accessed simultaneously.
@@ -1067,7 +1067,7 @@ APPEND ksdevice=bootif</pre><div class="para">
<span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>alt</strong></span>+<span class="keycap"><strong>f6</strong></span>
</td><td class="">
graphical display
- </td></tr></tbody></table></div></div><br class="table-break" /></div></div><div xml:lang="en-US" class="section" id="language-selection-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.3. Language Selection</h2></div></div></div><a id="idm225464567296" class="indexterm"></a><a id="idm225444118896" class="indexterm"></a><div class="para">
+ </td></tr></tbody></table></div></div><br class="table-break" /></div></div><div xml:lang="en-US" class="section" id="language-selection-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.3. Language Selection</h2></div></div></div><a id="idm219149648976" class="indexterm"></a><a id="idm219088110272" class="indexterm"></a><div class="para">
At the <span class="guilabel"><strong>Welcome to Fedora 20</strong></span> screen, use your mouse to select the language (for example, <span class="guilabel"><strong>English</strong></span>) you prefer to use for the installation and as the system default on the left side. On the right side, select your keyboard layout (for example, <span class="guilabel"><strong>English (United Kingdom)</strong></span>). Again, this layout will be used during the installation and it will be the default on the installed system. You can also change the keyboard layout at any time during the installation using the layout switching tool in the upper right hand corner.
</div><div class="para">
Alternatively, type your preferred language into the search box and select from the list of results.
@@ -1093,7 +1093,7 @@ APPEND ksdevice=bootif</pre><div class="para">
To cancel the installation, click <span class="guibutton"><strong>Quit</strong></span>.
</div><div class="note" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
When related background tasks are being run, certain menu items may be temporarily grayed out and unavailable.
- </div></div></div></div><div xml:lang="en-US" class="section" id="s1-timezone-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.5. Date and time</h2></div></div></div><a id="idm225466074944" class="indexterm"></a><a id="idm225455579040" class="indexterm"></a><a id="idm225404909648" class="indexterm"></a><a id="idm225442082128" class="indexterm"></a><a id="idm225477520768" class="indexterm"></a><a id="idm225477190464" class="indexterm"></a><a id="idm225419519408" class="indexterm"></a><div class="para">
+ </div></div></div></div><div xml:lang="en-US" class="section" id="s1-timezone-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.5. Date and time</h2></div></div></div><a id="idm219146771952" class="indexterm"></a><a id="idm219132337168" class="indexterm"></a><a id="idm219153688848" class="indexterm"></a><a id="idm219204639200" class="indexterm"></a><a id="idm219157473024" class="indexterm"></a><a id="idm219156510048" class="indexterm"></a><a id="idm219178657552" class="indexterm"></a><div class="para">
Select <span class="guilabel"><strong>Date and Time</strong></span> from the Installation Summary Menu.
</div><div class="para">
Set your time zone by selecting the city closest to your computer's physical location.
@@ -1115,7 +1115,7 @@ APPEND ksdevice=bootif</pre><div class="para">
Once you have made your selection, click <span class="guibutton"><strong>Done</strong></span> to return to the Installation Summary Menu.
</div><div class="note" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
To change your time zone configuration after you have completed the installation, visit the <span class="application"><strong>Date and Time</strong></span> section of the <span class="application"><strong>System Settings</strong></span> menu.
- </div></div></div></div><div xml:lang="en-US" class="section" id="sn-keyboard-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.6. Keyboard Configuration</h2></div></div></div><a id="idm225464965968" class="indexterm"></a><a id="idm225448392096" class="indexterm"></a><div class="para">
+ </div></div></div></div><div xml:lang="en-US" class="section" id="sn-keyboard-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.6. Keyboard Configuration</h2></div></div></div><a id="idm219163632832" class="indexterm"></a><a id="idm219183936768" class="indexterm"></a><div class="para">
Select <span class="guilabel"><strong>Keyboard</strong></span> from the Installation Summary Menu.
</div><div class="para">
In the left-hand pane, <span class="guilabel"><strong>English (United States)</strong></span> is listed as the keyboard layout, unless you clicked the checkbox in <a class="xref" href="#language-selection-x86">Section 9.3, “Language Selection”</a> to set the keyboard layout to the default for your selected language. If so, you may still want to select a more specific layout. For example, if you selected <span class="guilabel"><strong>French</strong></span> as the language for this installation, the layout listed in the left-hand pane will be <span class="guilabel"><strong>French (French)</strong></span>. However, you may want to change it to <span class="guilabel"><strong>French (French (Canada))</strong></span>.
@@ -1135,7 +1135,7 @@ APPEND ksdevice=bootif</pre><div class="para">
To change your keyboard configuration after you have completed the installation, visit the <span class="application"><strong>Keyboard</strong></span> (in GNOME) or <span class="application"><strong>Input Devices</strong></span> (in KDE) section of the <span class="application"><strong>System Settings</strong></span> menu.
</div></div></div><div class="para">
Fedora includes support for more than one keyboard layout for many languages. In particular, most European languages include a <code class="literal">latin1</code> option, which uses <em class="firstterm">dead keys</em> to access certain characters, such as those with diacritical marks. When you press a dead key, nothing will appear on your screen until you press another key to "complete" the character. For example, to type <code class="literal">é</code> on a latin1 keyboard layout, you would press (and release) the <span class="keycap"><strong>'</strong></span> key, and then press the <code class="literal">E</code> key. By contrast, you access this character on some other keyboards by pressing and holding down a key (such as <span class="keycap"><strong>Alt-Gr</strong></span>) while you press the <code class="literal">E</code> key. Other keyboards might have a dedicated key for this character.
- </div></div><div xml:lang="en-US" class="section" id="language-support-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.7. Language Support</h2></div></div></div><a id="idm225475362000" class="indexterm"></a><a id="idm225468260512" class="indexterm"></a><div class="para">
+ </div></div><div xml:lang="en-US" class="section" id="language-support-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.7. Language Support</h2></div></div></div><a id="idm219201746768" class="indexterm"></a><a id="idm219145507696" class="indexterm"></a><div class="para">
To install languages in addition to the one you selected in <a class="xref" href="#language-selection-x86">Section 9.3, “Language Selection”</a>, select <span class="guilabel"><strong>Language Support</strong></span> from the Installation Summary Menu.
</div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/langselection/langselection-hub-GUI.png" alt="Language Support" /><div class="longdesc"><div class="para">
The language support screen
@@ -1179,7 +1179,7 @@ APPEND ksdevice=bootif</pre><div class="para">
Choosing not to install available updates may pose a security risk to your system.
</div></div></div><div class="para">
Once you have selected your installation source, click <span class="guibutton"><strong>Done</strong></span> to return to the Installation Summary Menu.
-</div><div xml:lang="en-US" class="section" id="idm225473537472" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225473537472">9.8.1. Installing from Additional Repositories</h3></div></div></div><div class="para">
+</div><div xml:lang="en-US" class="section" id="idm219180754816" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm219180754816">9.8.1. Installing from Additional Repositories</h3></div></div></div><div class="para">
You can define additional <em class="firstterm">repositories</em> to increase the software available to your system during installation. A repository is a network location that stores software packages along with <em class="firstterm">metadata</em> that describes them. Many of the software packages used in Fedora require other software to be installed. The installer uses the metadata to ensure that these requirements are met for every piece of software you select for installation.
</div><div class="figure" xml:lang="en-US" lang="en-US"><div class="figure-contents"><div class="mediaobject"><img src="images/pkgselection/pkg-group-repos.png" width="444" alt="Adding a software repository" /><div class="longdesc"><div class="para">
Enter the details of additional software repositories.
@@ -1195,7 +1195,7 @@ APPEND ksdevice=bootif</pre><div class="para">
Once you provide information for an additional repository, the installer reads the package metadata over the network. Software that is specially marked is then included in the package listings in the <span class="guilabel"><strong>Software Selection</strong></span> section of the Installation Summary Menu (refer to <a class="xref" href="#s1-pkgselection-x86">Section 9.10, “Software Selection”</a>).
</div><div class="note" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Network Access Required</h2></div><div class="admonition"><div class="para">
If you add repositories during a non-network installation, such as from a Fedora DVD, you will need to configure a network connection via the Installation Summary Menu before the installation can proceed (refer to <a class="xref" href="#sn-Netconfig-x86">Section 9.9, “Network Configuration”</a>).
- </div></div></div></div></div><div xml:lang="en-US" class="section" id="sn-Netconfig-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.9. Network Configuration</h2></div></div></div><a id="idm225466076112" class="indexterm"></a><a id="idm225460164576" class="indexterm"></a><a id="idm225472905616" class="indexterm"></a><a id="idm225364796976" class="indexterm"></a><a id="idm225440624896" class="indexterm"></a><div class="para">
+ </div></div></div></div></div><div xml:lang="en-US" class="section" id="sn-Netconfig-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.9. Network Configuration</h2></div></div></div><a id="idm219127662112" class="indexterm"></a><a id="idm219176146848" class="indexterm"></a><a id="idm219160178912" class="indexterm"></a><a id="idm219203609936" class="indexterm"></a><a id="idm219139119664" class="indexterm"></a><div class="para">
Select <span class="guilabel"><strong>Network Configuration</strong></span> from the Installation Summary Menu.
</div><div class="para">
Detected network connections will be listed in the left-hand pane. To read more details about a connection, select it with your mouse and they will appear to the right. To activate or deactivate a network connection, move the switch in the top-right of the screen to either <span class="guilabel"><strong>ON</strong></span> or <span class="guilabel"><strong>OFF</strong></span>.
@@ -1217,7 +1217,7 @@ APPEND ksdevice=bootif</pre><div class="para">
When you have finished editing network settings, click <span class="guibutton"><strong>Save</strong></span> to save the new configuration. If you reconfigured a device that was already active during installation, you must restart the device in order to use the new configuration in the installer environment. Use the <span class="guibutton"><strong>ON/OFF</strong></span> switch on the <span class="guilabel"><strong>Network Configuration</strong></span> screen to restart the device.
</div><div class="note" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
When configuring a wireless connection that you also intend to use during the installation, you will not be prompted for a password as you would on an installed system. You must specify a password in the <span class="guilabel"><strong>Wireless Security</strong></span> tab in <span class="application"><strong>NetworkManager</strong></span>. Once you have saved the configuration, the installer will establish the wireless connection.
- </div></div></div><div xml:lang="en-US" class="section" id="idm225456097344" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm225456097344">9.9.1.1. Options common to all types of connection</h4></div></div></div><div class="para">
+ </div></div></div><div xml:lang="en-US" class="section" id="idm219166884416" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm219166884416">9.9.1.1. Options common to all types of connection</h4></div></div></div><div class="para">
Certain configuration options are common to all connection types.
</div><div class="para">
Specify a name for the connection in the <span class="guilabel"><strong>Connection name</strong></span> name field.
@@ -1231,13 +1231,13 @@ APPEND ksdevice=bootif</pre><div class="para">
Check this box to control whether a network configuration is available system-wide or not. During installation, ensure that it remains checked for any network interface that you configure.
</div></dd></dl></div><div class="note" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
The <span class="guilabel"><strong>VPN</strong></span> and <span class="guilabel"><strong>Firewall Zone</strong></span> options in the <span class="guilabel"><strong>General</strong></span> tab are not available during installation.
- </div></div></div></div><div xml:lang="en-US" class="section" id="idm225420652096" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm225420652096">9.9.1.2. The Ethernet tab</h4></div></div></div><div class="para">
+ </div></div></div></div><div xml:lang="en-US" class="section" id="idm219153934160" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm219153934160">9.9.1.2. The Ethernet tab</h4></div></div></div><div class="para">
Use the <span class="guilabel"><strong>Ethernet</strong></span> tab to specify or change the <em class="firstterm">media access control</em> (MAC) address for the network adapter. The <span class="guilabel"><strong>Device MAC address</strong></span> drop-down menu allows you to choose from a list of actual MAC addresses of deviced available on the system, while the <span class="guilabel"><strong>Cloned MAC Address</strong></span> field allows you to set an arbitrary address for this connection if necessary. Leave this field blank to use the device address.
</div><div class="para">
The MTU (<em class="firstterm">maximum transmission unit</em>) field sets the maximum unit size (in bytes) that can pass through the interface either manually or automatically.
</div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/netconfig/network-connections-ethernet.png" width="444" alt="The Ethernet tab" /><div class="longdesc"><div class="para">
The Ethernet tab
- </div></div></div></div><h6>Figure 9.10. The Ethernet tab</h6></div><br class="figure-break" /></div><div xml:lang="en-US" class="section" id="idm225463531248" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm225463531248">9.9.1.3. The 802.1x Security tab</h4></div></div></div><div class="para">
+ </div></div></div></div><h6>Figure 9.10. The Ethernet tab</h6></div><br class="figure-break" /></div><div xml:lang="en-US" class="section" id="idm219131191456" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm219131191456">9.9.1.3. The 802.1x Security tab</h4></div></div></div><div class="para">
Use the <span class="guilabel"><strong>802.1x Security</strong></span> tab to configure 802.1X <em class="firstterm">port-based network access control</em> (PNAC). Select <span class="guilabel"><strong>Use 802.1X security for this connection</strong></span> to enable access control, then specify details of your network. The configuration options include:
</div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><span class="guilabel"><strong>Authentication</strong></span></span></dt><dd><div class="para">
Choose one of the following methods of authentication:
@@ -1263,7 +1263,7 @@ APPEND ksdevice=bootif</pre><div class="para">
The password for the private key specified in the <span class="guilabel"><strong>Private key</strong></span> field. Select <span class="guilabel"><strong>Show password</strong></span> to make the password visible as you type it.
</div></dd></dl></div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/netconfig/network-connections-802.1x.png" width="444" alt="The 802.1x Security tab" /><div class="longdesc"><div class="para">
The 802.1x Security tab
- </div></div></div></div><h6>Figure 9.11. The 802.1x Security tab</h6></div><br class="figure-break" /></div><div class="section" id="idm225462078496"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm225462078496">9.9.1.4. The IPv4 Settings tab</h4></div></div></div><div class="para">
+ </div></div></div></div><h6>Figure 9.11. The 802.1x Security tab</h6></div><br class="figure-break" /></div><div class="section" id="idm219175328544"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm219175328544">9.9.1.4. The IPv4 Settings tab</h4></div></div></div><div class="para">
Use the <span class="guilabel"><strong>IPv4 Settings tab</strong></span> tab to configure the IPv4 parameters for the previously selected network connection.
</div><div class="para">
Use the <span class="guilabel"><strong>Method</strong></span> drop-down menu to specify which settings the system should attempt to obtain from a <em class="firstterm">Dynamic Host Configuration Protocol</em> (DHCP) service running on the network. Choose from the following options:
@@ -1287,7 +1287,7 @@ APPEND ksdevice=bootif</pre><div class="para">
Deselect the <span class="guilabel"><strong>Require IPv4 addressing for this connection to complete</strong></span> check box to allow the system to make this connection on an IPv6-enabled network if IPv4 configuration fails but IPv6 configuration succeeds.
</div><div class="figure" xml:lang="en-US" lang="en-US"><div class="figure-contents"><div class="mediaobject"><img src="images/netconfig/network-connections-ipv4-manual.png" width="444" alt="The IPv4 Settings tab" /><div class="longdesc"><div class="para">
The IPv4 Settings tab
- </div></div></div></div><h6>Figure 9.12. The IPv4 Settings tab</h6></div><br class="figure-break" /><div xml:lang="en-US" class="section" id="idm225453255392" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="idm225453255392">9.9.1.4.1. Editing IPv4 routes</h5></div></div></div><div class="para">
+ </div></div></div></div><h6>Figure 9.12. The IPv4 Settings tab</h6></div><br class="figure-break" /><div xml:lang="en-US" class="section" id="idm219165577696" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="idm219165577696">9.9.1.4.1. Editing IPv4 routes</h5></div></div></div><div class="para">
Fedora configures a number of routes automatically based on the IP addresses of a device. To edit additional routes, click the <span class="guibutton"><strong>Routes</strong></span> button. The <span class="guilabel"><strong>Editing IPv4 routes</strong></span> dialog appears.
</div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/netconfig/network-connections-ipv4-manual-routes.png" width="444" alt="The Editing IPv4 Routes dialog" /><div class="longdesc"><div class="para">
The Editing IPv4 Routes dialog
@@ -1297,7 +1297,7 @@ APPEND ksdevice=bootif</pre><div class="para">
Select <span class="guibutton"><strong>Ignore automatically obtained routes</strong></span> to make the interface use only the routes specified for it here.
</div><div class="para">
Select <span class="guibutton"><strong>Use this connection only for resources on its network</strong></span> to restrict connections only to the local network. Unlike additional routes added in this dialog, this setting will be transferred to the installed system and applies to the entire connection. It can be selected even if no additional routes have been configured.
- </div></div></div><div xml:lang="en-US" class="section" id="idm225475965568" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm225475965568">9.9.1.5. The IPv6 Settings tab</h4></div></div></div><div class="para">
+ </div></div></div><div xml:lang="en-US" class="section" id="idm219166879952" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm219166879952">9.9.1.5. The IPv6 Settings tab</h4></div></div></div><div class="para">
Use the <span class="guilabel"><strong>IPv6 Settings tab</strong></span> tab to configure the IPv6 parameters for the previously selected network connection.
</div><div class="para">
Use the <span class="guilabel"><strong>Method</strong></span> drop-down menu to specify which settings the system should attempt to obtain from a <em class="firstterm">Dynamic Host Configuration Protocol</em> (DHCP) service running on the network. Choose from the following options:
@@ -1321,7 +1321,7 @@ APPEND ksdevice=bootif</pre><div class="para">
Deselect the <span class="guilabel"><strong>Require IPv6 addressing for this connection to complete</strong></span> check box to allow the system to make this connection on an IPv4-enabled network if IPv6 configuration fails but IPv4 configuration succeeds.
</div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/netconfig/network-connections-ipv6-ignore.png" width="444" alt="The IPv6 Settings tab" /><div class="longdesc"><div class="para">
The IPv6 Settings tab
- </div></div></div></div><h6>Figure 9.14. The IPv6 Settings tab</h6></div><br class="figure-break" /><div class="section" id="idm225463273280"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="idm225463273280">9.9.1.5.1. Editing IPv6 routes</h5></div></div></div><div class="para">
+ </div></div></div></div><h6>Figure 9.14. The IPv6 Settings tab</h6></div><br class="figure-break" /><div class="section" id="idm219168919008"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="idm219168919008">9.9.1.5.1. Editing IPv6 routes</h5></div></div></div><div class="para">
Fedora configures a number of routes automatically based on the IP addresses of a device. To edit additional routes, click the <span class="guibutton"><strong>Routes</strong></span> button. The <span class="guilabel"><strong>Editing IPv6 routes</strong></span> dialog appears.
</div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/netconfig/network-connections-ipv6-manual-routes.png" width="444" alt="The Editing IPv6 Routes dialog" /><div class="longdesc"><div class="para">
The Editing IPv6 Routes dialog
@@ -1329,8 +1329,8 @@ APPEND ksdevice=bootif</pre><div class="para">
Click <span class="guibutton"><strong>Add</strong></span> to add the IP address, netmask, gateway address, and metric for a new static route.
</div><div class="para">
Select <span class="guibutton"><strong>Use this connection only for resources on its network</strong></span> to restrict connections only to the local network.
- </div></div></div></div></div><div xml:lang="en-US" class="section" id="s1-pkgselection-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.10. Software Selection</h2></div></div></div><a id="idm225440152208" class="indexterm"></a><a id="idm225441805360" class="indexterm"></a><a id="idm225440199744" class="indexterm"></a><a id="idm225435385248" class="indexterm"></a><a id="idm225441981072" class="indexterm"></a><a id="idm225439299120" class="indexterm"></a><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Installing in text mode</h2></div><div class="admonition"><div class="para">
- If you install Fedora in text mode, you cannot make package selections. The installer automatically selects packages only from the base and core groups. These packages are sufficient to ensure that the system is operational at the end of the installation process, ready to install updates and new packages. To change the package selection, complete the installation, then use the <span class="application"><strong>Add/Remove Software</strong></span> application to make desired changes.
+ </div></div></div></div></div><div xml:lang="en-US" class="section" id="s1-pkgselection-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.10. Software Selection</h2></div></div></div><a id="idm219129580720" class="indexterm"></a><a id="idm219140416880" class="indexterm"></a><a id="idm219200995888" class="indexterm"></a><a id="idm219134162640" class="indexterm"></a><a id="idm219130121104" class="indexterm"></a><a id="idm219156825456" class="indexterm"></a><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Installing in text mode</h2></div><div class="admonition"><div class="para">
+ If you install Fedora in text mode, you cannot make package selections. The installer automatically selects packages only from the base and core groups. These packages are sufficient to ensure that the system is operational at the end of the installation process, ready to install updates and new packages. To change the package selection, complete the installation, then use the <span class="application"><strong>yum</strong></span> utiliy to make desired changes.
</div></div></div><div class="figure" id="fig-pkgselection-group-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/pkgselection/pkg-group.png" alt="Software Selection" /><div class="longdesc"><div class="para">
Choose which environment and add-ons you want to install.
</div></div></div></div><h6>Figure 9.16. Software Selection</h6></div><br class="figure-break" /><div class="para">
@@ -1359,8 +1359,8 @@ APPEND ksdevice=bootif</pre><div class="para">
This option provides the <span class="application"><strong>Apache</strong></span> web server.
</div></dd><dt class="varlistentry"><span class="term">Infrastructure Server</span></dt><dd><div class="para">
This option provides a server for operating network infrastructure services.
- </div></dd><dt class="varlistentry"><span class="term">Basic X Window System</span></dt><dd><div class="para">
- This option provides the X Window System without a full graphical desktop environment.
+ </div></dd><dt class="varlistentry"><span class="term">Basic Desktop</span></dt><dd><div class="para">
+ This option provides the X Window System without a full graphical desktop environment. Optionally, you can select a window manager.
</div></dd><dt class="varlistentry"><span class="term">Minimal Install</span></dt><dd><div class="para">
This option provides only the packages essential to run Fedora. A minimal installation provides the basis for a single-purpose server or desktop appliance and maximizes performance and security on such an installation.
</div></dd></dl></div><div class="note" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
@@ -1376,9 +1376,7 @@ APPEND ksdevice=bootif</pre><div class="para">
</div><div class="section" id="sn-mandatory-services-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.10.1. Core Network Services </h3></div></div></div><div class="para">
All Fedora installations include the following network services:
</div><div xml:lang="en-US" class="itemizedlist" lang="en-US"><ul><li class="listitem"><div class="para">
- centralized logging through syslog
- </div></li><li class="listitem"><div class="para">
- email through SMTP (Simple Mail Transfer Protocol)
+ centralized logging through the <span class="application"><strong>systemd</strong></span> journal
</div></li><li class="listitem"><div class="para">
network file sharing through NFS (Network File System)
</div></li><li class="listitem"><div class="para">
@@ -1397,12 +1395,12 @@ APPEND ksdevice=bootif</pre><div class="para">
Some automated processes on your Fedora system use the email service to send reports and messages to the system administrator. By default, the email, logging, and printing services do not accept connections from other systems. Fedora installs the NFS sharing, HTTP, and VNC components without enabling those services.
</div><div class="para">
You may configure your Fedora system after installation to offer email, file sharing, logging, printing and remote desktop access services. The SSH service is enabled by default. You may use NFS to access files on other systems without enabling the NFS sharing service.
-</div></div></div><div xml:lang="en-US" class="section" id="s1-diskpartsetup-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.11. Storage and partitioning</h2></div></div></div><a id="idm225473217168" class="indexterm"></a><a id="idm225498547392" class="indexterm"></a><a id="idm225444312528" class="indexterm"></a><a id="idm225445299696" class="indexterm"></a><div class="warning" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Warning — Back up your data</h2></div><div class="admonition"><div class="para">
+</div></div></div><div xml:lang="en-US" class="section" id="s1-diskpartsetup-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.11. Storage and partitioning</h2></div></div></div><a id="idm219183595456" class="indexterm"></a><a id="idm219170079952" class="indexterm"></a><a id="idm219134855392" class="indexterm"></a><a id="idm219171324752" class="indexterm"></a><div class="warning" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Warning — Back up your data</h2></div><div class="admonition"><div class="para">
It is always a good idea to back up any data that you have on your systems. For example, if you are upgrading or creating a dual-boot system, you should back up any data you wish to keep on your storage devices. Mistakes do happen and can result in the loss of all your data.
</div></div></div><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important — Installing in text mode</h2></div><div class="admonition"><div class="para">
If you install Fedora in text mode, you can only use the default partitioning schemes described in this section. You cannot add or remove partitions or file systems beyond those that the installer automatically adds or removes. If you require a customized layout at installation time, you should perform a graphical installation over a VNC connection or a kickstart installation.
</div><div class="para">
- Furthermore, advanced options such as LVM, encrypted filesystems, and resizable filesystems are available only in graphical mode and kickstart.
+ Furthermore, advanced options such as encrypted filesystems and resizable filesystems are available only in graphical mode and kickstart.
</div></div></div><div class="important"><div class="admonition_header"><h2>Important — Booting from RAIDs</h2></div><div class="admonition"><div class="para">
If you have a RAID card, be aware that some BIOSes do not support booting from the RAID card. In cases such as these, the <code class="filename">/boot/</code> partition must be created on a partition outside of the RAID array, such as on a separate hard drive. An internal hard drive is necessary to use for partition creation with problematic RAID cards.
</div><div class="para">
@@ -1469,9 +1467,7 @@ APPEND ksdevice=bootif</pre><div class="para">
<span class="guilabel"><strong>BTRFS</strong></span> (B-Tree File System, as described in <a class="xref" href="#s3-diskpartitioning-file-x86">Section 9.14.1.1, “File System Types”</a>)
</div></li><li class="listitem"><div class="para">
<span class="guilabel"><strong>LVM</strong></span> (Logical Volume Management, as described in <a class="xref" href="#sn-partitioning-lvm">Appendix D, <em>Understanding LVM</em></a>. This is the default scheme.)
- </div></li></ul></div><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important — chain loading</h2></div><div class="admonition"><a id="idm225444464848" class="indexterm"></a><div class="para">
- To configure the Fedora boot loader to <em class="firstterm">chain load</em> from a different boot loader, you must specify the boot drive manually by selecting <span class="guilabel"><strong>Full disk summary and options</strong></span> from the <span class="guilabel"><strong>Installation Destination</strong></span> screen. Refer to <a class="xref" href="#s1-x86-bootloader">Section 9.11.2, “x86, AMD64, and Intel 64 Boot Loader Installation”</a> for instructions on specifying a boot drive.
- </div></div></div><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important — Mixing multipath and non-multipath devices</h2></div><div class="admonition"><a id="idm225477474560" class="indexterm"></a><div class="para">
+ </div></li></ul></div><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important — Mixing multipath and non-multipath devices</h2></div><div class="admonition"><a id="idm219182670720" class="indexterm"></a><div class="para">
When you install Fedora on a system with multipath and non-multipath storage devices, the automatic partitioning layout in the installer might create volume groups that contain a mix of multipath and non-multipath devices. This defeats the purpose of multipath storage.
</div><div class="para">
We advise that you select only multipath or only non-multipath devices on the <span class="guilabel"><strong>Installation Destination</strong></span> screen. Alternatively, proceed to manual partitioning (refer to <a class="xref" href="#s1-diskpartitioning-x86">Section 9.14, “Creating a Custom Partition Layout”</a>.
@@ -1503,9 +1499,7 @@ APPEND ksdevice=bootif</pre><div class="para">
Each device is presented on a separate row, with a checkbox to its left. Click the checkbox to make a device available during the installation process, or click the <em class="firstterm">radio button</em> at the left of the column headings to select or deselect all the devices listed in a particular screen. Later in the installation process, you can choose to install Fedora onto any of the devices selected here, and can choose to automatically mount any of the other devices selected here as part of the installed system.
</div><div class="para">
Note that the devices that you select here are not automatically erased by the installation process. Selecting a device on this screen does not, in itself, place data stored on the device at risk. Note also that any devices that you do not select here to form part of the installed system can be added to the system after installation by modifying the <code class="filename">/etc/fstab</code> file.
-</div><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important — chain loading</h2></div><div class="admonition"><a id="idm225452716096" class="indexterm"></a><div class="para">
- Any storage devices that you do not select on this screen are hidden from <span class="application"><strong>anaconda</strong></span> entirely. To <em class="firstterm">chain load</em> the Fedora boot loader from a different boot loader, select all the devices presented in this screen.
- </div></div></div><div class="para">
+</div><div class="para">
When you have selected the storage devices to make available during installation, click <span class="guibutton"><strong>Done</strong></span> to return to the <span class="guilabel"><strong>Installation Destination</strong></span> screen.
</div><div xml:lang="en-US" class="section" id="s1-advanced-storage-iSCSI-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.11.1.1. Add an iSCSI target</h4></div></div></div><div class="para">
To use iSCSI storage devices for the installation, <span class="application"><strong>anaconda</strong></span> must be able to <em class="firstterm">discover</em> them as iSCSI targets and be able to create an iSCSI <em class="firstterm">session</em> to access them. Each of these steps might require a username and password for <em class="firstterm">CHAP</em> (Challenge Handshake Authentication Protocol) authentication. Additionally, you can configure an iSCSI target to authenticate the iSCSI initiator on the system to which the target is attached (<em class="firstterm">reverse CHAP</em>), both for discovery and for the session. Used together, CHAP and reverse CHAP are called <em class="firstterm">mutual CHAP</em> or <em class="firstterm">two-way CHAP</em>. Mutual CHAP provides the greatest level of security for iSCSI connections, particularly if the username and password are different for CHAP authentication and reverse CHAP authentication.
@@ -1575,10 +1569,10 @@ APPEND ksdevice=bootif</pre><div class="para">
Configure FCoE Parameters
</div></div></div></div><h6>Figure 9.26. Configure FCoE Parameters</h6></div><br class="figure-break" /><div class="para">
<em class="firstterm">Data Center Bridging</em> (DCB) is a set of enhancements to the Ethernet protocols designed to increase the efficiency of Ethernet connections in storage networks and clusters. Enable or disable the installer's awareness of DCB with the checkbox in this dialog.
-</div></div></div><div xml:lang="en-US" class="section" id="s1-x86-bootloader" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.11.2. x86, AMD64, and Intel 64 Boot Loader Installation</h3></div></div></div><a id="idm225491949280" class="indexterm"></a><a id="idm225473062288" class="indexterm"></a><a id="idm225412497824" class="indexterm"></a><a id="idm225473538288" class="indexterm"></a><a id="idm225470788704" class="indexterm"></a><a id="idm225428413728" class="indexterm"></a><a id="idm225422673808" class="indexterm"></a><div class="para">
+</div></div></div><div xml:lang="en-US" class="section" id="s1-x86-bootloader" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.11.2. x86, AMD64, and Intel 64 Boot Loader Installation</h3></div></div></div><a id="idm219201632704" class="indexterm"></a><a id="idm219150435824" class="indexterm"></a><a id="idm219166260816" class="indexterm"></a><a id="idm219154176544" class="indexterm"></a><a id="idm219177160304" class="indexterm"></a><a id="idm219126770944" class="indexterm"></a><a id="idm219125758528" class="indexterm"></a><div class="para">
To boot the system without boot media, you usually need to install a boot loader. A boot loader is the first software program that runs when a computer starts. It is responsible for loading and transferring control to the operating system kernel software. The kernel, in turn, initializes the rest of the operating system.
</div><div class="para">
- GRUB (GRand Unified Bootloader), which is installed by default, is a very powerful boot loader. GRUB can load a variety of free operating systems, as well as proprietary operating systems with chain-loading (the mechanism for loading unsupported operating systems, such as Windows, by loading another boot loader). Note that Fedora 20 uses GRUB 2. GRUB Legacy is no longer actively developed.<a href="#ftn.idm225428984640" class="footnote"><sup class="footnote" id="idm225428984640">[2]</sup></a>
+ GRUB (GRand Unified Bootloader), which is installed by default, is a very powerful boot loader. GRUB can load a variety of free operating systems, as well as proprietary operating systems with chain-loading (the mechanism for loading unsupported operating systems, such as Windows, by loading another boot loader). Note that Fedora 20 uses GRUB 2. GRUB Legacy is no longer actively developed.<a href="#ftn.idm219201605792" class="footnote"><sup class="footnote" id="idm219201605792">[2]</sup></a>
</div><div class="para">
If there are no other operating systems on your computer, or you are completely removing any other operating systems the installation program will install <span class="application"><strong>GRUB</strong></span> as your boot loader without any intervention.
</div><div class="para">
@@ -1604,7 +1598,7 @@ APPEND ksdevice=bootif</pre><div class="para">
</div><div class="para">
In <code class="command">parted</code>, 1024 cylinders equals 528MB. For more information, refer to:
</div><pre class="screen">
-<a href="http://www.pcguide.com/ref/hdd/bios/sizeMB504-c.html">http://www.pcguide.com/ref/hdd/bios/sizeMB504-c.html</a></pre></div></div><div class="section" id="s2-x86-bootloader-alt"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.11.2.1. Alternative Boot Loaders</h4></div></div></div><a id="idm225493037200" class="indexterm"></a><div class="para">
+<a href="http://www.pcguide.com/ref/hdd/bios/sizeMB504-c.html">http://www.pcguide.com/ref/hdd/bios/sizeMB504-c.html</a></pre></div></div><div class="section" id="s2-x86-bootloader-alt"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.11.2.1. Alternative Boot Loaders</h4></div></div></div><a id="idm219133914928" class="indexterm"></a><div class="para">
<span class="application"><strong>GRUB</strong></span> is the default bootloader for Fedora, but is not the only choice. A variety of open-source and proprietary alternatives to <span class="application"><strong>GRUB</strong></span> are available to load Fedora, including <span class="application"><strong>LILO</strong></span>, <span class="application"><strong>SYSLINUX</strong></span>, and <span class="application"><strong>Acronis Disk Director Suite</strong></span>.
</div><div class="note"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
The Fedora Project does not support third-party boot loaders.
@@ -1640,7 +1634,7 @@ APPEND ksdevice=bootif</pre><div class="para">
If you click the <span class="guibutton"><strong>Shrink to</strong></span> button, a slider will appear next to it representing the size of the selected filesystem. Use your mouse to shrink the filesystem by dragging the indicator to your chosen size. The lowest possible size is displayed at the left-hand end of the slider.
</div><div class="para">
When enough space has been reclaimed for the installation to proceed, the <span class="guibutton"><strong>Reclaim Space</strong></span> button will become available. Click this button to return to the Installation Summary Menu and proceed with the installation.
-</div></div><div xml:lang="en-US" class="section" id="s1-diskpartitioning-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.14. Creating a Custom Partition Layout</h2></div></div></div><a id="idm225446052480" class="indexterm"></a><a id="idm225464522608" class="indexterm"></a><a id="idm225451837760" class="indexterm"></a><div class="para">
+</div></div><div xml:lang="en-US" class="section" id="s1-diskpartitioning-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.14. Creating a Custom Partition Layout</h2></div></div></div><a id="idm219170997152" class="indexterm"></a><a id="idm219170377664" class="indexterm"></a><a id="idm219183489344" class="indexterm"></a><div class="para">
If you chose to partition your disks manually in <a class="xref" href="#s1-diskpartsetup-x86">Section 9.11, “Storage and partitioning”</a>, you will directed to the <span class="guilabel"><strong>Manual Partitioning</strong></span> screen.
</div><div class="para">
By choosing to create a custom partitioning layout, you must now tell the installation program where to install Fedora. This is done by defining mount points for one or more disk partitions in which Fedora is installed. You may also need to create and/or delete partitions at this time.
@@ -1650,7 +1644,7 @@ APPEND ksdevice=bootif</pre><div class="para">
The Fedora installer can handle the partitioning requirements for a typical installation.
</div><div class="para">
The <span class="guilabel"><strong>Manual Partitioning</strong></span> screen initially features a single pane on the left for partitions. This will either be empty except for information about creating mount points, or it will display existing partitions that the installer has detected. The total space and available space on the devices selected in <a class="xref" href="#s1-diskpartsetup-x86">Section 9.11, “Storage and partitioning”</a> are displayed beneath this pane.
-</div><div xml:lang="en-US" class="section" id="Adding_Partitions-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.14.1. Adding and Configuring Partitions</h3></div></div></div><a id="idm225452713168" class="indexterm"></a><a id="idm225459259760" class="indexterm"></a><a id="idm225472696288" class="indexterm"></a><div class="para">
+</div><div xml:lang="en-US" class="section" id="Adding_Partitions-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.14.1. Adding and Configuring Partitions</h3></div></div></div><a id="idm219169773488" class="indexterm"></a><a id="idm219175640688" class="indexterm"></a><a id="idm219114812432" class="indexterm"></a><div class="para">
Adding a partition is a two-step process. You first create the partition at a certain size and specify the mount point. The partition will appear in the left pane. Next, you customize it using the options in the right pane, where you can choose a name, device type, file system type, label, and whether to encrypt or reformat the partition. This differs from previous partitioning methods where the partition was created and customized in the same step.
</div><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
If you configured your disks in the shell prompt, click the arrow button at the bottom of the left-hand pane before you begin partitioning. In the resulting dialog, click <span class="guibutton"><strong>Rescan disks</strong></span>. This enables the installer to take advantage of your changes.
@@ -1684,32 +1678,32 @@ APPEND ksdevice=bootif</pre><div class="para">
When all partitions have been created and customized, click <span class="guibutton"><strong>Done</strong></span> to return to the Installation Summary Menu. The <span class="guilabel"><strong>Summary of Changes</strong></span> dialog will appear first, prompting you to either review and accept your partitions or to return and modify them.
</div><div class="para">
Once you have accepted the partitions, you will be prompted to create a passphrase if you chose to encrypt any of them (refer to <a class="xref" href="#encrypt-x86">Section 9.12, “ Encrypt Partitions ”</a>).
-</div><div xml:lang="en-US" class="section" id="s3-diskpartitioning-file-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.14.1.1. File System Types</h4></div></div></div><a id="idm225473281952" class="indexterm"></a><a id="idm225459878624" class="indexterm"></a><a id="idm225495167264" class="indexterm"></a><a id="idm225462777520" class="indexterm"></a><div class="para">
+</div><div xml:lang="en-US" class="section" id="s3-diskpartitioning-file-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.14.1.1. File System Types</h4></div></div></div><a id="idm219179715808" class="indexterm"></a><a id="idm219149108688" class="indexterm"></a><a id="idm219140011360" class="indexterm"></a><a id="idm219141322304" class="indexterm"></a><div class="para">
Fedora allows you to create different partition types and file systems. The following is a brief description of the different partition types and file systems available, and how they can be used.
</div><div xml:lang="en-US" class="itemizedlist" lang="en-US"><h6>Partition types</h6><ul><li xml:lang="en-US" class="listitem" lang="en-US"><div class="para">
<span class="guilabel"><strong>standard partition</strong></span> — A standard partition can contain a file system or swap space, or it can provide a container for software RAID or an LVM physical volume.
</div></li><li xml:lang="en-US" class="listitem" lang="en-US"><div class="para">
- <span class="guilabel"><strong>logical volume (LVM)</strong></span> — Creating an LVM partition automatically generates an LVM logical volume. LVM can improve performance when using physical disks. To create a logical volume, refer to <a class="xref" href="#Create_LVM-x86">Section 9.14.3, “ Create LVM Logical Volume ”</a>. For more information regarding LVM, refer to the <em class="citetitle">Fedora Deployment Guide</em>.
+ <span class="guilabel"><strong>logical volume (LVM)</strong></span> — Creating an LVM partition automatically generates an LVM logical volume. LVM can improve performance when using physical disks. To create a logical volume, refer to <a class="xref" href="#Create_LVM-x86">Section 9.14.3, “ Create LVM Logical Volume ”</a>. For more information regarding LVM, refer to the <em class="citetitle">Fedora System Administrators Guide</em>.
</div></li><li xml:lang="en-US" class="listitem" lang="en-US"><div class="para">
- <span class="guilabel"><strong>software RAID</strong></span> — Creating two or more software RAID partitions allows you to create a RAID device. One RAID partition is assigned to each disk on the system. To create a RAID device, refer to <a class="xref" href="#Create_Software_RAID-x86">Section 9.14.2, “ Create Software RAID ”</a>. For more information regarding RAID, refer to the chapter <em class="citetitle">RAID (Redundant Array of Independent Disks)</em> in the <em class="citetitle">Fedora Deployment Guide</em>.
+ <span class="guilabel"><strong>software RAID</strong></span> — Creating two or more software RAID partitions allows you to create a RAID device. One RAID partition is assigned to each disk on the system. To create a RAID device, refer to <a class="xref" href="#Create_Software_RAID-x86">Section 9.14.2, “ Create Software RAID ”</a>. For more information regarding RAID, refer to the chapter <em class="citetitle">RAID (Redundant Array of Independent Disks)</em> in the <em class="citetitle">Fedora System Administrators Guide</em>.
</div></li><li xml:lang="en-US" class="listitem" lang="en-US"><div class="para">
<span class="guilabel"><strong>Btrfs</strong></span> — Btrfs is under development as a file system with several device-like features, so is presented in the installer as a type of partition. It is capable of addressing and managing more files, larger files, and larger volumes than the ext2, ext3, and ext4 file systems. To create a Btrfs volume and read more information, refer to <a class="xref" href="#Create_Btrfs-x86">Section 9.14.4, “ Create a Btrfs subvolume”</a>.
</div></li></ul></div><div xml:lang="en-US" class="itemizedlist" lang="en-US"><h6>File systems</h6><ul><li class="listitem"><div class="para">
<span class="guilabel"><strong>ext4</strong></span> — The ext4 file system is based on the ext3 file system and features a number of improvements. These include support for larger file systems and larger files, faster and more efficient allocation of disk space, no limit on the number of subdirectories within a directory, faster file system checking, and more robust journaling. The ext4 file system is selected by default and is highly recommended.
</div></li><li xml:lang="en-US" class="listitem" lang="en-US"><div class="para">
- <span class="guilabel"><strong>ext3</strong></span> — The ext3 file system is based on the ext2 file system and has one main advantage — journaling. Using a journaling file system reduces time spent recovering a file system after a crash as there is no need to <code class="command">fsck</code> <a href="#ftn.idm225447275664" class="footnote"><sup class="footnote" id="idm225447275664">[3]</sup></a> the file system.
+ <span class="guilabel"><strong>ext3</strong></span> — The ext3 file system is based on the ext2 file system and has one main advantage — journaling. Using a journaling file system reduces time spent recovering a file system after a crash as there is no need to <code class="command">fsck</code> <a href="#ftn.idm219203726096" class="footnote"><sup class="footnote" id="idm219203726096">[3]</sup></a> the file system.
</div></li><li xml:lang="en-US" class="listitem" lang="en-US"><div class="para">
<span class="guilabel"><strong>ext2</strong></span> — An ext2 file system supports standard Unix file types (regular files, directories, symbolic links, etc). It provides the ability to assign long file names, up to 255 characters.
</div></li><li xml:lang="en-US" class="listitem" lang="en-US"><div class="para">
- <span class="guilabel"><strong>swap</strong></span> — Swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing. Refer to the <em class="citetitle">Fedora Deployment Guide</em> for additional information.
+ <span class="guilabel"><strong>swap</strong></span> — Swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing. Refer to the <em class="citetitle">Fedora System Administrators Guide</em> for additional information.
</div></li><li xml:lang="en-US" class="listitem" lang="en-US"><div class="para">
- <span class="guilabel"><strong>BIOS Boot</strong></span> — A small partition requiring for booting a device with a GPT/GUID partition table.
+ <span class="guilabel"><strong>BIOS Boot</strong></span> — A small partition required for booting a device with a GPT/GUID partition table on BIOS systems. Not required for UEFI systems.
</div></li><li xml:lang="en-US" class="listitem" lang="en-US"><div class="para">
<span class="guilabel"><strong>xfs</strong></span> — XFS is a highly scalable, high-performance file system that supports filesystems up to 16 exabytes (approximately 16 million terabytes), files up to 8 exabytes (approximately 8 million terabytes) and directory structures containing tens of millions of entries. XFS supports metadata journaling, which facilitates quicker crash recovery. The XFS file system can also be defragmented and resized while mounted and active.
</div></li><li xml:lang="en-US" class="listitem" lang="en-US"><div class="para">
<span class="guilabel"><strong>vfat</strong></span> — The VFAT file system is a Linux file system that is compatible with Microsoft Windows long filenames on the FAT file system.
</div></li></ul></div></div></div><div xml:lang="en-US" class="section" id="Create_Software_RAID-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.14.2. Create Software RAID </h3></div></div></div><div class="para">
- <em class="firstterm">Redundant arrays of independent disks</em> (RAIDs) are constructed from multiple storage devices that are arranged to provide increased performance and — in some configurations — greater fault tolerance. Refer to the <em class="citetitle">Fedora Deployment Guide</em> for a description of different kinds of RAIDs.
+ <em class="firstterm">Redundant arrays of independent disks</em> (RAIDs) are constructed from multiple storage devices that are arranged to provide increased performance and — in some configurations — greater fault tolerance.
</div><div class="para">
In earlier versions of Fedora, RAID partitions and devices were created in separate steps. Now, the RAID device is created in one step and disks are added or removed as necessary. One RAID partition is allowed per disk for each device, so the number of disks available to the installer will determine which levels of RAID device are available to you.
</div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/diskpartitioning/software-raid.png" width="660" alt="Create a software RAID device" /><div class="longdesc"><div class="para">
@@ -1744,12 +1738,12 @@ APPEND ksdevice=bootif</pre><div class="para">
If fewer disks are included than the specified RAID level needs, a yellow notification bar at the bottom of the screen will inform you that <span class="guilabel"><strong>Device reconfiguration failed</strong></span>. Clicking this warning prompts a dialog informing you how many disks are required.
</div></li><li class="step"><div class="para">
Click <span class="guibutton"><strong>Update Settings</strong></span> to save your changes, and either continue with another partition or click <span class="guibutton"><strong>Done</strong></span> to return to the Installation Summary Menu.
-</div></li></ol></div></div><div xml:lang="en-US" class="section" id="Create_LVM-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.14.3. Create LVM Logical Volume </h3></div></div></div><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important — LVM Unavailable in Text-Mode Installations</h2></div><div class="admonition"><div class="para">
- LVM initial set up is not available during text-mode installation. If you need to create an LVM configuration from scratch, press <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F2</strong></span> to use a different virtual console, and run the <code class="command">lvm</code> command. To return to the text-mode installation, press <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F1</strong></span>.
+</div></li></ol></div></div><div xml:lang="en-US" class="section" id="Create_LVM-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.14.3. Create LVM Logical Volume </h3></div></div></div><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important - LVM in Text-Mode is Automatic Partitioning Only</h2></div><div class="admonition"><div class="para">
+ Text-mode installation only provides automatic partitioning for LVM volumes. If customization is required, use a kickstart, graphical, or vnc installation.
</div></div></div><div class="para">
<em class="firstterm">Logical Volume Management</em> (LVM) presents a simple logical view of underlying physical storage space, such as hard drives or LUNs. Partitions on physical storage are represented as <em class="firstterm">physical volumes</em> that can be grouped together into <em class="firstterm">volume groups</em>. Each volume group can be divided into multiple <em class="firstterm">logical volumes</em>, each of which is analogous to a standard disk partition. Therefore, LVM logical volumes function as partitions that can span multiple physical disks.
</div><div class="para">
- To read more about LVM, refer to the <em class="citetitle">Fedora Deployment Guide</em>. Note, LVM is only available in the graphical installation program.
+ To read more about LVM, refer to the <em class="citetitle">Fedora System Administrators Guide</em>. Note, LVM is only available in the graphical installation program.
</div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/diskpartitioning/lvm-pv.png" width="660" alt="Configure a logical volume" /><div class="longdesc"><div class="para">
The area of the Manual Partitioning screen for configuring a logical volume.
</div></div></div></div><h6>Figure 9.32. Configure a logical volume</h6></div><br class="figure-break" /><div class="para">
@@ -1800,7 +1794,7 @@ APPEND ksdevice=bootif</pre><div class="para">
Click <span class="guibutton"><strong>Update Settings</strong></span> to save your changes, and either continue with another partition or click <span class="guibutton"><strong>Done</strong></span> to return to the Installation Summary Menu.
</div></li></ol></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
Placing <code class="filename">/boot</code> on a Btrfs subvolume may lead to instability and is not recommended.
- </div></div></div></div><div xml:lang="en-US" class="section" id="s2-diskpartrecommend-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.14.5. Recommended Partitioning Scheme</h3></div></div></div><a id="idm225441724736" class="indexterm"></a><a id="idm225375923024" class="indexterm"></a><a id="idm225464569136" class="indexterm"></a><a id="idm225476084400" class="indexterm"></a><a id="idm225438370400" class="indexterm"></a><div xml:lang="en-US" class="section" id="idm225434791840" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm225434791840">9.14.5.1. x86, AMD64, and Intel 64 systems</h4></div></div></div><div class="para">
+ </div></div></div></div><div xml:lang="en-US" class="section" id="s2-diskpartrecommend-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.14.5. Recommended Partitioning Scheme</h3></div></div></div><a id="idm219140778032" class="indexterm"></a><a id="idm219182235936" class="indexterm"></a><a id="idm219133642208" class="indexterm"></a><a id="idm219166408304" class="indexterm"></a><a id="idm219206890320" class="indexterm"></a><div xml:lang="en-US" class="section" id="idm219085841040" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm219085841040">9.14.5.1. x86, AMD64, and Intel 64 systems</h4></div></div></div><div class="para">
<span class="emphasis"><em>Unless you have a reason for doing otherwise, we recommend that you create the following partitions for x86, AMD64, and Intel 64 systems</em></span>:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
A <code class="systemitem">swap</code> partition
@@ -1810,7 +1804,7 @@ APPEND ksdevice=bootif</pre><div class="para">
A <code class="filename">/</code> partition
</div></li><li class="listitem"><div class="para">
A <code class="filename">/home</code> partition
- </div></li></ul></div><div class="itemizedlist"><ul><li xml:lang="en-US" class="listitem" lang="en-US"><div class="formalpara"><h5 class="formalpara" id="idm225463074448">A <code class="filename">swap</code> partition (at least 256 MB)</h5>
+ </div></li></ul></div><div class="itemizedlist"><ul><li xml:lang="en-US" class="listitem" lang="en-US"><div class="formalpara"><h5 class="formalpara" id="idm219167612608">A <code class="filename">swap</code> partition (at least 256 MB)</h5>
Swap partitions support virtual memory: data is written to a swap partition when there is not enough RAM to store the data your system is processing.
</div><div class="para">
In years past, the recommended amount of swap space increased linearly with the amount of RAM in the system. Modern systems often include hundreds of gigabytes of RAM, however. As a consequence, recommended swap space is considered a function of system memory workload, not system memory.
@@ -1850,26 +1844,26 @@ APPEND ksdevice=bootif</pre><div class="para">
At the border between each range listed above (for example, a system with 2GB, 8GB, or 64GB of system RAM), discretion can be exercised with regard to chosen swap space and hibernation support. If your system resources allow for it, increasing the swap space may lead to better performance.
</div><div class="para">
Note that distributing swap space over multiple storage devices — particularly on systems with fast drives, controllers and interfaces — also improves swap space performance.
- </div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm225472579680">A <code class="filename">/boot/</code> partition (250 MB)</h5>
- The partition mounted on <code class="filename">/boot/</code> contains the operating system kernel (which allows your system to boot Fedora), along with files used during the bootstrap process. For most users, a 250 MB boot partition is sufficient.
+ </div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm219134029888">A <code class="filename">/boot/</code> partition (500 MB)</h5>
+ The partition mounted on <code class="filename">/boot/</code> contains the operating system kernel (which allows your system to boot Fedora), along with files used during the bootstrap process. For most users, a 500 MB boot partition is sufficient.
</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
If your hard drive is more than 1024 cylinders (and your system was manufactured more than two years ago), you may need to create a <code class="filename">/boot/</code> partition if you want the <code class="filename">/</code> (root) partition to use all of the remaining space on your hard drive.
</div></div></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
If you have a RAID card, be aware that some BIOSes do not support booting from the RAID card. In cases such as these, the <code class="filename">/boot/</code> partition must be created on a partition outside of the RAID array, such as on a separate hard drive.
- </div></div></div></li><li xml:lang="en-US" class="listitem" lang="en-US"><div class="formalpara"><h5 class="formalpara" id="idm225462111232">A <code class="filename">root</code> partition (3.0 GB - 5.0 GB)</h5>
+ </div></div></div></li><li xml:lang="en-US" class="listitem" lang="en-US"><div class="formalpara"><h5 class="formalpara" id="idm219134845216">A <code class="filename">root</code> partition (3.0 GB - 5.0 GB)</h5>
This is where "<code class="filename">/</code>" (the root directory) is located. In this setup, all files (except those stored in <code class="filename">/boot</code>) are on the root partition.
</div><div class="para">
- A 3.0 GB partition allows you to install a minimal installation, while a 5.0 GB root partition lets you perform a full installation, choosing all package groups.
+ A 3 GB partition allows you to install a minimal installation. For a full desktop installation, a <span class="emphasis"><em>minimum</em></span> of 20GB for the root partition is recommended.
</div><div class="important"><div class="admonition_header"><h2>Root and <code class="filename">/root</code></h2></div><div class="admonition"><div class="para">
The <code class="filename">/</code> (or root) partition is the top of the directory structure. The <code class="filename">/root</code> directory<code class="filename">/root</code> (sometimes pronounced "slash-root") directory is the home directory of the user account for system administration.
- </div></div></div></li><li xml:lang="en-US" class="listitem" lang="en-US"><div class="formalpara"><h5 class="formalpara" id="idm225475259728">A <code class="filename">home</code> partition (at least 100 MB)</h5>
+ </div></div></div></li><li xml:lang="en-US" class="listitem" lang="en-US"><div class="formalpara"><h5 class="formalpara" id="idm219165687280">A <code class="filename">home</code> partition (at least 100 MB)</h5>
To store user data separately from system data, create a dedicated partition within a volume group for the <code class="filename">/home</code> directory. This will enable you to upgrade or reinstall Fedora without erasing user data files.
</div></li></ul></div><div class="para">
Many systems have more partitions than the minimum listed above. Choose partitions based on your particular system needs. Refer to <a class="xref" href="#sn-partitioning-advice">Section 9.14.5.1.1, “Advice on Partitions”</a> for more information.
</div><div class="para">
If you create many partitions instead of one large <code class="filename">/</code> partition, upgrades become easier.
</div><div class="para">
- The following table summarizes minimum partition sizes for the partitions containing the listed directories. You <span class="emphasis"><em>do not</em></span> have to make a separate partition for each of these directories. For instance, if the partition containing <code class="filename">/foo</code> must be at least 500 MB, and you do not make a separate <code class="filename">/foo</code> partition, then the <code class="filename">/</code> (root) partition must be at least 500 MB.
+ The following table summarizes minimum partition sizes for the partitions containing the listed directories. You <span class="emphasis"><em>do not</em></span> have to make a separate partition for each of these directories. For instance, if the partition containing <code class="filename">/foo</code> must be at least 2 GB, and you do not make a separate <code class="filename">/foo</code> partition, then the <code class="filename">/</code> (root) partition must be at least 2 GB.
</div><div class="table" id="tb-Minumum_partition_sizes"><h6>Table 9.3. Minimum partition sizes</h6><div class="table-contents"><table summary="Minimum partition sizes" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="" align="left">
Directory
</th><th class="" align="left">
@@ -1877,19 +1871,19 @@ APPEND ksdevice=bootif</pre><div class="para">
</th></tr></thead><tbody><tr><td class="" align="left">
<code class="filename">/</code>
</td><td class="" align="left">
- 250 MB
+ 2 GB
</td></tr><tr><td class="" align="left">
<code class="filename">/usr</code>
</td><td class="" align="left">
- 250 MB, but avoid placing this on a separate partition
+ <code class="filename">/usr</code> on a seperate partition is not supported.
</td></tr><tr><td class="" align="left">
<code class="filename">/tmp</code>
</td><td class="" align="left">
- 50 MB
+ <code class="systemitem">tmpfs</code> by default, 50 MB otherwise.
</td></tr><tr><td class="" align="left">
<code class="filename">/var</code>
</td><td class="" align="left">
- 384 MB
+ 500 MB
</td></tr><tr><td class="" align="left">
<code class="filename">/home</code>
</td><td class="" align="left">
@@ -1907,13 +1901,13 @@ APPEND ksdevice=bootif</pre><div class="para">
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
Consider encrypting any partitions that might contain sensitive data. Encryption prevents unauthorized people from accessing the data on the partitions, even if they have access to the physical storage device. In most cases, you should at least encrypt the <code class="filename">/home</code> partition.
</div></li><li class="listitem"><div class="para">
- Each kernel installed on your system requires approximately 10 MB on the <code class="filename">/boot</code> partition. Unless you plan to install a great many kernels, the default partition size of 250 MB for <code class="filename">/boot</code> should suffice.
+ Each kernel installed on your system requires approximately 220 MB on the <code class="filename">/boot</code> partition. The boot partition can also be used during upgrades, so leaving extra room is recommended. Unless you plan to install a great many kernels, the default partition size of 500 MB for <code class="filename">/boot</code> should suffice.
</div></li><li class="listitem"><div class="para">
The <code class="filename">/var</code> directory holds content for a number of applications, including the <span class="application"><strong>Apache</strong></span> web server. It also is used to store downloaded update packages on a temporary basis. Ensure that the partition containing the <code class="filename">/var</code> directory has enough space to download pending updates and hold your other content.
</div><div class="warning" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
The <span class="application"><strong>PackageKit</strong></span> update software downloads updated packages to <code class="filename">/var/cache/yum/</code> by default. If you partition the system manually, and create a separate <code class="filename">/var/</code> partition, be sure to create the partition large enough (3.0 GB or more) to download package updates.
</div></div></div></li><li class="listitem"><div class="para">
- The <code class="filename">/usr</code> directory holds the majority of software content on a Fedora system. For an installation of the default set of software, allocate at least 4 GB of space. If you are a software developer or plan to use your Fedora system to learn software development skills, you may want to at least double this allocation.
+ The <code class="filename">/usr</code> directory holds the majority of software content on a Fedora system. Because crucial applications and utilities are located in <code class="filename">/usr</code>, Fedora does not support placing it on a separate partition.
</div><div class="important"><div class="admonition_header"><h2>Do not place <code class="filename">/usr</code> on a separate file system</h2></div><div class="admonition"><div class="para">
If <code class="filename">/usr</code> is on a separate file system from <code class="filename">/</code>, the boot process becomes much more complex because <code class="filename">/usr</code> contains boot-critical components. In some situations (like installations on iSCSI drives), the boot process might not work at all.
</div></div></div></li><li class="listitem"><div class="para">
@@ -1938,7 +1932,7 @@ APPEND ksdevice=bootif</pre><div class="para">
</th></tr></thead><tbody><tr><td class="" align="left">
<code class="filename">/boot</code>
</td><td class="" align="left">
- 250 MB <code class="systemitem">ext3</code> partition
+ 500 MB <code class="systemitem">ext3</code> partition
</td></tr><tr><td class="" align="left">
<code class="filename">swap</code>
</td><td class="" align="left">
@@ -1970,40 +1964,44 @@ APPEND ksdevice=bootif</pre><div class="para">
50 GB ext4
</td></tr></tbody></table></div></div><br class="table-break" />
- </div></div></div><br class="example-break" /></div></div></div></div><div xml:lang="en-US" class="section" id="Begin_installation-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.15. Begin installation</h2></div></div></div><div class="para">
+ </div></div></div><br class="example-break" /></div></div></div><div xml:lang="en-US" class="section" id="s1-diskpartitioning-confirm" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.14.6. Review and Confirm Custom Partition Layout</h3></div></div></div><div class="para">
+ After manually configuring a partition layout, you are given a summary of changes to be made to the disk. Review the summary to ensure that the installation will proceed as expected, and that no filesystems with important data will be lost.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/diskpartitioning/confirm.png" width="660" alt="Summary of Changes" /><div class="longdesc"><div class="para">
+ The itemized summary of devices to be created or destroyed as a result of manual partitioning.
+ </div></div></div></div><h6>Figure 9.34. Summary of Changes</h6></div><br class="figure-break" /></div></div><div xml:lang="en-US" class="section" id="Begin_installation-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.15. Begin installation</h2></div></div></div><div class="para">
When all required sections of the Installation Summary Menu have been completed, the yellow admonition at the bottom of the menu screen will disappear and the <span class="guibutton"><strong>Begin Installation</strong></span> button can be selected.
</div><div class="figure" xml:lang="en-US" lang="en-US"><div class="figure-contents"><div class="mediaobject"><img src="images/diskpartitioning/write_changes.png" width="660" alt="Ready to install" /><div class="longdesc"><div class="para">
When all required items on the Installation Summary Menu have been attended to, the installation can begin.
- </div></div></div></div><h6>Figure 9.34. Ready to install</h6></div><br class="figure-break" /><div class="para">
+ </div></div></div></div><h6>Figure 9.35. Ready to install</h6></div><br class="figure-break" /><div class="para">
If you have finished customizing your installation and are certain that you want to proceed, click <span class="guibutton"><strong>Begin Installation</strong></span>.
</div><div class="warning"><div class="admonition_header"><h2>Last chance to cancel safely</h2></div><div class="admonition"><div class="para">
Up to this point in the installation process, the installer has made no lasting changes to your computer. When you click <span class="guibutton"><strong>Begin Installation</strong></span>, the installer will allocate space on your hard drive and start to transfer Fedora into this space. Depending on the partitioning option that you chose, this process might include erasing data that already exists on your computer.
</div><div class="para">
- To revise any of the choices that you made up to this point, return to the relevant section of the Installation Summary Menu. To cancel installation completely, click <span class="guibutton"><strong>Quit</strong></span> or switch off your computer. To switch off most computers at this stage, press the power button and hold it down for a few seconds.
+ To revise any of the choices that you made up to this point, return to the relevant section of the Installation Summary Menu. To cancel installation completely, click <span class="guibutton"><strong>Quit</strong></span> or switch off your computer. To switch off most computers at this stage, press the power button and it will begin the shut down process.
</div><div class="para">
After you click <span class="guibutton"><strong>Begin Installation</strong></span>, allow the installation process to complete. If the process is interrupted (for example, by you switching off or resetting the computer, or by a power outage) you will probably not be able to use your computer until you restart and complete the Fedora installation process, or install a different operating system.
</div></div></div></div><div xml:lang="en-US" class="section" id="s1-progresshub-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.16. The Configuration Menu and Progress Screen</h2></div></div></div><div class="para">
Once you click <span class="guibutton"><strong>Begin Installation</strong></span> on the Installation Summary Menu, you will be directed to the Configuration Menu and Progress Screen. Fedora reports the installation progress on the screen as it writes the selected packages to your system.
</div><div class="figure" xml:lang="en-US" lang="en-US"><div class="figure-contents"><div class="mediaobject"><img src="images/pkgselection/installing-packages.png" alt="Installing packages" /><div class="longdesc"><div class="para">
The Packages Completed progress bar
- </div></div></div></div><h6>Figure 9.35. Installing packages</h6></div><br class="figure-break" /><div class="para">
- <a id="idm225448374160" class="indexterm"></a>
- <a id="idm225436848448" class="indexterm"></a>
+ </div></div></div></div><h6>Figure 9.36. Installing packages</h6></div><br class="figure-break" /><div class="para">
+ <a id="idm219074100160" class="indexterm"></a>
+ <a id="idm219139286928" class="indexterm"></a>
For your reference, a complete log of your installation can be found in <code class="filename">/root/install.log</code> once you reboot your system.
</div><div class="para">
While the packages are being installed, select the menu items above the progress bar to create user profiles and a root password. These items must be configured in order to complete the installation.
-</div><div xml:lang="en-US" class="section" id="sn-account_configuration-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.16.1. Set the Root Password</h3></div></div></div><a id="idm225426606752" class="indexterm"></a><a id="idm225439268976" class="indexterm"></a><div class="para">
+</div><div xml:lang="en-US" class="section" id="sn-account_configuration-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.16.1. Set the Root Password</h3></div></div></div><a id="idm219139117952" class="indexterm"></a><a id="idm219139169328" class="indexterm"></a><div class="para">
Setting up a root account and password is one of the most important steps during your installation. The root account is used to install packages, upgrade RPMs, and perform most system maintenance. Logging in as root gives you complete control over your system.
</div><div class="note" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
The root user (also known as the superuser) has complete access to the entire system; for this reason, logging in as the root user is best done <span class="emphasis"><em>only</em></span> to perform system maintenance or administration.
</div></div></div><div class="figure" xml:lang="en-US" lang="en-US"><div class="figure-contents"><div class="mediaobject"><img src="images/accountconfig/rootpassword.png" alt="Root Password" /><div class="longdesc"><div class="para">
Setting your root password.
- </div></div></div></div><h6>Figure 9.36. Root Password</h6></div><br class="figure-break" /><div class="para">
+ </div></div></div></div><h6>Figure 9.37. Root Password</h6></div><br class="figure-break" /><div class="para">
Use the root account only for system administration. Create a non-root account for your general use and use the <code class="command">su</code> command to change to root only when you need to perform tasks that require superuser authorization. These basic rules minimize the chances of a typo or an incorrect command doing damage to your system.
</div><div class="note" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
To become root, type <code class="command">su -</code> at the shell prompt in a terminal window and then press <span class="keycap"><strong>Enter</strong></span>. Then, enter the root password and press <span class="keycap"><strong>Enter</strong></span>.
</div></div></div><div class="para">
- The installation program requires you to set a root password<a href="#ftn.idm225443384144" class="footnote"><sup class="footnote" id="idm225443384144">[4]</sup></a> for your system. <span class="emphasis"><em>. You cannot proceed to the installation itself without entering a root password.</em></span>
+ The installation program requires you to set a root password<a href="#ftn.idm219130406384" class="footnote"><sup class="footnote" id="idm219130406384">[4]</sup></a> for your system. <span class="emphasis"><em>. You cannot proceed to the installation itself without entering a root password.</em></span>
</div><div class="para">
The root password must be at least six characters long; the password you type is not echoed to the screen. You must enter the password twice; if the two passwords do not match, the installation program asks you to enter them again.
</div><div class="para">
@@ -2020,7 +2018,7 @@ APPEND ksdevice=bootif</pre><div class="para">
Create a user account for yourself with this screen. Always use this account to log in to your Fedora system, rather than using the <code class="systemitem">root</code> account.
</div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/firstboot/fb-createuser.png" alt="The Create User screen" /><div class="longdesc"><div class="para">
The Create User screen
- </div></div></div></div><h6>Figure 9.37. The Create User screen</h6></div><br class="figure-break" /><div class="important"><div class="admonition_header"><h2>Note — Network Login Not Available During Installation</h2></div><div class="admonition"><div class="para">
+ </div></div></div></div><h6>Figure 9.38. The Create User screen</h6></div><br class="figure-break" /><div class="important"><div class="admonition_header"><h2>Note — Network Login Not Available During Installation</h2></div><div class="admonition"><div class="para">
It is not possible to configure network-based authentication during installation using the graphical interface in the current version of Fedora. This option now becomes available after the installation finishes and the system is started for the first time. Alternatively, you can use <span class="application"><strong>kickstart</strong></span> to configure network authentication during the installation process. See <a class="xref" href="#ch-kickstart2">Chapter 15, <em>Kickstart Installations</em></a> for more details on kickstart installations, and the <a href="https://docs.fedoraproject.org/en-US/Fedora/19/html-single/Release_Notes/in…">Fedora 19 Release Notes</a> for information about this limitation.
</div></div></div><div class="para">
Enter a user name and your full name, and then enter your chosen password. Type your password once more in the <span class="guilabel"><strong>Confirm Password</strong></span> box to ensure that it is correct.
@@ -2030,17 +2028,17 @@ APPEND ksdevice=bootif</pre><div class="para">
To create additional users or customise your first user account, click <span class="guibutton"><strong>Advanced</strong></span> to open the <span class="guilabel"><strong>Advanced User Configuration</strong></span> dialog.
</div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/firstboot/fb-createuser-usermanager.png" alt="Advanced User Configuration" /><div class="longdesc"><div class="para">
Advanced User Configuration
- </div></div></div></div><h6>Figure 9.38. Advanced User Configuration</h6></div><br class="figure-break" /><div class="para">
+ </div></div></div></div><h6>Figure 9.39. Advanced User Configuration</h6></div><br class="figure-break" /><div class="para">
In <span class="guilabel"><strong>Advanced User Configuration</strong></span> you can edit various properties, such as a private group for the user, the preferred login shell, and user and group IDs.
</div><div class="important"><div class="admonition_header"><h2>Important — Create at least one user account</h2></div><div class="admonition"><div class="para">
If you selected GNOME as your desktop environment during the package selection process, you will be able to create a user account after the installation finishes. Other desktop environments, such as KDE or Xfce, do not offer this functionality. It is therefore important to create at least one user account during this step; otherwise you will not be able to log in to the Fedora graphical environment. If you skipped this step during installation, refer to <a class="xref" href="#Trouble_After_Booting-GUI">Section 10.4.3, “Booting into a Graphical Environment”</a>.
</div></div></div><div class="note"><div class="admonition_header"><h2>Note — Creating Extra User Accounts</h2></div><div class="admonition"><div class="para">
- To add additional user accounts to your system after the installation is complete, choose <span class="guimenu"><strong>System</strong></span> → <span class="guisubmenu"><strong>Administration</strong></span> → <span class="guimenuitem"><strong>Users & Groups</strong></span>.
+ To add additional user accounts to your system after the installation is complete, use the <span class="application"><strong>system-config-users</strong></span> utility, the <code class="literal">Users</code> section of <span class="application"><strong>GNOME Settings</strong></span> or command line utilities such as <code class="command">useradd</code>. Refer to the <em class="citetitle">Fedora System Administrators Guide</em> for more information.
</div></div></div></div></div><div xml:lang="en-US" class="section" id="s1-complete-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.17. Installation Complete</h2></div></div></div><div class="para">
Congratulations! Now that you have configured the remaining settings, your Fedora installation is complete.
</div><div class="figure" xml:lang="en-US" id="fig-reboot" lang="en-US"><div class="figure-contents"><div class="mediaobject"><img src="images/reboot/reboot.png" alt="Packages installed" /><div class="longdesc"><div class="para">
The menu presented when the desktop loads, offering the choice to try Fedora or install it to the hard drive.
- </div></div></div></div><h6>Figure 9.39. Packages installed</h6></div><br class="figure-break" /><div class="para">
+ </div></div></div></div><h6>Figure 9.40. Packages installed</h6></div><br class="figure-break" /><div class="para">
Click <span class="guibutton"><strong>Reboot</strong></span> to reboot your system and begin using Fedora. Remember to remove any installation media if it is not ejected automatically upon reboot.
</div><div class="para">
After your computer's normal power-up sequence has completed, Fedora loads and starts. By default, the start process is hidden behind a graphical screen that displays a progress bar. Eventually, a <code class="prompt">login:</code> prompt or a GUI login screen (if you installed the X Window System and chose to start X automatically) appears. Once you have logged in, you can begin using Fedora.
@@ -2052,19 +2050,19 @@ APPEND ksdevice=bootif</pre><div class="para">
When you log in for the first time, a <span class="guilabel"><strong>Desktop Help</strong></span> window will automatically open, allowing you to view tutorials and watch several videos showcasing some of the desktop environment's features.
</div><div class="figure" id="figu-gnome-initial-setup"><div class="figure-contents"><div class="mediaobject"><img src="images/welcome/gnome-initial-setup-langselection.png" alt="Language selection in GNOME Initial Setup" /><div class="longdesc"><div class="para">
The first screen of the GNOME Initial Setup application, showing a language selection menu.
- </div></div></div></div><h6>Figure 9.40. Language selection in GNOME Initial Setup</h6></div><br class="figure-break" /></div><div xml:lang="en-US" class="section" id="sect-other-initial-setup" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.17.2. Initial Setup in Other Desktop Environments</h3></div></div></div><div class="para">
+ </div></div></div></div><h6>Figure 9.41. Language selection in GNOME Initial Setup</h6></div><br class="figure-break" /></div><div xml:lang="en-US" class="section" id="sect-other-initial-setup" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.17.2. Initial Setup in Other Desktop Environments</h3></div></div></div><div class="para">
In desktop environments other than <span class="application"><strong>GNOME</strong></span>, such as <span class="application"><strong>XFCE</strong></span> or <span class="application"><strong>KDE</strong></span>, you will only be presented with a screen allowing you to customize system settings and create a user account if you have not done so during the installation. If you have configured your language, keyboard layout, time zone and created a user previously (for example during the graphical installation), you will be able to log in and start using your system immediately. If only some of the available options are configured, the Initial Setup menu will prompt you the remaining ones.
</div><div class="para">
The Initial Setup application works the same way as the <span class="application"><strong>Anaconda</strong></span> graphical installer. For instructions on how to configure the available settings, see <a class="xref" href="#s1-guimode-interface-x86">Section 9.2, “The Graphical Installation Program User Interface”</a>.
</div><div class="figure" id="figu-other-initial-setup"><div class="figure-contents"><div class="mediaobject"><img src="images/welcome/initial-setup-hub.png" alt="The Initial Setup Menu" /><div class="longdesc"><div class="para">
The Initial Setup application's hub, allowing you to configure options not specified during the installation.
- </div></div></div></div><h6>Figure 9.41. The Initial Setup Menu</h6></div><br class="figure-break" /></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div id="ftn.idm225428984640" class="footnote"><div class="para"><a href="#idm225428984640" class="para"><sup class="para">[2] </sup></a>
+ </div></div></div></div><h6>Figure 9.42. The Initial Setup Menu</h6></div><br class="figure-break" /></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div id="ftn.idm219201605792" class="footnote"><div class="para"><a href="#idm219201605792" class="para"><sup class="para">[2] </sup></a>
<a href="http://www.gnu.org/software/grub/grub-legacy.en.html">http://www.gnu.org/software/grub/grub-legacy.en.html</a>
- </div></div><div id="ftn.idm225447275664" class="footnote"><div class="para"><a href="#idm225447275664" class="para"><sup class="para">[3] </sup></a>
+ </div></div><div id="ftn.idm219203726096" class="footnote"><div class="para"><a href="#idm219203726096" class="para"><sup class="para">[3] </sup></a>
The <code class="command">fsck</code> application is used to check the file system for metadata consistency and optionally repair one or more Linux file systems.
- </div></div><div id="ftn.idm225443384144" class="footnote"><div class="para"><a href="#idm225443384144" class="para"><sup class="para">[4] </sup></a>
+ </div></div><div id="ftn.idm219130406384" class="footnote"><div class="para"><a href="#idm219130406384" class="para"><sup class="para">[4] </sup></a>
A root password is the administrative password for your Fedora system. You should only log in as root when needed for system maintenance. The root account does not operate within the restrictions placed on normal user accounts, so changes made as root can have implications for your entire system.
- </div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-trouble-x86" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 10. Troubleshooting Installation on an Intel or AMD System</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#idm225499886064">10.1. You are unable to boot Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="#idm225419970064">10.1.1. Are You Unable to Boot With Your RAID Card?</a></span></dt><dt><span class="section"><a href="#idm225452658560">10.1.2. Is Your System Displaying Signal 11 Errors?</a></span></dt></dl></dd><dt><span class="section"><a href="#idm225471283760">10.2. Trouble Beginning the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#idm225464520544">10.2.1. Problems with Booting into the Graphical Installation</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-trouble-install-x86">10.3. Trouble During the Installation</
a></span></dt><dd><dl><dt><span class="section"><a href="#s2-trouble-nodevicefound-x86">10.3.1. <code class="computeroutput">No devices found to install Fedora </code> Error Message</a></span></dt><dt><span class="section"><a href="#s2-trouble-tracebacks-x86">10.3.2. Reporting traceback messages</a></span></dt><dt><span class="section"><a href="#s2-trouble-part-tables-x86">10.3.3. Trouble with Partition Tables</a></span></dt><dt><span class="section"><a href="#s2-trouble-space-x86">10.3.4. Using Remaining Space</a></span></dt><dt><span class="section"><a href="#s2-trouble-completeparts-x86">10.3.5. Other Partitioning Problems</a></span></dt></dl></dd><dt><span class="section"><a href="#idm225448803200">10.4. Problems After Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-trouble-grub">10.4.1. Trouble With the Graphical GRUB Screen on an x86-based System?</a></span></dt><dt><span class="section"><a href="#s2-trouble-grub-command-line">10.4.2. Blocked
by a GRUB command line after upgrading?</a></span></dt><dt><span class="section"><a href="#Trouble_After_Booting-GUI">10.4.3. Booting into a Graphical Environment</a></span></dt><dt><span class="section"><a href="#idm225460054624">10.4.4. Problems with the X Window System (GUI)</a></span></dt><dt><span class="section"><a href="#idm225503142160">10.4.5. Problems with the X Server Crashing and Non-Root Users</a></span></dt><dt><span class="section"><a href="#idm225461616880">10.4.6. Problems When You Try to Log In</a></span></dt><dt><span class="section"><a href="#s2-trouble-ram">10.4.7. Is Your RAM Not Being Recognized?</a></span></dt><dt><span class="section"><a href="#idm225465817296">10.4.8. Your Printer Does Not Work</a></span></dt><dt><span class="section"><a href="#idm225447278528">10.4.9. Apache HTTP Server or Sendmail stops responding during startup</a></span></dt></dl></dd></dl></div><a id="idm225435859360" class="indexterm"></a><a id="idm225434783072" class="indext
erm"></a><a id="idm225468563920" class="indexterm"></a><a id="idm225465681104" class="indexterm"></a><a id="idm225474242112" class="indexterm"></a><a id="idm225446175216" class="indexterm"></a><a id="idm225467394640" class="indexterm"></a><a id="idm225446576368" class="indexterm"></a><div class="para">
+ </div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-trouble-x86" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 10. Troubleshooting Installation on an Intel or AMD System</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#idm219175807424">10.1. You are unable to boot Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="#idm219168676576">10.1.1. Are You Unable to Boot With Your RAID Card?</a></span></dt><dt><span class="section"><a href="#idm219174625744">10.1.2. Is Your System Displaying Signal 11 Errors?</a></span></dt></dl></dd><dt><span class="section"><a href="#idm219168475296">10.2. Trouble Beginning the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#idm219139851008">10.2.1. Problems with Booting into the Graphical Installation</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-trouble-install-x86">10.3. Trouble During the Installation</
a></span></dt><dd><dl><dt><span class="section"><a href="#s2-trouble-nodevicefound-x86">10.3.1. <code class="computeroutput">No devices found to install Fedora </code> Error Message</a></span></dt><dt><span class="section"><a href="#s2-trouble-tracebacks-x86">10.3.2. Reporting traceback messages</a></span></dt><dt><span class="section"><a href="#s2-trouble-part-tables-x86">10.3.3. Trouble with Partition Tables</a></span></dt><dt><span class="section"><a href="#s2-trouble-space-x86">10.3.4. Using Remaining Space</a></span></dt><dt><span class="section"><a href="#s2-trouble-completeparts-x86">10.3.5. Other Partitioning Problems</a></span></dt></dl></dd><dt><span class="section"><a href="#idm219181583248">10.4. Problems After Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-trouble-grub">10.4.1. Trouble With the Graphical GRUB Screen on an x86-based System?</a></span></dt><dt><span class="section"><a href="#s2-trouble-grub-command-line">10.4.2. Blocked
by a GRUB command line after upgrading?</a></span></dt><dt><span class="section"><a href="#Trouble_After_Booting-GUI">10.4.3. Booting into a Graphical Environment</a></span></dt><dt><span class="section"><a href="#idm219179265600">10.4.4. Problems with the X Window System (GUI)</a></span></dt><dt><span class="section"><a href="#idm219157531344">10.4.5. Problems with the X Server Crashing and Non-Root Users</a></span></dt><dt><span class="section"><a href="#idm219150647984">10.4.6. Problems When You Try to Log In</a></span></dt><dt><span class="section"><a href="#s2-trouble-ram">10.4.7. Is Your RAM Not Being Recognized?</a></span></dt><dt><span class="section"><a href="#idm219173233792">10.4.8. Your Printer Does Not Work</a></span></dt><dt><span class="section"><a href="#idm219114810544">10.4.9. Apache HTTP Server or Sendmail stops responding during startup</a></span></dt></dl></dd></dl></div><a id="idm219140696464" class="indexterm"></a><a id="idm219165814160" class="indext
erm"></a><a id="idm219125607616" class="indexterm"></a><a id="idm219182002384" class="indexterm"></a><a id="idm219167772912" class="indexterm"></a><a id="idm219131381072" class="indexterm"></a><a id="idm219156922928" class="indexterm"></a><a id="idm219138089952" class="indexterm"></a><div class="para">
This section discusses some common installation problems and their solutions.
</div><div class="para">
For debugging purposes, <span class="application"><strong>anaconda</strong></span> logs installation actions into files in the <code class="filename">/tmp</code> directory. These files include:
@@ -2082,7 +2080,7 @@ APPEND ksdevice=bootif</pre><div class="para">
If the installation fails, the messages from these files are consolidated into <code class="filename">/tmp/anaconda-tb-<em class="replaceable"><code>identifier</code></em></code>, where <em class="replaceable"><code>identifier</code></em> is a random string.
</div><div class="para">
All of the files above reside in the installer's ramdisk and are thus volatile. To make a permanent copy, copy those files to another system on the network using <code class="command">scp</code> on the installation image (not the other way round).
-</div><div class="section" id="idm225499886064"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm225499886064">10.1. You are unable to boot Fedora</h2></div></div></div><a id="idm225458444672" class="indexterm"></a><div class="section" id="idm225419970064"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225419970064">10.1.1. Are You Unable to Boot With Your RAID Card?</h3></div></div></div><a id="idm225478546192" class="indexterm"></a><a id="idm225444567744" class="indexterm"></a><div class="para">
+</div><div class="section" id="idm219175807424"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm219175807424">10.1. You are unable to boot Fedora</h2></div></div></div><a id="idm219125428848" class="indexterm"></a><div class="section" id="idm219168676576"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm219168676576">10.1.1. Are You Unable to Boot With Your RAID Card?</h3></div></div></div><a id="idm219176355984" class="indexterm"></a><a id="idm219115125824" class="indexterm"></a><div class="para">
If you have performed an installation and cannot boot your system properly, you may need to reinstall and create your partitions differently.
</div><div class="para">
Some BIOSes do not support booting from RAID cards. At the end of an installation, a text-based screen showing the boot loader prompt (for example, <code class="prompt">GRUB:</code> ) and a flashing cursor may be all that appears. If this is the case, you must repartition your system.
@@ -2092,7 +2090,7 @@ APPEND ksdevice=bootif</pre><div class="para">
You must also install your preferred boot loader (GRUB or LILO) on the MBR of a drive that is outside of the RAID array. This should be the same drive that hosts the <code class="filename">/boot/</code> partition.
</div><div class="para">
Once these changes have been made, you should be able to finish your installation and boot the system properly.
- </div></div><div class="section" id="idm225452658560"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225452658560">10.1.2. Is Your System Displaying Signal 11 Errors?</h3></div></div></div><a id="idm225435906704" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="idm219174625744"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm219174625744">10.1.2. Is Your System Displaying Signal 11 Errors?</h3></div></div></div><a id="idm219143242352" class="indexterm"></a><div class="para">
A signal 11 error, commonly known as a <em class="firstterm">segmentation fault</em>, means that the program accessed a memory location that was not assigned to it. A signal 11 error may be due to a bug in one of the software programs that is installed, or faulty hardware.
</div><div class="para">
If you receive a fatal signal 11 error during your installation, it is probably due to a hardware error in memory on your system's bus. Like other operating systems, Fedora places its own demands on your system's hardware. Some of this hardware may not be able to meet those demands, even if they work properly under another OS.
@@ -2104,15 +2102,15 @@ APPEND ksdevice=bootif</pre><div class="para">
<strong class="userinput"><code>linux rd.live.check</code></strong></pre><div class="para">
For more information concerning signal 11 errors, refer to:
</div><pre xml:lang="en-US" class="screen" lang="en-US">
- <a href="http://www.bitwizard.nl/sig11/">http://www.bitwizard.nl/sig11/</a></pre></div></div><div class="section" id="idm225471283760"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm225471283760">10.2. Trouble Beginning the Installation</h2></div></div></div><a id="idm225364722608" class="indexterm"></a><div class="section" id="idm225464520544"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225464520544">10.2.1. Problems with Booting into the Graphical Installation</h3></div></div></div><a id="idm225458774928" class="indexterm"></a><a id="idm225443558624" class="indexterm"></a><div class="para">
+ <a href="http://www.bitwizard.nl/sig11/">http://www.bitwizard.nl/sig11/</a></pre></div></div><div class="section" id="idm219168475296"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm219168475296">10.2. Trouble Beginning the Installation</h2></div></div></div><a id="idm219121842480" class="indexterm"></a><div class="section" id="idm219139851008"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm219139851008">10.2.1. Problems with Booting into the Graphical Installation</h3></div></div></div><a id="idm219149349984" class="indexterm"></a><a id="idm219149729712" class="indexterm"></a><div class="para">
There are some video cards that have trouble booting into the graphical installation program. If the installation program does not run using its default settings, it tries to run in a lower resolution mode. If that still fails, the installation program attempts to run in text mode.
</div><div class="para">
One possible solution is to use only a basic video driver during installation. You can do this either by selecting <span class="guilabel"><strong>Install Fedora in basic graphics mode</strong></span> on the boot menu, or using the <code class="command">xdriver=vesa</code> boot option at the boot prompt. Alternatively, you can force the installer to use a specific screen resolution with the <code class="command">resolution=</code> boot option. This option may be most helpful for laptop users. Another solution to try is the <code class="command">driver=</code> option to specify the driver that should be loaded for your video card. If this works, you should report it as a bug, because the installer failed to detect your video card automatically. Refer to <a class="xref" href="#ap-admin-options">Chapter 11, <em>Boot Options</em></a> for more information on boot options.
</div><div class="note" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
To disable frame buffer support and allow the installation program to run in text mode, try using the <code class="command">nofb</code> boot option. This command may be necessary for accessibility with some screen reading hardware.
- </div></div></div></div></div><div xml:lang="en-US" class="section" id="s1-trouble-install-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.3. Trouble During the Installation</h2></div></div></div><a id="idm225412390880" class="indexterm"></a><div class="section" id="s2-trouble-nodevicefound-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.3.1. <code class="computeroutput">No devices found to install Fedora </code> Error Message</h3></div></div></div><a id="idm225475802976" class="indexterm"></a><div class="para">
+ </div></div></div></div></div><div xml:lang="en-US" class="section" id="s1-trouble-install-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.3. Trouble During the Installation</h2></div></div></div><a id="idm219074459568" class="indexterm"></a><div class="section" id="s2-trouble-nodevicefound-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.3.1. <code class="computeroutput">No devices found to install Fedora </code> Error Message</h3></div></div></div><a id="idm219144943200" class="indexterm"></a><div class="para">
If you receive an error message stating <code class="computeroutput">No devices found to install Fedora</code>, there is probably a SCSI controller that is not being recognized by the installation program.
-</div></div><div class="section" id="s2-trouble-tracebacks-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.3.2. Reporting traceback messages</h3></div></div></div><a id="idm225417643472" class="indexterm"></a><a id="idm225457989072" class="indexterm"></a><a id="idm225365145712" class="indexterm"></a><div class="para">
+</div></div><div class="section" id="s2-trouble-tracebacks-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.3.2. Reporting traceback messages</h3></div></div></div><a id="idm219167027008" class="indexterm"></a><a id="idm219138492416" class="indexterm"></a><a id="idm219178089184" class="indexterm"></a><div class="para">
If the installer encounters an error during the graphical installation process, it presents you with a crash reporting dialog box:
</div><div class="figure" xml:lang="en-US" lang="en-US"><div class="figure-contents"><div class="mediaobject"><img src="images/crashreporting/crashreporting.png" width="444" alt="The Crash Reporting Dialog Box" /><div class="longdesc"><div class="para">
An unhandled exception has occurred. This is most likely a bug. Please save a copy of the detailed exception and file a bug report against anaconda at https://bugzilla.redhat.com/bugzilla/
@@ -2154,7 +2152,7 @@ APPEND ksdevice=bootif</pre><div class="para">
Review the individual files that will be sent to Bugzilla.
</div></div></div></div><h6>Figure 10.7. Review the files to be sent</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
When the dialog reports that processing has finished, click <span class="guilabel"><strong>Show log</strong></span> to view details of the process or <span class="guilabel"><strong>Close</strong></span> to return to the initial crash reporting dialog box.
- </div></li></ol></div></div><div class="section" id="s2-trouble-part-tables-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.3.3. Trouble with Partition Tables</h3></div></div></div><a id="idm225451223936" class="indexterm"></a><a id="idm225439533872" class="indexterm"></a><div class="para">
+ </div></li></ol></div></div><div class="section" id="s2-trouble-part-tables-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.3.3. Trouble with Partition Tables</h3></div></div></div><a id="idm219170344624" class="indexterm"></a><a id="idm219173798048" class="indexterm"></a><div class="para">
If you receive an error after setting up your partitions (<a class="xref" href="#s1-diskpartsetup-x86">Section 9.11, “Storage and partitioning”</a>) that says something similar to
</div><div xml:lang="en-US" class="blockquote" lang="en-US"><blockquote xml:lang="en-US" class="blockquote" lang="en-US"><div class="para">
The partition table on device hda was unreadable. To create new partitions it must be initialized, causing the loss of ALL DATA on this drive.
@@ -2164,11 +2162,11 @@ APPEND ksdevice=bootif</pre><div class="para">
Users who have used programs such as <span class="application"><strong>EZ-BIOS</strong></span> have experienced similar problems, causing data to be lost (assuming the data was not backed up before the installation began) that could not be recovered.
</div><div class="para">
No matter what type of installation you are performing, backups of the existing data on your systems should always be made.
-</div></div><div class="section" id="s2-trouble-space-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.3.4. Using Remaining Space</h3></div></div></div><a id="idm225451286624" class="indexterm"></a><div class="para">
+</div></div><div class="section" id="s2-trouble-space-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.3.4. Using Remaining Space</h3></div></div></div><a id="idm219169503216" class="indexterm"></a><div class="para">
You have a <code class="filename">swap</code> and a <code class="filename">/</code> (root) partition created, and you have selected the root partition to use the remaining space, but it does not fill the hard drive.
</div><div class="para">
If your hard drive is more than 1024 cylinders, you must create a <code class="filename">/boot</code> partition if you want the <code class="filename">/</code> (root) partition to use all of the remaining space on your hard drive.
- </div></div><div class="section" id="s2-trouble-completeparts-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.3.5. Other Partitioning Problems</h3></div></div></div><a id="idm225415687568" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-trouble-completeparts-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.3.5. Other Partitioning Problems</h3></div></div></div><a id="idm219168608064" class="indexterm"></a><div class="para">
If you create partitions manually, but cannot return to the Installation Summary Menu, you probably have not created all the partitions necessary for installation to proceed.
</div><div class="para">
You must have the following partitions as a bare minimum:
@@ -2178,13 +2176,13 @@ APPEND ksdevice=bootif</pre><div class="para">
A <swap> partition of type swap
</div></li></ul></div><div class="note" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
When defining a partition's type as swap, do not assign it a mount point. <span class="application"><strong>Anaconda</strong></span> automatically assigns the mount point for you.
- </div></div></div></div></div><div class="section" id="idm225448803200"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm225448803200">10.4. Problems After Installation</h2></div></div></div><a id="idm225464106416" class="indexterm"></a><div xml:lang="en-US" class="section" id="s2-trouble-grub" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.4.1. Trouble With the Graphical GRUB Screen on an x86-based System?</h3></div></div></div><a id="idm225439491584" class="indexterm"></a><div class="para">
+ </div></div></div></div></div><div class="section" id="idm219181583248"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm219181583248">10.4. Problems After Installation</h2></div></div></div><a id="idm219130902336" class="indexterm"></a><div xml:lang="en-US" class="section" id="s2-trouble-grub" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.4.1. Trouble With the Graphical GRUB Screen on an x86-based System?</h3></div></div></div><a id="idm219182601536" class="indexterm"></a><div class="para">
If you are experiencing problems with GRUB, such as the boot menu being corrupt and unusable, you may need to disable the graphical boot screen. To do this, become the root user and add the following line to the <code class="filename">/etc/default/grub</code> file:
</div><pre class="screen">GRUB_TERMINAL=console</pre><div class="para">
Refresh the <code class="filename">grub.cfg</code> file by running the following command with root privileges so the changes will take effect:
</div><pre class="screen"><code class="command">grub2-mkconfig --output=/boot/grub2/grub.cfg</code></pre><div class="para">
To re-enable the graphical boot screen, remove the newly added line or comment it out by inserting the <code class="computeroutput">#</code> character at the beginning of the line.
- </div></div><div xml:lang="en-US" class="section" id="s2-trouble-grub-command-line" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.4.2. Blocked by a GRUB command line after upgrading?</h3></div></div></div><a id="idm225448631392" class="indexterm"></a><div class="para">
+ </div></div><div xml:lang="en-US" class="section" id="s2-trouble-grub-command-line" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.4.2. Blocked by a GRUB command line after upgrading?</h3></div></div></div><a id="idm219174196208" class="indexterm"></a><div class="para">
If you have restarted your machine after upgrading Fedora but cannot progress beyond the <span class="application"><strong>GRUB</strong></span> command line, you will need to issue commands to boot the operating system and then make the changes persistent once Fedora has loaded.
</div><div class="procedure"><ol class="1"><li class="step"><div class="para">
At the <span class="application"><strong>GRUB</strong></span> command line, display the superseded <span class="application"><strong>GRUB</strong></span> configuration file with the following command:
@@ -2196,7 +2194,7 @@ APPEND ksdevice=bootif</pre><div class="para">
Run the <code class="command">boot</code> command.
</div></li><li class="step"><div class="para">
Once Fedora has loaded, refresh the <span class="application"><strong>GRUB</strong></span> configuration file to make the changes persistent:
- </div><pre class="screen"><code class="command">grub2-mkconfig --output=/boot/grub2/grub.cfg</code></pre></li></ol></div></div><div class="section" id="Trouble_After_Booting-GUI"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.4.3. Booting into a Graphical Environment</h3></div></div></div><a id="idm225472190720" class="indexterm"></a><a id="idm225456088080" class="indexterm"></a><a id="idm225444104864" class="indexterm"></a><div class="para">
+ </div><pre class="screen"><code class="command">grub2-mkconfig --output=/boot/grub2/grub.cfg</code></pre></li></ol></div></div><div class="section" id="Trouble_After_Booting-GUI"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.4.3. Booting into a Graphical Environment</h3></div></div></div><a id="idm219205461136" class="indexterm"></a><a id="idm219152302320" class="indexterm"></a><a id="idm219153614176" class="indexterm"></a><div class="para">
If you have installed the X Window System but are not seeing a graphical desktop environment once you log into your system, you can start the X Window System graphical interface using the command <code class="command">startx</code>.
</div><div class="para">
Once you enter this command and press <span class="keycap"><strong>Enter</strong></span>, the graphical desktop environment is displayed.
@@ -2216,15 +2214,15 @@ APPEND ksdevice=bootif</pre><div class="para">
You will be prompted to confirm whether the file should be overwritten. Press <span class="keycap"><strong>y</strong></span> followed by <span class="keycap"><strong>Enter</strong></span>.
</div><div class="para">
The next time you log in after rebooting your system, you are presented with a graphical login prompt.
-</div></div><div xml:lang="en-US" class="section" id="idm225460054624" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225460054624">10.4.4. Problems with the X Window System (GUI)</h3></div></div></div><a id="idm225421554720" class="indexterm"></a><div class="para">
+</div></div><div xml:lang="en-US" class="section" id="idm219179265600" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm219179265600">10.4.4. Problems with the X Window System (GUI)</h3></div></div></div><a id="idm219126652048" class="indexterm"></a><div class="para">
If you are having trouble getting X (the X Window System) to start, you may not have installed it during your installation.
</div><div class="para">
If you want X, you can either install the packages from the Fedora installation media or perform an upgrade.
</div><div class="para">
If you elect to upgrade, select the X Window System packages, and choose GNOME, KDE, or both, during the upgrade package selection process.
</div><div class="para">
- Refer to <a class="xref" href="#sn-switching-to-gui-login">Section 17.3, “Switching to a Graphical Login”</a> for more detail on installing a desktop environment.
- </div></div><div xml:lang="en-US" class="section" id="idm225503142160" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225503142160">10.4.5. Problems with the X Server Crashing and Non-Root Users</h3></div></div></div><a id="idm225456305728" class="indexterm"></a><div class="para">
+ Refer to <a class="xref" href="#sn-switching-to-gui-login">Section 17.2, “Switching to a Graphical Login”</a> for more detail on installing a desktop environment.
+ </div></div><div xml:lang="en-US" class="section" id="idm219157531344" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm219157531344">10.4.5. Problems with the X Server Crashing and Non-Root Users</h3></div></div></div><a id="idm219203115456" class="indexterm"></a><div class="para">
If you are having trouble with the X server crashing when anyone logs in, you may have a full file system (or, a lack of available hard drive space).
</div><div class="para">
To verify that this is the problem you are experiencing, run the following command:
@@ -2232,7 +2230,7 @@ APPEND ksdevice=bootif</pre><div class="para">
The <code class="command">df</code> command should help you diagnose which partition is full. For additional information about <code class="command">df</code> and an explanation of the options available (such as the <code class="option">-h</code> option used in this example), refer to the <code class="command">df</code> man page by typing <code class="command">man df</code> at a shell prompt.
</div><div class="para">
A key indicator is 100% full or a percentage above 90% or 95% on a partition. The <code class="filename">/home/</code> and <code class="filename">/tmp/</code> partitions can sometimes fill up quickly with user files. You can make some room on that partition by removing old files. After you free up some disk space, try running X as the user that was unsuccessful before.
- </div></div><div class="section" id="idm225461616880"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225461616880">10.4.6. Problems When You Try to Log In</h3></div></div></div><a id="idm225501114624" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="idm219150647984"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm219150647984">10.4.6. Problems When You Try to Log In</h3></div></div></div><a id="idm219183080464" class="indexterm"></a><div class="para">
If you did not create a user account in the Configuration Menu and Progress Screen, switch to a console by pressing <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F2</strong></span>, log in as root and use the password you assigned to root.
</div><div class="para">
If you cannot remember your root password, boot your system as <code class="command">linux single</code>.
@@ -2253,7 +2251,7 @@ APPEND ksdevice=bootif</pre><div class="para">
If you cannot remember your user account password, you must become root. To become root, type <code class="command">su -</code> and enter your root password when prompted. Then, type <code class="command">passwd <username></code>. This allows you to enter a new password for the specified user account.
</div><div class="para">
If the graphical login screen does not appear, check your hardware for compatibility issues.
-</div></div><div xml:lang="en-US" class="section" id="s2-trouble-ram" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.4.7. Is Your RAM Not Being Recognized?</h3></div></div></div><a id="idm225471339280" class="indexterm"></a><div class="para">
+</div></div><div xml:lang="en-US" class="section" id="s2-trouble-ram" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.4.7. Is Your RAM Not Being Recognized?</h3></div></div></div><a id="idm219184740320" class="indexterm"></a><div class="para">
Sometimes, the kernel does not recognize all of your memory (RAM). The following procedure will allow you to confirm this and then adjust the kernel if necessary.
</div><div class="procedure"><ol class="1"><li class="step"><div class="para">
Run the <code class="command">cat /proc/meminfo</code> command and verify that the displayed quantity is the same as the known amount of RAM in your system. If they are not equal, you can first make a temporary change to confirm whether editing the kernel will be effective.
@@ -2285,13 +2283,13 @@ menuentry 'Fedora Linux, with Linux 3.1.0-0.rc6.git0.3.fc16.x86_64'
set root=(hd0,1)
linux /vmlinuz-(2.6.32.130.el6.i686 ro root=UUID=04a07c13-e6bf-6d5a-b207-002689545705 mem=8192M
initrd /initrd-(2.6.32.130.el6.i686.img
-</pre></div><div xml:lang="en-US" class="section" id="idm225465817296" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225465817296">10.4.8. Your Printer Does Not Work</h3></div></div></div><a id="idm225456630752" class="indexterm"></a><div class="para">
+</pre></div><div xml:lang="en-US" class="section" id="idm219173233792" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm219173233792">10.4.8. Your Printer Does Not Work</h3></div></div></div><a id="idm219157077488" class="indexterm"></a><div class="para">
If you are not sure how to set up your printer or are having trouble getting it to work properly, try using the <span class="application"><strong>Printer Configuration Tool</strong></span>.
</div><div class="para">
Type the <code class="command">system-config-printer</code> command at a shell prompt to launch the <span class="application"><strong>Printer Configuration Tool</strong></span>. If you are not root, it prompts you for the root password to continue.
- </div></div><div xml:lang="en-US" class="section" id="idm225447278528" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225447278528">10.4.9. Apache HTTP Server or Sendmail stops responding during startup</h3></div></div></div><a id="idm225474039840" class="indexterm"></a><a id="idm225455985824" class="indexterm"></a><div class="para">
+ </div></div><div xml:lang="en-US" class="section" id="idm219114810544" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm219114810544">10.4.9. Apache HTTP Server or Sendmail stops responding during startup</h3></div></div></div><a id="idm219184201552" class="indexterm"></a><a id="idm219133926464" class="indexterm"></a><div class="para">
If <span class="application"><strong>Apache HTTP Server</strong></span> (<span class="application"><strong>httpd</strong></span>) or <span class="application"><strong>Sendmail</strong></span> stops responding during startup, make sure the following line is in the <code class="filename">/etc/hosts</code> file:
- </div><pre class="screen">127.0.0.1 localhost.localdomain localhost</pre></div></div></div></div><div class="part" id="pt-Advanced_installation_options"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part II. Advanced installation options</h1></div></div></div><div class="partintro" id="idm225445753904"><div></div><div class="para">
+ </div><pre class="screen">127.0.0.1 localhost.localdomain localhost</pre></div></div></div></div><div class="part" id="pt-Advanced_installation_options"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part II. Advanced installation options</h1></div></div></div><div class="partintro" id="idm219183069776"><div></div><div class="para">
This part of the <em class="citetitle">Fedora Installation Guide</em> covers more advanced or uncommon methods of installing Fedora, including:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
boot options.
@@ -2301,7 +2299,7 @@ initrd /initrd-(2.6.32.130.el6.i686.img
installing through VNC.
</div></li><li class="listitem"><div class="para">
using <span class="application"><strong>kickstart</strong></span> to automate the installation process.
- </div></li></ul></div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="#ap-admin-options">11. Boot Options</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-bootoptions-installer">11.1. Configuring the Installation System at the Boot Menu</a></span></dt><dt><span class="section"><a href="#sn-bootoptions-hardware">11.2. Enhancing Hardware Support</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-bootoptions-hwdetection">11.2.1. Overriding Automatic Hardware Detection</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-boot-options-maintenance">11.3. Using the Maintenance Boot Modes</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-boot-options-memtest">11.3.1. Loading the Memory (RAM) Testing Mode</a></span></dt><dt><span class="section"><a href="#sect-boot-options-mediacheck">11.3.2. Verifying Boot Media</a></span></dt><dt><span class="section"><a href="#sect-
boot-options-rescue">11.3.3. Booting Your Computer in Rescue Mode</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ap-medialess-install">12. Installing Without Media</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-medialess-getting-files">12.1. Retrieving Boot Files</a></span></dt><dt><span class="section"><a href="#sn-medialess-editing-grub-conf">12.2. Editing the <span class="application"><strong>GRUB</strong></span> Configuration</a></span></dt><dt><span class="section"><a href="#sn-medialess-booting">12.3. Booting to Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ap-install-server">13. Setting Up an Installation Server</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-install-cobbler">13.1. Setting Up <span class="package">cobbler</span></a></span></dt><dt><span class="section"><a href="#sn-cobbler-setup-distro">13.2. Setting Up the Distribution</a></span></dt><dt><span class="section"><a href="#s
n-cobbler-mirror">13.3. Mirroring a Network Location</a></span></dt><dt><span class="section"><a href="#sn-cobbler-import">13.4. Importing the Distribution</a></span></dt><dt><span class="section"><a href="#sn-pxe-server-manual">13.5. Manually configure a PXE server</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-netboot-netserver">13.5.1. Setting up the Network Server</a></span></dt><dt><span class="section"><a href="#s1-netboot-pxe-config">13.5.2. PXE Boot Configuration</a></span></dt><dt><span class="section"><a href="#idm225434414752">13.5.3. Starting the <code class="command">tftp</code> Server</a></span></dt><dt><span class="section"><a href="#s2-netboot-custom-msg">13.5.4. Adding a Custom Boot Message</a></span></dt><dt><span class="section"><a href="#netboot-performing">13.5.5. Performing the PXE Installation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#vncwhitepaperadded">14. Installing Through VNC</a></span></dt><dd><dl><dt><
span class="section"><a href="#VNC_Whitepaper-vnc-viewer">14.1. VNC Viewer</a></span></dt><dt><span class="section"><a href="#VNC_Whitepaper-vnc-modes-in-anaconda">14.2. VNC Modes in Anaconda</a></span></dt><dd><dl><dt><span class="section"><a href="#VNC_Whitepaper-vnc-direct-mode">14.2.1. Direct Mode</a></span></dt><dt><span class="section"><a href="#VNC_Whitepaper-vnc-connect-mode">14.2.2. Connect Mode</a></span></dt></dl></dd><dt><span class="section"><a href="#VNC_Whitepaper-installation">14.3. Installation Using VNC</a></span></dt><dd><dl><dt><span class="section"><a href="#VNC_Whitepaper-installation-example">14.3.1. Installation Example</a></span></dt><dt><span class="section"><a href="#VNC_Whitepaper-kickstart-installation">14.3.2. Kickstart Considerations</a></span></dt><dt><span class="section"><a href="#VNC_Whitepaper-firewall-considerations">14.3.3. Firewall Considerations</a></span></dt></dl></dd><dt><span class="section"><a href="#VNC_Whitepaper-references">14.
4. References</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-kickstart2">15. Kickstart Installations</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-kickstart2-whatis">15.1. What are Kickstart Installations?</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-howuse">15.2. How Do You Perform a Kickstart Installation?</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-file">15.3. Creating the Kickstart File</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-options">15.4. Kickstart Options</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kickstart2-options-part-examples">15.4.1. Advanced Partitioning Example</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-packageselection">15.5. Package Selection</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-preinstallconfig">15.6. Pre-installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="#
s2-kickstart2-prescript-example">15.6.1. Example</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-postinstallconfig">15.7. Post-installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kickstart2-post-examples">15.7.1. Example</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-putkickstarthere">15.8. Making the Kickstart File Available</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kickstart2-boot-media">15.8.1. Creating Kickstart Boot Media</a></span></dt><dt><span class="section"><a href="#s2-kickstart2-networkbased">15.8.2. Making the Kickstart File Available on the Network</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-install-tree">15.9. Making the Installation Tree Available</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-startinginstall">15.10. Starting a Kickstart Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href
="#ch-redhat-config-kickstart">16. <span class="application"><strong>Kickstart Configurator</strong></span></a></span></dt><dd><dl><dt><span class="section"><a href="#s1-redhat-config-kickstart-basic">16.1. Basic Configuration</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-install">16.2. Installation Method</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-bootloader">16.3. Boot Loader Options</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-partitions">16.4. Partition Information</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-kickstart-create-part">16.4.1. Creating Partitions</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-redhat-config-kickstart-network">16.5. Network Configuration</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-auth">16.6. Authentication</a></span></dt><dt><span class="section"><a href="#s1-redh
at-config-kickstart-firewall">16.7. Firewall Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-kickstart-firewall-selinux">16.7.1. SELinux Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-redhat-config-kickstart-xconfig">16.8. Display Configuration</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-pkgs">16.9. Package Selection</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-prescript">16.10. Pre-Installation Script</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-postinstall">16.11. Post-Installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-kickstart-nochroot">16.11.1. Chroot Environment</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-kickstart-interpreter">16.11.2. Use an Interpreter</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-redhat-config
-kickstart-savefile">16.12. Saving the File</a></span></dt></dl></dd></dl></div></div><div xml:lang="en-US" class="chapter" id="ap-admin-options" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 11. Boot Options</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#sn-bootoptions-installer">11.1. Configuring the Installation System at the Boot Menu</a></span></dt><dt><span class="section"><a href="#sn-bootoptions-hardware">11.2. Enhancing Hardware Support</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-bootoptions-hwdetection">11.2.1. Overriding Automatic Hardware Detection</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-boot-options-maintenance">11.3. Using the Maintenance Boot Modes</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-boot-options-memtest">11.3.1. Loading the Memory (RAM) Testing Mode</a></span></dt><dt><span class="section"><a href="#sect-boot-options-
mediacheck">11.3.2. Verifying Boot Media</a></span></dt><dt><span class="section"><a href="#sect-boot-options-rescue">11.3.3. Booting Your Computer in Rescue Mode</a></span></dt></dl></dd></dl></div><a id="idm225458193008" class="indexterm"></a><a id="idm225468178272" class="indexterm"></a><div class="para">
+ </div></li></ul></div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="#ap-admin-options">11. Boot Options</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-bootoptions-installer">11.1. Configuring the Installation System at the Boot Menu</a></span></dt><dt><span class="section"><a href="#sn-bootoptions-hardware">11.2. Enhancing Hardware Support</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-bootoptions-hwdetection">11.2.1. Overriding Automatic Hardware Detection</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-boot-options-maintenance">11.3. Using the Maintenance Boot Modes</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-boot-options-memtest">11.3.1. Loading the Memory (RAM) Testing Mode</a></span></dt><dt><span class="section"><a href="#sect-boot-options-mediacheck">11.3.2. Verifying Boot Media</a></span></dt><dt><span class="section"><a href="#sect-
boot-options-rescue">11.3.3. Booting Your Computer in Rescue Mode</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ap-medialess-install">12. Installing Without Media</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-medialess-getting-files">12.1. Retrieving Boot Files</a></span></dt><dt><span class="section"><a href="#sn-medialess-editing-grub-conf">12.2. Editing the <span class="application"><strong>GRUB</strong></span> Configuration</a></span></dt><dt><span class="section"><a href="#sn-medialess-booting">12.3. Booting to Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ap-install-server">13. Setting Up an Installation Server</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-install-cobbler">13.1. Setting Up <span class="package">cobbler</span></a></span></dt><dt><span class="section"><a href="#sn-cobbler-setup-distro">13.2. Setting Up the Distribution</a></span></dt><dt><span class="section"><a href="#s
n-cobbler-mirror">13.3. Mirroring a Network Location</a></span></dt><dt><span class="section"><a href="#sn-cobbler-import">13.4. Importing the Distribution</a></span></dt><dt><span class="section"><a href="#sn-pxe-server-manual">13.5. Manually configure a PXE server</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-netboot-netserver">13.5.1. Setting up the Network Server</a></span></dt><dt><span class="section"><a href="#s1-netboot-pxe-config">13.5.2. PXE Boot Configuration</a></span></dt><dt><span class="section"><a href="#idm219163541472">13.5.3. Starting the <code class="command">tftp</code> Server</a></span></dt><dt><span class="section"><a href="#s2-netboot-custom-msg">13.5.4. Adding a Custom Boot Message</a></span></dt><dt><span class="section"><a href="#netboot-performing">13.5.5. Performing the PXE Installation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#vncwhitepaperadded">14. Installing Through VNC</a></span></dt><dd><dl><dt><
span class="section"><a href="#VNC_Whitepaper-vnc-viewer">14.1. VNC Viewer</a></span></dt><dt><span class="section"><a href="#VNC_Whitepaper-vnc-modes-in-anaconda">14.2. VNC Modes in Anaconda</a></span></dt><dd><dl><dt><span class="section"><a href="#VNC_Whitepaper-vnc-direct-mode">14.2.1. Direct Mode</a></span></dt><dt><span class="section"><a href="#VNC_Whitepaper-vnc-connect-mode">14.2.2. Connect Mode</a></span></dt></dl></dd><dt><span class="section"><a href="#VNC_Whitepaper-installation">14.3. Installation Using VNC</a></span></dt><dd><dl><dt><span class="section"><a href="#VNC_Whitepaper-installation-example">14.3.1. Installation Example</a></span></dt><dt><span class="section"><a href="#VNC_Whitepaper-kickstart-installation">14.3.2. Kickstart Considerations</a></span></dt><dt><span class="section"><a href="#VNC_Whitepaper-firewall-considerations">14.3.3. Firewall Considerations</a></span></dt></dl></dd><dt><span class="section"><a href="#VNC_Whitepaper-references">14.
4. References</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-kickstart2">15. Kickstart Installations</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-kickstart2-whatis">15.1. What are Kickstart Installations?</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-howuse">15.2. How Do You Perform a Kickstart Installation?</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-file">15.3. Creating the Kickstart File</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-options">15.4. Kickstart Options</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kickstart2-options-part-examples">15.4.1. Advanced Partitioning Example</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-packageselection">15.5. Package Selection</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-preinstallconfig">15.6. Pre-installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="#
s2-kickstart2-prescript-example">15.6.1. Example</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-postinstallconfig">15.7. Post-installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kickstart2-post-examples">15.7.1. Example</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-putkickstarthere">15.8. Making the Kickstart File Available</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kickstart2-boot-media">15.8.1. Creating Kickstart Boot Media</a></span></dt><dt><span class="section"><a href="#s2-kickstart2-networkbased">15.8.2. Making the Kickstart File Available on the Network</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-install-tree">15.9. Making the Installation Tree Available</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-startinginstall">15.10. Starting a Kickstart Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href
="#ch-redhat-config-kickstart">16. <span class="application"><strong>Kickstart Configurator</strong></span></a></span></dt><dd><dl><dt><span class="section"><a href="#s1-redhat-config-kickstart-basic">16.1. Basic Configuration</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-install">16.2. Installation Method</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-bootloader">16.3. Boot Loader Options</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-partitions">16.4. Partition Information</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-kickstart-create-part">16.4.1. Creating Partitions</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-redhat-config-kickstart-network">16.5. Network Configuration</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-auth">16.6. Authentication</a></span></dt><dt><span class="section"><a href="#s1-redh
at-config-kickstart-firewall">16.7. Firewall Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-kickstart-firewall-selinux">16.7.1. SELinux Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-redhat-config-kickstart-xconfig">16.8. Display Configuration</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-pkgs">16.9. Package Selection</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-prescript">16.10. Pre-Installation Script</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-postinstall">16.11. Post-Installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-kickstart-nochroot">16.11.1. Chroot Environment</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-kickstart-interpreter">16.11.2. Use an Interpreter</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-redhat-config
-kickstart-savefile">16.12. Saving the File</a></span></dt></dl></dd></dl></div></div><div xml:lang="en-US" class="chapter" id="ap-admin-options" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 11. Boot Options</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#sn-bootoptions-installer">11.1. Configuring the Installation System at the Boot Menu</a></span></dt><dt><span class="section"><a href="#sn-bootoptions-hardware">11.2. Enhancing Hardware Support</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-bootoptions-hwdetection">11.2.1. Overriding Automatic Hardware Detection</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-boot-options-maintenance">11.3. Using the Maintenance Boot Modes</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-boot-options-memtest">11.3.1. Loading the Memory (RAM) Testing Mode</a></span></dt><dt><span class="section"><a href="#sect-boot-options-
mediacheck">11.3.2. Verifying Boot Media</a></span></dt><dt><span class="section"><a href="#sect-boot-options-rescue">11.3.3. Booting Your Computer in Rescue Mode</a></span></dt></dl></dd></dl></div><a id="idm219132299424" class="indexterm"></a><a id="idm219082741360" class="indexterm"></a><div class="para">
The Fedora installation system includes a range of functions and options for administrators. To use boot options, append them to the boot command line. To access the command line on a system that displays a graphical boot screen, press the <span class="keycap"><strong>Tab</strong></span> key while one of the boot options on the screen is highlighted, or press the <span class="keycap"><strong>Esc</strong></span> key at any point in the boot menu. Multiple options added to the boot line need to be separated by a single space.
</div><div class="para">
Throughout this chapter, some options are presented ending an "equals" sign ('<code class="literal">=</code>'). These options require a value to be specified. For example, the <code class="option">inst.vncpassword=</code> option must also contain a password — for example, <code class="option">inst.vncpassword=testpasswd</code>. Other options are presented without the <code class="literal">=</code> sign; these options are booleans. This means that you either use them without specifying a value, or you can append either <code class="literal">=1</code> or <code class="literal">=0</code> to enable or disable them, respectively. For example, the <code class="option">rd.live.check</code> option is the same as <code class="option">rd.live.check=1</code>, and using <code class="option">rd.live.check=0</code> is exactly the same as not using the option at all.
@@ -2315,7 +2313,7 @@ initrd /initrd-(2.6.32.130.el6.i686.img
In addition to the options described in this chapter, the boot prompt also accepts valid <span class="package">dracut</span> kernel options. A list of these options is available as the <code class="systemitem">dracut.cmdline(7)</code> man page.
</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
Boot options specific to the installer always start with <code class="literal">inst.</code> in this guide. Currently, this prefix is optional, for example, <code class="option">inst.resolution=</code> will work exactly the same as <code class="option">resolution=</code>. However, it is expected that Anaconda will require the <code class="literal">inst.</code> prefix in future releases.
- </div></div></div><div class="variablelist" id="list-boot-options-source"><h6>Specifying the Installation Source</h6><a id="idm225465777136" class="indexterm"></a><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="option">inst.repo=</code></span></dt><dd><div class="para">
+ </div></div></div><div class="variablelist" id="list-boot-options-source"><h6>Specifying the Installation Source</h6><a id="idm219168013936" class="indexterm"></a><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="option">inst.repo=</code></span></dt><dd><div class="para">
Specifies the installation source — that is, a location where the installer can find the images and packages it needs. For example:
</div><pre class="screen"><code class="option">inst.repo=cdrom</code></pre><div class="para">
The target must be either:
@@ -2356,10 +2354,10 @@ initrd /initrd-(2.6.32.130.el6.i686.img
</td></tr><tr><td class="" align="left">
NFS Server
</td><td class="" align="left">
- <code class="option">inst.repo=nfs:[<em class="replaceable"><code>options</code></em>:]<em class="replaceable"><code>server</code></em>:/<em class="replaceable"><code>path</code></em></code> <a href="#ftn.idm225447269552" class="footnote"><sup class="footnote" id="idm225447269552">[a]</sup></a>
- </td></tr></tbody><tbody class="footnotes"><tr><td colspan="2"><div id="ftn.idm225447269552" class="footnote"><div class="para"><a href="#idm225447269552" class="para"><sup class="para">[a] </sup></a>
+ <code class="option">inst.repo=nfs:[<em class="replaceable"><code>options</code></em>:]<em class="replaceable"><code>server</code></em>:/<em class="replaceable"><code>path</code></em></code> <a href="#ftn.idm219143245104" class="footnote"><sup class="footnote" id="idm219143245104">[a]</sup></a>
+ </td></tr></tbody><tbody class="footnotes"><tr><td colspan="2"><div id="ftn.idm219143245104" class="footnote"><div class="para"><a href="#idm219143245104" class="para"><sup class="para">[a] </sup></a>
This option uses NFS protocol version 3 by default. To use a different version, add <code class="option">+nfsvers=<em class="replaceable"><code>X</code></em></code> to <em class="replaceable"><code>options</code></em>.
- </div></div></td></tr></tbody></table></div></div><br class="table-break" /><a id="idm225419266560" class="indexterm"></a><div class="para">
+ </div></div></td></tr></tbody></table></div></div><br class="table-break" /><a id="idm219170291952" class="indexterm"></a><div class="para">
Disk device names may be specified using the following formats:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
Kernel device name, for example <code class="systemitem">/dev/sda1</code> or <code class="systemitem">sdb2</code>
@@ -2369,9 +2367,9 @@ initrd /initrd-(2.6.32.130.el6.i686.img
File system UUID, for example <code class="systemitem">UUID=8176c7bf-04ff-403a-a832-9557f94e61db</code>
</div></li></ul></div><div class="para">
Non-alphanumeric characters must be represented as <code class="literal">\x<em class="replaceable"><code>NN</code></em></code>, where <em class="replaceable"><code>NN</code></em> is the hexadecimal representation of the character. For example, <code class="literal">\x20</code> is a white space ('<code class="literal"> </code>').
- </div></dd><dt class="varlistentry"><span class="term"><code class="option">inst.stage2=</code></span></dt><dd><a id="idm225461157936" class="indexterm"></a><div class="para">
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">inst.stage2=</code></span></dt><dd><a id="idm219084407920" class="indexterm"></a><div class="para">
Specifies the location of the installer runtime image to be loaded. The syntax is the same as in <a class="xref" href="#list-boot-options-source">Specifying the Installation Source</a>. This option will ignore everything except for the image itself, it is not possible to use it to specify the location of packages.
- </div></dd><dt class="varlistentry"><span class="term"><code class="option">inst.dd=</code></span></dt><dd><a id="idm225460168800" class="indexterm"></a><div class="para">
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">inst.dd=</code></span></dt><dd><a id="idm219176428752" class="indexterm"></a><div class="para">
If you need to perform a driver update during the installation, use the <code class="option">inst.dd=</code> option. It can be used multiple times. The location of a driver rpm package can be specified using any of the formats detailed in <a class="xref" href="#list-boot-options-source">Specifying the Installation Source</a>. For example:
</div><pre class="screen"><code class="option">inst.dd=cdrom</code></pre></dd></dl></div><div class="variablelist" id="list-boot-options-kickstart"><h6>Kickstart Boot Options</h6><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="option">inst.ks=</code></span></dt><dd><div class="para">
Gives the location of a Kickstart file to be used to automate the installation. Locations can be specified using any of the formats valid for <code class="option">inst.repo</code>. See <a class="xref" href="#list-boot-options-source">Specifying the Installation Source</a> for details.
@@ -2397,7 +2395,7 @@ initrd /initrd-(2.6.32.130.el6.i686.img
This can be useful when using <code class="option">inst.ks=http</code> to provision systems.
</div></dd><dt class="varlistentry"><span class="term"><code class="option">inst.ks.sendsn</code></span></dt><dd><div class="para">
Adds a header to outgoing <code class="systemitem">HTTP</code> requests. This header will contain the system's serial number, read from <code class="filename">/sys/class/dmi/id/product_serial</code>. The header has the following syntax:
- </div><pre class="screen"><code class="literal">X-System-Serial-Number: <em class="replaceable"><code>R8VA23D</code></em></code></pre></dd></dl></div><div class="variablelist" id="list-boot-options-display"><h6>Console, Environment and Display Options</h6><a id="idm225501265232" class="indexterm"></a><a id="idm225472765648" class="indexterm"></a><a id="idm225472764208" class="indexterm"></a><a id="idm225440902096" class="indexterm"></a><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="option">console=</code></span></dt><dd><div class="para">
+ </div><pre class="screen"><code class="literal">X-System-Serial-Number: <em class="replaceable"><code>R8VA23D</code></em></code></pre></dd></dl></div><div class="variablelist" id="list-boot-options-display"><h6>Console, Environment and Display Options</h6><a id="idm219122530720" class="indexterm"></a><a id="idm219184796640" class="indexterm"></a><a id="idm219184795200" class="indexterm"></a><a id="idm219178390176" class="indexterm"></a><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="option">console=</code></span></dt><dd><div class="para">
This kernel option specifies a device to be used as the primary console. For example, if you want to use a console on the first serial port, use <code class="option">console=ttyS0</code>. Implies the <code class="option">inst.text</code> option.
</div><div class="para">
You can use this option multiple times. In that case, the boot message will be displayed on all specified consoles, but only the last one will be used by the installer afterwards. For example, if you specify <code class="option">console=ttyS0 console=ttyS1</code>, the installer will use <code class="literal">ttyS1</code>.
@@ -2441,7 +2439,7 @@ initrd /initrd-(2.6.32.130.el6.i686.img
Starts the <code class="systemitem">sshd</code> service during the installation, which allows you to connect to the system during the installation using <code class="systemitem">SSH</code> and monitor its progress. For more information on SSH, see the <code class="systemitem">ssh(1)</code> man page and the corresponding chapter in the <em class="citetitle">Fedora System Administrator's Guide</em>.
</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
During the installation, the <code class="systemitem">root</code> account has no password by default. You can set a root password to be used during the installation with the <code class="command">sshpw</code> Kickstart command as described in <a class="xref" href="#s1-kickstart2-options">Section 15.4, “Kickstart Options”</a>.
- </div></div></div></dd></dl></div><div class="variablelist" id="list-boot-options-network"><h6>Network Boot Options</h6><a id="idm225458043760" class="indexterm"></a><div class="para">
+ </div></div></div></dd></dl></div><div class="variablelist" id="list-boot-options-network"><h6>Network Boot Options</h6><a id="idm219177510720" class="indexterm"></a><div class="para">
Initial network initialization is handled by <span class="package">dracut</span>. This section only lists some of the more commonly used options; for a complete list, see the <code class="systemitem">dracut.cmdline(7)</code> man page.
</div><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="option">ip=</code></span></dt><dd><div class="para">
Configures one or more network interfaces. To configure multiple interfaces, use the <code class="literal">ip</code> option multiple times — once for each interface. If multiple interfaces are configured, you must specify a primary boot interface using the <code class="option">bootdev</code> option described below.
@@ -2464,10 +2462,10 @@ initrd /initrd-(2.6.32.130.el6.i686.img
</td><td class="" align="left">
<code class="option">ip=<em class="replaceable"><code>ip</code></em>::<em class="replaceable"><code>gateway</code></em>:<em class="replaceable"><code>netmask</code></em>:<em class="replaceable"><code>hostname</code></em>:<em class="replaceable"><code>interface</code></em>:none</code>
</td></tr><tr><td class="" align="left">
- Automatic configuration of a specific interface with an override <a href="#ftn.idm225473957488" class="footnote"><sup class="footnote" id="idm225473957488">[a]</sup></a>
+ Automatic configuration of a specific interface with an override <a href="#ftn.idm219140492096" class="footnote"><sup class="footnote" id="idm219140492096">[a]</sup></a>
</td><td class="" align="left">
<code class="option">ip=<em class="replaceable"><code>ip</code></em>::<em class="replaceable"><code>gateway</code></em>:<em class="replaceable"><code>netmask</code></em>:<em class="replaceable"><code>hostname</code></em>:<em class="replaceable"><code>method</code></em>:<em class="replaceable"><code>mtu</code></em></code>
- </td></tr></tbody><tbody class="footnotes"><tr><td colspan="2"><div id="ftn.idm225473957488" class="footnote"><div class="para"><a href="#idm225473957488" class="para"><sup class="para">[a] </sup></a>
+ </td></tr></tbody><tbody class="footnotes"><tr><td colspan="2"><div id="ftn.idm219140492096" class="footnote"><div class="para"><a href="#idm219140492096" class="para"><sup class="para">[a] </sup></a>
Brings up the specified interface using the specified method of automatic configuration, such as <code class="literal">dhcp</code>, but overrides the automatically obtained IP address, gateway, netmask, hostname or other specified parameter. All parameters are optional; only specify the ones you wish to override and automatically obtained values will be used for the others.
</div></div></td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
The <code class="option">method</code> parameter can be any the following:
@@ -2509,15 +2507,15 @@ initrd /initrd-(2.6.32.130.el6.i686.img
Assigns a given interface name to a network device with a given MAC address. Can be used multiple times. The syntax <code class="option">ifname=<em class="replaceable"><code>interface</code></em>:<em class="replaceable"><code>MAC</code></em></code>. For example:
</div><pre class="screen"><code class="option">ifname=eth0:01:23:45:67:89:ab</code></pre></dd><dt class="varlistentry"><span class="term"><code class="option">inst.dhcpclass=</code></span></dt><dd><div class="para">
Specifies the DHCP class vendor identifier. The <code class="systemitem">dhcpd</code> service will see this value as <code class="literal">vendor-class-identifier</code>. The default value is <code class="literal">anaconda-$(uname -srm)</code>.
- </div></dd></dl></div><div class="variablelist" id="list-boot-options-advanced"><h6>Advanced Installation Options</h6><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="option">inst.multilib</code></span></dt><dd><a id="idm225455975920" class="indexterm"></a><a id="idm225456777008" class="indexterm"></a><div class="para">
+ </div></dd></dl></div><div class="variablelist" id="list-boot-options-advanced"><h6>Advanced Installation Options</h6><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="option">inst.multilib</code></span></dt><dd><a id="idm219176403840" class="indexterm"></a><a id="idm219181579232" class="indexterm"></a><div class="para">
Configure the system for multilib packages (that is, to allow installing 32-bit packages on a 64-bit x86 system) and install packages specified in this section as such.
</div><div class="para">
Normaly, on an AMD64/Intel 64 system, only packages for this architecture (marked as <code class="literal">x86_64</code>) and packages for all architectures (marked as <code class="literal">noarch</code> would be installed. When you use this option, packages for 32-bit AMD/Intel systems (marked as <code class="literal">i586</code>, <code class="literal">i686</code>, etc.) will be automatically installed as well if available.
</div><div class="para">
This only applies to packages directly specified in the <code class="literal">%packages</code> section. If a package is only installed as a dependency, only the exact specified dependency will be installed. For example, if you are installing package <span class="package">foo</span> which depends on package <span class="package">bar</span>, the former will be installed in multiple variants, while the latter will only be installed in variants specifically required.
- </div></dd><dt class="varlistentry"><span class="term"><code class="option">gpt</code></span></dt><dd><a id="idm225462937184" class="indexterm"></a><a id="idm225458118464" class="indexterm"></a><a id="idm225458117024" class="indexterm"></a><div class="para">
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">gpt</code></span></dt><dd><a id="idm219153536336" class="indexterm"></a><a id="idm219153534896" class="indexterm"></a><a id="idm219140351504" class="indexterm"></a><div class="para">
Install partition information into a GPT (GUID Partition Table) instead of MBR (Master Boot Record).
- </div></dd></dl></div><div class="variablelist" id="list-boot-options-vnc"><h6>Enabling Remote Access</h6><a id="idm225459566432" class="indexterm"></a><a id="idm225459564992" class="indexterm"></a><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="option">inst.vnc</code></span></dt><dd><div class="para">
+ </div></dd></dl></div><div class="variablelist" id="list-boot-options-vnc"><h6>Enabling Remote Access</h6><a id="idm219156512256" class="indexterm"></a><a id="idm219206612272" class="indexterm"></a><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="option">inst.vnc</code></span></dt><dd><div class="para">
Specifies that the installer's graphical interface should be run in a <code class="systemitem">VNC</code> session. If you specify this option, you will need to connect to the system using a VNC client application to be able to interact with the installer. VNC sharing is enabled, so multiple clients can connect to the system at the same time.
</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
A system installed using VNC will start in text mode by default.
@@ -2525,7 +2523,7 @@ initrd /initrd-(2.6.32.130.el6.i686.img
Sets a password on the VNC server used by the installer. Any VNC client attempting to connecting to the system will have to provide the correct password to gain access. For example, <code class="option">inst.vncpassword=<em class="replaceable"><code>testpasswd</code></em></code> will set the password to <code class="literal">testpasswd</code>.
</div></dd><dt class="varlistentry"><span class="term"><code class="option">inst.vncconnect=</code></span></dt><dd><div class="para">
Connect to a listening VNC client at a specified host and port once the installation starts. The correct syntax is <code class="option">inst.vncconnect=<em class="replaceable"><code>host</code></em>:<em class="replaceable"><code>port</code></em></code>, where <em class="replaceable"><code>host</code></em> is the address to the VNC client's host, and <em class="replaceable"><code>port</code></em> specifies which port to use. The <em class="replaceable"><code>port</code></em> parameter is optional, if you do not specify one, the installer will use <code class="literal">5900</code>.
- </div></dd></dl></div><div class="variablelist" id="list-boot-options-debug"><h6>Debugging and Troubleshooting</h6><a id="idm225426293888" class="indexterm"></a><a id="idm225502210384" class="indexterm"></a><a id="idm225502208944" class="indexterm"></a><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="option">inst.updates=</code></span></dt><dd><div class="para">
+ </div></dd></dl></div><div class="variablelist" id="list-boot-options-debug"><h6>Debugging and Troubleshooting</h6><a id="idm219162553616" class="indexterm"></a><a id="idm219162552176" class="indexterm"></a><a id="idm219198266224" class="indexterm"></a><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="option">inst.updates=</code></span></dt><dd><div class="para">
Specifies the location of the <code class="filename">updates.img</code> file to be applied to the installer runtime. The syntax is the same as in the <code class="option">inst.repo</code> option — see <a class="xref" href="#tabl-installmethods">Table 11.1, “Installation Sources”</a> for details. In all formats, if you do not specify a file name but only a directory, the installer will look for a file named <code class="filename">updates.img</code>.
</div></dd><dt class="varlistentry"><span class="term"><code class="option">inst.loglevel=</code></span></dt><dd><div class="para">
Specifies the minimum level for messages to be logged on a terminal. This only concerns terminal logging; log files will always contain messages of all levels.
@@ -2611,7 +2609,7 @@ initrd /initrd-(2.6.32.130.el6.i686.img
The <code class="option">isa</code> option causes the system to display an additional text screen at the beginning of the installation process. Use this screen to configure the ISA devices on your computer.
</div></div></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
Other kernel boot options have no particular meaning for <span class="application"><strong>anaconda</strong></span> and do not affect the installation process. However, if you use these options to boot the installation system, <span class="application"><strong>anaconda</strong></span> will preserve them in the bootloader configuration.
- </div></div></div></div></div><div class="section" id="sect-boot-options-maintenance"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">11.3. Using the Maintenance Boot Modes</h2></div></div></div><div class="section" id="sect-boot-options-memtest"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.3.1. Loading the Memory (RAM) Testing Mode</h3></div></div></div><a id="idm225470447344" class="indexterm"></a><a id="idm225446252864" class="indexterm"></a><div class="para">
+ </div></div></div></div></div><div class="section" id="sect-boot-options-maintenance"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">11.3. Using the Maintenance Boot Modes</h2></div></div></div><div class="section" id="sect-boot-options-memtest"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.3.1. Loading the Memory (RAM) Testing Mode</h3></div></div></div><a id="idm219135548608" class="indexterm"></a><a id="idm219135547648" class="indexterm"></a><div class="para">
Faults in memory modules may cause your system to freeze or crash unpredictably. In some cases, memory faults may only cause errors with particular combinations of software. For this reason, you should test the memory of a computer before you install Fedora for the first time, even if it has previously run other operating systems.
</div><div class="para">
Fedora includes the <span class="application"><strong>Memtest86+</strong></span> memory testing application. To boot your computer in memory testing mode, choose <span class="guimenuitem"><strong>Memory test</strong></span> at the boot menu. The first test starts immediately. By default, <span class="application"><strong>Memtest86+</strong></span> carries out a total of ten tests.
@@ -2623,11 +2621,11 @@ initrd /initrd-(2.6.32.130.el6.i686.img
To halt the tests and reboot your computer, enter <span class="keycap"><strong>Esc</strong></span> at any time.
</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
<span class="application"><strong>Memtest86+</strong></span> only works on BIOS installations and is not available on UEFI systems.
- </div></div></div></div><div class="section" id="sect-boot-options-mediacheck"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.3.2. Verifying Boot Media</h3></div></div></div><a id="idm225449420640" class="indexterm"></a><div class="para">
+ </div></div></div></div><div class="section" id="sect-boot-options-mediacheck"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.3.2. Verifying Boot Media</h3></div></div></div><a id="idm219154490784" class="indexterm"></a><div class="para">
You can test the integrity of an ISO-based installation source before using it to install Fedora. These sources include DVD, and ISO images stored on a hard drive or NFS server. Verifying that the ISO images are intact before you attempt an installation helps to avoid problems that are often encountered during installation.
</div><div class="para">
To test the checksum integrity of an ISO image, append the <code class="option">rd.live.check</code> to the boot loader command line. Note that this option is used automatically if you select the default installation option from the boot menu (<span class="guimenuitem"><strong>Test this media & install Fedora</strong></span>).
- </div></div><div class="section" id="sect-boot-options-rescue"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.3.3. Booting Your Computer in Rescue Mode</h3></div></div></div><a id="idm225365088768" class="indexterm"></a><a id="idm225495283472" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="sect-boot-options-rescue"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.3.3. Booting Your Computer in Rescue Mode</h3></div></div></div><a id="idm219125224208" class="indexterm"></a><a id="idm219184894544" class="indexterm"></a><div class="para">
You may boot a command-line Linux system from an installation disc without actually installing Fedora on the computer. This enables you to use the utilities and functions of a running Linux system to modify or repair systems that are already installed on the system.
</div><div class="para">
To load the rescue system with the installation disc, choose <span class="guimenuitem"><strong>Rescue a Fedora system</strong></span> from the <span class="guisubmenu"><strong>Troubleshooting</strong></span> submenu in the boot menu, or use the <code class="option">inst.rescue</code> boot option.
@@ -2681,7 +2679,7 @@ initrd /initrd-(2.6.32.130.el6.i686.img
Alternatively, specify the menu entry title. This is particularly useful if you have a number of menu entries across the various script files.
</div><pre class="screen">GRUB_DEFAULT="Fedora Linux"</pre></div><div class="section" id="sn-medialess-booting"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">12.3. Booting to Installation</h2></div></div></div><div class="para">
Reboot the system. <span class="application"><strong>GRUB</strong></span> boots the installation kernel and RAM disk, including any options you set. You may now refer to the appropriate chapter in this guide for the next step. If you chose to install remotely using VNC, refer to <a class="xref" href="#list-boot-options-vnc">Enabling Remote Access</a> for assistance in connecting to the remote system.
- </div></div></div><div xml:lang="en-US" class="chapter" id="ap-install-server" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 13. Setting Up an Installation Server</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#sn-install-cobbler">13.1. Setting Up <span class="package">cobbler</span></a></span></dt><dt><span class="section"><a href="#sn-cobbler-setup-distro">13.2. Setting Up the Distribution</a></span></dt><dt><span class="section"><a href="#sn-cobbler-mirror">13.3. Mirroring a Network Location</a></span></dt><dt><span class="section"><a href="#sn-cobbler-import">13.4. Importing the Distribution</a></span></dt><dt><span class="section"><a href="#sn-pxe-server-manual">13.5. Manually configure a PXE server</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-netboot-netserver">13.5.1. Setting up the Network Server</a></span></dt><dt><span class="section"><a href="#s1-netboot-pxe-config">13.5.2. P
XE Boot Configuration</a></span></dt><dt><span class="section"><a href="#idm225434414752">13.5.3. Starting the <code class="command">tftp</code> Server</a></span></dt><dt><span class="section"><a href="#s2-netboot-custom-msg">13.5.4. Adding a Custom Boot Message</a></span></dt><dt><span class="section"><a href="#netboot-performing">13.5.5. Performing the PXE Installation</a></span></dt></dl></dd></dl></div><div class="note"><div class="admonition_header"><h2>Experience Required</h2></div><div class="admonition"><div class="para">
+ </div></div></div><div xml:lang="en-US" class="chapter" id="ap-install-server" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 13. Setting Up an Installation Server</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#sn-install-cobbler">13.1. Setting Up <span class="package">cobbler</span></a></span></dt><dt><span class="section"><a href="#sn-cobbler-setup-distro">13.2. Setting Up the Distribution</a></span></dt><dt><span class="section"><a href="#sn-cobbler-mirror">13.3. Mirroring a Network Location</a></span></dt><dt><span class="section"><a href="#sn-cobbler-import">13.4. Importing the Distribution</a></span></dt><dt><span class="section"><a href="#sn-pxe-server-manual">13.5. Manually configure a PXE server</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-netboot-netserver">13.5.1. Setting up the Network Server</a></span></dt><dt><span class="section"><a href="#s1-netboot-pxe-config">13.5.2. P
XE Boot Configuration</a></span></dt><dt><span class="section"><a href="#idm219163541472">13.5.3. Starting the <code class="command">tftp</code> Server</a></span></dt><dt><span class="section"><a href="#s2-netboot-custom-msg">13.5.4. Adding a Custom Boot Message</a></span></dt><dt><span class="section"><a href="#netboot-performing">13.5.5. Performing the PXE Installation</a></span></dt></dl></dd></dl></div><div class="note"><div class="admonition_header"><h2>Experience Required</h2></div><div class="admonition"><div class="para">
This appendix is intended for users with previous Linux experience. If you are a new user, you may want to install using minimal boot media or the distribution DVD instead.
</div></div></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
The instructions in this appendix configures an automated install server. The default configuration includes destruction of all existing data on all disks for hosts that install using this method. This is often different from other network install server configurations which may provide for an interactive installation experience.
@@ -2765,7 +2763,7 @@ initrd /initrd-(2.6.32.130.el6.i686.img
20 and 21 or ftp, if the <code class="command">cobbler</code> server is to provide FTP installation service
</div></li><li class="listitem"><div class="para">
111 or sunrpc, if the <code class="command">cobbler</code> server is to provide NFS installation service
- </div></li></ul></div></div></div></li></ol></div></div><div xml:lang="en-US" class="section" id="sn-pxe-server-manual" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">13.5. Manually configure a PXE server</h2></div></div></div><a id="idm225409730112" class="indexterm"></a><div class="para">
+ </div></li></ul></div></div></div></li></ol></div></div><div xml:lang="en-US" class="section" id="sn-pxe-server-manual" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">13.5. Manually configure a PXE server</h2></div></div></div><a id="idm219146937504" class="indexterm"></a><div class="para">
The following steps must be performed to prepare for a PXE installation:
</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
Configure the network (NFS, FTP, HTTP) server to export the installation tree.
@@ -2779,9 +2777,9 @@ initrd /initrd-(2.6.32.130.el6.i686.img
Configure DHCP.
</div></li><li class="listitem"><div class="para">
Boot the client, and start the installation.
- </div></li></ol></div><div class="section" id="s1-netboot-netserver"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">13.5.1. Setting up the Network Server</h3></div></div></div><a id="idm225415369904" class="indexterm"></a><div class="para">
+ </div></li></ol></div><div class="section" id="s1-netboot-netserver"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">13.5.1. Setting up the Network Server</h3></div></div></div><a id="idm219139461024" class="indexterm"></a><div class="para">
First, configure an NFS, FTP, or HTTP server to export the entire installation tree for the version and variant of Fedora to be installed. Refer to <a class="xref" href="#s1-steps-network-installs-x86">Section 5.1, “Preparing for a Network Installation”</a> for detailed instructions.
- </div></div><div class="section" id="s1-netboot-pxe-config"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">13.5.2. PXE Boot Configuration</h3></div></div></div><a id="idm225464680704" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s1-netboot-pxe-config"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">13.5.2. PXE Boot Configuration</h3></div></div></div><a id="idm219139464800" class="indexterm"></a><div class="para">
The next step is to copy the files necessary to start the installation to the <code class="command">tftp</code> server so they can be found when the client requests them. The <code class="command">tftp</code> server is usually the same server as the network server exporting the installation tree.
</div><div class="para">
BIOS and EFI configuration differs for this procedure.
@@ -2796,7 +2794,7 @@ initrd /initrd-(2.6.32.130.el6.i686.img
<code class="command">systemctl status xinetd</code></pre>
</div></li><li class="step"><div class="para">
- Configure your DHCP server to use the boot images packaged with SYSLINUX. (If you do not have a DHCP server installed, refer to the <em class="citetitle">DHCP Servers</em> chapter in the <em class="citetitle">Fedora Deployment Guide</em>.)
+ Configure your DHCP server to use the boot images packaged with SYSLINUX. (If you do not have a DHCP server installed, refer to the <em class="citetitle">DHCP Servers</em> chapter in the <em class="citetitle">Fedora System Administrators Guide</em>.)
</div><div class="para">
A sample configuration in <code class="filename">/etc/dhcp/dhcpd.conf</code> might look like:
</div><pre class="screen">
@@ -2891,7 +2889,7 @@ label memtest86
<code class="command">systemctl status xinetd</code></pre>
</div></li><li class="step"><div class="para">
- Configure your DHCP server to use the EFI boot images packaged with GRUB. (If you do not have a DHCP server installed, refer to the <em class="citetitle">DHCP Servers</em> chapter in the <em class="citetitle">Fedora Deployment Guide</em>.)
+ Configure your DHCP server to use the EFI boot images packaged with GRUB. (If you do not have a DHCP server installed, refer to the <em class="citetitle">DHCP Servers</em> chapter in the <em class="citetitle">Fedora System Administrators Guide</em>.)
</div><div class="para">
A sample configuration in <code class="filename">/etc/dhcp/dhcpd.conf</code> might look like:
</div><pre class="screen">
@@ -2974,7 +2972,7 @@ title Fedora
Copy the boot images into your <code class="command">tftp</code> root directory:
</div><pre class="screen"><code class="command"> cp /<em class="replaceable"><code>path/to/image/</code></em>os/images/pxeboot/{vmlinuz,initrd.img} /var/lib/tftpboot/pxelinux/</code></pre></li><li class="step"><div class="para">
Reboot the system, and select the network device as your boot device when prompted.
- </div></li></ol></div></div></div><div xml:lang="en-US" class="section" id="idm225434414752" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225434414752">13.5.3. Starting the <code class="command">tftp</code> Server</h3></div></div></div><a id="idm225444402624" class="indexterm"></a><div class="para">
+ </div></li></ol></div></div></div><div xml:lang="en-US" class="section" id="idm219163541472" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm219163541472">13.5.3. Starting the <code class="command">tftp</code> Server</h3></div></div></div><a id="idm219180669888" class="indexterm"></a><div class="para">
On the DHCP server, verify that the <code class="filename">tftp-server</code> package is installed with the command <code class="command">rpm -q tftp-server</code>.
</div><div class="para">
<code class="command">tftp</code> is an xinetd-based service. Configure xinetd to process tftp requests by editing <code class="filename">/etc/xinetd.d/tftp</code> so that <code class="option">disable = no</code>.
@@ -2983,9 +2981,9 @@ title Fedora
</div><pre class="screen"><code class="command">systemctl start xinetd.service</code>
<code class="command">systemctl enable xinetd.service</code></pre><div class="para">
These commands configure the <code class="command">tftp</code> and <code class="command">xinetd</code> services to immediately turn on and also configure them to start at boot.
- </div></div><div class="section" id="s2-netboot-custom-msg"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">13.5.4. Adding a Custom Boot Message</h3></div></div></div><a id="idm225378227056" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-netboot-custom-msg"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">13.5.4. Adding a Custom Boot Message</h3></div></div></div><a id="idm219198640992" class="indexterm"></a><div class="para">
Optionally, modify <code class="filename">/tftpboot/linux-install/msgs/boot.msg</code> to use a custom boot message.
- </div></div><div class="section" id="netboot-performing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">13.5.5. Performing the PXE Installation</h3></div></div></div><a id="idm225443284704" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="netboot-performing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">13.5.5. Performing the PXE Installation</h3></div></div></div><a id="idm219087664288" class="indexterm"></a><div class="para">
For instructions on how to configure the network interface card with PXE support to boot from the network, consult the documentation for the NIC. It varies slightly per card.
</div><div class="para">
If your NIC does not support PXE booting, you can still PXE boot your system by using the <span class="application"><strong>iPXE</strong></span> bootloader. The Fedora Project does not distribute <span class="application"><strong>iPXE</strong></span> — refer to the project website at <a href="http://ipxe.org/">http://ipxe.org/</a> for more information.
@@ -3096,7 +3094,7 @@ title Fedora
Anaconda boot options: <a href="http://fedoraproject.org/wiki/Anaconda/Options">http://fedoraproject.org/wiki/Anaconda/Options</a>
</div></li><li class="listitem"><div class="para">
Kickstart documentation: <a href="http://fedoraproject.org/wiki/Anaconda/Kickstart">http://fedoraproject.org/wiki/Anaconda/Kickstart</a>
- </div></li></ul></div></div></div><div xml:lang="en-US" class="chapter" id="ch-kickstart2" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 15. Kickstart Installations</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-kickstart2-whatis">15.1. What are Kickstart Installations?</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-howuse">15.2. How Do You Perform a Kickstart Installation?</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-file">15.3. Creating the Kickstart File</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-options">15.4. Kickstart Options</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kickstart2-options-part-examples">15.4.1. Advanced Partitioning Example</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-packageselection">15.5. Package Selection</a></span></dt><dt><span class="section"><a href="#s1-kickstar
t2-preinstallconfig">15.6. Pre-installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kickstart2-prescript-example">15.6.1. Example</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-postinstallconfig">15.7. Post-installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kickstart2-post-examples">15.7.1. Example</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-putkickstarthere">15.8. Making the Kickstart File Available</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kickstart2-boot-media">15.8.1. Creating Kickstart Boot Media</a></span></dt><dt><span class="section"><a href="#s2-kickstart2-networkbased">15.8.2. Making the Kickstart File Available on the Network</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-install-tree">15.9. Making the Installation Tree Available</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-starti
nginstall">15.10. Starting a Kickstart Installation</a></span></dt></dl></div><a id="idm225364918304" class="indexterm"></a><a id="idm225463020112" class="indexterm"></a><div class="section" id="s1-kickstart2-whatis"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.1. What are Kickstart Installations?</h2></div></div></div><a id="idm225423890432" class="indexterm"></a><div class="para">
+ </div></li></ul></div></div></div><div xml:lang="en-US" class="chapter" id="ch-kickstart2" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 15. Kickstart Installations</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-kickstart2-whatis">15.1. What are Kickstart Installations?</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-howuse">15.2. How Do You Perform a Kickstart Installation?</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-file">15.3. Creating the Kickstart File</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-options">15.4. Kickstart Options</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kickstart2-options-part-examples">15.4.1. Advanced Partitioning Example</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-packageselection">15.5. Package Selection</a></span></dt><dt><span class="section"><a href="#s1-kickstar
t2-preinstallconfig">15.6. Pre-installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kickstart2-prescript-example">15.6.1. Example</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-postinstallconfig">15.7. Post-installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kickstart2-post-examples">15.7.1. Example</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-putkickstarthere">15.8. Making the Kickstart File Available</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-kickstart2-boot-media">15.8.1. Creating Kickstart Boot Media</a></span></dt><dt><span class="section"><a href="#s2-kickstart2-networkbased">15.8.2. Making the Kickstart File Available on the Network</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kickstart2-install-tree">15.9. Making the Installation Tree Available</a></span></dt><dt><span class="section"><a href="#s1-kickstart2-starti
nginstall">15.10. Starting a Kickstart Installation</a></span></dt></dl></div><a id="idm219127979888" class="indexterm"></a><a id="idm219145123104" class="indexterm"></a><div class="section" id="s1-kickstart2-whatis"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.1. What are Kickstart Installations?</h2></div></div></div><a id="idm219121763040" class="indexterm"></a><div class="para">
Many system administrators would prefer to use an automated installation method to install Fedora on their machines. To answer this need, Red Hat created the kickstart installation method. Using kickstart, a system administrator can create a single file containing the answers to all the questions that would normally be asked during a typical installation.
</div><div class="para">
Kickstart files can be kept on a single server system and read by individual computers during the installation. This installation method can support the use of a single kickstart file to install Fedora on multiple machines, making it ideal for network and system administrators.
@@ -3120,7 +3118,7 @@ title Fedora
Start the kickstart installation.
</div></li></ol></div><div class="para">
This chapter explains these steps in detail.
- </div></div><div class="section" id="s1-kickstart2-file"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.3. Creating the Kickstart File</h2></div></div></div><a id="idm225495049824" class="indexterm"></a><a id="idm225464331584" class="indexterm"></a><a id="idm225404526960" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s1-kickstart2-file"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.3. Creating the Kickstart File</h2></div></div></div><a id="idm219154152496" class="indexterm"></a><a id="idm219148278928" class="indexterm"></a><a id="idm219165723424" class="indexterm"></a><div class="para">
The kickstart file is a simple text file, containing a list of items, each identified by a keyword. You can create it by using the <span class="application"><strong>Kickstart Configurator</strong></span> application, or writing it from scratch. The Fedora installation program also creates a sample kickstart file based on the options that you selected during installation. It is written to the file <code class="filename">/root/anaconda-ks.cfg</code>. You should be able to edit it with any text editor or word processor that can save files as ASCII text.
</div><div class="para">
First, be aware of the following issues when you are creating your kickstart file:
@@ -3154,13 +3152,13 @@ title Fedora
Boot loader configuration
</div></li></ul></div><div class="para">
If any other items are specified for an upgrade, those items are ignored (note that this includes package selection).
- </div></li></ul></div></div><div class="section" id="s1-kickstart2-options"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.4. Kickstart Options</h2></div></div></div><a id="idm225444057856" class="indexterm"></a><a id="idm225464332544" class="indexterm"></a><div class="para">
+ </div></li></ul></div></div><div class="section" id="s1-kickstart2-options"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.4. Kickstart Options</h2></div></div></div><a id="idm219169791680" class="indexterm"></a><a id="idm219208185280" class="indexterm"></a><div class="para">
The following options can be placed in a kickstart file. If you prefer to use a graphical interface for creating your kickstart file, use the <span class="application"><strong>Kickstart Configurator</strong></span> application. Refer to <a class="xref" href="#ch-redhat-config-kickstart">Chapter 16, <em><span class="application"><strong>Kickstart Configurator</strong></span></em></a> for details.
</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
If the option is followed by an equals mark (=), a value must be specified after it. In the example commands, options in brackets ([]) are optional arguments for the command.
</div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="command">auth</code> or <code class="command">authconfig</code> (required) </span></dt><dd><div class="para">
- <a id="idm225471598688" class="indexterm"></a>
- <a id="idm225469104496" class="indexterm"></a>
+ <a id="idm219177667104" class="indexterm"></a>
+ <a id="idm219127986448" class="indexterm"></a>
Sets up the authentication options for the system. It is similar to the <code class="command">authconfig</code> command, which can be run after the install. By default, passwords are normally encrypted and are not shadowed.
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">--enablenis</code> — Turns on NIS support. By default, <code class="command">--enablenis</code> uses whatever domain it finds on the network. A domain should almost always be set by hand with the <code class="command">--nisdomain=</code> option.
@@ -3209,7 +3207,7 @@ title Fedora
</div></li><li class="listitem"><div class="para">
<code class="command">--passalgo=</code> — specify <code class="command">sha256</code> to set up the SHA-256 hashing algorithm or <code class="command">sha512</code> to set up the SHA-512 hashing algorithm.
</div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">autopart</code> (optional) </span></dt><dd><div class="para">
- <a id="idm225494062416" class="indexterm"></a>
+ <a id="idm219134934800" class="indexterm"></a>
Automatically create partitions — 1 GB or more root (<code class="filename">/</code>) partition, a swap partition, and an appropriate boot partition for the architecture. One or more of the default partition sizes can be redefined with the <code class="command">part</code> directive.
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">--encrypted</code> — Should all devices with support be encrypted by default? This is equivalent to checking the <span class="guilabel"><strong>Encrypt</strong></span> checkbox on the initial partitioning screen.
@@ -3220,12 +3218,12 @@ title Fedora
</div></li><li class="listitem"><div class="para">
<code class="command">--backuppassphrase=</code> — Add a randomly-generated passphrase to each encrypted volume. Store these passphrases in separate files in <code class="filename">/root</code>, encrypted using the X.509 certificate specified with <code class="command">--escrowcert</code>. This option is only meaningful if <code class="command">--escrowcert</code> is specified.
</div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">autostep</code> (optional) </span></dt><dd><div class="para">
- <a id="idm225459778208" class="indexterm"></a>
+ <a id="idm219149210448" class="indexterm"></a>
Similar to <code class="command">interactive</code> except it goes to the next screen for you. It is used mostly for debugging.
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">--autoscreenshot</code> — Take a screenshot at every step during installation and copy the images over to <code class="command">/root/anaconda-screenshots</code> after installation is complete. This is most useful for documentation.
</div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">bootloader</code> (required)</span></dt><dd><div class="para">
- <a id="idm225365109296" class="indexterm"></a>
+ <a id="idm219127783712" class="indexterm"></a>
Specifies how the boot loader should be installed. This option is required for both installations and upgrades.
</div><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
If you select text mode for a kickstart installation, make sure that you specify choices for the partitioning, bootloader, and package selection options. These steps are automated in text mode, and <span class="application"><strong>anaconda</strong></span> cannot prompt you for missing information. If you do not provide choices for these options, <span class="application"><strong>anaconda</strong></span> will stop the installation process.
@@ -3250,7 +3248,7 @@ title Fedora
</div></li><li class="listitem"><div class="para">
<code class="command">--extlinux</code> — install and use the <span class="application"><strong>extlinux</strong></span> bootloader.
</div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">btrfs</code> (optional) </span></dt><dd><div class="para">
- <a id="idm225456663936" class="indexterm"></a>
+ <a id="idm219176917408" class="indexterm"></a>
Create a BTRFS volume or subvolume. For a volume, the syntax is:
</div><pre class="screen">btrfs <em class="replaceable"><code><mntpoint></code></em> --data=<em class="replaceable"><code><level></code></em> --metadata=<em class="replaceable"><code><level></code></em> --label=<em class="replaceable"><code><label></code></em> <em class="replaceable"><code><partitions></code></em></pre><div class="para">
<em class="replaceable"><code><partitions></code></em> denotes that multiple partitions can be listed and should list the BTRFS identifiers to add to the BTRFS volume.
@@ -3269,7 +3267,7 @@ title Fedora
</div></li><li class="listitem"><div class="para">
<code class="command">--noformat</code> — Use an existing BTRFS volume and do not reformat the filesystem.
</div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">clearpart</code> (optional) </span></dt><dd><div class="para">
- <a id="idm225461416800" class="indexterm"></a>
+ <a id="idm219137961728" class="indexterm"></a>
Removes partitions from the system, prior to creation of new partitions. By default, no partitions are removed.
</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
If the <code class="command">clearpart</code> command is used, then the <code class="command">--onpart</code> command cannot be used on a logical partition.
@@ -3292,17 +3290,17 @@ title Fedora
</div></li><li class="listitem"><div class="para">
<code class="command">--none</code> (default) — Do not remove any partitions.
</div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">cmdline</code> (optional) </span></dt><dd><div class="para">
- <a id="idm225471338352" class="indexterm"></a>
+ <a id="idm219140831952" class="indexterm"></a>
Perform the installation in a completely non-interactive command line mode. Any prompts for interaction halts the install.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">device</code> (optional) </span></dt><dd><div class="para">
- <a id="idm225443897296" class="indexterm"></a>
+ <a id="idm219127698592" class="indexterm"></a>
On most PCI systems, the installation program autoprobes for Ethernet and SCSI cards properly. On older systems and some PCI systems, however, kickstart needs a hint to find the proper devices. The <code class="command">device</code> command, which tells the installation program to install extra modules, is in this format:
</div><pre class="screen">device <em class="replaceable"><code><moduleName></code></em> --opts=<em class="replaceable"><code><options></code></em></pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<em class="replaceable"><code><moduleName></code></em> — Replace with the name of the kernel module which should be installed.
</div></li><li class="listitem"><div class="para">
<code class="command">--opts=</code> — Mount options to use for mounting the NFS export. Any options that can be specified in <code class="filename">/etc/fstab</code> for an NFS mount are allowed. The options are listed in the <code class="command">nfs(5)</code> man page. Multiple options are separated with a comma.
</div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">driverdisk</code> (optional) </span></dt><dd><div class="para">
- <a id="idm225446900416" class="indexterm"></a>
+ <a id="idm219138117200" class="indexterm"></a>
Driver disks can be used during kickstart installations. You must copy the driver disks's contents to the root directory of a partition on the system's hard drive. Then you must use the <code class="command">driverdisk</code> command to tell the installation program where to look for the driver disk.
</div><pre class="screen">driverdisk <em class="replaceable"><code><partition></code></em> --source=<em class="replaceable"><code><url></code></em> --biospart=<em class="replaceable"><code><biospart></code></em> [--type=<em class="replaceable"><code><fstype></code></em>]</pre><div class="para">
Alternatively, a network location can be specified for the driver disk:
@@ -3317,7 +3315,7 @@ driverdisk --source=nfs:host:/path/to/img</pre><div class="itemizedlist"><ul><li
</div></li><li class="listitem"><div class="para">
<code class="command">--type=</code> — File system type (for example, vfat or ext2).
</div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">firewall</code> (optional) </span></dt><dd><div class="para">
- <a id="idm225444816992" class="indexterm"></a>
+ <a id="idm219145821312" class="indexterm"></a>
This option corresponds to the <span class="guilabel"><strong>Firewall Configuration</strong></span> screen in the installation program:
</div><pre class="screen">firewall --enabled|--disabled [--trust=] <em class="replaceable"><code><device></code></em> [--port=]</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">--enabled</code> or <code class="command">--enable</code> — Reject incoming connections that are not in response to outbound requests, such as DNS replies or DHCP requests. If access to services running on this machine is needed, you can choose to allow specific services through the firewall.
@@ -3338,17 +3336,17 @@ driverdisk --source=nfs:host:/path/to/img</pre><div class="itemizedlist"><ul><li
</div></li></ul></div></li><li class="listitem"><div class="para">
<code class="command">--port=</code> — You can specify that ports be allowed through the firewall using the port:protocol format. For example, to allow IMAP access through your firewall, specify <code class="command">imap:tcp</code>. Numeric ports can also be specified explicitly; for example, to allow UDP packets on port 1234 through, specify <code class="command">1234:udp</code>. To specify multiple ports, separate them by commas.
</div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">graphical</code> (optional) </span></dt><dd><div class="para">
- <a id="idm225443917536" class="indexterm"></a>
+ <a id="idm219184763600" class="indexterm"></a>
Perform the kickstart installation in graphical mode. This is the default.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">halt</code> (optional) </span></dt><dd><div class="para">
- <a id="idm225473071696" class="indexterm"></a>
+ <a id="idm219180861680" class="indexterm"></a>
Halt the system after the installation has successfully completed. This is similar to a manual installation, where anaconda displays a message and waits for the user to press a key before rebooting. During a kickstart installation, if no completion method is specified, this option is used as the default.
</div><div class="para">
The <code class="command">halt</code> option is equivalent to the <code class="command">shutdown -h</code> command.
</div><div class="para">
For other completion methods, refer to the <code class="command">poweroff</code>, <code class="command">reboot</code>, and <code class="command">shutdown</code> kickstart options.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">ignoredisk</code> (optional) </span></dt><dd><div class="para">
- <a id="idm225444156480" class="indexterm"></a>
+ <a id="idm219175464672" class="indexterm"></a>
Causes the installer to ignore the specified disks. This is useful if you use autopartition and want to be sure that some disks are ignored. For example, without <code class="literal">ignoredisk</code>, attempting to deploy on a SAN-cluster the kickstart would fail, as the installer detects passive paths to the SAN that return no partition table.
</div><div class="para">
The syntax is:
@@ -3367,9 +3365,9 @@ driverdisk --source=nfs:host:/path/to/img</pre><div class="itemizedlist"><ul><li
</div><pre class="programlisting">ignoredisk --only-use=disk/by-id/dm-uuid-mpath-2416CD96995134CA5D787F00A5AA11017</pre><div class="para">
To include a multipath device that uses LVM:
</div><pre class="programlisting">ignoredisk --only-use=disk/by-id/scsi-58095BEC5510947BE8C0360F604351918</pre></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">install</code> (optional) </span></dt><dd><div class="para">
- <a id="idm225468077072" class="indexterm"></a>
+ <a id="idm219133501152" class="indexterm"></a>
Tells the system to install a fresh system rather than upgrade an existing system. This is the default mode. For installation, you must specify the type of installation from <code class="command">cdrom</code>, <code class="command">harddrive</code>, <code class="command">nfs</code>, or <code class="command">url</code> (for FTP or HTTP installations). The <code class="command">install</code> command and the installation method command must be on separate lines.
- </div><a id="idm225468731216" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div><a id="idm219141380288" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">cdrom</code> — Install from the first optical drive on the system.
</div></li><li class="listitem"><div class="para">
<code class="command">harddrive</code> — Install from a Fedora installation tree on a local drive, which must be either vfat or ext2.
@@ -3424,7 +3422,7 @@ driverdisk --source=nfs:host:/path/to/img</pre><div class="itemizedlist"><ul><li
</div><pre class="screen">url --url http://<em class="replaceable"><code><server></code></em>/<em class="replaceable"><code><dir></code></em></pre><div class="para">
or:
</div><pre class="screen">url --url ftp://<em class="replaceable"><code><username></code></em>:<em class="replaceable"><code><password>@<server></code></em>/<em class="replaceable"><code><dir></code></em></pre></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">iscsi</code> (optional)</span></dt><dd><div class="para">
- <a id="idm225456625744" class="indexterm"></a>
+ <a id="idm219182941408" class="indexterm"></a>
iscsi --ipaddr= [options].
</div><div class="para">
Specifies additional iSCSI storage to be attached during installation. If you use the <em class="parameter"><code>iscsi</code></em> parameter, you must also assign a name to the iSCSI node, using the <em class="parameter"><code>iscsiname</code></em> parameter <span class="emphasis"><em>earlier</em></span> in the kickstart file.
@@ -3442,9 +3440,9 @@ driverdisk --source=nfs:host:/path/to/img</pre><div class="itemizedlist"><ul><li
<code class="command">--reverse-user=</code> — the username required to authenticate with the initiator from a target that uses reverse CHAP authentication
</div></li><li class="listitem"><div class="para">
<code class="command">--reverse-password=</code> — the password that corresponds with the username specified for the initiator
- </div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">iscsiname</code> (optional) </span></dt><dd><a id="idm225471916816" class="indexterm"></a><div class="para">
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">iscsiname</code> (optional) </span></dt><dd><a id="idm219138462768" class="indexterm"></a><div class="para">
Assigns a name to an iSCSI node specified by the iscsi parameter. If you use the <em class="parameter"><code>iscsi</code></em> parameter in your kickstart file, you must specify <em class="parameter"><code>iscsiname</code></em> <em class="firstterm">earlier</em> in the kickstart file.
- </div></dd><dt class="varlistentry"><span class="term"><code class="command">keyboard</code> (required) </span></dt><dd><a id="idm225426031808" class="indexterm"></a><div class="para">
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">keyboard</code> (required) </span></dt><dd><a id="idm219125259936" class="indexterm"></a><div class="para">
Set the available keyboard layouts for the system and how to switch between them with the following syntax:
</div><pre class="screen">keyboard --vckeymap=<em class="replaceable"><code><keymap></code></em>|--xlayouts=<em class="replaceable"><code><layout1></code></em>,...,<em class="replaceable"><code><layoutN></code></em>|<em class="replaceable"><code><layout></code></em> [--switch=<em class="replaceable"><code><option1></code></em>,...<em class="replaceable"><code><optionN></code></em>]</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">--vckeymap=<em class="replaceable"><code><keymap></code></em></code> — specify a VConsole keymap to serve as the keyboard layout. Available keymap names are listed in <code class="filename">/usr/lib/kbd/keymaps/<em class="replaceable"><code>architecture</code></em></code> with the <code class="filename">.map.gz</code> extension removed.
@@ -3457,7 +3455,7 @@ driverdisk --source=nfs:host:/path/to/img</pre><div class="itemizedlist"><ul><li
</div></li><li class="listitem"><div class="para">
<code class="command">--switch=</code> — specify keyboard shortcuts for switching between layouts. The list should be comma-separated with no spaces. Refer to <a href="https://fedoraproject.org/wiki/Anaconda/Kickstart">https://fedoraproject.org/wiki/Anaconda/Kickstart</a> for the available options.
</div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">lang</code> (required)
- <a id="idm225377640848" class="indexterm"></a>
+ <a id="idm219141236064" class="indexterm"></a>
</span></dt><dd><div class="para">
Sets the language to use during installation and the default language to use on the installed system. For example, to set the language to English, the kickstart file should contain the following line:
</div><pre class="screen">lang en_US</pre><div class="para">
@@ -3467,13 +3465,13 @@ driverdisk --source=nfs:host:/path/to/img</pre><div class="itemizedlist"><ul><li
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">--addsupport</code> — Set additional languages to be supported on the installed system.
</div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">langsupport</code> (deprecated)
- <a id="idm225462326368" class="indexterm"></a>
+ <a id="idm219125273440" class="indexterm"></a>
</span></dt><dd><div class="para">
The langsupport keyword is deprecated and its use will cause an error message to be printed to the screen and installation to halt. Instead of using the langsupport keyword, you should now list the support package groups for all languages you want supported in the <code class="command">%packages</code> section of your kickstart file. For instance, adding support for French means you should add the following to <code class="command">%packages</code>:
</div><pre class="screen">@french-support</pre></dd><dt class="varlistentry"><span class="term"><code class="command">logvol</code> (optional)
- <a id="idm225472024512" class="indexterm"></a>
- <a id="idm225466756336" class="indexterm"></a>
- <a id="idm225493181040" class="indexterm"></a>
+ <a id="idm219181270400" class="indexterm"></a>
+ <a id="idm219175698720" class="indexterm"></a>
+ <a id="idm219175697088" class="indexterm"></a>
</span></dt><dd><div class="para">
Create a logical volume for Logical Volume Management (LVM) with the syntax:
</div><pre class="screen">logvol <em class="replaceable"><code><mntpoint></code></em> --vgname=<em class="replaceable"><code><name></code></em> --size=<em class="replaceable"><code><size></code></em> --name=<em class="replaceable"><code><name></code></em> <em class="replaceable"><code><options></code></em></pre><div class="para">
@@ -3516,7 +3514,7 @@ logvol / --vgname=myvg --size=2000 --name=rootvol
</div><pre class="programlisting">part pv.01 --size 1 --grow
volgroup myvg pv.01
logvol / --vgname=myvg --size=1 --name=rootvol --grow --percent=90</pre></dd><dt class="varlistentry"><span class="term"><code class="command">logging</code> (optional)
- <a id="idm225476483504" class="indexterm"></a>
+ <a id="idm219128839488" class="indexterm"></a>
</span></dt><dd><div class="para">
This command controls the error logging of anaconda during installation. It has no effect on the installed system.
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
@@ -3528,11 +3526,11 @@ logvol / --vgname=myvg --size=1 --name=rootvol --grow --percent=90</pre></dd><dt
</div><div class="para">
Specify the minimum level of messages that appear on tty3. All messages will still be sent to the log file regardless of this level, however.
</div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">mediacheck</code> (optional)
- <a id="idm225442877616" class="indexterm"></a>
+ <a id="idm219180147024" class="indexterm"></a>
</span></dt><dd><div class="para">
If given, this will force anaconda to run mediacheck on the installation media. This command requires that installs be attended, so it is disabled by default.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">monitor</code> (optional)
- <a id="idm225471468400" class="indexterm"></a>
+ <a id="idm219144940416" class="indexterm"></a>
</span></dt><dd><div class="para">
If the monitor command is not given, anaconda will use X to automatically detect your monitor settings. Please try this before manually configuring your monitor.
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
@@ -3544,11 +3542,11 @@ logvol / --vgname=myvg --size=1 --name=rootvol --grow --percent=90</pre></dd><dt
</div></li><li class="listitem"><div class="para">
<code class="command">--vsync=</code> — Specifies the vertical sync frequency of the monitor.
</div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">mouse</code> (deprecated)
- <a id="idm225404900272" class="indexterm"></a>
+ <a id="idm219153866800" class="indexterm"></a>
</span></dt><dd><div class="para">
The mouse keyword is deprecated.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">network</code> (optional)
- <a id="idm225473864640" class="indexterm"></a>
+ <a id="idm219168480944" class="indexterm"></a>
</span></dt><dd><div class="para">
Configures network information for the target system and activates network devices in the installer environment. The device specified in the first <code class="command">network</code> command is activated automatically if network access is required during installation, for example, during a network installation or installation over VNC. You can also explicitly require device to activate in the installer environment with the <code class="option">--activate</code> option.
</div><div class="important"><div class="admonition_header"><h2> How to manually input network settings </h2></div><div class="admonition"><div class="para">
@@ -3649,8 +3647,8 @@ logvol / --vgname=myvg --size=1 --name=rootvol --grow --percent=90</pre></dd><dt
<code class="command">--noipv6</code> — Disable IPv6 on this device.
</div></li><li class="listitem"><div class="para">
<code class="command">--vlanid</code> — Specifies virtual LAN ID number (802.1q tag).
- </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <a id="idm225421453136" class="indexterm"></a>
- <a id="idm225459418640" class="indexterm"></a>
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <a id="idm219170740320" class="indexterm"></a>
+ <a id="idm219125310736" class="indexterm"></a>
<code class="command">part</code> or <code class="command">partition</code> (required for installs, ignored for upgrades) </span></dt><dd><div class="para">
Creates a partition on the system.
</div><div class="para">
@@ -3747,7 +3745,7 @@ logvol / --vgname=myvg --size=1 --name=rootvol --grow --percent=90</pre></dd><dt
<code class="command">--label=</code> — assign a label to an individual partition.
</div></li></ul></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
If partitioning fails for any reason, diagnostic messages appear on virtual console 3.
- </div></div></div></dd><dt class="varlistentry"><span class="term"> <a id="idm225375274976" class="indexterm"></a>
+ </div></div></div></dd><dt class="varlistentry"><span class="term"> <a id="idm219145503712" class="indexterm"></a>
<code class="command">poweroff</code> (optional) </span></dt><dd><div class="para">
Shut down and power off the system after the installation has successfully completed. Normally during a manual installation, anaconda displays a message and waits for the user to press a key before rebooting. During a kickstart installation, if no completion method is specified, the <code class="command">halt</code> option is used as default.
</div><div class="para">
@@ -3756,8 +3754,8 @@ logvol / --vgname=myvg --size=1 --name=rootvol --grow --percent=90</pre></dd><dt
The <code class="command">poweroff</code> option is highly dependent on the system hardware in use. Specifically, certain hardware components such as the BIOS, APM (advanced power management), and ACPI (advanced configuration and power interface) must be able to interact with the system kernel. Contact your manufacturer for more information on you system's APM/ACPI abilities.
</div></div></div><div class="para">
For other completion methods, refer to the <code class="command">halt</code>, <code class="command">reboot</code>, and <code class="command">shutdown</code> kickstart options.
- </div></dd><dt class="varlistentry"><span class="term"> <a id="idm225421772864" class="indexterm"></a>
- <a id="idm225441991168" class="indexterm"></a>
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm219143213488" class="indexterm"></a>
+ <a id="idm219139853936" class="indexterm"></a>
<code class="command">raid</code> (optional) </span></dt><dd><div class="para">
Assembles a software RAID device. This command is of the form:
</div><pre class="screen">raid <em class="replaceable"><code><mntpoint></code></em> --level=<em class="replaceable"><code><level></code></em> --device=<em class="replaceable"><code><mddevice></code></em> <em class="replaceable"><code><partitions*></code></em></pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
@@ -3804,9 +3802,9 @@ raid /usr --level=5 --device=md1 raid.11 raid.12 raid.13
</pre><div class="para">
For a detailed example of <code class="command">raid</code> in action, refer to <a class="xref" href="#s2-kickstart2-options-part-examples">Section 15.4.1, “Advanced Partitioning Example”</a>.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">realm</code> (optional)
- <a id="idm225460608096" class="indexterm"></a>
- <a id="idm225441167072" class="indexterm"></a>
- <a id="idm225441165440" class="indexterm"></a>
+ <a id="idm219088121184" class="indexterm"></a>
+ <a id="idm219184783920" class="indexterm"></a>
+ <a id="idm219184782176" class="indexterm"></a>
</span></dt><dd><div class="para">
Join Active Directory or IPA domains, with the syntax:
</div><pre class="screen">realm join <em class="replaceable"><code><options></code></em> <em class="replaceable"><code><domain></code></em></pre><div class="para">
@@ -3823,7 +3821,7 @@ raid /usr --level=5 --device=md1 raid.11 raid.12 raid.13
<code class="command">--no-password</code> — Join automatically without a password.
</div></li><li class="listitem"><div class="para">
<code class="command">--computer-ou OU=</code> — provide the distinguished name of an organizational unit in order to create the computer account. The exact format of the distinguished name depends on the client software and membership software. The root DSE portion of the distinguished name can typically be left out.
- </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <a id="idm225460494256" class="indexterm"></a>
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <a id="idm219136527328" class="indexterm"></a>
<code class="command">reboot</code> (optional) </span></dt><dd><div class="para">
Reboot after the installation is successfully completed (no arguments). Normally, kickstart displays a message and waits for the user to press a key before rebooting.
</div><div class="para">
@@ -3835,7 +3833,7 @@ raid /usr --level=5 --device=md1 raid.11 raid.12 raid.13
</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
Use of the <code class="command">reboot</code> option <span class="emphasis"><em>may</em></span> result in an endless installation loop, depending on the installation media and method.
</div></div></div></dd><dt class="varlistentry"><span class="term"><code class="command">repo</code> (optional)
- <a id="idm225441804336" class="indexterm"></a>
+ <a id="idm219168736432" class="indexterm"></a>
</span></dt><dd><div class="para">
Configures additional yum repositories that may be used as sources for package installation. Multiple repo lines may be specified.
</div><pre class="screen">repo --name=<em class="replaceable"><code><repoid></code></em> [--baseurl=<em class="replaceable"><code><url></code></em>| --mirrorlist=<em class="replaceable"><code><url></code></em>]
@@ -3846,7 +3844,7 @@ raid /usr --level=5 --device=md1 raid.11 raid.12 raid.13
</div></li><li class="listitem"><div class="para">
<code class="command">--mirrorlist=</code> — The URL pointing at a list of mirrors for the repository. The variables that may be used in yum repo config files are not supported here. You may use one of either this option or --baseurl, not both.
</div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">rootpw</code> (required) </span></dt><dd><div class="para">
- <a id="idm225457130032" class="indexterm"></a>
+ <a id="idm219140859744" class="indexterm"></a>
Sets the system's root password to the <em class="replaceable"><code><password></code></em> argument.
</div><pre class="screen">rootpw [--iscrypted|--allow-changes|--frozen] <em class="replaceable"><code><password></code></em></pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">--iscrypted</code> — If this is present, the password argument is assumed to already be encrypted.
@@ -3855,7 +3853,7 @@ raid /usr --level=5 --device=md1 raid.11 raid.12 raid.13
</div></li><li class="listitem"><div class="para">
<code class="command">--frozen</code> — If this is present, the password argument cannot be changed.
</div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">selinux</code> (optional) </span></dt><dd><div class="para">
- <a id="idm225502853920" class="indexterm"></a>
+ <a id="idm219133180784" class="indexterm"></a>
Sets the state of SELinux on the installed system. SELinux defaults to enforcing in anaconda.
</div><pre class="screen">selinux [--disabled|--enforcing|--permissive]</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">--enforcing</code> — Enables SELinux with the default targeted policy being enforced.
@@ -3866,9 +3864,9 @@ raid /usr --level=5 --device=md1 raid.11 raid.12 raid.13
</div></li><li class="listitem"><div class="para">
<code class="command">--disabled</code> — Disables SELinux completely on the system.
</div></li></ul></div><div class="para">
- For more information regarding SELinux for Fedora, refer to the <em class="citetitle">Fedora Deployment Guide</em>.
+ For more information regarding SELinux for Fedora, refer to the <em class="citetitle">Fedora Security Guide</em>.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">services</code> (optional) </span></dt><dd><div class="para">
- <a id="idm225468909280" class="indexterm"></a>
+ <a id="idm219178782704" class="indexterm"></a>
Modifies the default set of services that will run under the default runlevel. The list of disabled services is processed before the list of enabled services. Therefore, if a service appears on both lists, it is enabled.
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">--disabled</code> — Disable the services given in the comma separated list.
@@ -3883,18 +3881,18 @@ raid /usr --level=5 --device=md1 raid.11 raid.12 raid.13
</div><div class="para">
<code class="command">services --disabled auditd,cups,smartd,nfslock</code>
</div></div></div></dd><dt class="varlistentry"><span class="term"><code class="command">shutdown</code> (optional) </span></dt><dd><div class="para">
- <a id="idm225442791712" class="indexterm"></a>
+ <a id="idm219175385696" class="indexterm"></a>
Shut down the system after the installation has successfully completed. During a kickstart installation, if no completion method is specified, the <code class="command">halt</code> option is used as default.
</div><div class="para">
The <code class="command">shutdown</code> option is equivalent to the <code class="command">shutdown</code> command.
</div><div class="para">
For other completion methods, refer to the <code class="command">halt</code>, <code class="command">poweroff</code>, and <code class="command">reboot</code> kickstart options.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">skipx</code> (optional) </span></dt><dd><div class="para">
- <a id="idm225445980000" class="indexterm"></a>
+ <a id="idm219125441472" class="indexterm"></a>
If present, X is not configured on the installed system.
</div><div class="important"><div class="admonition_header"><h2>Package selection might configure X</h2></div><div class="admonition"><div class="para">
If you install a display manager among your package selection options, this package will create an X configuration, and the installed system will default to run level 5. The effect of the skipx option is overridden.
- </div></div></div></dd><dt class="varlistentry"><span class="term"><code class="command">sshpw</code> (optional) </span></dt><dd><a id="idm225464274464" class="indexterm"></a><div class="para">
+ </div></div></div></dd><dt class="varlistentry"><span class="term"><code class="command">sshpw</code> (optional) </span></dt><dd><a id="idm219164417760" class="indexterm"></a><div class="para">
During installation, you can interact with <span class="application"><strong>anaconda</strong></span> and monitor its progress over an SSH connection. Use the <code class="command">sshpw</code> command to create temporary accounts through which to log on. Each instance of the command creates a separate account that exists only in the installation environment. These accounts are not transferred to the installed system.
</div><pre class="screen">sshpw --username=<em class="replaceable"><code><name></code></em> <em class="replaceable"><code><password></code></em> [--iscrypted|--plaintext] [--lock]</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">--username</code> — Provides the name of the user. This option is required.
@@ -3907,12 +3905,12 @@ raid /usr --level=5 --device=md1 raid.11 raid.12 raid.13
</div></li></ul></div><div class="important"><div class="admonition_header"><h2>Important — You must boot with sshd=1</h2></div><div class="admonition"><div class="para">
By default, the <span class="application"><strong>ssh</strong></span> server is not started during installation. To make <code class="systemitem">ssh</code> available during installation, boot the system with the kernel boot option <em class="parameter"><code>sshd=1</code></em>. Refer to <a class="xref" href="#list-boot-options-display">Console, Environment and Display Options</a> for details of how to specify this kernel option at boot time.
</div></div></div></dd><dt class="varlistentry"><span class="term"><code class="command">text</code> (optional) </span></dt><dd><div class="para">
- <a id="idm225464344544" class="indexterm"></a>
+ <a id="idm219181080448" class="indexterm"></a>
Perform the kickstart installation in text mode. Kickstart installations are performed in graphical mode by default.
</div><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
If you select text mode for a kickstart installation, make sure that you specify choices for the partitioning, bootloader, and package selection options. These steps are automated in text mode, and <span class="application"><strong>anaconda</strong></span> cannot prompt you for missing information. If you do not provide choices for these options, <span class="application"><strong>anaconda</strong></span> will stop the installation process.
</div></div></div></dd><dt class="varlistentry"><span class="term"><code class="command">timezone</code> (required) </span></dt><dd><div class="para">
- <a id="idm225451142192" class="indexterm"></a>
+ <a id="idm219162165312" class="indexterm"></a>
Sets the system time zone to <em class="replaceable"><code><timezone></code></em>. Refer to <a href="https://fedoraproject.org/wiki/Anaconda/Kickstart">https://fedoraproject.org/wiki/Anaconda/Kickstart</a> for a list of supported timezones.
</div><pre class="screen">timezone [--utc] [--nontp] [--ntpservers=<em class="replaceable"><code><server1></code></em>,<em class="replaceable"><code><server2></code></em>,...,<em class="replaceable"><code><serverN></code></em>] <em class="replaceable"><code><timezone></code></em></pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">--utc</code> — If present, the system assumes the hardware clock is set to UTC (Greenwich Mean) time.
@@ -3921,10 +3919,10 @@ raid /usr --level=5 --device=md1 raid.11 raid.12 raid.13
</div></li><li class="listitem"><div class="para">
<code class="command">--ntpservers=</code> — Specify a list of NTP servers to be used, separated by commas without spaces.
</div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">upgrade</code> (optional) </span></dt><dd><div class="para">
- <a id="idm225473618560" class="indexterm"></a>
+ <a id="idm219115918880" class="indexterm"></a>
Tells the system to upgrade an existing system rather than install a fresh system. You must specify one of <code class="command">cdrom</code>, <code class="command">harddrive</code>, <code class="command">nfs</code>, or <code class="command">url</code> (for FTP and HTTP) as the location of the installation tree. Refer to <code class="command">install</code> for details.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">user</code> (optional) </span></dt><dd><div class="para">
- <a id="idm225442849664" class="indexterm"></a>
+ <a id="idm219181235152" class="indexterm"></a>
Creates a new user on the system.
</div><pre class="screen">user --name=<em class="replaceable"><code><username></code></em> [--groups=<em class="replaceable"><code><list></code></em>] [--homedir=<em class="replaceable"><code><homedir></code></em>] [--password=<em class="replaceable"><code><password></code></em>] [--iscrypted] [--shell=<em class="replaceable"><code><shell></code></em>] [--uid=<em class="replaceable"><code><uid></code></em>]</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">--name=</code> — Provides the name of the user. This option is required.
@@ -3941,7 +3939,7 @@ raid /usr --level=5 --device=md1 raid.11 raid.12 raid.13
</div></li><li class="listitem"><div class="para">
<code class="command">--uid=</code> — The user's UID. If not provided, this defaults to the next available non-system UID.
</div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">vnc</code> (optional) </span></dt><dd><div class="para">
- <a id="idm225477334880" class="indexterm"></a>
+ <a id="idm219115914144" class="indexterm"></a>
Allows the graphical installation to be viewed remotely via VNC. This method is usually preferred over text mode, as there are some size and language limitations in text installs. With no options, this command will start a VNC server on the machine with no password and will print out the command that needs to be run to connect a remote machine.
</div><pre class="screen">vnc [--host=<em class="replaceable"><code><hostname></code></em>] [--port=<em class="replaceable"><code><port></code></em>] [--password=<em class="replaceable"><code><password></code></em>]</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">--host=</code> — Instead of starting a VNC server on the install machine, connect to the VNC viewer process listening on the given hostname.
@@ -3950,7 +3948,7 @@ raid /usr --level=5 --device=md1 raid.11 raid.12 raid.13
</div></li><li class="listitem"><div class="para">
<code class="command">--password=</code> — Set a password which must be provided to connect to the VNC session. This is optional, but recommended.
</div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">volgroup</code> (optional) </span></dt><dd><div class="para">
- <a id="idm225467080768" class="indexterm"></a>
+ <a id="idm219169300320" class="indexterm"></a>
Use to create a Logical Volume Management (LVM) group with the syntax:
</div><pre class="screen">volgroup <em class="replaceable"><code><name></code></em> <em class="replaceable"><code><partition></code></em> <em class="replaceable"><code><options></code></em></pre><div class="para">
The options are as follows:
@@ -3966,7 +3964,7 @@ raid /usr --level=5 --device=md1 raid.11 raid.12 raid.13
volgroup myvg pv.01
logvol / --vgname=myvg --size=2000 --name=rootvol</pre><div class="para">
For a detailed example of <code class="command">volgroup</code> in action, refer to <a class="xref" href="#s2-kickstart2-options-part-examples">Section 15.4.1, “Advanced Partitioning Example”</a>.
- </div></dd><dt class="varlistentry"><span class="term"><code class="command">xconfig</code> (optional) </span></dt><dd><a id="idm225468754640" class="indexterm"></a><div class="para">
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">xconfig</code> (optional) </span></dt><dd><a id="idm219085787664" class="indexterm"></a><div class="para">
Configures the <span class="application"><strong>X Window System</strong></span>. If you install the <span class="application"><strong>X Window System</strong></span> with a kickstart file that does not include the <code class="command">xconfig</code> command, you must provide the <span class="application"><strong>X</strong></span> configuration manually during installation.
</div><div class="para">
Do not use this command in a kickstart file that does not install the <span class="application"><strong>X Window System</strong></span>.
@@ -3979,15 +3977,15 @@ logvol / --vgname=myvg --size=2000 --name=rootvol</pre><div class="para">
</div></li><li class="listitem"><div class="para">
<code class="command">--startxonboot</code> — Use a graphical login on the installed system.
</div></li></ul></div></dd><dt class="varlistentry"><span class="term"><code class="command">zerombr</code> (optional) </span></dt><dd><div class="para">
- <a id="idm225470779296" class="indexterm"></a>
+ <a id="idm219176225488" class="indexterm"></a>
If <code class="command">zerombr</code> is specified any invalid partition tables found on disks are initialized. This destroys all of the contents of disks with invalid partition tables.
</div><div class="para">
Note that this command was previously specified as <code class="command">zerombr yes</code>. This form is now deprecated; you should now simply specify <code class="command">zerombr</code> in your kickstart file instead.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">%include</code> (optional)</span></dt><dd><div class="para">
- <a id="idm225405312560" class="indexterm"></a>
- <a id="idm225459723120" class="indexterm"></a>
+ <a id="idm219176047072" class="indexterm"></a>
+ <a id="idm219176045360" class="indexterm"></a>
Use the <code class="command">%include <em class="replaceable"><code>/path/to/file</code></em></code> command to include the contents of another file in the kickstart file as though the contents were at the location of the <code class="command">%include</code> command in the kickstart file.
- </div></dd></dl></div><div class="section" id="s2-kickstart2-options-part-examples"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.4.1. Advanced Partitioning Example</h3></div></div></div><a id="idm225500988112" class="indexterm"></a><div class="para">
+ </div></dd></dl></div><div class="section" id="s2-kickstart2-options-part-examples"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.4.1. Advanced Partitioning Example</h3></div></div></div><a id="idm219167775296" class="indexterm"></a><div class="para">
The following is a single, integrated example showing the <code class="command">clearpart</code>, <code class="command">raid</code>, <code class="command">part</code>, <code class="command">volgroup</code>, and <code class="command">logvol</code> kickstart options in action:
</div><pre class="screen">clearpart --drives=hda,hdc --initlabel
# Raid 1 IDE config
@@ -4016,7 +4014,7 @@ logvol /var/freespace --vgname=sysvg --size=8000 --name=freespacetouse
logvol /usr/local --vgname=sysvg --size=1 --grow --name=usrlocal
</pre><div class="para">
This advanced example implements LVM over RAID, as well as the ability to resize various directories for future growth.
- </div></div></div><div class="section" id="s1-kickstart2-packageselection"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.5. Package Selection</h2></div></div></div><a id="idm225451943328" class="indexterm"></a><div class="warning"><div class="admonition_header"><h2>Warning — do not install every available package</h2></div><div class="admonition"><div class="para">
+ </div></div></div><div class="section" id="s1-kickstart2-packageselection"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.5. Package Selection</h2></div></div></div><a id="idm219142181200" class="indexterm"></a><div class="warning"><div class="admonition_header"><h2>Warning — do not install every available package</h2></div><div class="admonition"><div class="para">
You can use a kickstart file to install every available package by specifying <code class="literal">@Everything</code> or simply <code class="literal">*</code> in the %packages section. However, using a kickstart file in this way will introduce package and file conflicts onto the installed system
</div></div></div><div class="para">
Use the <code class="command">%packages</code> command to begin a kickstart file section that lists the packages you would like to install (this is for installations only, as package selection during upgrades is not supported).
@@ -4061,7 +4059,7 @@ docbook*
The --resolvedeps option has been deprecated. Dependencies are now always resolved automatically.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">--ignoredeps</code></span></dt><dd><div class="para">
The --ignoredeps option has been deprecated. Dependencies are resolved automatically every time now.
- </div></dd></dl></div></div><div class="section" id="s1-kickstart2-preinstallconfig"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.6. Pre-installation Script</h2></div></div></div><a id="idm225443964896" class="indexterm"></a><a id="idm225443963184" class="indexterm"></a><div class="para">
+ </div></dd></dl></div></div><div class="section" id="s1-kickstart2-preinstallconfig"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.6. Pre-installation Script</h2></div></div></div><a id="idm219168798992" class="indexterm"></a><a id="idm219168797280" class="indexterm"></a><div class="para">
You can add commands to run on the system immediately after the <code class="filename">ks.cfg</code> has been parsed. This section must be placed towards the end of the kickstart file, after the kickstart commands described in <a class="xref" href="#s1-kickstart2-options">Section 15.4, “Kickstart Options”</a>, and must start with the <code class="command">%pre</code> command. If your kickstart file also includes a <code class="command">%post</code> section, the order of the <code class="command">%pre</code> and <code class="command">%post</code> sections does not matter.
</div><div class="para">
You can access the network in the <code class="command">%pre</code> section; however, <em class="firstterm">name service</em> has not been configured at this point, so only IP addresses work.
@@ -4109,7 +4107,7 @@ fi
The partitioning commands selected in the script are used.
</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
The pre-installation script section of kickstart <span class="emphasis"><em>cannot</em></span> manage multiple install trees or source media. This information must be included for each created ks.cfg file, as the pre-installation script occurs during the second stage of the installation process.
- </div></div></div></div></div><div class="section" id="s1-kickstart2-postinstallconfig"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.7. Post-installation Script</h2></div></div></div><a id="idm225459909152" class="indexterm"></a><a id="idm225439865488" class="indexterm"></a><div class="para">
+ </div></div></div></div></div><div class="section" id="s1-kickstart2-postinstallconfig"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.7. Post-installation Script</h2></div></div></div><a id="idm219116042176" class="indexterm"></a><a id="idm219174716352" class="indexterm"></a><div class="para">
You have the option of adding commands to run on the system once the installation is complete. This section must be placed towards the end of the kickstart file, after the kickstart commands described in <a class="xref" href="#s1-kickstart2-options">Section 15.4, “Kickstart Options”</a>, and must start with the <code class="command">%post</code> command. If your kickstart file also includes a <code class="command">%pre</code> section, the order of the <code class="command">%pre</code> and <code class="command">%post</code> sections does not matter.
</div><div class="para">
This section is useful for functions such as installing additional software and configuring an additional nameserver.
@@ -4134,7 +4132,7 @@ openvt -s -w -- /mnt/temp/runme
umount /mnt/temp
</pre><div class="para">
NFS file locking is <span class="emphasis"><em>not</em></span> supported while in kickstart mode, therefore <code class="command">-o nolock</code> is required when mounting an NFS mount.
- </div></div></div><br class="example-break" /></div></div><div class="section" id="s1-kickstart2-putkickstarthere"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.8. Making the Kickstart File Available</h2></div></div></div><a id="idm225445770288" class="indexterm"></a><div class="para">
+ </div></div></div><br class="example-break" /></div></div><div class="section" id="s1-kickstart2-putkickstarthere"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.8. Making the Kickstart File Available</h2></div></div></div><a id="idm219184585584" class="indexterm"></a><div class="para">
A kickstart file must be placed in one of the following locations:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
On removable media, such as a floppy disk, optical disk, or USB flash drive
@@ -4146,19 +4144,19 @@ umount /mnt/temp
Normally a kickstart file is copied to the removable media or hard drive, or made available on the network. The network-based approach is most commonly used, as most kickstart installations tend to be performed on networked computers.
</div><div class="para">
Let us take a more in-depth look at where the kickstart file may be placed.
- </div><div class="section" id="s2-kickstart2-boot-media"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.8.1. Creating Kickstart Boot Media</h3></div></div></div><a id="idm225475327312" class="indexterm"></a><a id="idm225475325568" class="indexterm"></a><a id="idm225493457104" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s2-kickstart2-boot-media"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.8.1. Creating Kickstart Boot Media</h3></div></div></div><a id="idm219172187712" class="indexterm"></a><a id="idm219172185968" class="indexterm"></a><a id="idm219134350688" class="indexterm"></a><div class="para">
To perform a kickstart installation using removable media, the kickstart file must be named <code class="filename">ks.cfg</code> and must be located in the top-level directory of the disc.
- </div><a id="idm225476910912" class="indexterm"></a><div class="para">
+ </div><a id="idm219181557440" class="indexterm"></a><div class="para">
Diskette-based booting is no longer supported in Fedora. Installations must use CD-ROM or flash memory products for booting. However, the kickstart file may still reside on a diskette's top-level directory, and must be named <code class="filename">ks.cfg</code>. Separate boot media will be required.
</div><div class="para">
Refer to <a class="xref" href="#Making_Minimal_Boot_Media">Section 3.3, “Making Minimal Boot Media”</a> for instructions on creating boot media.
- </div><a id="idm225429879536" class="indexterm"></a><a id="idm225450984800" class="indexterm"></a><div class="para">
+ </div><a id="idm219205727328" class="indexterm"></a><a id="idm219205725584" class="indexterm"></a><div class="para">
To perform a pen-based flash memory kickstart installation, the kickstart file must be named <code class="filename">ks.cfg</code> and must be located in the flash memory's top-level directory. Create the boot image first, and then copy the <code class="filename">ks.cfg</code> file.
</div><div class="para">
Refer to <a class="xref" href="#Making_Minimal_Boot_Media">Section 3.3, “Making Minimal Boot Media”</a> for instructions on creating live USB media using the <code class="filename">Fedora-<em class="replaceable"><code>version</code></em>-<em class="replaceable"><code>architecture</code></em>-<em class="replaceable"><code>format</code></em>.iso</code> image file that you can download from the Fedora Project site at <a href="http://download.fedoraproject.org/">http://download.fedoraproject.org/</a>.
</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
Creation of USB flashdrives for booting is possible, but is heavily dependent on system hardware BIOS settings. Refer to your hardware manufacturer to see if your system supports booting to alternate devices.
- </div></div></div></div><div class="section" id="s2-kickstart2-networkbased"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.8.2. Making the Kickstart File Available on the Network</h3></div></div></div><a id="idm225433775760" class="indexterm"></a><a id="idm225494885152" class="indexterm"></a><div class="para">
+ </div></div></div></div><div class="section" id="s2-kickstart2-networkbased"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.8.2. Making the Kickstart File Available on the Network</h3></div></div></div><a id="idm219130144880" class="indexterm"></a><a id="idm219130143136" class="indexterm"></a><div class="para">
Network installations using kickstart are quite common, because system administrators can quickly and easily automate the installation on many networked computers. In general, the approach most commonly used is for the administrator to have both a BOOTP/DHCP server and an NFS server on the local network. The BOOTP/DHCP server is used to give the client system its networking information, while the actual files used during the installation are served by the NFS server. Often, these two servers run on the same physical machine, but they are not required to.
</div><div class="para">
Include the <code class="option">ks</code> kernel boot option in the <code class="literal">append</code> line of a target in your <code class="filename">pxelinux.cfg/default</code> file to specify the location of a kickstart file on your network. The syntax of the <code class="option">ks</code> option in a <code class="filename">pxelinux.cfg/default</code> file is identical to its syntax when used at the boot prompt. Refer to <a class="xref" href="#s1-kickstart2-startinginstall">Section 15.10, “Starting a Kickstart Installation”</a> for a description of the syntax and refer to <a class="xref" href="#ks-pxelinux-default">Example 15.2, “Using the <code class="option">ks</code> option in the <code class="filename">pxelinux.cfg/default</code> file”</a> for an example of an <code class="literal">append</code> line.
@@ -4168,23 +4166,23 @@ umount /mnt/temp
For example, if <code class="filename">foo.ks</code> is a kickstart file available on an NFS share at <code class="filename">192.168.0.200:/export/kickstart/</code>, part of your <code class="filename">pxelinux.cfg/default</code> file might include:
</div><pre class="programlisting">label 1
kernel Fedora20/vmlinuz
- append initrd=Fedora20/initrd.img ramdisk_size=10000 ks=nfs:192.168.0.200:/export/kickstart/foo.ks</pre></div></div><br class="example-break" /></div></div><div class="section" id="s1-kickstart2-install-tree"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.9. Making the Installation Tree Available</h2></div></div></div><a id="idm225463118544" class="indexterm"></a><div class="para">
+ append initrd=Fedora20/initrd.img ramdisk_size=10000 ks=nfs:192.168.0.200:/export/kickstart/foo.ks</pre></div></div><br class="example-break" /></div></div><div class="section" id="s1-kickstart2-install-tree"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.9. Making the Installation Tree Available</h2></div></div></div><a id="idm219132039952" class="indexterm"></a><div class="para">
The kickstart installation must access an <em class="firstterm">installation tree</em>. An installation tree is a copy of the binary Fedora DVD with the same directory structure.
</div><div class="para">
If you are performing a DVD-based installation, insert the Fedora installation DVD into the computer before starting the kickstart installation.
</div><div class="para">
If you are performing a hard drive installation, make sure the ISO images of the binary Fedora DVD are on a hard drive in the computer.
- </div><a id="idm225472962784" class="indexterm"></a><a id="idm225424815024" class="indexterm"></a><div class="para">
+ </div><a id="idm219184331088" class="indexterm"></a><a id="idm219184329456" class="indexterm"></a><div class="para">
If you are performing a network-based (NFS, FTP, or HTTP) installation, you must make the installation tree or ISO image available over the network. Refer to <a class="xref" href="#s1-steps-network-installs-x86">Section 5.1, “Preparing for a Network Installation”</a> for details.
- </div></div><div class="section" id="s1-kickstart2-startinginstall"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.10. Starting a Kickstart Installation</h2></div></div></div><a id="idm225448550048" class="indexterm"></a><a id="idm225463724208" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s1-kickstart2-startinginstall"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.10. Starting a Kickstart Installation</h2></div></div></div><a id="idm219182554736" class="indexterm"></a><a id="idm219139031504" class="indexterm"></a><div class="para">
To begin a kickstart installation, you must boot the system from boot media you have made or the Fedora DVD, and enter a special boot command at the boot prompt. The installation program looks for a kickstart file if the <code class="command">ks</code> command line argument is passed to the kernel.
</div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">DVD and local storage</span></dt><dd><div class="para">
- <a id="idm225429858256" class="indexterm"></a>
+ <a id="idm219087705952" class="indexterm"></a>
The <strong class="userinput"><code>linux ks=</code></strong> command also works if the <code class="filename">ks.cfg</code> file is located on a vfat or ext2 file system on local storage and you boot from the Fedora DVD.
</div></dd></dl></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">With Driver Disk</span></dt><dd><div class="para">
If you need to use a driver disk with kickstart, specify the <strong class="userinput"><code>dd</code></strong> option as well. For example, if installation requires a kickstart file on a local hard drive and also requires a driver disk, boot the system with:
</div><pre class="screen">linux ks=hd:<em class="replaceable"><code>partition</code></em>:/<em class="replaceable"><code>path</code></em>/ks.cfg dd</pre></dd><dt class="varlistentry"><span class="term">Boot CD-ROM</span></dt><dd><div class="para">
- <a id="idm225441109440" class="indexterm"></a>
+ <a id="idm219153357120" class="indexterm"></a>
If the kickstart file is on a boot CD-ROM as described in <a class="xref" href="#s2-kickstart2-boot-media">Section 15.8.1, “Creating Kickstart Boot Media”</a>, insert the CD-ROM into the system, boot the system, and enter the following command at the <code class="prompt">boot:</code> prompt (where <code class="filename">ks.cfg</code> is the name of the kickstart file):
</div><pre class="screen">linux ks=cdrom:/ks.cfg</pre></dd></dl></div><div class="para">
Other options to start a kickstart installation are as follows:
@@ -4438,37 +4436,37 @@ umount /mnt/temp
Enable a password for the vnc connection. This will prevent someone from inadvertently connecting to the vnc-based installation.
</div><div class="para">
Requires 'vnc' option to be specified as well.
- </div></dd></dl></div></div></div><div xml:lang="en-US" class="chapter" id="ch-redhat-config-kickstart" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 16. <span class="application"><strong>Kickstart Configurator</strong></span></h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-redhat-config-kickstart-basic">16.1. Basic Configuration</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-install">16.2. Installation Method</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-bootloader">16.3. Boot Loader Options</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-partitions">16.4. Partition Information</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-kickstart-create-part">16.4.1. Creating Partitions</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-redhat-config-kickstart-network">16.5. N
etwork Configuration</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-auth">16.6. Authentication</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-firewall">16.7. Firewall Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-kickstart-firewall-selinux">16.7.1. SELinux Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-redhat-config-kickstart-xconfig">16.8. Display Configuration</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-pkgs">16.9. Package Selection</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-prescript">16.10. Pre-Installation Script</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-postinstall">16.11. Post-Installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-kickstart-nochroot">16.11.1. Chroot Environment</a></span></
dt><dt><span class="section"><a href="#s2-redhat-config-kickstart-interpreter">16.11.2. Use an Interpreter</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-redhat-config-kickstart-savefile">16.12. Saving the File</a></span></dt></dl></div><a id="idm225412501504" class="indexterm"></a><a id="idm225458720288" class="indexterm"></a><div class="para">
+ </div></dd></dl></div></div></div><div xml:lang="en-US" class="chapter" id="ch-redhat-config-kickstart" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 16. <span class="application"><strong>Kickstart Configurator</strong></span></h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-redhat-config-kickstart-basic">16.1. Basic Configuration</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-install">16.2. Installation Method</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-bootloader">16.3. Boot Loader Options</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-partitions">16.4. Partition Information</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-kickstart-create-part">16.4.1. Creating Partitions</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-redhat-config-kickstart-network">16.5. N
etwork Configuration</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-auth">16.6. Authentication</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-firewall">16.7. Firewall Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-kickstart-firewall-selinux">16.7.1. SELinux Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-redhat-config-kickstart-xconfig">16.8. Display Configuration</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-pkgs">16.9. Package Selection</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-prescript">16.10. Pre-Installation Script</a></span></dt><dt><span class="section"><a href="#s1-redhat-config-kickstart-postinstall">16.11. Post-Installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-kickstart-nochroot">16.11.1. Chroot Environment</a></span></
dt><dt><span class="section"><a href="#s2-redhat-config-kickstart-interpreter">16.11.2. Use an Interpreter</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-redhat-config-kickstart-savefile">16.12. Saving the File</a></span></dt></dl></div><a id="idm219154720576" class="indexterm"></a><a id="idm219127646624" class="indexterm"></a><div class="para">
<span class="application"><strong>Kickstart Configurator</strong></span> allows you to create or modify a kickstart file using a graphical user interface, so that you do not have to remember the correct syntax of the file.
</div><div class="para">
<span class="application"><strong>Kickstart Configurator</strong></span> is not installed by default on Fedora 20. Run <code class="command">su - yum install system-config-kickstart</code> or use your graphical package manager to install the software.
</div><div class="para">
To launch <span class="application"><strong>Kickstart Configurator</strong></span>, boot your system into a graphical environment, then run <code class="command">system-config-kickstart</code>, or click <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>Kickstart</strong></span> on the GNOME desktop or <span class="guibutton"><strong>Kickoff Application Launcher</strong></span>+<span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Kickstart</strong></span> on the KDE desktop.
- </div><a id="idm225455423472" class="indexterm"></a><div class="para">
+ </div><a id="idm219200764064" class="indexterm"></a><div class="para">
As you are creating a kickstart file, you can click <span class="guimenu"><strong>File</strong></span> → <span class="guimenuitem"><strong>Preview</strong></span> at any time to review your current selections.
</div><div class="para">
To start with an existing kickstart file, select <span class="guimenu"><strong>File</strong></span> → <span class="guimenuitem"><strong>Open</strong></span> and select the existing file.
- </div><div class="section" id="s1-redhat-config-kickstart-basic"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.1. Basic Configuration</h2></div></div></div><a id="idm225460100928" class="indexterm"></a><div class="figure" id="redhat-config-kickstart-basic-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/ksconfig/ksconfig-basic.png" width="444" alt="Basic Configuration" /><div class="longdesc"><div class="para">
+ </div><div class="section" id="s1-redhat-config-kickstart-basic"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.1. Basic Configuration</h2></div></div></div><a id="idm219153608720" class="indexterm"></a><div class="figure" id="redhat-config-kickstart-basic-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/ksconfig/ksconfig-basic.png" width="444" alt="Basic Configuration" /><div class="longdesc"><div class="para">
Basic Configuration
- </div></div></div></div><h6>Figure 16.1. Basic Configuration</h6></div><br class="figure-break" /><a id="idm225450021056" class="indexterm"></a><div class="para">
+ </div></div></div></div><h6>Figure 16.1. Basic Configuration</h6></div><br class="figure-break" /><a id="idm219173877440" class="indexterm"></a><div class="para">
Choose the language to use during the installation and as the default language to be used after installation from the <span class="guimenu"><strong>Default Language</strong></span> menu.
- </div><a id="idm225442899200" class="indexterm"></a><div class="para">
+ </div><a id="idm219185464720" class="indexterm"></a><div class="para">
Select the system keyboard type from the <span class="guimenu"><strong>Keyboard</strong></span> menu.
- </div><a id="idm225460012928" class="indexterm"></a><div class="para">
+ </div><a id="idm219130990256" class="indexterm"></a><div class="para">
From the <span class="guimenu"><strong>Time Zone</strong></span> menu, choose the time zone to use for the system. To configure the system to use UTC, select <span class="guilabel"><strong>Use UTC clock</strong></span>.
- </div><a id="idm225448940640" class="indexterm"></a><a id="idm225500677600" class="indexterm"></a><div class="para">
+ </div><a id="idm219159192480" class="indexterm"></a><a id="idm219132338272" class="indexterm"></a><div class="para">
Enter the desired root password for the system in the <span class="guilabel"><strong>Root Password</strong></span> text entry box. Type the same password in the <span class="guilabel"><strong>Confirm Password</strong></span> text box. The second field is to make sure you do not mistype the password and then realize you do not know what it is after you have completed the installation. To save the password as an encrypted password in the file, select <span class="guilabel"><strong>Encrypt root password</strong></span>. If the encryption option is selected, when the file is saved, the plain text password that you typed is encrypted and written to the kickstart file. Do not type an already encrypted password and select to encrypt it. Because a kickstart file is a plain text file that can be easily read, it is recommended that an encrypted password be used.
</div><div class="para">
Choosing <span class="guilabel"><strong>Target Architecture</strong></span> specifies which specific hardware architecture distribution is used during installation.
</div><div class="para">
Choosing <span class="guilabel"><strong>Target Architecture</strong></span> specifies which specific hardware architecture distribution is used during installation.
- </div><a id="idm225463900560" class="indexterm"></a><div class="para">
+ </div><a id="idm219170785056" class="indexterm"></a><div class="para">
Choosing <span class="guilabel"><strong>Reboot system after installation</strong></span> reboots your system automatically after the installation is finished.
- </div><a id="idm225477300752" class="indexterm"></a><div class="para">
+ </div><a id="idm219202459072" class="indexterm"></a><div class="para">
Kickstart installations are performed in graphical mode by default. To override this default and use text mode instead, select the <span class="guilabel"><strong>Perform installation in text mode</strong></span> option.
- </div><a id="idm225420591328" class="indexterm"></a><div class="para">
+ </div><a id="idm219176031232" class="indexterm"></a><div class="para">
You can perform a kickstart installation in interactive mode. This means that the installation program uses all the options pre-configured in the kickstart file, but it allows you to preview the options in each screen before continuing to the next screen. To continue to the next screen, click the <span class="guibutton"><strong>Next</strong></span> button after you have approved the settings or change them before continuing the installation. To select this type of installation, select the <span class="guilabel"><strong>Perform installation in interactive mode</strong></span> option.
- </div></div><div class="section" id="s1-redhat-config-kickstart-install"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.2. Installation Method</h2></div></div></div><a id="idm225422235760" class="indexterm"></a><div class="figure" id="redhat-config-kickstart-install-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/ksconfig/ksconfig-install.png" width="444" alt="Installation Method" /><div class="longdesc"><div class="para">
+ </div></div><div class="section" id="s1-redhat-config-kickstart-install"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.2. Installation Method</h2></div></div></div><a id="idm219168741376" class="indexterm"></a><div class="figure" id="redhat-config-kickstart-install-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/ksconfig/ksconfig-install.png" width="444" alt="Installation Method" /><div class="longdesc"><div class="para">
Kickstart Installation Method
</div></div></div></div><h6>Figure 16.2. Installation Method</h6></div><br class="figure-break" /><div class="para">
The <span class="guilabel"><strong>Installation Method</strong></span> screen allows you to choose whether to perform a new installation or an upgrade. If you choose upgrade, the <span class="guilabel"><strong>Partition Information</strong></span> and <span class="guilabel"><strong>Package Selection</strong></span> options are disabled. They are not supported for kickstart upgrades.
@@ -4484,9 +4482,9 @@ umount /mnt/temp
<span class="guilabel"><strong>HTTP</strong></span> — Choose this option to install or upgrade from an HTTP server. In the text field for the HTTP server, enter the fully-qualified domain name or IP address. For the HTTP directory, enter the name of the HTTP directory that contains the <code class="filename"><em class="replaceable"><code>variant</code></em></code> directory. For example, if the HTTP server contains the directory <code class="filename">/mirrors/redhat/i386/Server/</code>, enter <code class="filename">/mirrors/redhat/i386/Server/</code> for the HTTP directory.
</div></li><li class="listitem"><div class="para">
<span class="guilabel"><strong>Hard Drive</strong></span> — Choose this option to install or upgrade from a hard drive. Hard drive installations require the use of ISO images. Be sure to verify that the ISO images are intact before you start the installation. To verify them, use an <code class="command">md5sum</code> program as well as the <code class="command">linux rd.live.check</code> boot option as discussed in <a class="xref" href="#sect-boot-options-mediacheck">Section 11.3.2, “Verifying Boot Media”</a>. Enter the hard drive partition that contains the ISO images (for example, <code class="filename">/dev/hda1</code>) in the <span class="guilabel"><strong>Hard Drive Partition</strong></span> text box. Enter the directory that contains the ISO images in the <span class="guilabel"><strong>Hard Drive Directory</strong></span> text box.
- </div></li></ul></div></div><div class="section" id="s1-redhat-config-kickstart-bootloader"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.3. Boot Loader Options</h2></div></div></div><div class="figure" id="redhat-config-kickstart-bootloader-fig"><div class="figure-contents"><a id="idm225436917904" class="indexterm"></a><div class="mediaobject"><img src="images/ksconfig/ksconfig-bootloader.png" width="444" alt="Boot Loader Options" /><div class="longdesc"><div class="para">
+ </div></li></ul></div></div><div class="section" id="s1-redhat-config-kickstart-bootloader"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.3. Boot Loader Options</h2></div></div></div><div class="figure" id="redhat-config-kickstart-bootloader-fig"><div class="figure-contents"><a id="idm219167789440" class="indexterm"></a><div class="mediaobject"><img src="images/ksconfig/ksconfig-bootloader.png" width="444" alt="Boot Loader Options" /><div class="longdesc"><div class="para">
Boot Loader Options
- </div></div></div></div><h6>Figure 16.3. Boot Loader Options</h6></div><br class="figure-break" /><a id="idm225463079952" class="indexterm"></a><div class="para">
+ </div></div></div></div><h6>Figure 16.3. Boot Loader Options</h6></div><br class="figure-break" /><a id="idm219159089344" class="indexterm"></a><div class="para">
Please note that this screen will be disabled if you have specified a target architecture other than x86 / x86_64.
</div><div class="para">
GRUB is the default boot loader for Fedora on x86 / x86_64 architectures. If you do not want to install a boot loader, select <span class="guilabel"><strong>Do not install a boot loader</strong></span>. If you choose not to install a boot loader, make sure you create a boot diskette or have another way to boot your system, such as a third-party boot loader.
@@ -4500,7 +4498,7 @@ umount /mnt/temp
Whenever you are required to enter this password, you will also be asked for a username, which is <code class="command">root</code>.
</div><div class="para">
If <span class="guilabel"><strong>Upgrade an existing installation</strong></span> is selected on the <span class="guilabel"><strong>Installation Method</strong></span> page, select <span class="guilabel"><strong>Upgrade existing boot loader</strong></span> to upgrade the existing boot loader configuration, while preserving the old entries.
- </div></div><div class="section" id="s1-redhat-config-kickstart-partitions"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.4. Partition Information</h2></div></div></div><a id="idm225455838784" class="indexterm"></a><div class="figure" id="redhat-config-kickstart-partitions-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/ksconfig/ksconfig-partitions.png" width="444" alt="Partition Information" /><div class="longdesc"><div class="para">
+ </div></div><div class="section" id="s1-redhat-config-kickstart-partitions"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.4. Partition Information</h2></div></div></div><a id="idm219180025856" class="indexterm"></a><div class="figure" id="redhat-config-kickstart-partitions-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/ksconfig/ksconfig-partitions.png" width="444" alt="Partition Information" /><div class="longdesc"><div class="para">
Kickstart Partition Information
</div></div></div></div><h6>Figure 16.4. Partition Information</h6></div><br class="figure-break" /><div class="para">
Select whether or not to clear the Master Boot Record (MBR). Choose to remove all existing partitions, remove all existing Linux partitions, or preserve existing partitions.
@@ -4526,7 +4524,7 @@ umount /mnt/temp
To edit an existing partition, select the partition from the list and click the <span class="guibutton"><strong>Edit</strong></span> button. The same <span class="guilabel"><strong>Partition Options</strong></span> window appears as when you chose to add a partition as shown in <a class="xref" href="#redhat-config-kickstart-add-part-fig">Figure 16.5, “Creating Partitions”</a>, except it reflects the values for the selected partition. Modify the partition options and click <span class="guibutton"><strong>OK</strong></span>.
</div><div class="para">
To delete an existing partition, select the partition from the list and click the <span class="guibutton"><strong>Delete</strong></span> button.
- </div><div class="section" id="s3-redhat-config-kickstart-raid"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">16.4.1.1. Creating Software RAID Partitions</h4></div></div></div><a id="idm225447559648" class="indexterm"></a><a id="idm225419960544" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-redhat-config-kickstart-raid"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">16.4.1.1. Creating Software RAID Partitions</h4></div></div></div><a id="idm219181305536" class="indexterm"></a><a id="idm219171338320" class="indexterm"></a><div class="para">
To create a software RAID partition, use the following steps:
</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
Click the <span class="guibutton"><strong>RAID</strong></span> button.
@@ -4550,15 +4548,15 @@ umount /mnt/temp
Software RAID Device
</div></div></div></div><h6>Figure 16.7. Creating a Software RAID Device</h6></div><br class="figure-break" /></li><li class="listitem"><div class="para">
Click <span class="guibutton"><strong>OK</strong></span> to add the device to the list.
- </div></li></ol></div></div></div></div><div class="section" id="s1-redhat-config-kickstart-network"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.5. Network Configuration</h2></div></div></div><a id="idm225472760864" class="indexterm"></a><div class="figure" id="redhat-config-kickstart-network-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/ksconfig/ksconfig-network.png" width="444" alt="Network Configuration" /><div class="longdesc"><div class="para">
+ </div></li></ol></div></div></div></div><div class="section" id="s1-redhat-config-kickstart-network"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.5. Network Configuration</h2></div></div></div><a id="idm219176313680" class="indexterm"></a><div class="figure" id="redhat-config-kickstart-network-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/ksconfig/ksconfig-network.png" width="444" alt="Network Configuration" /><div class="longdesc"><div class="para">
Network Configuration for Kickstart
</div></div></div></div><h6>Figure 16.8. Network Configuration</h6></div><br class="figure-break" /><div class="para">
If the system to be installed via kickstart does not have an Ethernet card, do not configure one on the <span class="guilabel"><strong>Network Configuration</strong></span> page.
</div><div class="para">
- Networking is only required if you choose a networking-based installation method (NFS, FTP, or HTTP). Networking can always be configured after installation with the <span class="application"><strong>Network Administration Tool</strong></span> (<code class="command">system-config-network</code>). Refer to the Fedora Deployment Guide for details.
+ Networking is only required if you choose a networking-based installation method (NFS, FTP, or HTTP). Networking can always be configured after installation. Refer to the <em class="citetitle">Fedora System Administrators Guide</em> for details.
</div><div class="para">
For each Ethernet card on the system, click <span class="guibutton"><strong>Add Network Device</strong></span> and select the network device and network type for the device. Select <span class="guilabel"><strong>eth0</strong></span> to configure the first Ethernet card, <span class="guilabel"><strong>eth1</strong></span> for the second Ethernet card, and so on.
- </div></div><div class="section" id="s1-redhat-config-kickstart-auth"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.6. Authentication</h2></div></div></div><a id="idm225477928736" class="indexterm"></a><div class="figure" id="redhat-config-kickstart-auth-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/ksconfig/ksconfig-auth.png" width="444" alt="Authentication" /><div class="longdesc"><div class="para">
+ </div></div><div class="section" id="s1-redhat-config-kickstart-auth"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.6. Authentication</h2></div></div></div><a id="idm219133245552" class="indexterm"></a><div class="figure" id="redhat-config-kickstart-auth-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/ksconfig/ksconfig-auth.png" width="444" alt="Authentication" /><div class="longdesc"><div class="para">
Authentication for Kickstart
</div></div></div></div><h6>Figure 16.9. Authentication</h6></div><br class="figure-break" /><div class="para">
In the <span class="guilabel"><strong>Authentication</strong></span> section, select whether to use shadow passwords and MD5 encryption for user passwords. These options are highly recommended and chosen by default.
@@ -4577,8 +4575,8 @@ umount /mnt/temp
</div></li><li class="listitem"><div class="para">
Name Switch Cache
</div></li></ul></div><div class="para">
- These methods are not enabled by default. To enable one or more of these methods, click the appropriate tab, click the checkbox next to <span class="guilabel"><strong>Enable</strong></span>, and enter the appropriate information for the authentication method. Refer to the Fedora Deployment Guide for more information about the options.
- </div></div><div class="section" id="s1-redhat-config-kickstart-firewall"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.7. Firewall Configuration</h2></div></div></div><a id="idm225440983904" class="indexterm"></a><div class="para">
+ These methods are not enabled by default. To enable one or more of these methods, click the appropriate tab, click the checkbox next to <span class="guilabel"><strong>Enable</strong></span>, and enter the appropriate information for the authentication method. Refer to the <em class="citetitle">Fedora System Administrators Guide</em> for more information about the options.
+ </div></div><div class="section" id="s1-redhat-config-kickstart-firewall"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.7. Firewall Configuration</h2></div></div></div><a id="idm219138104880" class="indexterm"></a><div class="para">
The <span class="guilabel"><strong>Firewall Configuration</strong></span> window is similar to the screen in the installation program and the <span class="application"><strong>Security Level Configuration Tool</strong></span>.
</div><div class="figure" id="redhat-config-kickstart-firewall-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/ksconfig/ksconfig-firewall.png" width="444" alt="Firewall Configuration" /><div class="longdesc"><div class="para">
Firewall Configuration for Kickstart
@@ -4592,15 +4590,15 @@ umount /mnt/temp
If a service is selected in the <span class="guilabel"><strong>Trusted services</strong></span> list, connections for the service are accepted and processed by the system.
</div><div class="para">
In the <span class="guilabel"><strong>Other ports</strong></span> text field, list any additional ports that should be opened for remote access. Use the following format: <strong class="userinput"><code>port:protocol</code></strong>. For example, to allow IMAP access through the firewall, specify <strong class="userinput"><code>imap:tcp</code></strong>. Numeric ports can also be specified explicitly; to allow UDP packets on port 1234 through the firewall, enter <strong class="userinput"><code>1234:udp</code></strong>. To specify multiple ports, separate them with commas.
- </div><div class="section" id="s2-redhat-config-kickstart-firewall-selinux"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.7.1. SELinux Configuration</h3></div></div></div><a id="idm225443229584" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s2-redhat-config-kickstart-firewall-selinux"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.7.1. SELinux Configuration</h3></div></div></div><a id="idm219184426464" class="indexterm"></a><div class="para">
Kickstart can set SELinux to <code class="command">enforcing</code>, <code class="command">permissive</code> or <code class="command">disabled</code> mode. Finer grained configuration is not possible at this time.
- </div></div></div><div class="section" id="s1-redhat-config-kickstart-xconfig"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.8. Display Configuration</h2></div></div></div><a id="idm225501098368" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s1-redhat-config-kickstart-xconfig"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.8. Display Configuration</h2></div></div></div><a id="idm219184037408" class="indexterm"></a><div class="para">
If you are installing the X Window System, you can configure it during the kickstart installation by checking the <span class="guilabel"><strong>Configure the X Window System</strong></span> option on the <span class="guilabel"><strong>Display Configuration</strong></span> window as shown in <a class="xref" href="#xconfig-fig">Figure 16.11, “X Configuration”</a>. If this option is not chosen, the X configuration options are disabled and the <code class="command">skipx</code> option is written to the kickstart file.
</div><div class="figure" id="xconfig-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/ksconfig/ksconfig-xconfig.png" width="444" alt="X Configuration" /><div class="longdesc"><div class="para">
X Configuration for Kickstart
</div></div></div></div><h6>Figure 16.11. X Configuration</h6></div><br class="figure-break" /><div class="para">
Select whether to start the Setup Agent the first time the installed system boots. The Setup Agent is disabled by default, but the setting can be changed to enabled or enabled in reconfiguration mode. Reconfiguration mode enables the language, mouse, keyboard, root password, security level, time zone, and networking configuration options in addition to the default ones.
- </div></div><div class="section" id="s1-redhat-config-kickstart-pkgs"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.9. Package Selection</h2></div></div></div><a id="idm225467073936" class="indexterm"></a><div class="figure" id="redhat-config-kickstart-pkgs-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/ksconfig/ksconfig-pkgs.png" width="444" alt="Package Selection" /><div class="longdesc"><div class="para">
+ </div></div><div class="section" id="s1-redhat-config-kickstart-pkgs"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.9. Package Selection</h2></div></div></div><a id="idm219162793696" class="indexterm"></a><div class="figure" id="redhat-config-kickstart-pkgs-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/ksconfig/ksconfig-pkgs.png" width="444" alt="Package Selection" /><div class="longdesc"><div class="para">
Package Selection for Kickstart
</div></div></div></div><h6>Figure 16.12. Package Selection</h6></div><br class="figure-break" /><div class="para">
The <span class="guilabel"><strong>Package Selection</strong></span> window allows you to choose which package groups to install.
@@ -4608,7 +4606,7 @@ umount /mnt/temp
Package resolution is carried out automatically.
</div><div class="para">
Currently, <span class="application"><strong>Kickstart Configurator </strong></span> does not allow you to select individual packages. To install individual packages, modify the <code class="command">%packages</code> section of the kickstart file after you save it. Refer to <a class="xref" href="#s1-kickstart2-packageselection">Section 15.5, “Package Selection”</a> for details.
- </div></div><div class="section" id="s1-redhat-config-kickstart-prescript"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.10. Pre-Installation Script</h2></div></div></div><a id="idm225494954864" class="indexterm"></a><div class="figure" id="redhat-config-kickstart-prescript-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/ksconfig/ksconfig-prescript.png" width="444" alt="Pre-Installation Script" /><div class="longdesc"><div class="para">
+ </div></div><div class="section" id="s1-redhat-config-kickstart-prescript"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.10. Pre-Installation Script</h2></div></div></div><a id="idm219145567776" class="indexterm"></a><div class="figure" id="redhat-config-kickstart-prescript-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/ksconfig/ksconfig-prescript.png" width="444" alt="Pre-Installation Script" /><div class="longdesc"><div class="para">
Pre-Installation Script for Kickstart
</div></div></div></div><h6>Figure 16.13. Pre-Installation Script</h6></div><br class="figure-break" /><div class="para">
You can add commands to run on the system immediately after the kickstart file has been parsed and before the installation begins. If you have configured the network in the kickstart file, the network is enabled before this section is processed. To include a pre-installation script, type it in the text area.
@@ -4622,7 +4620,7 @@ umount /mnt/temp
Do not include the <code class="command">%pre</code> command. It is added for you.
</div></div></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
The pre-installation script is run after the source media is mounted and stage 2 of the bootloader has been loaded. For this reason it is not possible to change the source media in the pre-installation script.
- </div></div></div></div><div class="section" id="s1-redhat-config-kickstart-postinstall"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.11. Post-Installation Script</h2></div></div></div><a id="idm225462786736" class="indexterm"></a><div class="figure" id="redhat-config-kickstart-postinstall-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/ksconfig/ksconfig-postscript.png" width="444" alt="Post-Installation Script" /><div class="longdesc"><div class="para">
+ </div></div></div></div><div class="section" id="s1-redhat-config-kickstart-postinstall"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.11. Post-Installation Script</h2></div></div></div><a id="idm219181548976" class="indexterm"></a><div class="figure" id="redhat-config-kickstart-postinstall-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/ksconfig/ksconfig-postscript.png" width="444" alt="Post-Installation Script" /><div class="longdesc"><div class="para">
Post-Installation Script for Kickstart
</div></div></div></div><h6>Figure 16.14. Post-Installation Script</h6></div><br class="figure-break" /><div class="para">
You can also add commands to execute on the system after the installation is completed. If the network is properly configured in the kickstart file, the network is enabled, and the script can include commands to access resources on the network. To include a post-installation script, type it in the text area.
@@ -4642,7 +4640,7 @@ umount /mnt/temp
</div><pre class="screen">
<code class="command">echo "Hackers will be punished" > /mnt/sysimage/etc/motd</code></pre></div><div class="section" id="s2-redhat-config-kickstart-interpreter"><div class="titlepage"><div><div keep-