commit 7d4063af954bfaddee4aa29157f222ce9064e0c0
Author: Jack Reed <jreed(a)redhat.com>
Date: Thu Oct 27 15:42:25 2011 +1000
BZ#709317, 668549, 695280, 714340
fedoradocs.db | Bin 614400 -> 614400 bytes
public_html/Sitemap | 8 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/as-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/as-IN/opds-Fedora_Core.xml | 2 +-
.../as-IN/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/as-IN/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/bg-BG/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/bg-BG/opds-Fedora_Core.xml | 2 +-
.../bg-BG/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/bg-BG/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/bn-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/bn-IN/opds-Fedora_Core.xml | 2 +-
.../bn-IN/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/bn-IN/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/bs-BA/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/bs-BA/opds-Fedora_Core.xml | 2 +-
.../bs-BA/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/bs-BA/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ca-ES/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ca-ES/opds-Fedora_Core.xml | 2 +-
.../ca-ES/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/ca-ES/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/cs-CZ/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/cs-CZ/opds-Fedora_Core.xml | 2 +-
.../cs-CZ/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/cs-CZ/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/da-DK/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/da-DK/opds-Fedora_Core.xml | 2 +-
.../da-DK/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/da-DK/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/de-DE/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/de-DE/opds-Fedora_Core.xml | 2 +-
.../de-DE/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/de-DE/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/el-GR/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/el-GR/opds-Fedora_Core.xml | 2 +-
.../el-GR/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/el-GR/opds.xml | 12 +-
...Documentation-0.1-Installation_Guide-en-US.epub | Bin 7242458 -> 7242738 bytes
.../0.1/html-single/Installation_Guide/index.html | 780 ++++++++++----------
.../Installation_Guide/Adding_Partitions-x86.html | 8 +-
.../Assign_Storage_Devices-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 +-
.../html/Installation_Guide/Disk_Space-x86.html | 6 +-
.../Installation-Guide-Preface.html | 8 +-
.../Installation_Guide/Storage_Devices-x86.html | 6 +-
.../Trouble_After_Booting-GUI.html | 2 +-
.../VNC_Whitepaper-firewall-considerations.html | 2 +-
.../VNC_Whitepaper-installation.html | 4 +-
.../VNC_Whitepaper-kickstart-installation.html | 2 +-
.../VNC_Whitepaper-vnc-connect-mode.html | 6 +-
.../html/Installation_Guide/ap-admin-options.html | 4 +-
.../0.1/html/Installation_Guide/ap-rescuemode.html | 22 +-
.../0.1/html/Installation_Guide/ap-techref.html | 26 +-
.../0.1/html/Installation_Guide/apcs02.html | 4 +-
.../0.1/html/Installation_Guide/apcs02s02.html | 2 +-
.../0.1/html/Installation_Guide/apcs02s03.html | 2 +-
.../0.1/html/Installation_Guide/apcs03.html | 4 +-
.../0.1/html/Installation_Guide/apcs04.html | 4 +-
.../0.1/html/Installation_Guide/apcs04s03.html | 2 +-
.../0.1/html/Installation_Guide/apcs04s04.html | 2 +-
.../0.1/html/Installation_Guide/apcs04s05.html | 2 +-
.../0.1/html/Installation_Guide/apcs04s06.html | 2 +-
.../0.1/html/Installation_Guide/apcs04s07.html | 2 +-
.../0.1/html/Installation_Guide/apcs05.html | 6 +-
.../0.1/html/Installation_Guide/apcs05s02.html | 2 +-
.../0.1/html/Installation_Guide/apcs05s03.html | 2 +-
.../0.1/html/Installation_Guide/ch-Boot-x86.html | 32 +-
.../ch-Installation_Phase_2-x86.html | 6 +-
.../html/Installation_Guide/ch-Preparing-x86.html | 6 +-
.../Installation_Guide/ch-boot-init-shutdown.html | 4 +-
.../0.1/html/Installation_Guide/ch-ent-table.html | 2 +-
.../0.1/html/Installation_Guide/ch-firstboot.html | 2 +-
.../0.1/html/Installation_Guide/ch-grub.html | 4 +-
.../html/Installation_Guide/ch-guimode-x86.html | 4 +-
.../0.1/html/Installation_Guide/ch-kickstart2.html | 2 +-
.../0.1/html/Installation_Guide/ch-new-users.html | 16 +-
.../0.1/html/Installation_Guide/ch-next-steps.html | 6 +-
.../html/Installation_Guide/ch-partitions-x86.html | 40 +-
.../ch-redhat-config-kickstart.html | 20 +-
.../0.1/html/Installation_Guide/ch-steps-x86.html | 2 +-
.../html/Installation_Guide/ch-trouble-x86.html | 6 +-
.../html/Installation_Guide/ch-upgrade-x86.html | 6 +-
.../html/Installation_Guide/ch-x86-uninstall.html | 2 +-
.../0.1/html/Installation_Guide/ch04s06.html | 2 +-
.../0.1/html/Installation_Guide/ch08s04.html | 2 +-
.../0.1/html/Installation_Guide/ch10s02.html | 2 +-
.../0.1/html/Installation_Guide/ch10s04.html | 2 +-
.../0.1/html/Installation_Guide/ch10s04s03.html | 2 +-
.../0.1/html/Installation_Guide/ch10s04s04.html | 2 +-
.../0.1/html/Installation_Guide/ch10s04s05.html | 2 +-
.../0.1/html/Installation_Guide/ch10s04s07.html | 2 +-
.../0.1/html/Installation_Guide/ch10s04s08.html | 2 +-
.../0.1/html/Installation_Guide/ch13s05s05.html | 2 +-
.../0.1/html/Installation_Guide/ch20s02.html | 2 +-
.../0.1/html/Installation_Guide/index.html | 6 +-
.../0.1/html/Installation_Guide/ix01.html | 2 +-
.../Installation_Guide/netboot-performing.html | 2 +-
.../0.1/html/Installation_Guide/pr01s02.html | 2 +-
.../0.1/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 +-
.../Installation_Guide/rescuemode_drivers.html | 2 +-
.../Installation_Guide/s1-begininstall-hd-x86.html | 2 +-
.../s1-begininstall-nfs-x86.html | 2 +-
.../s1-begininstall-perform-nfs-x86.html | 2 +-
.../s1-begininstall-url-x86.html | 2 +-
.../s1-boot-init-shutdown-process.html | 6 +-
.../s1-boot-init-shutdown-run-boot.html | 2 +-
.../s1-boot-init-shutdown-shutdown.html | 2 +-
.../s1-boot-init-shutdown-sysv.html | 4 +-
.../s1-diskpartitioning-x86.html | 2 +-
.../Installation_Guide/s1-diskpartsetup-x86.html | 6 +-
.../s1-grub-additional-resources.html | 4 +-
.../html/Installation_Guide/s1-grub-commands.html | 2 +-
.../Installation_Guide/s1-grub-configfile.html | 4 +-
.../Installation_Guide/s1-grub-installing.html | 4 +-
.../Installation_Guide/s1-grub-interfaces.html | 4 +-
.../html/Installation_Guide/s1-grub-runlevels.html | 2 +-
.../Installation_Guide/s1-grub-terminology.html | 4 +-
.../html/Installation_Guide/s1-grub-whatis.html | 8 +-
.../s1-guimode-interface-x86.html | 4 +-
.../s1-installationmethod-x86.html | 8 +-
.../Installation_Guide/s1-installmethod-x86.html | 10 +-
.../Installation_Guide/s1-installpkgs-x86.html | 4 +-
.../Installation_Guide/s1-kickstart2-file.html | 2 +-
.../s1-kickstart2-install-tree.html | 4 +-
.../Installation_Guide/s1-kickstart2-options.html | 110 ++--
.../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 +-
.../Installation_Guide/s1-langselection-x86.html | 2 +-
.../Installation_Guide/s1-netboot-add-hosts.html | 2 +-
.../Installation_Guide/s1-netboot-pxe-config.html | 2 +-
.../html/Installation_Guide/s1-netboot-tftp.html | 2 +-
.../Installation_Guide/s1-pkgselection-x86.html | 4 +-
.../s1-redhat-config-kickstart-auth.html | 2 +-
.../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 | 2 +-
.../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 | 6 +-
.../html/Installation_Guide/s1-timezone-x86.html | 2 +-
.../Installation_Guide/s1-trouble-install-x86.html | 2 +-
.../html/Installation_Guide/s1-x86-bootloader.html | 12 +-
.../s2-boot-init-shutdown-init.html | 10 +-
.../s2-boot-init-shutdown-kernel.html | 2 +-
.../s2-boot-init-shutdown-loader.html | 6 +-
.../s2-boot-init-shutdown-sysv-util.html | 2 +-
.../s2-diskpartrecommend-x86.html | 8 +-
.../s2-grub-configfile-commands.html | 2 +-
.../s2-grub-terminology-files.html | 2 +-
.../s2-grub-terminology-rootfs.html | 2 +-
.../s2-grub-useful-websites.html | 2 +-
.../s2-grub-whatis-booting-uefi.html | 2 +-
.../s2-grub-whatis-features.html | 2 +-
.../s2-kickstart2-networkbased.html | 2 +-
.../Installation_Guide/s2-netboot-custom-msg.html | 2 +-
.../s2-trouble-completeparts-x86.html | 2 +-
.../s2-trouble-part-tables-x86.html | 2 +-
.../html/Installation_Guide/s2-trouble-ram.html | 2 +-
.../Installation_Guide/s2-trouble-space-x86.html | 2 +-
.../s2-trouble-tracebacks-x86.html | 2 +-
.../Installation_Guide/s2-x86-bootloader-alt.html | 2 +-
.../s2-x86-bootloader-rescue.html | 2 +-
.../sn-Is_Your_Hardware_Compatible-x86.html | 2 +-
.../html/Installation_Guide/sn-Netconfig-x86.html | 16 +-
.../sn-account_configuration-x86.html | 6 +-
.../sn-automating-installation.html | 2 +-
.../0.1/html/Installation_Guide/sn-boot-modes.html | 2 +-
.../sn-booting-from-pxe-x86.html | 2 +-
.../sn-cobbler-setup-distro.html | 4 +-
.../Installation_Guide/sn-expert-download.html | 2 +-
.../html/Installation_Guide/sn-expert-prepare.html | 2 +-
.../Installation_Guide/sn-firstboot-datetime.html | 2 +-
.../sn-guimode-virtual-consoles-x86.html | 2 +-
.../Installation_Guide/sn-initialize-hdd-x86.html | 2 +-
.../html/Installation_Guide/sn-keyboard-x86.html | 2 +-
.../html/Installation_Guide/sn-making-media.html | 2 +-
.../html/Installation_Guide/sn-mode-rescue.html | 4 +-
.../sn-package-selection-x86.html | 2 +-
.../Installation_Guide/sn-partitioning-lvm.html | 8 +-
.../sn-partitioning-raid-x86.html | 2 +-
.../Installation_Guide/sn-pxe-server-manual.html | 4 +-
.../html/Installation_Guide/sn-remote-logging.html | 2 +-
.../sn-remoteaccess-installation-vnclistener.html | 2 +-
.../sn-remoteaccess-installation.html | 6 +-
.../Installation_Guide/sn-ssh-installation.html | 2 +-
.../sn-switching-to-gui-login.html | 8 +-
.../Installation_Guide/sn-telnet-installation.html | 2 +-
.../sn-upgrading-bootloader-x86.html | 2 +-
..._Documentation-0.1-Installation_Guide-en-US.pdf | Bin 4256368 -> 4259527 bytes
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/en-US/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/en-US/opds-Fedora_Core.xml | 2 +-
.../en-US/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/en-US/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/es-ES/opds-Fedora.xml | 2 +-
public_html/es-ES/opds-Fedora_15.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/es-ES/opds-Fedora_Core.xml | 2 +-
.../es-ES/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/es-ES/opds.xml | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/fa-IR/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/fa-IR/opds-Fedora_Core.xml | 2 +-
.../fa-IR/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/fa-IR/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/fi-FI/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/fi-FI/opds-Fedora_Core.xml | 2 +-
.../fi-FI/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/fi-FI/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/fr-FR/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/fr-FR/opds-Fedora_Core.xml | 2 +-
.../fr-FR/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/fr-FR/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/gu-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/gu-IN/opds-Fedora_Core.xml | 2 +-
.../gu-IN/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/gu-IN/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/he-IL/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/he-IL/opds-Fedora_Core.xml | 2 +-
.../he-IL/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/he-IL/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/hi-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/hi-IN/opds-Fedora_Core.xml | 2 +-
.../hi-IN/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/hi-IN/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/hu-HU/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/hu-HU/opds-Fedora_Core.xml | 2 +-
.../hu-HU/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/hu-HU/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/id-ID/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/id-ID/opds-Fedora_Core.xml | 2 +-
.../id-ID/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/id-ID/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/it-IT/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/it-IT/opds-Fedora_Core.xml | 2 +-
.../it-IT/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/it-IT/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ja-JP/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ja-JP/opds-Fedora_Core.xml | 2 +-
.../ja-JP/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/ja-JP/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/kn-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/kn-IN/opds-Fedora_Core.xml | 2 +-
.../kn-IN/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/kn-IN/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ko-KR/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ko-KR/opds-Fedora_Core.xml | 2 +-
.../ko-KR/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/ko-KR/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ml-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ml-IN/opds-Fedora_Core.xml | 2 +-
.../ml-IN/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/ml-IN/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/mr-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/mr-IN/opds-Fedora_Core.xml | 2 +-
.../mr-IN/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/mr-IN/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/nb-NO/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/nb-NO/opds-Fedora_Core.xml | 2 +-
.../nb-NO/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/nb-NO/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/nl-NL/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/nl-NL/opds-Fedora_Core.xml | 2 +-
.../nl-NL/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/nl-NL/opds.xml | 12 +-
public_html/opds.xml | 88 ++--
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/or-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/or-IN/opds-Fedora_Core.xml | 2 +-
.../or-IN/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/or-IN/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pa-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pa-IN/opds-Fedora_Core.xml | 2 +-
.../pa-IN/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/pa-IN/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pl-PL/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pl-PL/opds-Fedora_Core.xml | 2 +-
.../pl-PL/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/pl-PL/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pt-BR/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pt-BR/opds-Fedora_Core.xml | 2 +-
.../pt-BR/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/pt-BR/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pt-PT/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pt-PT/opds-Fedora_Core.xml | 2 +-
.../pt-PT/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/pt-PT/opds.xml | 12 +-
.../ro/opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ro/opds-Fedora.xml | 2 +-
.../ro/opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ro/opds-Fedora_Core.xml | 2 +-
public_html/ro/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/ro/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ru-RU/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ru-RU/opds-Fedora_Core.xml | 2 +-
.../ru-RU/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/ru-RU/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sk-SK/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sk-SK/opds-Fedora_Core.xml | 2 +-
.../sk-SK/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/sk-SK/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sr-Latn-RS/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sr-Latn-RS/opds-Fedora_Core.xml | 2 +-
.../sr-Latn-RS/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/sr-Latn-RS/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sr-RS/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sr-RS/opds-Fedora_Core.xml | 2 +-
.../sr-RS/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/sr-RS/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sv-SE/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sv-SE/opds-Fedora_Core.xml | 2 +-
.../sv-SE/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/sv-SE/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ta-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ta-IN/opds-Fedora_Core.xml | 2 +-
.../ta-IN/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/ta-IN/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/te-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/te-IN/opds-Fedora_Core.xml | 2 +-
.../te-IN/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/te-IN/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/uk-UA/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/uk-UA/opds-Fedora_Core.xml | 2 +-
.../uk-UA/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/uk-UA/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/zh-CN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/zh-CN/opds-Fedora_Core.xml | 2 +-
.../zh-CN/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/zh-CN/opds.xml | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/zh-TW/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/zh-TW/opds-Fedora_Core.xml | 2 +-
.../zh-TW/opds-Fedora_Draft_Documentation.xml | 4 +-
public_html/zh-TW/opds.xml | 12 +-
428 files changed, 1350 insertions(+), 1350 deletions(-)
---
diff --git a/fedoradocs.db b/fedoradocs.db
index a1c59a6..3adde0b 100644
Binary files a/fedoradocs.db and b/fedoradocs.db differ
diff --git a/public_html/Sitemap b/public_html/Sitemap
index 5cdae5f..7f51970 100644
--- a/public_html/Sitemap
+++ b/public_html/Sitemap
@@ -3962,25 +3962,25 @@
</url>
<url>
<loc>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Ins…</loc>
- <lastmod>2011-10-26</lastmod>
+ <lastmod>2011-10-27</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Ins…</loc>
- <lastmod>2011-10-26</lastmod>
+ <lastmod>2011-10-27</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html-sin…</loc>
- <lastmod>2011-10-26</lastmod>
+ <lastmod>2011-10-27</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/pdf/Inst…</loc>
- <lastmod>2011-10-26</lastmod>
+ <lastmod>2011-10-27</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 3be9781..473dc7b 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>2011-10-26T05:58:23</updated>
+ <updated>2011-10-27T05:38:22</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 76dd956..02425ff 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>2011-10-26T05:58:25</updated>
+ <updated>2011-10-27T05:38:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
index 110467c..f180262 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>2011-10-26T05:58:25</updated>
+ <updated>2011-10-27T05:38:24</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 40c3db0..2f68532 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>2011-10-26T05:58:25</updated>
+ <updated>2011-10-27T05:38:24</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 5cf01fb..73602ab 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>2011-10-26T05:58:25</updated>
+ <updated>2011-10-27T05:38:24</updated>
<!--author>
<name></name>
<uri></uri>
@@ -133,7 +133,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2011-10-26</updated>
+ <updated>2011-10-27</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.xml b/public_html/as-IN/opds.xml
index 9708cb5..4771e09 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>2011-10-26T05:58:25</updated>
+ <updated>2011-10-27T05:38:25</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>2011-10-26T05:58:23</updated>
+ <updated>2011-10-27T05:38:22</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>2011-10-26T05:58:25</updated>
+ <updated>2011-10-27T05:38:24</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>2011-10-26T05:58:25</updated>
+ <updated>2011-10-27T05:38:24</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>2011-10-26T05:58:25</updated>
+ <updated>2011-10-27T05:38:24</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 Draft Documentation</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Draft_Documentation/opds-Fedora_…</id>
- <updated>2011-10-26T05:58:25</updated>
+ <updated>2011-10-27T05:38:24</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/bg-BG/opds-Community_Services_Infrastructure.xml b/public_html/bg-BG/opds-Community_Services_Infrastructure.xml
index 7eb7a94..c74443b 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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 ba6320d..fb70069 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml b/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
index d694dd7..1badea3 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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 12347f7..c6b2a03 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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 86d195d..dd9a2c0 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -133,7 +133,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2011-10-26</updated>
+ <updated>2011-10-27</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.xml b/public_html/bg-BG/opds.xml
index a7f6bb8..1fccd53 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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 Draft Documentation</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Draft_Documentation/opds-Fedora_…</id>
- <updated>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/bn-IN/opds-Community_Services_Infrastructure.xml b/public_html/bn-IN/opds-Community_Services_Infrastructure.xml
index ec51d52..ffe6832 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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 69b2ded..d7b7ab8 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
index 7a58963..5ff3078 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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 3b00fb0..fe0be3c 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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 92afba9..621583e 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -133,7 +133,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2011-10-26</updated>
+ <updated>2011-10-27</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.xml b/public_html/bn-IN/opds.xml
index ea3b05b..fdc200e 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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 Draft Documentation</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Draft_Documentation/opds-Fedora_…</id>
- <updated>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/bs-BA/opds-Community_Services_Infrastructure.xml b/public_html/bs-BA/opds-Community_Services_Infrastructure.xml
index a2dbba4..0e23c97 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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 f3a76d8..a810fae 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml b/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
index a22e751..e1511f3 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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 f791a74..ee87dee 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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 018b3cf..aa19ae5 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -133,7 +133,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2011-10-26</updated>
+ <updated>2011-10-27</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.xml b/public_html/bs-BA/opds.xml
index e3be686..f2e3ee2 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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 Draft Documentation</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Draft_Documentation/opds-Fedora_…</id>
- <updated>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/ca-ES/opds-Community_Services_Infrastructure.xml b/public_html/ca-ES/opds-Community_Services_Infrastructure.xml
index ad85383..f9dc45a 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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 8f919e0..9c235b3 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml b/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
index 0be541e..6c97c2d 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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 75d3c5a..3181d38 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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 9b27ea6..3636d19 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -133,7 +133,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2011-10-26</updated>
+ <updated>2011-10-27</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.xml b/public_html/ca-ES/opds.xml
index e232325..2002488 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</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 Draft Documentation</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Draft_Documentation/opds-Fedora_…</id>
- <updated>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:25</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/cs-CZ/opds-Community_Services_Infrastructure.xml b/public_html/cs-CZ/opds-Community_Services_Infrastructure.xml
index e86e56c..880bb89 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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:26</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 1ace0f6..d107a7a 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>2011-10-26T05:58:27</updated>
+ <updated>2011-10-27T05:38:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml b/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
index 47b22ff..ac86922 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>2011-10-26T05:58:27</updated>
+ <updated>2011-10-27T05:38:26</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 b594428..6581829 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>2011-10-26T05:58:27</updated>
+ <updated>2011-10-27T05:38:26</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 46321e9..911968c 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>2011-10-26T05:58:27</updated>
+ <updated>2011-10-27T05:38:26</updated>
<!--author>
<name></name>
<uri></uri>
@@ -133,7 +133,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2011-10-26</updated>
+ <updated>2011-10-27</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.xml b/public_html/cs-CZ/opds.xml
index 82fe751..52132be 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>2011-10-26T05:58:27</updated>
+ <updated>2011-10-27T05:38:26</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>2011-10-26T05:58:26</updated>
+ <updated>2011-10-27T05:38:26</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>2011-10-26T05:58:27</updated>
+ <updated>2011-10-27T05:38:26</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>2011-10-26T05:58:27</updated>
+ <updated>2011-10-27T05:38:26</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>2011-10-26T05:58:27</updated>
+ <updated>2011-10-27T05:38:26</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 Draft Documentation</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Draft_Documentation/opds-Fedora_…</id>
- <updated>2011-10-26T05:58:27</updated>
+ <updated>2011-10-27T05:38:26</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/da-DK/opds-Community_Services_Infrastructure.xml b/public_html/da-DK/opds-Community_Services_Infrastructure.xml
index 2be1605..297d556 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>2011-10-26T05:58:27</updated>
+ <updated>2011-10-27T05:38:26</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 afbd576..fd6f79e 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>2011-10-26T05:58:27</updated>
+ <updated>2011-10-27T05:38:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml b/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
index 6089b74..a9874fb 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>2011-10-26T05:58:27</updated>
+ <updated>2011-10-27T05:38:26</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 2a01c11..769544c 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>2011-10-26T05:58:27</updated>
+ <updated>2011-10-27T05:38:26</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 7074f28..df836c6 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>2011-10-26T05:58:27</updated>
+ <updated>2011-10-27T05:38:26</updated>
<!--author>
<name></name>
<uri></uri>
@@ -133,7 +133,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2011-10-26</updated>
+ <updated>2011-10-27</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.xml b/public_html/da-DK/opds.xml
index 8e67649..585a220 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>2011-10-26T05:58:27</updated>
+ <updated>2011-10-27T05:38:26</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>2011-10-26T05:58:27</updated>
+ <updated>2011-10-27T05:38:26</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>2011-10-26T05:58:27</updated>
+ <updated>2011-10-27T05:38:26</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>2011-10-26T05:58:27</updated>
+ <updated>2011-10-27T05:38:26</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>2011-10-26T05:58:27</updated>
+ <updated>2011-10-27T05:38:26</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 Draft Documentation</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Draft_Documentation/opds-Fedora_…</id>
- <updated>2011-10-26T05:58:27</updated>
+ <updated>2011-10-27T05:38:26</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/de-DE/opds-Community_Services_Infrastructure.xml b/public_html/de-DE/opds-Community_Services_Infrastructure.xml
index aa5cb36..cc38055 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>2011-10-26T05:58:27</updated>
+ <updated>2011-10-27T05:38:26</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 c7c8748..c8b20cb 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>2011-10-26T05:58:28</updated>
+ <updated>2011-10-27T05:38:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml b/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
index a1c74e1..5cf26bd 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>2011-10-26T05:58:28</updated>
+ <updated>2011-10-27T05:38:27</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 49c8a41..07fb99d 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>2011-10-26T05:58:28</updated>
+ <updated>2011-10-27T05:38:27</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 72c135c..97a9b96 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>2011-10-26T05:58:28</updated>
+ <updated>2011-10-27T05:38:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -133,7 +133,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2011-10-26</updated>
+ <updated>2011-10-27</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.xml b/public_html/de-DE/opds.xml
index 16f5314..eef4594 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>2011-10-26T05:58:28</updated>
+ <updated>2011-10-27T05:38:27</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>2011-10-26T05:58:27</updated>
+ <updated>2011-10-27T05:38:26</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>2011-10-26T05:58:28</updated>
+ <updated>2011-10-27T05:38:27</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>2011-10-26T05:58:28</updated>
+ <updated>2011-10-27T05:38:27</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>2011-10-26T05:58:28</updated>
+ <updated>2011-10-27T05:38:27</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 Draft Documentation</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Draft_Documentation/opds-Fedora_…</id>
- <updated>2011-10-26T05:58:28</updated>
+ <updated>2011-10-27T05:38:27</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/el-GR/opds-Community_Services_Infrastructure.xml b/public_html/el-GR/opds-Community_Services_Infrastructure.xml
index ce7b53f..1a87bf4 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>2011-10-26T05:58:28</updated>
+ <updated>2011-10-27T05:38:27</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 54a6f7a..4c5aca3 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>2011-10-26T05:58:28</updated>
+ <updated>2011-10-27T05:38:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml b/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
index 3326414..5503573 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>2011-10-26T05:58:28</updated>
+ <updated>2011-10-27T05:38:27</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 bf2722e..dca7e1d 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>2011-10-26T05:58:28</updated>
+ <updated>2011-10-27T05:38:27</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 cc08dea..3531b7b 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>2011-10-26T05:58:28</updated>
+ <updated>2011-10-27T05:38:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -133,7 +133,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2011-10-26</updated>
+ <updated>2011-10-27</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.xml b/public_html/el-GR/opds.xml
index 785a719..87f4ce8 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>2011-10-26T05:58:28</updated>
+ <updated>2011-10-27T05:38:27</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>2011-10-26T05:58:28</updated>
+ <updated>2011-10-27T05:38:27</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>2011-10-26T05:58:28</updated>
+ <updated>2011-10-27T05:38:27</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>2011-10-26T05:58:28</updated>
+ <updated>2011-10-27T05:38:27</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>2011-10-26T05:58:28</updated>
+ <updated>2011-10-27T05:38:27</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 Draft Documentation</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Draft_Documentation/opds-Fedora_…</id>
- <updated>2011-10-26T05:58:28</updated>
+ <updated>2011-10-27T05:38:27</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/epub/Installation_Guide/Fedora_Draft_Documentation-0.1-Installation_Guide-en-US.epub b/public_html/en-US/Fedora_Draft_Documentation/0.1/epub/Installation_Guide/Fedora_Draft_Documentation-0.1-Installation_Guide-en-US.epub
index babd384..4ce4d55 100644
Binary files a/public_html/en-US/Fedora_Draft_Documentation/0.1/epub/Installation_Guide/Fedora_Draft_Documentation-0.1-Installation_Guide-en-US.epub and b/public_html/en-US/Fedora_Draft_Documentation/0.1/epub/Installation_Guide/Fedora_Draft_Documentation-0.1-Installation_Guide-en-US.epub differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Installation_Guide/index.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Installation_Guide/index.html
index 0bb97cc..305b5d8 100644
--- a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Installation_Guide/index.html
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Installation_Guide/index.html
@@ -7,10 +7,10 @@
addID('Fedora_Draft_Documentation.0.1.books');
addID('Fedora_Draft_Documentation.0.1.Installation_Guide');
- </script></head><body class="draft 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="id864750" 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 Draft Documentation</span> <span class="productnumber"></span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="id864750" 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 16 on x86, AMD64, and Intel 64 architectures</h2></div><p class="edition">Edition 16.0.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="draft 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="id530856" 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 Draft Documentation</span> <span class="productnumber"></span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="id530856" 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 16 on x86, AMD64, and Intel 64 architectures</h2></div><p class="edition">Edition 16.0.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="id690007" 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="id472385" class="legalnotice"><h1 class="legalnotice">Legal Notice</h1><div class="para">
Copyright <span class="trademark"></span>© 2011 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.
@@ -32,11 +32,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><dt><span class="preface"><a href="#Installation-Guide-Preface">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="#id820388">1. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="#id757067">1.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="#id923439">1.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="#id913772">1.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="section"><a href="#id599087">2. We Need Feedback!</a></span></dt><dt><span class="section"><a href="#id1374097">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 Fedora</a></span></dt><dt><span class="section"><a hre
f="#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><dt><span class="section"><a href="#sn-expert-post-install">1.5. Perform Post-installation Steps</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><d
l><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><dd><dl><dt><span class="section"><a href="#Making_Minimal_Boot_Media-UEFI">3.3.1. UEFI-based systems</a></span></dt></dl></dd></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="#id578290">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></d
t><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="#id911845">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></d
t><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="sectio
n"><a href="#s2-x86-starting-bootopts">7.1.3. Additional Boot Options</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-install-diff-source-x86">7.2. Installing from a Different Source </a></span></dt><dt><span class="section"><a href="#sn-booting-from-pxe-x86">7.3. Booting from the Network using PXE </a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Installation_Phase_2-x86">8. Configuring Language and Installation Source</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-guimode-textinterface-x86">8.1. The Text Mode Installation Program User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="#id789979">8.1.1. Using the Keyboard to Navigate</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-langselection-x86">8.2. Language Selection</a></span></dt><dt><span class="section"><a href="#s1-installationmethod-x86">8.3. Installation Method</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-begininst
all-cd-inst-x86">8.3.1. Installing from DVD</a></span></dt><dt><span class="section"><a href="#s1-begininstall-hd-x86">8.3.2. Installing from a Hard Drive</a></span></dt><dt><span class="section"><a href="#s1-begininstall-perform-nfs-x86">8.3.3. Performing a Network Installation</a></span></dt><dt><span class="section"><a href="#s1-begininstall-nfs-x86">8.3.4. Installing via NFS</a></span></dt><dt><span class="section"><a href="#s1-begininstall-url-x86">8.3.5. Installing via FTP or HTTP</a></span></dt></dl></dd><dt><span class="section"><a href="#id550527">8.4. Verifying Media</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-guimode-x86">9. Installing using anaconda</a></span></dt><dd><dl><dt><span class="section"><a href="#id1040236">9.1. The Text Mode Installation Program User Interface</a></span></dt><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="se
ction"><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="#sn-keyboard-x86">9.3. Keyboard Configuration</a></span></dt><dt><span class="section"><a href="#Storage_Devices-x86">9.4. Storage Devices</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Storage_Device_Selection_Screen-x86">9.4.1. The Storage Devices Selection Screen </a></span></dt></dl></dd><dt><span class="section"><a href="#sn-Netconfig-x86">9.5. Setting the Hostname</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-Netconfig-x86-edit">9.5.1. Edit Network Connections</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-timezone-x86">9.6. Time Zone Configuration</a></span></dt><dt><span class="section"><a href="#sn-account_configuration-x86">9.7. Set the Root Password</
a></span></dt><dt><span class="section"><a href="#Assign_Storage_Devices-x86">9.8. Assign Storage Devices </a></span></dt><dt><span class="section"><a href="#sn-initialize-hdd-x86">9.9. Initializing the Hard Disk</a></span></dt><dt><span class="section"><a href="#sn-upgrading-system-x86">9.10. Upgrading an Existing System </a></span></dt><dd><dl><dt><span class="section"><a href="#sn-upgrade-examine-x86">9.10.1. The Upgrade Dialog </a></span></dt><dt><span class="section"><a href="#sn-upgrade-tree-x86">9.10.2. Upgrading Using the Installer </a></span></dt><dt><span class="section"><a href="#sn-upgrading-bootloader-x86">9.10.3. Upgrading Boot Loader Configuration </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-diskpartsetup-x86">9.11. Disk Partitioning Setup</a></span></dt><dt><span class="section"><a href="#encrypt-x86">9.12. Encrypt Partitions </a></span></dt><dt><span class="section"><a href="#s1-diskpartitioning-x86">9.13. Creating a Custom Layout
or Modifying the Default Layout </a></span></dt><dd><dl><dt><span class="section"><a href="#Create_Storage-x86">9.13.1. Create Storage </a></span></dt><dt><span class="section"><a href="#Adding_Partitions-x86">9.13.2. Adding Partitions</a></span></dt><dt><span class="section"><a href="#Create_Software_RAID-x86">9.13.3. Create Software RAID </a></span></dt><dt><span class="section"><a href="#Create_LVM-x86">9.13.4. Create LVM Logical Volume </a></span></dt><dt><span class="section"><a href="#s2-diskpartrecommend-x86">9.13.5. Recommended Partitioning Scheme</a></span></dt></dl></dd><dt><span class="section"><a href="#Write_changes_to_disk-x86">9.14. Write changes to disk</a></span></dt><dt><span class="section"><a href="#s1-x86-bootloader">9.15. x86, AMD64, and Intel 64 Boot Loader Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#x86-bootloader-adv">9.15.1. Advanced Boot Loader Configuration</a></span></dt><dt><span class="section"><a href="#s2-x86-b
ootloader-rescue">9.15.2. Rescue Mode</a></span></dt><dt><span class="section"><a href="#s2-x86-bootloader-alt">9.15.3. Alternative Boot Loaders</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-pkgselection-x86">9.16. Package Group Selection</a></span></dt><dd><dl><dt><span class="section"><a href="#id1266148">9.16.1. Installing from Additional Repositories</a></span></dt><dt><span class="section"><a href="#sn-package-selection-x86">9.16.2. Customizing the Software Selection </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-installpkgs-x86">9.17. Installing Packages</a></span></dt><dt><span class="section"><a href="#s1-complete-x86">9.18. Installation Complete</a></span></dt></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="#id693508">10.1. You are unable to boot Fedora</a></span></dt><dd><dl><dt><span class="section"
><a href="#id844055">10.1.1. Are You Unable to Boot With Your RAID Card?</a></span></dt><dt><span class="section"><a href="#id663989">10.1.2. Is Your System Displaying Signal 11 Errors?</a></span></dt></dl></dd><dt><span class="section"><a href="#id666318">10.2. Trouble Beginning the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#id1432449">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. Saving 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="#id908960">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="#Trouble_After_Booting-GUI">10.4.2. Booting into a Graphical Environment</a></span></dt><dt><span class="section"><a href="#id540116">10.4.3. Problems with the X Window System (GUI)</a></span></dt><dt><span class="section"><a href="#id970287">10.4.4. Problems with the X Server Crashing and Non-Root Users</a></span></dt><dt><span class="section"><a href="#id656508">10.4.5. Problems When You Try to Log In</a></span></dt><dt><span class="section"><a href="#s2-trouble-ram">10.4.6. Is Your R
AM Not Being Recognized?</a></span></dt><dt><span class="section"><a href="#id1001590">10.4.7. Your Printer Does Not Work</a></span></dt><dt><span class="section"><a href="#id618256">10.4.8. 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><dd><dl><dt><span class="section"><a href="#sn-boot-options-language">11.1.1. Specifying the Language</a></span></dt><dt><span class="section"><a href="#sn-boot-options-interface">11.1.2. Configuring the Interface</a></span></dt><dt><span class="section"><a href="#sn-boot-options-update">11.1.3. Updating anaconda</a></span></dt><dt><s
pan class="section"><a href="#sn-boot-options-installmethod">11.1.4. Specifying the Installation Method</a></span></dt><dt><span class="section"><a href="#sn-boot-options-network">11.1.5. Specifying the Network Settings</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-remoteaccess-installation">11.2. Enabling Remote Access to the Installation System</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-remoteaccess-installation-vnc">11.2.1. Enabling Remote Access with VNC</a></span></dt><dt><span class="section"><a href="#sn-remoteaccess-installation-vnclistener">11.2.2. Connecting the Installation System to a VNC Listener</a></span></dt><dt><span class="section"><a href="#sn-ssh-installation">11.2.3. Enabling Remote Access with ssh</a></span></dt><dt><span class="section"><a href="#sn-telnet-installation">11.2.4. Enabling Remote Access with Telnet</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-remote-logging">11.3. Logging to a Remote
System During the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-remote-logging-logserver">11.3.1. Configuring a Log Server</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-automating-installation">11.4. Automating the Installation with Kickstart</a></span></dt><dt><span class="section"><a href="#sn-bootoptions-hardware">11.5. Enhancing Hardware Support</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-bootoptions-hwdetection">11.5.1. Overriding Automatic Hardware Detection</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-boot-modes">11.6. Using the Maintenance Boot Modes</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-memtest">11.6.1. Loading the Memory (RAM) Testing Mode</a></span></dt><dt><span class="section"><a href="#sn-boot-mediacheck">11.6.2. Verifying boot media</a></span></dt><dt><span class="section"><a href="#sn-mode-rescue">11.6.3. Booting Your Computer with the Rescue Mode</a><
/span></dt><dt><span class="section"><a href="#sn-mode-upgradeany">11.6.4. Upgrading your computer</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="#s1-netboot-add-hosts">13.5.3. Adding PXE Hosts</a></span></dt><dt><span class="section"><a href="#s1-netboot-tftp">13.5.4. TFTPD</a></span></dt><dt><span class="section"><a href="#id636107">13.5.5. Configuring the DHCP Server</a></span></dt><dt><span class="section"><a href="#s2-netboot-custom-msg">13.5.6. Adding a Custom Boot Message</a></span></dt><dt><span class="section"><a href="#netboot-performing">13.5.7
. 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="se
ction"><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 Se
lection</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. Netwo
rk 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-firstboot">17. Firstboot</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-firstboot-license">17.1. License Agreement</a></span></dt><dt><span class="section"><a href="#sn-firstboot-systemuser">17.2. Create User</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-firstboot-authentication">17.2.1. Authentication Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-firstboot-datetime">17.3. Date and Time</a></span></dt><dt><span class="section"><a href="#sn-smolt">17.4. Hardware Profile</a></span></dt></dl></dd><dt><span class="chapter">
<a href="#ch-next-steps">18. Your Next Steps</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-system-updating">18.1. Updating Your System</a></span></dt><dt><span class="section"><a href="#sn-finishing-upgrade">18.2. Finishing an Upgrade</a></span></dt><dt><span class="section"><a href="#sn-switching-to-gui-login">18.3. Switching to a Graphical Login</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-enabling-repos">18.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">18.4. Subscribing to Fedora Announcements and News</a></span></dt><dt><span class="section"><a href="#sn-web-help">18.5. Finding Documentation and Support</a></span></dt><dt><span class="section"><a href="#sn-community">18.6. Joining the Fedora Community</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ap-rescuemode">19. Basic System Recovery</a></span></dt><dd><dl><dt><span
class="section"><a href="#Rescue_Mode-x86">19.1. Rescue Mode</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-rescuemode-common-problems">19.1.1. Common Problems</a></span></dt><dt><span class="section"><a href="#s1-rescuemode-boot">19.1.2. Booting into Rescue Mode</a></span></dt><dt><span class="section"><a href="#s1-rescuemode-booting-single">19.1.3. Booting into Single-User Mode</a></span></dt><dt><span class="section"><a href="#s1-rescuemode-booting-emergency">19.1.4. Booting into Emergency Mode</a></span></dt></dl></dd><dt><span class="section"><a href="#rescuemode_drivers">19.2. Using rescue mode to fix or work around driver problems</a></span></dt><dd><dl><dt><span class="section"><a href="#rescuemode_drivers-rpm">19.2.1. Using RPM to add, remove, or replace a driver</a></span></dt><dt><span class="section"><a href="#rescuemode_drivers-blacklisting">19.2.2. Blacklisting a driver</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-upg
rade-x86">20. Upgrading Your Current System</a></span></dt><dd><dl><dt><span class="section"><a href="#id758868">20.1. Determining Whether to Upgrade or Re-Install</a></span></dt><dt><span class="section"><a href="#id1382392">20.2. Upgrading Your System</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-x86-uninstall">21. Removing Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-x86-uninstall-single">21.1. Fedora is the only operating system on the computer</a></span></dt><dt><span class="section"><a href="#sn-x86-uninstall-dual">21.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">21.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">21.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">21.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">21.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. Pa
rtitions 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="#id1380380">C.1. What is block device encryption? </a></span></dt><dt><span class="section"><a href="#id914008">C.2. Encrypting block devices using dm-crypt/LUKS </a></span></dt><dd><dl><dt><span class="section"><a href="#id621867">C.2.1. Overview of LUKS </a></span></dt><dt><span class="section"><a href="#id1380455">C.2.2. How will I access the encrypted devices after installation? (System Startup) </a></span></dt><dt><span class="section"><a href="#id912117">C.2.3. Choosing a Good Passphrase </a></span></dt></dl></dd><dt><span class="section"><a href="#id840120">C.3. Creating Encrypted Block Devices in Anaconda </a></span></dt><dd><dl><dt><span class="section"><a href="#id657114">C.3.1. What Kinds of Block Devices Can Be Encrypted? </a></span></dt><dt><span class="section"><a h
ref="#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="#id713599">C.4. Creating Encrypted Block Devices on the Installed System After Installation </a></span></dt><dd><dl><dt><span class="section"><a href="#id654443">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="#id722647">C.4.3. Format the device as a dm-crypt/LUKS encrypted device </a></span></dt><dt><span class="section"><a href="#id624790">C.4.4. Create a mapping to allow access to the device's decrypted contents </a></span></dt><dt><span class="section"><a href="#id518906">C.4.5. Create filesystems on the mapped device, or continue t
o build complex storage structures using the mapped device </a></span></dt><dt><span class="section"><a href="#id663334">C.4.6. Add the mapping information to <code class="filename">/etc/crypttab</code></a></span></dt><dt><span class="section"><a href="#id818056">C.4.7. Add an entry to <code class="filename">/etc/fstab</code></a></span></dt></dl></dd><dt><span class="section"><a href="#id751166">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="#id955380">C.5.2. Add a new passphrase to an existing device </a></span></dt><dt><span class="section"><a href="#id670979">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="#ch-g
rub">E. The GRUB Boot Loader</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-grub-arch">E.1. Boot Loaders and System Architecture</a></span></dt><dt><span class="section"><a href="#s1-grub-whatis">E.2. GRUB</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-grub-whatis-booting-bios">E.2.1. GRUB and the boot process on BIOS-based x86 systems</a></span></dt><dt><span class="section"><a href="#s2-grub-whatis-booting-uefi">E.2.2. GRUB and the boot process on UEFI-based x86 systems</a></span></dt><dt><span class="section"><a href="#s2-grub-whatis-features">E.2.3. Features of GRUB</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-grub-installing">E.3. Installing GRUB</a></span></dt><dt><span class="section"><a href="#s1-grub-terminology">E.4. GRUB Terminology</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-grub-terminology-devices">E.4.1. Device Names</a></span></dt><dt><span class="section"><a href="#s2-grub-terminology-files">
E.4.2. File Names and Blocklists</a></span></dt><dt><span class="section"><a href="#s2-grub-terminology-rootfs">E.4.3. The Root File System and GRUB</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-grub-interfaces">E.5. GRUB Interfaces</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-grub-interfaces-orderofuse">E.5.1. Interfaces Load Order</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-grub-commands">E.6. GRUB Commands</a></span></dt><dt><span class="section"><a href="#s1-grub-configfile">E.7. GRUB Menu Configuration File</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-grub-configfile-structure">E.7.1. Configuration File Structure</a></span></dt><dt><span class="section"><a href="#s2-grub-configfile-commands">E.7.2. Configuration File Directives</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-grub-runlevels">E.8. Changing Runlevels at Boot Time</a></span></dt><dt><span class="section"><a href="#s1-gru
b-additional-resources">E.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-grub-installed-documentation">E.9.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-grub-useful-websites">E.9.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#ch-boot-init-shutdown">F. Boot Process, Init, and Shutdown</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-boot-process-basics">F.1. The Boot Process</a></span></dt><dt><span class="section"><a href="#s1-boot-init-shutdown-process">F.2. A Detailed Look at the Boot Process</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-firmware_interface">F.2.1. The firmware interface</a></span></dt><dt><span class="section"><a href="#s2-boot-init-shutdown-loader">F.2.2. The Boot Loader</a></span></dt><dt><span class="section"><a href="#s2-boot-init-shutdown-kernel">F.2.3. The Kernel</a></span></dt><dt><span class="section">
<a href="#s2-boot-init-shutdown-init">F.2.4. The <code class="command">/sbin/init</code> Program</a></span></dt><dt><span class="section"><a href="#s2-boot-init-shutdown-jobs">F.2.5. Job definitions</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-boot-init-shutdown-run-boot">F.3. Running Additional Programs at Boot Time</a></span></dt><dt><span class="section"><a href="#s1-boot-init-shutdown-sysv">F.4. SysV Init Runlevels</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-init-boot-shutdown-rl">F.4.1. Runlevels</a></span></dt><dt><span class="section"><a href="#s2-boot-init-shutdown-sysv-util">F.4.2. Runlevel Utilities</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-boot-init-shutdown-shutdown">F.5. Shutting Down</a></span></dt></dl></dd><dt><span class="appendix"><a href="#ap-techref">G. Other Technical Documentation</a></span></dt></dl></dd><dt><span class="appendix"><a href="#ch-Contributors_and_production_methods">H. Contributor
s and production methods</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-Contributors">H.1. Contributors</a></span></dt><dt><span class="section"><a href="#sn-Production_methods">H.2. Production methods</a></span></dt></dl></dd><dt><span class="appendix"><a href="#appe-Publican-Revision_History">I. Revision History</a></span></dt><dt><span class="index"><a href="#id671497">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" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id820388">1. Document Conventions</h2></div></div></div><div class="para">
+ </div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="#Installation-Guide-Preface">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="#id630623">1. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="#id665911">1.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="#id1002109">1.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="#id883260">1.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="section"><a href="#id777665">2. We Need Feedback!</a></span></dt><dt><span class="section"><a href="#id921379">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 Fedora</a></span></dt><dt><span class="section"><a hre
f="#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><dt><span class="section"><a href="#sn-expert-post-install">1.5. Perform Post-installation Steps</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><d
l><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><dd><dl><dt><span class="section"><a href="#Making_Minimal_Boot_Media-UEFI">3.3.1. UEFI-based systems</a></span></dt></dl></dd></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="#id743701">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></d
t><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="#id519672">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></d
t><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="sectio
n"><a href="#s2-x86-starting-bootopts">7.1.3. Additional Boot Options</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-install-diff-source-x86">7.2. Installing from a Different Source </a></span></dt><dt><span class="section"><a href="#sn-booting-from-pxe-x86">7.3. Booting from the Network using PXE </a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Installation_Phase_2-x86">8. Configuring Language and Installation Source</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-guimode-textinterface-x86">8.1. The Text Mode Installation Program User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="#id1039021">8.1.1. Using the Keyboard to Navigate</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-langselection-x86">8.2. Language Selection</a></span></dt><dt><span class="section"><a href="#s1-installationmethod-x86">8.3. Installation Method</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-beginins
tall-cd-inst-x86">8.3.1. Installing from DVD</a></span></dt><dt><span class="section"><a href="#s1-begininstall-hd-x86">8.3.2. Installing from a Hard Drive</a></span></dt><dt><span class="section"><a href="#s1-begininstall-perform-nfs-x86">8.3.3. Performing a Network Installation</a></span></dt><dt><span class="section"><a href="#s1-begininstall-nfs-x86">8.3.4. Installing via NFS</a></span></dt><dt><span class="section"><a href="#s1-begininstall-url-x86">8.3.5. Installing via FTP or HTTP</a></span></dt></dl></dd><dt><span class="section"><a href="#id870317">8.4. Verifying Media</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-guimode-x86">9. Installing using anaconda</a></span></dt><dd><dl><dt><span class="section"><a href="#id711680">9.1. The Text Mode Installation Program User Interface</a></span></dt><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="se
ction"><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="#sn-keyboard-x86">9.3. Keyboard Configuration</a></span></dt><dt><span class="section"><a href="#Storage_Devices-x86">9.4. Storage Devices</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Storage_Device_Selection_Screen-x86">9.4.1. The Storage Devices Selection Screen </a></span></dt></dl></dd><dt><span class="section"><a href="#sn-Netconfig-x86">9.5. Setting the Hostname</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-Netconfig-x86-edit">9.5.1. Edit Network Connections</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-timezone-x86">9.6. Time Zone Configuration</a></span></dt><dt><span class="section"><a href="#sn-account_configuration-x86">9.7. Set the Root Password</
a></span></dt><dt><span class="section"><a href="#Assign_Storage_Devices-x86">9.8. Assign Storage Devices </a></span></dt><dt><span class="section"><a href="#sn-initialize-hdd-x86">9.9. Initializing the Hard Disk</a></span></dt><dt><span class="section"><a href="#sn-upgrading-system-x86">9.10. Upgrading an Existing System </a></span></dt><dd><dl><dt><span class="section"><a href="#sn-upgrade-examine-x86">9.10.1. The Upgrade Dialog </a></span></dt><dt><span class="section"><a href="#sn-upgrade-tree-x86">9.10.2. Upgrading Using the Installer </a></span></dt><dt><span class="section"><a href="#sn-upgrading-bootloader-x86">9.10.3. Upgrading Boot Loader Configuration </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-diskpartsetup-x86">9.11. Disk Partitioning Setup</a></span></dt><dt><span class="section"><a href="#encrypt-x86">9.12. Encrypt Partitions </a></span></dt><dt><span class="section"><a href="#s1-diskpartitioning-x86">9.13. Creating a Custom Layout
or Modifying the Default Layout </a></span></dt><dd><dl><dt><span class="section"><a href="#Create_Storage-x86">9.13.1. Create Storage </a></span></dt><dt><span class="section"><a href="#Adding_Partitions-x86">9.13.2. Adding Partitions</a></span></dt><dt><span class="section"><a href="#Create_Software_RAID-x86">9.13.3. Create Software RAID </a></span></dt><dt><span class="section"><a href="#Create_LVM-x86">9.13.4. Create LVM Logical Volume </a></span></dt><dt><span class="section"><a href="#s2-diskpartrecommend-x86">9.13.5. Recommended Partitioning Scheme</a></span></dt></dl></dd><dt><span class="section"><a href="#Write_changes_to_disk-x86">9.14. Write changes to disk</a></span></dt><dt><span class="section"><a href="#s1-x86-bootloader">9.15. x86, AMD64, and Intel 64 Boot Loader Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#x86-bootloader-adv">9.15.1. Advanced Boot Loader Configuration</a></span></dt><dt><span class="section"><a href="#s2-x86-b
ootloader-rescue">9.15.2. Rescue Mode</a></span></dt><dt><span class="section"><a href="#s2-x86-bootloader-alt">9.15.3. Alternative Boot Loaders</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-pkgselection-x86">9.16. Package Group Selection</a></span></dt><dd><dl><dt><span class="section"><a href="#id513788">9.16.1. Installing from Additional Repositories</a></span></dt><dt><span class="section"><a href="#sn-package-selection-x86">9.16.2. Customizing the Software Selection </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-installpkgs-x86">9.17. Installing Packages</a></span></dt><dt><span class="section"><a href="#s1-complete-x86">9.18. Installation Complete</a></span></dt></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="#id705731">10.1. You are unable to boot Fedora</a></span></dt><dd><dl><dt><span class="section">
<a href="#id809826">10.1.1. Are You Unable to Boot With Your RAID Card?</a></span></dt><dt><span class="section"><a href="#id595519">10.1.2. Is Your System Displaying Signal 11 Errors?</a></span></dt></dl></dd><dt><span class="section"><a href="#id709919">10.2. Trouble Beginning the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#id560395">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. Saving 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 c
lass="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="#id889363">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="#Trouble_After_Booting-GUI">10.4.2. Booting into a Graphical Environment</a></span></dt><dt><span class="section"><a href="#id746602">10.4.3. Problems with the X Window System (GUI)</a></span></dt><dt><span class="section"><a href="#id532309">10.4.4. Problems with the X Server Crashing and Non-Root Users</a></span></dt><dt><span class="section"><a href="#id646088">10.4.5. Problems When You Try to Log In</a></span></dt><dt><span class="section"><a href="#s2-trouble-ram">10.4.6. Is Your RAM
Not Being Recognized?</a></span></dt><dt><span class="section"><a href="#id615608">10.4.7. Your Printer Does Not Work</a></span></dt><dt><span class="section"><a href="#id762738">10.4.8. 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><dd><dl><dt><span class="section"><a href="#sn-boot-options-language">11.1.1. Specifying the Language</a></span></dt><dt><span class="section"><a href="#sn-boot-options-interface">11.1.2. Configuring the Interface</a></span></dt><dt><span class="section"><a href="#sn-boot-options-update">11.1.3. Updating anaconda</a></span></dt><dt><span
class="section"><a href="#sn-boot-options-installmethod">11.1.4. Specifying the Installation Method</a></span></dt><dt><span class="section"><a href="#sn-boot-options-network">11.1.5. Specifying the Network Settings</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-remoteaccess-installation">11.2. Enabling Remote Access to the Installation System</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-remoteaccess-installation-vnc">11.2.1. Enabling Remote Access with VNC</a></span></dt><dt><span class="section"><a href="#sn-remoteaccess-installation-vnclistener">11.2.2. Connecting the Installation System to a VNC Listener</a></span></dt><dt><span class="section"><a href="#sn-ssh-installation">11.2.3. Enabling Remote Access with ssh</a></span></dt><dt><span class="section"><a href="#sn-telnet-installation">11.2.4. Enabling Remote Access with Telnet</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-remote-logging">11.3. Logging to a Remote Sy
stem During the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-remote-logging-logserver">11.3.1. Configuring a Log Server</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-automating-installation">11.4. Automating the Installation with Kickstart</a></span></dt><dt><span class="section"><a href="#sn-bootoptions-hardware">11.5. Enhancing Hardware Support</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-bootoptions-hwdetection">11.5.1. Overriding Automatic Hardware Detection</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-boot-modes">11.6. Using the Maintenance Boot Modes</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-memtest">11.6.1. Loading the Memory (RAM) Testing Mode</a></span></dt><dt><span class="section"><a href="#sn-boot-mediacheck">11.6.2. Verifying boot media</a></span></dt><dt><span class="section"><a href="#sn-mode-rescue">11.6.3. Booting Your Computer with the Rescue Mode</a></sp
an></dt><dt><span class="section"><a href="#sn-mode-upgradeany">11.6.4. Upgrading your computer</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><sp
an 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="#s1-netboot-add-hosts">13.5.3. Adding PXE Hosts</a></span></dt><dt><span class="section"><a href="#s1-netboot-tftp">13.5.4. TFTPD</a></span></dt><dt><span class="section"><a href="#id736470">13.5.5. Configuring the DHCP Server</a></span></dt><dt><span class="section"><a href="#s2-netboot-custom-msg">13.5.6. Adding a Custom Boot Message</a></span></dt><dt><span class="section"><a href="#netboot-performing">13.5.7. P
erforming 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="secti
on"><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 Selec
tion</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-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-firstboot">17. Firstboot</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-firstboot-license">17.1. License Agreement</a></span></dt><dt><span class="section"><a href="#sn-firstboot-systemuser">17.2. Create User</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-firstboot-authentication">17.2.1. Authentication Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-firstboot-datetime">17.3. Date and Time</a></span></dt><dt><span class="section"><a href="#sn-smolt">17.4. Hardware Profile</a></span></dt></dl></dd><dt><span class="chapter"><a
href="#ch-next-steps">18. Your Next Steps</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-system-updating">18.1. Updating Your System</a></span></dt><dt><span class="section"><a href="#sn-finishing-upgrade">18.2. Finishing an Upgrade</a></span></dt><dt><span class="section"><a href="#sn-switching-to-gui-login">18.3. Switching to a Graphical Login</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-enabling-repos">18.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">18.4. Subscribing to Fedora Announcements and News</a></span></dt><dt><span class="section"><a href="#sn-web-help">18.5. Finding Documentation and Support</a></span></dt><dt><span class="section"><a href="#sn-community">18.6. Joining the Fedora Community</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ap-rescuemode">19. Basic System Recovery</a></span></dt><dd><dl><dt><span cla
ss="section"><a href="#Rescue_Mode-x86">19.1. Rescue Mode</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-rescuemode-common-problems">19.1.1. Common Problems</a></span></dt><dt><span class="section"><a href="#s1-rescuemode-boot">19.1.2. Booting into Rescue Mode</a></span></dt><dt><span class="section"><a href="#s1-rescuemode-booting-single">19.1.3. Booting into Single-User Mode</a></span></dt><dt><span class="section"><a href="#s1-rescuemode-booting-emergency">19.1.4. Booting into Emergency Mode</a></span></dt></dl></dd><dt><span class="section"><a href="#rescuemode_drivers">19.2. Using rescue mode to fix or work around driver problems</a></span></dt><dd><dl><dt><span class="section"><a href="#rescuemode_drivers-rpm">19.2.1. Using RPM to add, remove, or replace a driver</a></span></dt><dt><span class="section"><a href="#rescuemode_drivers-blacklisting">19.2.2. Blacklisting a driver</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-upgrad
e-x86">20. Upgrading Your Current System</a></span></dt><dd><dl><dt><span class="section"><a href="#id487971">20.1. Determining Whether to Upgrade or Re-Install</a></span></dt><dt><span class="section"><a href="#id518799">20.2. Upgrading Your System</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-x86-uninstall">21. Removing Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-x86-uninstall-single">21.1. Fedora is the only operating system on the computer</a></span></dt><dt><span class="section"><a href="#sn-x86-uninstall-dual">21.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">21.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">21.2.2. Your computer dual-boots Fedora and Mac OS X</a></span></dt><dt><span class="section"><a href="#sn-x
86-uninstall-dual-linux">21.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">21.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. Partit
ions 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="#id675605">C.1. What is block device encryption? </a></span></dt><dt><span class="section"><a href="#id577927">C.2. Encrypting block devices using dm-crypt/LUKS </a></span></dt><dd><dl><dt><span class="section"><a href="#id729434">C.2.1. Overview of LUKS </a></span></dt><dt><span class="section"><a href="#id604599">C.2.2. How will I access the encrypted devices after installation? (System Startup) </a></span></dt><dt><span class="section"><a href="#id790119">C.2.3. Choosing a Good Passphrase </a></span></dt></dl></dd><dt><span class="section"><a href="#id858295">C.3. Creating Encrypted Block Devices in Anaconda </a></span></dt><dd><dl><dt><span class="section"><a href="#id483190">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="#id575929">C.4. Creating Encrypted Block Devices on the Installed System After Installation </a></span></dt><dd><dl><dt><span class="section"><a href="#id642391">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="#id713433">C.4.3. Format the device as a dm-crypt/LUKS encrypted device </a></span></dt><dt><span class="section"><a href="#id624005">C.4.4. Create a mapping to allow access to the device's decrypted contents </a></span></dt><dt><span class="section"><a href="#id615432">C.4.5. Create filesystems on the mapped device, or continue to buil
d complex storage structures using the mapped device </a></span></dt><dt><span class="section"><a href="#id710988">C.4.6. Add the mapping information to <code class="filename">/etc/crypttab</code></a></span></dt><dt><span class="section"><a href="#id529126">C.4.7. Add an entry to <code class="filename">/etc/fstab</code></a></span></dt></dl></dd><dt><span class="section"><a href="#id590845">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="#id674776">C.5.2. Add a new passphrase to an existing device </a></span></dt><dt><span class="section"><a href="#id645286">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="#ch-grub">E
. The GRUB Boot Loader</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-grub-arch">E.1. Boot Loaders and System Architecture</a></span></dt><dt><span class="section"><a href="#s1-grub-whatis">E.2. GRUB</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-grub-whatis-booting-bios">E.2.1. GRUB and the boot process on BIOS-based x86 systems</a></span></dt><dt><span class="section"><a href="#s2-grub-whatis-booting-uefi">E.2.2. GRUB and the boot process on UEFI-based x86 systems</a></span></dt><dt><span class="section"><a href="#s2-grub-whatis-features">E.2.3. Features of GRUB</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-grub-installing">E.3. Installing GRUB</a></span></dt><dt><span class="section"><a href="#s1-grub-terminology">E.4. GRUB Terminology</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-grub-terminology-devices">E.4.1. Device Names</a></span></dt><dt><span class="section"><a href="#s2-grub-terminology-files">E.4.2.
File Names and Blocklists</a></span></dt><dt><span class="section"><a href="#s2-grub-terminology-rootfs">E.4.3. The Root File System and GRUB</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-grub-interfaces">E.5. GRUB Interfaces</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-grub-interfaces-orderofuse">E.5.1. Interfaces Load Order</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-grub-commands">E.6. GRUB Commands</a></span></dt><dt><span class="section"><a href="#s1-grub-configfile">E.7. GRUB Menu Configuration File</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-grub-configfile-structure">E.7.1. Configuration File Structure</a></span></dt><dt><span class="section"><a href="#s2-grub-configfile-commands">E.7.2. Configuration File Directives</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-grub-runlevels">E.8. Changing Runlevels at Boot Time</a></span></dt><dt><span class="section"><a href="#s1-grub-addi
tional-resources">E.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-grub-installed-documentation">E.9.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-grub-useful-websites">E.9.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#ch-boot-init-shutdown">F. Boot Process, Init, and Shutdown</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-boot-process-basics">F.1. The Boot Process</a></span></dt><dt><span class="section"><a href="#s1-boot-init-shutdown-process">F.2. A Detailed Look at the Boot Process</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-firmware_interface">F.2.1. The firmware interface</a></span></dt><dt><span class="section"><a href="#s2-boot-init-shutdown-loader">F.2.2. The Boot Loader</a></span></dt><dt><span class="section"><a href="#s2-boot-init-shutdown-kernel">F.2.3. The Kernel</a></span></dt><dt><span class="section"><a hre
f="#s2-boot-init-shutdown-init">F.2.4. The <code class="command">/sbin/init</code> Program</a></span></dt><dt><span class="section"><a href="#s2-boot-init-shutdown-jobs">F.2.5. Job definitions</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-boot-init-shutdown-run-boot">F.3. Running Additional Programs at Boot Time</a></span></dt><dt><span class="section"><a href="#s1-boot-init-shutdown-sysv">F.4. SysV Init Runlevels</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-init-boot-shutdown-rl">F.4.1. Runlevels</a></span></dt><dt><span class="section"><a href="#s2-boot-init-shutdown-sysv-util">F.4.2. Runlevel Utilities</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-boot-init-shutdown-shutdown">F.5. Shutting Down</a></span></dt></dl></dd><dt><span class="appendix"><a href="#ap-techref">G. Other Technical Documentation</a></span></dt></dl></dd><dt><span class="appendix"><a href="#ch-Contributors_and_production_methods">H. Contributors and
production methods</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-Contributors">H.1. Contributors</a></span></dt><dt><span class="section"><a href="#sn-Production_methods">H.2. Production methods</a></span></dt></dl></dd><dt><span class="appendix"><a href="#appe-Publican-Revision_History">I. Revision History</a></span></dt><dt><span class="index"><a href="#id525244">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" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id630623">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"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id757067">1.1. Typographic Conventions</h3></div></div></div><div class="para">
+ </div><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id665911">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>
@@ -84,7 +84,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"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id923439">1.2. Pull-quote Conventions</h3></div></div></div><div class="para">
+ </div></blockquote></div></div><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id1002109">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:
@@ -109,7 +109,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"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id913772">1.3. Notes and Warnings</h3></div></div></div><div class="para">
+}</pre></div><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id883260">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.
@@ -117,13 +117,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" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id599087">2. We Need Feedback!</h2></div></div></div><a id="id852643" class="indexterm"></a><div class="para">
+ </div></div></div></div></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id777665">2. We Need Feedback!</h2></div></div></div><a id="id684425" 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 Documentation.</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"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id1374097">3. Acknowledgments</h2></div></div></div><div class="para">
+ </div></div><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id921379">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="http://docs.redhat.com/docs">http://docs.redhat.com/docs</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.
@@ -165,7 +165,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="id820768" class="indexterm"></a><div class="para">
+ </div></div></div><div class="orderedlist"><ol><li class="listitem"><a id="id503508" 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.
@@ -177,7 +177,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" id="sn-expert-prepare">1.3. Prepare for Installation</h2></div></div></div><a id="id696280" 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" id="sn-expert-prepare">1.3. Prepare for Installation</h2></div></div></div><a id="id997881" 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.13, “ Creating a Custom Layout or Modifying the Default Layout ”</a> for more information.
@@ -189,7 +189,7 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
After the system reboots, it displays additional configuration options. Make appropriate changes to your system and proceed to the login prompt.
</div><div class="para">
Refer to <a class="xref" href="#ch-firstboot">Chapter 17, <em>Firstboot</em></a> or the Firstboot page on the Fedora wiki: <a href="http://fedoraproject.org/wiki/FirstBoot">http://fedoraproject.org/wiki/FirstBoot</a> for more detail.
- </div></div></div><div xml:lang="en-US" class="chapter" id="ch-new-users" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 2. Obtaining Fedora</h2></div></div></div><div class="toc"><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></div><a id="id696931" class="indexterm"></a><a id="id550872" class="indexterm"></a><a id="id722940" 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><h2 class="title">Chapter 2. Obtaining Fedora</h2></div></div></div><div class="toc"><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></div><a id="id498107" class="indexterm"></a><a id="id472836" class="indexterm"></a><a id="id997433" 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:
@@ -213,11 +213,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" id="sn-which-download-mirror">2.1.1.1. From a Mirror</h4></div></div></div><a id="id647652" 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" id="sn-which-download-mirror">2.1.1.1. From a Mirror</h4></div></div></div><a id="id613174" 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 16 distribution normally appears in the directory <code class="filename">fedora/linux/releases/16/</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 16 for x86_64 at <code class="filename">fedora/linux/releases/16/Fedora/x86_64/iso/Fedora-16-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" id="sn-which-download-bt">2.1.1.2. From BitTorrent</h4></div></div></div><a id="id553957" class="indexterm"></a><a id="id650272" 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" id="sn-which-download-bt">2.1.1.2. From BitTorrent</h4></div></div></div><a id="id868707" class="indexterm"></a><a id="id868715" 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.
@@ -225,9 +225,9 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
You do not need to find a special mirror for BitTorrent files. The BitTorrent protocol ensures that your computer participates in a nearby group. To download and use the Fedora BitTorrent files, visit <a href="http://torrent.fedoraproject.org/">http://torrent.fedoraproject.org/</a>.
</div><div class="note"><div class="admonition_header"><h2>Minimal Boot Images</h2></div><div class="admonition"><div class="para">
Minimal boot CD and USB flash disk images are not available through BitTorrent.
- </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" id="sn-which-arch">2.1.2. Which Architecture Is My Computer?</h3></div></div></div><a id="id691167" 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" id="sn-which-arch">2.1.2. Which Architecture Is My Computer?</h3></div></div></div><a id="id664208" 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="id1081763" 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 align="left">
+ </div><a id="id675787" 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 align="left">
Processor manufacturer and model
</th><th align="left">
Architecture type for Fedora
@@ -249,11 +249,11 @@ 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 16 for x86_64 is named <code class="filename">Fedora-16-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="id762134">Full Distribution on DVD</h5>
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="id664099">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="id840421">Live Image</h5>
+ </div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="id929874">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. The Live image also provides an <code class="literal">Install to Hard Disk</code> desktop shortcut (alternatively, the shortcut can be found in <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span>). If you decide you like what you see, and want to install it, simply activate the selection to copy Fedora to your hard disk. You can download the Live image directly from a mirror, or using BitTorrent.
- </div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="id662563">Minimal Boot Media</h5>
+ </div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="id732826">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.
@@ -277,7 +277,7 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
<code class="filename">fedora/linux/releases/16/Fedora/<em class="replaceable"><code>arch</code></em>/os/images/boot.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" id="sect-Obtaining_Fedora-Obtaining_Fedora_on_CD_or_DVD">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><h2 class="title">Chapter 3. Making Media</h2></div></div></div><div class="toc"><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-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><dd><dl><dt><span class="section"><a href="#Making_Minimal_Boot_Media-UEFI">3.3.1. UEFI-based systems</a></span></dt></dl>
</dd></dl></div><a id="id558794" class="indexterm"></a><a id="id558779" class="indexterm"></a><div class="para">
+ </div></div></div><div xml:lang="en-US" class="chapter" id="sn-making-media" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 3. Making Media</h2></div></div></div><div class="toc"><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-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><dd><dl><dt><span class="section"><a href="#Making_Minimal_Boot_Media-UEFI">3.3.1. UEFI-based systems</a></span></dt></dl>
</dd></dl></div><a id="id653759" class="indexterm"></a><a id="id666165" class="indexterm"></a><div class="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
@@ -527,17 +527,17 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
For example:
</div><pre class="screen"><code class="command">dd if=/mnt/dvdiso/images/efidisk.img of=/dev/sdc</code></pre></li><li class="step"><div class="para">
Unmount the ISO image file:
- </div><pre class="screen"><code class="command">umount /mnt/dvdiso</code></pre></li></ol></div></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="id753570"><div></div><div class="para">
+ </div><pre class="screen"><code class="command">umount /mnt/dvdiso</code></pre></li></ol></div></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="id707397"><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><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="#id578290">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="#id911845">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-install-diff-source-x86">7.2. Installing from a Different Source </a></span></dt><dt><span class="section"><a href="#sn-booting-from-pxe-x86">7.3. Booting from the Network using PXE </a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Installation_Phase_2-x86">8. Configuring Language and Installation Source</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-guimode-textinterface-x86">8.1. The Text Mode Installation Program U
ser Interface</a></span></dt><dd><dl><dt><span class="section"><a href="#id789979">8.1.1. Using the Keyboard to Navigate</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-langselection-x86">8.2. Language Selection</a></span></dt><dt><span class="section"><a href="#s1-installationmethod-x86">8.3. Installation Method</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-begininstall-cd-inst-x86">8.3.1. Installing from DVD</a></span></dt><dt><span class="section"><a href="#s1-begininstall-hd-x86">8.3.2. Installing from a Hard Drive</a></span></dt><dt><span class="section"><a href="#s1-begininstall-perform-nfs-x86">8.3.3. Performing a Network Installation</a></span></dt><dt><span class="section"><a href="#s1-begininstall-nfs-x86">8.3.4. Installing via NFS</a></span></dt><dt><span class="section"><a href="#s1-begininstall-url-x86">8.3.5. Installing via FTP or HTTP</a></span></dt></dl></dd><dt><span class="section"><a href="#id550527">8.4. Verifying Media</a>
</span></dt></dl></dd><dt><span class="chapter"><a href="#ch-guimode-x86">9. Installing using anaconda</a></span></dt><dd><dl><dt><span class="section"><a href="#id1040236">9.1. The Text Mode Installation Program User Interface</a></span></dt><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="#sn-keyboard-x86">9.3. Keyboard Configuration</a></span></dt><dt><span class="section"><a href="#Storage_Devices-x86">9.4. Storage Devices</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Storage_Device_Selection_Screen-x86">9.4.1. The Storage Devices Selection Screen </a></span></dt></dl></dd><dt><spa
n class="section"><a href="#sn-Netconfig-x86">9.5. Setting the Hostname</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-Netconfig-x86-edit">9.5.1. Edit Network Connections</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-timezone-x86">9.6. Time Zone Configuration</a></span></dt><dt><span class="section"><a href="#sn-account_configuration-x86">9.7. Set the Root Password</a></span></dt><dt><span class="section"><a href="#Assign_Storage_Devices-x86">9.8. Assign Storage Devices </a></span></dt><dt><span class="section"><a href="#sn-initialize-hdd-x86">9.9. Initializing the Hard Disk</a></span></dt><dt><span class="section"><a href="#sn-upgrading-system-x86">9.10. Upgrading an Existing System </a></span></dt><dd><dl><dt><span class="section"><a href="#sn-upgrade-examine-x86">9.10.1. The Upgrade Dialog </a></span></dt><dt><span class="section"><a href="#sn-upgrade-tree-x86">9.10.2. Upgrading Using the Installer </a></span></dt><dt><span class="sect
ion"><a href="#sn-upgrading-bootloader-x86">9.10.3. Upgrading Boot Loader Configuration </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-diskpartsetup-x86">9.11. Disk Partitioning Setup</a></span></dt><dt><span class="section"><a href="#encrypt-x86">9.12. Encrypt Partitions </a></span></dt><dt><span class="section"><a href="#s1-diskpartitioning-x86">9.13. Creating a Custom Layout or Modifying the Default Layout </a></span></dt><dd><dl><dt><span class="section"><a href="#Create_Storage-x86">9.13.1. Create Storage </a></span></dt><dt><span class="section"><a href="#Adding_Partitions-x86">9.13.2. Adding Partitions</a></span></dt><dt><span class="section"><a href="#Create_Software_RAID-x86">9.13.3. Create Software RAID </a></span></dt><dt><span class="section"><a href="#Create_LVM-x86">9.13.4. Create LVM Logical Volume </a></span></dt><dt><span class="section"><a href="#s2-diskpartrecommend-x86">9.13.5. Recommended Partitioning Scheme</a></span></dt></dl></
dd><dt><span class="section"><a href="#Write_changes_to_disk-x86">9.14. Write changes to disk</a></span></dt><dt><span class="section"><a href="#s1-x86-bootloader">9.15. x86, AMD64, and Intel 64 Boot Loader Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#x86-bootloader-adv">9.15.1. Advanced Boot Loader Configuration</a></span></dt><dt><span class="section"><a href="#s2-x86-bootloader-rescue">9.15.2. Rescue Mode</a></span></dt><dt><span class="section"><a href="#s2-x86-bootloader-alt">9.15.3. Alternative Boot Loaders</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-pkgselection-x86">9.16. Package Group Selection</a></span></dt><dd><dl><dt><span class="section"><a href="#id1266148">9.16.1. Installing from Additional Repositories</a></span></dt><dt><span class="section"><a href="#sn-package-selection-x86">9.16.2. Customizing the Software Selection </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-installpkgs-x86">9.17. Ins
talling Packages</a></span></dt><dt><span class="section"><a href="#s1-complete-x86">9.18. Installation Complete</a></span></dt></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="#id693508">10.1. You are unable to boot Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="#id844055">10.1.1. Are You Unable to Boot With Your RAID Card?</a></span></dt><dt><span class="section"><a href="#id663989">10.1.2. Is Your System Displaying Signal 11 Errors?</a></span></dt></dl></dd><dt><span class="section"><a href="#id666318">10.2. Trouble Beginning the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#id1432449">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 c
lass="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. Saving 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="#id908960">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="#Trouble_After_Booting-GUI">10.4.2. Booting into a Graphical Environment</a></span></dt><
dt><span class="section"><a href="#id540116">10.4.3. Problems with the X Window System (GUI)</a></span></dt><dt><span class="section"><a href="#id970287">10.4.4. Problems with the X Server Crashing and Non-Root Users</a></span></dt><dt><span class="section"><a href="#id656508">10.4.5. Problems When You Try to Log In</a></span></dt><dt><span class="section"><a href="#s2-trouble-ram">10.4.6. Is Your RAM Not Being Recognized?</a></span></dt><dt><span class="section"><a href="#id1001590">10.4.7. Your Printer Does Not Work</a></span></dt><dt><span class="section"><a href="#id618256">10.4.8. 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><dt><span class="section"><a href="#id578290">4.1. Upgr
ade 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="#id911845">4.6. Choose a boot method</a></span></dt></dl></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div
><div keep-together.within-column="always"><h2 class="title" id="id578290">4.1. Upgrade or Install?</h2></div></div></div><div class="para">
+ </div><div class="toc"><p><strong>Table of Contents</strong></p><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="#id743701">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="#id519672">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-install-diff-source-x86">7.2. Installing from a Different Source </a></span></dt><dt><span class="section"><a href="#sn-booting-from-pxe-x86">7.3. Booting from the Network using PXE </a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Installation_Phase_2-x86">8. Configuring Language and Installation Source</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-guimode-textinterface-x86">8.1. The Text Mode Installation Program U
ser Interface</a></span></dt><dd><dl><dt><span class="section"><a href="#id1039021">8.1.1. Using the Keyboard to Navigate</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-langselection-x86">8.2. Language Selection</a></span></dt><dt><span class="section"><a href="#s1-installationmethod-x86">8.3. Installation Method</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-begininstall-cd-inst-x86">8.3.1. Installing from DVD</a></span></dt><dt><span class="section"><a href="#s1-begininstall-hd-x86">8.3.2. Installing from a Hard Drive</a></span></dt><dt><span class="section"><a href="#s1-begininstall-perform-nfs-x86">8.3.3. Performing a Network Installation</a></span></dt><dt><span class="section"><a href="#s1-begininstall-nfs-x86">8.3.4. Installing via NFS</a></span></dt><dt><span class="section"><a href="#s1-begininstall-url-x86">8.3.5. Installing via FTP or HTTP</a></span></dt></dl></dd><dt><span class="section"><a href="#id870317">8.4. Verifying Media</a
></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-guimode-x86">9. Installing using anaconda</a></span></dt><dd><dl><dt><span class="section"><a href="#id711680">9.1. The Text Mode Installation Program User Interface</a></span></dt><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="#sn-keyboard-x86">9.3. Keyboard Configuration</a></span></dt><dt><span class="section"><a href="#Storage_Devices-x86">9.4. Storage Devices</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Storage_Device_Selection_Screen-x86">9.4.1. The Storage Devices Selection Screen </a></span></dt></dl></dd><dt><spa
n class="section"><a href="#sn-Netconfig-x86">9.5. Setting the Hostname</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-Netconfig-x86-edit">9.5.1. Edit Network Connections</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-timezone-x86">9.6. Time Zone Configuration</a></span></dt><dt><span class="section"><a href="#sn-account_configuration-x86">9.7. Set the Root Password</a></span></dt><dt><span class="section"><a href="#Assign_Storage_Devices-x86">9.8. Assign Storage Devices </a></span></dt><dt><span class="section"><a href="#sn-initialize-hdd-x86">9.9. Initializing the Hard Disk</a></span></dt><dt><span class="section"><a href="#sn-upgrading-system-x86">9.10. Upgrading an Existing System </a></span></dt><dd><dl><dt><span class="section"><a href="#sn-upgrade-examine-x86">9.10.1. The Upgrade Dialog </a></span></dt><dt><span class="section"><a href="#sn-upgrade-tree-x86">9.10.2. Upgrading Using the Installer </a></span></dt><dt><span class="sect
ion"><a href="#sn-upgrading-bootloader-x86">9.10.3. Upgrading Boot Loader Configuration </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-diskpartsetup-x86">9.11. Disk Partitioning Setup</a></span></dt><dt><span class="section"><a href="#encrypt-x86">9.12. Encrypt Partitions </a></span></dt><dt><span class="section"><a href="#s1-diskpartitioning-x86">9.13. Creating a Custom Layout or Modifying the Default Layout </a></span></dt><dd><dl><dt><span class="section"><a href="#Create_Storage-x86">9.13.1. Create Storage </a></span></dt><dt><span class="section"><a href="#Adding_Partitions-x86">9.13.2. Adding Partitions</a></span></dt><dt><span class="section"><a href="#Create_Software_RAID-x86">9.13.3. Create Software RAID </a></span></dt><dt><span class="section"><a href="#Create_LVM-x86">9.13.4. Create LVM Logical Volume </a></span></dt><dt><span class="section"><a href="#s2-diskpartrecommend-x86">9.13.5. Recommended Partitioning Scheme</a></span></dt></dl></
dd><dt><span class="section"><a href="#Write_changes_to_disk-x86">9.14. Write changes to disk</a></span></dt><dt><span class="section"><a href="#s1-x86-bootloader">9.15. x86, AMD64, and Intel 64 Boot Loader Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#x86-bootloader-adv">9.15.1. Advanced Boot Loader Configuration</a></span></dt><dt><span class="section"><a href="#s2-x86-bootloader-rescue">9.15.2. Rescue Mode</a></span></dt><dt><span class="section"><a href="#s2-x86-bootloader-alt">9.15.3. Alternative Boot Loaders</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-pkgselection-x86">9.16. Package Group Selection</a></span></dt><dd><dl><dt><span class="section"><a href="#id513788">9.16.1. Installing from Additional Repositories</a></span></dt><dt><span class="section"><a href="#sn-package-selection-x86">9.16.2. Customizing the Software Selection </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-installpkgs-x86">9.17. Inst
alling Packages</a></span></dt><dt><span class="section"><a href="#s1-complete-x86">9.18. Installation Complete</a></span></dt></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="#id705731">10.1. You are unable to boot Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="#id809826">10.1.1. Are You Unable to Boot With Your RAID Card?</a></span></dt><dt><span class="section"><a href="#id595519">10.1.2. Is Your System Displaying Signal 11 Errors?</a></span></dt></dl></dd><dt><span class="section"><a href="#id709919">10.2. Trouble Beginning the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#id560395">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 cla
ss="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. Saving 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="#id889363">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="#Trouble_After_Booting-GUI">10.4.2. Booting into a Graphical Environment</a></span></dt><dt
><span class="section"><a href="#id746602">10.4.3. Problems with the X Window System (GUI)</a></span></dt><dt><span class="section"><a href="#id532309">10.4.4. Problems with the X Server Crashing and Non-Root Users</a></span></dt><dt><span class="section"><a href="#id646088">10.4.5. Problems When You Try to Log In</a></span></dt><dt><span class="section"><a href="#s2-trouble-ram">10.4.6. Is Your RAM Not Being Recognized?</a></span></dt><dt><span class="section"><a href="#id615608">10.4.7. Your Printer Does Not Work</a></span></dt><dt><span class="section"><a href="#id762738">10.4.8. 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><dt><span class="section"><a href="#id743701">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="#id519672">4.6. Choose a boot method</a></span></dt></dl></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><d
iv keep-together.within-column="always"><h2 class="title" id="id743701">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 20, <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" id="sn-Is_Your_Hardware_Compatible-x86">4.2. Is Your Hardware Compatible?</h2></div></div></div><a id="id904379" class="indexterm"></a><a id="id708835" 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" id="sn-Is_Your_Hardware_Compatible-x86">4.2. Is Your Hardware Compatible?</h2></div></div></div><a id="id624238" class="indexterm"></a><a id="id624234" 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 16 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">
The most recent list of supported hardware can be found in the Release Notes for Fedora 16, available at <a href="http://docs.fedoraproject.org/release-notes">http://docs.fedoraproject.org/release-notes</a> .
</div><div class="para">
At the end of a successful Fedora installation process, the installation program offers you the option to provide details of your hardware configuration anonymously to the Fedora Project (refer to <a class="xref" href="#sn-smolt">Section 17.4, “Hardware Profile”</a>). You can view the statistics gathered by this method at <a href="http://smolt.fedoraproject.org/static/stats/devices.html">http://smolt.fedoraproject.org/static/stats/devices.html</a>. Viewing the list of hardware that makes up systems on which other people have successfully installed Fedora might help you determine how suitable your hardware is.
- </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" id="sn-partitioning-raid-x86">4.3. RAID and Other Disk Devices </h2></div></div></div><a id="id693775" class="indexterm"></a><a id="id848613" class="indexterm"></a><a id="id740200" 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" id="sn-partitioning-raid-x86">4.3. RAID and Other Disk Devices </h2></div></div></div><a id="id632734" class="indexterm"></a><a id="id751771" class="indexterm"></a><a id="id564319" 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 16 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 16. 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.
@@ -551,39 +551,39 @@ 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" id="Disk_Space-x86">4.4. Do You Have Enough Disk Space?</h2></div></div></div><a id="id907430" class="indexterm"></a><a id="id931889" class="indexterm"></a><a id="id1312178" 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" id="Disk_Space-x86">4.4. Do You Have Enough Disk Space?</h2></div></div></div><a id="id601006" class="indexterm"></a><a id="id609533" class="indexterm"></a><a id="id586760" 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<sup>[<a id="id711072" href="#ftn.id711072" class="footnote">1</a>]</sup></em></span> disk space for the installation of Fedora, or
+ have enough <span class="emphasis"><em>unpartitioned<sup>[<a id="id791435" href="#ftn.id791435" class="footnote">1</a>]</sup></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.13.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" id="s1-installmethod-x86">4.5. Selecting an Installation Method</h2></div></div></div><a id="id810649" 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" id="s1-installmethod-x86">4.5. Selecting an Installation Method</h2></div></div></div><a id="id624020" 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="id755389" class="indexterm"></a><div class="variablelist"><dl><dt class="varlistentry"><span class="term">DVD</span></dt><dd><div class="para">
+ </div><a id="id539867" class="indexterm"></a><div class="variablelist"><dl><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.3.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 askmethod</code> or <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.3, “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.3.1, “Installing from DVD”</a> for CD installation instructions.
- </div></dd><dt class="varlistentry"><span class="term">Hard Drive</span></dt><dd><a id="id1427431" class="indexterm"></a><div class="para">
+ </div></dd><dt class="varlistentry"><span class="term">Hard Drive</span></dt><dd><a id="id884660" 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 askmethod</code> or <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.3, “Installation Method”</a>). Refer to <a class="xref" href="#s1-begininstall-hd-x86">Section 8.3.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="id782938" class="indexterm"></a><div class="para">
+ </div></dd><dt class="varlistentry"><span class="term">NFS</span></dt><dd><a id="id816853" 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 askmethod</code> or <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.3, “Installation Method”</a>). Refer to <a class="xref" href="#s1-begininstall-nfs-x86">Section 8.3.4, “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="id910850" class="indexterm"></a><div class="para">
+ </div></dd><dt class="varlistentry"><span class="term">URL</span></dt><dd><a id="id786071" 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 askmethod</code>, <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.3, “Installation Method”</a>). Refer to <a class="xref" href="#s1-begininstall-url-x86">Section 8.3.5, “Installing via FTP or HTTP”</a>, for FTP and HTTP installation instructions.
</div></dd></dl></div><div class="para">
If you booted the distribution DVD and did not use the alternate installation source option <code class="option">askmethod</code>, the next stage loads automatically from the DVD. Proceed to <a class="xref" href="#s1-langselection-x86">Section 8.2, “Language Selection”</a>.
</div><div class="note"><div class="admonition_header"><h2>DVD Activity</h2></div><div class="admonition"><div class="para">
If you boot from a Fedora installation DVD, the installation program loads its next stage from that disc. This happens regardless of which installation method you choose, unless you eject the disc before you proceed. The installation program still downloads <span class="emphasis"><em>package data</em></span> from the source you choose.
- </div></div></div></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id911845">4.6. Choose a boot method</h2></div></div></div><a id="id560312" class="indexterm"></a><div class="para">
+ </div></div></div></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id519672">4.6. Choose a boot method</h2></div></div></div><a id="id596428" 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 16 CD-ROM or DVD, and you have a DVD/CD-ROM drive on a system that supports booting from it.
@@ -593,9 +593,9 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
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.
</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 class="footnote"><div class="para"><sup>[<a id="ftn.id711072" href="#id711072" class="para">1</a>] </sup>
+ </div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><div class="para"><sup>[<a id="ftn.id791435" href="#id791435" class="para">1</a>] </sup>
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><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" id="s1-steps-network-installs-x86">5.1.
Preparing for a Network Installation</h2></div></div></div><a id="id951260" class="indexterm"></a><a id="id760556" class="indexterm"></a><a id="id1130690" class="indexterm"></a><a id="id919559" class="indexterm"></a><a id="id930637" class="indexterm"></a><a id="id637115" class="indexterm"></a><a id="id637106" class="indexterm"></a><a id="id866386" 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><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" id="s1-steps-network-installs-x86">5.1.
Preparing for a Network Installation</h2></div></div></div><a id="id680014" class="indexterm"></a><a id="id1079810" class="indexterm"></a><a id="id680009" class="indexterm"></a><a id="id699508" class="indexterm"></a><a id="id597110" class="indexterm"></a><a id="id735426" class="indexterm"></a><a id="id843394" class="indexterm"></a><a id="id501687" 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.
@@ -626,7 +626,9 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
Transfer the ISO image to the NFS exported directory. On a Linux system, run:
</div><pre xml:lang="en-US" class="screen" lang="en-US"><code class="command">mv /<em class="replaceable"><code>path_to_image</code></em>/<em class="replaceable"><code>name_of_image</code></em>.iso /<em class="replaceable"><code>publicly_available_directory</code></em>/</code></pre><div class="para">
where <em class="replaceable"><code>path_to_image</code></em> is the path to the ISO image file, <em class="replaceable"><code>name_of_image</code></em> is the name of the ISO image file, and <em class="replaceable"><code>publicly_available_directory</code></em> is a directory that is available over NFS or that you intend to make available over NFS.
-</div></li><li class="step"><div class="para">
+</div><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Contents of ISO directory</h2></div><div class="admonition"><div class="para">
+ The directory specified must only contain the ISO image file being used for this installation, otherwise <span class="application"><strong>anaconda</strong></span> will be unable to locate it.
+ </div></div></div></li><li class="step"><div class="para">
Use a SHA256 checksum program to verify that the ISO image that you copied is intact. Many SHA256 checksum programs are available for various operating systems. On a Linux system, run:
</div><pre xml:lang="en-US" class="screen" lang="en-US"><code class="command">$ sha256sum <em class="replaceable"><code>name_of_image</code></em>.iso</code></pre><div class="para">
where <em class="replaceable"><code>name_of_image</code></em> is the name of the ISO image file. The SHA256 checksum program displays a string of 64 characters called a <em class="firstterm">hash</em>. Compare this hash to the hash displayed for this particular image on the <span class="guilabel"><strong>GPG Keys</strong></span> page on the Fedora Project site at <a href="http://fedoraproject.org/en/keys">http://fedoraproject.org/en/keys</a>. The two hashes should be identical.
@@ -643,7 +645,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 mediacheck</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" id="s1-steps-hd-installs-x86">5.2. Preparing for a Hard Drive Installation</h2></div></div></div><a id="id738598" class="indexterm"></a><a id="id656472" 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 mediacheck</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" id="s1-steps-hd-installs-x86">5.2. Preparing for a Hard Drive Installation</h2></div></div></div><a id="id862082" class="indexterm"></a><a id="id732704" 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.
@@ -663,7 +665,9 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
Obtain an ISO image of the Fedora installation DVD (refer to <a class="xref" href="#ch-new-users">Chapter 2, <em>Obtaining Fedora</em></a>). Alternatively, if you have the DVD on physical media, you can create an image of it with the following command on a Linux system:
</div><pre xml:lang="en-US" class="screen" lang="en-US"><code class="command">dd if=/dev/<em class="replaceable"><code>dvd</code></em> of=/<em class="replaceable"><code>path_to_image</code></em>/<em class="replaceable"><code>name_of_image</code></em>.iso</code></pre><div class="para">
where <em class="replaceable"><code>dvd</code></em> is your DVD drive device, <em class="replaceable"><code>name_of_image</code></em> is the name you give to the give to the resulting ISO image file, and <em class="replaceable"><code>path_to_image</code></em> is the path to the location on your system where the resulting ISO image will be stored.
-</div></li><li class="step"><div class="para">
+</div><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Contents of ISO directory</h2></div><div class="admonition"><div class="para">
+ The directory specified must only contain the ISO image file being used for this installation, otherwise <span class="application"><strong>anaconda</strong></span> will be unable to locate it.
+ </div></div></div></li><li class="step"><div class="para">
Transfer the ISO image to the hard drive.
</div><div class="para">
The ISO image must be located on a hard drive that is either internal to the computer on which you will install Fedora, or on a hard drive that is attached to that computer by USB.
@@ -674,7 +678,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 mediacheck</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="id559971" class="indexterm"></a><a id="id580740" class="indexterm"></a><div class="para">
+<strong class="userinput"><code>linux mediacheck</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="id716140" class="indexterm"></a><a id="id506528" 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.
@@ -716,7 +720,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><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-install-diff-source-x86">7.2. Installing from a Different Source </a></span></dt><dt><span class="section"><a href="#sn-booting-from-pxe-x86">7.3. Booting from the Network using PXE </a></span></dt></dl></div><a id="id819811" c
lass="indexterm"></a><a id="id634506" class="indexterm"></a><a id="id746592" class="indexterm"></a><a id="id771470" 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><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-install-diff-source-x86">7.2. Installing from a Different Source </a></span></dt><dt><span class="section"><a href="#sn-booting-from-pxe-x86">7.3. Booting from the Network using PXE </a></span></dt></dl></div><a id="id616013" c
lass="indexterm"></a><a id="id693872" class="indexterm"></a><a id="id701151" class="indexterm"></a><a id="id615628" 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 16 does not support UEFI for 32-bit x86 systems.
</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.
@@ -746,7 +750,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>Write changes to disk</strong></span> on the <span class="guilabel"><strong>Write partitioning to disk</strong></span> screen. 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" id="s1-x86-starting">7.1. Starting the Installation Program</h2></div></div></div><a id="id567801" class="indexterm"></a><a id="id697271" 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" id="s1-x86-starting">7.1. Starting the Installation Program</h2></div></div></div><a id="id680522" class="indexterm"></a><a id="id708570" 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 16 does not support UEFI for 32-bit x86 systems.
</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.
@@ -754,7 +758,7 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
Fedora 16 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 16, 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" id="s2-x86-starting-booting">7.1.1. Booting the Installation Program on x86, AMD64, and Intel 64 Systems</h3></div></div></div><a id="id750301" class="indexterm"></a><a id="id665247" 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" id="s2-x86-starting-booting">7.1.1. Booting the Installation Program on x86, AMD64, and Intel 64 Systems</h3></div></div></div><a id="id839674" class="indexterm"></a><a id="id534231" 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.
@@ -806,20 +810,20 @@ 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="#sn-memtest">Section 11.6.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" id="s2-x86-starting-bootopts">7.1.3. Additional Boot Options</h3></div></div></div><a id="id797863" 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" id="s2-x86-starting-bootopts">7.1.3. Additional Boot Options</h3></div></div></div><a id="id590302" 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.
</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
Refer to <a class="xref" href="#ap-admin-options">Chapter 11, <em>Boot Options</em></a> for additional boot options not covered in this section.
</div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <a id="id621221" class="indexterm"></a>
- <a id="id915157" class="indexterm"></a>
+ <a id="id760821" class="indexterm"></a>
+ <a id="id844008" 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="id642818" class="indexterm"></a>
- <a id="id677934" class="indexterm"></a>
+ <a id="id524334" class="indexterm"></a>
+ <a id="id706530" class="indexterm"></a>
To specify an installation source, use the <code class="command">linux repo=</code> option. For example:
</div><pre class="screen">
<strong class="userinput"><code>linux repo=cdrom:<em class="replaceable"><code>device</code></em></code></strong></pre><pre class="screen">
@@ -830,18 +834,18 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
<strong class="userinput"><code>linux repo=nfsiso<em class="replaceable"><code>:options</code></em>:<em class="replaceable"><code>server</code></em>:/<em class="replaceable"><code>path</code></em></code></strong></pre><div class="para">
In these examples, <code class="literal">cdrom</code> refers to a CD or DVD drive, <code class="literal">ftp</code> refers to a location accessible by FTP, <code class="literal">http</code> refers to a location accessible by HTTP, <code class="literal">hd</code> refers to an ISO image file accessible on a hard drive partition, <code class="literal">nfs</code> refers to an expanded tree of installation files accessible by NFS, and <code class="literal">nfsiso</code> refers to an ISO image file accessible by NFS.
</div></li><li class="listitem"><div class="para">
- <a id="id711142" class="indexterm"></a>
- <a id="id729409" class="indexterm"></a>
- <a id="id598714" class="indexterm"></a>
+ <a id="id732790" class="indexterm"></a>
+ <a id="id579361" class="indexterm"></a>
+ <a id="id696340" 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 mediacheck</code></strong></pre><div class="para">
The installation program prompts you to insert a DVD or select an ISO image to test, and select <span class="guibutton"><strong>OK</strong></span> to perform the checksum operation. 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="id768518" class="indexterm"></a>
- <a id="id701855" class="indexterm"></a>
- <a id="id1385193" class="indexterm"></a>
- <a id="id922586" class="indexterm"></a>
+ <a id="id552055" class="indexterm"></a>
+ <a id="id842316" class="indexterm"></a>
+ <a id="id782742" class="indexterm"></a>
+ <a id="id874178" 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">
@@ -854,7 +858,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" id="s3-x86-starting-kernelopts">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="id803430" class="indexterm"></a><pre class="screen">
+ </div><a id="id648440" 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">
@@ -894,7 +898,7 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
Refer to <a class="xref" href="#s1-installmethod-x86">Section 4.5, “Selecting an Installation Method”</a> for information about installing from locations other than the media with which you booted the system.
</div></div><div class="section" id="sn-booting-from-pxe-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sn-booting-from-pxe-x86">7.3. Booting from the Network using PXE </h2></div></div></div><div class="para">
To boot with
- <a id="id615484" class="indexterm"></a>
+ <a id="id651798" 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.
@@ -915,9 +919,9 @@ APPEND ksdevice=bootif</pre><div class="para">
These configuration options above cause the installer to use the same network interface the firmware interface and PXE use. You can also use the following option:
</div><pre class="programlisting">ksdevice=link</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 Language and Installation Source</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-guimode-textinterface-x86">8.1. The Text Mode Installation Program User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="#id789979">8.1.1. Using the Keyboard to Navigate</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-langselection-x86">8.2. Language Selection</a></span></dt><dt><span class="section"><a href="#s1-installationmethod-x86">8.3. Installation Method</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-begininstall-cd-inst-x86">8.3.1. Installing from DVD</a></span></dt><dt><span class="section"><a href="#s1-begininstall-hd-x86">8.3.2. Installing from a Hard Drive</a></span></dt><dt><span class="section"><a href="#s1-begi
ninstall-perform-nfs-x86">8.3.3. Performing a Network Installation</a></span></dt><dt><span class="section"><a href="#s1-begininstall-nfs-x86">8.3.4. Installing via NFS</a></span></dt><dt><span class="section"><a href="#s1-begininstall-url-x86">8.3.5. Installing via FTP or HTTP</a></span></dt></dl></dd><dt><span class="section"><a href="#id550527">8.4. Verifying Media</a></span></dt></dl></div><div class="para">
+ </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 Language and Installation Source</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-guimode-textinterface-x86">8.1. The Text Mode Installation Program User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="#id1039021">8.1.1. Using the Keyboard to Navigate</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-langselection-x86">8.2. Language Selection</a></span></dt><dt><span class="section"><a href="#s1-installationmethod-x86">8.3. Installation Method</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-begininstall-cd-inst-x86">8.3.1. Installing from DVD</a></span></dt><dt><span class="section"><a href="#s1-begininstall-hd-x86">8.3.2. Installing from a Hard Drive</a></span></dt><dt><span class="section"><a href="#s1-beg
ininstall-perform-nfs-x86">8.3.3. Performing a Network Installation</a></span></dt><dt><span class="section"><a href="#s1-begininstall-nfs-x86">8.3.4. Installing via NFS</a></span></dt><dt><span class="section"><a href="#s1-begininstall-url-x86">8.3.5. Installing via FTP or HTTP</a></span></dt></dl></dd><dt><span class="section"><a href="#id870317">8.4. Verifying Media</a></span></dt></dl></div><div class="para">
Before the graphical installation program starts, you need to configure the language and installation source.
-</div><div xml:lang="en-US" class="section" id="s1-guimode-textinterface-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-guimode-textinterface-x86">8.1. The Text Mode Installation Program User Interface</h2></div></div></div><a id="id650204" class="indexterm"></a><a id="id617269" class="indexterm"></a><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="s1-guimode-textinterface-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-guimode-textinterface-x86">8.1. The Text Mode Installation Program User Interface</h2></div></div></div><a id="id495053" class="indexterm"></a><a id="id786028" class="indexterm"></a><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>
@@ -945,7 +949,7 @@ APPEND ksdevice=bootif</pre><div class="para">
Button Widget — Button widgets are the primary method of interacting with the installation program. You progress through the windows of the installation program by navigating these buttons, using the <span class="keycap"><strong>Tab</strong></span> and <span class="keycap"><strong>Enter</strong></span> keys. Buttons can be selected when they are highlighted.
</div></li><li class="listitem"><div class="para">
Cursor — Although not a widget, the cursor is used to select (and interact with) a particular widget. As the cursor is moved from widget to widget, it may cause the widget to change color, or the cursor itself may only appear positioned in or next to the widget. In <a class="xref" href="#fig-install-widget1-x86">Figure 8.1, “Installation Program Widgets as seen in <span class="guilabel">URL Setup</span>”</a>, the cursor is positioned on the <span class="guibutton"><strong>OK</strong></span> button. <a class="xref" href="#fig-install-widget2-x86">Figure 8.2, “Installation Program Widgets as seen in <span class="guilabel">Choose a Language</span>”</a>, shows the cursor on the <span class="guibutton"><strong>Edit</strong></span> button.
- </div></li></ul></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id789979">8.1.1. Using the Keyboard to Navigate</h3></div></div></div><a id="id783173" class="indexterm"></a><a id="id508488" class="indexterm"></a><div class="para">
+ </div></li></ul></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id1039021">8.1.1. Using the Keyboard to Navigate</h3></div></div></div><a id="id891178" class="indexterm"></a><a id="id526707" 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.
@@ -953,7 +957,7 @@ 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 xml:lang="en-US" class="section" id="s1-langselection-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-langselection-x86">8.2. Language Selection</h2></div></div></div><a id="id802425" class="indexterm"></a><div class="para">
+ </div></div></div></div></div><div xml:lang="en-US" class="section" id="s1-langselection-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-langselection-x86">8.2. Language Selection</h2></div></div></div><a id="id870607" class="indexterm"></a><div class="para">
Use the arrow keys on your keyboard to select a language to use during the installation process (refer to <a class="xref" href="#fig-langselection-x86">Figure 8.3, “Language Selection”</a>). With your selected language highlighted, press the <span class="keycap"><strong>Tab</strong></span> key to move to the <span class="guibutton"><strong>OK</strong></span> button and press the <span class="keycap"><strong>Enter</strong></span> key to confirm your choice.
</div><div class="para">
The language you select here will become the default language for the operating system once it is installed. Selecting the appropriate language also helps target your time zone configuration later in the installation. The installation program tries to define the appropriate time zone based on what you specify on this screen.
@@ -963,21 +967,21 @@ APPEND ksdevice=bootif</pre><div class="para">
Language selection screen.
</div></div></div></div><h6>Figure 8.3. Language Selection</h6></div><br class="figure-break" /><div class="para">
Once you select the appropriate language, click <span class="guibutton"><strong>Next</strong></span> to continue.
-</div></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" id="s1-installationmethod-x86">8.3. Installation Method</h2></div></div></div><a id="id719783" class="indexterm"></a><div class="para">
+</div></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" id="s1-installationmethod-x86">8.3. Installation Method</h2></div></div></div><a id="id530520" class="indexterm"></a><div class="para">
If you booted the installation from minimal boot media or with the <code class="command">askmethod</code> boot option, use the arrow keys on your keyboard to select an installation method (refer to <a class="xref" href="#fig-installationmethod-x86">Figure 8.4, “Installation Method”</a>). With your selected method highlighted, press the <span class="keycap"><strong>Tab</strong></span> key to move to the <span class="guibutton"><strong>OK</strong></span> button and press the <span class="keycap"><strong>Enter</strong></span> key to confirm your choice.
</div><div class="figure" id="fig-installationmethod-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/installationmethod/method.png" alt="Installation Method" /><div class="longdesc"><div class="para">
Installation method screen.
- </div></div></div></div><h6>Figure 8.4. Installation Method</h6></div><br class="figure-break" /><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" id="s1-begininstall-cd-inst-x86">8.3.1. Installing from DVD</h3></div></div></div><a id="id716574" class="indexterm"></a><a id="id918036" class="indexterm"></a><a id="id524508" class="indexterm"></a><a id="id590193" class="indexterm"></a><a id="id714997" class="indexterm"></a><a id="id805113" class="indexterm"></a><div class="para">
+ </div></div></div></div><h6>Figure 8.4. Installation Method</h6></div><br class="figure-break" /><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" id="s1-begininstall-cd-inst-x86">8.3.1. Installing from DVD</h3></div></div></div><a id="id683601" class="indexterm"></a><a id="id711188" class="indexterm"></a><a id="id763705" class="indexterm"></a><a id="id578115" class="indexterm"></a><a id="id647048" class="indexterm"></a><a id="id750344" 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="id630135" class="indexterm"></a><a id="id568855" class="indexterm"></a><div class="para">
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><a id="id504249" class="indexterm"></a><a id="id722026" 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 the <span class="guilabel"><strong>Write changes to disk</strong></span> screen. Refer to <a class="xref" href="#Write_changes_to_disk-x86">Section 9.14, “Write changes to disk”</a> for more information.
- </div></div></div><a id="id697605" class="indexterm"></a><div class="para">
+ </div></div></div><a id="id782973" 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 the DVD drive is found and the driver loaded, the installer will present you with the option to perform a media check on the DVD. This will take some time, and you may opt to skip over this step. However, if you later encounter problems with the installer, you should reboot and perform the media check before calling for support. From the media check dialog, continue to the next stage of the installation process (refer to <a class="xref" href="#sn-keyboard-x86">Section 9.3, “Keyboard Configuration”</a>).
- </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" id="s1-begininstall-hd-x86">8.3.2. Installing from a Hard Drive</h3></div></div></div><a id="id557144" class="indexterm"></a><a id="id904460" class="indexterm"></a><a id="id768539" class="indexterm"></a><a id="id767073" class="indexterm"></a><a id="id597754" class="indexterm"></a><a id="id609282" class="indexterm"></a><a id="id622033" class="indexterm"></a><a id="id797615" class="indexterm"></a><a id="id573400" class="indexterm"></a><a id="id642656" 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" id="s1-begininstall-hd-x86">8.3.2. Installing from a Hard Drive</h3></div></div></div><a id="id682435" class="indexterm"></a><a id="id569673" class="indexterm"></a><a id="id924949" class="indexterm"></a><a id="id803692" class="indexterm"></a><a id="id782673" class="indexterm"></a><a id="id676559" class="indexterm"></a><a id="id833844" class="indexterm"></a><a id="id686533" class="indexterm"></a><a id="id1352094" class="indexterm"></a><a id="id476984" class="indexterm"></a><div class="para">
The <span class="guilabel"><strong>Select Partition</strong></span> screen applies only if you are installing from a disk partition (that is, you selected <span class="guimenuitem"><strong>Hard Drive</strong></span> in the <span class="guilabel"><strong>Installation Method</strong></span> dialog). This dialog allows you to name the disk partition and directory from which you are installing Fedora. If you used the <code class="literal">repo=hd</code> boot option, you already specified a partition.
</div><div class="figure" xml:lang="en-US" lang="en-US"><div class="figure-contents"><div class="mediaobject"><img src="images/begininstall/hd.png" width="444" alt="Selecting Partition Dialog for Hard Drive Installation" /><div class="longdesc"><div class="para">
Selecting partition dialog for a hard drive installation.
@@ -1015,7 +1019,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">
Select <span class="guibutton"><strong>OK</strong></span> to continue. Proceed with <a class="xref" href="#ch-guimode-x86">Chapter 9, <em>Installing using anaconda</em></a>.
- </div></div><div xml:lang="en-US" class="section" id="s1-begininstall-perform-nfs-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-begininstall-perform-nfs-x86">8.3.3. Performing a Network Installation</h3></div></div></div><a id="id733545" class="indexterm"></a><a id="id726246" class="indexterm"></a><a id="id564608" class="indexterm"></a><div class="para">
+ </div></div><div xml:lang="en-US" class="section" id="s1-begininstall-perform-nfs-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-begininstall-perform-nfs-x86">8.3.3. Performing a Network Installation</h3></div></div></div><a id="id501682" class="indexterm"></a><a id="id658505" class="indexterm"></a><a id="id677239" class="indexterm"></a><div class="para">
When you start an installation with the <code class="literal">askmethod</code> or <code class="literal">repo=</code> options, you can install Fedora from a network server using FTP, HTTP, or NFS protocols. <span class="application"><strong>Anaconda</strong></span> uses the same network connection to consult additional software repositories later in the installation process.
</div><div class="para">
If your system has more than one network device, <span class="application"><strong>anaconda</strong></span> presents you with a list of all available devices and prompts you to select one to use during installation. If your system only has a single network device, <span class="application"><strong>anaconda</strong></span> automatically selects it and does not present this dialog.
@@ -1055,7 +1059,7 @@ APPEND ksdevice=bootif</pre><div class="para">
If you are installing via NFS, proceed to <a class="xref" href="#s1-begininstall-nfs-x86">Section 8.3.4, “Installing via NFS”</a>.
</div></li><li class="listitem"><div class="para">
If you are installing via Web or FTP, proceed to <a class="xref" href="#s1-begininstall-url-x86">Section 8.3.5, “Installing via FTP or HTTP”</a>.
- </div></li></ul></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" id="s1-begininstall-nfs-x86">8.3.4. Installing via NFS</h3></div></div></div><a id="id700580" class="indexterm"></a><a id="id617088" class="indexterm"></a><a id="id671672" class="indexterm"></a><a id="id783429" class="indexterm"></a><div class="para">
+ </div></li></ul></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" id="s1-begininstall-nfs-x86">8.3.4. Installing via NFS</h3></div></div></div><a id="id619370" class="indexterm"></a><a id="id679246" class="indexterm"></a><a id="id478482" class="indexterm"></a><a id="id742719" class="indexterm"></a><div class="para">
The NFS dialog applies only if you selected <span class="guimenuitem"><strong>NFS Image</strong></span> in the <span class="guilabel"><strong>Installation Method</strong></span> dialog. If you used the <code class="literal">repo=nfs</code> boot option, you already specified a server and path.
</div><div class="figure" xml:lang="en-US" lang="en-US"><div class="figure-contents"><div class="mediaobject"><img src="images/begininstall/nfs.png" width="444" alt="NFS Setup Dialog" /><div class="longdesc"><div class="para">
NFS setup dialog.
@@ -1073,7 +1077,7 @@ APPEND ksdevice=bootif</pre><div class="para">
Specify any NFS mount options that you require in the <span class="guilabel"><strong>NFS mount options</strong></span> field. Refer to the man pages for <span class="application"><strong>mount</strong></span> and <span class="application"><strong>nfs</strong></span> for a comprehensive list of options. If you do not require any mount options, leave the field empty.
</div></li><li class="step"><div class="para">
Proceed with <a class="xref" href="#ch-guimode-x86">Chapter 9, <em>Installing using anaconda</em></a>.
- </div></li></ol></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" id="s1-begininstall-url-x86">8.3.5. Installing via FTP or HTTP</h3></div></div></div><a id="id687858" class="indexterm"></a><a id="id574290" class="indexterm"></a><a id="id507976" class="indexterm"></a><a id="id669969" class="indexterm"></a><a id="id596867" class="indexterm"></a><a id="id700165" 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></li></ol></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" id="s1-begininstall-url-x86">8.3.5. Installing via FTP or HTTP</h3></div></div></div><a id="id659904" class="indexterm"></a><a id="id782855" class="indexterm"></a><a id="id505304" class="indexterm"></a><a id="id647052" class="indexterm"></a><a id="id730402" class="indexterm"></a><a id="id861267" 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">
The URL dialog applies only if you are installing from a FTP or HTTP server (if you selected <span class="guimenuitem"><strong>URL</strong></span> in the <span class="guilabel"><strong>Installation Method</strong></span> dialog). This dialog prompts you for information about the FTP or HTTP server from which you are installing Fedora. If you used the <code class="literal">repo=ftp</code> or <code class="literal">repo=http</code> boot option, you already specified a server and path.
@@ -1095,13 +1099,13 @@ APPEND ksdevice=bootif</pre><div class="para">
URL setup dialog.
</div></div></div></div><h6>Figure 8.11. URL Setup Dialog</h6></div><br class="figure-break" /><div class="para">
Proceed with <a class="xref" href="#ch-guimode-x86">Chapter 9, <em>Installing using anaconda</em></a>.
- </div></div></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id550527">8.4. Verifying Media</h2></div></div></div><div class="para">
+ </div></div></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id870317">8.4. Verifying Media</h2></div></div></div><div class="para">
The DVD offers an option to verify the integrity of the media. Recording errors sometimes occur while producing DVD media. An error in the data for package chosen in the installation program can cause the installation to abort. To minimize the chances of data errors affecting the installation, verify the media before installing.
</div><div class="para">
If the verification succeeds, the installation process proceeds normally. If the process fails, create a new DVD using the ISO image you downloaded earlier.
- </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. Installing using anaconda</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#id1040236">9.1. The Text Mode Installation Program User Interface</a></span></dt><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="#sn-keyboard-x86">9.3. Keyboard Configuration</a></span></dt><dt><span class="section"><a href="#Storage_Devices-x86">9.4. Storage Devices</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Storage_Device_Sele
ction_Screen-x86">9.4.1. The Storage Devices Selection Screen </a></span></dt></dl></dd><dt><span class="section"><a href="#sn-Netconfig-x86">9.5. Setting the Hostname</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-Netconfig-x86-edit">9.5.1. Edit Network Connections</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-timezone-x86">9.6. Time Zone Configuration</a></span></dt><dt><span class="section"><a href="#sn-account_configuration-x86">9.7. Set the Root Password</a></span></dt><dt><span class="section"><a href="#Assign_Storage_Devices-x86">9.8. Assign Storage Devices </a></span></dt><dt><span class="section"><a href="#sn-initialize-hdd-x86">9.9. Initializing the Hard Disk</a></span></dt><dt><span class="section"><a href="#sn-upgrading-system-x86">9.10. Upgrading an Existing System </a></span></dt><dd><dl><dt><span class="section"><a href="#sn-upgrade-examine-x86">9.10.1. The Upgrade Dialog </a></span></dt><dt><span class="section"><a href="#
sn-upgrade-tree-x86">9.10.2. Upgrading Using the Installer </a></span></dt><dt><span class="section"><a href="#sn-upgrading-bootloader-x86">9.10.3. Upgrading Boot Loader Configuration </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-diskpartsetup-x86">9.11. Disk Partitioning Setup</a></span></dt><dt><span class="section"><a href="#encrypt-x86">9.12. Encrypt Partitions </a></span></dt><dt><span class="section"><a href="#s1-diskpartitioning-x86">9.13. Creating a Custom Layout or Modifying the Default Layout </a></span></dt><dd><dl><dt><span class="section"><a href="#Create_Storage-x86">9.13.1. Create Storage </a></span></dt><dt><span class="section"><a href="#Adding_Partitions-x86">9.13.2. Adding Partitions</a></span></dt><dt><span class="section"><a href="#Create_Software_RAID-x86">9.13.3. Create Software RAID </a></span></dt><dt><span class="section"><a href="#Create_LVM-x86">9.13.4. Create LVM Logical Volume </a></span></dt><dt><span class="section"><
a href="#s2-diskpartrecommend-x86">9.13.5. Recommended Partitioning Scheme</a></span></dt></dl></dd><dt><span class="section"><a href="#Write_changes_to_disk-x86">9.14. Write changes to disk</a></span></dt><dt><span class="section"><a href="#s1-x86-bootloader">9.15. x86, AMD64, and Intel 64 Boot Loader Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#x86-bootloader-adv">9.15.1. Advanced Boot Loader Configuration</a></span></dt><dt><span class="section"><a href="#s2-x86-bootloader-rescue">9.15.2. Rescue Mode</a></span></dt><dt><span class="section"><a href="#s2-x86-bootloader-alt">9.15.3. Alternative Boot Loaders</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-pkgselection-x86">9.16. Package Group Selection</a></span></dt><dd><dl><dt><span class="section"><a href="#id1266148">9.16.1. Installing from Additional Repositories</a></span></dt><dt><span class="section"><a href="#sn-package-selection-x86">9.16.2. Customizing the Software Sele
ction </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-installpkgs-x86">9.17. Installing Packages</a></span></dt><dt><span class="section"><a href="#s1-complete-x86">9.18. Installation Complete</a></span></dt></dl></div><a id="id641533" class="indexterm"></a><div class="para">
+ </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. Installing using anaconda</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#id711680">9.1. The Text Mode Installation Program User Interface</a></span></dt><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="#sn-keyboard-x86">9.3. Keyboard Configuration</a></span></dt><dt><span class="section"><a href="#Storage_Devices-x86">9.4. Storage Devices</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Storage_Device_Selec
tion_Screen-x86">9.4.1. The Storage Devices Selection Screen </a></span></dt></dl></dd><dt><span class="section"><a href="#sn-Netconfig-x86">9.5. Setting the Hostname</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-Netconfig-x86-edit">9.5.1. Edit Network Connections</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-timezone-x86">9.6. Time Zone Configuration</a></span></dt><dt><span class="section"><a href="#sn-account_configuration-x86">9.7. Set the Root Password</a></span></dt><dt><span class="section"><a href="#Assign_Storage_Devices-x86">9.8. Assign Storage Devices </a></span></dt><dt><span class="section"><a href="#sn-initialize-hdd-x86">9.9. Initializing the Hard Disk</a></span></dt><dt><span class="section"><a href="#sn-upgrading-system-x86">9.10. Upgrading an Existing System </a></span></dt><dd><dl><dt><span class="section"><a href="#sn-upgrade-examine-x86">9.10.1. The Upgrade Dialog </a></span></dt><dt><span class="section"><a href="#s
n-upgrade-tree-x86">9.10.2. Upgrading Using the Installer </a></span></dt><dt><span class="section"><a href="#sn-upgrading-bootloader-x86">9.10.3. Upgrading Boot Loader Configuration </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-diskpartsetup-x86">9.11. Disk Partitioning Setup</a></span></dt><dt><span class="section"><a href="#encrypt-x86">9.12. Encrypt Partitions </a></span></dt><dt><span class="section"><a href="#s1-diskpartitioning-x86">9.13. Creating a Custom Layout or Modifying the Default Layout </a></span></dt><dd><dl><dt><span class="section"><a href="#Create_Storage-x86">9.13.1. Create Storage </a></span></dt><dt><span class="section"><a href="#Adding_Partitions-x86">9.13.2. Adding Partitions</a></span></dt><dt><span class="section"><a href="#Create_Software_RAID-x86">9.13.3. Create Software RAID </a></span></dt><dt><span class="section"><a href="#Create_LVM-x86">9.13.4. Create LVM Logical Volume </a></span></dt><dt><span class="section"><a
href="#s2-diskpartrecommend-x86">9.13.5. Recommended Partitioning Scheme</a></span></dt></dl></dd><dt><span class="section"><a href="#Write_changes_to_disk-x86">9.14. Write changes to disk</a></span></dt><dt><span class="section"><a href="#s1-x86-bootloader">9.15. x86, AMD64, and Intel 64 Boot Loader Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#x86-bootloader-adv">9.15.1. Advanced Boot Loader Configuration</a></span></dt><dt><span class="section"><a href="#s2-x86-bootloader-rescue">9.15.2. Rescue Mode</a></span></dt><dt><span class="section"><a href="#s2-x86-bootloader-alt">9.15.3. Alternative Boot Loaders</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-pkgselection-x86">9.16. Package Group Selection</a></span></dt><dd><dl><dt><span class="section"><a href="#id513788">9.16.1. Installing from Additional Repositories</a></span></dt><dt><span class="section"><a href="#sn-package-selection-x86">9.16.2. Customizing the Software Select
ion </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-installpkgs-x86">9.17. Installing Packages</a></span></dt><dt><span class="section"><a href="#s1-complete-x86">9.18. Installation Complete</a></span></dt></dl></div><a id="id899534" 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" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id1040236">9.1. The Text Mode Installation Program User Interface</h2></div></div></div><div class="important"><div class="admonition_header"><h2>Important — Graphical Interface on the Installed System</h2></div><div class="admonition"><div class="para">
+</div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id711680">9.1. The Text Mode Installation Program User Interface</h2></div></div></div><div class="important"><div class="admonition_header"><h2>Important — Graphical Interface on the Installed System</h2></div><div class="admonition"><div class="para">
Installing in text mode does not prevent you from using a graphical interface on your system once it is installed.
</div></div></div><div class="para">
Apart from the graphical installer, <span class="application"><strong>anaconda</strong></span> also includes a text-based installer.
@@ -1127,7 +1131,7 @@ APPEND ksdevice=bootif</pre><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 18.3, “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.
- </div></div><div class="section" id="s1-guimode-interface-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-guimode-interface-x86">9.2. The Graphical Installation Program User Interface</h2></div></div></div><a id="id933852" class="indexterm"></a><a id="id667307" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s1-guimode-interface-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-guimode-interface-x86">9.2. The Graphical Installation Program User Interface</h2></div></div></div><a id="id712444" class="indexterm"></a><a id="id857800" 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.
@@ -1140,11 +1144,11 @@ APPEND ksdevice=bootif</pre><div class="para">
It is highly recommended that installs be performed using the GUI installation program. The GUI installation program offers the full functionality of the Fedora installation program, including LVM configuration which is not available during a text mode installation.
</div><div class="para">
Users who must use the text mode installation program can follow the GUI installation instructions and obtain all needed information.
-</div></div></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" id="sect-adminoptions-screenshots">9.2.1. Screenshots during installation</h3></div></div></div><a id="id878965" class="indexterm"></a><div class="para">
+</div></div></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" id="sect-adminoptions-screenshots">9.2.1. Screenshots during installation</h3></div></div></div><a id="id622118" 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" id="sn-guimode-virtual-consoles-x86">9.2.2. A Note about Virtual Consoles</h3></div></div></div><a id="id611817" class="indexterm"></a><a id="id586500" class="indexterm"></a><a id="id689589" 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" id="sn-guimode-virtual-consoles-x86">9.2.2. A Note about Virtual Consoles</h3></div></div></div><a id="id782014" class="indexterm"></a><a id="id845377" class="indexterm"></a><a id="id632246" 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.
@@ -1188,7 +1192,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>f5</strong></span>
</td><td>
other messages
- </td></tr></tbody></table></div></div><br class="table-break" /></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" id="sn-keyboard-x86">9.3. Keyboard Configuration</h2></div></div></div><a id="id951239" class="indexterm"></a><a id="id876714" 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="sn-keyboard-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sn-keyboard-x86">9.3. Keyboard Configuration</h2></div></div></div><a id="id479625" class="indexterm"></a><a id="id849789" class="indexterm"></a><div class="para">
Using your mouse, select the correct layout type (for example, U.S. English) for the keyboard you would prefer to use for the installation and as the system default (refer to the figure below).
</div><div class="para">
Once you have made your selection, click <span class="guibutton"><strong>Next</strong></span> to continue.
@@ -1200,7 +1204,7 @@ APPEND ksdevice=bootif</pre><div class="para">
To change your keyboard layout type after you have completed the installation, use the <span class="application"><strong>Keyboard Configuration Tool</strong></span>.
</div><div class="para">
Type the <code class="command">system-config-keyboard</code> command in a shell prompt to launch the <span class="application"><strong>Keyboard Configuration Tool</strong></span>. If you are not root, it prompts you for the root password to continue.
- </div></div></div></div><div xml:lang="en-US" class="section" id="Storage_Devices-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="Storage_Devices-x86">9.4. Storage Devices</h2></div></div></div><a id="id803214" class="indexterm"></a><a id="id769367" class="indexterm"></a><div class="para">
+ </div></div></div></div><div xml:lang="en-US" class="section" id="Storage_Devices-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="Storage_Devices-x86">9.4. Storage Devices</h2></div></div></div><a id="id564249" class="indexterm"></a><a id="id529935" class="indexterm"></a><div class="para">
You can install Fedora on a large variety of storage devices. This screen allows you to select either basic or specialized storage devices.
</div><div class="figure" xml:lang="en-US" lang="en-US"><div class="figure-contents"><div class="mediaobject"><img src="images/storagedevices/storagedevices.png" width="444" alt="Storage devices" /><div class="longdesc"><div class="para">
Screen to select basic or specialized storage devices
@@ -1258,11 +1262,11 @@ 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="id557955" class="indexterm"></a><div class="para">
+</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="id730373" 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">
when you have selected the storage devices to make available during installation, click <span class="guibutton"><strong>Next</strong></span> and proceed to <a class="xref" href="#sn-initialize-hdd-x86">Section 9.9, “Initializing the Hard Disk”</a>
- </div><div xml:lang="en-US" class="section" id="s1-advanced-storage-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s1-advanced-storage-x86">9.4.1.1. Advanced Storage Options </h4></div></div></div><a id="id700421" class="indexterm"></a><a id="id695568" class="indexterm"></a><div class="para">
+ </div><div xml:lang="en-US" class="section" id="s1-advanced-storage-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s1-advanced-storage-x86">9.4.1.1. Advanced Storage Options </h4></div></div></div><a id="id807711" class="indexterm"></a><a id="id534845" class="indexterm"></a><div class="para">
From this screen you can configure an <em class="firstterm">iSCSI</em> (SCSI over TCP/IP) target or <em class="firstterm">FCoE</em> (Fibre channel over ethernet) <em class="firstterm">SAN</em> (storage area network). Refer to <a class="xref" href="#ISCSI_disks">Appendix B, <em>ISCSI disks</em></a> for an introduction to iSCSI.
</div><div class="figure" xml:lang="en-US" lang="en-US"><div class="figure-contents"><div class="mediaobject"><img src="images/diskpartadvanced/advanced_storage.png" alt="Advanced Storage Options" /><div class="longdesc"><div class="para">
Advanced Storage Options.
@@ -1380,7 +1384,7 @@ APPEND ksdevice=bootif</pre><div class="para">
Configure FCoE Parameters
</div></div></div></div><h6>Figure 9.21. 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></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" id="sn-Netconfig-x86">9.5. Setting the Hostname</h2></div></div></div><a id="id887568" class="indexterm"></a><a id="id969278" class="indexterm"></a><a id="id617733" class="indexterm"></a><a id="id889529" class="indexterm"></a><a id="id591150" 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" id="sn-Netconfig-x86">9.5. Setting the Hostname</h2></div></div></div><a id="id858966" class="indexterm"></a><a id="id564027" class="indexterm"></a><a id="id515544" class="indexterm"></a><a id="id549234" class="indexterm"></a><a id="id595024" class="indexterm"></a><div class="para">
Setup prompts you to supply a host name for this computer, either as a <em class="firstterm">fully-qualified domain name</em> (FQDN) in the format <em class="replaceable"><code>hostname</code></em>.<em class="replaceable"><code>domainname</code></em> or as a <em class="firstterm">short host name</em> in the format <em class="replaceable"><code>hostname</code></em>. Many networks have a <em class="firstterm">Dynamic Host Configuration Protocol</em> (DHCP) service that automatically supplies connected systems with a domain name. To allow the DHCP service to assign the domain name to this machine, specify the short host name only.
</div><div class="note" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Valid Hostnames</h2></div><div class="admonition"><div class="para">
You may give your system any name provided that the full hostname is unique. The hostname may include letters, numbers and hyphens.
@@ -1406,7 +1410,7 @@ APPEND ksdevice=bootif</pre><div class="para">
To add a new connection or to modify or remove a connection configured earlier in the installation process, click the tab that corresponds to the type of connection. To add a new connection of that type, click <span class="guibutton"><strong>Add</strong></span>. To modify an existing connection, select it in the list and click <span class="guibutton"><strong>Edit</strong></span>. In either case, a dialog box appears with a set of tabs that is appropriate to the particular connection type, as described below. To remove a connection, select it in the list and click <span class="guibutton"><strong>Delete</strong></span>.
</div><div class="para">
When you have finished editing network settings, click <span class="guibutton"><strong>Apply</strong></span> to save the new configuration. If you reconfigured a device that was already active during installation, you must restart the device to use the new configuration — refer to <a class="xref" href="#restart-network-device-x86">Section 9.5.1.6, “Restart a network device”</a>.
- </div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id544062">9.5.1.1. Options common to all types of connection</h4></div></div></div><div class="para">
+ </div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id590991">9.5.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.
@@ -1414,11 +1418,11 @@ APPEND ksdevice=bootif</pre><div class="para">
Select <span class="guilabel"><strong>Start automatically</strong></span> to start the connection automatically when the system boots.
</div><div class="para">
When <span class="application"><strong>NetworkManager</strong></span> runs on an installed system, the <span class="guilabel"><strong>Available to all users</strong></span> option controls whether a network configuration is available system-wide or not. During installation, ensure that <span class="guilabel"><strong>Available to all users</strong></span> remains selected for any network interface that you configure.
-</div></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id658071">9.5.1.2. The Wired tab</h4></div></div></div><div class="para">
+</div></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id508573">9.5.1.2. The Wired tab</h4></div></div></div><div class="para">
Use the <span class="guilabel"><strong>Wired</strong></span> tab to specify or change the <em class="firstterm">media access control</em> (MAC) address for the network adapter, and either set the <em class="firstterm">maximum transmission unit</em> (MTU, in bytes) that can pass through the interface.
</div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/netconfig/network-connections-wired.png" width="444" alt="The Wired tab" /><div class="longdesc"><div class="para">
The Wired tab
- </div></div></div></div><h6>Figure 9.24. The Wired tab</h6></div><br class="figure-break" /></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id807283">9.5.1.3. The 802.1x Security tab</h4></div></div></div><div class="para">
+ </div></div></div></div><h6>Figure 9.24. The Wired tab</h6></div><br class="figure-break" /></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id692137">9.5.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><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:
@@ -1440,7 +1444,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.25. The 802.1x Security tab</h6></div><br class="figure-break" /></div><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id693553">9.5.1.4. The IPv4 Settings tab</h4></div></div></div><div class="para">
+ </div></div></div></div><h6>Figure 9.25. The 802.1x Security tab</h6></div><br class="figure-break" /></div><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id800590">9.5.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:
@@ -1464,7 +1468,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.26. The IPv4 Settings tab</h6></div><br class="figure-break" /><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="id972882">9.5.1.4.1. Editing IPv4 routes</h5></div></div></div><div class="para">
+ </div></div></div></div><h6>Figure 9.26. The IPv4 Settings tab</h6></div><br class="figure-break" /><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="id458832">9.5.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
@@ -1474,7 +1478,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.
- </div></div></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id918888">9.5.1.5. The IPv6 Settings tab</h4></div></div></div><div class="para">
+ </div></div></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id1292389">9.5.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:
@@ -1498,7 +1502,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.28. The IPv6 Settings tab</h6></div><br class="figure-break" /><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="id620804">9.5.1.5.1. Editing IPv6 routes</h5></div></div></div><div class="para">
+ </div></div></div></div><h6>Figure 9.28. The IPv6 Settings tab</h6></div><br class="figure-break" /><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="id550220">9.5.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
@@ -1528,7 +1532,7 @@ APPEND ksdevice=bootif</pre><div class="para">
The device is now reconnected in <span class="application"><strong>anaconda</strong></span>.
</div></li><li class="step"><div class="para">
Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F6</strong></span> to return to <span class="application"><strong>anaconda</strong></span>.
- </div></li></ol></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" id="s1-timezone-x86">9.6. Time Zone Configuration</h2></div></div></div><a id="id514296" class="indexterm"></a><a id="id918820" class="indexterm"></a><a id="id711189" class="indexterm"></a><a id="id587382" class="indexterm"></a><a id="id751098" class="indexterm"></a><a id="id643048" class="indexterm"></a><a id="id695722" class="indexterm"></a><div class="para">
+ </div></li></ol></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" id="s1-timezone-x86">9.6. Time Zone Configuration</h2></div></div></div><a id="id993723" class="indexterm"></a><a id="id755496" class="indexterm"></a><a id="id742663" class="indexterm"></a><a id="id528502" class="indexterm"></a><a id="id628742" class="indexterm"></a><a id="id669610" class="indexterm"></a><a id="id626867" class="indexterm"></a><div class="para">
Set your time zone by selecting the city closest to your computer's physical location. Click on the map to zoom in to a particular geographical region of the world.
</div><div class="para">
Specify a time zone even if you plan to use NTP (Network Time Protocol) to maintain the accuracy of the system clock.
@@ -1552,7 +1556,7 @@ APPEND ksdevice=bootif</pre><div class="para">
Type the <code class="command">system-config-date</code> command in a shell prompt to launch the <span class="application"><strong>Time and Date Properties Tool</strong></span>. If you are not root, it prompts you for the root password to continue.
</div><div class="para">
To run the <span class="application"><strong>Time and Date Properties Tool</strong></span> as a text-based application, use the command <code class="command">timeconfig</code>.
- </div></div></div></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"><h2 class="title" id="sn-account_configuration-x86">9.7. Set the Root Password</h2></div></div></div><a id="id887811" class="indexterm"></a><a id="id754286" class="indexterm"></a><div class="para">
+ </div></div></div></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"><h2 class="title" id="sn-account_configuration-x86">9.7. Set the Root Password</h2></div></div></div><a id="id589974" class="indexterm"></a><a id="id1012654" 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.
@@ -1563,7 +1567,7 @@ APPEND ksdevice=bootif</pre><div class="para">
</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 prompts you to set a root password<sup>[<a id="id687036" href="#ftn.id687036" class="footnote">2</a>]</sup> for your system. <span class="emphasis"><em>. You cannot proceed to the next stage of the installation process without entering a root password.</em></span>
+ The installation program prompts you to set a root password<sup>[<a id="id857612" href="#ftn.id857612" class="footnote">2</a>]</sup> for your system. <span class="emphasis"><em>. You cannot proceed to the next stage of the installation process 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">
@@ -1590,13 +1594,13 @@ APPEND ksdevice=bootif</pre><div class="para">
Move a device from one list to the other by clicking on the device, then clicking either the button labeled with a left-pointing arrow to move it to the list of data storage devices or the button labeled with a right-pointing arrow to move it to the list of devices available for installation of the operating system.
</div><div class="para">
The list of devices available as installation targets also includes a radio button beside each device. Use this radio button to specify the device that you want to use as the boot device for the system.
-</div><div class="important"><div class="admonition_header"><h2>Important — chain loading</h2></div><div class="admonition"><a id="id781777" class="indexterm"></a><div class="para">
+</div><div class="important"><div class="admonition_header"><h2>Important — chain loading</h2></div><div class="admonition"><a id="id700054" class="indexterm"></a><div class="para">
If any storage device contains a boot loader that will chain load the Fedora boot loader, include that storage device among the <span class="guilabel"><strong>Install Target Devices</strong></span>. Storage devices that you identify as <span class="guilabel"><strong>Install Target Devices</strong></span> remain visible to <span class="application"><strong>anaconda</strong></span> during boot loader configuration.
</div><div class="para">
Storage devices that you identify as <span class="guilabel"><strong>Install Target Devices</strong></span> on this screen are not automatically erased by the installation process unless you selected the <span class="guilabel"><strong>Use All Space</strong></span> option on the partitioning screen (refer to <a class="xref" href="#s1-diskpartsetup-x86">Section 9.11, “Disk Partitioning Setup”</a>).
</div></div></div><div class="para">
When you have finished identifying devices to be used for installation, click <span class="guibutton"><strong>Next</strong></span> to continue.
-</div></div><div xml:lang="en-US" class="section" id="sn-initialize-hdd-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sn-initialize-hdd-x86">9.9. Initializing the Hard Disk</h2></div></div></div><a id="id563929" class="indexterm"></a><div class="para">
+</div></div><div xml:lang="en-US" class="section" id="sn-initialize-hdd-x86" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sn-initialize-hdd-x86">9.9. Initializing the Hard Disk</h2></div></div></div><a id="id849777" class="indexterm"></a><div class="para">
If no readable partition tables are found on existing hard disks, the installation program asks to initialize the hard disk. This operation makes any existing data on the hard disk unreadable. If your system has a brand new hard disk with no operating system installed, or you have removed all partitions on the hard disk, click <span class="guibutton"><strong>Re-initialize drive</strong></span>.
</div><div class="para">
The installation program presents you with a separate dialog for each disk on which it cannot read a valid partition table. Click the <span class="guibutton"><strong>Ignore all</strong></span> button or <span class="guibutton"><strong>Re-initialize all</strong></span> button to apply the same answer to all devices.
@@ -1635,7 +1639,7 @@ APPEND ksdevice=bootif</pre><div class="para">
Note that the above examples store backup materials in a <code class="filename">/home</code> directory. If your <code class="filename">/home</code> directory is not a separate partition, <span class="emphasis"><em>you should not follow these examples verbatim!</em></span> Store your backups on another device such as CD or DVD discs or an external hard disk.
</div></div></div><div class="para">
For more information on completing the upgrade process later, refer to <a class="xref" href="#sn-finishing-upgrade">Section 18.2, “Finishing an Upgrade”</a>.
-</div></div><div class="section" id="sn-upgrading-bootloader-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sn-upgrading-bootloader-x86">9.10.3. Upgrading Boot Loader Configuration </h3></div></div></div><a id="id770751" class="indexterm"></a><a id="id573132" class="indexterm"></a><div class="para">
+</div></div><div class="section" id="sn-upgrading-bootloader-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sn-upgrading-bootloader-x86">9.10.3. Upgrading Boot Loader Configuration </h3></div></div></div><a id="id1481973" class="indexterm"></a><a id="id762153" class="indexterm"></a><div class="para">
Your completed Fedora installation must be registered in the <em class="firstterm">boot loader</em> to boot properly. A boot loader is software on your machine that locates and starts the operating system. Refer to <a class="xref" href="#ch-grub">Appendix E, <em>The GRUB Boot Loader</em></a> for more information about boot loaders.
</div><div class="figure" xml:lang="en-US" lang="en-US"><div class="figure-contents"><div class="mediaobject"><img src="images/upgrading/upgradebootloader.png" width="444" alt="The Upgrade Boot Loader Dialog" /><div class="longdesc"><div class="para">
The dialog includes three radio buttons, labeled <span class="guilabel"><strong>Update boot loader configuration</strong></span>, <span class="guilabel"><strong>Skip boot loader updating</strong></span>, and <span class="guilabel"><strong>Create new boot loader configuration</strong></span>
@@ -1647,7 +1651,7 @@ APPEND ksdevice=bootif</pre><div class="para">
Install a new boot loader as part of an upgrade process only if you are certain you want to replace the existing boot loader. If you install a new boot loader, you may not be able to boot other operating systems on the same machine until you have configured the new boot loader. Select <span class="guilabel"><strong>Create new boot loader configuration</strong></span> to remove the existing boot loader and install GRUB.
</div><div class="para">
After you make your selection, click <span class="guibutton"><strong>Next</strong></span> to continue. If you selected the <span class="guilabel"><strong>Create new boot loader configuration</strong></span> option, refer to <a class="xref" href="#s1-x86-bootloader">Section 9.15, “x86, AMD64, and Intel 64 Boot Loader Configuration”</a>. If you chose to update or skip boot loader configuration, installation continues without further input from you.
- </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" id="s1-diskpartsetup-x86">9.11. Disk Partitioning Setup</h2></div></div></div><a id="id672620" class="indexterm"></a><a id="id855364" class="indexterm"></a><a id="id992850" class="indexterm"></a><a id="id554842" 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" id="s1-diskpartsetup-x86">9.11. Disk Partitioning Setup</h2></div></div></div><a id="id762981" class="indexterm"></a><a id="id599151" class="indexterm"></a><a id="id605358" class="indexterm"></a><a id="id978957" 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.
@@ -1693,9 +1697,9 @@ APPEND ksdevice=bootif</pre><div class="para">
Select <span class="guilabel"><strong>Encrypt system</strong></span> to encrypt all partitions except the <code class="filename">/boot</code> partition. Refer to <a class="xref" href="#Disk_Encryption_Guide">Appendix C, <em>Disk Encryption</em></a> for information on encryption.
</div><div class="para">
To review and make any necessary changes to the partitions created by automatic partitioning, select the <span class="guilabel"><strong>Review</strong></span> option. After selecting <span class="guilabel"><strong>Review</strong></span> and clicking <span class="guibutton"><strong>Next</strong></span> to move forward, the partitions created for you by <span class="application"><strong>anaconda</strong></span> appear. You can make modifications to these partitions if they do not meet your needs.
-</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="id780098" class="indexterm"></a><div class="para">
+</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="id901757" 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. If you chose any of the automatic partitioning options, you must now select the <span class="guilabel"><strong>Review and modify partitioning layout</strong></span> option before you click <span class="guibutton"><strong>Next</strong></span> or you cannot specify the correct 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="id851156" class="indexterm"></a><div class="para">
+ </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="id716482" 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 disk selection screen that appears after selecting automatic partitioning. Alternatively, select custom partitioning.
@@ -1713,7 +1717,7 @@ APPEND ksdevice=bootif</pre><div class="para">
If you lose this passphrase, any encrypted partitions and the data on them will become completely inaccessible. There is no way to recover a lost passphrase.
</div><div class="para">
Note that if you perform a kickstart installation of Fedora, you can save encryption passphrases and create backup encryption passphrases during installation. Refer to <a class="xref" href="#Disk_Encryption_Guide-Saving_Passphrases">Section C.3.2, “Saving Passphrases”</a> and <a class="xref" href="#Disk_Encryption_Guide-Creating_and_Saving_Backup_Passphrases">Section C.3.3, “Creating and Saving Backup Passphrases”</a>.
- </div></div></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" id="s1-diskpartitioning-x86">9.13. Creating a Custom Layout or Modifying the Default Layout </h2></div></div></div><a id="id642231" class="indexterm"></a><a id="id695630" class="indexterm"></a><a id="id740406" class="indexterm"></a><div class="para">
+ </div></div></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" id="s1-diskpartitioning-x86">9.13. Creating a Custom Layout or Modifying the Default Layout </h2></div></div></div><a id="id1318940" class="indexterm"></a><a id="id1297228" class="indexterm"></a><a id="id547960" class="indexterm"></a><div class="para">
If you chose one of the four automatic partitioning options and did not select <span class="guilabel"><strong>Review</strong></span>, skip ahead to <a class="xref" href="#s1-pkgselection-x86">Section 9.16, “Package Group Selection”</a>.
</div><div class="para">
If you chose one of the automatic partitioning options and selected <span class="guilabel"><strong>Review</strong></span>, you can either accept the current partition settings (click <span class="guibutton"><strong>Next</strong></span>), or modify the setup manually in the partitioning screen.
@@ -1787,7 +1791,7 @@ APPEND ksdevice=bootif</pre><div class="para">
<span class="guilabel"><strong>LVM Volume Group</strong></span> — create a <em class="firstterm">volume group</em> from one or more physical volumes. This option is only available when at least one physical volume is available on the system.
</div></li><li xml:lang="en-US" class="listitem" lang="en-US"><div class="para">
<span class="guilabel"><strong>LVM Logical Volume</strong></span> — create a <em class="firstterm">logical volume</em> on a volume group. This option is only available when at least one volume group is available on the system.
- </div></li></ul></div></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" id="Adding_Partitions-x86">9.13.2. Adding Partitions</h3></div></div></div><a id="id1344181" class="indexterm"></a><a id="id687821" class="indexterm"></a><a id="id637714" class="indexterm"></a><div class="para">
+ </div></li></ul></div></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" id="Adding_Partitions-x86">9.13.2. Adding Partitions</h3></div></div></div><a id="id1346593" class="indexterm"></a><a id="id685734" class="indexterm"></a><a id="id793103" class="indexterm"></a><div class="para">
To add a new partition, select the <span class="guibutton"><strong>Create</strong></span> button. A dialog box appears (refer to <a class="xref" href="#fig-diskpartitioning-part-add-x86">Figure 9.40, “Creating a New Partition”</a>).
</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
You must dedicate at least one partition for this installation, and optionally more. For more information, refer to <a class="xref" href="#ch-partitions-x86">Appendix A, <em>An Introduction to Disk Partitions</em></a>.
@@ -1813,7 +1817,7 @@ APPEND ksdevice=bootif</pre><div class="para">
<span class="guibutton"><strong>OK</strong></span>: Select <span class="guibutton"><strong>OK</strong></span> once you are satisfied with the settings and wish to create the partition.
</div></li><li xml:lang="en-US" class="listitem" lang="en-US"><div class="para">
<span class="guibutton"><strong>Cancel</strong></span>: Select <span class="guibutton"><strong>Cancel</strong></span> if you do not want to create the partition.
- </div></li></ul></div><div class="section" id="s3-diskpartitioning-file-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-diskpartitioning-file-x86">9.13.2.1. File System Types</h4></div></div></div><a id="id845330" class="indexterm"></a><a id="id635082" class="indexterm"></a><a id="id567602" class="indexterm"></a><a id="id691719" class="indexterm"></a><div class="para">
+ </div></li></ul></div><div class="section" id="s3-diskpartitioning-file-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-diskpartitioning-file-x86">9.13.2.1. File System Types</h4></div></div></div><a id="id1422771" class="indexterm"></a><a id="id684898" class="indexterm"></a><a id="id968240" class="indexterm"></a><a id="id1311418" 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.
@@ -1826,7 +1830,7 @@ APPEND ksdevice=bootif</pre><div class="para">
</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> <sup>[<a id="id698750" href="#ftn.id698750" class="footnote">3</a>]</sup> 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> <sup>[<a id="id839110" href="#ftn.id839110" class="footnote">3</a>]</sup> 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">
@@ -1895,7 +1899,7 @@ APPEND ksdevice=bootif</pre><div class="para">
Choose this option to create an LVM logical volume. Select a mount point, file system type, and size (in MB) just as if it were a standard disk partition. You can also choose a name for the logical volume and specify the volume group to which it will belong.
</div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/diskpartitioning/lvm-lv.png" alt="Make Logical Volume" /><div class="longdesc"><div class="para">
The Make Logical Volume dialog.
- </div></div></div></div><h6>Figure 9.45. Make Logical Volume</h6></div><br class="figure-break" /></dd></dl></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" id="s2-diskpartrecommend-x86">9.13.5. Recommended Partitioning Scheme</h3></div></div></div><a id="id570089" class="indexterm"></a><a id="id529775" class="indexterm"></a><a id="id1110025" class="indexterm"></a><a id="id734551" class="indexterm"></a><a id="id673156" class="indexterm"></a><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id688091">9.13.5.1. x86, AMD64, and Intel 64 systems</h4></div></div></div><div class="para">
+ </div></div></div></div><h6>Figure 9.45. Make Logical Volume</h6></div><br class="figure-break" /></dd></dl></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" id="s2-diskpartrecommend-x86">9.13.5. Recommended Partitioning Scheme</h3></div></div></div><a id="id737206" class="indexterm"></a><a id="id621893" class="indexterm"></a><a id="id523880" class="indexterm"></a><a id="id841585" class="indexterm"></a><a id="id696941" class="indexterm"></a><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id829651">9.13.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
@@ -1939,7 +1943,7 @@ APPEND ksdevice=bootif</pre><div class="para">
a minimum of 32GB of swap space
</td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
Note that you can obtain better performance by distributing swap space over multiple storage devices, particularly on systems with fast drives, controllers, and interfaces.
- </div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="id956399">A <code class="filename">/boot/</code> partition (250 MB)</h5>
+ </div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="id805980">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><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important — Supported file systems</h2></div><div class="admonition"><div class="para">
The <span class="application"><strong>GRUB</strong></span> bootloader in Fedora 16 supports only the ext2, ext3, and ext4 (recommended) file systems. You cannot use any other file system for <code class="filename">/boot</code>, such as Btrfs, XFS, or VFAT.
@@ -1947,13 +1951,13 @@ APPEND ksdevice=bootif</pre><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="id526831">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="id613286">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.
</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="id661848">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="id902526">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.13.5.1.1, “Advice on Partitions”</a> for more information.
@@ -2069,12 +2073,12 @@ APPEND ksdevice=bootif</pre><div class="para">
To revise any of the choices that you made up to this point, click <span class="guibutton"><strong>Go back</strong></span>. To cancel installation completely, switch off your computer. To switch off most computers at this stage, press the power button and hold it down for a few seconds.
</div><div class="para">
After you click <span class="guibutton"><strong>Write changes to disk</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-x86-bootloader" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-x86-bootloader">9.15. x86, AMD64, and Intel 64 Boot Loader Configuration</h2></div></div></div><a id="id765770" class="indexterm"></a><a id="id596009" class="indexterm"></a><a id="id592289" class="indexterm"></a><a id="id529729" class="indexterm"></a><a id="id554989" class="indexterm"></a><a id="id817523" class="indexterm"></a><a id="id692172" class="indexterm"></a><div class="para">
+</div></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"><h2 class="title" id="s1-x86-bootloader">9.15. x86, AMD64, and Intel 64 Boot Loader Configuration</h2></div></div></div><a id="id714338" class="indexterm"></a><a id="id779506" class="indexterm"></a><a id="id939353" class="indexterm"></a><a id="id564700" class="indexterm"></a><a id="id968251" class="indexterm"></a><a id="id870307" class="indexterm"></a><a id="id647916" 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="important"><div class="admonition_header"><h2>Installing in text mode</h2></div><div class="admonition"><div class="para">
If you install Fedora in text mode, the installer configures the bootloader automatically and you cannot customize bootloader settings during the installation process.
</div></div></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 16 uses GRUB 2. GRUB Legacy is no longer actively developed.<sup>[<a id="id564841" href="#ftn.id564841" class="footnote">4</a>]</sup>
+ 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 16 uses GRUB 2. GRUB Legacy is no longer actively developed.<sup>[<a id="id954308" href="#ftn.id954308" class="footnote">4</a>]</sup>
</div><div class="note"><div class="admonition_header"><h2>The GRUB boot menu</h2></div><div class="admonition"><div class="para">
The GRUB menu defaults to being hidden, except on dual-boot systems. To show the GRUB menu during system boot, press and hold the <span class="keycap"><strong>Shift</strong></span> key before the kernel is loaded. (Any other key works as well but the <span class="keycap"><strong>Shift</strong></span> key is the safest to use.)
</div></div></div><div class="figure" id="fig-x86-bootloader"><div class="figure-contents"><div class="mediaobject"><img src="images/x86-bootloader/x86-bootloader.png" width="444" alt="Boot Loader Configuration" /><div class="longdesc"><div class="para">
@@ -2111,7 +2115,7 @@ APPEND ksdevice=bootif</pre><div class="para">
Boot loader passwords provide a security mechanism in an environment where physical access to your server is available.
</div><div class="para">
If you are installing a boot loader, you should create a password to protect your system. Without a boot loader password, users with access to your system can pass options to the kernel which can compromise your system security. With a boot loader password in place, the password must first be entered before selecting any non-standard boot options. However, it is still possible for someone with physical access to the machine to boot from a diskette, CD-ROM, DVD, or USB media if the BIOS supports it. Security plans which include boot loader passwords should also address alternate boot methods.
- </div><a id="id779695" class="indexterm"></a><a id="id770466" class="indexterm"></a><a id="id553118" class="indexterm"></a><div class="note"><div class="admonition_header"><h2>GRUB Passwords Not Required</h2></div><div class="admonition"><div class="para">
+ </div><a id="id792558" class="indexterm"></a><a id="id591041" class="indexterm"></a><a id="id524261" class="indexterm"></a><div class="note"><div class="admonition_header"><h2>GRUB Passwords Not Required</h2></div><div class="admonition"><div class="para">
You may not require a <span class="application"><strong>GRUB</strong></span> password if your system only has trusted operators, or is physically secured with controlled console access. However, if an untrusted person can get physical access to your computer's keyboard and monitor, that person can reboot the system and access <span class="application"><strong>GRUB</strong></span>. A password is helpful in this case.
</div></div></div><div class="para">
If you choose to use a boot loader password to enhance your system security, be sure to select the checkbox labeled <span class="guilabel"><strong>Use a boot loader password</strong></span>.
@@ -2125,12 +2129,12 @@ APPEND ksdevice=bootif</pre><div class="para">
When selecting a GRUB password, be aware that GRUB recognizes only the QWERTY keyboard layout, regardless of the keyboard actually attached to the system. If you use a keyboard with a significantly different layout, it might be more effective to memorize a pattern of keystrokes rather than the word that the pattern produces.
</div></div></div><div class="para">
To configure more advanced boot loader options, such as changing the drive order or passing options to the kernel, be sure <span class="guilabel"><strong>Configure advanced boot loader options</strong></span> is selected before clicking <span class="guibutton"><strong>Next</strong></span>.
- </div><div class="section" id="x86-bootloader-adv"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="x86-bootloader-adv">9.15.1. Advanced Boot Loader Configuration</h3></div></div></div><a id="id659258" class="indexterm"></a><a id="id522301" class="indexterm"></a><a id="id1395376" class="indexterm"></a><a id="id776658" class="indexterm"></a><div class="para">
+ </div><div class="section" id="x86-bootloader-adv"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="x86-bootloader-adv">9.15.1. Advanced Boot Loader Configuration</h3></div></div></div><a id="id843480" class="indexterm"></a><a id="id525729" class="indexterm"></a><a id="id509601" class="indexterm"></a><a id="id522583" class="indexterm"></a><div class="para">
Now that you have chosen which boot loader to install, you can also determine where you want the boot loader to be installed. You may install the boot loader in one of two places:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
The master boot record (MBR) — This is the recommended place to install a boot loader, unless the MBR already starts another operating system loader, such as System Commander. The MBR is a special area on your hard drive that is automatically loaded by your computer's BIOS, and is the earliest point at which the boot loader can take control of the boot process. If you install it in the MBR, when your machine boots, GRUB presents a boot prompt. You can then boot Fedora or any other operating system that you have configured the boot loader to boot.
</div></li><li class="listitem"><div class="para">
- <a id="id569396" class="indexterm"></a>
+ <a id="id1423767" class="indexterm"></a>
The first sector of your boot partition — This is recommended if you are already using another boot loader on your system. In this case, your other boot loader takes control first. You can then configure that boot loader to start GRUB, which then boots Fedora.
</div><div class="note"><div class="admonition_header"><h2>GRUB as a Secondary Boot Loader</h2></div><div class="admonition"><div class="para">
If you install GRUB as a secondary boot loader, you must reconfigure your primary boot loader whenever you install and boot from a new kernel. The kernel of an operating system such as Microsoft Windows does not boot in the same fashion. Most users therefore use GRUB as the primary boot loader on dual-boot systems.
@@ -2149,17 +2153,17 @@ 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><div class="section" id="s2-x86-bootloader-rescue"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-x86-bootloader-rescue">9.15.2. Rescue Mode</h3></div></div></div><a id="id901565" 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><div class="section" id="s2-x86-bootloader-rescue"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-x86-bootloader-rescue">9.15.2. Rescue Mode</h3></div></div></div><a id="id600615" class="indexterm"></a><div class="para">
Rescue mode provides the ability to boot a small Fedora environment entirely from boot media or some other boot method instead of the system's hard drive. There may be times when you are unable to get Fedora running completely enough to access files on your system's hard drive. Using rescue mode, you can access the files stored on your system's hard drive, even if you cannot actually run Fedora from that hard drive. If you need to use rescue mode, try the following method:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
Boot an x86, AMD64, or Intel 64 system from any installation medium, such as CD, DVD, USB, or PXE, and type <strong class="userinput"><code>linux rescue</code></strong> at the installation boot prompt. Refer to <a class="xref" href="#ap-rescuemode">Chapter 19, <em>Basic System Recovery</em></a> for a more complete description of rescue mode.
</div></li></ul></div><div class="para">
For additional information, refer to the <em class="citetitle">Fedora Deployment Guide</em>.
- </div></div><div class="section" id="s2-x86-bootloader-alt"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-x86-bootloader-alt">9.15.3. Alternative Boot Loaders</h3></div></div></div><a id="id797670" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-x86-bootloader-alt"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-x86-bootloader-alt">9.15.3. Alternative Boot Loaders</h3></div></div></div><a id="id728669" 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.
- </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" id="s1-pkgselection-x86">9.16. Package Group Selection</h2></div></div></div><a id="id1042822" class="indexterm"></a><a id="id573691" class="indexterm"></a><a id="id592275" class="indexterm"></a><a id="id697800" class="indexterm"></a><a id="id573770" class="indexterm"></a><a id="id1042881" class="indexterm"></a><div class="para">
+ </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" id="s1-pkgselection-x86">9.16. Package Group Selection</h2></div></div></div><a id="id845229" class="indexterm"></a><a id="id921201" class="indexterm"></a><a id="id511518" class="indexterm"></a><a id="id688895" class="indexterm"></a><a id="id594178" class="indexterm"></a><a id="id651932" class="indexterm"></a><div class="para">
Now that you have made most of the choices for your installation, you are ready to confirm the default package selection or customize packages for your system.
</div><div class="para">
The <span class="guilabel"><strong>Package Installation Defaults</strong></span> screen appears and details the default package set for your Fedora installation. This screen varies depending on the version of Fedora you are installing.
@@ -2183,7 +2187,7 @@ APPEND ksdevice=bootif</pre><div class="para">
To select a component, click on the checkbox beside it (refer to <a class="xref" href="#fig-pkgselection-group-x86">Figure 9.49, “Package Group Selection”</a>).
</div><div class="para">
To customize your package set further, select the <span class="guilabel"><strong>Customize now</strong></span> option on the screen. Clicking <span class="guibutton"><strong>Next</strong></span> takes you to the <span class="guilabel"><strong>Package Group Selection</strong></span> screen.
-</div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id1266148">9.16.1. Installing from Additional Repositories</h3></div></div></div><div class="para">
+</div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id513788">9.16.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="para">
The basic options are:
@@ -2235,7 +2239,7 @@ APPEND ksdevice=bootif</pre><div class="para">
Choose to add or remove optional packages from this package group.
</div></div></div></div><h6>Figure 9.53. Package Group Details</h6></div><br class="figure-break" /><div class="para">
Fedora divides the included software into
- <a id="id655338" class="indexterm"></a>
+ <a id="id490747" class="indexterm"></a>
<em class="firstterm">package groups</em>. For ease of use, the package selection screen displays these groups as categories.
</div><div class="para">
You can select package groups, which group components together according to function (for example, <span class="guilabel"><strong>X Window System</strong></span> and <span class="guilabel"><strong>Editors</strong></span>), individual packages, or a combination of the two.
@@ -2288,8 +2292,8 @@ APPEND ksdevice=bootif</pre><div class="para">
</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" width="444" alt="Packages completed" /><div class="longdesc"><div class="para">
The Packages Completed progress bar
</div></div></div></div><h6>Figure 9.56. Packages completed</h6></div><br class="figure-break" /><div class="para">
- <a id="id567641" class="indexterm"></a>
- <a id="id665436" class="indexterm"></a>
+ <a id="id751036" class="indexterm"></a>
+ <a id="id696060" 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">
After installation completes, select <span class="guibutton"><strong>Reboot</strong></span> to restart your computer. Fedora ejects any loaded discs before the computer reboots.
@@ -2301,13 +2305,13 @@ APPEND ksdevice=bootif</pre><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.
</div><div class="para">
The first time you start your Fedora system in run level 5 (the graphical run level), the <span class="application"><strong>FirstBoot</strong></span> tool appears, which guides you through the Fedora configuration. Using this tool, you can set your system time and date, install software, configure your machine to receive software updates, and more. <span class="application"><strong>FirstBoot</strong></span> lets you configure your environment at the beginning, so that you can get started using your Fedora system quickly.
-</div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><div class="para"><sup>[<a id="ftn.id687036" href="#id687036" class="para">2</a>] </sup>
+</div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><div class="para"><sup>[<a id="ftn.id857612" href="#id857612" class="para">2</a>] </sup>
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 class="footnote"><div class="para"><sup>[<a id="ftn.id698750" href="#id698750" class="para">3</a>] </sup>
+ </div></div><div class="footnote"><div class="para"><sup>[<a id="ftn.id839110" href="#id839110" class="para">3</a>] </sup>
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 class="footnote"><div class="para"><sup>[<a id="ftn.id564841" href="#id564841" class="para">4</a>] </sup>
+ </div></div><div class="footnote"><div class="para"><sup>[<a id="ftn.id954308" href="#id954308" class="para">4</a>] </sup>
<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></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><dt><span class="section"><a href="#id693508">10.1. You are unable to boot Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="#id844055">10.1.1. Are You Unable to Boot With Your RAID Card?</a></span></dt><dt><span class="section"><a href="#id663989">10.1.2. Is Your System Displaying Signal 11 Errors?</a></span></dt></dl></dd><dt><span class="section"><a href="#id666318">10.2. Trouble Beginning the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#id1432449">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="sectio
n"><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. Saving 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="#id908960">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="#Trouble_After_Booting-GUI">10.4.2. Booting into a Graphical Environment</a></span></dt><dt><span cla
ss="section"><a href="#id540116">10.4.3. Problems with the X Window System (GUI)</a></span></dt><dt><span class="section"><a href="#id970287">10.4.4. Problems with the X Server Crashing and Non-Root Users</a></span></dt><dt><span class="section"><a href="#id656508">10.4.5. Problems When You Try to Log In</a></span></dt><dt><span class="section"><a href="#s2-trouble-ram">10.4.6. Is Your RAM Not Being Recognized?</a></span></dt><dt><span class="section"><a href="#id1001590">10.4.7. Your Printer Does Not Work</a></span></dt><dt><span class="section"><a href="#id618256">10.4.8. Apache HTTP Server or Sendmail stops responding during startup</a></span></dt></dl></dd></dl></div><a id="id868750" class="indexterm"></a><a id="id575098" class="indexterm"></a><a id="id527408" class="indexterm"></a><a id="id531539" class="indexterm"></a><a id="id828554" class="indexterm"></a><a id="id780528" class="indexterm"></a><a id="id517471" class="indexterm"></a><a id="id586094" 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><dt><span class="section"><a href="#id705731">10.1. You are unable to boot Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="#id809826">10.1.1. Are You Unable to Boot With Your RAID Card?</a></span></dt><dt><span class="section"><a href="#id595519">10.1.2. Is Your System Displaying Signal 11 Errors?</a></span></dt></dl></dd><dt><span class="section"><a href="#id709919">10.2. Trouble Beginning the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#id560395">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. Saving 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="#id889363">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="#Trouble_After_Booting-GUI">10.4.2. Booting into a Graphical Environment</a></span></dt><dt><span clas
s="section"><a href="#id746602">10.4.3. Problems with the X Window System (GUI)</a></span></dt><dt><span class="section"><a href="#id532309">10.4.4. Problems with the X Server Crashing and Non-Root Users</a></span></dt><dt><span class="section"><a href="#id646088">10.4.5. Problems When You Try to Log In</a></span></dt><dt><span class="section"><a href="#s2-trouble-ram">10.4.6. Is Your RAM Not Being Recognized?</a></span></dt><dt><span class="section"><a href="#id615608">10.4.7. Your Printer Does Not Work</a></span></dt><dt><span class="section"><a href="#id762738">10.4.8. Apache HTTP Server or Sendmail stops responding during startup</a></span></dt></dl></dd></dl></div><a id="id470129" class="indexterm"></a><a id="id992484" class="indexterm"></a><a id="id552017" class="indexterm"></a><a id="id627386" class="indexterm"></a><a id="id592543" class="indexterm"></a><a id="id907026" class="indexterm"></a><a id="id486596" class="indexterm"></a><a id="id1399082" 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:
@@ -2325,7 +2329,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"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id693508">10.1. You are unable to boot Fedora</h2></div></div></div><a id="id499208" class="indexterm"></a><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id844055">10.1.1. Are You Unable to Boot With Your RAID Card?</h3></div></div></div><a id="id524940" class="indexterm"></a><a id="id865516" class="indexterm"></a><div class="para">
+</div><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id705731">10.1. You are unable to boot Fedora</h2></div></div></div><a id="id1344242" class="indexterm"></a><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id809826">10.1.1. Are You Unable to Boot With Your RAID Card?</h3></div></div></div><a id="id484475" class="indexterm"></a><a id="id846247" 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.
@@ -2335,7 +2339,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"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id663989">10.1.2. Is Your System Displaying Signal 11 Errors?</h3></div></div></div><a id="id1321946" class="indexterm"></a><div class="para">
+ </div></div><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id595519">10.1.2. Is Your System Displaying Signal 11 Errors?</h3></div></div></div><a id="id621150" 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.
@@ -2347,15 +2351,15 @@ APPEND ksdevice=bootif</pre><div class="para">
<strong class="userinput"><code>linux mediacheck</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"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id666318">10.2. Trouble Beginning the Installation</h2></div></div></div><a id="id572272" class="indexterm"></a><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id1432449">10.2.1. Problems with Booting into the Graphical Installation</h3></div></div></div><a id="id502184" class="indexterm"></a><a id="id654551" 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"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id709919">10.2. Trouble Beginning the Installation</h2></div></div></div><a id="id846262" class="indexterm"></a><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id560395">10.2.1. Problems with Booting into the Graphical Installation</h3></div></div></div><a id="id927901" class="indexterm"></a><a id="id669116" 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 system with basic video driver</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" id="s1-trouble-install-x86">10.3. Trouble During the Installation</h2></div></div></div><a id="id765741" class="indexterm"></a><div class="section" id="s2-trouble-nodevicefound-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-trouble-nodevicefound-x86">10.3.1. <code class="computeroutput">No devices found to install Fedora </code> Error Message</h3></div></div></div><a id="id763844" 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" id="s1-trouble-install-x86">10.3. Trouble During the Installation</h2></div></div></div><a id="id520407" class="indexterm"></a><div class="section" id="s2-trouble-nodevicefound-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-trouble-nodevicefound-x86">10.3.1. <code class="computeroutput">No devices found to install Fedora </code> Error Message</h3></div></div></div><a id="id733810" 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" id="s2-trouble-tracebacks-x86">10.3.2. Saving traceback messages</h3></div></div></div><a id="id912203" class="indexterm"></a><a id="id633574" class="indexterm"></a><a id="id757399" 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" id="s2-trouble-tracebacks-x86">10.3.2. Saving traceback messages</h3></div></div></div><a id="id608806" class="indexterm"></a><a id="id625520" class="indexterm"></a><a id="id754019" class="indexterm"></a><div class="para">
If <span class="application"><strong>anaconda</strong></span> 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/
@@ -2395,7 +2399,7 @@ APPEND ksdevice=bootif</pre><div class="para">
</div></div></div></div><h6>Figure 10.8. Save Crash Report to Remote Server</h6></div><br class="figure-break" /></dd><dt class="varlistentry"><span class="term">Cancel</span></dt><dd><div class="para">
cancels saving the error report.
</div></dd></dl></div>
-</div></div><div class="section" id="s2-trouble-part-tables-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-trouble-part-tables-x86">10.3.3. Trouble with Partition Tables</h3></div></div></div><a id="id503094" class="indexterm"></a><a id="id627097" class="indexterm"></a><div class="para">
+</div></div><div class="section" id="s2-trouble-part-tables-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-trouble-part-tables-x86">10.3.3. Trouble with Partition Tables</h3></div></div></div><a id="id797102" class="indexterm"></a><a id="id767788" class="indexterm"></a><div class="para">
If you receive an error after the <span class="guilabel"><strong>Disk Partitioning Setup</strong></span> (<a class="xref" href="#s1-diskpartsetup-x86">Section 9.11, “Disk Partitioning Setup”</a>) phase of the installation saying 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.
@@ -2405,11 +2409,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" id="s2-trouble-space-x86">10.3.4. Using Remaining Space</h3></div></div></div><a id="id552514" 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" id="s2-trouble-space-x86">10.3.4. Using Remaining Space</h3></div></div></div><a id="id592741" 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" id="s2-trouble-completeparts-x86">10.3.5. Other Partitioning Problems</h3></div></div></div><a id="id560285" 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" id="s2-trouble-completeparts-x86">10.3.5. Other Partitioning Problems</h3></div></div></div><a id="id598061" class="indexterm"></a><div class="para">
If you create partitions manually, but cannot move to the next screen, 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:
@@ -2419,7 +2423,7 @@ 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"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id908960">10.4. Problems After Installation</h2></div></div></div><a id="id912539" 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" id="s2-trouble-grub">10.4.1. Trouble With the Graphical GRUB Screen on an x86-based System?</h3></div></div></div><a id="id652386" class="indexterm"></a><div class="para">
+ </div></div></div></div></div><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id889363">10.4. Problems After Installation</h2></div></div></div><a id="id728566" 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" id="s2-trouble-grub">10.4.1. Trouble With the Graphical GRUB Screen on an x86-based System?</h3></div></div></div><a id="id508506" class="indexterm"></a><div class="para">
If you are experiencing problems with GRUB, you may need to disable the graphical boot screen. To do this, become the root user and edit the <code class="filename">/boot/grub/grub.conf</code> file.
</div><div class="para">
Within the <code class="filename">grub.conf</code> file, comment out the line which begins with <code class="computeroutput">splashimage</code> by inserting the <code class="computeroutput">#</code> character at the beginning of the line.
@@ -2431,7 +2435,7 @@ APPEND ksdevice=bootif</pre><div class="para">
Once you reboot, the <code class="filename">grub.conf</code> file is reread and any changes you have made take effect.
</div><div class="para">
You may re-enable the graphical boot screen by uncommenting (or adding) the above line back into the <code class="filename">grub.conf</code> file.
- </div></div><div class="section" id="Trouble_After_Booting-GUI"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="Trouble_After_Booting-GUI">10.4.2. Booting into a Graphical Environment</h3></div></div></div><a id="id933623" class="indexterm"></a><a id="id618858" class="indexterm"></a><a id="id545404" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="Trouble_After_Booting-GUI"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="Trouble_After_Booting-GUI">10.4.2. Booting into a Graphical Environment</h3></div></div></div><a id="id514973" class="indexterm"></a><a id="id880679" class="indexterm"></a><a id="id639378" 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.
@@ -2463,7 +2467,7 @@ id:3:initdefault:</pre><div class="para">
When you are satisfied with your change, save and exit the file using the <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Q</strong></span> keys. A window appears and asks if you would like to save the changes. Click <span class="guibutton"><strong>Save</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" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id540116">10.4.3. Problems with the X Window System (GUI)</h3></div></div></div><a id="id569838" class="indexterm"></a><div class="para">
+</div></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id746602">10.4.3. Problems with the X Window System (GUI)</h3></div></div></div><a id="id1013674" 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.
@@ -2471,7 +2475,7 @@ id:3:initdefault:</pre><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 18.3, “Switching to a Graphical Login”</a> for more detail on installing a desktop environment.
- </div></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id970287">10.4.4. Problems with the X Server Crashing and Non-Root Users</h3></div></div></div><a id="id599466" class="indexterm"></a><div class="para">
+ </div></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id532309">10.4.4. Problems with the X Server Crashing and Non-Root Users</h3></div></div></div><a id="id674433" 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:
@@ -2479,7 +2483,7 @@ id:3:initdefault:</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"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id656508">10.4.5. Problems When You Try to Log In</h3></div></div></div><a id="id868227" class="indexterm"></a><div class="para">
+ </div></div><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id646088">10.4.5. Problems When You Try to Log In</h3></div></div></div><a id="id547229" class="indexterm"></a><div class="para">
If you did not create a user account in the <span class="application"><strong>firstboot</strong></span> screens, 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>.
@@ -2500,7 +2504,7 @@ id:3:initdefault:</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" id="s2-trouble-ram">10.4.6. Is Your RAM Not Being Recognized?</h3></div></div></div><a id="id608336" 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" id="s2-trouble-ram">10.4.6. Is Your RAM Not Being Recognized?</h3></div></div></div><a id="id880458" class="indexterm"></a><div class="para">
Sometimes, the kernel does not recognize all of your memory (RAM). You can check this with the <code class="command">cat /proc/meminfo</code> command.
</div><div class="para">
Verify that the displayed quantity is the same as the known amount of RAM in your system. If they are not equal, add the following line to the <code class="filename">/boot/grub/grub.conf</code>:
@@ -2536,13 +2540,13 @@ initrd /initrd-(2.6.32.130.el6.i686.img
Once the boot loader screen has returned, type <code class="command">b</code> to boot the system.
</div><div class="para">
Remember to replace <em class="replaceable"><code>xx</code></em> with the amount of RAM in your system. Press <span class="keycap"><strong>Enter</strong></span> to boot.
- </div></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id1001590">10.4.7. Your Printer Does Not Work</h3></div></div></div><a id="id677032" class="indexterm"></a><div class="para">
+ </div></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id615608">10.4.7. Your Printer Does Not Work</h3></div></div></div><a id="id603203" 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" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id618256">10.4.8. Apache HTTP Server or Sendmail stops responding during startup</h3></div></div></div><a id="id671903" class="indexterm"></a><a id="id1245539" class="indexterm"></a><div class="para">
+ </div></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id762738">10.4.8. Apache HTTP Server or Sendmail stops responding during startup</h3></div></div></div><a id="id590855" class="indexterm"></a><a id="id713658" 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="id525349"><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="id592168"><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.
@@ -2552,7 +2556,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><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><dd><dl><dt><span class="section"><a href="#sn-boot-options-language">11.1.1. Specifying the Language</a></span></dt><dt><span class="section"><a href="#sn-boot-options-interface">11.1.2. Configuring the Interface</a></span></dt><dt><span class="section"><a href="#sn-boot-options-update">11.1.3. Updating anaconda</a></span></dt><dt><span class="section"><a href="#sn-boot-options-installmethod">11.1.4. Specifying the Installation Method</a></span></dt><dt><span class="section"><a href="#sn-boot-options-network">11.1.5. Specifying the Network Settings</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-remoteaccess-installation">11.2. Enabling Remote A
ccess to the Installation System</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-remoteaccess-installation-vnc">11.2.1. Enabling Remote Access with VNC</a></span></dt><dt><span class="section"><a href="#sn-remoteaccess-installation-vnclistener">11.2.2. Connecting the Installation System to a VNC Listener</a></span></dt><dt><span class="section"><a href="#sn-ssh-installation">11.2.3. Enabling Remote Access with ssh</a></span></dt><dt><span class="section"><a href="#sn-telnet-installation">11.2.4. Enabling Remote Access with Telnet</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-remote-logging">11.3. Logging to a Remote System During the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-remote-logging-logserver">11.3.1. Configuring a Log Server</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-automating-installation">11.4. Automating the Installation with Kickstart</a></span></dt><dt><span class="section"><a
href="#sn-bootoptions-hardware">11.5. Enhancing Hardware Support</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-bootoptions-hwdetection">11.5.1. Overriding Automatic Hardware Detection</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-boot-modes">11.6. Using the Maintenance Boot Modes</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-memtest">11.6.1. Loading the Memory (RAM) Testing Mode</a></span></dt><dt><span class="section"><a href="#sn-boot-mediacheck">11.6.2. Verifying boot media</a></span></dt><dt><span class="section"><a href="#sn-mode-rescue">11.6.3. Booting Your Computer with the Rescue Mode</a></span></dt><dt><span class="section"><a href="#sn-mode-upgradeany">11.6.4. Upgrading your computer</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 File
s</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 c
lass="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="#s1-netboot-add-hosts">13.5.3. Adding PXE Hosts</a></span></dt><dt><span class="section"><a href="#s1-netboot-tftp">13.5.4. TFTPD</a></span></dt><dt><span class="section"><a href="#id636107">13.5.5. Configuring the DHCP Server</a></span></dt><dt><span class="section"><a href="#s2-netboot-custom-msg">13.5.6. Adding a Custom Boot Message</a></span></dt><dt><span class="section"><a href="#netboot-performing">13.5.7. 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 cla
ss="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="sectio
n"><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-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></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><dt><span class="section"><a href="#sn-bootoptions-installer">11.1. Configuring the Installation System at the Boot Menu</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-boot-options-language">11.1.1. Specifying the Language</a></span></dt><dt><span class="section"><a href="#sn-boot-options-interface">11.1.2. Configuring the Interface</a></span></dt><dt><span class="section"><a href="#sn-boot-options-update">11.1.3. Updating anaconda</a></span></dt><dt><span class="section"><a href="#sn-boot-options-installmethod">11.1.4. Specifying the Installation Method</a></span></dt><dt><span class="section"><a href="#sn-boot-options-network">11.1.5. Specifying the Network Settings</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-remoteaccess-installation">11.2. Enabling Remote Access to the Installation System</a></span></dt><dd><dl><
dt><span class="section"><a href="#sn-remoteaccess-installation-vnc">11.2.1. Enabling Remote Access with VNC</a></span></dt><dt><span class="section"><a href="#sn-remoteaccess-installation-vnclistener">11.2.2. Connecting the Installation System to a VNC Listener</a></span></dt><dt><span class="section"><a href="#sn-ssh-installation">11.2.3. Enabling Remote Access with ssh</a></span></dt><dt><span class="section"><a href="#sn-telnet-installation">11.2.4. Enabling Remote Access with Telnet</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-remote-logging">11.3. Logging to a Remote System During the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-remote-logging-logserver">11.3.1. Configuring a Log Server</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-automating-installation">11.4. Automating the Installation with Kickstart</a></span></dt><dt><span class="section"><a href="#sn-bootoptions-hardware">11.5. Enhancing Hardware
Support</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-bootoptions-hwdetection">11.5.1. Overriding Automatic Hardware Detection</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-boot-modes">11.6. Using the Maintenance Boot Modes</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-memtest">11.6.1. Loading the Memory (RAM) Testing Mode</a></span></dt><dt><span class="section"><a href="#sn-boot-mediacheck">11.6.2. Verifying boot media</a></span></dt><dt><span class="section"><a href="#sn-mode-rescue">11.6.3. Booting Your Computer with the Rescue Mode</a></span></dt><dt><span class="section"><a href="#sn-mode-upgradeany">11.6.4. Upgrading your computer</a></span></dt></dl></dd></dl></div><div class="para">
+ </div></li></ul></div><div class="toc"><p><strong>Table of Contents</strong></p><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><dd><dl><dt><span class="section"><a href="#sn-boot-options-language">11.1.1. Specifying the Language</a></span></dt><dt><span class="section"><a href="#sn-boot-options-interface">11.1.2. Configuring the Interface</a></span></dt><dt><span class="section"><a href="#sn-boot-options-update">11.1.3. Updating anaconda</a></span></dt><dt><span class="section"><a href="#sn-boot-options-installmethod">11.1.4. Specifying the Installation Method</a></span></dt><dt><span class="section"><a href="#sn-boot-options-network">11.1.5. Specifying the Network Settings</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-remoteaccess-installation">11.2. Enabling Remote A
ccess to the Installation System</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-remoteaccess-installation-vnc">11.2.1. Enabling Remote Access with VNC</a></span></dt><dt><span class="section"><a href="#sn-remoteaccess-installation-vnclistener">11.2.2. Connecting the Installation System to a VNC Listener</a></span></dt><dt><span class="section"><a href="#sn-ssh-installation">11.2.3. Enabling Remote Access with ssh</a></span></dt><dt><span class="section"><a href="#sn-telnet-installation">11.2.4. Enabling Remote Access with Telnet</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-remote-logging">11.3. Logging to a Remote System During the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-remote-logging-logserver">11.3.1. Configuring a Log Server</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-automating-installation">11.4. Automating the Installation with Kickstart</a></span></dt><dt><span class="section"><a
href="#sn-bootoptions-hardware">11.5. Enhancing Hardware Support</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-bootoptions-hwdetection">11.5.1. Overriding Automatic Hardware Detection</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-boot-modes">11.6. Using the Maintenance Boot Modes</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-memtest">11.6.1. Loading the Memory (RAM) Testing Mode</a></span></dt><dt><span class="section"><a href="#sn-boot-mediacheck">11.6.2. Verifying boot media</a></span></dt><dt><span class="section"><a href="#sn-mode-rescue">11.6.3. Booting Your Computer with the Rescue Mode</a></span></dt><dt><span class="section"><a href="#sn-mode-upgradeany">11.6.4. Upgrading your computer</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 File
s</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 c
lass="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="#s1-netboot-add-hosts">13.5.3. Adding PXE Hosts</a></span></dt><dt><span class="section"><a href="#s1-netboot-tftp">13.5.4. TFTPD</a></span></dt><dt><span class="section"><a href="#id736470">13.5.5. Configuring the DHCP Server</a></span></dt><dt><span class="section"><a href="#s2-netboot-custom-msg">13.5.6. Adding a Custom Boot Message</a></span></dt><dt><span class="section"><a href="#netboot-performing">13.5.7. 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 cla
ss="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="sectio
n"><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-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></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><dt><span class="section"><a href="#sn-bootoptions-installer">11.1. Configuring the Installation System at the Boot Menu</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-boot-options-language">11.1.1. Specifying the Language</a></span></dt><dt><span class="section"><a href="#sn-boot-options-interface">11.1.2. Configuring the Interface</a></span></dt><dt><span class="section"><a href="#sn-boot-options-update">11.1.3. Updating anaconda</a></span></dt><dt><span class="section"><a href="#sn-boot-options-installmethod">11.1.4. Specifying the Installation Method</a></span></dt><dt><span class="section"><a href="#sn-boot-options-network">11.1.5. Specifying the Network Settings</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-remoteaccess-installation">11.2. Enabling Remote Access to the Installation System</a></span></dt><dd><dl><
dt><span class="section"><a href="#sn-remoteaccess-installation-vnc">11.2.1. Enabling Remote Access with VNC</a></span></dt><dt><span class="section"><a href="#sn-remoteaccess-installation-vnclistener">11.2.2. Connecting the Installation System to a VNC Listener</a></span></dt><dt><span class="section"><a href="#sn-ssh-installation">11.2.3. Enabling Remote Access with ssh</a></span></dt><dt><span class="section"><a href="#sn-telnet-installation">11.2.4. Enabling Remote Access with Telnet</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-remote-logging">11.3. Logging to a Remote System During the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-remote-logging-logserver">11.3.1. Configuring a Log Server</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-automating-installation">11.4. Automating the Installation with Kickstart</a></span></dt><dt><span class="section"><a href="#sn-bootoptions-hardware">11.5. Enhancing Hardware
Support</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-bootoptions-hwdetection">11.5.1. Overriding Automatic Hardware Detection</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-boot-modes">11.6. Using the Maintenance Boot Modes</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-memtest">11.6.1. Loading the Memory (RAM) Testing Mode</a></span></dt><dt><span class="section"><a href="#sn-boot-mediacheck">11.6.2. Verifying boot media</a></span></dt><dt><span class="section"><a href="#sn-mode-rescue">11.6.3. Booting Your Computer with the Rescue Mode</a></span></dt><dt><span class="section"><a href="#sn-mode-upgradeany">11.6.4. Upgrading your computer</a></span></dt></dl></dd></dl></div><div class="para">
The Fedora installation system includes a range of functions and options for administrators. To use boot options, enter <strong class="userinput"><code>linux <em class="replaceable"><code>option</code></em></code></strong> at the <code class="prompt">boot:</code> prompt.
</div><div class="para">
To access the <code class="prompt">boot:</code> prompt on a system that displays a graphical boot screen, press the <span class="keycap"><strong>Esc</strong></span> key while the graphical boot screen is displayed.
@@ -2587,12 +2591,12 @@ initrd /initrd-(2.6.32.130.el6.i686.img
</div><pre class="screen">
<strong class="userinput"><code>linux resolution=<em class="replaceable"><code>1024x768</code></em></code></strong></pre><div class="para">
To run the installation process in
- <a id="id557481" class="indexterm"></a>
+ <a id="id670979" class="indexterm"></a>
<code class="option">text</code> mode, enter:
</div><pre class="screen">
<strong class="userinput"><code>linux text</code></strong></pre><div class="para">
To enable support for a
- <a id="id542874" class="indexterm"></a>
+ <a id="id728384" class="indexterm"></a>
serial console, enter <code class="option">serial</code> as an additional option.
</div><div class="para">
Use <code class="option">display=<em class="replaceable"><code>ip</code></em>:0</code> to allow remote display forwarding. In this command, <em class="replaceable"><code>ip</code></em> should be replaced with the IP address of the system on which you want the display to appear.
@@ -2658,15 +2662,15 @@ initrd /initrd-(2.6.32.130.el6.i686.img
This example configures the network settings for an installation system that uses the IP address <code class="systemitem">192.168.1.10</code> for interface <code class="systemitem">eth0</code>:
</div><pre class="screen"><strong class="userinput"><code>linux ip=192.168.1.10 netmask=255.255.255.0 gateway=192.168.1.1 dns=192.168.1.3 ksdevice=eth0</code></strong></pre><div class="para">
If you specify the network configuration and network device at the <code class="prompt">boot:</code> prompt, these settings are used for the installation process and the <span class="guilabel"><strong>Networking Devices</strong></span> and <span class="guilabel"><strong>Configure TCP/IP</strong></span> dialogs do not appear.
- </div></div></div><div class="section" id="sn-remoteaccess-installation"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sn-remoteaccess-installation">11.2. Enabling Remote Access to the Installation System</h2></div></div></div><a id="id811083" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="sn-remoteaccess-installation"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sn-remoteaccess-installation">11.2. Enabling Remote Access to the Installation System</h2></div></div></div><a id="id611959" class="indexterm"></a><div class="para">
You may access either graphical or text interfaces for the installation system from any other system. Access to a text mode display requires <span class="application"><strong>telnet</strong></span>, which is installed by default on Fedora systems. To remotely access the graphical display of an installation system, use client software that supports the VNC (Virtual Network Computing) display protocol.
</div><div class="note"><div class="admonition_header"><h2>Installing a VNC Client on Fedora</h2></div><div class="admonition"><div class="para">
- <a id="id787768" class="indexterm"></a>
+ <a id="id680554" class="indexterm"></a>
Fedora includes the VNC client <span class="application"><strong>vncviewer</strong></span>. To obtain <span class="application"><strong>vncviewer</strong></span>, install the <span class="package">tigervnc</span> package.
</div></div></div><div class="para">
The installation system supports two methods of establishing a VNC connection. You may start the installation, and manually login to the graphical display with a VNC client on another system. Alternatively, you may configure the installation system to automatically connect to a VNC client on the network that is running in <em class="firstterm">listening mode</em>.
</div><div class="section" id="sn-remoteaccess-installation-vnc"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sn-remoteaccess-installation-vnc">11.2.1. Enabling Remote Access with VNC</h3></div></div></div><div class="para">
- <a id="id642279" class="indexterm"></a>
+ <a id="id527602" class="indexterm"></a>
To enable remote graphical access to the installation system, enter two options at the prompt:
</div><pre class="screen">
<strong class="userinput"><code>linux vnc vncpassword=<em class="replaceable"><code>qwerty</code></em></code></strong></pre><div class="para">
@@ -2683,7 +2687,7 @@ Press <enter> for a shell</pre><div class="para">
You may then login to the installation system with a VNC client. To run the <span class="application"><strong>vncviewer</strong></span> client on Fedora, choose <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>Accessories</strong></span> → <span class="guimenuitem"><strong>VNC Viewer</strong></span>, or type the command <span class="application"><strong>vncviewer</strong></span> in a terminal window. Enter the server and display number in the <span class="guilabel"><strong>VNC Server</strong></span> dialog. For the example above, the <span class="guilabel"><strong>VNC Server</strong></span> is <strong class="userinput"><code>computer.mydomain.com:1</code></strong>.
</div></div><div class="section" id="sn-remoteaccess-installation-vnclistener"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sn-remoteaccess-installation-vnclistener">11.2.2. Connecting the Installation System to a VNC Listener</h3></div></div></div><div class="para">
To have the installation system automatically connect to a VNC client, first start the client in
- <a id="id595790" class="indexterm"></a>
+ <a id="id611048" class="indexterm"></a>
listening mode. On Fedora systems, use the <code class="option">-listen</code> option to run <span class="application"><strong>vncviewer</strong></span> as a listener. In a terminal window, enter the command:
</div><pre class="screen">
<strong class="userinput"><code>vncviewer -listen</code></strong></pre><div class="note"><div class="admonition_header"><h2>Firewall Reconfiguration Required</h2></div><div class="admonition"><div class="para">
@@ -2693,14 +2697,14 @@ Press <enter> for a shell</pre><div class="para">
</div><div class="para">
For example, to connect to a VNC client on the system <code class="systemitem">desktop.mydomain.com</code> on the port 5500, enter the following at the <code class="prompt">boot:</code> prompt:
</div><pre class="screen">
-<strong class="userinput"><code>linux vnc vncpassword=<em class="replaceable"><code>qwerty</code></em> vncconnect=<em class="replaceable"><code>desktop.mydomain.com:5500</code></em></code></strong></pre></div><div class="section" id="sn-ssh-installation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sn-ssh-installation">11.2.3. Enabling Remote Access with ssh</h3></div></div></div><a id="id819348" class="indexterm"></a><div class="para">
+<strong class="userinput"><code>linux vnc vncpassword=<em class="replaceable"><code>qwerty</code></em> vncconnect=<em class="replaceable"><code>desktop.mydomain.com:5500</code></em></code></strong></pre></div><div class="section" id="sn-ssh-installation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sn-ssh-installation">11.2.3. Enabling Remote Access with ssh</h3></div></div></div><a id="id654431" class="indexterm"></a><div class="para">
To enable remote access to a text mode installation, use the <code class="option">sshd=1</code> option at the <code class="prompt">boot:</code> prompt:
</div><pre class="screen">
<strong class="userinput"><code>linux sshd=1</code></strong></pre><div class="para">
You can then connect to the installation system with the <code class="command">ssh</code> utility. The <code class="command">ssh</code> command requires the name or IP address of the installation system, and a password if you specified one (for example, in a kickstart file).
</div></div><div class="section" id="sn-telnet-installation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sn-telnet-installation">11.2.4. Enabling Remote Access with Telnet</h3></div></div></div><div class="para">
To enable remote access to a text mode installation, use the
- <a id="id934108" class="indexterm"></a>
+ <a id="id519992" class="indexterm"></a>
<code class="option">telnet</code> option at the <code class="prompt">boot:</code> prompt:
</div><pre class="screen">
<strong class="userinput"><code>linux text telnet</code></strong></pre><div class="para">
@@ -2710,7 +2714,7 @@ Press <enter> for a shell</pre><div class="para">
To ensure the security of the installation process, only use the <code class="option">telnet</code> option to install systems on networks with restricted access.
</div></div></div></div></div><div class="section" id="sn-remote-logging"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sn-remote-logging">11.3. Logging to a Remote System During the Installation</h2></div></div></div><div class="para">
By default, the installation process sends log messages to the console as they are generated. You may specify that these messages go to a remote system that runs a
- <a id="id563412" class="indexterm"></a>
+ <a id="id871914" class="indexterm"></a>
<em class="firstterm">syslog</em> service.
</div><div class="para">
To configure remote logging, add the <code class="option">syslog</code> option. Specify the IP address of the logging system, and the UDP port number of the log service on that system. By default, syslog services that accept remote messages listen on UDP port 514.
@@ -2733,7 +2737,7 @@ Press <enter> for a shell</pre><div class="para">
By default, the syslog service listens on UDP port 514. To permit connections to this port from other systems, choose <span class="guimenu"><strong>System</strong></span> → <span class="guisubmenu"><strong>Administration</strong></span> → <span class="guimenuitem"><strong> Firewall</strong></span>. Select <span class="guilabel"><strong>Other ports</strong></span>, and <span class="guibutton"><strong>Add</strong></span>. Enter <strong class="userinput"><code>514</code></strong> in the <span class="guilabel"><strong>Port(s)</strong></span> field, and specify <strong class="userinput"><code>udp</code></strong> as the <span class="guilabel"><strong>Protocol</strong></span>.
</div></div></div></div></div><div class="section" id="sn-automating-installation"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sn-automating-installation">11.4. Automating the Installation with Kickstart</h2></div></div></div><div class="para">
You can allow an installation to run unattended by using Kickstart. A
- <a id="id777258" class="indexterm"></a>
+ <a id="id638719" class="indexterm"></a>
<em class="firstterm">Kickstart</em> file specifies settings for an installation. Once the installation system boots, it can read a Kickstart file and carry out the installation process without any further input from a user.
</div><div class="note"><div class="admonition_header"><h2>Every Installation Produces a Kickstart File</h2></div><div class="admonition"><div class="para">
The Fedora installation process automatically writes a Kickstart file that contains the settings for the installed system. This file is always saved as <code class="filename">/root/anaconda-ks.cfg</code>. You may use this file to repeat the installation with identical settings, or modify copies to specify settings for other systems.
@@ -2859,7 +2863,7 @@ Press <enter> for a shell</pre><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
- <a id="id694947" class="indexterm"></a>
+ <a id="id791560" class="indexterm"></a>
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.
</div><div class="para">
In most cases, a single successful pass with <span class="application"><strong>Memtest86+</strong></span> is sufficient to verify that your RAM is in good condition. In some rare circumstances, however, errors that went undetected on the first pass might appear on subsequent passes. To perform a thorough test of the RAM on an important system, leave <span class="application"><strong>Memtest86+</strong></span> running overnight or for a few days.
@@ -2875,9 +2879,9 @@ Press <enter> for a shell</pre><div class="para">
select <span class="guilabel"><strong>OK</strong></span> at the prompt to test the media before installation when booting from the Fedora DVD
</div></li><li class="listitem"><div class="para">
boot Fedora with the option <code class="option">mediacheck</code> option.
- </div></li></ul></div></div><div class="section" id="sn-mode-rescue"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sn-mode-rescue">11.6.3. Booting Your Computer with the Rescue Mode</h3></div></div></div><a id="id527840" class="indexterm"></a><div class="para">
+ </div></li></ul></div></div><div class="section" id="sn-mode-rescue"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sn-mode-rescue">11.6.3. Booting Your Computer with the Rescue Mode</h3></div></div></div><a id="id1398027" class="indexterm"></a><div class="para">
You may boot a command-line Linux system from either a
- <a id="id925079" class="indexterm"></a>
+ <a id="id535985" class="indexterm"></a>
rescue disc or an installation disc, without 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 your computer.
</div><div class="para">
The rescue disc starts the rescue mode system by default. To load the rescue system with the installation disc, choose <span class="guimenuitem"><strong>Rescue installed system</strong></span> from the boot menu.
@@ -2924,7 +2928,7 @@ Press <enter> for a shell</pre><div class="para">
When you are finished, change the <code class="option">default</code> option in <code class="filename">/boot/grub/grub.conf</code> to point to the new first stanza you added:
</div><pre class="screen">default 0</pre></div><div class="section" id="sn-medialess-booting"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sn-medialess-booting">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="#sn-remoteaccess-installation">Section 11.2, “Enabling Remote Access to the Installation System”</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><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 Conf
iguration</a></span></dt><dt><span class="section"><a href="#s1-netboot-add-hosts">13.5.3. Adding PXE Hosts</a></span></dt><dt><span class="section"><a href="#s1-netboot-tftp">13.5.4. TFTPD</a></span></dt><dt><span class="section"><a href="#id636107">13.5.5. Configuring the DHCP Server</a></span></dt><dt><span class="section"><a href="#s2-netboot-custom-msg">13.5.6. Adding a Custom Boot Message</a></span></dt><dt><span class="section"><a href="#netboot-performing">13.5.7. 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><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 Conf
iguration</a></span></dt><dt><span class="section"><a href="#s1-netboot-add-hosts">13.5.3. Adding PXE Hosts</a></span></dt><dt><span class="section"><a href="#s1-netboot-tftp">13.5.4. TFTPD</a></span></dt><dt><span class="section"><a href="#id736470">13.5.5. Configuring the DHCP Server</a></span></dt><dt><span class="section"><a href="#s2-netboot-custom-msg">13.5.6. Adding a Custom Boot Message</a></span></dt><dt><span class="section"><a href="#netboot-performing">13.5.7. 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.
@@ -2954,7 +2958,9 @@ Press <enter> for a shell</pre><div class="para">
To mount a physical DVD disc, use the following command:
</div><pre class="screen"><code class="command">mount -o context=system_u:object_r:httpd_sys_content_t:s0 /dev/dvd /mnt/dvd</code></pre><div class="para">
To mount a DVD ISO image, use the following command:
- </div><pre class="screen"><code class="command">mount -ro loop,context=system_u:object_r:httpd_sys_content_t:s0 /path/to/image.iso /mnt/dvd</code></pre></li><li class="step"><div class="para">
+ </div><pre class="screen"><code class="command">mount -ro loop,context=system_u:object_r:httpd_sys_content_t:s0 /path/to/image.iso /mnt/dvd</code></pre><div class="note"><div class="admonition_header"><h2>If SELinux enabled, use the default label</h2></div><div class="admonition"><div class="para">
+ If SELinux is enabled, use the default <code class="command">iso9660_t</code> label instead of <code class="command">httpd_sys_content_t</code>.
+ </div></div></div></li><li class="step"><div class="para">
To support NFS installation, create a file <code class="filename">/etc/exports</code> and add the following line to it:
</div><pre class="screen">/mnt/dvd *(ro,async)</pre><div class="para">
Start the NFS server using the following commands:
@@ -3001,7 +3007,7 @@ Press <enter> for a shell</pre><div class="para">
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" id="sn-pxe-server-manual">13.5. Manually configure a PXE server</h2></div></div></div><a id="id713464" 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" id="sn-pxe-server-manual">13.5. Manually configure a PXE server</h2></div></div></div><a id="id1260738" 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.
@@ -3015,13 +3021,13 @@ Press <enter> for a shell</pre><div class="para">
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" id="s1-netboot-netserver">13.5.1. Setting up the Network Server</h3></div></div></div><a id="id836863" 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" id="s1-netboot-netserver">13.5.1. Setting up the Network Server</h3></div></div></div><a id="id817926" 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" id="s1-netboot-pxe-config">13.5.2. PXE Boot Configuration</h3></div></div></div><a id="id677325" 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" id="s1-netboot-pxe-config">13.5.2. PXE Boot Configuration</h3></div></div></div><a id="id711715" 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">
To copy these files, run the <span class="application"><strong>Network Booting Tool</strong></span> on the NFS, FTP, or HTTP server. A separate PXE server is not necessary.
- </div></div><div class="section" id="s1-netboot-add-hosts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-netboot-add-hosts">13.5.3. Adding PXE Hosts</h3></div></div></div><a id="id802976" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s1-netboot-add-hosts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-netboot-add-hosts">13.5.3. Adding PXE Hosts</h3></div></div></div><a id="id750065" class="indexterm"></a><div class="para">
After configuring the network server, the interface as shown in <a class="xref" href="#fig-netboot-add-hosts">Figure 13.1, “Add Hosts”</a> is displayed.
</div><div class="figure" id="fig-netboot-add-hosts"><div class="figure-contents"><div class="mediaobject"><img src="images/pxe/netboot-add-hosts.png" width="444" alt="Add Hosts" /><div class="longdesc"><div class="para">
Add Hosts
@@ -3043,14 +3049,14 @@ Press <enter> for a shell</pre><div class="para">
<span class="guilabel"><strong>Kickstart File</strong></span> — The location of a kickstart file to use, such as <strong class="userinput"><code>http://server.example.com/kickstart/ks.cfg</code></strong>. This file can be created with the <span class="application"><strong>Kickstart Configurator</strong></span>. 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></li></ul></div><div class="para">
Ignore the <span class="guilabel"><strong>Snapshot name</strong></span> and <span class="guilabel"><strong>Ethernet</strong></span> options. They are only used for diskless environments.
- </div></div><div class="section" id="s1-netboot-tftp"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-netboot-tftp">13.5.4. TFTPD</h3></div></div></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id709865">13.5.4.1. Starting the <code class="command">tftp</code> Server</h4></div></div></div><a id="id590628" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s1-netboot-tftp"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-netboot-tftp">13.5.4. TFTPD</h3></div></div></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id885283">13.5.4.1. Starting the <code class="command">tftp</code> Server</h4></div></div></div><a id="id899542" 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; start it with the following commands:
</div><pre class="screen"><code class="command">/sbin/chkconfig --level 345 xinetd on</code>
<code class="command">/sbin/chkconfig --level 345 tftp on</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 time in runlevels 3, 4, and 5.
- </div></div></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id636107">13.5.5. Configuring the DHCP Server</h3></div></div></div><a id="id755371" class="indexterm"></a><a id="id728120" class="indexterm"></a><a id="id616723" class="indexterm"></a><a id="id596072" class="indexterm"></a><div class="para">
+ </div></div></div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id736470">13.5.5. Configuring the DHCP Server</h3></div></div></div><a id="id478674" class="indexterm"></a><a id="id700841" class="indexterm"></a><a id="id807888" class="indexterm"></a><a id="id612869" class="indexterm"></a><div class="para">
If a DHCP server does not already exist on the network, configure one. Refer to the Fedora Deployment Guide for details. Make sure the configuration file contains the following so that PXE booting is enabled for systems which support it:
</div><pre class="programlisting">
allow booting;
@@ -3061,9 +3067,9 @@ class "pxeclients" {
filename "linux-install/pxelinux.0"; }
</pre><div class="para">
where the next-server <em class="replaceable"><code><server-ip></code></em> should be replaced with the IP address of the <code class="command">tftp</code> server.
- </div></div><div class="section" id="s2-netboot-custom-msg"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-netboot-custom-msg">13.5.6. Adding a Custom Boot Message</h3></div></div></div><a id="id666147" 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" id="s2-netboot-custom-msg">13.5.6. Adding a Custom Boot Message</h3></div></div></div><a id="id495872" 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" id="netboot-performing">13.5.7. Performing the PXE Installation</h3></div></div></div><a id="id914034" 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" id="netboot-performing">13.5.7. Performing the PXE Installation</h3></div></div></div><a id="id529944" 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>gPXE</strong></span> bootloader. The Fedora Project does not distribute <span class="application"><strong>gPXE</strong></span> — refer to the Etherboot Project website at <a href="http://etherboot.org/wiki/start">http://etherboot.org/wiki/start</a> for more information.
@@ -3123,9 +3129,9 @@ class "pxeclients" {
</div><div class="para">
The VNC connect mode changes how VNC is started. Rather than anaconda starting up and waiting for you to connect, the VNC connect mode allows anaconda to automatically connect to your view. You won't need to know the IP address of the target system in this case.
</div><div class="para">
- To activate the VNC connect mode, pass the <code class="command">vncconnect</code> boot parameter:
- </div><pre class="screen">boot: <strong class="userinput"><code>linux vncconnect=<em class="replaceable"><code>HOST</code></em></code></strong></pre><div class="para">
- Replace HOST with your VNC viewer's IP address or DNS host name. Before starting the installation process on the target system, start up your VNC viewer and have it wait for an incoming connection.
+ To activate the VNC connect mode, pass the <code class="command">vnc vncconnect</code> boot parameter:
+ </div><pre class="screen">boot: <strong class="userinput"><code>linux vnc vncconnect=<em class="replaceable"><code>HOST</code></em>[:<em class="replaceable"><code>port</code></em>]</code></strong></pre><div class="para">
+ Replace HOST with your VNC viewer's IP address or DNS host name. Specifying the port is optional. Before starting the installation process on the target system, start up your VNC viewer and have it wait for an incoming connection.
</div><div class="para">
Start the installation and when your VNC viewer displays the graphical installer, you are ready to go.
</div></div></div><div xml:lang="en-US" class="section" id="VNC_Whitepaper-installation" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="VNC_Whitepaper-installation">14.3. Installation Using VNC</h2></div></div></div><div class="para">
@@ -3145,8 +3151,8 @@ class "pxeclients" {
</div><pre class="screen">boot: <strong class="userinput"><code>linux vnc</code></strong></pre></li><li class="listitem"><div class="para">
Boot over the network.
</div><div class="para">
- If the target system is configured with a static IP address, add the <code class="command">vnc</code> command to the kickstart file. If the target system is using DHCP, add <code class="command">vncconnect=<em class="replaceable"><code>HOST</code></em></code> to the boot arguments for the target system. HOST is the IP address or DNS host name of the VNC viewer system. Enter the following at the prompt:
- </div><pre class="screen">boot: <strong class="userinput"><code>linux vncconnect=<em class="replaceable"><code>HOST</code></em></code></strong></pre></li></ol></div></li><li class="listitem"><div class="para">
+ If the target system is configured with a static IP address, add the <code class="command">vnc</code> command to the kickstart file. If the target system is using DHCP, add <code class="command">vnc vncconnect=<em class="replaceable"><code>HOST</code></em>[:<em class="replaceable"><code>port</code></em>]</code> to the boot arguments for the target system. HOST is the IP address or DNS host name of the VNC viewer system. Specifying the port is optional. Enter the following at the prompt:
+ </div><pre class="screen">boot: <strong class="userinput"><code>linux vnc vncconnect=<em class="replaceable"><code>HOST</code></em>[:<em class="replaceable"><code>port</code></em>]</code></strong></pre></li></ol></div></li><li class="listitem"><div class="para">
When prompted for the network configuration on the target system, assign it an available RFC 1918 address in the same network you used for the VNC viewer system. For example, 192.168.100.2/24.
</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
This IP address is only used during installation. You will have an opportunity to configure the final network settings, if any, later in the installer.
@@ -3155,7 +3161,7 @@ class "pxeclients" {
</div></li></ol></div></div><div class="section" id="VNC_Whitepaper-kickstart-installation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="VNC_Whitepaper-kickstart-installation">14.3.2. Kickstart Considerations</h3></div></div></div><div class="para">
If your target system will be booting over the network, VNC is still available. Just add the <code class="command">vnc</code> command to the kickstart file for the system. You will be able to connect to the target system using your VNC viewer and monitor the installation progress. The address to use is the one the system is configured with via the kickstart file.
</div><div class="para">
- If you are using DHCP for the target system, the reverse <code class="command">vncconnect</code> method may work better for you. Rather than adding the <code class="command">vnc</code> boot parameter to the kickstart file, add the <code class="command">vncconnect=<em class="replaceable"><code>HOST</code></em></code> parameter to the list of boot arguments for the target system. For HOST, put the IP address or DNS host name of the VNC viewer system. See the next section for more details on using the vncconnect mode.
+ If you are using DHCP for the target system, the reverse <code class="command">vnc vncconnect</code> method may work better for you. Rather than adding the <code class="command">vnc</code> boot parameter to the kickstart file, add the <code class="command">vnc vncconnect=<em class="replaceable"><code>HOST</code></em>[:<em class="replaceable"><code>port</code></em>]</code> parameter to the list of boot arguments for the target system. For HOST, put the IP address or DNS host name of the VNC viewer system. Specifying the port is optional. See the next section for more details on using the vncconnect mode.
</div></div><div class="section" id="VNC_Whitepaper-firewall-considerations"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="VNC_Whitepaper-firewall-considerations">14.3.3. Firewall Considerations</h3></div></div></div><div class="para">
If you are performing the installation where the VNC viewer system is a workstation on a different subnet from the target system, you may run in to network routing problems. VNC works fine so long as your viewer system has a route to the target system and ports 5900 and 5901 are open. If your environment has a firewall, make sure ports 5900 and 5901 are open between your workstation and the target system.
</div><div class="para">
@@ -3163,7 +3169,7 @@ class "pxeclients" {
</div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
Be sure to use a temporary password for the <code class="command">vncpassword</code> option. It should not be a password you use on any systems, especially a real root password.
</div></div></div><div class="para">
- If you continue to have trouble, consider using the <code class="command">vncconnect</code> parameter. In this mode of operation, you start the viewer on your system first telling it to listen for an incoming connection. Pass <code class="command">vncconnect=<em class="replaceable"><code>HOST</code></em></code> at the boot prompt and the installer will attempt to connect to the specified HOST (either a hostname or IP address).
+ If you continue to have trouble, consider using the <code class="command">vnc vncconnect</code> parameter. In this mode of operation, you start the viewer on your system first telling it to listen for an incoming connection. Pass <code class="command">vnc vncconnect=<em class="replaceable"><code>HOST</code></em>[:<em class="replaceable"><code>port</code></em>]</code> at the boot prompt and the installer will attempt to connect to the specified HOST (either a hostname or IP address). Specifying the port is optional.
</div></div></div><div xml:lang="en-US" class="section" id="VNC_Whitepaper-references" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="VNC_Whitepaper-references">14.4. References</h2></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
VNC description at Wikipedia: <a href="http://en.wikipedia.org/wiki/Vnc">http://en.wikipedia.org/wiki/Vnc</a>
</div></li><li class="listitem"><div class="para">
@@ -3174,7 +3180,7 @@ class "pxeclients" {
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><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-preinstal
lconfig">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">1
5.10. Starting a Kickstart Installation</a></span></dt></dl></div><a id="id925181" class="indexterm"></a><a id="id597600" class="indexterm"></a><div class="section" id="s1-kickstart2-whatis"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kickstart2-whatis">15.1. What are Kickstart Installations?</h2></div></div></div><a id="id733778" 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><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-preinstal
lconfig">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">1
5.10. Starting a Kickstart Installation</a></span></dt></dl></div><a id="id529696" class="indexterm"></a><a id="id639267" class="indexterm"></a><div class="section" id="s1-kickstart2-whatis"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kickstart2-whatis">15.1. What are Kickstart Installations?</h2></div></div></div><a id="id848992" 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.
@@ -3198,7 +3204,7 @@ class "pxeclients" {
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" id="s1-kickstart2-file">15.3. Creating the Kickstart File</h2></div></div></div><a id="id519944" class="indexterm"></a><a id="id926873" class="indexterm"></a><a id="id592151" 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" id="s1-kickstart2-file">15.3. Creating the Kickstart File</h2></div></div></div><a id="id599581" class="indexterm"></a><a id="id714945" class="indexterm"></a><a id="id778394" 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:
@@ -3232,12 +3238,12 @@ class "pxeclients" {
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" id="s1-kickstart2-options">15.4. Kickstart Options</h2></div></div></div><a id="id931170" class="indexterm"></a><a id="id698802" 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" id="s1-kickstart2-options">15.4. Kickstart Options</h2></div></div></div><a id="id564570" class="indexterm"></a><a id="id720171" 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><dt class="varlistentry"><span class="term"><code class="command">autopart</code> (optional) </span></dt><dd><div class="para">
- <a id="id798349" class="indexterm"></a>
+ <a id="id878750" 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.
@@ -3248,7 +3254,7 @@ class "pxeclients" {
</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">ignoredisk</code> (optional) </span></dt><dd><div class="para">
- <a id="id531941" class="indexterm"></a>
+ <a id="id748715" 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:
@@ -3267,13 +3273,13 @@ class "pxeclients" {
</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">autostep</code> (optional) </span></dt><dd><div class="para">
- <a id="id1353722" class="indexterm"></a>
+ <a id="id773729" 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">auth</code> or <code class="command">authconfig</code> (required) </span></dt><dd><div class="para">
- <a id="id690501" class="indexterm"></a>
- <a id="id637774" class="indexterm"></a>
+ <a id="id488070" class="indexterm"></a>
+ <a id="id789410" 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.
@@ -3326,7 +3332,7 @@ class "pxeclients" {
</div><div class="para">
Remove the <code class="command">--enablemd5</code> option if it is present.
</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="id651437" class="indexterm"></a>
+ <a id="id716246" 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.
@@ -3343,7 +3349,7 @@ class "pxeclients" {
</div></li><li class="listitem"><div class="para">
<code class="command">--upgrade</code> — Upgrade the existing boot loader configuration, preserving the old entries. This option is only available for upgrades.
</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="id886049" class="indexterm"></a>
+ <a id="id614020" 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.
@@ -3364,17 +3370,17 @@ class "pxeclients" {
</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="id525834" class="indexterm"></a>
+ <a id="id737514" 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="id549220" class="indexterm"></a>
+ <a id="id559791" 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="id488549" class="indexterm"></a>
+ <a id="id884945" class="indexterm"></a>
Driver diskettes can be used during kickstart installations. You must copy the driver diskettes'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 diskette:
@@ -3389,7 +3395,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="id507965" class="indexterm"></a>
+ <a id="id839894" 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.
@@ -3412,8 +3418,8 @@ 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">firstboot</code> (optional) </span></dt><dd><div class="para">
- <a id="id855505" class="indexterm"></a>
- <a id="id642250" class="indexterm"></a>
+ <a id="id731690" class="indexterm"></a>
+ <a id="id620545" class="indexterm"></a>
Determine whether the <span class="application"><strong>firstboot</strong></span> starts the first time the system is booted. If enabled, the <span class="package">firstboot</span> package must be installed. If not specified, this option is disabled by default.
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">--enable</code> or <code class="command">--enabled</code> — The <span class="application"><strong>Setup Agent</strong></span> is started the first time the system boots.
@@ -3422,19 +3428,19 @@ driverdisk --source=nfs:host:/path/to/img</pre><div class="itemizedlist"><ul><li
</div></li><li class="listitem"><div class="para">
<code class="command">--reconfig</code> — Enable the <span class="application"><strong>Setup Agent</strong></span> to start at boot time in reconfiguration mode. This mode enables the language, mouse, keyboard, root password, security level, time zone, and networking configuration options in addition to the default ones.
</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="id591190" class="indexterm"></a>
+ <a id="id774932" 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="id566792" class="indexterm"></a>
+ <a id="id631583" 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">install</code> (optional) </span></dt><dd><div class="para">
- <a id="id912254" class="indexterm"></a>
+ <a id="id564535" 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="id674074" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div><a id="id828127" 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.
@@ -3475,7 +3481,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="id993780" class="indexterm"></a>
+ <a id="id868685" 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.
@@ -3493,9 +3499,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="id876427" 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="id680517" 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="id634412" 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="id494042" class="indexterm"></a><div class="para">
Sets the default keyboard type for the system. The available keyboard types are:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="literal">be-latin1</code> — Belgian
@@ -3606,7 +3612,7 @@ driverdisk --source=nfs:host:/path/to/img</pre><div class="itemizedlist"><ul><li
</div></li></ul></div><div class="para">
The file <code class="filename">/usr/lib/python2.6/site-packages/system_config_keyboard/keyboard_models.py</code> on 32-bit systems or <code class="filename">/usr/lib64/python2.6/site-packages/system_config_keyboard/keyboard_models.py</code> on 64-bit systems also contains this list and is part of the <span class="package">system-config-keyboard</span> package.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">lang</code> (required)
- <a id="id792510" class="indexterm"></a>
+ <a id="id648382" 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">
@@ -3614,13 +3620,13 @@ driverdisk --source=nfs:host:/path/to/img</pre><div class="itemizedlist"><ul><li
</div><div class="para">
Certain languages (for example, Chinese, Japanese, Korean, and Indic languages) are not supported during text-mode installation. If you specify one of these languages with the <code class="command">lang</code> command, the installation process continues in English, but the installed system uses your selection as its default language.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">langsupport</code> (deprecated)
- <a id="id765133" class="indexterm"></a>
+ <a id="id786335" 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="id636507" class="indexterm"></a>
- <a id="id525757" class="indexterm"></a>
- <a id="id493435" class="indexterm"></a>
+ <a id="id1402181" class="indexterm"></a>
+ <a id="id627523" class="indexterm"></a>
+ <a id="id656856" 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">
@@ -3661,7 +3667,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="id685827" class="indexterm"></a>
+ <a id="id709852" 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">
@@ -3673,11 +3679,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="id556744" class="indexterm"></a>
+ <a id="id654503" 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="id653934" class="indexterm"></a>
+ <a id="id812598" 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">
@@ -3689,11 +3695,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="id814776" class="indexterm"></a>
+ <a id="id736495" 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="id802995" class="indexterm"></a>
+ <a id="id678123" 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">
@@ -3788,8 +3794,8 @@ logvol / --vgname=myvg --size=1 --name=rootvol --grow --percent=90</pre></dd><dt
<code class="command">--noipv4</code> — Disable IPv4 on this device.
</div></li><li class="listitem"><div class="para">
<code class="command">--noipv6</code> — Disable IPv6 on this device.
- </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <a id="id768211" class="indexterm"></a>
- <a id="id806382" class="indexterm"></a>
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <a id="id858613" class="indexterm"></a>
+ <a id="id564998" 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">
@@ -3876,7 +3882,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="id641625" class="indexterm"></a>
+ </div></div></div></dd><dt class="varlistentry"><span class="term"> <a id="id801846" 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">
@@ -3885,8 +3891,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="id818681" class="indexterm"></a>
- <a id="id840753" class="indexterm"></a>
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="id557982" class="indexterm"></a>
+ <a id="id591165" 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">
@@ -3930,7 +3936,7 @@ part raid.13 --size=1 --grow --ondisk=sdc
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"> <a id="id692422" class="indexterm"></a>
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="id547568" 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">
@@ -3942,7 +3948,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="id893051" class="indexterm"></a>
+ <a id="id814272" 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>]
@@ -3953,12 +3959,12 @@ 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="id530200" class="indexterm"></a>
+ <a id="id564880" 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] <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.
</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="id733589" class="indexterm"></a>
+ <a id="id482353" 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.
@@ -3971,7 +3977,7 @@ raid /usr --level=5 --device=md1 raid.11 raid.12 raid.13
</div></li></ul></div><div class="para">
For more information regarding SELinux for Fedora, refer to the <em class="citetitle">Fedora Deployment Guide</em>.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">services</code> (optional) </span></dt><dd><div class="para">
- <a id="id910870" class="indexterm"></a>
+ <a id="id708522" 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.
@@ -3986,18 +3992,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="id686310" class="indexterm"></a>
+ <a id="id638220" 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="id1361058" class="indexterm"></a>
+ <a id="id780680" 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="id801573" 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="id593014" 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.
@@ -4010,20 +4016,20 @@ 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="#sn-ssh-installation">Section 11.2.3, “Enabling Remote Access with ssh”</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="id766482" class="indexterm"></a>
+ <a id="id944071" 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="id893303" class="indexterm"></a>
+ <a id="id679492" class="indexterm"></a>
Sets the system time zone to <em class="replaceable"><code><timezone></code></em> which may be any of the time zones listed by <code class="command">timeconfig</code>.
</div><pre class="screen">timezone [--utc] <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.
</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="id756624" class="indexterm"></a>
+ <a id="id599555" 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="id689457" class="indexterm"></a>
+ <a id="id476860" 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.
@@ -4040,7 +4046,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="id668024" class="indexterm"></a>
+ <a id="id867007" 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.
@@ -4049,7 +4055,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="id688201" class="indexterm"></a>
+ <a id="id761938" 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:
@@ -4065,7 +4071,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="id592987" 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="id634948" 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>.
@@ -4078,15 +4084,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="id574348" class="indexterm"></a>
+ <a id="id708167" 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="id844963" class="indexterm"></a>
- <a id="id798399" class="indexterm"></a>
+ <a id="id515112" class="indexterm"></a>
+ <a id="id495439" 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" id="s2-kickstart2-options-part-examples">15.4.1. Advanced Partitioning Example</h3></div></div></div><a id="id637849" 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" id="s2-kickstart2-options-part-examples">15.4.1. Advanced Partitioning Example</h3></div></div></div><a id="id599772" 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
@@ -4115,7 +4121,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" id="s1-kickstart2-packageselection">15.5. Package Selection</h2></div></div></div><a id="id723189" 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" id="s1-kickstart2-packageselection">15.5. Package Selection</h2></div></div></div><a id="id512706" 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).
@@ -4158,7 +4164,7 @@ docbook*
The --ignoredeps option has been deprecated. Dependencies are resolved automatically every time now.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">--ignoremissing</code></span></dt><dd><div class="para">
Ignore the missing packages and groups instead of halting the installation to ask if the installation should be aborted or continued. For example:
- </div><pre class="screen">%packages --ignoremissing</pre></dd></dl></div></div><div class="section" id="s1-kickstart2-preinstallconfig"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kickstart2-preinstallconfig">15.6. Pre-installation Script</h2></div></div></div><a id="id976870" class="indexterm"></a><a id="id597119" class="indexterm"></a><div class="para">
+ </div><pre class="screen">%packages --ignoremissing</pre></dd></dl></div></div><div class="section" id="s1-kickstart2-preinstallconfig"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kickstart2-preinstallconfig">15.6. Pre-installation Script</h2></div></div></div><a id="id600559" class="indexterm"></a><a id="id627952" 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.
@@ -4206,7 +4212,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" id="s1-kickstart2-postinstallconfig">15.7. Post-installation Script</h2></div></div></div><a id="id735173" class="indexterm"></a><a id="id541652" 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" id="s1-kickstart2-postinstallconfig">15.7. Post-installation Script</h2></div></div></div><a id="id668655" class="indexterm"></a><a id="id465580" 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.
@@ -4231,7 +4237,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" id="s1-kickstart2-putkickstarthere">15.8. Making the Kickstart File Available</h2></div></div></div><a id="id842364" 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" id="s1-kickstart2-putkickstarthere">15.8. Making the Kickstart File Available</h2></div></div></div><a id="id526168" 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
@@ -4243,19 +4249,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" id="s2-kickstart2-boot-media">15.8.1. Creating Kickstart Boot Media</h3></div></div></div><a id="id674591" class="indexterm"></a><a id="id603372" class="indexterm"></a><a id="id567480" 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" id="s2-kickstart2-boot-media">15.8.1. Creating Kickstart Boot Media</h3></div></div></div><a id="id999321" class="indexterm"></a><a id="id635341" class="indexterm"></a><a id="id988608" 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="id634335" class="indexterm"></a><div class="para">
+ </div><a id="id535046" 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="id592597" class="indexterm"></a><a id="id744813" class="indexterm"></a><div class="para">
+ </div><a id="id863625" class="indexterm"></a><a id="id944012" 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" id="s2-kickstart2-networkbased">15.8.2. Making the Kickstart File Available on the Network</h3></div></div></div><a id="id771464" class="indexterm"></a><a id="id588618" 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" id="s2-kickstart2-networkbased">15.8.2. Making the Kickstart File Available on the Network</h3></div></div></div><a id="id701363" class="indexterm"></a><a id="id648095" 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.
@@ -4265,25 +4271,25 @@ 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 Fedora16/vmlinuz
- append initrd=Fedora16/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" id="s1-kickstart2-install-tree">15.9. Making the Installation Tree Available</h2></div></div></div><a id="id572952" class="indexterm"></a><div class="para">
+ append initrd=Fedora16/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" id="s1-kickstart2-install-tree">15.9. Making the Installation Tree Available</h2></div></div></div><a id="id514686" 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="id869929" class="indexterm"></a><a id="id668160" class="indexterm"></a><div class="para">
+ </div><a id="id677233" class="indexterm"></a><a id="id577919" 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" id="s1-kickstart2-startinginstall">15.10. Starting a Kickstart Installation</h2></div></div></div><a id="id810899" class="indexterm"></a><a id="id810914" class="indexterm"></a><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important — Kickstart installations and firstboot</h2></div><div class="admonition"><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" id="s1-kickstart2-startinginstall">15.10. Starting a Kickstart Installation</h2></div></div></div><a id="id510266" class="indexterm"></a><a id="id844022" class="indexterm"></a><div class="important" xml:lang="en-US" lang="en-US"><div class="admonition_header"><h2>Important — Kickstart installations and firstboot</h2></div><div class="admonition"><div class="para">
<span class="application"><strong>Firstboot</strong></span> does not run after a system is installed from a Kickstart file unless a desktop and the X Window System were included in the installation and graphical login was enabled. Either specify a user with the <code class="option">user</code> option in the Kickstart file before installing additional systems from it (refer to <a class="xref" href="#s1-kickstart2-options">Section 15.4, “Kickstart Options”</a> for details) or log into the installed system with a virtual console as root and add users with the <code class="command">adduser</code> command.
</div></div></div><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><dt class="varlistentry"><span class="term">DVD and local storage</span></dt><dd><div class="para">
- <a id="id771347" class="indexterm"></a>
+ <a id="id867244" 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><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="id592607" class="indexterm"></a>
+ <a id="id780888" 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:
@@ -4541,37 +4547,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><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 Confi
guration</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="id522029" class="indexterm"></a><a id="id1349556" 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><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 Confi
guration</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="id785519" class="indexterm"></a><a id="id699531" 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 16. 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="id758240" class="indexterm"></a><div class="para">
+ </div><a id="id598208" 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" id="s1-redhat-config-kickstart-basic">16.1. Basic Configuration</h2></div></div></div><a id="id693539" 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" id="s1-redhat-config-kickstart-basic">16.1. Basic Configuration</h2></div></div></div><a id="id620482" 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="id563660" class="indexterm"></a><div class="para">
+ </div></div></div></div><h6>Figure 16.1. Basic Configuration</h6></div><br class="figure-break" /><a id="id858426" 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="id742094" class="indexterm"></a><div class="para">
+ </div><a id="id854872" class="indexterm"></a><div class="para">
Select the system keyboard type from the <span class="guimenu"><strong>Keyboard</strong></span> menu.
- </div><a id="id845804" class="indexterm"></a><div class="para">
+ </div><a id="id621398" 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="id625424" class="indexterm"></a><a id="id565964" class="indexterm"></a><div class="para">
+ </div><a id="id536412" class="indexterm"></a><a id="id705041" 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="id893681" class="indexterm"></a><div class="para">
+ </div><a id="id944264" 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="id767974" class="indexterm"></a><div class="para">
+ </div><a id="id694312" 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="id526432" class="indexterm"></a><div class="para">
+ </div><a id="id691688" 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" id="s1-redhat-config-kickstart-install">16.2. Installation Method</h2></div></div></div><a id="id650299" 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" id="s1-redhat-config-kickstart-install">16.2. Installation Method</h2></div></div></div><a id="id618195" 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.
@@ -4587,9 +4593,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 mediacheck</code> boot option as discussed in <a class="xref" href="#sn-boot-mediacheck">Section 11.6.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" id="s1-redhat-config-kickstart-bootloader">16.3. Boot Loader Options</h2></div></div></div><div class="figure" id="redhat-config-kickstart-bootloader-fig"><div class="figure-contents"><a id="id533984" 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" id="s1-redhat-config-kickstart-bootloader">16.3. Boot Loader Options</h2></div></div></div><div class="figure" id="redhat-config-kickstart-bootloader-fig"><div class="figure-contents"><a id="id538067" 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="id516910" 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="id867121" 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.
@@ -4601,7 +4607,7 @@ umount /mnt/temp
You can password protect the GRUB boot loader by configuring a GRUB password. Select <span class="guilabel"><strong>Use GRUB password</strong></span>, and enter a password in the <span class="guilabel"><strong>Password</strong></span> field. Type the same password in the <span class="guilabel"><strong>Confirm Password</strong></span> text field. To save the password as an encrypted password in the file, select <span class="guilabel"><strong>Encrypt GRUB 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. If the password you typed was already encrypted, unselect the encryption option.
</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" id="s1-redhat-config-kickstart-partitions">16.4. Partition Information</h2></div></div></div><a id="id812394" 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" id="s1-redhat-config-kickstart-partitions">16.4. Partition Information</h2></div></div></div><a id="id937860" 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.
@@ -4627,7 +4633,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" id="s3-redhat-config-kickstart-raid">16.4.1.1. Creating Software RAID Partitions</h4></div></div></div><a id="id531007" class="indexterm"></a><a id="id520668" 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" id="s3-redhat-config-kickstart-raid">16.4.1.1. Creating Software RAID Partitions</h4></div></div></div><a id="id747926" class="indexterm"></a><a id="id621904" 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.
@@ -4651,7 +4657,7 @@ 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" id="s1-redhat-config-kickstart-network">16.5. Network Configuration</h2></div></div></div><a id="id534527" 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" id="s1-redhat-config-kickstart-network">16.5. Network Configuration</h2></div></div></div><a id="id902738" 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.
@@ -4659,7 +4665,7 @@ umount /mnt/temp
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.
</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" id="s1-redhat-config-kickstart-auth">16.6. Authentication</h2></div></div></div><a id="id528126" 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" id="s1-redhat-config-kickstart-auth">16.6. Authentication</h2></div></div></div><a id="id703682" 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.
@@ -4679,7 +4685,7 @@ umount /mnt/temp
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" id="s1-redhat-config-kickstart-firewall">16.7. Firewall Configuration</h2></div></div></div><a id="id1325793" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s1-redhat-config-kickstart-firewall"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-redhat-config-kickstart-firewall">16.7. Firewall Configuration</h2></div></div></div><a id="id514709" 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
@@ -4693,15 +4699,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" id="s2-redhat-config-kickstart-firewall-selinux">16.7.1. SELinux Configuration</h3></div></div></div><a id="id713420" 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" id="s2-redhat-config-kickstart-firewall-selinux">16.7.1. SELinux Configuration</h3></div></div></div><a id="id895382" 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" id="s1-redhat-config-kickstart-xconfig">16.8. Display Configuration</h2></div></div></div><a id="id533855" 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" id="s1-redhat-config-kickstart-xconfig">16.8. Display Configuration</h2></div></div></div><a id="id578551" 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" id="s1-redhat-config-kickstart-pkgs">16.9. Package Selection</h2></div></div></div><a id="id742561" 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" id="s1-redhat-config-kickstart-pkgs">16.9. Package Selection</h2></div></div></div><a id="id868315" 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.
@@ -4709,7 +4715,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" id="s1-redhat-config-kickstart-prescript">16.10. Pre-Installation Script</h2></div></div></div><a id="id676806" 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" id="s1-redhat-config-kickstart-prescript">16.10. Pre-Installation Script</h2></div></div></div><a id="id590622" 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.
@@ -4723,7 +4729,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" id="s1-redhat-config-kickstart-postinstall">16.11. Post-Installation Script</h2></div></div></div><a id="id556979" 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" id="s1-redhat-config-kickstart-postinstall">16.11. Post-Installation Script</h2></div></div></div><a id="id784449" 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.
@@ -4743,7 +4749,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-together.within-column="always"><h3 class="title" id="s2-redhat-config-kickstart-interpreter">16.11.2. Use an Interpreter</h3></div></div></div><div class="para">
To specify a scripting language to use to execute the script, select the <span class="guilabel"><strong>Use an interpreter</strong></span> option and enter the interpreter in the text box beside it. For example, <strong class="userinput"><code>/usr/bin/python2.2</code></strong> can be specified for a Python script. This option corresponds to using <code class="command">%post --interpreter <em class="replaceable"><code>/usr/bin/python2.2</code></em></code> in your kickstart file.
- </div></div></div><div class="section" id="s1-redhat-config-kickstart-savefile"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-redhat-config-kickstart-savefile">16.12. Saving the File</h2></div></div></div><a id="id642804" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s1-redhat-config-kickstart-savefile"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-redhat-config-kickstart-savefile">16.12. Saving the File</h2></div></div></div><a id="id504942" class="indexterm"></a><div class="para">
To review the contents of the kickstart file after you have finished choosing your kickstart options, select <span class="guimenuitem"><strong>File</strong></span> => <span class="guimenuitem"><strong>Preview</strong></span> from the pull-down menu.
</div><div class="figure" id="redhat-config-kickstart-preview"><div class="figure-contents"><div class="mediaobject"><img src="images/ksconfig/ksconfig-confirm.png" alt="Preview" /><div class="longdesc"><div class="para">
Preview
@@ -4751,7 +4757,7 @@ umount /mnt/temp
To save the kickstart file, click the <span class="guibutton"><strong>Save to File</strong></span> button in the preview window. To save the file without previewing it, select <span class="guimenuitem"><strong>File</strong></span> => <span class="guimenuitem"><strong>Save File</strong></span> or press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>S</strong></span> . A dialog box appears. Select where to save the file.
</div><div class="para">
After saving the file, refer to <a class="xref" href="#s1-kickstart2-startinginstall">Section 15.10, “Starting a Kickstart Installation”</a> for information on how to start the kickstart installation.
- </div></div></div></div><div class="part" id="pt-After_installation"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part III. After installation</h1></div></div></div><div class="partintro" id="id885553"><div></div><div class="para">
+ </div></div></div></div><div class="part" id="pt-After_installation"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part III. After installation</h1></div></div></div><div class="partintro" id="id709615"><div></div><div class="para">
This part of the <em class="citetitle">Fedora Installation Guide</em> covers finalizing the installation, as well as some installation-related tasks that you might perform at some time in the future. These include:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
using a Fedora installation disk to rescue a damaged system.
@@ -4759,7 +4765,7 @@ umount /mnt/temp
upgrading to a new version of Fedora.
</div></li><li class="listitem"><div class="para">
removing Fedora from your computer.
- </div></li></ul></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="chapter"><a href="#ch-firstboot">17. Firstboot</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-firstboot-license">17.1. License Agreement</a></span></dt><dt><span class="section"><a href="#sn-firstboot-systemuser">17.2. Create User</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-firstboot-authentication">17.2.1. Authentication Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-firstboot-datetime">17.3. Date and Time</a></span></dt><dt><span class="section"><a href="#sn-smolt">17.4. Hardware Profile</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-next-steps">18. Your Next Steps</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-system-updating">18.1. Updating Your System</a></span></dt><dt><span class="section"><a href="#sn-finishing-upgrade">18.2. Finishing an Upgrade</a></span></dt><dt><sp
an class="section"><a href="#sn-switching-to-gui-login">18.3. Switching to a Graphical Login</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-enabling-repos">18.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">18.4. Subscribing to Fedora Announcements and News</a></span></dt><dt><span class="section"><a href="#sn-web-help">18.5. Finding Documentation and Support</a></span></dt><dt><span class="section"><a href="#sn-community">18.6. Joining the Fedora Community</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ap-rescuemode">19. Basic System Recovery</a></span></dt><dd><dl><dt><span class="section"><a href="#Rescue_Mode-x86">19.1. Rescue Mode</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-rescuemode-common-problems">19.1.1. Common Problems</a></span></dt><dt><span class="section"><a href="#s1-rescuemode-boot">19.1.2. Booting into Rescue
Mode</a></span></dt><dt><span class="section"><a href="#s1-rescuemode-booting-single">19.1.3. Booting into Single-User Mode</a></span></dt><dt><span class="section"><a href="#s1-rescuemode-booting-emergency">19.1.4. Booting into Emergency Mode</a></span></dt></dl></dd><dt><span class="section"><a href="#rescuemode_drivers">19.2. Using rescue mode to fix or work around driver problems</a></span></dt><dd><dl><dt><span class="section"><a href="#rescuemode_drivers-rpm">19.2.1. Using RPM to add, remove, or replace a driver</a></span></dt><dt><span class="section"><a href="#rescuemode_drivers-blacklisting">19.2.2. Blacklisting a driver</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-upgrade-x86">20. Upgrading Your Current System</a></span></dt><dd><dl><dt><span class="section"><a href="#id758868">20.1. Determining Whether to Upgrade or Re-Install</a></span></dt><dt><span class="section"><a href="#id1382392">20.2. Upgrading Your System</a></span></dt></dl
></dd><dt><span class="chapter"><a href="#ch-x86-uninstall">21. Removing Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-x86-uninstall-single">21.1. Fedora is the only operating system on the computer</a></span></dt><dt><span class="section"><a href="#sn-x86-uninstall-dual">21.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">21.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">21.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">21.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">21.3. Replacing Fedora with MS-DOS or legacy versions of Microsoft Windows</a></spa
n></dt></dl></dd></dl></div></div><div xml:lang="en-US" class="chapter" id="ch-firstboot" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 17. Firstboot</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sn-firstboot-license">17.1. License Agreement</a></span></dt><dt><span class="section"><a href="#sn-firstboot-systemuser">17.2. Create User</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-firstboot-authentication">17.2.1. Authentication Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-firstboot-datetime">17.3. Date and Time</a></span></dt><dt><span class="section"><a href="#sn-smolt">17.4. Hardware Profile</a></span></dt></dl></div><a id="id804804" class="indexterm"></a><div class="important"><div class="admonition_header"><h2>Important — Firstboot not available after text-mode installation</h2></div><div class="admonition"><div class="para">
+ </div></li></ul></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="chapter"><a href="#ch-firstboot">17. Firstboot</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-firstboot-license">17.1. License Agreement</a></span></dt><dt><span class="section"><a href="#sn-firstboot-systemuser">17.2. Create User</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-firstboot-authentication">17.2.1. Authentication Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-firstboot-datetime">17.3. Date and Time</a></span></dt><dt><span class="section"><a href="#sn-smolt">17.4. Hardware Profile</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-next-steps">18. Your Next Steps</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-system-updating">18.1. Updating Your System</a></span></dt><dt><span class="section"><a href="#sn-finishing-upgrade">18.2. Finishing an Upgrade</a></span></dt><dt><sp
an class="section"><a href="#sn-switching-to-gui-login">18.3. Switching to a Graphical Login</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-enabling-repos">18.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">18.4. Subscribing to Fedora Announcements and News</a></span></dt><dt><span class="section"><a href="#sn-web-help">18.5. Finding Documentation and Support</a></span></dt><dt><span class="section"><a href="#sn-community">18.6. Joining the Fedora Community</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ap-rescuemode">19. Basic System Recovery</a></span></dt><dd><dl><dt><span class="section"><a href="#Rescue_Mode-x86">19.1. Rescue Mode</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-rescuemode-common-problems">19.1.1. Common Problems</a></span></dt><dt><span class="section"><a href="#s1-rescuemode-boot">19.1.2. Booting into Rescue
Mode</a></span></dt><dt><span class="section"><a href="#s1-rescuemode-booting-single">19.1.3. Booting into Single-User Mode</a></span></dt><dt><span class="section"><a href="#s1-rescuemode-booting-emergency">19.1.4. Booting into Emergency Mode</a></span></dt></dl></dd><dt><span class="section"><a href="#rescuemode_drivers">19.2. Using rescue mode to fix or work around driver problems</a></span></dt><dd><dl><dt><span class="section"><a href="#rescuemode_drivers-rpm">19.2.1. Using RPM to add, remove, or replace a driver</a></span></dt><dt><span class="section"><a href="#rescuemode_drivers-blacklisting">19.2.2. Blacklisting a driver</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-upgrade-x86">20. Upgrading Your Current System</a></span></dt><dd><dl><dt><span class="section"><a href="#id487971">20.1. Determining Whether to Upgrade or Re-Install</a></span></dt><dt><span class="section"><a href="#id518799">20.2. Upgrading Your System</a></span></dt></dl>
</dd><dt><span class="chapter"><a href="#ch-x86-uninstall">21. Removing Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-x86-uninstall-single">21.1. Fedora is the only operating system on the computer</a></span></dt><dt><span class="section"><a href="#sn-x86-uninstall-dual">21.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">21.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">21.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">21.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">21.3. Replacing Fedora with MS-DOS or legacy versions of Microsoft Windows</a></span
></dt></dl></dd></dl></div></div><div xml:lang="en-US" class="chapter" id="ch-firstboot" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 17. Firstboot</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sn-firstboot-license">17.1. License Agreement</a></span></dt><dt><span class="section"><a href="#sn-firstboot-systemuser">17.2. Create User</a></span></dt><dd><dl><dt><span class="section"><a href="#sn-firstboot-authentication">17.2.1. Authentication Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#sn-firstboot-datetime">17.3. Date and Time</a></span></dt><dt><span class="section"><a href="#sn-smolt">17.4. Hardware Profile</a></span></dt></dl></div><a id="id466141" class="indexterm"></a><div class="important"><div class="admonition_header"><h2>Important — Firstboot not available after text-mode installation</h2></div><div class="admonition"><div class="para">
Firstboot is only available on systems after a graphical installation or after a kickstart installation where a desktop and the X window system were installed and graphical login was enabled. If you performed a text-mode installation or a kickstart installation that did not include a desktop and the X window system, the <span class="application"><strong>Firstboot</strong></span> configuration tool does not appear.
</div></div></div><div class="para">
<span class="application"><strong>Firstboot</strong></span> launches the first time that you start a new Fedora system. Use <span class="application"><strong>Firstboot</strong></span> to configure the system for use before you log in.
@@ -4811,7 +4817,7 @@ umount /mnt/temp
The <span class="guilabel"><strong>Advanced Options</strong></span> tab lets you enable other authentication mechanisms, including fingerprint readers, smart cards, and local access control in <code class="filename">/etc/security/access.conf</code>.
</div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/firstboot/fb-auth-advanced.png" alt="Firstboot authentication Advanced Options screen" /><div class="longdesc"><div class="para">
Firstboot authentication Advanced Options screen
- </div></div></div></div><h6>Figure 17.6. Firstboot authentication Advanced Options screen</h6></div><br class="figure-break" /></div></div><div class="section" id="sn-firstboot-datetime"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sn-firstboot-datetime">17.3. Date and Time</h2></div></div></div><a id="id1081329" class="indexterm"></a><div class="para">
+ </div></div></div></div><h6>Figure 17.6. Firstboot authentication Advanced Options screen</h6></div><br class="figure-break" /></div></div><div class="section" id="sn-firstboot-datetime"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sn-firstboot-datetime">17.3. Date and Time</h2></div></div></div><a id="id600636" class="indexterm"></a><div class="para">
Use this screen to adjust the date and time of the system clock. To change these settings after installation, click <span class="guimenu"><strong>System</strong></span> → <span class="guisubmenu"><strong>Administration</strong></span> → <span class="guimenuitem"><strong>Date & Time</strong></span>.
</div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/firstboot/fb-datetime.png" width="444" alt="Firstboot date and time screen" /><div class="longdesc"><div class="para">
Firstboot date and time screen
@@ -4831,7 +4837,7 @@ umount /mnt/temp
An update applet reminds you of updates when they are available. This applet is installed by default in Fedora. It checks for software updates from all configured repositories, and runs as a background service. It generates a notification message on the desktop if updates are found, and you can click the message to update your system's software.
</div><div class="para">
To update your system with the latest packages manually, use
- <a id="id529866" class="indexterm"></a>
+ <a id="id490764" class="indexterm"></a>
<span class="application"><strong>Update System</strong></span>:
</div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/nextsteps/updating.png" width="444" alt="Updating your system" /><div class="longdesc"><div class="para">
Updating your system screen
@@ -4844,11 +4850,11 @@ umount /mnt/temp
</div></li><li class="listitem"><div class="para">
If one or more updates require a system reboot, the update process displays a dialog with the option to <span class="guibutton"><strong>Reboot Now</strong></span>. Either select this option to reboot the system immediately, or <span class="guibutton"><strong>Cancel</strong></span> it and reboot the system at a more convenient time.
</div></li><li class="listitem"><div class="para">
- If a reboot is not required the update will conclude with a dialog that indicates that the System Update Completed and all selected updates have been successfully installed as well as a button to <span class="guibutton"><strong>Close</strong></span> <a id="id756805" class="indexterm"></a>
+ If a reboot is not required the update will conclude with a dialog that indicates that the System Update Completed and all selected updates have been successfully installed as well as a button to <span class="guibutton"><strong>Close</strong></span> <a id="id690106" class="indexterm"></a>
<span class="application"><strong>Update System</strong></span>
</div></li></ol></div><div class="para">
To update packages from the command-line, use the
- <a id="id622626" class="indexterm"></a>
+ <a id="id1373892" class="indexterm"></a>
<code class="command">yum</code> utility. Type this command to begin a full update of your system with <code class="command">yum</code>:
</div><pre class="screen">
<strong class="userinput"><code>su -c 'yum update'</code></strong></pre><div class="para">
@@ -4894,13 +4900,7 @@ umount /mnt/temp
</div><pre class="screen">
<code class="command">rm -f /etc/systemd/system/default.target</code>
<code class="command">ln -s /lib/systemd/system/graphical.target</code>
- <code class="command">/etc/systemd/system/default.target</code></pre></li><li class="step"><div class="para">
- Press the <span class="keycap"><strong>I</strong></span> key to enter <code class="literal">insert</code> mode.
- </div></li><li class="step"><div class="para">
- Find the line that includes the text <code class="literal">initdefault</code>. Change the numeral <code class="literal">3</code> to <code class="literal">5</code>.
- </div></li><li class="step"><div class="para">
- Type <code class="literal">:wq</code> and press the <span class="keycap"><strong>Enter</strong></span> key to save the file and exit the <span class="application"><strong>vi</strong></span> text editor.
- </div></li></ol></div><div class="para">
+ <code class="command">/etc/systemd/system/default.target</code></pre></li></ol></div><div class="para">
Reboot the system using the <code class="command">reboot</code> command. Your system will restart and present a graphical login.
</div><div class="para">
If you encounter any problems with the graphical login, refer to <a class="xref" href="#ch-trouble-x86">Chapter 10, <em>Troubleshooting Installation on an Intel or AMD System</em></a>.
@@ -5007,9 +5007,9 @@ gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release</pre><div class="para"
To make a difference, start here:
</div><div class="para">
<a href="http://join.fedoraproject.org/">http://join.fedoraproject.org/</a>
- </div></div></div><div xml:lang="en-US" class="chapter" id="ap-rescuemode" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 19. Basic System Recovery</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#Rescue_Mode-x86">19.1. Rescue Mode</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-rescuemode-common-problems">19.1.1. Common Problems</a></span></dt><dt><span class="section"><a href="#s1-rescuemode-boot">19.1.2. Booting into Rescue Mode</a></span></dt><dt><span class="section"><a href="#s1-rescuemode-booting-single">19.1.3. Booting into Single-User Mode</a></span></dt><dt><span class="section"><a href="#s1-rescuemode-booting-emergency">19.1.4. Booting into Emergency Mode</a></span></dt></dl></dd><dt><span class="section"><a href="#rescuemode_drivers">19.2. Using rescue mode to fix or work around driver problems</a></span></dt><dd><dl><dt><span class="section"><a href="#rescuemode_drivers-rpm">19.2.1. Using R
PM to add, remove, or replace a driver</a></span></dt><dt><span class="section"><a href="#rescuemode_drivers-blacklisting">19.2.2. Blacklisting a driver</a></span></dt></dl></dd></dl></div><a id="id581460" class="indexterm"></a><div class="para">
+ </div></div></div><div xml:lang="en-US" class="chapter" id="ap-rescuemode" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 19. Basic System Recovery</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#Rescue_Mode-x86">19.1. Rescue Mode</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-rescuemode-common-problems">19.1.1. Common Problems</a></span></dt><dt><span class="section"><a href="#s1-rescuemode-boot">19.1.2. Booting into Rescue Mode</a></span></dt><dt><span class="section"><a href="#s1-rescuemode-booting-single">19.1.3. Booting into Single-User Mode</a></span></dt><dt><span class="section"><a href="#s1-rescuemode-booting-emergency">19.1.4. Booting into Emergency Mode</a></span></dt></dl></dd><dt><span class="section"><a href="#rescuemode_drivers">19.2. Using rescue mode to fix or work around driver problems</a></span></dt><dd><dl><dt><span class="section"><a href="#rescuemode_drivers-rpm">19.2.1. Using R
PM to add, remove, or replace a driver</a></span></dt><dt><span class="section"><a href="#rescuemode_drivers-blacklisting">19.2.2. Blacklisting a driver</a></span></dt></dl></dd></dl></div><a id="id623704" class="indexterm"></a><div class="para">
When things go wrong, there are ways to fix problems. However, these methods require that you understand the system well. This chapter describes how to boot into rescue mode, single-user mode, and emergency mode, where you can use your own knowledge to repair the system.
- </div><div class="section" id="Rescue_Mode-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="Rescue_Mode-x86">19.1. Rescue Mode</h2></div></div></div><div class="section" id="s1-rescuemode-common-problems"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-rescuemode-common-problems">19.1.1. Common Problems</h3></div></div></div><a id="id539165" class="indexterm"></a><div class="para">
+ </div><div class="section" id="Rescue_Mode-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="Rescue_Mode-x86">19.1. Rescue Mode</h2></div></div></div><div class="section" id="s1-rescuemode-common-problems"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-rescuemode-common-problems">19.1.1. Common Problems</h3></div></div></div><a id="id613636" class="indexterm"></a><div class="para">
You might need to boot into one of these recovery modes for any of the following reasons:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
You are unable to boot normally into Fedora (runlevel 3 or 5).
@@ -5017,23 +5017,23 @@ gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release</pre><div class="para"
You are having hardware or software problems, and you want to get a few important files off of your system's hard drive.
</div></li><li class="listitem"><div class="para">
You forgot the root password.
- </div></li></ul></div><div class="section" id="s2-rescuemode-whatis-unable-boot"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-rescuemode-whatis-unable-boot">19.1.1.1. Unable to Boot into Fedora</h4></div></div></div><a id="id759826" class="indexterm"></a><a id="id810881" class="indexterm"></a><div class="para">
+ </div></li></ul></div><div class="section" id="s2-rescuemode-whatis-unable-boot"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-rescuemode-whatis-unable-boot">19.1.1.1. Unable to Boot into Fedora</h4></div></div></div><a id="id863510" class="indexterm"></a><a id="id863494" class="indexterm"></a><div class="para">
This problem is often caused by the installation of another operating system after you have installed Fedora. Some other operating systems assume that you have no other operating system(s) on your computer. They overwrite the Master Boot Record (MBR) that originally contained the GRUB boot loader. If the boot loader is overwritten in this manner, you cannot boot Fedora unless you can get into rescue mode and reconfigure the boot loader.
</div><div class="para">
Another common problem occurs when using a partitioning tool to resize a partition or create a new partition from free space after installation, and it changes the order of your partitions. If the partition number of your <code class="filename">/</code> partition changes, the boot loader might not be able to find it to mount the partition. To fix this problem, boot in rescue mode and modify the <code class="filename">/boot/grub/grub.conf</code> file.
</div><div class="para">
For instructions on how to reinstall the GRUB boot loader from a rescue environment, refer to <a class="xref" href="#s2-rescuemode-boot-reinstall-bootloader">Section 19.1.2.1, “Reinstalling the Boot Loader”</a>.
- </div></div><div class="section" id="s2-rescuemode-hardware-troubles"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-rescuemode-hardware-troubles">19.1.1.2. Hardware/Software Problems</h4></div></div></div><a id="id735590" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-rescuemode-hardware-troubles"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-rescuemode-hardware-troubles">19.1.1.2. Hardware/Software Problems</h4></div></div></div><a id="id730931" class="indexterm"></a><div class="para">
This category includes a wide variety of different situations. Two examples include failing hard drives and specifying an invalid root device or kernel in the boot loader configuration file. If either of these occur, you might not be able to reboot into Fedora. However, if you boot into one of the system recovery modes, you might be able to resolve the problem or at least get copies of your most important files.
- </div></div><div class="section" id="s2-rescuemode-root-password"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-rescuemode-root-password">19.1.1.3. Root Password</h4></div></div></div><a id="id795601" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-rescuemode-root-password"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-rescuemode-root-password">19.1.1.3. Root Password</h4></div></div></div><a id="id623674" class="indexterm"></a><div class="para">
What can you do if you forget your root password? To reset it to a different password, boot into rescue mode or single-user mode, and use the <code class="command">passwd</code> command to reset the root password.
- </div></div></div><div class="section" id="s1-rescuemode-boot"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-rescuemode-boot">19.1.2. Booting into Rescue Mode</h3></div></div></div><a id="id795588" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s1-rescuemode-boot"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-rescuemode-boot">19.1.2. Booting into Rescue Mode</h3></div></div></div><a id="id794550" class="indexterm"></a><div class="para">
Rescue mode provides the ability to boot a small Fedora environment entirely from CD-ROM, or some other boot method, instead of the system's hard drive.
</div><div class="para">
As the name implies, rescue mode is provided to rescue you from something. During normal operation, your Fedora system uses files located on your system's hard drive to do everything — run programs, store your files, and more.
</div><div class="para">
However, there may be times when you are unable to get Fedora running completely enough to access files on your system's hard drive. Using rescue mode, you can access the files stored on your system's hard drive, even if you cannot actually run Fedora from that hard drive.
- </div><a id="id754587" class="indexterm"></a><div class="para">
+ </div><a id="id794530" class="indexterm"></a><div class="para">
To boot into rescue mode, you must be able to boot the system using one of the following methods<sup>[<a id="boot-media" href="#ftn.boot-media" class="footnote">5</a>]</sup>:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
By booting the system from a boot CD-ROM or DVD.
@@ -5076,7 +5076,7 @@ gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release</pre><div class="para"
</div><pre class="screen">
<code class="command">pvdisplay</code></pre><pre class="screen">
<code class="command">vgdisplay</code></pre><pre class="screen">
-<code class="command">lvdisplay</code></pre><a id="id567348" class="indexterm"></a><div class="para">
+<code class="command">lvdisplay</code></pre><a id="id596099" class="indexterm"></a><div class="para">
From the prompt, you can run many useful commands, such as:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">ssh</code>, <code class="command">scp</code>, and <code class="command">ping</code> if the network is started
@@ -5088,7 +5088,7 @@ gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release</pre><div class="para"
<code class="command">rpm</code> for installing or upgrading software
</div></li><li class="listitem"><div class="para">
<code class="command">vi</code> for editing text files
- </div></li></ul></div><div class="section" id="s2-rescuemode-boot-reinstall-bootloader"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-rescuemode-boot-reinstall-bootloader">19.1.2.1. Reinstalling the Boot Loader</h4></div></div></div><a id="id594123" class="indexterm"></a><a id="id642236" class="indexterm"></a><div class="para">
+ </div></li></ul></div><div class="section" id="s2-rescuemode-boot-reinstall-bootloader"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-rescuemode-boot-reinstall-bootloader">19.1.2.1. Reinstalling the Boot Loader</h4></div></div></div><a id="id675542" class="indexterm"></a><a id="id478377" class="indexterm"></a><div class="para">
In many cases, the GRUB boot loader can mistakenly be deleted, corrupted, or replaced by other operating systems.
</div><div class="para">
The following steps detail the process on how GRUB is reinstalled on the master boot record:
@@ -5104,7 +5104,7 @@ gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release</pre><div class="para"
Review the <code class="filename">/boot/grub/grub.conf</code> file, as additional entries may be needed for GRUB to control additional operating systems.
</div></li><li class="listitem"><div class="para">
Reboot the system.
- </div></li></ul></div></div></div><div class="section" id="s1-rescuemode-booting-single"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-rescuemode-booting-single">19.1.3. Booting into Single-User Mode</h3></div></div></div><a id="id645923" class="indexterm"></a><a id="id887571" class="indexterm"></a><a id="id554526" class="indexterm"></a><div class="para">
+ </div></li></ul></div></div></div><div class="section" id="s1-rescuemode-booting-single"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-rescuemode-booting-single">19.1.3. Booting into Single-User Mode</h3></div></div></div><a id="id877251" class="indexterm"></a><a id="id849201" class="indexterm"></a><a id="id600666" class="indexterm"></a><div class="para">
One of the advantages of single-user mode is that you do not need a boot CD-ROM; however, it does not give you the option to mount the file systems as read-only or not mount them at all.
</div><div class="para">
If your system boots, but does not allow you to log in when it has completed booting, try single-user mode.
@@ -5118,11 +5118,11 @@ gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release</pre><div class="para"
Select <span class="guilabel"><strong>Fedora</strong></span> with the version of the kernel that you wish to boot and type <code class="command">a</code> to append the line.
</div></li><li class="listitem"><div class="para">
Go to the end of the line and type <strong class="userinput"><code>single</code></strong> as a separate word (press the <span class="keycap"><strong>Spacebar</strong></span> and then type <strong class="userinput"><code>single</code></strong>). Press <span class="keycap"><strong>Enter</strong></span> to exit edit mode.
- </div></li></ol></div></div><div class="section" id="s1-rescuemode-booting-emergency"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-rescuemode-booting-emergency">19.1.4. Booting into Emergency Mode</h3></div></div></div><a id="id596756" class="indexterm"></a><a id="id699807" class="indexterm"></a><div class="para">
+ </div></li></ol></div></div><div class="section" id="s1-rescuemode-booting-emergency"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-rescuemode-booting-emergency">19.1.4. Booting into Emergency Mode</h3></div></div></div><a id="id709807" class="indexterm"></a><a id="id564862" class="indexterm"></a><div class="para">
In emergency mode, you are booted into the most minimal environment possible. The root file system is mounted read-only and almost nothing is set up. The main advantage of emergency mode over single-user mode is that the <code class="command">init</code> files are not loaded. If <code class="command">init</code> is corrupted or not working, you can still mount file systems to recover data that could be lost during a re-installation.
</div><div class="para">
To boot into emergency mode, use the same method as described for single-user mode in <a class="xref" href="#s1-rescuemode-booting-single">Section 19.1.3, “Booting into Single-User Mode”</a> with one exception, replace the keyword <strong class="userinput"><code>single</code></strong> with the keyword <strong class="userinput"><code>emergency</code></strong>.
- </div></div></div><div xml:lang="en-US" class="section" id="rescuemode_drivers" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="rescuemode_drivers">19.2. Using rescue mode to fix or work around driver problems</h2></div></div></div><a id="id640930" class="indexterm"></a><a id="id770412" class="indexterm"></a><a id="id1265223" class="indexterm"></a><a id="id968793" class="indexterm"></a><a id="id786157" class="indexterm"></a><a id="id590380" class="indexterm"></a><div class="para">
+ </div></div></div><div xml:lang="en-US" class="section" id="rescuemode_drivers" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="rescuemode_drivers">19.2. Using rescue mode to fix or work around driver problems</h2></div></div></div><a id="id800759" class="indexterm"></a><a id="id597956" class="indexterm"></a><a id="id602950" class="indexterm"></a><a id="id516099" class="indexterm"></a><a id="id524176" class="indexterm"></a><a id="id679654" class="indexterm"></a><div class="para">
A malfunctioning or missing driver can prevent a system from booting normally. Rescue mode provides an environment in which you can add, remove, or replace a driver even when the system fails to boot. Wherever possible, we recommend that you use the <span class="application"><strong>RPM</strong></span> package manager to remove malfunctioning drivers or to add updated or missing drivers. If you cannot remove a malfunctioning driver for some reason, you can instead <em class="firstterm">blacklist</em> the driver so that it does not load at boot time.
</div><div class="para">
Note that when you install a driver from a driver disc, the driver disc updates all initramfs images on the system to use this driver. If a problem with a driver prevents a system from booting, you cannot rely on booting the system from another initramfs image.
@@ -5168,9 +5168,9 @@ gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release</pre><div class="para"
Reboot the system. You no longer need to supply <code class="option">rdblacklist</code> manually as a kernel option until you next update the default kernel. If you update the default kernel before the problem with the driver has been fixed, you must edit <code class="filename">grub.conf</code> again to ensure that the faulty driver is not loaded at boot time.
</div></li></ol></div></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote" id="boot-media"><div class="para"><sup>[<a id="ftn.boot-media" href="#boot-media" class="para">5</a>] </sup>
Refer to the earlier sections of this guide for more details.
- </div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-upgrade-x86" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 20. Upgrading Your Current System</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#id758868">20.1. Determining Whether to Upgrade or Re-Install</a></span></dt><dt><span class="section"><a href="#id1382392">20.2. Upgrading Your System</a></span></dt></dl></div><div class="para">
+ </div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-upgrade-x86" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 20. Upgrading Your Current System</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#id487971">20.1. Determining Whether to Upgrade or Re-Install</a></span></dt><dt><span class="section"><a href="#id518799">20.2. Upgrading Your System</a></span></dt></dl></div><div class="para">
This chapter explains the various methods available for upgrading your Fedora system.
-</div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id758868">20.1. Determining Whether to Upgrade or Re-Install</h2></div></div></div><a id="id935485" class="indexterm"></a><a id="id689486" class="indexterm"></a><div class="para">
+</div><div xml:lang="en-US" class="section" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id487971">20.1. Determining Whether to Upgrade or Re-Install</h2></div></div></div><a id="id696887" class="indexterm"></a><a id="id558665" class="indexterm"></a><div class="para">
While upgrading from Fedora 15 is supported, you are more likely to have a consistent experience by backing up your data and then installing this release of Fedora 16 over your previous Fedora installation.
</div><div class="para">
To upgrade from Fedora 15 you should bring your system up to date before performing the upgrade.
@@ -5198,7 +5198,7 @@ gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release</pre><div class="para"
Some upgraded packages may require the installation of other packages for proper operation. If you choose to customize your packages to upgrade, you may be required to resolve dependency problems. Otherwise, the upgrade procedure takes care of these dependencies, but it may need to install additional packages which are not on your system.
</div><div class="para">
Depending on how you have partitioned your system, the upgrade program may prompt you to add an additional swap file. If the upgrade program does not detect a swap file that equals twice your RAM, it asks you if you would like to add a new swap file. If your system does not have a lot of RAM (less than 256 MB), it is recommended that you add this swap file.
- </div><a id="id676695" class="indexterm"></a><a id="id496951" class="indexterm"></a></div><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id1382392">20.2. Upgrading Your System</h2></div></div></div><div class="para">
+ </div><a id="id573151" class="indexterm"></a><a id="id565914" class="indexterm"></a></div><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id518799">20.2. Upgrading Your System</h2></div></div></div><div class="para">
In most cases, the simplest way to upgrade an existing Fedora installation is with the <span class="application"><strong>preupgrade</strong></span> tool. When a new version of Fedora is available, <span class="application"><strong>preupgrade</strong></span> downloads the packages necessary to upgrade your installation, and initiates the upgrade process.
</div><div class="para">
Install <span class="application"><strong>preupgrade</strong></span> with your graphical package manager, or type <code class="command">yum install preupgrade</code> at the command line and press <span class="keycap"><strong>Enter</strong></span>.
@@ -5218,7 +5218,7 @@ gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release</pre><div class="para"
To perform an upgrade, select <span class="guilabel"><strong>Perform an upgrade of an existing installation</strong></span>. Click <span class="guibutton"><strong>Next</strong></span> when you are ready to begin your upgrade.
</div><div class="para">
To re-install your system, select <span class="guilabel"><strong>Perform a new Fedora installation</strong></span> and refer to <a class="xref" href="#ch-guimode-x86">Chapter 9, <em>Installing using anaconda</em></a> for further instructions.
- </div></div></div><div xml:lang="en-US" class="chapter" id="ch-x86-uninstall" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 21. Removing Fedora</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sn-x86-uninstall-single">21.1. Fedora is the only operating system on the computer</a></span></dt><dt><span class="section"><a href="#sn-x86-uninstall-dual">21.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">21.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">21.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">21.2.3. Your computer dual-boots Fedora and a different Linux distribution</a></span></dt></dl></dd><dt><span class="section"><a h
ref="#sn-x86-uninstall-legacy">21.3. Replacing Fedora with MS-DOS or legacy versions of Microsoft Windows</a></span></dt></dl></div><a id="id669784" class="indexterm"></a><a id="id669769" class="indexterm"></a><div class="para">
+ </div></div></div><div xml:lang="en-US" class="chapter" id="ch-x86-uninstall" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 21. Removing Fedora</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sn-x86-uninstall-single">21.1. Fedora is the only operating system on the computer</a></span></dt><dt><span class="section"><a href="#sn-x86-uninstall-dual">21.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">21.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">21.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">21.2.3. Your computer dual-boots Fedora and a different Linux distribution</a></span></dt></dl></dd><dt><span class="section"><a h
ref="#sn-x86-uninstall-legacy">21.3. Replacing Fedora with MS-DOS or legacy versions of Microsoft Windows</a></span></dt></dl></div><a id="id506648" class="indexterm"></a><a id="id874150" class="indexterm"></a><div class="para">
We respect your freedom to choose an operating system for your computer. This section explains how to uninstall Fedora.
</div><div class="warning"><div class="admonition_header"><h2> These instructions may destroy data! </h2></div><div class="admonition"><div class="para">
If you have data from Fedora that you want to keep, back it up before you proceed. Write your data to CD, DVD, external hard disk, or other storage device.
@@ -5523,15 +5523,15 @@ sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)</pre></li><li class="step
Once you have removed the Linux partitions and made all of the changes you need to make, type <code class="command">quit</code> to quit <code class="command">parted</code>.
</div><div class="para">
After quitting <code class="command">parted</code>, type <code class="command">exit</code> at the boot prompt to exit rescue mode and reboot your system, instead of continuing with the installation. The system should reboot automatically. If it does not, you can reboot your computer using <span class="keycap"><strong>Control</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Delete</strong></span> .
- </div></div></div></div><div class="part" id="pt-Technical_appendixes"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part IV. Technical appendixes</h1></div></div></div><div class="partintro" id="id512071"><div></div><div class="para">
+ </div></div></div></div><div class="part" id="pt-Technical_appendixes"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part IV. Technical appendixes</h1></div></div></div><div class="partintro" id="id857874"><div></div><div class="para">
The appendixes in this section do not contain instructions that tell you how to install Fedora. Instead, they provide technical background that you might find helpful to understand the options that Fedora offers you at various points in the installation process.
- </div><div class="toc"><p><strong>Table of Contents</strong></p><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="#id1380380">C.1. What is block device encryption? </a></span></dt><dt><span class="section"><a href="#id914008">C.2. Encrypting block de
vices using dm-crypt/LUKS </a></span></dt><dd><dl><dt><span class="section"><a href="#id621867">C.2.1. Overview of LUKS </a></span></dt><dt><span class="section"><a href="#id1380455">C.2.2. How will I access the encrypted devices after installation? (System Startup) </a></span></dt><dt><span class="section"><a href="#id912117">C.2.3. Choosing a Good Passphrase </a></span></dt></dl></dd><dt><span class="section"><a href="#id840120">C.3. Creating Encrypted Block Devices in Anaconda </a></span></dt><dd><dl><dt><span class="section"><a href="#id657114">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="#id713599">C.4. Creating Encrypted Block D
evices on the Installed System After Installation </a></span></dt><dd><dl><dt><span class="section"><a href="#id654443">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="#id722647">C.4.3. Format the device as a dm-crypt/LUKS encrypted device </a></span></dt><dt><span class="section"><a href="#id624790">C.4.4. Create a mapping to allow access to the device's decrypted contents </a></span></dt><dt><span class="section"><a href="#id518906">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="#id663334">C.4.6. Add the mapping information to <code class="filename">/etc/crypttab</code></a></span></dt><dt><span class="section"><a href="#id818056">C.4.7. Add an entry to <code class="filename">/etc/fstab</code></a></sp
an></dt></dl></dd><dt><span class="section"><a href="#id751166">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="#id955380">C.5.2. Add a new passphrase to an existing device </a></span></dt><dt><span class="section"><a href="#id670979">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="#ch-grub">E. The GRUB Boot Loader</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-grub-arch">E.1. Boot Loaders and System Architecture</a></span></dt><dt><span class="section"><a href="#s1-grub-whatis">E.2. GRUB</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-grub-whatis-booting-bios">E.2.1. GRUB and the boot p
rocess on BIOS-based x86 systems</a></span></dt><dt><span class="section"><a href="#s2-grub-whatis-booting-uefi">E.2.2. GRUB and the boot process on UEFI-based x86 systems</a></span></dt><dt><span class="section"><a href="#s2-grub-whatis-features">E.2.3. Features of GRUB</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-grub-installing">E.3. Installing GRUB</a></span></dt><dt><span class="section"><a href="#s1-grub-terminology">E.4. GRUB Terminology</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-grub-terminology-devices">E.4.1. Device Names</a></span></dt><dt><span class="section"><a href="#s2-grub-terminology-files">E.4.2. File Names and Blocklists</a></span></dt><dt><span class="section"><a href="#s2-grub-terminology-rootfs">E.4.3. The Root File System and GRUB</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-grub-interfaces">E.5. GRUB Interfaces</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-grub-interfaces-ordero
fuse">E.5.1. Interfaces Load Order</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-grub-commands">E.6. GRUB Commands</a></span></dt><dt><span class="section"><a href="#s1-grub-configfile">E.7. GRUB Menu Configuration File</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-grub-configfile-structure">E.7.1. Configuration File Structure</a></span></dt><dt><span class="section"><a href="#s2-grub-configfile-commands">E.7.2. Configuration File Directives</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-grub-runlevels">E.8. Changing Runlevels at Boot Time</a></span></dt><dt><span class="section"><a href="#s1-grub-additional-resources">E.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-grub-installed-documentation">E.9.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-grub-useful-websites">E.9.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><
a href="#ch-boot-init-shutdown">F. Boot Process, Init, and Shutdown</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-boot-process-basics">F.1. The Boot Process</a></span></dt><dt><span class="section"><a href="#s1-boot-init-shutdown-process">F.2. A Detailed Look at the Boot Process</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-firmware_interface">F.2.1. The firmware interface</a></span></dt><dt><span class="section"><a href="#s2-boot-init-shutdown-loader">F.2.2. The Boot Loader</a></span></dt><dt><span class="section"><a href="#s2-boot-init-shutdown-kernel">F.2.3. The Kernel</a></span></dt><dt><span class="section"><a href="#s2-boot-init-shutdown-init">F.2.4. The <code class="command">/sbin/init</code> Program</a></span></dt><dt><span class="section"><a href="#s2-boot-init-shutdown-jobs">F.2.5. Job definitions</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-boot-init-shutdown-run-boot">F.3. Running Additional Programs at Boot Ti
me</a></span></dt><dt><span class="section"><a href="#s1-boot-init-shutdown-sysv">F.4. SysV Init Runlevels</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-init-boot-shutdown-rl">F.4.1. Runlevels</a></span></dt><dt><span class="section"><a href="#s2-boot-init-shutdown-sysv-util">F.4.2. Runlevel Utilities</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-boot-init-shutdown-shutdown">F.5. Shutting Down</a></span></dt></dl></dd><dt><span class="appendix"><a href="#ap-techref">G. Other Technical Documentation</a></span></dt></dl></div></div><div xml:lang="en-US" class="appendix" id="ch-partitions-x86" lang="en-US"><div class="titlepage"><div><div><h1 class="title">An Introduction to Disk Partitions</h1></div></div></div><a id="id763338" class="indexterm"></a><a id="id646306" 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 class="toc"><p><strong>Table of Contents</strong></p><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="#id675605">C.1. What is block device encryption? </a></span></dt><dt><span class="section"><a href="#id577927">C.2. Encrypting block dev
ices using dm-crypt/LUKS </a></span></dt><dd><dl><dt><span class="section"><a href="#id729434">C.2.1. Overview of LUKS </a></span></dt><dt><span class="section"><a href="#id604599">C.2.2. How will I access the encrypted devices after installation? (System Startup) </a></span></dt><dt><span class="section"><a href="#id790119">C.2.3. Choosing a Good Passphrase </a></span></dt></dl></dd><dt><span class="section"><a href="#id858295">C.3. Creating Encrypted Block Devices in Anaconda </a></span></dt><dd><dl><dt><span class="section"><a href="#id483190">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="#id575929">C.4. Creating Encrypted Block Dev
ices on the Installed System After Installation </a></span></dt><dd><dl><dt><span class="section"><a href="#id642391">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="#id713433">C.4.3. Format the device as a dm-crypt/LUKS encrypted device </a></span></dt><dt><span class="section"><a href="#id624005">C.4.4. Create a mapping to allow access to the device's decrypted contents </a></span></dt><dt><span class="section"><a href="#id615432">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="#id710988">C.4.6. Add the mapping information to <code class="filename">/etc/crypttab</code></a></span></dt><dt><span class="section"><a href="#id529126">C.4.7. Add an entry to <code class="filename">/etc/fstab</code></a></span
></dt></dl></dd><dt><span class="section"><a href="#id590845">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="#id674776">C.5.2. Add a new passphrase to an existing device </a></span></dt><dt><span class="section"><a href="#id645286">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="#ch-grub">E. The GRUB Boot Loader</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-grub-arch">E.1. Boot Loaders and System Architecture</a></span></dt><dt><span class="section"><a href="#s1-grub-whatis">E.2. GRUB</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-grub-whatis-booting-bios">E.2.1. GRUB and the boot pro
cess on BIOS-based x86 systems</a></span></dt><dt><span class="section"><a href="#s2-grub-whatis-booting-uefi">E.2.2. GRUB and the boot process on UEFI-based x86 systems</a></span></dt><dt><span class="section"><a href="#s2-grub-whatis-features">E.2.3. Features of GRUB</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-grub-installing">E.3. Installing GRUB</a></span></dt><dt><span class="section"><a href="#s1-grub-terminology">E.4. GRUB Terminology</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-grub-terminology-devices">E.4.1. Device Names</a></span></dt><dt><span class="section"><a href="#s2-grub-terminology-files">E.4.2. File Names and Blocklists</a></span></dt><dt><span class="section"><a href="#s2-grub-terminology-rootfs">E.4.3. The Root File System and GRUB</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-grub-interfaces">E.5. GRUB Interfaces</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-grub-interfaces-orderofu
se">E.5.1. Interfaces Load Order</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-grub-commands">E.6. GRUB Commands</a></span></dt><dt><span class="section"><a href="#s1-grub-configfile">E.7. GRUB Menu Configuration File</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-grub-configfile-structure">E.7.1. Configuration File Structure</a></span></dt><dt><span class="section"><a href="#s2-grub-configfile-commands">E.7.2. Configuration File Directives</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-grub-runlevels">E.8. Changing Runlevels at Boot Time</a></span></dt><dt><span class="section"><a href="#s1-grub-additional-resources">E.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-grub-installed-documentation">E.9.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-grub-useful-websites">E.9.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a
href="#ch-boot-init-shutdown">F. Boot Process, Init, and Shutdown</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-boot-process-basics">F.1. The Boot Process</a></span></dt><dt><span class="section"><a href="#s1-boot-init-shutdown-process">F.2. A Detailed Look at the Boot Process</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-firmware_interface">F.2.1. The firmware interface</a></span></dt><dt><span class="section"><a href="#s2-boot-init-shutdown-loader">F.2.2. The Boot Loader</a></span></dt><dt><span class="section"><a href="#s2-boot-init-shutdown-kernel">F.2.3. The Kernel</a></span></dt><dt><span class="section"><a href="#s2-boot-init-shutdown-init">F.2.4. The <code class="command">/sbin/init</code> Program</a></span></dt><dt><span class="section"><a href="#s2-boot-init-shutdown-jobs">F.2.5. Job definitions</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-boot-init-shutdown-run-boot">F.3. Running Additional Programs at Boot Time
</a></span></dt><dt><span class="section"><a href="#s1-boot-init-shutdown-sysv">F.4. SysV Init Runlevels</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-init-boot-shutdown-rl">F.4.1. Runlevels</a></span></dt><dt><span class="section"><a href="#s2-boot-init-shutdown-sysv-util">F.4.2. Runlevel Utilities</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-boot-init-shutdown-shutdown">F.5. Shutting Down</a></span></dt></dl></dd><dt><span class="appendix"><a href="#ap-techref">G. Other Technical Documentation</a></span></dt></dl></div></div><div xml:lang="en-US" class="appendix" id="ch-partitions-x86" lang="en-US"><div class="titlepage"><div><div><h1 class="title">An Introduction to Disk Partitions</h1></div></div></div><a id="id725843" class="indexterm"></a><a id="id942995" 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">
This appendix is not necessarily applicable to non-x86-based architectures. However, the general concepts mentioned here may apply.
</div></div></div><div class="para">
This appendix is not necessarily applicable to non-x86-based architectures. However, the general concepts mentioned here may apply.
</div><div class="para">
If you are reasonably comfortable with disk partitions, you could skip ahead to <a class="xref" href="#s2-partitions-make-room-x86">Section A.1.4, “Making Room For Fedora”</a>, for more information on the process of freeing up disk space to prepare for a Fedora installation. This section also discusses the partition naming scheme used by Linux systems, sharing disk space with other operating systems, and related topics.
- </div><div class="section" id="s1-partitions-concepts-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-partitions-concepts-x86">A.1. Hard Disk Basic Concepts</h2></div></div></div><a id="id499757" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s1-partitions-concepts-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-partitions-concepts-x86">A.1. Hard Disk Basic Concepts</h2></div></div></div><a id="id779409" class="indexterm"></a><div class="para">
Hard disks perform a very simple function — they store data and reliably retrieve it on command.
</div><div class="para">
When discussing issues such as disk partitioning, it is important to know a bit about the underlying hardware. Unfortunately, it is easy to become bogged down in details. Therefore, this appendix uses a simplified diagram of a disk drive to help explain what is really happening when a disk drive is partitioned. <a class="xref" href="#fig-partitions-unused-drive-x86">Figure A.1, “An Unused Disk Drive”</a>, shows a brand-new, unused disk drive.
@@ -5539,7 +5539,7 @@ sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)</pre></li><li class="step
Image of an unused disk drive.
</div></div></div></div><h6>Figure A.1. An Unused Disk Drive</h6></div><br class="figure-break" /><div class="para">
Not much to look at, is it? But if we are talking about disk drives on a basic level, it is adequate. Say that we would like to store some data on this drive. As things stand now, it will not work. There is something we need to do first.
-</div><div class="section" id="s2-partitions-filesystem-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-partitions-filesystem-x86">A.1.1. It is Not What You Write, it is How You Write It</h3></div></div></div><a id="id913261" class="indexterm"></a><a id="id565824" class="indexterm"></a><div class="para">
+</div><div class="section" id="s2-partitions-filesystem-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-partitions-filesystem-x86">A.1.1. It is Not What You Write, it is How You Write It</h3></div></div></div><a id="id647791" class="indexterm"></a><a id="id621303" class="indexterm"></a><div class="para">
Experienced computer users probably got this one on the first try. We need to <em class="firstterm">format</em> the drive. Formatting (usually known as "making a <em class="firstterm">file system</em>") writes information to the drive, creating order out of the empty space in an unformatted drive.
</div><div class="figure" id="fig-partitions-formatted-drive-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/partitions/formatted-drive.png" alt="Disk Drive with a File System" /><div class="longdesc"><div class="para">
Image of a formatted disk drive.
@@ -5548,7 +5548,7 @@ sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)</pre></li><li class="step
</div><div xml:lang="en-US" class="itemizedlist" lang="en-US"><ul><li class="listitem"><div class="para">
A small percentage of the drive's available space is used to store file system-related data and can be considered as overhead.
</div></li><li class="listitem"><div class="para">
- A file system splits the remaining space into small, consistently-sized segments. For Linux, these segments are known as <em class="firstterm">blocks</em>. <sup>[<a id="id551010" href="#ftn.id551010" class="footnote">6</a>]</sup>
+ A file system splits the remaining space into small, consistently-sized segments. For Linux, these segments are known as <em class="firstterm">blocks</em>. <sup>[<a id="id750049" href="#ftn.id750049" class="footnote">6</a>]</sup>
</div></li></ul></div><div class="para">
Given that file systems make things like directories and files possible, these trade-offs are usually seen as a small price to pay.
</div><div class="para">
@@ -5563,7 +5563,7 @@ sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)</pre></li><li class="step
As <a class="xref" href="#fig-partitions-used-formatted-dr-x86">Figure A.4, “Disk Drive with Data Written to It”</a>, shows, some of the previously-empty blocks are now holding data. However, by just looking at this picture, we cannot determine exactly how many files reside on this drive. There may only be one file or many, as all files use at least one block and some files use multiple blocks. Another important point to note is that the used blocks do not have to form a contiguous region; used and unused blocks may be interspersed. This is known as <em class="firstterm">fragmentation</em>. Fragmentation can play a part when attempting to resize an existing partition.
</div><div class="para">
As with most computer-related technologies, disk drives changed over time after their introduction. In particular, they got bigger. Not larger in physical size, but bigger in their capacity to store information. And, this additional capacity drove a fundamental change in the way disk drives were used.
-</div></div><div class="section" id="s2-partitions-partitioning-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-partitions-partitioning-x86">A.1.2. Partitions: Turning One Drive Into Many</h3></div></div></div><a id="id573347" class="indexterm"></a><a id="id798353" class="indexterm"></a><div class="para">
+</div></div><div class="section" id="s2-partitions-partitioning-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-partitions-partitioning-x86">A.1.2. Partitions: Turning One Drive Into Many</h3></div></div></div><a id="id575897" class="indexterm"></a><a id="id599824" class="indexterm"></a><div class="para">
As disk drive capacities soared, some people began to wonder if having all of that formatted space in one big chunk was such a great idea. This line of thinking was driven by several issues, some philosophical, some technical. On the philosophical side, above a certain size, it seemed that the additional space provided by a larger drive created more clutter. On the technical side, some file systems were never designed to support anything above a certain capacity. Or the file systems <span class="emphasis"><em>could</em></span> support larger drives with a greater capacity, but the overhead imposed by the file system to track files became excessive.
</div><div class="para">
The solution to this problem was to divide disks into <em class="firstterm">partitions</em>. Each partition can be accessed as if it was a separate disk. This is done through the addition of a <em class="firstterm">partition table</em>.
@@ -5571,7 +5571,7 @@ sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)</pre></li><li class="step
While the diagrams in this chapter show the partition table as being separate from the actual disk drive, this is not entirely accurate. In reality, the partition table is stored at the very start of the disk, before any file system or user data. But for clarity, they are separate in our diagrams.
</div></div></div><div class="figure" id="fig-partitions-unused-partitione-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/partitions/unused-partitioned-drive.png" alt="Disk Drive with Partition Table" /><div class="longdesc"><div class="para">
Image of an unused disk drive with a partition table.
-</div></div></div></div><h6>Figure A.5. Disk Drive with Partition Table</h6></div><br class="figure-break" /><a id="id812416" class="indexterm"></a><a id="id728184" class="indexterm"></a><div class="para">
+</div></div></div></div><h6>Figure A.5. Disk Drive with Partition Table</h6></div><br class="figure-break" /><a id="id777639" class="indexterm"></a><a id="id882818" class="indexterm"></a><div class="para">
As <a class="xref" href="#fig-partitions-unused-partitione-x86">Figure A.5, “Disk Drive with Partition Table”</a> shows, the partition table is divided into four sections or four <em class="firstterm">primary</em> partitions. A primary partition is a partition on a hard drive that can contain only one logical drive (or section). Each section can hold the information necessary to define a single partition, meaning that the partition table can define no more than four partitions.
</div><div class="para">
Each partition table entry contains several important characteristics of the partition:
@@ -5595,7 +5595,7 @@ sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)</pre></li><li class="step
We have labeled this partition as being of the "DOS" type. Although it is only one of several possible partition types listed in <a class="xref" href="#tb-partitions-types-x86">Table A.1, “Partition Types”</a>, it is adequate for the purposes of this discussion.
</div><div class="para">
<a class="xref" href="#tb-partitions-types-x86">Table A.1, “Partition Types”</a>, contains a listing of some popular (and obscure) partition types, along with their hexadecimal numeric values.
- </div><a id="id758500" class="indexterm"></a><a id="id737082" class="indexterm"></a><div class="table" id="tb-partitions-types-x86"><h6>Table A.1. Partition Types</h6><div class="table-contents"><table summary="Partition Types" border="1"><colgroup><col width="33%" /><col width="17%" /><col width="33%" /><col width="17%" /></colgroup><thead><tr><th>
+ </div><a id="id642402" class="indexterm"></a><a id="id777528" class="indexterm"></a><div class="table" id="tb-partitions-types-x86"><h6>Table A.1. Partition Types</h6><div class="table-contents"><table summary="Partition Types" border="1"><colgroup><col width="33%" /><col width="17%" /><col width="33%" /><col width="17%" /></colgroup><thead><tr><th>
Partition Type
</th><th>
Value
@@ -5773,7 +5773,7 @@ sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)</pre></li><li class="step
</div><div class="para">
- </div></div><div class="section" id="s2-partitions-overview-extended-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-partitions-overview-extended-x86">A.1.3. Partitions within Partitions — An Overview of Extended Partitions</h3></div></div></div><a id="id779293" class="indexterm"></a><a id="id805902" class="indexterm"></a><a id="id652843" class="indexterm"></a><a id="id534574" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-partitions-overview-extended-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-partitions-overview-extended-x86">A.1.3. Partitions within Partitions — An Overview of Extended Partitions</h3></div></div></div><a id="id592606" class="indexterm"></a><a id="id601396" class="indexterm"></a><a id="id729468" class="indexterm"></a><a id="id692935" class="indexterm"></a><div class="para">
Of course, over time it became obvious that four partitions would not be enough. As disk drives continued to grow, it became more and more likely that a person could configure four reasonably-sized partitions and still have disk space left over. There needed to be some way of creating more partitions.
</div><div class="para">
Enter the extended partition. As you may have noticed in <a class="xref" href="#tb-partitions-types-x86">Table A.1, “Partition Types”</a>, there is an "Extended" partition type. It is this partition type that is at the heart of extended partitions.
@@ -5785,7 +5785,7 @@ sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)</pre></li><li class="step
As this figure implies, there is a difference between primary and logical partitions — there can only be four primary partitions, but there is no fixed limit to the number of logical partitions that can exist. However, due to the way in which partitions are accessed in Linux, you should avoid defining more than 12 logical partitions on a single disk drive.
</div><div class="para">
Now that we have discussed partitions in general, let us review how to use this knowledge to install Fedora.
-</div></div><div class="section" id="s2-partitions-make-room-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-partitions-make-room-x86">A.1.4. Making Room For Fedora</h3></div></div></div><a id="id570511" class="indexterm"></a><div class="para">
+</div></div><div class="section" id="s2-partitions-make-room-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-partitions-make-room-x86">A.1.4. Making Room For Fedora</h3></div></div></div><a id="id715798" class="indexterm"></a><div class="para">
The following list presents some possible scenarios you may face when attempting to repartition your hard disk:
</div><div xml:lang="en-US" class="itemizedlist" lang="en-US"><ul><li class="listitem"><div class="para">
Unpartitioned free space is available
@@ -5797,7 +5797,7 @@ sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)</pre></li><li class="step
Let us look at each scenario in order.
</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">
Keep in mind that the following illustrations are simplified in the interest of clarity and do not reflect the exact partition layout that you encounter when actually installing Fedora.
- </div></div></div><div class="section" id="s3-partitions-free-space-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-partitions-free-space-x86">A.1.4.1. Using Unpartitioned Free Space</h4></div></div></div><a id="id806062" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s3-partitions-free-space-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-partitions-free-space-x86">A.1.4.1. Using Unpartitioned Free Space</h4></div></div></div><a id="id591007" class="indexterm"></a><div class="para">
In this situation, the partitions already defined do not span the entire hard disk, leaving unallocated space that is not part of any defined partition. <a class="xref" href="#fig-partitions-unpart-space-x86">Figure A.8, “Disk Drive with Unpartitioned Free Space”</a>, shows what this might look like.
</div><div class="figure" id="fig-partitions-unpart-space-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/partitions/unpart-space.png" width="444" alt="Disk Drive with Unpartitioned Free Space" /><div class="longdesc"><div class="para">
Image of a disk drive with unpartitioned free space, where <em class="wordasword">1</em> represents an undefined partition with unallocated space and <em class="wordasword">2</em> represents a defined partition with allocated space.
@@ -5809,7 +5809,7 @@ sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)</pre></li><li class="step
In any case, you can create the necessary partitions from the unused space. Unfortunately, this scenario, although very simple, is not very likely (unless you have just purchased a new disk just for Fedora). Most pre-installed operating systems are configured to take up all available space on a disk drive (refer to <a class="xref" href="#s3-partitions-active-part-x86">Section A.1.4.3, “Using Free Space from an Active Partition”</a>).
</div><div class="para">
Next, we will discuss a slightly more common situation.
-</div></div><div class="section" id="s3-partitions-unused-part-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-partitions-unused-part-x86">A.1.4.2. Using Space from an Unused Partition</h4></div></div></div><a id="id919613" class="indexterm"></a><div class="para">
+</div></div><div class="section" id="s3-partitions-unused-part-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-partitions-unused-part-x86">A.1.4.2. Using Space from an Unused Partition</h4></div></div></div><a id="id500255" class="indexterm"></a><div class="para">
In this case, maybe you have one or more partitions that you do not use any longer. Perhaps you have dabbled with another operating system in the past, and the partition(s) you dedicated to it never seem to be used anymore. <a class="xref" href="#fig-partitions-unused-partition-x86">Figure A.9, “Disk Drive With an Unused Partition”</a>, illustrates such a situation.
</div><div class="figure" id="fig-partitions-unused-partition-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/partitions/unused-partition.png" width="444" alt="Disk Drive With an Unused Partition" /><div class="longdesc"><div class="para">
Image of a disk drive with an unused partition, where <em class="wordasword">1</em> represents an unused partition and <em class="wordasword">2</em> represents reallocating an unused partition for Linux.
@@ -5817,11 +5817,11 @@ sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)</pre></li><li class="step
In <a class="xref" href="#fig-partitions-unused-partition-x86">Figure A.9, “Disk Drive With an Unused Partition”</a>, <em class="wordasword">1</em> represents an unused partition and <em class="wordasword">2</em> represents reallocating an unused partition for Linux.
</div><div class="para">
If you find yourself in this situation, you can use the space allocated to the unused partition. You first must delete the partition and then create the appropriate Linux partition(s) in its place. You can delete the unused partition and manually create new partitions during the installation process.
-</div></div><div class="section" id="s3-partitions-active-part-x86"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-partitions-active-part-x86">A.1.4.3. Using Free Space from an Active Partition</h4></div></div></div><a id="id702161" cl