Thu Apr 30 18:08:26 UTC 2009

Author: ke4qqq

Update of /cvs/fedora/web/html/docs/install-guide/f11/en-US/html
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv1208/f11/en-US/html

Added Files:
	Disk_Encryption_Guide.html ISCSI_disks.html 
	Installation-Guide-Preface.html 
	VNC_Whitepaper-firewall-considerations.html 
	VNC_Whitepaper-installation.html 
	VNC_Whitepaper-kickstart-installation.html 
	VNC_Whitepaper-references.html 
	VNC_Whitepaper-vnc-connect-mode.html 
	VNC_Whitepaper-vnc-modes-in-anaconda.html 
	ap-admin-options.html ap-install-server.html 
	ap-medialess-install.html ap-rescuemode.html ap-techref.html 
	apcs02.html apcs02s02.html apcs02s03.html apcs03.html 
	apcs03s02.html apcs04.html apcs04s03.html apcs04s04.html 
	apcs04s05.html apcs04s06.html apcs04s07.html apcs05.html 
	apcs05s02.html apcs05s03.html 
	appe-Publican-Revision_History.html 
	ch-Contributors_and_production_methods.html 
	ch-beginninginstallation.html ch-boot-init-shutdown.html 
	ch-driverdisk-x86.html ch-ent-table.html 
	ch-experts-quickstart.html ch-firstboot.html ch-grub.html 
	ch-guimode-x86.html ch-introduction.html ch-kickstart2.html 
	ch-new-users.html ch-next-steps.html ch-partitions-x86.html 
	ch-redhat-config-kickstart.html ch-steps-x86.html 
	ch-trouble-x86.html ch-upgrade-x86.html ch-x86-uninstall.html 
	ch02s04s02.html ch02s04s02s02.html ch03s03.html ch03s04.html 
	ch03s05s02.html ch03s06.html ch05s02.html ch05s03.html 
	ch05s04.html ch07s12.html ch07s21s03.html ch07s21s05.html 
	ch07s21s06.html ch08s02.html ch08s03s06.html ch08s04.html 
	ch08s04s02.html ch08s04s03.html ch08s04s04.html 
	ch08s04s05.html ch08s04s07.html ch08s04s09.html 
	ch11s05s05.html ch18s02.html index.html ix01.html 
	netboot-performing.html pr01s02.html 
	pt-Advanced_installation_options.html 
	pt-After_installation.html pt-Before_you_begin.html 
	pt-Technical_appendixes.html pt-The_installation_process.html 
	randomize_device.html s1-advanced-storage-x86.html 
	s1-begininstall-cd-inst-x86.html s1-begininstall-hd-x86.html 
	s1-begininstall-nfs-x86.html 
	s1-begininstall-perform-nfs-x86.html 
	s1-begininstall-url-x86.html 
	s1-boot-init-shutdown-process.html 
	s1-boot-init-shutdown-run-boot.html 
	s1-boot-init-shutdown-shutdown.html 
	s1-boot-init-shutdown-sysv.html s1-complete-x86.html 
	s1-diskpartauto-x86.html s1-diskpartitioning-x86.html 
	s1-diskpartsetup-x86.html s1-grub-additional-resources.html 
	s1-grub-commands.html s1-grub-configfile.html 
	s1-grub-installing.html s1-grub-interfaces.html 
	s1-grub-runlevels.html s1-grub-terminology.html 
	s1-guimode-textinterface-x86.html s1-installmethod.html 
	s1-installpkgs-x86.html s1-kickstart2-file.html 
	s1-kickstart2-howuse.html s1-kickstart2-install-tree.html 
	s1-kickstart2-options.html s1-kickstart2-packageselection.html 
	s1-kickstart2-postinstallconfig.html 
	s1-kickstart2-preinstallconfig.html 
	s1-kickstart2-putkickstarthere.html 
	s1-kickstart2-startinginstall.html s1-langselection-x86.html 
	s1-netboot-add-hosts.html s1-netboot-pxe-config.html 
	s1-netboot-tftp.html s1-pkgselection-x86.html 
	s1-preparetoinstall-x86.html 
	s1-redhat-config-kickstart-auth.html 
	s1-redhat-config-kickstart-bootloader.html 
	s1-redhat-config-kickstart-firewall.html 
	s1-redhat-config-kickstart-install.html 
	s1-redhat-config-kickstart-network.html 
	s1-redhat-config-kickstart-partitions.html 
	s1-redhat-config-kickstart-pkgs.html 
	s1-redhat-config-kickstart-postinstall.html 
	s1-redhat-config-kickstart-prescript.html 
	s1-redhat-config-kickstart-savefile.html 
	s1-redhat-config-kickstart-xconfig.html 
	s1-rescuemode-boot.html s1-rescuemode-booting-emergency.html 
	s1-rescuemode-booting-single.html 
	s1-steps-network-installs-x86.html s1-timezone-x86.html 
	s1-trouble-install-x86.html s1-x86-bootloader.html 
	s1-x86-starting.html s2-boot-init-shutdown-init.html 
	s2-boot-init-shutdown-kernel.html 
	s2-boot-init-shutdown-loader.html 
	s2-boot-init-shutdown-sysv-util.html 
	s2-diskpartdelete-x86.html s2-diskpartitioning-dd-x86.html 
	s2-diskpartrecommend-x86.html s2-grub-configfile-commands.html 
	s2-grub-related-books.html s2-grub-terminology-files.html 
	s2-grub-terminology-rootfs.html s2-grub-useful-websites.html 
	s2-kickstart2-networkbased.html s2-netboot-custom-msg.html 
	s2-redhat-config-kickstart-interpreter.html 
	s2-steps-make-cd.html s2-trouble-completeparts-x86.html 
	s2-trouble-part-tables-x86.html s2-trouble-ram.html 
	s2-trouble-sound.html s2-trouble-space-x86.html 
	s2-trouble-tracebacks-x86.html s2-x86-bootloader-alt.html 
	s2-x86-bootloader-rescue.html s2-x86-starting-bootopts.html 
	sn-Is_Your_Hardware_Compatible-x86.html 
	sn-Production_methods.html sn-about-document.html 
	sn-account_configuration.html sn-audience.html 
	sn-automating-installation.html sn-boot-mediacheck.html 
	sn-boot-modes.html sn-booting-from-pxe.html 
	sn-bootoptions-hardware.html sn-bootoptions-hwdetection.html 
	sn-cannot-download.html sn-cobbler-import.html 
	sn-cobbler-mirror.html sn-cobbler-setup-distro.html 
	sn-community.html sn-expert-download.html 
	sn-expert-install.html sn-expert-post-install.html 
	sn-expert-prepare.html sn-finishing-upgrade.html 
	sn-firstboot-datetime.html sn-firstboot-systemuser.html 
	sn-graphics-problem.html sn-iSCSI_disks_during_start_up.html 
	sn-initialize-hdd.html sn-install-diff-source.html 
	sn-lang-packages.html sn-making-media.html 
	sn-mandatory-services.html sn-medialess-booting.html 
	sn-medialess-editing-grub-conf.html sn-mode-rescue.html 
	sn-mode-upgradeany.html sn-networkconfig-fedora.html 
	sn-news-subscriptions.html sn-package-selection.html 
	sn-partitioning-lvm.html sn-pxe-server-manual.html 
	sn-remote-logging.html 
	sn-remoteaccess-installation-vnclistener.html 
	sn-remoteaccess-installation.html sn-smolt.html 
	sn-start-installation.html sn-switching-to-gui-login.html 
	sn-telnet-installation.html sn-upgrade-tree.html 
	sn-upgrading-bootloader.html sn-upgrading-system.html 
	sn-verifying-dvd.html sn-verifying-media.html sn-web-help.html 
	sn-welcome-x86.html sn-which-arch.html sn-which-files.html 
	sn-x86-uninstall-dual-linux.html 
	sn-x86-uninstall-dual-mac.html sn-x86-uninstall-dual.html 
	sn-x86-uninstall-legacy.html vncwhitepaperadded.html 
Log Message:
Install guide for PRF11 


--- NEW FILE Disk_Encryption_Guide.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>AppendixÂ C.Â Disk Encryption Guide</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-Technical_appendixes.html" title="PartÂ V.Â Technical appendixes" /><link rel="prev" href="sn-iSCSI_disks_during_start_up.html" title="B.2.Â iSCSI disks during start up" /><link rel="next" href="apcs02.html" title="C.2.Â Encrypting block devices using dm-crypt/LUKS" /></head><body class="draft "><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.p
 ng" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-iSCSI_disks_during_start_up.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apcs02.html"><strong>Next</strong></a></li></ul><div class="appendix" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h1 id="Disk_Encryption_Guide" class="title">Disk Encryption Guide</h1></div></div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="id873270">C.1.Â What is block device encryption? </h2></div></div></div><div class="para">
			Block device encryption protects the data on a block device by encrypting it. To access the device's decrypted contents, a user must provide a passphrase or key as authentication. This provides additional security beyond existing OS security mechanisms in that it protects the device's contents even if it has been physically removed from the system.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-iSCSI_disks_during_start_up.html"><strong>Prev</strong>B.2.Â iSCSI disks during start up</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="apcs02.html"><strong>Next</strong>C.2.Â Encrypting block devices using dm-crypt/LUKS </a></li></ul></body></html>


--- NEW FILE ISCSI_disks.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>AppendixÂ B.Â ISCSI disks</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-Technical_appendixes.html" title="PartÂ V.Â Technical appendixes" /><link rel="prev" href="ch-partitions-x86.html" title="AppendixÂ A.Â An Introduction to Disk Partitions" /><link rel="next" href="sn-iSCSI_disks_during_start_up.html" title="B.2.Â iSCSI disks during start up" /></head><body class="draft "><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.pn
 g" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-partitions-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-iSCSI_disks_during_start_up.html"><strong>Next</strong></a></li></ul><div class="appendix" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h1 id="ISCSI_disks" class="title">ISCSI disks</h1></div></div></div><div class="para">
		<em class="firstterm">Internet Small Computer System Interface</em> (iSCSI) is a protocol that allows computers to communicate with storage devices by SCSI requests and responses carried over TCP/IP. Because iSCSI is based on the standard SCSI protocols, it uses some terminology from SCSI. The device on the SCSI bus to which requests get sent (and which answers these requests) is known as the <em class="firstterm">target</em> and the device issuing requests is known as the <em class="firstterm">initiator</em>. In other words, an iSCSI disk is a target and the iSCSI software equivalent of a SCSI controller or SCSI Host Bus Adapter (HBA) is called an initiator. This appendix only covers Linux as an iSCSI initiator: how Linux uses iSCSI disks, but not how Linux hosts iSCSI disks.
	</div><div class="para">
		Linux has a software iSCSI initiator in the kernel that takes the place and form of a SCSI HBA driver and therefore allows Linux to use iSCSI disks. However, as iSCSI is a fully network-based protocol, iSCSI initiator support needs more than just the ability to send SCSI packets over the network. Before Linux can use an iSCSI target, Linux must find the target on the network and make a connection to it. In some cases, Linux must send authentication information to gain access to the target. Linux must also detect any failure of the network connection and must establish a new connection, including logging in again if necessary.
	</div><div class="para">
		The discovery, connection, and logging in is handled in userspace by the <span class="application"><strong>iscsiadm</strong></span> utility, and the error handling is also handled in userspace by <span class="application"><strong>iscsid</strong></span>.
	</div><div class="para">
		Both <span class="application"><strong>iscsiadm</strong></span> and <span class="application"><strong>iscsid</strong></span> are part of the <span class="application"><strong>iscsi-initiator-utils</strong></span> package under Fedora.
	</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-iSCSI_in_Fedora-iSCSI_disks_in_anaconda">B.1.Â iSCSI disks in <span class="application"><strong>anaconda</strong></span></h2></div></div></div><div class="para">
			<span class="application"><strong>Anaconda</strong></span> can discover (and then log in to) iSCSI disks in two ways:
		</div><div class="orderedlist"><ol><li><div class="para">
					When anaconda starts, it checks if the BIOS or add-on boot ROMs of the system support <em class="firstterm">iSCSI Boot Firmware Table</em> (iBFT), a BIOS extension for systems which can boot from iSCSI. If the BIOS supports iBFT, <span class="application"><strong>anaconda</strong></span> will read the iSCSI target information for the configured boot disk from the BIOS and log in to this target, making it available as an installation target.
				</div></li><li><div class="para">
					The initial partitioning screen presents you with an <span class="guilabel"><strong>Advanced storage configuration</strong></span> button that allows you to add iSCSI target information like the discovery IP-address. <span class="application"><strong>Anaconda</strong></span> will probe the given IP-address and log in to any targets that it finds. See <a class="xref" href="s1-advanced-storage-x86.html" title="7.19.Â  Advanced Storage Options">SectionÂ 7.19, â€œ Advanced Storage Options â€</a> for the details that you can specify for iSCSI targets.
				</div></li></ol></div><div class="para">
			While <span class="application"><strong>anaconda</strong></span> uses <span class="application"><strong>iscsiadm</strong></span> to find and log into iSCSI targets, <span class="application"><strong>iscsiadm</strong></span> automatically stores any information about these targets iscsiadm iSCSI database. <span class="application"><strong>Anaconda</strong></span> then copies this database to the installed system and marks any iSCSI targets not used for <code class="filename">/</code> so that the system will automatically log in to them when it starts. If <code class="filename">/</code> is placed on an iSCSI target, <span class="application"><strong>initrd</strong></span> will log into this target and <span class="application"><strong>anaconda</strong></span> does not include this target in start up scripts to avoid multiple attempts to log into the same target.
		</div><div class="para">
			If <code class="filename">/</code> is placed on an iSCSI target, <span class="application"><strong>anaconda</strong></span> sets <span class="application"><strong>NetworkManager</strong></span> to ignore any network interfaces that were active during the installation process. These interfaces will also be configured by <span class="application"><strong>initrd</strong></span> when the system starts. If <span class="application"><strong>NetworkManager</strong></span> were to reconfigure these interfaces, the system would lose its connection to <code class="filename">/</code>.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-partitions-x86.html"><strong>Prev</strong>AppendixÂ A.Â An Introduction to Disk Partitions</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-iSCSI_disks_during_start_up.html"><strong>Next</strong>B.2.Â iSCSI disks during start up</a></li></ul></body></html>


--- NEW FILE Installation-Guide-Preface.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Preface</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="index.html" title="Installation Guide" /><link rel="prev" href="index.html" title="Installation Guide" /><link rel="next" href="pr01s02.html" title="2.Â We Need Feedback!" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"><strong>Prev
 </strong></a></li><li class="next"><a accesskey="n" href="pr01s02.html"><strong>Next</strong></a></li></ul><div class="preface" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h1 id="Installation-Guide-Preface" class="title">Preface</h1></div></div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="id822194">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" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id820721">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>
		</div><div class="para">
			Used to highlight system input, including shell commands, file names and paths. Also used to highlight key caps and key-combinations. For example:
		</div><div class="blockquote"><blockquote class="blockquote"><div class="para">
				To see the contents of the file <code class="filename">my_next_bestselling_novel</code> in your current working directory, enter the <code class="command">cat my_next_bestselling_novel</code> command at the shell prompt and press <span class="keycap"><strong>Enter</strong></span> to execute the command.
			</div></blockquote></div><div class="para">
			The above includes a file name, a shell command and a key cap, all presented in Mono-spaced Bold and all distinguishable thanks to context.
		</div><div class="para">
			Key-combinations can be distinguished from key caps by the hyphen connecting each part of a key-combination. For example:
		</div><div class="blockquote"><blockquote class="blockquote"><div class="para">
				Press <span class="keycap"><strong>Enter</strong></span> to execute the command.
			</div><div class="para">
				Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F1</strong></span> to switch to the first virtual terminal. Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F7</strong></span> to return to your X-Windows session.
			</div></blockquote></div><div class="para">
			The first sentence highlights the particular key cap to press. The second highlights two sets of three key caps, each set pressed simultaneously.
		</div><div class="para">
			If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in <code class="literal">Mono-spaced Bold</code>. For example:
		</div><div class="blockquote"><blockquote class="blockquote"><div class="para">
				File-related classes include <code class="classname">filesystem</code> for file systems, <code class="classname">file</code> for files, and <code class="classname">dir</code> for directories. Each class has its own associated set of permissions.
			</div></blockquote></div><div class="para">
			<span class="application"><strong>Proportional Bold</strong></span>
		</div><div class="para">
			This denotes words or phrases encountered on a system, including application names; dialogue box text; labelled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example:
		</div><div class="blockquote"><blockquote class="blockquote"><div class="para">
				Choose <span class="guimenu"><strong>System > Preferences > Mouse</strong></span> from the main menu bar to launch <span class="application"><strong>Mouse Preferences</strong></span>. In the <span class="guilabel"><strong>Buttons</strong></span> tab, click the <span class="guilabel"><strong>Left-handed mouse</strong></span> check box and click <span class="guibutton"><strong>Close</strong></span> to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand).
			</div><div class="para">
				To insert a special character into a <span class="application"><strong>gedit</strong></span> file, choose <span class="guimenu"><strong>Applications > Accessories > Character Map</strong></span> from the main menu bar. Next, choose <span class="guimenu"><strong>Search > Findâ€¦</strong></span> from the <span class="application"><strong>Character Map</strong></span> menu bar, type the name of the character in the <span class="guilabel"><strong>Search</strong></span> field and click <span class="guibutton"><strong>Next</strong></span>. The character you sought will be highlighted in the <span class="guilabel"><strong>Character Table</strong></span>. Double-click this highlighted character to place it in the <span class="guilabel"><strong>Text to copy</strong></span> field and then click the <span class="guibutton"><strong>Copy</strong></span> button. Now switch back to your document and choose <span class="guimenu"><strong>Edit > Paste</strong></span> from the <
 span class="application"><strong>gedit</strong></span> menu bar.
			</div></blockquote></div><div class="para">
			The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in Proportional Bold and all distinguishable by context.
		</div><div class="para">
			Note the <span class="guimenu"><strong>></strong></span> shorthand used to indicate traversal through a menu and its sub-menus. This is to avoid the difficult-to-follow 'Select <span class="guimenuitem"><strong>Mouse</strong></span> from the <span class="guimenu"><strong>Preferences</strong></span> sub-menu in the <span class="guimenu"><strong>System</strong></span> menu of the main menu bar' approach.
		</div><div class="para">
			<code class="command"><em class="replaceable"><code>Mono-spaced Bold Italic</code></em></code> or <span class="application"><strong><em class="replaceable"><code>Proportional Bold Italic</code></em></strong></span>
		</div><div class="para">
			Whether Mono-spaced Bold or Proportional Bold, the addition of Italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example:
		</div><div class="blockquote"><blockquote class="blockquote"><div class="para">
				To connect to a remote machine using ssh, type <code class="command">ssh <em class="replaceable"><code>username</code></em>@<em class="replaceable"><code>domain.name</code></em></code> at a shell prompt. If the remote machine is <code class="filename">example.com</code> and your username on that machine is john, type <code class="command">ssh john at example.com</code>.
			</div><div class="para">
				The <code class="command">mount -o remount <em class="replaceable"><code>file-system</code></em></code> command remounts the named file system. For example, to remount the <code class="filename">/home</code> file system, the command is <code class="command">mount -o remount /home</code>.
			</div><div class="para">
				To see the version of a currently installed package, use the <code class="command">rpm -q <em class="replaceable"><code>package</code></em></code> command. It will return a result as follows: <code class="command"><em class="replaceable"><code>package-version-release</code></em></code>.
			</div></blockquote></div><div class="para">
			Note the words in bold italics above â€” username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system.
		</div><div class="para">
			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">
				When the Apache HTTP Server accepts requests, it dispatches child processes or threads to handle them. This group of child processes or threads is known as a <em class="firstterm">server-pool</em>. Under Apache HTTP Server 2.0, the responsibility for creating and maintaining these server-pools has been abstracted to a group of modules called <em class="firstterm">Multi-Processing Modules</em> (<em class="firstterm">MPMs</em>). Unlike other modules, only one module from the MPM group can be loaded by the Apache HTTP Server.
			</div></blockquote></div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id813569">1.2.Â Pull-quote Conventions</h3></div></div></div><div class="para">
			Two, commonly multi-line, data types 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:
		</div><pre class="screen">
books        Desktop   documentation  drafts  mss    photos   stuff  svn
books_tests  Desktop1  downloads      images  notes  scripts  svgs
</pre><div class="para">
			Source-code listings are also set in <code class="computeroutput">Mono-spaced Roman</code> but are presented and highlighted as follows:
		</div><pre class="programlisting">
package org.jboss.book.jca.ex1;

import javax.naming.InitialContext;

public class ExClient
{
   public static void main(String args[]) 
       throws Exception
   {
      InitialContext iniCtx = new InitialContext();
      Object         ref    = iniCtx.lookup("EchoBean");
      EchoHome       home   = (EchoHome) ref;
      Echo           echo   = home.create();

      System.out.println("Created Echo");

      System.out.println("Echo.echo('Hello') = " + echo.echo("Hello"));
   }
   
}
</pre></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id833572">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"><h2>Note</h2><div class="para">
				A note is a tip or shortcut or alternative approach 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.
			</div></div><div class="important"><h2>Important</h2><div class="para">
				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 Important boxes won't cause data loss but may cause irritation and frustration.
			</div></div><div class="warning"><h2>Warning</h2><div class="para">
				A Warning should not be ignored. Ignoring warnings will most likely cause data loss.
			</div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"><strong>Prev</strong>Installation Guide</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="pr01s02.html"><strong>Next</strong>2.Â We Need Feedback!</a></li></ul></body></html>


--- NEW FILE VNC_Whitepaper-firewall-considerations.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.3.3.Â Firewall Considerations</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="VNC_Whitepaper-installation.html" title="12.3.Â Installation Using VNC" /><link rel="prev" href="VNC_Whitepaper-kickstart-installation.html" title="12.3.2.Â Kickstart Considerations" /><link rel="next" href="VNC_Whitepaper-references.html" title="12.4.Â References" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="VNC_Whitepaper-kickstart-installation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="VNC_Whitepaper-references.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="VNC_Whitepaper-firewall-considerations">12.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">
			In addition to passing the <code class="command">vnc</code> boot parameter, you may also want to pass the <code class="command">vncpassword</code> parameter in these scenarios. While the password is sent in plain text over the network, it does provide an extra step before a viewer can connect to a system. Once the viewer connects to the target system over VNC, no other connections are permitted. These limitations are usually sufficient for installation purposes.
		</div><div class="important"><h2>Important</h2><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 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).
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="VNC_Whitepaper-kickstart-installation.html"><strong>Prev</strong>12.3.2.Â Kickstart Considerations</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="VNC_Whitepaper-references.html"><strong>Next</strong>12.4.Â References</a></li></ul></body></html>


--- NEW FILE VNC_Whitepaper-installation.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.3.Â Installation Using VNC</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="vncwhitepaperadded.html" title="ChapterÂ 12.Â Installing Through VNC" /><link rel="prev" href="VNC_Whitepaper-vnc-connect-mode.html" title="12.2.2.Â Connect Mode" /><link rel="next" href="VNC_Whitepaper-kickstart-installation.html" title="12.3.2.Â Kickstart Considerations" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="VNC_Whitepaper-vnc-connect-mode.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="VNC_Whitepaper-kickstart-installation.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="VNC_Whitepaper-installation">12.3.Â Installation Using VNC</h2></div></div></div><div class="para">
		Now that you have installed a VNC viewer application and selected a VNC mode for use in anaconda, you are ready to begin the installation.
	</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="VNC_Whitepaper-installation-example">12.3.1.Â Installation Example</h3></div></div></div><div class="para">
			The easiest way to perform an installation using VNC is to connect another computer directly to the network port on the target system. The laptop on a datacenter crash cart usually fills this role. If you are performing your installation this way, make sure you follow these steps:
		</div><div class="orderedlist"><ol><li><div class="para">
					Connect the laptop or other workstation to the target system using a crossover cable. If you are using regular patch cables, make sure you connect the two systems using a small hub or switch. Most recent Ethernet interfaces will automatically detect if they need to be crossover or not, so it may be possible to connect the two systems directly using a regular patch cable.
				</div></li><li><div class="para">
					Configure the VNC viewer system to use a RFC 1918 address with no gateway. This private network connection will only be used for the purpose of installation. Configure the VNC viewer system to be 192.168.100.1/24. If that address is in use, just pick something else in the RFC 1918 address space that is available to you.
				</div></li><li><div class="para">
					Start the installation on the target system.
				</div><div class="orderedlist"><ol><li><div class="para">
							Booting the installation DVD or CD.
						</div><div class="para">
							If booting the installation media (CD or DVD), make sure <code class="command">vnc</code> is passed as a boot parameter. To add the <code class="command">vnc</code> parameter, you will need a console attached to the target system that allows you to interact with the boot process. Enter the following at the prompt:
						</div><div class="para">
							
<pre class="screen">
boot: <strong class="userinput"><code>linux vnc</code></strong>
</pre>
						</div></li><li><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><div class="para">
							
<pre class="screen">
boot: <strong class="userinput"><code>linux vncconnect=<em class="replaceable"><code>HOST</code></em></code></strong>
</pre>
						</div></li></ol></div></li><li><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"><h2>Note</h2><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.
					</div></div></li><li><div class="para">
					Once the installer indicates it is starting anaconda, you will be instructed to connect to the system using the VNC viewer. Connect to the viewer and follow the graphical installation mode instructions found in the product documentation.
				</div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="VNC_Whitepaper-vnc-connect-mode.html"><strong>Prev</strong>12.2.2.Â Connect Mode</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="VNC_Whitepaper-kickstart-installation.html"><strong>Next</strong>12.3.2.Â Kickstart Considerations</a></li></ul></body></html>


--- NEW FILE VNC_Whitepaper-kickstart-installation.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.3.2.Â Kickstart Considerations</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="VNC_Whitepaper-installation.html" title="12.3.Â Installation Using VNC" /><link rel="prev" href="VNC_Whitepaper-installation.html" title="12.3.Â Installation Using VNC" /><link rel="next" href="VNC_Whitepaper-firewall-considerations.html" title="12.3.3.Â Firewall Considerations" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="VNC_Whitepaper-installation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="VNC_Whitepaper-firewall-considerations.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="VNC_Whitepaper-kickstart-installation">12.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.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="VNC_Whitepaper-installation.html"><strong>Prev</strong>12.3.Â Installation Using VNC</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="VNC_Whitepaper-firewall-considerations.html"><strong>Next</strong>12.3.3.Â Firewall Considerations</a></li></ul></body></html>


--- NEW FILE VNC_Whitepaper-references.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.4.Â References</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="vncwhitepaperadded.html" title="ChapterÂ 12.Â Installing Through VNC" /><link rel="prev" href="VNC_Whitepaper-firewall-considerations.html" title="12.3.3.Â Firewall Considerations" /><link rel="next" href="ch-kickstart2.html" title="ChapterÂ 13.Â Kickstart Installations" /></head><body class="draft "><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="Documen
 tation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="VNC_Whitepaper-firewall-considerations.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-kickstart2.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="VNC_Whitepaper-references">12.4.Â References</h2></div></div></div><div class="itemizedlist"><ul><li><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><div class="para">
				TightVNC: <a href="http://www.tightvnc.com/">http://www.tightvnc.com/</a>
			</div></li><li><div class="para">
				RFC 1918 - Address Allocation for Private Networks: <a href="http://www.ietf.org/rfc/rfc1918.txt">http://www.ietf.org/rfc/rfc1918.txt</a>
			</div></li><li><div class="para">
				Anaconda boot options: <a href="http://fedoraproject.org/wiki/Anaconda/Options">http://fedoraproject.org/wiki/Anaconda/Options</a>
			</div></li><li><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><ul class="docnav"><li class="previous"><a accesskey="p" href="VNC_Whitepaper-firewall-considerations.html"><strong>Prev</strong>12.3.3.Â Firewall Considerations</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-kickstart2.html"><strong>Next</strong>ChapterÂ 13.Â Kickstart Installations</a></li></ul></body></html>


--- NEW FILE VNC_Whitepaper-vnc-connect-mode.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.2.2.Â Connect Mode</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="VNC_Whitepaper-vnc-modes-in-anaconda.html" title="12.2.Â VNC Modes in Anaconda" /><link rel="prev" href="VNC_Whitepaper-vnc-modes-in-anaconda.html" title="12.2.Â VNC Modes in Anaconda" /><link rel="next" href="VNC_Whitepaper-installation.html" title="12.3.Â Installation Using VNC" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="VNC_Whitepaper-vnc-modes-in-anaconda.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="VNC_Whitepaper-installation.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="VNC_Whitepaper-vnc-connect-mode">12.2.2.Â Connect Mode</h3></div></div></div><div class="para">
			Certain firewall configurations or instances where the target system is configured to obtain a dynamic IP address may cause trouble with the direct VNC mode in anaconda. In addition, if you lack a console on the target system to see the message that tells you the IP address to connect to, then you will not be able to continue the installation.
		</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><div class="para">
			
<pre class="screen">
boot: <strong class="userinput"><code>linux vncconnect=<em class="replaceable"><code>HOST</code></em></code></strong>
</pre>
		</div><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.
		</div><div class="para">
			Start the installation and when your VNC viewer displays the graphical installer, you are ready to go.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="VNC_Whitepaper-vnc-modes-in-anaconda.html"><strong>Prev</strong>12.2.Â VNC Modes in Anaconda</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="VNC_Whitepaper-installation.html"><strong>Next</strong>12.3.Â Installation Using VNC</a></li></ul></body></html>


--- NEW FILE VNC_Whitepaper-vnc-modes-in-anaconda.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.2.Â VNC Modes in Anaconda</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="vncwhitepaperadded.html" title="ChapterÂ 12.Â Installing Through VNC" /><link rel="prev" href="vncwhitepaperadded.html" title="ChapterÂ 12.Â Installing Through VNC" /><link rel="next" href="VNC_Whitepaper-vnc-connect-mode.html" title="12.2.2.Â Connect Mode" /></head><body class="draft "><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="Documentat
 ion Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="vncwhitepaperadded.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="VNC_Whitepaper-vnc-connect-mode.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="VNC_Whitepaper-vnc-modes-in-anaconda">12.2.Â VNC Modes in Anaconda</h2></div></div></div><div class="para">
		Anaconda offers two modes for VNC installation. The mode you select will depend on the network configuration in your environment.
	</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="VNC_Whitepaper-vnc-direct-mode">12.2.1.Â Direct Mode</h3></div></div></div><div class="para">
			Direct mode VNC in anaconda is when the client initiates a connection to the VNC server running in anaconda. Anaconda will tell you when to initiate this connection in the VNC viewer. Direct mode can be activated by either of the following commands:
		</div><div class="itemizedlist"><ul><li><div class="para">
					Specify <code class="command">vnc</code> as a boot argument.
				</div></li><li><div class="para">
					Specify the <code class="command">vnc</code> command in the kickstart file used for installation.
				</div></li></ul></div><div class="para">
			When you activate VNC mode, anaconda will complete the first stage of the installer and then start VNC to run the graphical installer. The installer will display a message on the console in the following format:
		</div><div class="para">
			
<pre class="screen">
Running anaconda <em class="replaceable"><code>VERSION</code></em>, the <em class="replaceable"><code>PRODUCT</code></em> system installer - please wait...
</pre>
		</div><div class="para">
			Anaconda will also tell you the IP address and display number to use in your VNC viewer. At this point, you need to start the VNC viewer and connect to the target system to continue the installation. The VNC viewer will present anaconda to you in graphical mode.
		</div><div class="para">
			There are some disadvantages to direct mode, including:
		</div><div class="itemizedlist"><ul><li><div class="para">
					Requires visual access to the system console to see the IP address and port to connect the VNC viewer to.
				</div></li><li><div class="para">
					Requires interactive access to the system console to complete the first stage of the installer.
				</div></li></ul></div><div class="para">
			If either of these disadvantages would prevent you from using direct mode VNC in anaconda, then connect mode is probably more suited to your environment.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="vncwhitepaperadded.html"><strong>Prev</strong>ChapterÂ 12.Â Installing Through VNC</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="VNC_Whitepaper-vnc-connect-mode.html"><strong>Next</strong>12.2.2.Â Connect Mode</a></li></ul></body></html>


--- NEW FILE ap-admin-options.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ChapterÂ 9.Â Boot Options</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-Advanced_installation_options.html" title="PartÂ III.Â Advanced installation options" /><link rel="prev" href="pt-Advanced_installation_options.html" title="PartÂ III.Â Advanced installation options" /><link rel="next" href="sn-remoteaccess-installation.html" title="9.2.Â Enabling Remote Access to the Installation System" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="pt-Advanced_installation_options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-remoteaccess-installation.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="ap-admin-options">ChapterÂ 9.Â Boot Options</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ap-admin-options.html#sn-bootoptions-installer">9.1. Configuring the Installation System at the Boot Menu</a></span></dt><dd><dl><dt><span class="section"><a href="ap-admin-options.html#sn-boot-options-language">9.1.1. Specifying the Language</a></span></dt><dt><span class="section"><a href="ap-admin-options.html#sn-boot-options-interface">9.1.2. Configuring the Interface</a></span></dt><dt><span class="section"><a href="ap-admin
 -options.html#sn-boot-options-update">9.1.3. Updating anaconda</a></span></dt><dt><span class="section"><a href="ap-admin-options.html#sn-boot-options-installmethod">9.1.4. Specifying the Installation Method</a></span></dt><dt><span class="section"><a href="ap-admin-options.html#sn-boot-options-network">9.1.5. Manually Configuring the Network Settings</a></span></dt></dl></dd><dt><span class="section"><a href="sn-remoteaccess-installation.html">9.2. Enabling Remote Access to the Installation System</a></span></dt><dd><dl><dt><span class="section"><a href="sn-remoteaccess-installation.html#sn-remoteaccess-installation-vnc">9.2.1. Enabling Remote Access with VNC</a></span></dt><dt><span class="section"><a href="sn-remoteaccess-installation-vnclistener.html">9.2.2. Connecting the Installation System to a VNC Listener</a></span></dt><dt><span class="section"><a href="sn-telnet-installation.html">9.2.3. Enabling Remote Access with Telnet</a></span></dt></dl></dd><dt><span class="
 section"><a href="sn-remote-logging.html">9.3. Logging to a Remote System During the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="sn-remote-logging.html#sn-remote-logging-logserver">9.3.1. Configuring a Log Server</a></span></dt></dl></dd><dt><span class="section"><a href="sn-automating-installation.html">9.4. Automating the Installation with Kickstart</a></span></dt><dt><span class="section"><a href="sn-bootoptions-hardware.html">9.5. Enhancing Hardware Support</a></span></dt><dd><dl><dt><span class="section"><a href="sn-bootoptions-hardware.html#sn-bootoptions-driverdisks">9.5.1. Adding Hardware Support with Driver Disks</a></span></dt><dt><span class="section"><a href="sn-bootoptions-hwdetection.html">9.5.2. Overriding Automatic Hardware Detection</a></span></dt></dl></dd><dt><span class="section"><a href="sn-boot-modes.html">9.6. Using the Maintenance Boot Modes</a></span></dt><dd><dl><dt><span class="section"><a href="sn-boot-modes.html#sn-memt
 est">9.6.1. Loading the Memory (RAM) Testing Mode</a></span></dt><dt><span class="section"><a href="sn-boot-mediacheck.html">9.6.2. Verifying boot media</a></span></dt><dt><span class="section"><a href="sn-mode-rescue.html">9.6.3. Booting Your Computer with the Rescue Mode</a></span></dt><dt><span class="section"><a href="sn-mode-upgradeany.html">9.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">
		If you specify more than one option, separate each of the options by a single space. For example:
	</div><pre class="screen">
<strong class="userinput"><code>linux <em class="replaceable"><code>option1</code></em> <em class="replaceable"><code>option2</code></em> <em class="replaceable"><code>option3</code></em></code></strong>
</pre><div class="note"><h2>Anaconda Boot Options</h2><div class="para">
			The anaconda installer has many boot options, most are listed on the wiki <a href="http://fedoraproject.org/wiki/Anaconda/Options">http://fedoraproject.org/wiki/Anaconda/Options</a>.
		</div></div><div class="note"><h2>Kernel Boot Options</h2><div class="para">
			The <a href="http://fedoraproject.org/wiki/KernelCommonProblems">http://fedoraproject.org/wiki/KernelCommonProblems</a> page lists many common kernel boot options. The full list of kernel options is in the file /usr/share/doc/kernel-doc-<em class="replaceable"><code>version</code></em>/Documentation/kernel-parameters.txt, which is installed with the kernel-doc package.
		</div></div><div class="note"><h2>Rescue Mode</h2><div class="para">
			The Fedora installation and <em class="firstterm">rescue discs</em> may either boot with <em class="firstterm">rescue mode</em>, or load the installation system. For more information on rescue discs and rescue mode, refer to <a class="xref" href="sn-mode-rescue.html" title="9.6.3.Â Booting Your Computer with the Rescue Mode">SectionÂ 9.6.3, â€œBooting Your Computer with the Rescue Modeâ€</a>.
		</div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-bootoptions-installer">9.1.Â Configuring the Installation System at the Boot Menu</h2></div></div></div><div class="para">
			You can use the boot menu to specify a number of settings for the installation system, including:
		</div><div class="itemizedlist"><ul><li><div class="para">
					language
				</div></li><li><div class="para">
					display resolution
				</div></li><li><div class="para">
					interface type
				</div></li><li><div class="para">
					Installation method
				</div></li><li><div class="para">
					network settings
				</div></li></ul></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-boot-options-language">9.1.1.Â Specifying the Language</h3></div></div></div><div class="para">
				To set the language for both the installation process and the final system, specify the ISO code for that language with the <code class="option">lang</code> option. Use the <code class="option">keymap</code> option to configure the correct keyboard layout.
			</div><div class="para">
				For example, the ISO codes <strong class="userinput"><code>el_GR</code></strong> and <strong class="userinput"><code>gr</code></strong> identify the Greek language and the Greek keyboard layout:
			</div><pre class="screen">
<strong class="userinput"><code>linux lang=<em class="replaceable"><code>el_GR</code></em> keymap=<em class="replaceable"><code>gr</code></em></code></strong>
</pre></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-boot-options-interface">9.1.2.Â Configuring the Interface</h3></div></div></div><div class="para">
				You may force the installation system to use the lowest possible screen resolution (640x480) with the <code class="option">lowres</code> option. To use a specific display resolution, enter <code class="option">resolution=<em class="replaceable"><code>setting</code></em></code> as a boot option. For example, to set the display resolution to 1024x768, enter:
			</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="id804238" 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="id908808" 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.
			</div><div class="para">
				On the system you want the display to appear on, you must execute the command <code class="command">xhost +<em class="replaceable"><code>remotehostname</code></em></code>, where <em class="replaceable"><code>remotehostname</code></em> is the name of the host from which you are running the original display. Using the command <code class="command">xhost +<em class="replaceable"><code>remotehostname</code></em></code> limits access to the remote display terminal and does not allow access from anyone or any system not specifically authorized for remote access.
			</div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-boot-options-update">9.1.3.Â Updating anaconda</h3></div></div></div><div class="para">
				You can install Fedora with a newer version of the <span class="application"><strong>anaconda</strong></span> installation program than the one supplied on your installation media.
			</div><div class="para">
				The boot option
			</div><pre class="screen">
  <strong class="userinput"><code>linux updates</code></strong>
</pre><div class="para">
				presents you with a prompt that asks you for a floppy disk containing <span class="application"><strong>anaconda</strong></span> updates. You do not need to specify this option if you are performing a network installation and have already placed the updates image contents in <code class="filename">rhupdates/</code> on the server.
			</div><div class="para">
				To load the <span class="application"><strong>anaconda</strong></span> updates from a network location instead, use:
			</div><pre class="screen">
  <strong class="userinput"><code>linux updates=</code></strong>
</pre><div class="para">
				followed by the URL for the location where the updates are stored.
			</div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-boot-options-installmethod">9.1.4.Â Specifying the Installation Method</h3></div></div></div><div class="para">
				Use the <code class="option">askmethod</code> option to display additional menus that enable you to specify the installation method and network settings. You may also configure the installation method and network settings at the <code class="prompt">boot:</code> prompt itself.
			</div><div class="para">
				To specify the installation method from the <code class="prompt">boot:</code> prompt, use the <code class="option">method</code> option. Refer to <a class="xref" href="ap-admin-options.html#tb-installmethods" title="TableÂ 9.1.Â Installation methods">TableÂ 9.1, â€œInstallation methodsâ€</a> for the supported installation methods.
			</div><div class="table" id="tb-installmethods"><div class="table-contents"><table summary="Installation methods" border="1"><colgroup><col align="left" /><col align="left" /></colgroup><thead><tr><th align="left">
								Installation method
							</th><th align="left">
								Option format
							</th></tr></thead><tbody><tr><td align="left">
								CD or DVD drive
							</td><td align="left">
								<code class="option">method=<em class="replaceable"><code>cdrom</code></em></code>
							</td></tr><tr><td align="left">
								Hard Drive
							</td><td align="left">
								<code class="option">method=<em class="replaceable"><code>hd://device/</code></em></code>
							</td></tr><tr><td align="left">
								HTTP Server
							</td><td align="left">
								<code class="option">method=<em class="replaceable"><code>http://server.mydomain.com/directory/</code></em></code>
							</td></tr><tr><td align="left">
								FTP Server
							</td><td align="left">
								<code class="option">method=<em class="replaceable"><code>ftp://server.mydomain.com/directory/</code></em></code>
							</td></tr><tr><td align="left">
								NFS Server
							</td><td align="left">
								<code class="option">method=<em class="replaceable"><code>nfs:server.mydomain.com:/directory/</code></em></code>
							</td></tr></tbody></table></div><h6>TableÂ 9.1.Â Installation methods</h6></div><br class="table-break" /></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-boot-options-network">9.1.5.Â Manually Configuring the Network Settings</h3></div></div></div><div class="para">
				By default, the installation system uses DHCP to automatically obtain the correct network settings. To manually configure the network settings yourself, either enter them in the <span class="guilabel"><strong>Configure TCP/IP</strong></span> screen, or at the <code class="prompt">boot:</code> prompt. You may specify the <code class="option">ip</code> address, <code class="option">netmask</code>, <code class="option">gateway</code>, and <code class="option">dns</code> server settings for the installation system at the prompt. If you specify the network configuration at the <code class="prompt">boot:</code> prompt, these settings are used for the installation process, and the <span class="guilabel"><strong>Configure TCP/IP</strong></span> screen does not appear.
			</div><div class="para">
				This example configures the network settings for an installation system that uses the IP address <code class="systemitem">192.168.1.10</code>:
			</div><pre class="screen">
<strong class="userinput"><code>linux ip=<em class="replaceable"><code>192.168.1.10</code></em> netmask=<em class="replaceable"><code>255.255.255.0</code></em> gateway=<em class="replaceable"><code>192.168.1.1</code></em> dns=<em class="replaceable"><code>192.168.1.2,192.168.1.3</code></em></code></strong>
</pre><div class="note"><h2>Configuring the Installed System</h2><div class="para">
					Use the Network Configuration screen to specify the network settings for the new system. Refer to <a class="xref" href="sn-networkconfig-fedora.html#sn-networkconfig-fedora_manual-configuration" title="7.15.1.Â Manual configuration">SectionÂ 7.15.1, â€œManual configurationâ€</a> for more information on configuring the network settings for the installed system.
				</div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pt-Advanced_installation_options.html"><strong>Prev</strong>PartÂ III.Â Advanced installation options</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-remoteaccess-installation.html"><strong>Next</strong>9.2.Â Enabling Remote Access to the Installation S...</a></li></ul></body></html>


--- NEW FILE ap-install-server.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ChapterÂ 11.Â Setting Up an Installation Server</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-Advanced_installation_options.html" title="PartÂ III.Â Advanced installation options" /><link rel="prev" href="sn-medialess-booting.html" title="10.3.Â Booting to Installation" /><link rel="next" href="sn-cobbler-setup-distro.html" title="11.2.Â Setting Up the Distribution" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-medialess-booting.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-cobbler-setup-distro.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="ap-install-server">ChapterÂ 11.Â Setting Up an Installation Server</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ap-install-server.html#sn-install-cobbler">11.1. Setting Up cobbler</a></span></dt><dt><span class="section"><a href="sn-cobbler-setup-distro.html">11.2. Setting Up the Distribution</a></span></dt><dt><span class="section"><a href="sn-cobbler-mirror.html">11.3. Mirroring a Network Location</a></span></dt><dt><span class="section"><a href="sn-cobbler-import.html">11.4. Importing the Distribution</a></span></dt><dt><span class="section"><a href="sn-pxe
 -server-manual.html">11.5. Manually configure a PXE server</a></span></dt><dd><dl><dt><span class="section"><a href="sn-pxe-server-manual.html#s1-netboot-netserver">11.5.1. Setting up the Network Server</a></span></dt><dt><span class="section"><a href="s1-netboot-pxe-config.html">11.5.2. PXE Boot Configuration</a></span></dt><dt><span class="section"><a href="s1-netboot-add-hosts.html">11.5.3. Adding PXE Hosts</a></span></dt><dt><span class="section"><a href="s1-netboot-tftp.html">11.5.4. TFTPD</a></span></dt><dt><span class="section"><a href="ch11s05s05.html">11.5.5. Configuring the DHCP Server</a></span></dt><dt><span class="section"><a href="s2-netboot-custom-msg.html">11.5.6. Adding a Custom Boot Message</a></span></dt><dt><span class="section"><a href="netboot-performing.html">11.5.7. Performing the PXE Installation</a></span></dt></dl></dd></dl></div><div class="note"><h2>Experience Required</h2><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 class="warning"><h2>Warning</h2><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.
		</div></div><div class="para">
	Fedora allows for installation over a network using the NFS, FTP, or HTTP protocols. A network installation can be started from a boot CD-ROM, a bootable flash memory drive, or by using the <code class="command">askmethod</code> boot option with the Fedora CD #1 or DVD. Alternatively, if the system to be installed contains a network interface card (NIC) with Pre-Execution Environment (PXE) support, it can be configured to boot from files on another networked system rather than local media such as a CD-ROM.
</div><div class="para">
	For a PXE network installation, the client's NIC with PXE support sends out a broadcast request for DHCP information. The DHCP server provides the client with an IP address, other network information such as name server, the IP address or hostname of the <code class="command">tftp</code> server (which provides the files necessary to start the installation program), and the location of the files on the <code class="command">tftp</code> server. This is possible because of PXELINUX, which is part of the <code class="filename">syslinux</code> package.
</div><div class="para">
		In the past, administrators needed to perform a great deal of manual configuration to produce an installation server. However, if you have a Red Hat Enterprise Linux, CentOS, or Fedora server on your local network, you can use <span class="package">cobbler</span> to perform these tasks. To configure a PXE server manually, see <a class="xref" href="sn-pxe-server-manual.html" title="11.5.Â Manually configure a PXE server">SectionÂ 11.5, â€œManually configure a PXE serverâ€</a>.
	</div><div class="para">
		To perform the tasks in this section, switch to the <code class="systemitem">root</code> account with the command <code class="command">su -</code>. As an alternative, you can run a command with the <code class="option">-c</code> option, using the form <code class="command">su -c '<em class="replaceable"><code>command</code></em>'</code>.
	</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-install-cobbler">11.1.Â Setting Up <span class="package">cobbler</span></h2></div></div></div><div class="para">
			To install <span class="package">cobbler</span> use the following command:
		</div><pre class="screen"><code class="command">yum -y install cobbler</code>
</pre><div class="para">
			The <code class="command">cobbler</code> command can check its own settings for validity and report the results. Run the following command to check the settings:
		</div><pre class="screen"><code class="command">cobbler check</code>
</pre><div class="para">
			Change the settings in the <code class="filename">/var/lib/cobbler/settings</code> file to reflect the IP address information for the server. You must change at least the <code class="option">server</code> and <code class="option">next_server</code> options, although these options may point to the same IP address.
		</div><div class="para">
			If you are not already running a DHCP server, you should also change the <code class="option">manage_dhcp</code> option to <strong class="userinput"><code>1</code></strong>. If you are running a DHCP server, configure it according to the instructions found in the <span class="package">syslinux</span> package documentation. For more information, refer to your local files <code class="filename">/usr/share/doc/syslinux-<em class="replaceable"><code>version</code></em>/syslinux.doc</code> and <code class="filename">/usr/share/doc/syslinux-<em class="replaceable"><code>version</code></em>/pxelinux.doc</code>.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-medialess-booting.html"><strong>Prev</strong>10.3.Â Booting to Installation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-cobbler-setup-distro.html"><strong>Next</strong>11.2.Â Setting Up the Distribution</a></li></ul></body></html>


--- NEW FILE ap-medialess-install.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ChapterÂ 10.Â Installing Without Media</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-Advanced_installation_options.html" title="PartÂ III.Â Advanced installation options" /><link rel="prev" href="sn-mode-upgradeany.html" title="9.6.4.Â Upgrading your computer" /><link rel="next" href="sn-medialess-editing-grub-conf.html" title="10.2.Â Editing the GRUB Configuration" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-mode-upgradeany.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-medialess-editing-grub-conf.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="ap-medialess-install">ChapterÂ 10.Â Installing Without Media</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ap-medialess-install.html#sn-medialess-getting-files">10.1. Retrieving Boot Files</a></span></dt><dt><span class="section"><a href="sn-medialess-editing-grub-conf.html">10.2. Editing the GRUB Configuration</a></span></dt><dt><span class="section"><a href="sn-medialess-booting.html">10.3. Booting to Installation</a></span></dt></dl></div><div class="para">
		This section discusses how to install Fedora to your system without making any additional physical media. Instead, you can use your existing <span class="application"><strong>GRUB</strong></span> boot loader to start the installation program.
	</div><div class="important"><h2>Linux Required</h2><div class="para">
			This procedure assumes you are already using Fedora or another relatively modern Linux distribution, and the <span class="application"><strong>GRUB</strong></span> boot loader. It also assumes you are a somewhat experienced Linux user.
		</div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-medialess-getting-files">10.1.Â Retrieving Boot Files</h2></div></div></div><div class="para">
			To perform an installation without media or a PXE server, your system must have two files stored locally, a kernel and an initial RAM disk.
		</div><div class="procedure"><ol class="1"><li><div class="para">
					Download a Live image or DVD distribution, or to locate an installation mirror, visit <a href="http://mirrors.fedoraproject.org/publiclist/Fedora/11/">http://mirrors.fedoraproject.org/publiclist/Fedora/11/</a>.
				</div></li><li><div class="para">
					Locate the <code class="filename">isolinux/</code> folder using one of the following methods:
				</div><div class="itemizedlist"><ul><li><div class="para">
							If you chose to download an image, open it with the appropriate desktop tool. If you are using Fedora, double-click the file to open it with the <span class="application"><strong>Archive Manager</strong></span>. Open the <code class="filename">isolinux/</code> folder.
						</div></li><li><div class="para">
							If you chose not to download a whole image because you wish to install via the network, locate the desired release. In general, once you find a suitable mirror, browse to the <code class="filename">releases/11/Fedora/<em class="replaceable"><code>arch</code></em>/os/isolinux/</code> folder.
						</div></li></ul></div><div class="note"><h2>Installation Types Available</h2><div class="para">
						If you download an image, you may then choose a hard disk-based installation or a network installation. If you only download selected files from a mirror, you may only perform a network installation.
					</div></div></li><li><div class="para">
					Copy the <code class="filename">vmlinuz</code> and <code class="filename">initrd.img</code> files from the chosen source to the <code class="filename">/boot/</code> directory, renaming them to <code class="filename">vmlinuz-install</code> and <code class="filename">initrd.img-install</code>You must have <code class="systemitem">root</code> privileges to write files into the <code class="filename">/boot/</code> directory.
				</div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-mode-upgradeany.html"><strong>Prev</strong>9.6.4.Â Upgrading your computer</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-medialess-editing-grub-conf.html"><strong>Next</strong>10.2.Â Editing the GRUB Configuration</a></li></ul></body></html>


--- NEW FILE ap-rescuemode.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ChapterÂ 17.Â Basic System Recovery</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-After_installation.html" title="PartÂ IV.Â After installation" /><link rel="prev" href="sn-community.html" title="16.6.Â Joining the Fedora Community" /><link rel="next" href="s1-rescuemode-boot.html" title="17.2.Â Booting into Rescue Mode" /></head><body class="draft "><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 Sit
 e" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-community.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-rescuemode-boot.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="ap-rescuemode">ChapterÂ 17.Â Basic System Recovery</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ap-rescuemode.html#s1-rescuemode-common-problems">17.1. Common Problems</a></span></dt><dd><dl><dt><span class="section"><a href="ap-rescuemode.html#s2-rescuemode-whatis-unable-boot">17.1.1. Unable to Boot into Fedora</a></span></dt><dt><span class="section"><a href="ap-rescuemode.html#s2-rescuemode-hardware-troubles">17.1.2. Hardware/Software Problems</a></span></dt><dt><span class="section"><a href="ap-rescuemode.html#s2-rescuemode-root-password">17.1.3. Root Password</a></span></dt></dl></dd><dt><span class="section"><a 
 href="s1-rescuemode-boot.html">17.2. Booting into Rescue Mode</a></span></dt><dd><dl><dt><span class="section"><a href="s1-rescuemode-boot.html#s2-rescuemode-boot-reinstall-bootloader">17.2.1. Reinstalling the Boot Loader</a></span></dt></dl></dd><dt><span class="section"><a href="s1-rescuemode-booting-single.html">17.3. Booting into Single-User Mode</a></span></dt><dt><span class="section"><a href="s1-rescuemode-booting-emergency.html">17.4. Booting into Emergency Mode</a></span></dt></dl></div><a id="id847494" 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" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-rescuemode-common-problems">17.1.Â Common Problems</h2></div></div></div><a id="id814730" 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><div class="para">
					You are unable to boot normally into Fedora (runlevel 3 or 5).
				</div></li><li><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><div class="para">
					You forgot the root password.
				</div></li></ul></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-rescuemode-whatis-unable-boot">17.1.1.Â Unable to Boot into Fedora</h3></div></div></div><a id="id832051" class="indexterm"></a><a id="id806115" 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="s1-rescuemode-boot.html#s2-rescuemode-boot-reinstall-bootloader" title="17.2.1.Â Reinstalling the Boot Loader">SectionÂ 17.2.1, â€œReinstalling the Boot Loaderâ€</a>.
			</div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-rescuemode-hardware-troubles">17.1.2.Â Hardware/Software Problems</h3></div></div></div><a id="id817765" 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" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-rescuemode-root-password">17.1.3.Â Root Password</h3></div></div></div><a id="id799834" 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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-community.html"><strong>Prev</strong>16.6.Â Joining the Fedora Community</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-rescuemode-boot.html"><strong>Next</strong>17.2.Â Booting into Rescue Mode</a></li></ul></body></html>


--- NEW FILE ap-techref.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>AppendixÂ G.Â Other Technical Documentation</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-Technical_appendixes.html" title="PartÂ V.Â Technical appendixes" /><link rel="prev" href="s1-boot-init-shutdown-shutdown.html" title="F.5.Â Shutting Down" /><link rel="next" href="ch-Contributors_and_production_methods.html" title="AppendixÂ H.Â Contributors and production methods" /></head><body class="draft "><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_Con
 tent/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-boot-init-shutdown-shutdown.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-Contributors_and_production_methods.html"><strong>Next</strong></a></li></ul><div class="appendix" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h1 id="ap-techref" class="title">Other Technical Documentation</h1></div></div></div><div class="para">
		This document provides a reference for using the Fedora installation software, known as <code class="command">anaconda</code>. To learn more about 
		<a id="id816665" class="indexterm"></a>
		<code class="command">anaconda</code>, visit the project Web page: <a href="http://www.fedoraproject.org/wiki/Anaconda">http://www.fedoraproject.org/wiki/Anaconda</a>.
	</div><div class="para">
		Both <code class="command">anaconda</code> and Fedora systems use a common set of software components. For detailed information on key technologies, refer to the Web sites listed below:
	</div><div class="variablelist"><dl><dt><span class="term">Boot Loader</span></dt><dd><div class="para">
					Fedora uses the 
					<a id="id852244" class="indexterm"></a>
					<code class="command">GRUB</code> boot loader. Refer to <a href="http://www.gnu.org/software/grub/">http://www.gnu.org/software/grub/</a> for more information.
				</div></dd><dt><span class="term">Disk Partitioning</span></dt><dd><div class="para">
					Fedora uses <code class="command">parted</code> to partition disks. Refer to <a href="http://www.gnu.org/software/parted/">http://www.gnu.org/software/parted/</a> for more information.
				</div></dd><dt><span class="term">Storage Management</span></dt><dd><div class="para">
					<a id="id805968" class="indexterm"></a>
					 Logical Volume Management (LVM) provides administrators with a range of facilities to manage storage. By default, the Fedora installation process formats drives as LVM volumes. Refer to <a href="http://www.tldp.org/HOWTO/LVM-HOWTO/">http://www.tldp.org/HOWTO/LVM-HOWTO/</a> for more information.
				</div></dd><dt><span class="term">Audio Support</span></dt><dd><div class="para">
					The Linux kernel used by Fedora incorporates 
					<a id="id886650" class="indexterm"></a>
					 PulseAudio audio server. For more information about PulseAudio, refer to the project documentation: <a href="http://www.pulseaudio.org/wiki/Documentation">http://www.pulseaudio.org/wiki/Documentation</a>.
				</div></dd><dt><span class="term">Graphics System</span></dt><dd><div class="para">
					Both the installation system and Fedora use the 
					<a id="id933353" class="indexterm"></a>
					<code class="command">Xorg</code> suite to provide graphical capabilities. Components of <code class="command">Xorg</code> manage the display, keyboard and mouse for the desktop environments that users interact with. Refer to <a href="http://www.x.org/">http://www.x.org/</a> for more information.
				</div></dd><dt><span class="term">Remote Displays</span></dt><dd><div class="para">
					Fedora and <code class="command">anaconda</code> include 
					<a id="id803158" class="indexterm"></a>
					 VNC (Virtual Network Computing) software to enable remote access to graphical displays. For more information about VNC, refer to the documentation on the RealVNC Web site: <a href="http://www.realvnc.com/documentation.html">http://www.realvnc.com/documentation.html</a>.
				</div></dd><dt><span class="term">Command-line Interface</span></dt><dd><div class="para">
					By default, Fedora uses the GNU <code class="command">bash</code> shell to provide a command-line interface. The GNU Core Utilities complete the command-line environment. Refer to <a href="http://www.gnu.org/software/bash/bash.html">http://www.gnu.org/software/bash/bash.html</a> for more information on <code class="command">bash</code>. To learn more about the GNU Core Utilities, refer to <a href="http://www.gnu.org/software/coreutils/">http://www.gnu.org/software/coreutils/</a>.
				</div></dd><dt><span class="term">Remote System Access</span></dt><dd><div class="para">
					Fedora incorporates the 
					<a id="id868087" class="indexterm"></a>
					 OpenSSH suite to provide remote access to the system. The SSH 
					<a id="id854495" class="indexterm"></a>
					 service enables a number of functions, which include access to the command-line from other systems, remote command execution, and network file transfers. During the installation process <code class="command">anaconda</code> may use the <code class="command">scp</code>
					<a id="id854522" class="indexterm"></a>
					 feature of OpenSSH to transfer crash reports to remote systems. Refer to the OpenSSH Web site for more information: <a href="http://www.openssh.com/">http://www.openssh.com/</a>.
				</div></dd><dt><span class="term">Access Control</span></dt><dd><div class="para">
					<a id="id799171" class="indexterm"></a>
					 SELinux provides Mandatory Access Control (MAC) capabilities that supplement the standard Linux security features. Refer to the SELinux Project Pages for more information: <a href="http://docs.fedoraproject.org/selinux-guide">http://docs.fedoraproject.org/selinux-guide</a>.
				</div></dd><dt><span class="term">Firewall</span></dt><dd><div class="para">
					The Linux kernel used by Fedora incorporates the <code class="command">netfilter</code> framework to provide 
					<a id="id908473" class="indexterm"></a>
					 firewall features. The Netfilter project website provides documentation for both <code class="command">netfilter</code>, and the <code class="command">iptables</code> administration facilities: <a href="http://netfilter.org/documentation/index.html">http://netfilter.org/documentation/index.html</a>.
				</div></dd><dt><span class="term">Software Installation</span></dt><dd><div class="para">
					Fedora uses 
					<a id="id867978" class="indexterm"></a>
					<code class="command">yum</code> to manage the RPM packages that make up the system. Refer to <a href="http://docs.fedoraproject.org/yum/">http://docs.fedoraproject.org/yum/</a> for more information.
				</div></dd><dt><span class="term">Virtualization</span></dt><dd><div class="para">
					<a id="id928166" class="indexterm"></a>
					 Virtualization provides the capability to simultaneously run multiple operating systems on the same computer. Fedora also includes tools to install and manage the secondary systems on a Fedora host. You may select virtualization support during the installation process, or at any time thereafter. Refer to <a href="http://www.fedoraproject.org/wiki/Tools/Virtualization">http://www.fedoraproject.org/wiki/Tools/Virtualization</a> for more information.
				</div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-boot-init-shutdown-shutdown.html"><strong>Prev</strong>F.5.Â Shutting Down</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-Contributors_and_production_methods.html"><strong>Next</strong>AppendixÂ H.Â Contributors and production methods</a></li></ul></body></html>


--- NEW FILE apcs02.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>C.2.Â Encrypting block devices using dm-crypt/LUKS</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="Disk_Encryption_Guide.html" title="AppendixÂ C.Â Disk Encryption Guide" /><link rel="prev" href="Disk_Encryption_Guide.html" title="AppendixÂ C.Â Disk Encryption Guide" /><link rel="next" href="apcs02s02.html" title="C.2.2.Â How will I access the encrypted devices after installation? (System Startup)" /></head><body class="draft "><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.or
 g"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="Disk_Encryption_Guide.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apcs02s02.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="id906540">C.2.Â Encrypting block devices using dm-crypt/LUKS </h2></div></div></div><div class="para">
			<a href="http://luks.endorphin.org"> LUKS</a> (Linux Unified Key Setup) is a specification for block device encryption. It establishes an on-disk format for the data, as well as a passphrase/key management policy.
		</div><div class="para">
			LUKS uses the kernel device mapper subsystem via the <code class="command">dm-crypt</code> module. This arrangement provides a low-level mapping that handles encryption and decryption of the device's data. User-level operations, such as creating and accessing encrypted devices, are accomplished through the use of the <code class="command">cryptsetup</code> utility.
		</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id785142">C.2.1.Â Overview of LUKS </h3></div></div></div><div class="itemizedlist"><ul><li><div class="para">
						What LUKS does: 
						<div class="itemizedlist"><ul><li><div class="para">
									LUKS encrypts entire block devices 
									<div class="itemizedlist"><ul><li><div class="para">
												LUKS is thereby well-suited for protecting the contents of mobile devices such as: 
												<div class="itemizedlist"><ul><li><div class="para">
															Removable storage media
														</div></li><li><div class="para">
															Laptop disk drives
														</div></li></ul></div>
											</div></li></ul></div>
								</div></li><li><div class="para">
									The underlying contents of the encrypted block device are arbitrary. 
									<div class="itemizedlist"><ul><li><div class="para">
												This makes it useful for encrypting <code class="command">swap</code> devices.
											</div></li><li><div class="para">
												This can also be useful with certain databases that use specially formatted block devices for data storage.
											</div></li></ul></div>
								</div></li><li><div class="para">
									LUKS uses the existing device mapper kernel subsystem. 
									<div class="itemizedlist"><ul><li><div class="para">
												This is the same subsystem used by LVM, so it is well tested.
											</div></li></ul></div>
								</div></li><li><div class="para">
									LUKS provides passphrase strengthening. 
									<div class="itemizedlist"><ul><li><div class="para">
												This protects against dictionary attacks.
											</div></li></ul></div>
								</div></li><li><div class="para">
									LUKS devices contain multiple key slots. 
									<div class="itemizedlist"><ul><li><div class="para">
												This allows users to add backup keys/passphrases.
											</div></li></ul></div>
								</div></li></ul></div>
					</div></li><li><div class="para">
						What LUKS does <span class="emphasis"><em>not</em></span> do: 
						<div class="itemizedlist"><ul><li><div class="para">
									LUKS is not well-suited for applications requiring many (more than eight) users to have distinct access keys to the same device.
								</div></li><li><div class="para">
									LUKS is not well-suited for applications requiring file-level encryption.
								</div></li></ul></div>
					</div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="Disk_Encryption_Guide.html"><strong>Prev</strong>AppendixÂ C.Â Disk Encryption Guide</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="apcs02s02.html"><strong>Next</strong>C.2.2.Â How will I access the encrypted devices af...</a></li></ul></body></html>


--- NEW FILE apcs02s02.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>C.2.2.Â How will I access the encrypted devices after installation? (System Startup)</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="apcs02.html" title="C.2.Â Encrypting block devices using dm-crypt/LUKS" /><link rel="prev" href="apcs02.html" title="C.2.Â Encrypting block devices using dm-crypt/LUKS" /><link rel="next" href="apcs02s03.html" title="C.2.3.Â Choosing a Good Passphrase" /></head><body class="draft "><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="Com
 mon_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apcs02s03.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id785326">C.2.2.Â How will I access the encrypted devices after installation? (System Startup) </h3></div></div></div><div class="para">
				During system startup you will be presented with a passphrase prompt. After the correct passphrase has been provided the system will continue to boot normally. If you used different passphrases for multiple encypted devices you may need to enter more than one passphrase during the startup.
			</div><div class="para">
				<div class="note"><h2>Tip</h2><div class="para">
						Consider using the same passphrase for all encrypted block devices in a given system. This will simplify system startup and you will have fewer passphrases to remember. Just make sure you choose a good passphrase!
					</div></div>
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs02.html"><strong>Prev</strong>C.2.Â Encrypting block devices using dm-crypt/LUKS </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="apcs02s03.html"><strong>Next</strong>C.2.3.Â Choosing a Good Passphrase </a></li></ul></body></html>


--- NEW FILE apcs02s03.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>C.2.3.Â Choosing a Good Passphrase</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="apcs02.html" title="C.2.Â Encrypting block devices using dm-crypt/LUKS" /><link rel="prev" href="apcs02s02.html" title="C.2.2.Â How will I access the encrypted devices after installation? (System Startup)" /><link rel="next" href="apcs03.html" title="C.3.Â Creating Encrypted Block Devices in Anaconda" /></head><body class="draft "><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="Com
 mon_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs02s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apcs03.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id839248">C.2.3.Â Choosing a Good Passphrase </h3></div></div></div><div class="para">
				While dm-crypt/LUKS supports both keys and passphrases, the anaconda installer only supports the use of passphrases for creating and accessing encrypted block devices during installation.
			</div><div class="para">
				LUKS does provide passphrase strengthening but it is still a good idea to choose a good (meaning "difficult to guess") passphrase. Note the use of the term "passphrase", as opposed to the term "password". This is intentional. Providing a phrase containing multiple words to increase the security of your data is important.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs02s02.html"><strong>Prev</strong>C.2.2.Â How will I access the encrypted devices af...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="apcs03.html"><strong>Next</strong>C.3.Â Creating Encrypted Block Devices in Anaconda </a></li></ul></body></html>


--- NEW FILE apcs03.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>C.3.Â Creating Encrypted Block Devices in Anaconda</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="Disk_Encryption_Guide.html" title="AppendixÂ C.Â Disk Encryption Guide" /><link rel="prev" href="apcs02s03.html" title="C.2.3.Â Choosing a Good Passphrase" /><link rel="next" href="apcs03s02.html" title="C.3.2.Â Limitations of Anaconda's Block Device Encryption Support" /></head><body class="draft "><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/imag
 es/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs02s03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apcs03s02.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="id839268">C.3.Â Creating Encrypted Block Devices in Anaconda </h2></div></div></div><div class="para">
			You can create encrypted devices during system installation. This allows you to easily configure a system with encrypted partitions.
		</div><div class="para">
			To enable block device encryption, check the "Encrypt System" checkbox when selecting automatic partitioning or the "Encrypt" checkbox when creating an individual partition, software RAID array, or logical volume. After you finish partitioning, you will be prompted for an encryption passphrase. This passphrase will be required to access the encrypted devices. If you have pre-existing LUKS devices and provided correct passphrases for them earlier in the install process the passphrase entry dialog will also contain a checkbox. Checking this checkbox indicates that you would like the new passphrase to be added to an available slot in each of the pre-existing encrypted block devices.
		</div><div class="para">
			<div class="note"><h2>Tip</h2><div class="para">
					Checking the "Encrypt System" checkbox on the "Automatic Partitioning" screen and then choosing "Create custom layout" does not cause any block devices to be encrypted automatically.
				</div></div>
		</div><div class="para">
			<div class="note"><h2>Tip</h2><div class="para">
					You can use <code class="command">kickstart</code> to set a separate passphrase for each new encrypted block device.
				</div></div>
		</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id906052">C.3.1.Â What Kinds of Block Devices Can Be Encrypted? </h3></div></div></div><div class="para">
				Most types of block devices can be encrypted using LUKS. From anaconda you can encrypt partitions, LVM physical volumes, LVM logical volumes, and software RAID arrays.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs02s03.html"><strong>Prev</strong>C.2.3.Â Choosing a Good Passphrase </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="apcs03s02.html"><strong>Next</strong>C.3.2.Â Limitations of Anaconda's Block Device Enc...</a></li></ul></body></html>


--- NEW FILE apcs03s02.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>C.3.2.Â Limitations of Anaconda's Block Device Encryption Support</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="apcs03.html" title="C.3.Â Creating Encrypted Block Devices in Anaconda" /><link rel="prev" href="apcs03.html" title="C.3.Â Creating Encrypted Block Devices in Anaconda" /><link rel="next" href="apcs04.html" title="C.4.Â Creating Encrypted Block Devices on the Installed System After Installation" /></head><body class="draft "><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.fedorap
 roject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apcs04.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id906064">C.3.2.Â Limitations of Anaconda's Block Device Encryption Support </h3></div></div></div><div class="para">
				This section is about Anaconda's Block Device Encryption Support
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs03.html"><strong>Prev</strong>C.3.Â Creating Encrypted Block Devices in Anaconda </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="apcs04.html"><strong>Next</strong>C.4.Â Creating Encrypted Block Devices on the Inst...</a></li></ul></body></html>


--- NEW FILE apcs04.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>C.4.Â Creating Encrypted Block Devices on the Installed System After Installation</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="Disk_Encryption_Guide.html" title="AppendixÂ C.Â Disk Encryption Guide" /><link rel="prev" href="apcs03s02.html" title="C.3.2.Â Limitations of Anaconda's Block Device Encryption Support" /><link rel="next" href="randomize_device.html" title="C.4.2.Â Optional: Fill the device with random data" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs03s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="randomize_device.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="id906088">C.4.Â Creating Encrypted Block Devices on the Installed System After Installation </h2></div></div></div><div class="para">
			Encrypted block devices can be created and configured after installation.
		</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id885513">C.4.1.Â Create the block devices </h3></div></div></div><div class="para">
				Create the block devices you want to encrypt by using <code class="command">parted</code>, <code class="command">pvcreate</code>, <code class="command">lvcreate</code> and <code class="command">mdadm</code>.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs03s02.html"><strong>Prev</strong>C.3.2.Â Limitations of Anaconda's Block Device Enc...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="randomize_device.html"><strong>Next</strong>C.4.2.Â Optional: Fill the device with random data</a></li></ul></body></html>


--- NEW FILE apcs04s03.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>C.4.3.Â Format the device as a dm-crypt/LUKS encrypted device</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="apcs04.html" title="C.4.Â Creating Encrypted Block Devices on the Installed System After Installation" /><link rel="prev" href="randomize_device.html" title="C.4.2.Â Optional: Fill the device with random data" /><link rel="next" href="apcs04s04.html" title="C.4.4.Â Create a mapping to allow access to the device's decrypted contents" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="randomize_device.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apcs04s04.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id927032">C.4.3.Â Format the device as a dm-crypt/LUKS encrypted device </h3></div></div></div><div class="para">
				<div class="warning"><h2>Warning</h2><div class="para">
						The command below will destroy any existing data on the device.
					</div></div>
				
<pre class="programlisting">cryptsetup luksFormat <device>
</pre>
			</div><div class="para">
				<div class="note"><h2>Tip</h2><div class="para">
						For more information, read the <code class="command">cryptsetup(8)</code> man page.
					</div></div>
			</div><div class="para">
				After supplying the passphrase twice the device will be formatted for use. To verify, use the following command:
			</div><pre class="programlisting">cryptsetup isLuks <device> && echo Success
</pre><div class="para">
				To see a summary of the encryption information for the device, use the following command:
			</div><pre class="programlisting">cryptsetup luksDump <device>
</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="randomize_device.html"><strong>Prev</strong>C.4.2.Â Optional: Fill the device with random data</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="apcs04s04.html"><strong>Next</strong>C.4.4.Â Create a mapping to allow access to the de...</a></li></ul></body></html>


--- NEW FILE apcs04s04.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>C.4.4.Â Create a mapping to allow access to the device's decrypted contents</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="apcs04.html" title="C.4.Â Creating Encrypted Block Devices on the Installed System After Installation" /><link rel="prev" href="apcs04s03.html" title="C.4.3.Â Format the device as a dm-crypt/LUKS encrypted device" /><link rel="next" href="apcs04s05.html" title="C.4.5.Â Create filesystems on the mapped device, or continue to build complex storage structures using the mapped device" /></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_C
 ontent/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><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs04s03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apcs04s05.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id854179">C.4.4.Â Create a mapping to allow access to the device's decrypted contents </h3></div></div></div><div class="para">
				To access the device's decrypted contents, a mapping must be established using the kernel <code class="command">device-mapper</code>.
			</div><div class="para">
				It is useful to choose a meaningful name for this mapping. LUKS provides a UUID (Universally Unique Identifier) for each device. This, unlike the device name (eg: <code class="filename">/dev/sda3</code>), is guaranteed to remain constant as long as the LUKS header remains intact. To find a LUKS device's UUID, run the following command:
			</div><pre class="programlisting">cryptsetup luksUUID <device>
</pre><div class="para">
				An example of a reliable, informative and unique mapping name would be <code class="command">luks-<uuid></code>, where <uuid> is replaced with the device's LUKS UUID (eg: <code class="command">luks-50ec957a-5b5a-47ee-85e6-f8085bbc97a8</code>). This naming convention might seem unwieldy but is it not necessary to type it often.
			</div><pre class="programlisting">cryptsetup luksOpen <device> <name>
</pre><div class="para">
				There should now be a device node, <code class="filename">/dev/mapper/<name></code>, which represents the decrypted device. This block device can be read from and written to like any other unencrypted block device.
			</div><div class="para">
				To see some information about the mapped device, use the following command:
			</div><pre class="programlisting">dmsetup info <name>
</pre><div class="para">
				<div class="note"><h2>Tip</h2><div class="para">
						For more information, read the <code class="command">dmsetup(8)</code> man page.
					</div></div>
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs04s03.html"><strong>Prev</strong>C.4.3.Â Format the device as a dm-crypt/LUKS encry...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="apcs04s05.html"><strong>Next</strong>C.4.5.Â Create filesystems on the mapped device, o...</a></li></ul></body></html>


--- NEW FILE apcs04s05.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>C.4.5.Â Create filesystems on the mapped device, or continue to build complex storage structures using the mapped device</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="apcs04.html" title="C.4.Â Creating Encrypted Block Devices on the Installed System After Installation" /><link rel="prev" href="apcs04s04.html" title="C.4.4.Â Create a mapping to allow access to the device's decrypted contents" /><link rel="next" href="apcs04s06.html" title="C.4.6.Â Add the mapping information to /etc/crypttab" /></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/im
 ages/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><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs04s04.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apcs04s06.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id807473">C.4.5.Â Create filesystems on the mapped device, or continue to build complex storage structures using the mapped device </h3></div></div></div><div class="para">
				Use the mapped device node (<code class="filename">/dev/mapper/<name></code>) as any other block device. To create an <code class="command">ext2</code> filesystem on the mapped device, use the following command:
			</div><pre class="programlisting">mke2fs /dev/mapper/<name>
</pre><div class="para">
				To mount this filesystem on <code class="filename">/mnt/test</code>, use the following command:
			</div><div class="para">
				<div class="important"><h2>Important</h2><div class="para">
						The directory <code class="filename">/mnt/test</code> must exist before executing this command.
					</div></div>
			</div><pre class="programlisting">mount /dev/mapper/<name> /mnt/test
</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs04s04.html"><strong>Prev</strong>C.4.4.Â Create a mapping to allow access to the de...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="apcs04s06.html"><strong>Next</strong>C.4.6.Â Add the mapping information to /etc/cryptt...</a></li></ul></body></html>


--- NEW FILE apcs04s06.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>C.4.6.Â Add the mapping information to /etc/crypttab</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="apcs04.html" title="C.4.Â Creating Encrypted Block Devices on the Installed System After Installation" /><link rel="prev" href="apcs04s05.html" title="C.4.5.Â Create filesystems on the mapped device, or continue to build complex storage structures using the mapped device" /><link rel="next" href="apcs04s07.html" title="C.4.7.Â Add an entry to /etc/fstab" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs04s05.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apcs04s07.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id851189">C.4.6.Â Add the mapping information to <code class="filename">/etc/crypttab</code></h3></div></div></div><div class="para">
				In order for the system to set up a mapping for the device, an entry must be present in the <code class="filename">/etc/crypttab</code> file. If the file doesn't exist, create it and change the owner and group to root (<code class="command">root:root</code>) and change the mode to <code class="command">0744</code>. Add a line to the file with the following format:
			</div><pre class="programlisting"><name>  <device>  none
</pre><div class="para">
				The <device> field should be given in the form "UUID=<luks_uuid>", where <luks_uuid> is the LUKS uuid as given by the command <code class="command">cryptsetup luksUUID <device></code>. This ensures the correct device will be identified and used even if the device node (eg: <code class="filename">/dev/sda5</code>) changes.
			</div><div class="para">
				<div class="note"><h2>Tip</h2><div class="para">
						For details on the format of the <code class="filename">/etc/crypttab</code> file, read the <code class="command">crypttab(5)</code> man page.
					</div></div>
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs04s05.html"><strong>Prev</strong>C.4.5.Â Create filesystems on the mapped device, o...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="apcs04s07.html"><strong>Next</strong>C.4.7.Â Add an entry to /etc/fstab</a></li></ul></body></html>


--- NEW FILE apcs04s07.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>C.4.7.Â Add an entry to /etc/fstab</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="apcs04.html" title="C.4.Â Creating Encrypted Block Devices on the Installed System After Installation" /><link rel="prev" href="apcs04s06.html" title="C.4.6.Â Add the mapping information to /etc/crypttab" /><link rel="next" href="apcs05.html" title="C.5.Â Common Post-Installation Tasks" /></head><body class="draft "><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/ima
 ges/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs04s06.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apcs05.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id968055">C.4.7.Â Add an entry to <code class="filename">/etc/fstab</code></h3></div></div></div><div class="para">
				Add an entry to /etc/fstab. This is only necessary if you want to establish a persistent association between the device and a mountpoint. Use the decrypted device, <code class="filename">/dev/mapper/<name></code> in the <code class="filename">/etc/fstab</code> file.
			</div><div class="para">
				In many cases it is desirable to list devices in <code class="filename">/etc/fstab</code> by UUID or by a filesystem label. The main purpose of this is to provide a constant identifier in the event that the device name (eg: <code class="filename">/dev/sda4</code>) changes. LUKS device names in the form of <code class="filename">/dev/mapper/luks-<luks_uuid></code> are based only on the device's LUKS UUID, and are therefore guaranteed to remain constant. This fact makes them suitable for use in <code class="filename">/etc/fstab</code>.
			</div><div class="para">
				<div class="note"><h2>Title</h2><div class="para">
						For details on the format of the <code class="filename">/etc/fstab</code> file, read the <code class="command">fstab(5)</code> man page.
					</div></div>
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs04s06.html"><strong>Prev</strong>C.4.6.Â Add the mapping information to /etc/cryptt...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="apcs05.html"><strong>Next</strong>C.5.Â Common Post-Installation Tasks </a></li></ul></body></html>


--- NEW FILE apcs05.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>C.5.Â Common Post-Installation Tasks</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="Disk_Encryption_Guide.html" title="AppendixÂ C.Â Disk Encryption Guide" /><link rel="prev" href="apcs04s07.html" title="C.4.7.Â Add an entry to /etc/fstab" /><link rel="next" href="apcs05s02.html" title="C.5.2.Â Add a new passphrase to an existing device" /></head><body class="draft "><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="Docu
 mentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs04s07.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apcs05s02.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="id805134">C.5.Â Common Post-Installation Tasks </h2></div></div></div><div class="para">
			The following sections are about common post-installation tasks.
		</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="new_key">C.5.1.Â Set a randomly generated key as an additional way to access an encrypted block device</h3></div></div></div><div class="para">
				These sections are about generating keys and adding keys.
			</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="id843763">C.5.1.1.Â Generate a key </h4></div></div></div><div class="para">
					This will generate a 256-bit key in the file <code class="filename">$HOME/keyfile</code>.
				</div><pre class="programlisting">
		dd if=/dev/urandom of=$HOME/keyfile bs=32 count=1
		chmod 600 $HOME/keyfile
</pre></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="id843785">C.5.1.2.Â Add the key to an available keyslot on the encrypted device </h4></div></div></div><pre class="programlisting">cryptsetup luksAddKey <device> ~/keyfile
</pre></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs04s07.html"><strong>Prev</strong>C.4.7.Â Add an entry to /etc/fstab</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="apcs05s02.html"><strong>Next</strong>C.5.2.Â Add a new passphrase to an existing device </a></li></ul></body></html>


--- NEW FILE apcs05s02.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>C.5.2.Â Add a new passphrase to an existing device</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="apcs05.html" title="C.5.Â Common Post-Installation Tasks" /><link rel="prev" href="apcs05.html" title="C.5.Â Common Post-Installation Tasks" /><link rel="next" href="apcs05s03.html" title="C.5.3.Â Remove a passphrase or key from a device" /></head><body class="draft "><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="Documen
 tation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs05.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apcs05s03.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id843800">C.5.2.Â Add a new passphrase to an existing device </h3></div></div></div><pre class="programlisting">cryptsetup luksAddKey <device>
</pre><div class="para">
				After being prompted for any one of the existing passprases for authentication, you will be prompted to enter the new passphrase.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs05.html"><strong>Prev</strong>C.5.Â Common Post-Installation Tasks </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="apcs05s03.html"><strong>Next</strong>C.5.3.Â Remove a passphrase or key from a device </a></li></ul></body></html>


--- NEW FILE apcs05s03.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>C.5.3.Â Remove a passphrase or key from a device</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="apcs05.html" title="C.5.Â Common Post-Installation Tasks" /><link rel="prev" href="apcs05s02.html" title="C.5.2.Â Add a new passphrase to an existing device" /><link rel="next" href="sn-partitioning-lvm.html" title="AppendixÂ D.Â Understanding LVM" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs05s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-partitioning-lvm.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id939115">C.5.3.Â Remove a passphrase or key from a device </h3></div></div></div><pre class="programlisting">cryptsetup luksRemoveKey <device>
</pre><div class="para">
				You will be prompted for the passphrase you wish to remove and then for any one of the remaining passphrases for authentication.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs05s02.html"><strong>Prev</strong>C.5.2.Â Add a new passphrase to an existing device </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-partitioning-lvm.html"><strong>Next</strong>AppendixÂ D.Â Understanding LVM</a></li></ul></body></html>


--- NEW FILE appe-Publican-Revision_History.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>AppendixÂ I.Â Revision History</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="index.html" title="Installation Guide" /><link rel="prev" href="sn-Production_methods.html" title="H.2.Â Production methods" /><link rel="next" href="ix01.html" title="Index" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href
 ="sn-Production_methods.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ix01.html"><strong>Next</strong></a></li></ul><div class="appendix" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h1 id="appe-Publican-Revision_History" class="title">Revision History</h1></div></div></div><div class="para">
		<div class="revhistory"><table border="0" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="3"><b>Revision History</b></th></tr><tr><td align="left">Revision 11.0.0</td><td align="left">Wed Apr 01 2009</td><td align="left"><span class="author"><span class="firstname">Hans</span> <span class="surname">De Goede</span></span>, <span class="author"><span class="firstname">Paul</span> <span class="othername">W.</span> <span class="surname">Frields</span></span>, <span class="author"><span class="firstname">Ruediger</span> <span class="surname">Landmann</span></span>, <span class="author"><span class="firstname">David</span> <span class="surname">Nalley</span></span>, <span class="author"><span class="firstname">The anaconda</span> <span class="surname">team</span></span>, <span class="author"><span class="firstname">Red Hat</span> <span class="surname">Engineering Content Services</span></span></td></tr><tr><td align="left" colspan="3">
					<table class="simplelist" border="0" summary="Simple list"><tr><td>Major update, incorporating material from the <em class="citetitle">Red Hat Enterprise Linux Installation Guide</em> and elsewhere, plus fixes for numerous bugs</td></tr></table>
				</td></tr><tr><td align="left">Revision 10.0.1</td><td align="left">Mon Feb 16 2009</td><td align="left"><span class="author"><span class="firstname">Ruediger</span> <span class="surname">Landmann</span></span></td></tr><tr><td align="left" colspan="3">
					<table class="simplelist" border="0" summary="Simple list"><tr><td>Convert to build in Publican</td></tr></table>
				</td></tr><tr><td align="left">Revision 10.0.0</td><td align="left">Mon Nov 24 2008</td><td align="left"><span class="author"><span class="firstname">Karsten</span> <span class="surname">Wade</span></span></td></tr><tr><td align="left" colspan="3">
					<table class="simplelist" border="0" summary="Simple list"><tr><td>Build and publish Fedora 10 version</td></tr></table>
				</td></tr><tr><td align="left">Revision 9.9.2</td><td align="left">Sat Oct 18 2008</td><td align="left"><span class="author"><span class="firstname">Jared</span> <span class="othername">K.</span> <span class="surname">Smith</span></span></td></tr><tr><td align="left" colspan="3">
					<table class="simplelist" border="0" summary="Simple list"><tr><td>Prepare for release of Fedora 10</td></tr></table>
				</td></tr><tr><td align="left">Revision 9.0.2</td><td align="left">Fri Jul 25 2008</td><td align="left"><span class="author"><span class="firstname">Paul</span> <span class="othername">W.</span> <span class="surname">Frields</span></span></td></tr><tr><td align="left" colspan="3">
					<table class="simplelist" border="0" summary="Simple list"><tr><td>Fix incorrect livecd-tools instructions</td></tr></table>
				</td></tr><tr><td align="left">Revision 9.0.1</td><td align="left">Sat Jun 28 2008</td><td align="left"><span class="author"><span class="firstname">Paul</span> <span class="othername">W.</span> <span class="surname">Frields</span></span></td></tr><tr><td align="left" colspan="3">
					<table class="simplelist" border="0" summary="Simple list"><tr><td>Lots of bug fixes</td></tr></table>
				</td></tr><tr><td align="left">Revision 9.0.0</td><td align="left">Tue May 13 2008</td><td align="left"><span class="author"><span class="firstname">Paul</span> <span class="othername">W.</span> <span class="surname">Frields</span></span></td></tr><tr><td align="left" colspan="3">
					<table class="simplelist" border="0" summary="Simple list"><tr><td>Add information on upgrading a distribution</td></tr></table>
				</td></tr></table></div>
	</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-Production_methods.html"><strong>Prev</strong>H.2.Â Production methods</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ix01.html"><strong>Next</strong>Index</a></li></ul></body></html>


--- NEW FILE ch-Contributors_and_production_methods.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>AppendixÂ H.Â Contributors and production methods</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="index.html" title="Installation Guide" /><link rel="prev" href="ap-techref.html" title="AppendixÂ G.Â Other Technical Documentation" /><link rel="next" href="sn-Production_methods.html" title="H.2.Â Production methods" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ap-techref.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-Production_methods.html"><strong>Next</strong></a></li></ul><div class="appendix" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h1 id="ch-Contributors_and_production_methods" class="title">Contributors and production methods</h1></div></div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-Contributors">H.1.Â Contributors</h2></div></div></div><div class="itemizedlist"><ul><li><div class="para">
					<a href="http://fedoraproject.org/wiki/User:Fab">Fabian Affolter</a> (translator - German)
				</div></li><li><div class="para">
					<a href="http://fedoraproject.org/wiki/AmanAlam">Amanpreet Singh Alam</a> (translator - Punjabi)
				</div></li><li><div class="para">
					Jean-Paul Aubry (translator - French)
				</div></li><li><div class="para">
					David Barzilay (translator - Brazilian Portuguese)
				</div></li><li><div class="para">
					<a href="http://fedoraproject.org/wiki/User:Beckerde">Domingo Becker</a> (translator - Spanish)
				</div></li><li><div class="para">
					Subhransu Behera (translator - Oriya)
				</div></li><li><div class="para">
					MichaÅ‚ Bentkowski (translator - Polish)
				</div></li><li><div class="para">
					Rahul Bhalerao (translator - Marathi)
				</div></li><li><div class="para">
					Runa Bhattacharjee (translator - Bengali (India))
				</div></li><li><div class="para">
					<a href="http://fedoraproject.org/wiki/TetaBilianou">Teta Bilianou</a> (translator - Greek)
				</div></li><li><div class="para">
					Lucas Brausch (translator - German)
				</div></li><li><div class="para">
					<a href="http://fedoraproject.org/wiki/User:Logan">Hector Daniel Cabrera </a> (translator - Spanish)
				</div></li><li><div class="para">
					<a href="https://fedoraproject.org/wiki/DavidCantrell">David Cantrell</a> (writer - VNC installation)
				</div></li><li><div class="para">
					Guido Caruso (translator - Italian)
				</div></li><li><div class="para">
					Guillaume Chardin (translator - French)
				</div></li><li><div class="para">
					<a href="http://fedoraproject.org/wiki/NikosCharonitakis">Nikos Charonitakis</a> (translator - Greek)
				</div></li><li><div class="para">
					Chester Cheng (translator - Chinese (Traditional))
				</div></li><li><div class="para">
					Glaucia Cintra (translator - Brazilian Portuguese)
				</div></li><li><div class="para">
					Fabien Decroux (translator - French)
				</div></li><li><div class="para">
					<a href="https://fedoraproject.org/wiki/HansdeGoede">Hans De Goede</a> (writer - iSCSI)
				</div></li><li><div class="para">
					Claudio Rodrigo Pereyra Diaz (translator - Spanish)
				</div></li><li><div class="para">
					<a href="http://fedoraproject.org/wiki/PiotrDr%C4%85g">Piotr DrÄ…g</a> (translator - Polish)
				</div></li><li><div class="para">
					<a href="http://fedoraproject.org/wiki/DamienDurand">Damien Durand</a> (translator - French)
				</div></li><li><div class="para">
					<a href="https://fedoraproject.org/wiki/StuartEllis"> Stuart Ellis</a> (writer, editor)
				</div></li><li><div class="para">
					<a href="http://fedoraproject.org/wiki/User:Fakoor"> Ali Fakoor</a> (translator - Persian)
				</div></li><li><div class="para">
					Felix I (translator - Tamil)
				</div></li><li><div class="para">
					Tony Fu (translator - Chinese (Simplified))
				</div></li><li><div class="para">
					<a href="https://fedoraproject.org/wiki/User:Pfrields"> Paul W. Frields</a> (writer, editor)
				</div></li><li><div class="para">
					Paul Gampe (translator - Japanese)
				</div></li><li><div class="para">
					Sree Ganesh (translator - Telugu)
				</div></li><li><div class="para">
					<a href="http://fedoraproject.org/wiki/DimitrisGlezos">Dimitris Glezos</a> (translator - Greek)
				</div></li><li><div class="para">
					<a href="http://fedoraproject.org/wiki/GuillermoGomez">Guillermo GÃ³mez</a> (translator - Spanish)
				</div></li><li><div class="para">
					<a href="http://fedoraproject.org/wiki/RuiGouveia">Rui Gouveia</a> (translator - Portuguese)
				</div></li><li><div class="para">
					Kiyoto James Hashida (translator - Japanese)
				</div></li><li><div class="para">
					Severin Heiniger (translator - German)
				</div></li><li><div class="para">
					Xi Huang (translator - Chinese (Simplified))
				</div></li><li><div class="para">
					Ryuichi Hyugabaru (translator - Japanese)
				</div></li><li><div class="para">
					Jayaradha N (translator - Tamil)
				</div></li><li><div class="para">
					Chris Johnson (writer)
				</div></li><li><div class="para">
					Eunju Kim (translator - Korean)
				</div></li><li><div class="para">
					Michelle J Kim (translator - Korean)
				</div></li><li><div class="para">
					<a href="http://translate.fedoraproject.org/people/kmilos">MiloÅ¡ KomarÄeviÄ‡</a> (translator - Serbian)
				</div></li><li><div class="para">
					Alexey Kostyuk (translator - Russian)
				</div></li><li><div class="para">
					Daniela Kugelmann (translator - German)
				</div></li><li><div class="para">
					<a href="https://fedoraproject.org/wiki/User:Rlandmann">RÃ¼diger Landmann</a> (writer, editor)
				</div></li><li><div class="para">
					<a href="http://translate.fedoraproject.org/people/raada">Magnus Larsson</a> (translator - Swedish)
				</div></li><li><div class="para">
					<a href="https://fedoraproject.org/wiki/ChristopherusLaurentius">Christopherus Laurentius</a> (translator - Indonesian)
				</div></li><li><div class="para">
					Florent Le Coz (translator - French)
				</div></li><li><div class="para">
					Erick Lemon (writer)
				</div></li><li><div class="para">
					Andy Liu (translator - Chinese (Traditional))
				</div></li><li><div class="para">
					Wei Liu (translator - Chinese (Simplified))
				</div></li><li><div class="para">
					Yelitza Louze (translator - Spanish)
				</div></li><li><div class="para">
					Gan Lu (translator - Chinese (Simplified))
				</div></li><li><div class="para">
					<a href="http://fedoraproject.org/wiki/IgorMiletic">Igor MiletiÄ‡</a> (translator - Serbian)
				</div></li><li><div class="para">
					Noriko Mizumoto (translator - Japanese)
				</div></li><li><div class="para">
					Jeremy W. Mooney (writer)
				</div></li><li><div class="para">
					EnikÅ‘ Nagy (translator - Hungarian)
				</div></li><li><div class="para">
					Igor NestoroviÄ‡ (translator - Serbian)
				</div></li><li><div class="para">
					<a href="https://fedoraproject.org/wiki/User:ke4qqq"> David Nalley</a> (writer, editor)
				</div></li><li><div class="para">
					John Nguyen (writer)
				</div></li><li><div class="para">
					Manuel Ospina (translator - Spanish)
				</div></li><li><div class="para">
					Janis Ozolins (translator - Latvian)
				</div></li><li><div class="para">
					Ankit Patel (translator - Gujarati)
				</div></li><li><div class="para">
					<a href="http://fedoraproject.org/wiki/User:Dpaulo">Davidson Paulo</a> (translator - Brazilian Portuguese)
				</div></li><li><div class="para">
					Ani Peter (translator - Malayalam)
				</div></li><li><div class="para">
					<a href="https://translate.fedoraproject.org/people/aphukan">Amitakhya Phukan</a> (translator - Assamese)
				</div></li><li><div class="para">
					<a href="https://fedoraproject.org/wiki/User:Perplex">Silvio Pierro</a> (translator - Italian)
				</div></li><li><div class="para">
					Micha Pietsch (translator - German)
				</div></li><li><div class="para">
					JosÃ© Nuno Pires (translator - Portuguese)
				</div></li><li><div class="para">
					Piotr PodgÃ³rski (translator - Polish)
				</div></li><li><div class="para">
					Yulia Poyarkova (translator - Russian)
				</div></li><li><div class="para">
					Shankar Prasad (translator - Kannada)
				</div></li><li><div class="para">
					Rajesh Ranjan (translator - Hindi)
				</div></li><li><div class="para">
					<a href="https://fedoraproject.org/wiki/TommyReynolds"> Tommy Reynolds </a> (writer)
				</div></li><li><div class="para">
					Tim Richert (translator - German)
				</div></li><li><div class="para">
					<a href="http://fedoraproject.org/wiki/DominikSandjaja">Dominik Sandjaja</a> (translator - German)
				</div></li><li><div class="para">
					<a href="http://translate.fedoraproject.org/people/szaman">Sharuzzaman Ahmat Raslan</a> (translator - Malay)
				</div></li><li><div class="para">
					<a href="https://fedoraproject.org/wiki/User:Saeedi">Mohsen Saeedi</a> (translator - Persian)
				</div></li><li><div class="para">
					<a href="https://fedoraproject.org/wiki/User:Tiansworld">Tian Shixiong</a> (translator - Chinese (Simplified))
				</div></li><li><div class="para">
					Audrey Simons (translator - French)
				</div></li><li><div class="para">
					Keld Simonsen (translator - Danish)
				</div></li><li><div class="para">
					<a href="https://fedoraproject.org/wiki/User:Jsmith"> Jared K. Smith</a> (writer, editor)
				</div></li><li><div class="para">
					Espen Stefansen (translator - Norwegian BokmÃ¥l)
				</div></li><li><div class="para">
					<a href="https://fedoraproject.org/wiki/User:Peti"> Sulyok PÃ©ter</a> (translator - Hungarian)
				</div></li><li><div class="para">
					<a href="https://fedoraproject.org/wiki/User:Zoli73"> SÃ¼megi ZoltÃ¡n</a> (translator - Hungarian)
				</div></li><li><div class="para">
					<a href="https://fedoraproject.org/wiki/User:Tombo">Francesco Tombolini</a> (translator - Italian)
				</div></li><li><div class="para">
					Timo Trinks (translator - German)
				</div></li><li><div class="para">
					<a href="http://fedoraproject.org/wiki/DimitriosTypaldos">Dimitris Typaldos</a> (translator - Greek)
				</div></li><li><div class="para">
					GÃ¶ran Uddeborg (translator - Swedish)
				</div></li><li><div class="para">
					<a href="http://fedoraproject.org/wiki/MichaelUghetto">MichaÃ«l Ughetto</a> (translator - French)
				</div></li><li><div class="para">
					Francesco Valente (translator - Italian)
				</div></li><li><div class="para">
					<a href="http://fedoraproject.org/wiki/KarstenWade"> Karsten Wade</a> (writer, editor, publisher)
				</div></li><li><div class="para">
					Sarah Saiying Wang (translator - Chinese (Simplified))
				</div></li><li><div class="para">
					<a href="http://fedoraproject.org/wiki/GeertWarrink">Geert Warrink</a> (translator - Dutch)
				</div></li><li><div class="para">
					Elizabeth Ann West (editor)
				</div></li><li><div class="para">
					Tyronne Wickramarathne (translator - Sinhalese)
				</div></li><li><div class="para">
					Ben Wu (translator - Chinese (Traditional))
				</div></li><li><div class="para">
					Xiaofan Yang (translator - Chinese (Simplified))
				</div></li><li><div class="para">
					<a href="http://translate.fedoraproject.org/people/bbbush">Yuan Yijun</a> (translator - Chinese (Simplified))
				</div></li><li><div class="para">
					<a href="http://fedoraproject.org/wiki/DiegoZacarao">Diego BÃºrigo ZacarÃ£o</a> (translator - Brazilian Portuguese)
				</div></li><li><div class="para">
					<a href="http://fedoraproject.org/wiki/User:Izaac">Izaac Zavaleta</a> (translator - Spanish)
				</div></li></ul></div><div class="para">
			<a href="http://docs.fedoraproject.org/install-guide/">http://docs.fedoraproject.org/install-guide/</a>
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ap-techref.html"><strong>Prev</strong>AppendixÂ G.Â Other Technical Documentation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-Production_methods.html"><strong>Next</strong>H.2.Â Production methods</a></li></ul></body></html>


--- NEW FILE ch-beginninginstallation.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ChapterÂ 6.Â Beginning the Installation</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-The_installation_process.html" title="PartÂ II.Â The installation process" /><link rel="prev" href="pt-The_installation_process.html" title="PartÂ II.Â The installation process" /><link rel="next" href="sn-install-diff-source.html" title="6.2.Â Installing from a Different Source" /></head><body class="draft "><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/im
 ages/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pt-The_installation_process.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-install-diff-source.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="ch-beginninginstallation">ChapterÂ 6.Â Beginning the Installation</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-beginninginstallation.html#sn-boot-menu">6.1. The Boot Menu</a></span></dt><dt><span class="section"><a href="sn-install-diff-source.html">6.2. Installing from a Different Source</a></span></dt><dt><span class="section"><a href="sn-verifying-media.html">6.3. Verifying Media</a></span></dt><dd><dl><dt><span class="section"><a href="sn-verifying-media.html#sn-verifying-livecd">6.3.1. Verifying the Live CD</a></span></dt><dt><span class="section">
 <a href="sn-verifying-dvd.html">6.3.2. Verifying the DVD</a></span></dt></dl></dd><dt><span class="section"><a href="sn-booting-from-pxe.html">6.4. Booting from the Network using PXE</a></span></dt><dt><span class="section"><a href="sn-graphics-problem.html">6.5. Graphical and Text Interfaces</a></span></dt></dl></div><div class="note"><h2>Aborting the Installation</h2><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 class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-boot-menu">6.1.Â The Boot Menu</h2></div></div></div><div class="para">
			The boot media displays a graphical boot menu with several options. If no key is hit within 60 seconds, the default boot option runs. To choose the default, either wait for the timer to run out or hit <span class="keycap"><strong>Enter</strong></span> on the keyboard. To select a different option than the default, use the arrow keys on your keyboard, and hit <span class="keycap"><strong>Enter</strong></span> when the correct option is highlighted. If you want to customize the boot options for a particular option, hit the <span class="keycap"><strong>Tab</strong></span> key.
		</div><div class="note"><h2>Using Boot Options</h2><div class="para">
				For a listing and explanation of common boot options, refer to <a class="xref" href="ap-admin-options.html" title="ChapterÂ 9.Â Boot Options">ChapterÂ 9, <i>Boot Options</i></a>.
			</div></div><div class="para">
			When using Fedora Live media, press any key during the initial boot countdown to bring up the <span class="guilabel"><strong>Boot Options</strong></span> menu. The boot options include:
		</div><div class="itemizedlist"><ul><li><div class="formalpara"><h5 class="formalpara" id="id805274">Boot</h5>
						This option is the default. If you select this option, only the kernel and startup programs load into memory. This option takes less time to load. As you use programs, they are loaded from the disc, which takes more time. This mode can be used on machines with less total memory.
					</div></li><li><div class="formalpara"><h5 class="formalpara" id="id809910">Verify and Boot</h5>
						This option lets you verify the disc before you run the Live CD environment. Refer to <a class="xref" href="sn-verifying-media.html" title="6.3.Â Verifying Media">SectionÂ 6.3, â€œVerifying Mediaâ€</a> for more information on the verification process.
					</div></li><li><div class="formalpara"><h5 class="formalpara" id="id872977">Memory Test</h5>
						This option runs an exhaustive test on the memory on your system. For more information, refer to <a class="xref" href="sn-boot-modes.html#sn-memtest" title="9.6.1.Â Loading the Memory (RAM) Testing Mode">SectionÂ 9.6.1, â€œLoading the Memory (RAM) Testing Modeâ€</a>.
					</div></li><li><div class="formalpara"><h5 class="formalpara" id="id789619">Boot from local drive</h5>
						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></li></ul></div><div class="para">
			If you boot the DVD, rescue CD, or minimal boot media, the boot menu options include:
		</div><div class="itemizedlist"><ul><li><div class="formalpara"><h5 class="formalpara" id="id789644">Install or upgrade an existing system</h5>
						This option is the default. Choose this option to install Fedora onto your computer system using the graphical installation program.
					</div></li><li><div class="formalpara"><h5 class="formalpara" id="id789660">Install system with basic video driver</h5>
						This option allows you to install Fedora in graphical mode even if the installation program is unable to load the correct driver for your video card. If your screen appears distorted or goes blank when using the the <span class="guilabel"><strong>Install or upgrade an existing system</strong></span> option, restart your computer and try this option instead.
					</div></li><li><div class="formalpara"><h5 class="formalpara" id="id852761">Rescue installed system</h5>
						Choose this option to repair a problem with your installed Fedora system that prevents you from booting normally. Although Fedora is an exceptionally stable computing platform, it is still possible for occasional problems to occur that prevent booting. The rescue environment contains utility programs that allow you fix a wide variety of these problems.
					</div></li><li><div class="formalpara"><h5 class="formalpara" id="id852779">Boot from local drive</h5>
						(as for Live CD)
					</div></li><li><div class="formalpara"><h5 class="formalpara" id="id852794">Memory Test</h5>
						(as for Live CD)
					</div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pt-The_installation_process.html"><strong>Prev</strong>PartÂ II.Â The installation process</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-install-diff-source.html"><strong>Next</strong>6.2.Â Installing from a Different Source</a></li></ul></body></html>


--- NEW FILE ch-boot-init-shutdown.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>AppendixÂ F.Â Boot Process, Init, and Shutdown</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-Technical_appendixes.html" title="PartÂ V.Â Technical appendixes" /><link rel="prev" href="s2-grub-related-books.html" title="E.8.3.Â Related Books" /><link rel="next" href="s1-boot-init-shutdown-process.html" title="F.2.Â A Detailed Look at the Boot Process" /></head><body class="draft "><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_rig
 ht.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-grub-related-books.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-boot-init-shutdown-process.html"><strong>Next</strong></a></li></ul><div class="appendix" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h1 id="ch-boot-init-shutdown" class="title">Boot Process, Init, and Shutdown</h1></div></div></div><a id="id865773" class="indexterm"></a><div class="para">
		An important and powerful aspect of Fedora is the open, user-configurable method it uses for starting the operating system. Users are free to configure many aspects of the boot process, including specifying the programs launched at boot-time. Similarly, system shutdown gracefully terminates processes in an organized and configurable way, although customization of this process is rarely required.
	</div><div class="para">
		Understanding how the boot and shutdown processes work not only allows customization, but also makes it easier to troubleshoot problems related to starting or shutting down the system.
	</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-boot-process-basics">F.1.Â The Boot Process</h2></div></div></div><a id="id839906" class="indexterm"></a><div class="para">
			Below are the basic stages of the boot process for an x86 system:
		</div><div class="orderedlist"><ol><li><div class="para">
					The system BIOS checks the system and launches the first stage boot loader on the MBR of the primary hard disk.
				</div></li><li><div class="para">
					The first stage boot loader loads itself into memory and launches the second stage boot loader from the <code class="filename">/boot/</code> partition.
				</div></li><li><div class="para">
					The second stage boot loader loads the kernel into memory, which in turn loads any necessary modules and mounts the root partition read-only.
				</div></li><li><div class="para">
					The kernel transfers control of the boot process to the <code class="command">/sbin/init</code> program.
				</div></li><li><div class="para">
					The <code class="command">/sbin/init</code> program loads all services and user-space tools, and mounts all partitions listed in <code class="filename">/etc/fstab</code>.
				</div></li><li><div class="para">
					The user is presented with a login screen for the freshly booted Linux system.
				</div></li></ol></div><div class="para">
			Because configuration of the boot process is more common than the customization of the shutdown process, the remainder of this chapter discusses in detail how the boot process works and how it can be customized to suite specific needs.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-grub-related-books.html"><strong>Prev</strong>E.8.3.Â Related Books</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-boot-init-shutdown-process.html"><strong>Next</strong>F.2.Â A Detailed Look at the Boot Process</a></li></ul></body></html>


--- NEW FILE ch-driverdisk-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ChapterÂ 5.Â Driver Media for Intel and AMD Systems</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-Before_you_begin.html" title="PartÂ I.Â Before you begin" /><link rel="prev" href="ch-ent-table.html" title="ChapterÂ 4.Â System Specifications List" /><link rel="next" href="ch05s02.html" title="5.2.Â So What Is Driver Media Anyway?" /></head><body class="draft "><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="Documen
 tation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-ent-table.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch05s02.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="ch-driverdisk-x86">ChapterÂ 5.Â Driver Media for <span class="trademark">Intel</span>Â® and AMD Systems</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-driverdisk-x86.html#id808556">5.1. Why Do I Need Driver Media?</a></span></dt><dt><span class="section"><a href="ch05s02.html">5.2. So What Is Driver Media Anyway?</a></span></dt><dt><span class="section"><a href="ch05s03.html">5.3. How Do I Obtain Driver Media?</a></span></dt><dd><dl><dt><span class="section"><a href="ch05s03.html#id806929">5.3.1. Creating a Driver Diskette from an Image File</a></span></dt></dl></dd><dt><span class="section"><a href="ch05s04.html">5.4
 . Using a Driver Image During Installation</a></span></dt></dl></div><a id="id816079" class="indexterm"></a><a id="id801400" class="indexterm"></a><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="id808556">5.1.Â Why Do I Need Driver Media?</h2></div></div></div><div class="para">
	While the Fedora installation program is loading, a screen may appear asking you for driver media. The driver media screen is most often seen in the following scenarios:
</div><div class="itemizedlist"><ul><li><div class="para">
					There is no driver available for a piece of hardware that is necessary for installation to proceed.
				</div></li><li><div class="para">
					If you run the installation program by entering <strong class="userinput"><code>linux dd</code></strong> at the installation boot prompt. 
				</div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-ent-table.html"><strong>Prev</strong>ChapterÂ 4.Â System Specifications List</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch05s02.html"><strong>Next</strong>5.2.Â So What Is Driver Media Anyway?</a></li></ul></body></html>


--- NEW FILE ch-ent-table.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ChapterÂ 4.Â System Specifications List</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-Before_you_begin.html" title="PartÂ I.Â Before you begin" /><link rel="prev" href="ch03s06.html" title="3.6.Â Preparing for a Hard Drive Installation" /><link rel="next" href="ch-driverdisk-x86.html" title="ChapterÂ 5.Â Driver Media for Intel and AMD Systems" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s06.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-driverdisk-x86.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="ch-ent-table">ChapterÂ 4.Â System Specifications List</h2></div></div></div><a id="id792187" class="indexterm"></a><a id="id811330" 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.html" title="3.2.Â Is Your Hardware Compatible?">SectionÂ 3.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.
	</div><div class="itemizedlist"><ul><li><div class="para">
				If you plan to use a customized partition layout, record:
			</div><div class="itemizedlist"><ul><li><div class="para">
						The model numbers, sizes, types, and interfaces of the hard drives attached to the system. For example, Seagate ST3320613AS 320 GB on SATA0, Western Digital WD7500AAKS 750 GB on SATA1. This will allow you to identify specific hard drives during the partitioning process.
					</div></li></ul></div></li><li><div class="para">
				If you are installing Fedora as an additional operating system on an existing system, record:
			</div><div class="itemizedlist"><ul><li><div class="para">
						The mount points of the existing partitions on the system. For example, <code class="filename">/boot</code> on <code class="filename">sda1</code>, <code class="filename">/</code> on <code class="filename">sda2</code>, and <code class="filename">/home</code> on <code class="filename">sdb1</code>. This will allow you to identify specific partitions during the partitioning process.
					</div></li></ul></div></li><li><div class="para">
				If you plan to install from an image on a local hard drive:
			</div><div class="itemizedlist"><ul><li><div class="para">
						The hard drive and directory that holds the image â€“ see <a class="xref" href="s1-begininstall-hd-x86.html#table-Location_of_ISO_images" title="TableÂ 7.2.Â Location of ISO images for different partition types">TableÂ 7.2, â€œLocation of ISO images for different partition typesâ€</a> for examples.
					</div></li></ul></div></li><li><div class="para">
				If you plan to install from a network location, or install on an iSCSI target:
			</div><div class="itemizedlist"><ul><li><div class="para">
						The make and model numbers of the network adapters on your system. For example, Netgear GA311. This will allow you to identify adapters when manually configuring the network.
					</div></li><li><div class="para">
						IP, DHCP, and BOOTP addresses
					</div></li><li><div class="para">
						Netmask
					</div></li><li><div class="para">
						Gateway IP address
					</div></li><li><div class="para">
						One or more name server IP addresses (DNS)
					</div></li></ul></div><div class="para">
				If any of these networking requirements or terms are unfamiliar to you, contact your network administrator for assistance.
			</div></li><li><div class="para">
				If you plan to install from a network location:
			</div><div class="itemizedlist"><ul><li><div class="para">
						The location of the image on an FTP server, HTTP (web) server, or NFS server â€“ see <a class="xref" href="s1-begininstall-url-x86.html" title="7.9.Â Installing via FTP or HTTP">SectionÂ 7.9, â€œInstalling via FTP or HTTPâ€</a> and <a class="xref" href="s1-begininstall-nfs-x86.html" title="7.8.Â Installing via NFS">SectionÂ 7.8, â€œInstalling via NFSâ€</a> for examples.
					</div></li></ul></div></li><li><div class="para">
				If you plan to install on an iSCSI target:
			</div><div class="itemizedlist"><ul><li><div class="para">
						The location of the iSCSI target. Depending on your network, you might also need a CHAP username and password, and perhaps a reverse CHAP username and password â€“ see <a class="xref" href="s1-advanced-storage-x86.html" title="7.19.Â  Advanced Storage Options">SectionÂ 7.19, â€œ Advanced Storage Options â€</a>.
					</div></li></ul></div></li><li><div class="para">
				If your computer is part of a domain:
			</div><div class="itemizedlist"><ul><li><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s06.html"><strong>Prev</strong>3.6.Â Preparing for a Hard Drive Installation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-driverdisk-x86.html"><strong>Next</strong>ChapterÂ 5.Â Driver Media for Intel and AMD Systems</a></li></ul></body></html>


--- NEW FILE ch-experts-quickstart.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ChapterÂ 1.Â Quick Start for Experts</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="index.html" title="Installation Guide" /><link rel="prev" href="sn-audience.html" title="2.2.Â Audience" /><link rel="next" href="sn-expert-download.html" title="1.2.Â Download Files" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a acc
 esskey="p" href="sn-audience.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-expert-download.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="ch-experts-quickstart">ChapterÂ 1.Â Quick Start for Experts</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-experts-quickstart.html#sn-expert-overview">1.1. Overview</a></span></dt><dt><span class="section"><a href="sn-expert-download.html">1.2. Download Files</a></span></dt><dt><span class="section"><a href="sn-expert-prepare.html">1.3. Prepare for Installation</a></span></dt><dt><span class="section"><a href="sn-expert-install.html">1.4. Install Fedora</a></span></dt><dt><span class="section"><a href="sn-expert-post-install.html">1.5. Perform Post-installation Steps</a></span></dt></dl></div><div class="para">
		This section offers a very brief overview of installation tasks for experienced readers who are eager to get started. Note that many explanatory notes and helpful hints appear in the following chapters of this guide. If an issue arises during the installation process, consult the appropriate chapters in the full guide for help.
	</div><div class="warning"><h2>Experts Only</h2><div class="para">
			This section is intended only for experts. Other readers may not be familiar with some of the terms in this section, and should move on to <a class="xref" href="ch-new-users.html" title="ChapterÂ 2.Â New Users">ChapterÂ 2, <i>New Users</i></a> instead.
		</div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-expert-overview">1.1.Â Overview</h2></div></div></div><div class="para">
			The installation procedure is fairly simple, and consists of only a few steps:
		</div><div class="orderedlist"><ol><li><div class="para">
					Download files to make media or another bootable configuration.
				</div></li><li><div class="para">
					Prepare system for installation.
				</div></li><li><div class="para">
					Boot the computer and run the installation process.
				</div></li><li><div class="para">
					Reboot and perform post-installation configuration.
				</div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-audience.html"><strong>Prev</strong>2.2.Â Audience</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-expert-download.html"><strong>Next</strong>1.2.Â Download Files</a></li></ul></body></html>


--- NEW FILE ch-firstboot.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ChapterÂ 15.Â Firstboot</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-After_installation.html" title="PartÂ IV.Â After installation" /><link rel="prev" href="pt-After_installation.html" title="PartÂ IV.Â After installation" /><link rel="next" href="sn-firstboot-systemuser.html" title="15.2.Â System User" /></head><body class="draft "><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><ul 
 class="docnav"><li class="previous"><a accesskey="p" href="pt-After_installation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-firstboot-systemuser.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="ch-firstboot">ChapterÂ 15.Â Firstboot</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-firstboot.html#sn-firstboot-license">15.1. License Agreement</a></span></dt><dt><span class="section"><a href="sn-firstboot-systemuser.html">15.2. System User</a></span></dt><dt><span class="section"><a href="sn-firstboot-datetime.html">15.3. Date and Time</a></span></dt><dt><span class="section"><a href="sn-smolt.html">15.4. Hardware Profile</a></span></dt></dl></div><a id="id804752" class="indexterm"></a><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.
	</div><div class="figure" id="id846323"><div class="figure-contents"><div class="mediaobject"><img src="images/firstboot/fb-welcome.png" alt="Firstboot welcome screen" /><div class="longdesc"><div class="para">
					Firstboot welcome screen
				</div></div></div></div><h6>FigureÂ 15.1.Â Firstboot welcome screen</h6></div><br class="figure-break" /><div class="para">
		Select <span class="guibutton"><strong>Forward</strong></span> to start the <span class="application"><strong>Firstboot</strong></span>.
	</div><div class="note"><h2>Graphical Interface Required</h2><div class="para">
			<span class="application"><strong>Firstboot</strong></span> requires a graphical interface. If you did not install one, or if Fedora has trouble starting it, you may see a slightly different setup screen.
		</div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-firstboot-license">15.1.Â License Agreement</h2></div></div></div><div class="para">
			This screen displays the overall licensing terms for Fedora. Each software package in Fedora is covered by its own license. All licensing guidelines for Fedora are located at <a href="http://fedoraproject.org/wiki/Legal/Licenses">http://fedoraproject.org/wiki/Legal/Licenses</a>.
		</div><div class="figure" id="id785126"><div class="figure-contents"><div class="mediaobject"><img src="images/firstboot/fb-license.png" alt="Firstboot license screen" /><div class="longdesc"><div class="para">
						Firstboot license screen
					</div></div></div></div><h6>FigureÂ 15.2.Â Firstboot license screen</h6></div><br class="figure-break" /><div class="para">
			If you agree to the terms of the licence, select <span class="guibutton"><strong>Forward</strong></span>.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pt-After_installation.html"><strong>Prev</strong>PartÂ IV.Â After installation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-firstboot-systemuser.html"><strong>Next</strong>15.2.Â System User</a></li></ul></body></html>


--- NEW FILE ch-grub.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>AppendixÂ E.Â The GRUB Boot Loader</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-Technical_appendixes.html" title="PartÂ V.Â Technical appendixes" /><link rel="prev" href="sn-partitioning-lvm.html" title="AppendixÂ D.Â Understanding LVM" /><link rel="next" href="s1-grub-installing.html" title="E.2.Â Installing GRUB" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-partitioning-lvm.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-grub-installing.html"><strong>Next</strong></a></li></ul><div class="appendix" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h1 id="ch-grub" class="title">The GRUB Boot Loader</h1></div></div></div><a id="id852343" class="indexterm"></a><div class="para">
		When a computer running Linux is turned on, the operating system is loaded into memory by a special program called a <em class="firstterm">boot loader</em>. A boot loader usually exists on the system's primary hard drive (or other media device) and has the sole responsibility of loading the Linux kernel with its required files or (in some cases) other operating systems into memory.
	</div><div class="para">
		This appendix discusses commands and configuration options for the GRUB boot loader included with Fedora for the x86 architecture.
	</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-grub-whatis">E.1.Â GRUB</h2></div></div></div><a id="id905838" class="indexterm"></a><a id="id819776" class="indexterm"></a><div class="para">
			The <em class="firstterm">GNU GRand Unified Boot loader</em> (GRUB) is a program which enables the selection of the installed operating system or kernel to be loaded at system boot time. It also allows the user to pass arguments to the kernel.
		</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-grub-whatis-booting">E.1.1.Â GRUB and the x86 Boot Process</h3></div></div></div><a id="id796770" class="indexterm"></a><a id="id863296" class="indexterm"></a><a id="id885168" class="indexterm"></a><div class="para">
				This section discusses the specific role GRUB plays when booting an x86 system. For a look at the overall boot process, refer to <a class="xref" href="s1-boot-init-shutdown-process.html" title="F.2.Â A Detailed Look at the Boot Process">SectionÂ F.2, â€œA Detailed Look at the Boot Processâ€</a>.
			</div><div class="para">
				GRUB loads itself into memory in the following stages:
			</div><div class="orderedlist"><ol><li><div class="para">
						<span class="emphasis"><em>The Stage 1 or primary boot loader is read into memory by the BIOS from the MBR <sup>[<a id="id873688" href="#ftn.id873688" class="footnote">6</a>]</sup>.</em></span> The primary boot loader exists on less than 512 bytes of disk space within the MBR and is capable of loading either the Stage 1.5 or Stage 2 boot loader.
					</div></li><li><div class="para">
						<span class="emphasis"><em>The Stage 1.5 boot loader is read into memory by the Stage 1 boot loader, if necessary.</em></span> Some hardware requires an intermediate step to get to the Stage 2 boot loader. This is sometimes true when the <code class="filename">/boot/</code> partition is above the 1024 cylinder head of the hard drive or when using LBA mode. The Stage 1.5 boot loader is found either on the <code class="filename">/boot/</code> partition or on a small part of the MBR and the <code class="filename">/boot/</code> partition.
					</div></li><li><div class="para">
						<span class="emphasis"><em>The Stage 2 or secondary boot loader is read into memory.</em></span> The secondary boot loader displays the GRUB menu and command environment. This interface allows the user to select which kernel or operating system to boot, pass arguments to the kernel, or look at system parameters.
					</div></li><li><div class="para">
						<span class="emphasis"><em>The secondary boot loader reads the operating system or kernel as well as the contents of <code class="filename">/boot/sysroot/</code> into memory.</em></span> Once GRUB determines which operating system or kernel to start, it loads it into memory and transfers control of the machine to that operating system.
					</div></li></ol></div><div class="para">
				The method used to boot Linux is called <em class="firstterm">direct loading</em> because the boot loader loads the operating system directly. There is no intermediary between the boot loader and the kernel.
			</div><div class="para">
				The boot process used by other operating systems may differ. For example, the <span class="trademark">Microsoft</span>Â® <span class="trademark">Windows</span>Â® operating system, as well as other operating systems, are loaded using <em class="firstterm">chain loading</em>. Under this method, the MBR points to the first sector of the partition holding the operating system, where it finds the files necessary to actually boot that operating system.
			</div><div class="para">
				GRUB supports both direct and chain loading boot methods, allowing it to boot almost any operating system.
			</div><div class="warning"><h2>Warning</h2><div class="para">
					During installation, Microsoft's DOS and Windows installation programs completely overwrite the MBR, destroying any existing boot loaders. If creating a dual-boot system, it is best to install the Microsoft operating system first.
				</div></div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-grub-whatis-features">E.1.2.Â Features of GRUB</h3></div></div></div><a id="id933823" class="indexterm"></a><div class="para">
				GRUB contains several features that make it preferable to other boot loaders available for the x86 architecture. Below is a partial list of some of the more important features:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<span class="emphasis"><em>GRUB provides a true command-based, pre-OS environment on x86 machines.</em></span> This feature affords the user maximum flexibility in loading operating systems with specified options or gathering information about the system. For years, many non-x86 architectures have employed pre-OS environments that allow system booting from a command line.
					</div></li><li><div class="para">
						<span class="emphasis"><em>GRUB supports <em class="firstterm">Logical Block Addressing (LBA)</em> mode.</em></span> LBA places the addressing conversion used to find files in the hard drive's firmware, and is used on many IDE and all SCSI hard devices. Before LBA, boot loaders could encounter the 1024-cylinder BIOS limitation, where the BIOS could not find a file after the 1024 cylinder head of the disk. LBA support allows GRUB to boot operating systems from partitions beyond the 1024-cylinder limit, so long as the system BIOS supports LBA mode. Most modern BIOS revisions support LBA mode.
					</div></li><li><div class="para">
						<span class="emphasis"><em>GRUB can read ext2 partitions.</em></span> This functionality allows GRUB to access its configuration file, <code class="filename">/boot/grub/grub.conf</code>, every time the system boots, eliminating the need for the user to write a new version of the first stage boot loader to the MBR when configuration changes are made. The only time a user needs to reinstall GRUB on the MBR is if the physical location of the <code class="filename">/boot/</code> partition is moved on the disk. For details on installing GRUB to the MBR, refer to <a class="xref" href="s1-grub-installing.html" title="E.2.Â Installing GRUB">SectionÂ E.2, â€œInstalling GRUBâ€</a>.
					</div></li></ul></div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id873688" href="#id873688" class="para">6</a>] </sup>
							For more on the system BIOS and the MBR, refer to <a class="xref" href="s1-boot-init-shutdown-process.html#s2-boot-init-shutdown-bios" title="F.2.1.Â The BIOS">SectionÂ F.2.1, â€œThe BIOSâ€</a>.
						</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-partitioning-lvm.html"><strong>Prev</strong>AppendixÂ D.Â Understanding LVM</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-grub-installing.html"><strong>Next</strong>E.2.Â Installing GRUB</a></li></ul></body></html>


--- NEW FILE ch-guimode-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ChapterÂ 7.Â Installing on Intel and AMD Systems</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-The_installation_process.html" title="PartÂ II.Â The installation process" /><link rel="prev" href="sn-graphics-problem.html" title="6.5.Â Graphical and Text Interfaces" /><link rel="next" href="s1-guimode-textinterface-x86.html" title="7.2.Â The Text Mode Installation Program User Interface" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-graphics-problem.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-guimode-textinterface-x86.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="ch-guimode-x86">ChapterÂ 7.Â Installing on <span class="trademark">Intel</span>Â® and AMD Systems</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-guimode-x86.html#s1-guimode-interface-x86">7.1. The Graphical Installation Program User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="ch-guimode-x86.html#sn-guimode-virtual-consoles-x86">7.1.1. A Note about Virtual Consoles</a></span></dt></dl></dd><dt><span class="section"><a href="s1-guimode-textinterface-x86.html">7.2. The Text Mode Installation Program User Interface<
 /a></span></dt><dd><dl><dt><span class="section"><a href="s1-guimode-textinterface-x86.html#id834187">7.2.1. Using the Keyboard to Navigate</a></span></dt></dl></dd><dt><span class="section"><a href="s1-x86-starting.html">7.3. Starting the Installation Program</a></span></dt><dd><dl><dt><span class="section"><a href="s1-x86-starting.html#s2-x86-starting-booting">7.3.1. Booting the Installation Program on x86, AMD64, and Intel 64 Systems</a></span></dt><dt><span class="section"><a href="s2-x86-starting-bootopts.html">7.3.2. Additional Boot Options</a></span></dt></dl></dd><dt><span class="section"><a href="s1-installmethod.html">7.4. Selecting an Installation Method</a></span></dt><dt><span class="section"><a href="s1-begininstall-cd-inst-x86.html">7.5. Installing from DVD/CD-ROM</a></span></dt><dd><dl><dt><span class="section"><a href="s1-begininstall-cd-inst-x86.html#s2-begininstall-unrec-ide-x86">7.5.1. What If the IDE CD-ROM Was Not Found?</a></span></dt></dl></dd><dt><sp
 an class="section"><a href="s1-begininstall-hd-x86.html">7.6. Installing from a Hard Drive</a></span></dt><dt><span class="section"><a href="s1-begininstall-perform-nfs-x86.html">7.7. Performing a Network Installation</a></span></dt><dt><span class="section"><a href="s1-begininstall-nfs-x86.html">7.8. Installing via NFS</a></span></dt><dt><span class="section"><a href="s1-begininstall-url-x86.html">7.9. Installing via FTP or HTTP</a></span></dt><dt><span class="section"><a href="sn-welcome-x86.html">7.10. Welcome to Fedora</a></span></dt><dt><span class="section"><a href="s1-langselection-x86.html">7.11. Language Selection</a></span></dt><dt><span class="section"><a href="ch07s12.html">7.12. Keyboard Configuration</a></span></dt><dt><span class="section"><a href="sn-initialize-hdd.html">7.13. Initializing the Hard Disk</a></span></dt><dt><span class="section"><a href="sn-upgrading-system.html">7.14. Upgrading an Existing System</a></span></dt><dd><dl><dt><span class="section
 "><a href="sn-upgrading-system.html#sn-upgrade-examine">7.14.1. Upgrade Examine</a></span></dt><dt><span class="section"><a href="sn-upgrade-tree.html">7.14.2. Upgrading Using the Installer</a></span></dt><dt><span class="section"><a href="sn-upgrading-bootloader.html">7.14.3. Upgrading Boot Loader Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="sn-networkconfig-fedora.html">7.15. Network Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="sn-networkconfig-fedora.html#sn-networkconfig-fedora_manual-configuration">7.15.1. Manual configuration</a></span></dt></dl></dd><dt><span class="section"><a href="s1-timezone-x86.html">7.16. Time Zone Configuration</a></span></dt><dt><span class="section"><a href="sn-account_configuration.html">7.17. Set the Root Password</a></span></dt><dt><span class="section"><a href="s1-diskpartsetup-x86.html">7.18. Disk Partitioning Setup</a></span></dt><dd><dl><dt><span class="section"><a href="s1-diskpa
 rtsetup-x86.html#sn-partitioning-raid">7.18.1. RAID and Other Disk Devices</a></span></dt></dl></dd><dt><span class="section"><a href="s1-advanced-storage-x86.html">7.19.  Advanced Storage Options </a></span></dt><dt><span class="section"><a href="s1-diskpartauto-x86.html">7.20. Create Default Layout</a></span></dt><dt><span class="section"><a href="s1-diskpartitioning-x86.html">7.21. Partitioning Your System</a></span></dt><dd><dl><dt><span class="section"><a href="s1-diskpartitioning-x86.html#id888157">7.21.1. Graphical Display of Hard Drive(s)</a></span></dt><dt><span class="section"><a href="s2-diskpartitioning-dd-x86.html">7.21.2. The partitioning screen</a></span></dt><dt><span class="section"><a href="ch07s21s03.html">7.21.3. Partition Fields</a></span></dt><dt><span class="section"><a href="s2-diskpartrecommend-x86.html">7.21.4. Recommended Partitioning Scheme</a></span></dt><dt><span class="section"><a href="ch07s21s05.html">7.21.5. Adding Partitions</a></span></dt>
 <dt><span class="section"><a href="ch07s21s06.html">7.21.6. Editing Partitions</a></span></dt><dt><span class="section"><a href="s2-diskpartdelete-x86.html">7.21.7. Deleting a Partition</a></span></dt></dl></dd><dt><span class="section"><a href="s1-x86-bootloader.html">7.22. x86, AMD64, and Intel 64 Boot Loader Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="s1-x86-bootloader.html#x86-bootloader-adv">7.22.1. Advanced Boot Loader Configuration</a></span></dt><dt><span class="section"><a href="s2-x86-bootloader-rescue.html">7.22.2. Rescue Mode</a></span></dt><dt><span class="section"><a href="s2-x86-bootloader-alt.html">7.22.3. Alternative Boot Loaders</a></span></dt></dl></dd><dt><span class="section"><a href="s1-pkgselection-x86.html">7.23. Package Group Selection</a></span></dt><dd><dl><dt><span class="section"><a href="s1-pkgselection-x86.html#sn-additional-repos">7.23.1. Installing from Additional Repositories</a></span></dt><dt><span class="sectio
 n"><a href="sn-package-selection.html">7.23.2. Customizing the Software Selection</a></span></dt></dl></dd><dt><span class="section"><a href="s1-preparetoinstall-x86.html">7.24. Preparing to Install</a></span></dt><dd><dl><dt><span class="section"><a href="s1-preparetoinstall-x86.html#id838976">7.24.1.  Prepare to Install </a></span></dt></dl></dd><dt><span class="section"><a href="s1-installpkgs-x86.html">7.25. Installing Packages</a></span></dt><dt><span class="section"><a href="s1-complete-x86.html">7.26. Installation Complete</a></span></dt></dl></div><a id="id822612" class="indexterm"></a><div class="para">
	This chapter explains how to perform a Fedora installation from the DVD/CD-ROM, using the graphical, mouse-based installation program. The following topics are discussed:
</div><div class="itemizedlist"><ul><li><div class="para">
			Becoming familiar with the installation program's user interface
		</div></li><li><div class="para">
			Starting the installation program
		</div></li><li><div class="para">
			Selecting an installation method
		</div></li><li><div class="para">
			Configuration steps during the installation (language, keyboard, mouse, partitioning, etc.)
		</div></li><li><div class="para">
			Finishing the installation
		</div></li></ul></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-guimode-interface-x86">7.1.Â The Graphical Installation Program User Interface</h2></div></div></div><a id="id847128" class="indexterm"></a><a id="id914298" class="indexterm"></a><div class="para">
	If you have used a <em class="firstterm">graphical user interface (GUI)</em> before, you are already familiar with this process; use your mouse to navigate the screens, click buttons, or enter text fields.
</div><div class="para">
	You can also navigate through the installation using the keyboard. The <span class="keycap"><strong>Tab</strong></span> key allows you to move around the screen, the Up and Down arrow keys to scroll through lists, <span class="keycap"><strong>+</strong></span> and <span class="keycap"><strong>-</strong></span> keys expand and collapse lists, while <span class="keycap"><strong>Space</strong></span> and <span class="keycap"><strong>Enter</strong></span> selects or removes from selection a highlighted item. You can also use the <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong><em class="replaceable"><code>X</code></em></strong></span> key command combination as a way of clicking on buttons or making other screen selections, where <span class="keycap"><strong><em class="replaceable"><code>X</code></em></strong></span> is replaced with any underlined letter appearing within that screen.
</div><div class="note"><h2>Note</h2><div class="para">
		If you are using an x86, AMD64, or <span class="trademark">Intel</span>Â® 64 system, and you do not wish to use the GUI installation program, the text mode installation program is also available. To start the text mode installation program, press the <span class="keycap"><strong>Esc</strong></span> key while the Fedora boot menu is displayed, then use the following command at the <code class="prompt">boot:</code> prompt:
	</div><pre class="screen">
<strong class="userinput"><code>linux text</code></strong>
</pre><div class="para">
		Refer to <a class="xref" href="ch-beginninginstallation.html#sn-boot-menu" title="6.1.Â The Boot Menu">SectionÂ 6.1, â€œThe Boot Menuâ€</a> for a description of the Fedora boot menu and to <a class="xref" href="s1-guimode-textinterface-x86.html" title="7.2.Â The Text Mode Installation Program User Interface">SectionÂ 7.2, â€œThe Text Mode Installation Program User Interfaceâ€</a> for a brief overview of text mode installation instructions.
	</div><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 class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-guimode-virtual-consoles-x86">7.1.1.Â A Note about Virtual Consoles</h3></div></div></div><a id="id868105" class="indexterm"></a><a id="id839897" class="indexterm"></a><a id="id851212" 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.
</div><div class="para">
	These virtual consoles can be helpful if you encounter a problem while installing Fedora. Messages displayed on the installation or system consoles can help pinpoint a problem. Refer to <a class="xref" href="ch-guimode-x86.html#tb-guimode-console-x86" title="TableÂ 7.1.Â Console, Keystrokes, and Contents">TableÂ 7.1, â€œConsole, Keystrokes, and Contentsâ€</a> for a listing of the virtual consoles, keystrokes used to switch to them, and their contents.
</div><div class="para">
	Generally, there is no reason to leave the default console (virtual console #6) for graphical installations unless you are attempting to diagnose installation problems.
</div><div class="table" id="tb-guimode-console-x86"><div class="table-contents"><table summary="Console, Keystrokes, and Contents" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>
								console
							</th><th>
								keystrokes
							</th><th>
								contents
							</th></tr></thead><tbody><tr><td>
								1
							</td><td>
								<span class="keycap"><strong>ctrl</strong></span>+<span class="keycap"><strong>alt</strong></span>+<span class="keycap"><strong>f1</strong></span>
							</td><td>
								installation dialog
							</td></tr><tr><td>
								2
							</td><td>
								<span class="keycap"><strong>ctrl</strong></span>+<span class="keycap"><strong>alt</strong></span>+<span class="keycap"><strong>f2</strong></span>
							</td><td>
								shell prompt
							</td></tr><tr><td>
								3
							</td><td>
								<span class="keycap"><strong>ctrl</strong></span>+<span class="keycap"><strong>alt</strong></span>+<span class="keycap"><strong>f3</strong></span>
							</td><td>
								install log (messages from installation program)
							</td></tr><tr><td>
								4
							</td><td>
								<span class="keycap"><strong>ctrl</strong></span>+<span class="keycap"><strong>alt</strong></span>+<span class="keycap"><strong>f4</strong></span>
							</td><td>
								system-related messages
							</td></tr><tr><td>
								5
							</td><td>
								<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><tr><td>
								6
							</td><td>
								<span class="keycap"><strong>ctrl</strong></span>+<span class="keycap"><strong>alt</strong></span>+<span class="keycap"><strong>f6</strong></span>
							</td><td>
								graphical display
							</td></tr></tbody></table></div><h6>TableÂ 7.1.Â Console, Keystrokes, and Contents</h6></div><br class="table-break" /></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-graphics-problem.html"><strong>Prev</strong>6.5.Â Graphical and Text Interfaces</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-guimode-textinterface-x86.html"><strong>Next</strong>7.2.Â The Text Mode Installation Program User Inte...</a></li></ul></body></html>


--- NEW FILE ch-introduction.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Introduction</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="index.html" title="Installation Guide" /><link rel="prev" href="pr01s02.html" title="2.Â We Need Feedback!" /><link rel="next" href="sn-about-document.html" title="2.Â About This Document" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="pr
 01s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-about-document.html"><strong>Next</strong></a></li></ul><div class="preface" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h1 id="ch-introduction" 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.
	</div><div class="para">
		This document does not detail all of the features of the installation system.
	</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-background">1.Â Background</h2></div></div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-about-fedora">1.1.Â About Fedora</h3></div></div></div><div class="para">
				To find out more about Fedora, refer to <a href="http://fedoraproject.org/">http://fedoraproject.org/</a>. To read other documentation on Fedora related topics, refer to <a href="http://docs.fedoraproject.org/">http://docs.fedoraproject.org/</a>.
			</div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-additional-help">1.2.Â Getting Additional Help</h3></div></div></div><div class="para">
				For information on additional help resources for Fedora, visit <a href="http://fedoraproject.org/wiki/Communicate">http://fedoraproject.org/wiki/Communicate</a>.
			</div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s02.html"><strong>Prev</strong>2.Â We Need Feedback!</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-about-document.html"><strong>Next</strong>2.Â About This Document</a></li></ul></body></html>


--- NEW FILE ch-kickstart2.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ChapterÂ 13.Â Kickstart Installations</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-Advanced_installation_options.html" title="PartÂ III.Â Advanced installation options" /><link rel="prev" href="VNC_Whitepaper-references.html" title="12.4.Â References" /><link rel="next" href="s1-kickstart2-howuse.html" title="13.2.Â How Do You Perform a Kickstart Installation?" /></head><body class="draft "><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/imag
 es/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="VNC_Whitepaper-references.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-kickstart2-howuse.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="ch-kickstart2">ChapterÂ 13.Â Kickstart Installations</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-kickstart2.html#s1-kickstart2-whatis">13.1. What are Kickstart Installations?</a></span></dt><dt><span class="section"><a href="s1-kickstart2-howuse.html">13.2. How Do You Perform a Kickstart Installation?</a></span></dt><dt><span class="section"><a href="s1-kickstart2-file.html">13.3. Creating the Kickstart File</a></span></dt><dt><span class="section"><a href="s1-kickstart2-options.html">13.4. Kickstart Options</a></span></dt><dd><dl><dt><span class="section"><
 a href="s1-kickstart2-options.html#s2-kickstart2-options-part-examples">13.4.1. Advanced Partitioning Example</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kickstart2-packageselection.html">13.5. Package Selection</a></span></dt><dt><span class="section"><a href="s1-kickstart2-preinstallconfig.html">13.6. Pre-installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kickstart2-preinstallconfig.html#s2-kickstart2-prescript-example">13.6.1. Example</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kickstart2-postinstallconfig.html">13.7. Post-installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kickstart2-postinstallconfig.html#s2-kickstart2-post-examples">13.7.1. Examples</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kickstart2-putkickstarthere.html">13.8. Making the Kickstart File Available</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kickstart2-putkickstarthere.
 html#s2-kickstart2-boot-media">13.8.1. Creating Kickstart Boot Media</a></span></dt><dt><span class="section"><a href="s2-kickstart2-networkbased.html">13.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.html">13.9. Making the Installation Tree Available</a></span></dt><dt><span class="section"><a href="s1-kickstart2-startinginstall.html">13.10. Starting a Kickstart Installation</a></span></dt></dl></div><a id="id825750" class="indexterm"></a><a id="id848910" class="indexterm"></a><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-kickstart2-whatis">13.1.Â What are Kickstart Installations?</h2></div></div></div><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.
		</div><div class="para">
			Kickstart provides a way for users to automate a Fedora installation.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="VNC_Whitepaper-references.html"><strong>Prev</strong>12.4.Â References</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-kickstart2-howuse.html"><strong>Next</strong>13.2.Â How Do You Perform a Kickstart Installation?</a></li></ul></body></html>


--- NEW FILE ch-new-users.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ChapterÂ 2.Â New Users</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="index.html" title="Installation Guide" /><link rel="prev" href="sn-expert-post-install.html" title="1.5.Â Perform Post-installation Steps" /><link rel="next" href="sn-which-arch.html" title="2.2.Â Which Architecture Is My Computer?" /></head><body class="draft "><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><ul class="
 docnav"><li class="previous"><a accesskey="p" href="sn-expert-post-install.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-which-arch.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="ch-new-users">ChapterÂ 2.Â New Users</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-new-users.html#sn-howto-download">2.1. How Do I Download Installation Files?</a></span></dt><dd><dl><dt><span class="section"><a href="ch-new-users.html#sn-which-download-mirror">2.1.1. From a Mirror</a></span></dt><dt><span class="section"><a href="ch-new-users.html#sn-which-download-bt">2.1.2. From BitTorrent</a></span></dt></dl></dd><dt><span class="section"><a href="sn-which-arch.html">2.2. Which Architecture Is My Computer?</a></span></dt><dt><span class="section"><a href="sn-which-files.html">2.3. Which Files Do I Download?</a></span></dt><dt><spa
 n class="section"><a href="sn-making-media.html">2.4. How Do I Make Fedora Media?</a></span></dt><dd><dl><dt><span class="section"><a href="sn-making-media.html#sn-making-disc-media">2.4.1. Making CD or DVD Discs</a></span></dt><dt><span class="section"><a href="ch02s04s02.html">2.4.2. Making USB Media</a></span></dt></dl></dd><dt><span class="section"><a href="sn-cannot-download.html">2.5. What If I Cannot Download Fedora?</a></span></dt><dt><span class="section"><a href="sn-start-installation.html">2.6. How Do I Start the Installation Program?</a></span></dt></dl></div><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="note"><h2>Download Links</h2><div class="para">
			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.html" title="2.2.Â Which Architecture Is My Computer?">SectionÂ 2.2, â€œWhich Architecture Is My Computer?â€</a>.
		</div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-howto-download">2.1.Â How Do I Download Installation Files?</h2></div></div></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:
		</div><div class="itemizedlist"><ul><li><div class="para">
					A full set of the software on DVD media
				</div></li><li><div class="para">
					Live images you can use to try Fedora, and then install to your system if you so choose
				</div></li><li><div class="para">
					Reduced-size bootable CD and USB flash disk images you can use to install over an Internet connection
				</div></li><li><div class="para">
					Source code on DVD media
				</div></li></ul></div><div class="para">
			Most users want the Fedora Live image or the full set of installable software on DVD or CDs. The reduced bootable images are suitable for use with a fast Internet connection and install Fedora on one computer. Source code discs are not used for installing Fedora, but are resources for experienced users and software developers.
		</div><div class="note"><h2>Downloading media</h2><a id="id827412" class="indexterm"></a><a id="id813346" class="indexterm"></a><a id="id798526" class="indexterm"></a><div class="para">
				Users with a broadband Internet connection can download <em class="firstterm">ISO images</em> of CD and DVD media or images of USB flash disks. An ISO image is a copy of an entire disc in a format suitable for writing directly to a CD or DVD. A USB flash disk image is a copy of an entire disk in a format suitable for writing directly to a USB flash disk.
			</div><div class="para">
				For more information on burning CDs and DVDs, refer to <a class="xref" href="sn-making-media.html" title="2.4.Â How Do I Make Fedora Media?">SectionÂ 2.4, â€œHow Do I Make Fedora Media?â€</a>.
			</div></div><div class="para">
			Fedora software is available for download at no cost in a variety of ways.
		</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-which-download-mirror">2.1.1.Â From a Mirror</h3></div></div></div><a id="id806245" class="indexterm"></a><div class="para">
				To find the freely downloadable distributions of Fedora, look for a <em class="firstterm">mirror</em>. A mirror is a computer server open to the public for free downloads of software, including Fedora. Mirrors offer both free open source software and closed source software. To locate a mirror, visit <a href="http://mirrors.fedoraproject.org/publiclist">http://mirrors.fedoraproject.org/publiclist</a> using a Web browser, and choose a server from the list. The web page lists mirrors by geographic location. Mirrors geographically closer to you are ideal for faster downloading speeds.
			</div><div class="para">
				Mirrors publish Fedora software under a well-organized hierarchy of folders. For example, the Fedora 11 distribution normally appears in the directory <code class="filename">fedora/linux/releases/11/</code>. This directory contains a folder for each architecture supported by that release of Fedora. CD and DVD media files appear 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 11 for x86_64 at <code class="filename">fedora/linux/releases/11/Fedora/x86_64/iso/Fedora-11-x86_64-DVD.iso</code>.
			</div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-which-download-bt">2.1.2.Â From BitTorrent</h3></div></div></div><a id="id809008" class="indexterm"></a><a id="id809018" 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.
			</div><div class="para">
				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"><h2>Minimal Boot Images</h2><div class="para">
					Minimal boot CD and USB flash disk images are not available through BitTorrent.
				</div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-expert-post-install.html"><strong>Prev</strong>1.5.Â Perform Post-installation Steps</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-which-arch.html"><strong>Next</strong>2.2.Â Which Architecture Is My Computer?</a></li></ul></body></html>


--- NEW FILE ch-next-steps.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ChapterÂ 16.Â Your Next Steps</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-After_installation.html" title="PartÂ IV.Â After installation" /><link rel="prev" href="sn-smolt.html" title="15.4.Â Hardware Profile" /><link rel="next" href="sn-finishing-upgrade.html" title="16.2.Â Finishing an Upgrade" /></head><body class="draft "><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><ul class="
 docnav"><li class="previous"><a accesskey="p" href="sn-smolt.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-finishing-upgrade.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="ch-next-steps">ChapterÂ 16.Â Your Next Steps</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-next-steps.html#sn-system-updating">16.1. Updating Your System</a></span></dt><dt><span class="section"><a href="sn-finishing-upgrade.html">16.2. Finishing an Upgrade</a></span></dt><dt><span class="section"><a href="sn-switching-to-gui-login.html">16.3. Switching to a Graphical Login</a></span></dt><dt><span class="section"><a href="sn-news-subscriptions.html">16.4. Subscribing to Fedora Announcements and News</a></span></dt><dt><span class="section"><a href="sn-web-help.html">16.5. Finding Documentation and Support</a></span></dt><dt><span class="sec
 tion"><a href="sn-community.html">16.6. Joining the Fedora Community</a></span></dt></dl></div><div class="para">
		Fedora provides you with a complete operating system with a vast range of capabilities, supported by a large community.
	</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-system-updating">16.1.Â Updating Your System</h2></div></div></div><div class="para">
			The Fedora Project releases updated software packages for Fedora throughout the support period of each version. Updated packages add new features, improve reliability, resolve bugs, or remove security vulnerabilities. To ensure the security of your system, update regularly, and as soon as possible after a security announcement is issued. Refer to <a class="xref" href="sn-news-subscriptions.html" title="16.4.Â Subscribing to Fedora Announcements and News">SectionÂ 16.4, â€œSubscribing to Fedora Announcements and Newsâ€</a> for information on the Fedora announcements services.
		</div><div class="para">
			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="id796956" class="indexterm"></a>
			 <span class="application"><strong>Update System</strong></span>:
		</div><div class="figure" id="id784716"><div class="figure-contents"><div class="mediaobject"><img src="images/nextsteps/updating.png" alt="Updating your system" /><div class="longdesc"><div class="para">
						Updating your system screen
					</div></div></div></div><h6>FigureÂ 16.1.Â Updating your system</h6></div><br class="figure-break" /><div class="orderedlist"><ol><li><div class="para">
					Choose <span class="guimenu"><strong>System</strong></span> â†’ <span class="guisubmenu"><strong>Administration</strong></span> â†’ <span class="guimenuitem"><strong>Update System</strong></span>.
				</div></li><li><div class="para">
					To review the list of updated packages, select <span class="guilabel"><strong>Review</strong></span>.
				</div></li><li><div class="para">
					Click <span class="guibutton"><strong>Update System</strong></span> to begin the update process.
				</div></li><li><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><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="id822735" 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="id822757" 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">
			Enter the <code class="systemitem">root</code> password when prompted.
		</div><div class="para">
			Refer to <a href="http://docs.fedoraproject.org/yum/">http://docs.fedoraproject.org/yum/</a> for more information on <code class="command">yum</code>.
		</div><div class="note"><h2>Network Connection Required</h2><div class="para">
				Ensure that your system has an active network connection before you run the <span class="application"><strong>Update Software</strong></span> tool, or the <code class="command">yum</code> utility. The update process downloads information and packages from a network of servers.
			</div></div><div class="para">
			If your Fedora system has a permanent network connection, you may choose to enable daily system updates. To enable automatic updates, follow the instructions on the webpage <a href="http://docs.fedoraproject.org/yum/sn-updating-your-system.html">http://docs.fedoraproject.org/yum/sn-updating-your-system.html</a>.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-smolt.html"><strong>Prev</strong>15.4.Â Hardware Profile</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-finishing-upgrade.html"><strong>Next</strong>16.2.Â Finishing an Upgrade</a></li></ul></body></html>


--- NEW FILE ch-partitions-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>AppendixÂ A.Â An Introduction to Disk Partitions</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-Technical_appendixes.html" title="PartÂ V.Â Technical appendixes" /><link rel="prev" href="pt-Technical_appendixes.html" title="PartÂ V.Â Technical appendixes" /><link rel="next" href="ISCSI_disks.html" title="AppendixÂ B.Â ISCSI disks" /></head><body class="draft "><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="Document
 ation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pt-Technical_appendixes.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ISCSI_disks.html"><strong>Next</strong></a></li></ul><div class="appendix" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h1 id="ch-partitions-x86" class="title">An Introduction to Disk Partitions</h1></div></div></div><a id="id854580" class="indexterm"></a><a id="id830782" class="indexterm"></a><div class="note"><h2>Note</h2><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 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="ch-partitions-x86.html#s2-partitions-make-room-x86" title="A.1.4.Â Making Room For Fedora">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" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-partitions-concepts-x86">A.1.Â Hard Disk Basic Concepts</h2></div></div></div><a id="id829652" 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="ch-partitions-x86.html#fig-partitions-unused-drive-x86" title="FigureÂ A.1.Â An Unused Disk Drive">FigureÂ A.1, â€œAn Unused Disk Driveâ€</a>, shows a brand-new, unused disk drive.
		</div><div class="figure" id="fig-partitions-unused-drive-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/partitions/unused-drive.png" alt="An Unused Disk Drive" /><div class="longdesc"><div class="para">
	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" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><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="id927853" class="indexterm"></a><a id="id784340" 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.
</div></div></div></div><h6>FigureÂ A.2.Â Disk Drive with a File System</h6></div><br class="figure-break" /><div class="para">
				As <a class="xref" href="ch-partitions-x86.html#fig-partitions-formatted-drive-x86" title="FigureÂ A.2.Â Disk Drive with a File System">FigureÂ A.2, â€œDisk Drive with a File Systemâ€</a>, implies, the order imposed by a file system involves some trade-offs:
			</div><div class="itemizedlist"><ul><li><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><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="id871029" href="#ftn.id871029" class="footnote">5</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">
				It is also worth noting that there is no single, universal file system. As <a class="xref" href="ch-partitions-x86.html#fig-partitions-other-formatted-d-x86" title="FigureÂ A.3.Â Disk Drive with a Different File System">FigureÂ A.3, â€œDisk Drive with a Different File Systemâ€</a>, shows, a disk drive may have one of many different file systems written on it. As you might guess, different file systems tend to be incompatible; that is, an operating system that supports one file system (or a handful of related file system types) may not support another. This last statement is not a hard-and-fast rule, however. For example, Fedora supports a wide variety of file systems (including many commonly used by other operating systems), making data interchange between different file systems easy.
			</div><div class="figure" id="fig-partitions-other-formatted-d-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/partitions/other-formatted-drive.png" alt="Disk Drive with a Different File System" /><div class="longdesc"><div class="para">
	Image of a disk drive with a different file system.
</div></div></div></div><h6>FigureÂ A.3.Â Disk Drive with a Different File System</h6></div><br class="figure-break" /><div class="para">
	Of course, writing a file system to disk is only the beginning. The goal of this process is to actually <span class="emphasis"><em>store</em></span> and <span class="emphasis"><em>retrieve</em></span> data. Let us take a look at our drive after some files have been written to it.
</div><div class="figure" id="fig-partitions-used-formatted-dr-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/partitions/used-formatted-drive.png" alt="Disk Drive with Data Written to It" /><div class="longdesc"><div class="para">
	Image of a disk drive with data written to it.
</div></div></div></div><h6>FigureÂ A.4.Â Disk Drive with Data Written to It</h6></div><br class="figure-break" /><div class="para">
				As <a class="xref" href="ch-partitions-x86.html#fig-partitions-used-formatted-dr-x86" title="FigureÂ A.4.Â Disk Drive with Data Written to It">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" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-partitions-partitioning-x86">A.1.2.Â Partitions: Turning One Drive Into Many</h3></div></div></div><a id="id897965" class="indexterm"></a><a id="id955906" 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>.
</div><div class="note"><h2>Note</h2><div class="para">
		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 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="id949828" class="indexterm"></a><a id="id810048" class="indexterm"></a><div class="para">
				As <a class="xref" href="ch-partitions-x86.html#fig-partitions-unused-partitione-x86" title="FigureÂ A.5.Â Disk Drive with Partition Table">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:
</div><div class="itemizedlist"><ul><li><div class="para">
			The points on the disk where the partition starts and ends
		</div></li><li><div class="para">
			Whether the partition is "active"
		</div></li><li><div class="para">
			The partition's type
		</div></li></ul></div><div class="para">
	Let us take a closer look at each of these characteristics. The starting and ending points actually define the partition's size and location on the disk. The "active" flag is used by some operating systems' boot loaders. In other words, the operating system in the partition that is marked "active" is booted.
</div><div class="para">
	The partition's type can be a bit confusing. The type is a number that identifies the partition's anticipated usage. If that statement sounds a bit vague, that is because the meaning of the partition type is a bit vague. Some operating systems use the partition type to denote a specific file system type, to flag the partition as being associated with a particular operating system, to indicate that the partition contains a bootable operating system, or some combination of the three.
</div><div class="para">
				By this point, you might be wondering how all this additional complexity is normally used. Refer to <a class="xref" href="ch-partitions-x86.html#fig-partitions-dos-single-part-x86" title="FigureÂ A.6.Â Disk Drive With Single Partition">FigureÂ A.6, â€œDisk Drive With Single Partitionâ€</a>, for an example.
			</div><div class="figure" id="fig-partitions-dos-single-part-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/partitions/dos-single-partition.png" alt="Disk Drive With Single Partition" /><div class="longdesc"><div class="para">
	Image of a disk drive with a single partition.
</div></div></div></div><h6>FigureÂ A.6.Â Disk Drive With Single Partition</h6></div><br class="figure-break" /><div class="para">
	In many cases, there is only a single partition spanning the entire disk, essentially duplicating the method used before partitions. The partition table has only one entry used, and it points to the start of the partition.
</div><div class="para">
				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="ch-partitions-x86.html#tb-partitions-types-x86" title="TableÂ A.1.Â Partition Types">TableÂ A.1, â€œPartition Typesâ€</a>, it is adequate for the purposes of this discussion.
			</div><div class="para">
				<a class="xref" href="ch-partitions-x86.html#tb-partitions-types-x86" title="TableÂ A.1.Â Partition Types">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="id824746" class="indexterm"></a><a id="id892808" class="indexterm"></a><div class="table" id="tb-partitions-types-x86"><div class="table-contents"><table summary="Partition Types" border="1"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>
								Partition Type
							</th><th>
								Value
							</th><th>
								Partition Type
							</th><th>
								Value
							</th></tr></thead><tbody><tr><td>
								Empty
							</td><td>
								00
							</td><td>
								Novell Netware 386
							</td><td>
								65
							</td></tr><tr><td>
								DOS 12-bit FAT
							</td><td>
								01
							</td><td>
								PIC/IX
							</td><td>
								75
							</td></tr><tr><td>
								XENIX root
							</td><td>
								02
							</td><td>
								Old MINIX
							</td><td>
								80
							</td></tr><tr><td>
								XENIX usr
							</td><td>
								03
							</td><td>
								Linux/MINUX
							</td><td>
								81
							</td></tr><tr><td>
								DOS 16-bit <=32M
							</td><td>
								04
							</td><td>
								Linux swap
							</td><td>
								82
							</td></tr><tr><td>
								Extended
							</td><td>
								05
							</td><td>
								Linux native
							</td><td>
								83
							</td></tr><tr><td>
								DOS 16-bit >=32
							</td><td>
								06
							</td><td>
								Linux extended
							</td><td>
								85
							</td></tr><tr><td>
								OS/2 HPFS
							</td><td>
								07
							</td><td>
								Amoeba
							</td><td>
								93
							</td></tr><tr><td>
								AIX
							</td><td>
								08
							</td><td>
								Amoeba BBT
							</td><td>
								94
							</td></tr><tr><td>
								AIX bootable
							</td><td>
								09
							</td><td>
								BSD/386
							</td><td>
								a5
							</td></tr><tr><td>
								OS/2 Boot Manager
							</td><td>
								0a
							</td><td>
								OpenBSD
							</td><td>
								a6
							</td></tr><tr><td>
								Win95 FAT32
							</td><td>
								0b
							</td><td>
								NEXTSTEP
							</td><td>
								a7
							</td></tr><tr><td>
								Win95 FAT32 (LBA)
							</td><td>
								0c
							</td><td>
								BSDI fs
							</td><td>
								b7
							</td></tr><tr><td>
								Win95 FAT16 (LBA)
							</td><td>
								0e
							</td><td>
								BSDI swap
							</td><td>
								b8
							</td></tr><tr><td>
								Win95 Extended (LBA)
							</td><td>
								0f
							</td><td>
								Syrinx
							</td><td>
								c7
							</td></tr><tr><td>
								Venix 80286
							</td><td>
								40
							</td><td>
								CP/M
							</td><td>
								db
							</td></tr><tr><td>
								Novell
							</td><td>
								51
							</td><td>
								DOS access
							</td><td>
								e1
							</td></tr><tr><td>
								PPC PReP Boot
							</td><td>
								41
							</td><td>
								DOS R/O
							</td><td>
								e3
							</td></tr><tr><td>
								GNU HURD
							</td><td>
								63
							</td><td>
								DOS secondary
							</td><td>
								f2
							</td></tr><tr><td>
								Novell Netware 286
							</td><td>
								64
							</td><td>
								BBT
							</td><td>
								ff
							</td></tr></tbody></table></div><h6>TableÂ A.1.Â Partition Types</h6></div><br class="table-break" /></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><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="id909984" class="indexterm"></a><a id="id889499" class="indexterm"></a><a id="id830692" class="indexterm"></a><a id="id927758" 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="ch-partitions-x86.html#tb-partitions-types-x86" title="TableÂ A.1.Â Partition Types">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.
			</div><div class="para">
				When a partition is created and its type is set to "Extended," an extended partition table is created. In essence, the extended partition is like a disk drive in its own right â€” it has a partition table that points to one or more partitions (now called <em class="firstterm">logical partitions</em>, as opposed to the four <em class="firstterm">primary partitions</em>) contained entirely within the extended partition itself. <a class="xref" href="ch-partitions-x86.html#fig-partitions-extended-part-x86" title="FigureÂ A.7.Â Disk Drive With Extended Partition">FigureÂ A.7, â€œDisk Drive With Extended Partitionâ€</a>, shows a disk drive with one primary partition and one extended partition containing two logical partitions (along with some unpartitioned free space).
			</div><div class="figure" id="fig-partitions-extended-part-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/partitions//extended-partitions.png" alt="Disk Drive With Extended Partition" /><div class="longdesc"><div class="para">
	Image of a disk drive with an extended partition.
</div></div></div></div><h6>FigureÂ A.7.Â Disk Drive With Extended Partition</h6></div><br class="figure-break" /><div class="para">
	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" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-partitions-make-room-x86">A.1.4.Â Making Room For Fedora</h3></div></div></div><a id="id841657" 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 class="itemizedlist"><ul><li><div class="para">
			Unpartitioned free space is available
		</div></li><li><div class="para">
			An unused partition is available
		</div></li><li><div class="para">
			Free space in an actively used partition is available
		</div></li></ul></div><div class="para">
	Let us look at each scenario in order.
</div><div class="note"><h2>Note</h2><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 class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="s3-partitions-free-space-x86">A.1.4.1.Â Using Unpartitioned Free Space</h4></div></div></div><a id="id901009" 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="ch-partitions-x86.html#fig-partitions-unpart-space-x86" title="FigureÂ A.8.Â Disk Drive with Unpartitioned Free Space">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" 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.
</div></div></div></div><h6>FigureÂ A.8.Â Disk Drive with Unpartitioned Free Space</h6></div><br class="figure-break" /><div class="para">
					In <a class="xref" href="ch-partitions-x86.html#fig-partitions-unpart-space-x86" title="FigureÂ A.8.Â Disk Drive with Unpartitioned Free Space">FigureÂ A.8, â€œDisk Drive with Unpartitioned Free Spaceâ€</a>, <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.
				</div><div class="para">
	If you think about it, an unused hard disk also falls into this category. The only difference is that <span class="emphasis"><em>all</em></span> the space is not part of any defined partition.
</div><div class="para">
					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="ch-partitions-x86.html#s3-partitions-active-part-x86" title="A.1.4.3.Â Using Free Space from an Active Partition">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" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><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="id912892" 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="ch-partitions-x86.html#fig-partitions-unused-partition-x86" title="FigureÂ A.9.Â Disk Drive With an Unused Partition">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" 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.
</div></div></div></div><h6>FigureÂ A.9.Â Disk Drive With an Unused Partition</h6></div><br class="figure-break" /><div class="para">
					In <a class="xref" href="ch-partitions-x86.html#fig-partitions-unused-partition-x86" title="FigureÂ A.9.Â Disk Drive With an Unused Partition">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" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><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="id893987" class="indexterm"></a><div class="para">
	This is the most common situation. It is also, unfortunately, the hardest to handle. The main problem is that, even if you have enough free space, it is presently allocated to a partition that is already in use. If you purchased a computer with pre-installed software, the hard disk most likely has one massive partition holding the operating system and data.
</div><div class="para">
	Aside from adding a new hard drive to your system, you have two choices:
</div><div class="variablelist"><dl><dt><span class="term"> <a id="id876910" class="indexterm"></a>
<span class="emphasis"><em>Destructive Repartitioning</em></span></span></dt><dd><div class="para">
	Basically, you delete the single large partition and create several smaller ones. As you might imagine, any data you had in the original partition is destroyed. This means that making a complete backup is necessary. For your own sake, make two backups, use verification (if available in your backup software), and try to read data from your backup <span class="emphasis"><em>before</em></span> you delete the partition.
</div><div class="warning"><h2>Warning</h2><div class="para">
		If there was an operating system of some type installed on that partition, it needs to be reinstalled as well. Be aware that some computers sold with pre-installed operating systems may not include the CD-ROM media to reinstall the original operating system. The best time to notice if this applies to your system is <span class="emphasis"><em>before</em></span> you destroy your original partition and its operating system installation.
	</div></div><div class="para">
								After creating a smaller partition for your existing operating system, you can reinstall any software, restore your data, and start your Fedora installation. <a class="xref" href="ch-partitions-x86.html#fig-partitions-dstrct-reprt-x86" title="FigureÂ A.10.Â Disk Drive Being Destructively Repartitioned">FigureÂ A.10, â€œDisk Drive Being Destructively Repartitionedâ€</a> shows this being done.
							</div><div class="figure" id="fig-partitions-dstrct-reprt-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/partitions/dstrct-reprt.png" alt="Disk Drive Being Destructively Repartitioned" /><div class="longdesc"><div class="para">
	Image of a disk drive being destructively repartitioned, where <em class="wordasword">1</em> represents before and <em class="wordasword">2</em> represents after.
</div></div></div></div><h6>FigureÂ A.10.Â Disk Drive Being Destructively Repartitioned</h6></div><br class="figure-break" /><div class="para">
								In <a class="xref" href="ch-partitions-x86.html#fig-partitions-dstrct-reprt-x86" title="FigureÂ A.10.Â Disk Drive Being Destructively Repartitioned">FigureÂ A.10, â€œDisk Drive Being Destructively Repartitionedâ€</a>, <em class="wordasword">1</em> represents before and <em class="wordasword">2</em> represents after.
							</div><div class="warning"><h2>Warning</h2><div class="para">
									As <a class="xref" href="ch-partitions-x86.html#fig-partitions-dstrct-reprt-x86" title="FigureÂ A.10.Â Disk Drive Being Destructively Repartitioned">FigureÂ A.10, â€œDisk Drive Being Destructively Repartitionedâ€</a>, shows, any data present in the original partition is lost without proper backup!
								</div></div></dd><dt><span class="term"> <a id="id903663" class="indexterm"></a>
						<span class="emphasis"><em>Non-Destructive Repartitioning</em></span></span></dt><dd><div class="para">
								Here, you run a program that does the seemingly impossible: it makes a big partition smaller without losing any of the files stored in that partition. Many people have found this method to be reliable and trouble-free. What software should you use to perform this feat? There are several disk management software products on the market. Do some research to find the one that is best for your situation.
							</div><div class="para">
								While the process of non-destructive repartitioning is rather straightforward, there are a number of steps involved:
							</div><div class="itemizedlist"><ul><li><div class="para">
										Compress and backup existing data
									</div></li><li><div class="para">
										Resize the existing partition
									</div></li><li><div class="para">
										Create new partition(s)
									</div></li></ul></div></dd></dl></div><div class="para">
					Next we will look at each step in a bit more detail.
				</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h5 class="title" id="s4-partitions-compress-data-x86">A.1.4.3.1.Â Compress existing data</h5></div></div></div><div class="para">
						As <a class="xref" href="ch-partitions-x86.html#fig-partitions-compression-x86" title="FigureÂ A.11.Â Disk Drive Being Compressed">FigureÂ A.11, â€œDisk Drive Being Compressedâ€</a>, shows, the first step is to compress the data in your existing partition. The reason for doing this is to rearrange the data such that it maximizes the available free space at the "end" of the partition.
					</div><div class="figure" id="fig-partitions-compression-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/partitions/compression.png" alt="Disk Drive Being Compressed" /><div class="longdesc"><div class="para">
									Image of a disk drive being compressed, where <em class="wordasword">1</em> represents before and <em class="wordasword">2</em> represents after.
								</div></div></div></div><h6>FigureÂ A.11.Â Disk Drive Being Compressed</h6></div><br class="figure-break" /><div class="para">
						In <a class="xref" href="ch-partitions-x86.html#fig-partitions-compression-x86" title="FigureÂ A.11.Â Disk Drive Being Compressed">FigureÂ A.11, â€œDisk Drive Being Compressedâ€</a>, <em class="wordasword">1</em> represents before and <em class="wordasword">2</em> represents after.
					</div><div class="para">
						This step is crucial. Without it, the location of your data could prevent the partition from being resized to the extent desired. Note also that, for one reason or another, some data cannot be moved. If this is the case (and it severely restricts the size of your new partition(s)), you may be forced to destructively repartition your disk.
					</div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h5 class="title" id="s4-partitions-resize-x86">A.1.4.3.2.Â Resize the existing partition</h5></div></div></div><div class="para">
						<a class="xref" href="ch-partitions-x86.html#fig-partitions-part-resize-x86" title="FigureÂ A.12.Â Disk Drive with Partition Resized">FigureÂ A.12, â€œDisk Drive with Partition Resizedâ€</a>, shows the actual resizing process. While the actual result of the resizing operation varies depending on the software used, in most cases the newly freed space is used to create an unformatted partition of the same type as the original partition.
					</div><div class="figure" id="fig-partitions-part-resize-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/partitions/part-resize.png" alt="Disk Drive with Partition Resized" /><div class="longdesc"><div class="para">
									Image of a disk drive with a resized partition, where <em class="wordasword">1</em> represents before and <em class="wordasword">2</em> represents after.
								</div></div></div></div><h6>FigureÂ A.12.Â Disk Drive with Partition Resized</h6></div><br class="figure-break" /><div class="para">
						In <a class="xref" href="ch-partitions-x86.html#fig-partitions-part-resize-x86" title="FigureÂ A.12.Â Disk Drive with Partition Resized">FigureÂ A.12, â€œDisk Drive with Partition Resizedâ€</a>, <em class="wordasword">1</em> represents before and <em class="wordasword">2</em> represents after.
					</div><div class="para">
						It is important to understand what the resizing software you use does with the newly freed space, so that you can take the appropriate steps. In the case we have illustrated, it would be best to delete the new DOS partition and create the appropriate Linux partition(s).
					</div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h5 class="title" id="s4-partitions-create-new-x86">A.1.4.3.3.Â Create new partition(s)</h5></div></div></div><div class="para">
						As the previous step implied, it may or may not be necessary to create new partitions. However, unless your resizing software is Linux-aware, it is likely that you must delete the partition that was created during the resizing process. <a class="xref" href="ch-partitions-x86.html#fig-partitions-nondestruct-fin-x86" title="FigureÂ A.13.Â Disk Drive with Final Partition Configuration">FigureÂ A.13, â€œDisk Drive with Final Partition Configurationâ€</a>, shows this being done.
					</div><div class="figure" id="fig-partitions-nondestruct-fin-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/partitions/nondestruct-fin.png" alt="Disk Drive with Final Partition Configuration" /><div class="longdesc"><div class="para">
									Image of a disk drive with final partition configuration, where <em class="wordasword">1</em> represents before and <em class="wordasword">2</em> represents after.
								</div></div></div></div><h6>FigureÂ A.13.Â Disk Drive with Final Partition Configuration</h6></div><br class="figure-break" /><div class="para">
						In <a class="xref" href="ch-partitions-x86.html#fig-partitions-nondestruct-fin-x86" title="FigureÂ A.13.Â Disk Drive with Final Partition Configuration">FigureÂ A.13, â€œDisk Drive with Final Partition Configurationâ€</a>, <em class="wordasword">1</em> represents before and <em class="wordasword">2</em> represents after.
					</div><div class="note"><h2>Note</h2><div class="para">
							The following information is specific to x86-based computers only.
						</div></div><a id="id822106" class="indexterm"></a><div class="para">
						As a convenience to our customers, we provide the <code class="command">parted</code> utility. This is a freely available program that can resize partitions.
					</div><div class="para">
						If you decide to repartition your hard drive with <code class="command">parted</code>, it is important that you be familiar with disk storage and that you perform a backup of your computer data. You should make two copies of all the important data on your computer. These copies should be to removable media (such as tape, CD-ROM, or diskettes), and you should make sure they are readable before proceeding.
					</div><div class="para">
						Should you decide to use <code class="command">parted</code>, be aware that after <code class="command">parted</code> runs you are left with <span class="emphasis"><em>two</em></span> partitions: the one you resized, and the one <code class="command">parted</code> created out of the newly freed space. If your goal is to use that space to install Fedora, you should delete the newly created partition, either by using the partitioning utility under your current operating system or while setting up partitions during installation.
					</div></div></div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-partitions-part-name-x86">A.1.5.Â Partition Naming Scheme</h3></div></div></div><a id="id955980" class="indexterm"></a><a id="id928552" class="indexterm"></a><div class="para">
				Linux refers to disk partitions using a combination of letters and numbers which may be confusing, particularly if you are used to the "C drive" way of referring to hard disks and their partitions. In the DOS/Windows world, partitions are named using the following method:
			</div><div class="itemizedlist"><ul><li><div class="para">
						Each partition's type is checked to determine if it can be read by DOS/Windows.
					</div></li><li><div class="para">
						If the partition's type is compatible, it is assigned a "drive letter." The drive letters start with a "C" and move on to the following letters, depending on the number of partitions to be labeled.
					</div></li><li><div class="para">
						The drive letter can then be used to refer to that partition as well as the file system contained on that partition.
					</div></li></ul></div><div class="para">
				Fedora uses a naming scheme that is more flexible and conveys more information than the approach used by other operating systems. The naming scheme is file-based, with file names in the form of <code class="filename">/dev/<em class="replaceable"><code>xxyN</code></em></code>.
			</div><div class="para">
				Here is how to decipher the partition naming scheme:
			</div><div class="variablelist"><dl><dt><span class="term"><code class="filename">/dev/</code></span></dt><dd><div class="para">
							This is the name of the directory in which all device files reside. Since partitions reside on hard disks, and hard disks are devices, the files representing all possible partitions reside in <code class="filename">/dev/</code>.
						</div></dd><dt><span class="term"><code class="filename"><em class="replaceable"><code>xx</code></em></code></span></dt><dd><div class="para">
							The first two letters of the partition name indicate the type of device on which the partition resides, usually either <code class="filename">hd</code> (for IDE disks) or <code class="filename">sd</code> (for SCSI disks).
						</div></dd><dt><span class="term"><code class="filename"><em class="replaceable"><code>y</code></em></code></span></dt><dd><div class="para">
							This letter indicates which device the partition is on. For example, <code class="filename">/dev/hda</code> (the first IDE hard disk) or <code class="filename">/dev/sdb</code> (the second SCSI disk).
						</div></dd><dt><span class="term"><code class="filename"><em class="replaceable"><code>N</code></em></code></span></dt><dd><div class="para">
							The final number denotes the partition. The first four (primary or extended) partitions are numbered <code class="filename">1</code> through <code class="filename">4</code>. Logical partitions start at <code class="filename">5</code>. So, for example, <code class="filename">/dev/hda3</code> is the third primary or extended partition on the first IDE hard disk, and <code class="filename">/dev/sdb6</code> is the second logical partition on the second SCSI hard disk.
						</div></dd></dl></div><div class="note"><h2>Note</h2><div class="para">
					There is no part of this naming convention that is based on partition type; unlike DOS/Windows, <span class="emphasis"><em>all</em></span> partitions can be identified under Fedora. Of course, this does not mean that Fedora can access data on every type of partition, but in many cases it is possible to access data on a partition dedicated to another operating system.
				</div></div><div class="para">
				Keep this information in mind; it makes things easier to understand when you are setting up the partitions Fedora requires.
			</div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-partitions-other-os-x86">A.1.6.Â Disk Partitions and Other Operating Systems</h3></div></div></div><a id="id941035" class="indexterm"></a><div class="para">
				If your Fedora partitions are sharing a hard disk with partitions used by other operating systems, most of the time you will have no problems. However, there are certain combinations of Linux and other operating systems that require extra care.
			</div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-partitions-mt-points-x86">A.1.7.Â Disk Partitions and Mount Points</h3></div></div></div><a id="id948034" class="indexterm"></a><a id="id948047" class="indexterm"></a><div class="para">
				One area that many people new to Linux find confusing is the matter of how partitions are used and accessed by the Linux operating system. In DOS/Windows, it is relatively simple: Each partition gets a "drive letter." You then use the correct drive letter to refer to files and directories on its corresponding partition.
			</div><div class="para">
				This is entirely different from how Linux deals with partitions and, for that matter, with disk storage in general. The main difference is that each partition is used to form part of the storage necessary to support a single set of files and directories. This is done by associating a partition with a directory through a process known as <em class="firstterm">mounting</em>. Mounting a partition makes its storage available starting at the specified directory (known as a <em class="firstterm">mount point</em>).
			</div><div class="para">
				For example, if partition <code class="filename">/dev/hda5</code> is mounted on <code class="filename">/usr/</code>, that would mean that all files and directories under <code class="filename">/usr/</code> physically reside on <code class="filename">/dev/hda5</code>. So the file <code class="filename">/usr/share/doc/FAQ/txt/Linux-FAQ</code> would be stored on <code class="filename">/dev/hda5</code>, while the file <code class="filename">/etc/gdm/custom.conf</code> would not.
			</div><div class="para">
				Continuing our example, it is also possible that one or more directories below <code class="filename">/usr/</code> would be mount points for other partitions. For instance, a partition (say, <code class="filename">/dev/hda7</code>) could be mounted on <code class="filename">/usr/local/</code>, meaning that <code class="filename">/usr/local/man/whatis</code> would then reside on <code class="filename">/dev/hda7</code> rather than <code class="filename">/dev/hda5</code>.
			</div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-partitions-how-many-x86">A.1.8.Â How Many Partitions?</h3></div></div></div><a id="id839872" class="indexterm"></a><div class="para">
				At this point in the process of preparing to install Fedora, you must give some consideration to the number and size of the partitions to be used by your new operating system. The question of "how many partitions" continues to spark debate within the Linux community and, without any end to the debate in sight, it is safe to say that there are probably as many partition layouts as there are people debating the issue.
			</div><div class="para">
				Keeping this in mind, we recommend that, unless you have a reason for doing otherwise, you should at least create the following partitions: <code class="filename">swap</code>, <code class="filename">/boot/</code> (or a <code class="filename">/boot/efi/</code> partition for Itanium systems), a <code class="filename">/var/</code> partition for Itanium systems, and <code class="filename">/</code> (root).
			</div><div class="para">
				For more information, refer to <a class="xref" href="s2-diskpartrecommend-x86.html" title="7.21.4.Â Recommended Partitioning Scheme">SectionÂ 7.21.4, â€œRecommended Partitioning Schemeâ€</a>.
			</div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id871029" href="#id871029" class="para">5</a>] </sup>
				Blocks really <span class="emphasis"><em>are</em></span> consistently sized, unlike our illustrations. Keep in mind, also, that an average disk drive contains thousands of blocks. But for the purposes of this discussion, please ignore these minor discrepancies.
			</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pt-Technical_appendixes.html"><strong>Prev</strong>PartÂ V.Â Technical appendixes</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ISCSI_disks.html"><strong>Next</strong>AppendixÂ B.Â ISCSI disks</a></li></ul></body></html>


--- NEW FILE ch-redhat-config-kickstart.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ChapterÂ 14.Â Kickstart Configurator</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-Advanced_installation_options.html" title="PartÂ III.Â Advanced installation options" /><link rel="prev" href="s1-kickstart2-startinginstall.html" title="13.10.Â Starting a Kickstart Installation" /><link rel="next" href="s1-redhat-config-kickstart-install.html" title="14.2.Â Installation Method" /></head><body class="draft "><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="Com
 mon_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kickstart2-startinginstall.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-redhat-config-kickstart-install.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="ch-redhat-config-kickstart">ChapterÂ 14.Â <span class="application"><strong>Kickstart Configurator</strong></span></h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-redhat-config-kickstart.html#s1-redhat-config-kickstart-basic">14.1. Basic Configuration</a></span></dt><dt><span class="section"><a href="s1-redhat-config-kickstart-install.html">14.2. Installation Method</a></span></dt><dt><span class="section"><a href="s1-redhat-config-kickstart-bootloader.html">14.3. Boot Loader Options</a></span></dt><dt><span class="section"><a h
 ref="s1-redhat-config-kickstart-partitions.html">14.4. Partition Information</a></span></dt><dd><dl><dt><span class="section"><a href="s1-redhat-config-kickstart-partitions.html#s2-redhat-config-kickstart-create-part">14.4.1. Creating Partitions</a></span></dt></dl></dd><dt><span class="section"><a href="s1-redhat-config-kickstart-network.html">14.5. Network Configuration</a></span></dt><dt><span class="section"><a href="s1-redhat-config-kickstart-auth.html">14.6. Authentication</a></span></dt><dt><span class="section"><a href="s1-redhat-config-kickstart-firewall.html">14.7. Firewall Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="s1-redhat-config-kickstart-firewall.html#s2-redhat-config-kickstart-firewall-selinux">14.7.1. SELinux Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="s1-redhat-config-kickstart-xconfig.html">14.8. Display Configuration</a></span></dt><dt><span class="section"><a href="s1-redhat-config-kickstart-pkgs
 .html">14.9. Package Selection</a></span></dt><dt><span class="section"><a href="s1-redhat-config-kickstart-prescript.html">14.10. Pre-Installation Script</a></span></dt><dt><span class="section"><a href="s1-redhat-config-kickstart-postinstall.html">14.11. Post-Installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="s1-redhat-config-kickstart-postinstall.html#s2-redhat-config-kickstart-nochroot">14.11.1. Chroot Environment</a></span></dt><dt><span class="section"><a href="s2-redhat-config-kickstart-interpreter.html">14.11.2. Use an Interpreter</a></span></dt></dl></dd><dt><span class="section"><a href="s1-redhat-config-kickstart-savefile.html">14.12. Saving the File</a></span></dt></dl></div><a id="id966222" class="indexterm"></a><a id="id884455" 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">
		To use <span class="application"><strong>Kickstart Configurator</strong></span>, you must be running the X Window System. To start <span class="application"><strong>Kickstart Configurator</strong></span>, select <span class="guimenu"><strong>Applications</strong></span> (the main menu on the panel) => <span class="guimenu"><strong>System Tools</strong></span> => <span class="guimenuitem"><strong>Kickstart</strong></span>, or type the command <code class="command">/usr/sbin/system-config-kickstart</code>.
	</div><a id="id845066" class="indexterm"></a><div class="para">
		As you are creating a kickstart file, you can select <span class="guimenuitem"><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" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-redhat-config-kickstart-basic">14.1.Â Basic Configuration</h2></div></div></div><a id="id797821" 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" alt="Basic Configuration" /><div class="longdesc"><div class="para">
						Basic Configuration
					</div></div></div></div><h6>FigureÂ 14.1.Â Basic Configuration</h6></div><br class="figure-break" /><a id="id788802" 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="id812523" class="indexterm"></a><div class="para">
			Select the system keyboard type from the <span class="guimenu"><strong>Keyboard</strong></span> menu.
		</div><a id="id812550" 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="id865912" class="indexterm"></a><a id="id865929" 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><a id="id802272" 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="id796878" 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="id796905" 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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kickstart2-startinginstall.html"><strong>Prev</strong>13.10.Â Starting a Kickstart Installation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-redhat-config-kickstart-install.html"><strong>Next</strong>14.2.Â Installation Method</a></li></ul></body></html>


--- NEW FILE ch-steps-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ChapterÂ 3.Â Steps to Get You Started</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-Before_you_begin.html" title="PartÂ I.Â Before you begin" /><link rel="prev" href="pt-Before_you_begin.html" title="PartÂ I.Â Before you begin" /><link rel="next" href="sn-Is_Your_Hardware_Compatible-x86.html" title="3.2.Â Is Your Hardware Compatible?" /></head><body class="draft "><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="Doc
 umentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pt-Before_you_begin.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-Is_Your_Hardware_Compatible-x86.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="ch-steps-x86">ChapterÂ 3.Â Steps to Get You Started</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-steps-x86.html#id787237">3.1. Upgrade or Install?</a></span></dt><dt><span class="section"><a href="sn-Is_Your_Hardware_Compatible-x86.html">3.2. Is Your Hardware Compatible?</a></span></dt><dt><span class="section"><a href="ch03s03.html">3.3. Do You Have Enough Disk Space?</a></span></dt><dt><span class="section"><a href="ch03s04.html">3.4. Can You Install Using the CD-ROM or DVD?</a></span></dt><dd><dl><dt><span class="section"><a href="ch03s04.html#id825179">3.4.1. Alternative Boo
 t Methods</a></span></dt><dt><span class="section"><a href="s2-steps-make-cd.html">3.4.2. Making an Installation Boot CD-ROM</a></span></dt></dl></dd><dt><span class="section"><a href="s1-steps-network-installs-x86.html">3.5. Preparing for a Network Installation</a></span></dt><dd><dl><dt><span class="section"><a href="s1-steps-network-installs-x86.html#id799943">3.5.1. Preparing for FTP and HTTP installation</a></span></dt><dt><span class="section"><a href="ch03s05s02.html">3.5.2. Preparing for an NFS install</a></span></dt></dl></dd><dt><span class="section"><a href="ch03s06.html">3.6. Preparing for a Hard Drive Installation</a></span></dt></dl></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="id787237">3.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.html" title="ChapterÂ 18.Â Upgrading Your Current System">ChapterÂ 18, <i>Upgrading Your Current System</i></a>.
	</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pt-Before_you_begin.html"><strong>Prev</strong>PartÂ I.Â Before you begin</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-Is_Your_Hardware_Compatible-x86.html"><strong>Next</strong>3.2.Â Is Your Hardware Compatible?</a></li></ul></body></html>


--- NEW FILE ch-trouble-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ChapterÂ 8.Â Troubleshooting Installation on an Intel or AMD System</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-The_installation_process.html" title="PartÂ II.Â The installation process" /><link rel="prev" href="s1-complete-x86.html" title="7.26.Â Installation Complete" /><link rel="next" href="ch08s02.html" title="8.2.Â Trouble Beginning the Installation" /></head><body class="draft "><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/i
 mage_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-complete-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch08s02.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="ch-trouble-x86">ChapterÂ 8.Â Troubleshooting Installation on an <span class="trademark">Intel</span>Â® or AMD System</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-trouble-x86.html#id888245">8.1. You are unable to boot Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="ch-trouble-x86.html#id842934">8.1.1. Are You Unable to Boot With Your RAID Card?</a></span></dt><dt><span class="section"><a href="ch-trouble-x86.html#id835915">8.1.2. Is Your System Displaying Signal 11 Errors?</a></span></dt></dl></dd><dt><span class="section"><a href="ch08s02.html">8.2. Trouble Beginning t
 he Installation</a></span></dt><dd><dl><dt><span class="section"><a href="ch08s02.html#id914845">8.2.1. Problems with Booting into the Graphical Installation</a></span></dt></dl></dd><dt><span class="section"><a href="s1-trouble-install-x86.html">8.3. Trouble During the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="s1-trouble-install-x86.html#s2-trouble-nodevicefound-x86">8.3.1. No devices found to install Fedora  Error Message</a></span></dt><dt><span class="section"><a href="s2-trouble-tracebacks-x86.html">8.3.2. Saving traceback messages without removeable media</a></span></dt><dt><span class="section"><a href="s2-trouble-part-tables-x86.html">8.3.3. Trouble with Partition Tables</a></span></dt><dt><span class="section"><a href="s2-trouble-space-x86.html">8.3.4. Using Remaining Space</a></span></dt><dt><span class="section"><a href="s2-trouble-completeparts-x86.html">8.3.5. Other Partitioning Problems</a></span></dt><dt><span class="section"><a hr
 ef="ch08s03s06.html">8.3.6. Are You Seeing Python Errors?</a></span></dt></dl></dd><dt><span class="section"><a href="ch08s04.html">8.4. Problems After Installation</a></span></dt><dd><dl><dt><span class="section"><a href="ch08s04.html#s2-trouble-grub">8.4.1. Trouble With the Graphical GRUB Screen on an x86-based System?</a></span></dt><dt><span class="section"><a href="ch08s04s02.html">8.4.2. Booting into a Graphical Environment</a></span></dt><dt><span class="section"><a href="ch08s04s03.html">8.4.3. Problems with the X Window System (GUI)</a></span></dt><dt><span class="section"><a href="ch08s04s04.html">8.4.4. Problems with the X Server Crashing and Non-Root Users</a></span></dt><dt><span class="section"><a href="ch08s04s05.html">8.4.5. Problems When You Try to Log In</a></span></dt><dt><span class="section"><a href="s2-trouble-ram.html">8.4.6. Is Your RAM Not Being Recognized?</a></span></dt><dt><span class="section"><a href="ch08s04s07.html">8.4.7. Your Printer Does No
 t Work</a></span></dt><dt><span class="section"><a href="s2-trouble-sound.html">8.4.8. Problems with Sound Configuration</a></span></dt><dt><span class="section"><a href="ch08s04s09.html">8.4.9. Apache-based httpd service/Sendmail Hangs During Startup</a></span></dt></dl></dd></dl></div><a id="id799616" class="indexterm"></a><div class="para">
	This appendix discusses some common installation problems and their solutions.
</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="id888245">8.1.Â You are unable to boot Fedora</h2></div></div></div><a id="id820522" class="indexterm"></a><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id842934">8.1.1.Â Are You Unable to Boot With Your RAID Card?</h3></div></div></div><a id="id820736" class="indexterm"></a><a id="id798874" 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.
			</div><div class="para">
				Whether you choose automatic or manual partitioning, you must install your <code class="filename">/boot</code> partition outside of the RAID array, such as on a separate hard drive. An internal hard drive is necessary to use for partition creation with problematic RAID cards.
			</div><div class="para">
				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" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id835915">8.1.2.Â Is Your System Displaying Signal 11 Errors?</h3></div></div></div><a id="id835938" class="indexterm"></a><div class="para">
	A signal 11 error, commonly know 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.
</div><div class="para">
	Ensure that you have the latest installation updates and images. Review the online errata to see if newer versions are available. If the latest images still fail, it may be due to a problem with your hardware. Commonly, these errors are in your memory or CPU-cache. A possible solution for this error is turning off the CPU-cache in the BIOS, if your system supports this. You could also try to swap your memory around in the motherboard slots to check if the problem is either slot or memory related.
</div><div class="para">
	Another option is to perform a media check on your installation CD-ROMs. <span class="application"><strong>Anaconda</strong></span>, the 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. Red Hat recommends 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 CDs). 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 class="para">
	For more information concerning signal 11 errors, refer to:
</div><pre class="screen">
	<a href="http://www.bitwizard.nl/sig11/">http://www.bitwizard.nl/sig11/</a>
</pre></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-complete-x86.html"><strong>Prev</strong>7.26.Â Installation Complete</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch08s02.html"><strong>Next</strong>8.2.Â Trouble Beginning the Installation</a></li></ul></body></html>


--- NEW FILE ch-upgrade-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ChapterÂ 18.Â Upgrading Your Current System</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-After_installation.html" title="PartÂ IV.Â After installation" /><link rel="prev" href="s1-rescuemode-booting-emergency.html" title="17.4.Â Booting into Emergency Mode" /><link rel="next" href="ch18s02.html" title="18.2.Â Upgrading Your System" /></head><body class="draft "><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="Docum
 entation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-rescuemode-booting-emergency.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch18s02.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="ch-upgrade-x86">ChapterÂ 18.Â Upgrading Your Current System</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-upgrade-x86.html#id840127">18.1. Determining Whether to Upgrade or Re-Install</a></span></dt><dt><span class="section"><a href="ch18s02.html">18.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 class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="id840127">18.1.Â Determining Whether to Upgrade or Re-Install</h2></div></div></div><a id="id926836" class="indexterm"></a><a id="id842285" class="indexterm"></a><div class="para">
		While upgrading from Fedora 10 is supported, you are more likely to have a consistent experience by backing up your data and then installing this release of Fedora 11 over your previous Fedora installation.
	</div><div class="para">
		To upgrade from Fedora 10 you should bring your system up to date before performing the upgrade.
	</div><div class="important"><h2>Important</h2><div class="para">
			It is not possible to upgrade directly from Fedora 9 to Fedora 11. To upgrade Fedora 9 to Fedora 11, upgrade to Fedora 10 first.
		</div></div><div class="para">
		<span class="emphasis"><em>This recommended reinstallation method helps to ensure the best system stability possible.</em></span>
	</div><div class="para">
		If you currently use Fedora 10, you can perform a traditional, installation program-based upgrade.
	</div><div class="para">
		However, before you chose to upgrade your system, there are a few things you should keep in mind:
	</div><div class="itemizedlist"><ul><li><div class="para">
				Individual package configuration files may or may not work after performing an upgrade due to changes in various configuration file formats or layouts.
			</div></li><li><div class="para">
				If you have one of Red Hat's layered products (such as the Cluster Suite) installed, it may need to be manually upgraded after the upgrade has been completed.
			</div></li><li><div class="para">
				Third party or ISV applications may not work correctly following the upgrade.
			</div></li></ul></div><div class="para">
		Upgrading your system installs updated versions of the packages which are currently installed on your system.
	</div><div class="para">
		The upgrade process preserves existing configuration files by renaming them with an <code class="filename">.rpmsave</code> extension (for example, <code class="filename">sendmail.cf.rpmsave</code>). The upgrade process also creates a log of its actions in <code class="filename">/root/upgrade.log</code>.
	</div><div class="warning"><h2>Warning</h2><div class="para">
			As software evolves, configuration file formats can change. It is very important to carefully compare your original configuration files to the new files before integrating your changes.
		</div></div><div class="note"><h2>Note</h2><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 hard drive(s). Mistakes do happen and can result in the loss of all of your data.
		</div></div><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="id811279" class="indexterm"></a><a id="id821568" class="indexterm"></a></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-rescuemode-booting-emergency.html"><strong>Prev</strong>17.4.Â Booting into Emergency Mode</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch18s02.html"><strong>Next</strong>18.2.Â Upgrading Your System</a></li></ul></body></html>


--- NEW FILE ch-x86-uninstall.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ChapterÂ 19.Â Removing Fedora</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-After_installation.html" title="PartÂ IV.Â After installation" /><link rel="prev" href="ch18s02.html" title="18.2.Â Upgrading Your System" /><link rel="next" href="sn-x86-uninstall-dual.html" title="19.2.Â Your computer dual-boots Fedora and another operating system" /></head><body class="draft "><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" a
 lt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-x86-uninstall-dual.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="ch-x86-uninstall">ChapterÂ 19.Â Removing Fedora</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-x86-uninstall.html#sn-x86-uninstall-single">19.1. Fedora is the only operating system on the computer</a></span></dt><dt><span class="section"><a href="sn-x86-uninstall-dual.html">19.2. Your computer dual-boots Fedora and another operating system</a></span></dt><dd><dl><dt><span class="section"><a href="sn-x86-uninstall-dual.html#sn-x86-uninstall-dual-windows">19.2.1. Your computer dual-boots Fedora and a Microsoft Windows operating system</a></span></dt><dt><span class="section"><a href="sn-x86-uninstall
 -dual-mac.html">19.2.2. Your computer dual-boots Fedora and Mac OS X</a></span></dt><dt><span class="section"><a href="sn-x86-uninstall-dual-linux.html">19.2.3. Your computer dual-boots Fedora and a different Linux distribution</a></span></dt></dl></dd><dt><span class="section"><a href="sn-x86-uninstall-legacy.html">19.3. Replacing Fedora with MS-DOS or legacy versions of Microsoft Windows</a></span></dt></dl></div><a id="id791174" class="indexterm"></a><a id="id965890" 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"><h2> These instructions may destroy data! </h2><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.
		</div><div class="para">
			As a precaution, also back up data from any other operating systems that are installed on the same computer. Mistakes do happen and can result in the loss of all your data.
		</div><div class="para">
			If you back up data from Fedora to be used later in another operating system, make sure that the storage medium or device is readable by that other operating system. For example, without extra third-party software, Microsoft Windows cannot read an external hard drive that you have formatted with Fedora to use the ext2, ext3, or ext4 file system.
		</div></div><div class="para">
		To uninstall Fedora from your x86-based system, you must remove the Fedora boot loader information from your master boot record (MBR) and remove any partitions that contain the operating system. The method for removing Fedora from your computer varies, depending on whether Fedora is the only operating system installed on the computer, or whether the computer is configured to dual-boot Fedora and another operating system.
	</div><div class="para">
		These instructions cannot cover every possible computer configuration. If your computer is configured to boot three or more operating systems, or has a highly-customized partition scheme, use the following sections as a general guide to partition removal with the various tools described. In these situations, you will also need to learn to configure your chosen bootloader. See <a class="xref" href="ch-grub.html" title="AppendixÂ E.Â The GRUB Boot Loader">AppendixÂ E, <i>The GRUB Boot Loader</i></a> for a general introduction to the subject, but detailed instructions are beyond the scope of this document.
	</div><div class="important"><h2>Legacy versions of Microsoft operating systems</h2><div class="para">
			<span class="application"><strong>Fdisk</strong></span>, the disk partitioning tool provided with MS-DOS and Microsoft Windows, is unable to remove the file systems used by Fedora. MS-DOS and versions of Windows prior to Windows XP (except for Windows 2000) have no other means of removing or modifying partitions. Refer to <a class="xref" href="sn-x86-uninstall-legacy.html" title="19.3.Â Replacing Fedora with MS-DOS or legacy versions of Microsoft Windows">SectionÂ 19.3, â€œReplacing Fedora with MS-DOS or legacy versions of Microsoft Windowsâ€</a> for alternative removal methods for use with MS-DOS and these versions of Windows.
		</div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-x86-uninstall-single">19.1.Â Fedora is the only operating system on the computer</h2></div></div></div><div class="para">
		If Fedora is the only operating system on your computer, use the installation media for the replacement operating system to remove Fedora. Examples of installation media include the Windows XP installation CD, Windows Vista installation DVD, Mac OS X installation CDs or DVD, or the installation CD, CDs, or DVD of another Linux distribution.
	</div><div class="para">
		Note that some manufacturers of factory-built computers pre-installed with Microsoft Windows do not supply the Windows installation CD or DVD with the computer. The manufacturer may instead have supplied their own "system restore disk", or have included software with the computer that allowed you to create your own "system restore disk" when you first started the computer. In some cases, the system restore software is stored on a separate partition on the system's hard drive. If you cannot identify the installation media for an operating system that was pre-installed on your computer, consult the documentation supplied with the machine, or contact the manufacturer.
	</div><div class="para">
		When you have located the installation media for your chosen operating system:
	</div><div class="orderedlist"><ol><li><div class="para">
				Back up any data that you want to keep.
			</div></li><li><div class="para">
				Shut down the computer.
			</div></li><li><div class="para">
				Boot your computer with the installation disk for the replacement operating system.
			</div></li><li><div class="para">
				Follow the prompts presented during the installation process. Windows, OS X, and most Linux installation disks allow you to manually partition your hard drive during the installation process, or will offer you the option to remove all partitions and start with a fresh partition scheme. At this point, remove any existing partitions that the installation software detects or allow the installer to remove the partitions automatically. "System restore" media for computers pre-installed with Microsoft Windows might create a default partition layout automatically without input from you.
			</div><div class="warning"><h2>Warning</h2><div class="para">
					If your computer has system restore software stored on a partition on a hard drive, take care when removing partitions while installing an operating system from other media. Under these circumstances, you could destroy the partition holding the system restore software.
				</div></div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s02.html"><strong>Prev</strong>18.2.Â Upgrading Your System</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-x86-uninstall-dual.html"><strong>Next</strong>19.2.Â Your computer dual-boots Fedora and another...</a></li></ul></body></html>


--- NEW FILE ch02s04s02.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.2.Â Making USB Media</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="sn-making-media.html" title="2.4.Â How Do I Make Fedora Media?" /><link rel="prev" href="sn-making-media.html" title="2.4.Â How Do I Make Fedora Media?" /><link rel="next" href="ch02s04s02s02.html" title="2.4.2.2.Â USB Image Creation in Linux" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-making-media.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch02s04s02s02.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id785804">2.4.2.Â Making USB Media</h3></div></div></div><div class="para">
				To make bootable USB media, use a Fedora Live image. Use either a Windows or Linux system to make the bootable USB media.
			</div><div class="note"><h2>USB Image Writing is Nondestructive</h2><div class="para">
					Writing the Live image to the USB media is <span class="emphasis"><em>nondestructive</em></span>. Any existing data on the media is not harmed.
				</div><div class="para">
					<span class="emphasis"><em>It is always a good idea to back up important data before performing sensitive disk operations.</em></span>
				</div></div><div class="para">
				To begin, make sure there is sufficient free space available on the USB media. There is no need to repartition or reformat your media. <span class="emphasis"><em>It is always a good idea to back up important data before performing sensitive disk operations.</em></span>
			</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="id785846">2.4.2.1.Â USB Image Creation from Windows</h4></div></div></div><div class="procedure"><ol class="1"><li><div class="para">
							Download a Live ISO file as explained in <a class="xref" href="sn-which-files.html" title="2.3.Â Which Files Do I Download?">SectionÂ 2.3, â€œWhich Files Do I Download?â€</a>.
						</div></li><li><div class="para">
							Download the Windows <span class="application"><strong>liveusb-creator</strong></span> program at <a href="http://fedorahosted.org/liveusb-creator">http://fedorahosted.org/liveusb-creator</a>.
						</div></li><li><div class="para">
							Follow the instructions given at the site and in the <span class="application"><strong>liveusb-creator</strong></span> program to create the bootable USB media.
						</div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-making-media.html"><strong>Prev</strong>2.4.Â How Do I Make Fedora Media?</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch02s04s02s02.html"><strong>Next</strong>2.4.2.2.Â USB Image Creation in Linux</a></li></ul></body></html>


--- NEW FILE ch02s04s02s02.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.2.2.Â USB Image Creation in Linux</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch02s04s02.html" title="2.4.2.Â Making USB Media" /><link rel="prev" href="ch02s04s02.html" title="2.4.2.Â Making USB Media" /><link rel="next" href="sn-cannot-download.html" title="2.5.Â What If I Cannot Download Fedora?" /></head><body class="draft "><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><ul cl
 ass="docnav"><li class="previous"><a accesskey="p" href="ch02s04s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-cannot-download.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="id785908">2.4.2.2.Â USB Image Creation in Linux</h4></div></div></div><div class="procedure"><div class="para">
						USB media often comes in the form of flash devices sometimes called <em class="firstterm">pen drives</em>, <em class="firstterm">thumb disks</em>, or <em class="firstterm">keys</em>; or as an externally connected hard disk device. Almost all media of this type is formatted as a vfat file system. You can create bootable USB media on media formatted as ext2, ext3, or vfat.
					</div><div class="important"><h2>ext4 and Btrfs</h2><div class="para">
							The <span class="application"><strong>GRUB</strong></span> bootloader does not support the ext4 or Btrfs file systems. You cannot create bootable USB media on media formatted as ext4 or Btrfs.
						</div></div><div class="important"><h2>Unusual USB Media</h2><div class="para">
							In a few cases with oddly formatted or partitioned USB media, the image writing may fail.
						</div></div><ol class="1"><li><div class="para">
							Download a Live ISO file as shown in <a class="xref" href="sn-which-files.html" title="2.3.Â Which Files Do I Download?">SectionÂ 2.3, â€œWhich Files Do I Download?â€</a>.
						</div></li><li><div class="para">
							Install the <span class="package">livecd-tools</span> package on your system. For Fedora systems, use the following command:
						</div><pre class="screen">su -c 'yum -y install livecd-tools'
</pre></li><li><div class="para">
							Plug in your USB media.
						</div></li><li><div class="para">
							Find the device name for your USB media. If the media has a volume name, look up the name in <code class="filename">/dev/disk/by-label</code>, or use the <code class="command">findfs</code>:
						</div><pre class="screen">su -c 'findfs LABEL="<em class="replaceable"><code>MyLabel</code></em>"'
</pre><div class="para">
							If the media does not have a volume name, or you do not know it, consult the <code class="filename">/var/log/messages</code> log for details:
						</div><pre class="screen">su -c 'less /var/log/messages'
</pre></li><li><div class="para">
							Use the <code class="command">livecd-iso-to-disk</code> command to write the ISO image to the media:
						</div><pre class="screen">su -c 'livecd-iso-to-disk <em class="replaceable"><code>the_image.iso</code></em> /dev/<em class="replaceable"><code>sdX1</code></em>'
</pre><div class="para">
							Replace <em class="replaceable"><code>sdX1</code></em> with the device name for the partition on the USB media. Most flash drives and external hard disks use only one partition. If you have changed this behavior or have oddly partitioned media, you may need to consult other sources of help.
						</div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch02s04s02.html"><strong>Prev</strong>2.4.2.Â Making USB Media</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-cannot-download.html"><strong>Next</strong>2.5.Â What If I Cannot Download Fedora?</a></li></ul></body></html>


--- NEW FILE ch03s03.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.3.Â Do You Have Enough Disk Space?</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-steps-x86.html" title="ChapterÂ 3.Â Steps to Get You Started" /><link rel="prev" href="sn-Is_Your_Hardware_Compatible-x86.html" title="3.2.Â Is Your Hardware Compatible?" /><link rel="next" href="ch03s04.html" title="3.4.Â Can You Install Using the CD-ROM or DVD?" /></head><body class="draft "><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.pn
 g" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-Is_Your_Hardware_Compatible-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch03s04.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="id840408">3.3.Â Do You Have Enough Disk Space?</h2></div></div></div><a id="id792530" class="indexterm"></a><a id="id875145" class="indexterm"></a><a id="id819135" 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.html" title="AppendixÂ A.Â An Introduction to Disk Partitions">AppendixÂ A, <i>An Introduction to Disk Partitions</i></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 <span class="trademark">Intel</span>Â® 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 class="itemizedlist"><ul><li><div class="para">
			have enough <span class="emphasis"><em>unpartitioned<sup>[<a id="id812157" href="#ftn.id812157" class="footnote">1</a>]</sup></em></span> disk space for the installation of Fedora, or
		</div></li><li><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.html" title="7.21.4.Â Recommended Partitioning Scheme">SectionÂ 7.21.4, â€œ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.html" title="AppendixÂ A.Â An Introduction to Disk Partitions">AppendixÂ A, <i>An Introduction to Disk Partitions</i></a>.
	</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id812157" href="#id812157" class="para">1</a>] </sup>
				Unpartitioned disk space means that available disk space on the hard drive(s) 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.
			</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-Is_Your_Hardware_Compatible-x86.html"><strong>Prev</strong>3.2.Â Is Your Hardware Compatible?</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch03s04.html"><strong>Next</strong>3.4.Â Can You Install Using the CD-ROM or DVD?</a></li></ul></body></html>


--- NEW FILE ch03s04.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.4.Â Can You Install Using the CD-ROM or DVD?</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-steps-x86.html" title="ChapterÂ 3.Â Steps to Get You Started" /><link rel="prev" href="ch03s03.html" title="3.3.Â Do You Have Enough Disk Space?" /><link rel="next" href="s2-steps-make-cd.html" title="3.4.2.Â Making an Installation Boot CD-ROM" /></head><body class="draft "><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="Do
 cumentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-steps-make-cd.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="id838914">3.4.Â Can You Install Using the CD-ROM or DVD?</h2></div></div></div><a id="id834084" class="indexterm"></a><a id="id842974" class="indexterm"></a><div class="para">
		There are several methods that can be used to install Fedora.
	</div><div class="para">
	Installing from a CD-ROM or DVD requires that you have a Fedora 11 CD-ROM or DVD, and you have a DVD/CD-ROM drive on a system that supports booting from it.
</div><div class="para">
		Your BIOS may need to be changed to allow booting from your DVD/CD-ROM drive. For more information about changing your BIOS, refer to <a class="xref" href="s1-x86-starting.html#s2-x86-starting-booting" title="7.3.1.Â Booting the Installation Program on x86, AMD64, and Intel 64 Systems">SectionÂ 7.3.1, â€œBooting the Installation Program on x86, AMD64, and Intel 64 Systemsâ€</a>.
	</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id825179">3.4.1.Â Alternative Boot Methods</h3></div></div></div><a id="id874099" class="indexterm"></a><div class="variablelist"><dl><dt><span class="term">Boot DVD/CD-ROM</span></dt><dd><div class="para">
						<a id="id836335" class="indexterm"></a>
						 If you can boot using the DVD/CD-ROM drive, you can create your own CD-ROM to boot the installation program. This may be useful, for example, if you are performing an installation over a network or from a hard drive. Refer to <a class="xref" href="s2-steps-make-cd.html" title="3.4.2.Â Making an Installation Boot CD-ROM">SectionÂ 3.4.2, â€œMaking an Installation Boot CD-ROMâ€</a> for further instructions.
					</div></dd><dt><span class="term">USB pen drive</span></dt><dd><div class="para">
						<a id="id854330" class="indexterm"></a>
						<a id="id831138" class="indexterm"></a>
						 If you cannot boot from the DVD/CD-ROM drive, but you can boot using a USB device, such as a USB pen drive, the following alternative boot method is available:
					</div><div class="para">
						To boot using a USB pen drive, use the <code class="command">dd</code> command to copy the <code class="filename">diskboot.img</code> image file from the <code class="filename">/images/</code> directory on the DVD or CD-ROM #1. For example:
					</div><pre class="screen">dd if=diskboot.img of=/dev/sda
</pre><div class="para">
						Your BIOS must support booting from a USB device in order for this boot method to work.
					</div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s03.html"><strong>Prev</strong>3.3.Â Do You Have Enough Disk Space?</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-steps-make-cd.html"><strong>Next</strong>3.4.2.Â Making an Installation Boot CD-ROM</a></li></ul></body></html>


--- NEW FILE ch03s05s02.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.5.2.Â Preparing for an NFS install</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-steps-network-installs-x86.html" title="3.5.Â Preparing for a Network Installation" /><link rel="prev" href="s1-steps-network-installs-x86.html" title="3.5.Â Preparing for a Network Installation" /><link rel="next" href="ch03s06.html" title="3.6.Â Preparing for a Hard Drive Installation" /></head><body class="draft "><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_Conte
 nt/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-steps-network-installs-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch03s06.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id831122">3.5.2.Â Preparing for an NFS install</h3></div></div></div><div class="para">
		For NFS installation it is not necessary to mount the iso image. It is sufficient to make the iso image itself available via NFS. You can do this by moving the iso image or images to the NFS exported directory:
	</div><div class="itemizedlist"><ul><li><div class="para">
				For DVD:
			</div><div class="para">
				<code class="command"> mv <em class="replaceable"><code>/location/of/disk/space/</code></em>f11.iso <em class="replaceable"><code>/publicly/available/directory/</code></em></code>
			</div></li><li><div class="para">
				For CDROMs:
			</div><div class="para">
				<code class="command"> mv <em class="replaceable"><code>/location/of/disk/space/</code></em>f11-disk*.iso <em class="replaceable"><code>/publicly/available/directory/</code></em></code>
			</div></li></ul></div><div class="para">
		Ensure that the <code class="filename"><em class="replaceable"><code>/publicly/available/directory</code></em></code> directory is exported via NFS via an entry in <code class="filename">/etc/exports</code>.
	</div><div class="para">
		To export to a specific system:
	</div><div class="para">
		<code class="command"><em class="replaceable"><code>/publicly/available/directory</code></em> <em class="replaceable"><code>client.ip.address</code></em>(ro,no_root_squash) </code>
	</div><div class="para">
		To export to all systems use an entry such as:
	</div><div class="para">
		<code class="command"><em class="replaceable"><code>/publicly/available/directory</code></em> *(ro,no_root_squash) </code>
	</div><div class="para">
		Start the NFS daemon (on a Fedora system, use <code class="command">/sbin/service nfs start</code>). If NFS is already running, reload the configuration file (on a Fedora system use <code class="command">/sbin/service nfs reload</code>).
	</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-steps-network-installs-x86.html"><strong>Prev</strong>3.5.Â Preparing for a Network Installation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch03s06.html"><strong>Next</strong>3.6.Â Preparing for a Hard Drive Installation</a></li></ul></body></html>


--- NEW FILE ch03s06.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.6.Â Preparing for a Hard Drive Installation</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-steps-x86.html" title="ChapterÂ 3.Â Steps to Get You Started" /><link rel="prev" href="ch03s05s02.html" title="3.5.2.Â Preparing for an NFS install" /><link rel="next" href="ch-ent-table.html" title="ChapterÂ 4.Â System Specifications List" /></head><body class="draft "><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="Documen
 tation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s05s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-ent-table.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="id854648">3.6.Â Preparing for a Hard Drive Installation</h2></div></div></div><a id="id854656" class="indexterm"></a><a id="id854346" class="indexterm"></a><div class="para">
	Hard drive installations require the use of the ISO (or DVD/CD-ROM) images. An ISO image is a file containing an exact copy of a DVD/CD-ROM image. After placing the required ISO images (the binary Fedora DVD/CD-ROMs) in a directory, choose to install from the hard drive. You can then point the installation program at that directory to perform the installation.
</div><div class="para">
	To prepare your system for a hard drive installation, you must set the system up in one of the following ways:
</div><div class="itemizedlist"><ul><li><div class="para">
	Using a set of CD-ROMs, or a DVD â€” Create ISO image files from each installation CD-ROM, or from the DVD. For each CD-ROM (once for the DVD), execute the following command on a Linux system: 
<pre class="screen">
<code class="command">dd if=/dev/cdrom of=/tmp/<em class="replaceable"><code>file-name</code></em>.iso</code>
</pre>
</div></li><li><div class="para">
	Using ISO images â€” transfer these images to the system to be installed.
</div><div class="para">
	Verifying that ISO images are intact before you attempt an installation, helps to avoid problems. To verify the ISO images are intact prior to performing an installation, use an <code class="command">md5sum</code> program (many <code class="command">md5sum</code> programs are available for various operating systems). An <code class="command">md5sum</code> program should be available on the same Linux machine as the ISO images.
</div></li></ul></div><a id="id837867" class="indexterm"></a><a id="id823760" class="indexterm"></a><a id="id823777" class="indexterm"></a><div class="note"><h2>Note</h2><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 CDs). 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 class="para">
	Additionally, if a file called <code class="filename">updates.img</code> exists in the location from which you install, it is used for updates to <code class="filename">anaconda</code>, the installation program. Refer to the file <code class="filename">install-methods.txt</code> in the <code class="filename">anaconda</code> RPM package for detailed information on the various ways to install Fedora, as well as how to apply the installation program updates.
</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s05s02.html"><strong>Prev</strong>3.5.2.Â Preparing for an NFS install</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-ent-table.html"><strong>Next</strong>ChapterÂ 4.Â System Specifications List</a></li></ul></body></html>


--- NEW FILE ch05s02.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.2.Â So What Is Driver Media Anyway?</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-driverdisk-x86.html" title="ChapterÂ 5.Â Driver Media for Intel and AMD Systems" /><link rel="prev" href="ch-driverdisk-x86.html" title="ChapterÂ 5.Â Driver Media for Intel and AMD Systems" /><link rel="next" href="ch05s03.html" title="5.3.Â How Do I Obtain Driver Media?" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-driverdisk-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch05s03.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="id810647">5.2.Â So What Is Driver Media Anyway?</h2></div></div></div><div class="para">
		Driver media can add support for hardware that may or may not be supported by the installation program. Driver media could include a driver diskette or image produced by Red Hat, it could be a diskette or CD-ROM you make yourself from driver images found on the Internet, or it could be a diskette or CD-ROM that a hardware vendor includes with a piece of hardware.
	</div><div class="para">
		Driver media is used if you need access to a particular device to install Fedora. Drivers can be used for  non-standard,  very new,  or uncommon devices.
	</div><div class="note"><h2>Note</h2><div class="para">
			If an unsupported device is not needed to install Fedora on your system, continue with the installation and add support for the new piece of hardware once the installation is complete.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-driverdisk-x86.html"><strong>Prev</strong>ChapterÂ 5.Â Driver Media for Intel and AMD Systems</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch05s03.html"><strong>Next</strong>5.3.Â How Do I Obtain Driver Media?</a></li></ul></body></html>


--- NEW FILE ch05s03.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.3.Â How Do I Obtain Driver Media?</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-driverdisk-x86.html" title="ChapterÂ 5.Â Driver Media for Intel and AMD Systems" /><link rel="prev" href="ch05s02.html" title="5.2.Â So What Is Driver Media Anyway?" /><link rel="next" href="ch05s04.html" title="5.4.Â Using a Driver Image During Installation" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch05s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch05s04.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="id834812">5.3.Â How Do I Obtain Driver Media?</h2></div></div></div><a id="id808127" class="indexterm"></a><div class="para">
	Driver images may be available from a hardware or software vendor's website. If you suspect that your system may require one of these drivers, you should create a driver diskette or CD-ROM before beginning your Fedora installation.
</div><div class="note"><h2>Note</h2><div class="para">
		It is also possible to use a driver image via a network file. Instead of using the <code class="command">linux dd</code> boot command, use the <code class="command">linux dd=<em class="replaceable"><code>url</code></em></code> command, where <em class="replaceable"><code>url</code></em> is replaced by an HTTP, FTP, or NFS address of the driver image to be used.
	</div></div><a id="id867878" class="indexterm"></a><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id806929">5.3.1.Â Creating a Driver Diskette from an Image File</h3></div></div></div><a id="id806935" class="indexterm"></a><div class="para">
				To create a driver diskette from a driver diskette image using Linux:
			</div><div class="orderedlist"><ol><li><div class="para">
						Insert a blank, formatted diskette  into the first diskette drive.
					</div></li><li><div class="para">
						From the same directory containing the driver diskette image, such as <code class="filename"><em class="replaceable"><code>drvnet.img</code></em></code>, type <code class="command">dd if=<em class="replaceable"><code>drvnet.img</code></em> of=/dev/fd0</code> as root.
					</div></li></ol></div><div class="note"><h2>Note</h2><a id="id841843" class="indexterm"></a><div class="para">
					The installation program supports using an external flash drive as a way to add driver images during the installation process. The best way to do this is to mount the flash drive and copy the desired <code class="filename">driverdisk.img</code> onto the flash drive. For example:
				</div><pre class="screen">dd if=driverdisk.img of=/dev/sda
</pre><div class="para">
					You are then prompted during the installation to select the partition and specify the file to be used.
				</div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch05s02.html"><strong>Prev</strong>5.2.Â So What Is Driver Media Anyway?</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch05s04.html"><strong>Next</strong>5.4.Â Using a Driver Image During Installation</a></li></ul></body></html>


--- NEW FILE ch05s04.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.4.Â Using a Driver Image During Installation</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-driverdisk-x86.html" title="ChapterÂ 5.Â Driver Media for Intel and AMD Systems" /><link rel="prev" href="ch05s03.html" title="5.3.Â How Do I Obtain Driver Media?" /><link rel="next" href="pt-The_installation_process.html" title="PartÂ II.Â The installation process" /></head><body class="draft "><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/im
 age_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch05s03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="pt-The_installation_process.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="id806945">5.4.Â Using a Driver Image During Installation</h2></div></div></div><a id="id806950" class="indexterm"></a><div class="para">
	If you need to use a driver image, such as during a PCMCIA device or NFS installation, the installation program prompts you to insert the driver (as a diskette, CD-ROM, or file name) when it is needed.
</div><div class="para">
			For example, to specifically load a driver diskette that you have created, begin the installation process by booting from the Fedora DVD (or using boot media you have created). For x86-based systems, at the <code class="prompt">boot:</code> prompt, enter <strong class="userinput"><code>linux dd</code></strong> if using an x86 or x86-64 system. Refer to <a class="xref" href="s1-x86-starting.html#s2-x86-starting-booting" title="7.3.1.Â Booting the Installation Program on x86, AMD64, and Intel 64 Systems">SectionÂ 7.3.1, â€œBooting the Installation Program on x86, AMD64, and Intel 64 Systemsâ€</a> for details on booting the installation program. 
		</div><div class="para">
	The installation program asks you to insert the driver diskette. Once the driver diskette is read by the installation program, it can apply those drivers to hardware discovered on your system later in the installation process.
</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch05s03.html"><strong>Prev</strong>5.3.Â How Do I Obtain Driver Media?</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="pt-The_installation_process.html"><strong>Next</strong>PartÂ II.Â The installation process</a></li></ul></body></html>


--- NEW FILE ch07s12.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.12.Â Keyboard Configuration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="s1-langselection-x86.html" title="7.11.Â Language Selection" /><link rel="next" href="sn-initialize-hdd.html" title="7.13.Â Initializing the Hard Disk" /></head><body class="draft "><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="Documentatio
 n Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-langselection-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-initialize-hdd.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="id839221">7.12.Â Keyboard Configuration</h2></div></div></div><a id="id885826" class="indexterm"></a><a id="id908884" 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.
</div><div class="figure" id="id836859"><div class="figure-contents"><div class="mediaobject"><img src="images/kbdconfig/keyboard.png" alt="Keyboard Configuration" /><div class="longdesc"><div class="para">
					Keyboard configuration screen
				</div></div></div></div><h6>FigureÂ 7.8.Â Keyboard Configuration</h6></div><br class="figure-break" /><div class="note"><h2>Note</h2><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-langselection-x86.html"><strong>Prev</strong>7.11.Â Language Selection</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-initialize-hdd.html"><strong>Next</strong>7.13.Â Initializing the Hard Disk</a></li></ul></body></html>


--- NEW FILE ch07s21s03.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.21.3.Â Partition Fields</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-diskpartitioning-x86.html" title="7.21.Â Partitioning Your System" /><link rel="prev" href="s2-diskpartitioning-dd-x86.html" title="7.21.2.Â The partitioning screen" /><link rel="next" href="s2-diskpartrecommend-x86.html" title="7.21.4.Â Recommended Partitioning Scheme" /></head><body class="draft "><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" al
 t="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-diskpartitioning-dd-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-diskpartrecommend-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id914091">7.21.3.Â Partition Fields</h3></div></div></div><div class="para">
		Above the partition hierarchy are labels which present information about the partitions you are creating. The labels are defined as follows:
	</div><div class="itemizedlist"><ul><li><div class="para">
				<span class="guilabel"><strong>Device</strong></span>: This field displays the partition's device name.
			</div></li><li><div class="para">
				<span class="guilabel"><strong>Mount Point/RAID/Volume</strong></span>: A mount point is the location within the directory hierarchy at which a volume exists; the volume is "mounted" at this location. This field indicates where the partition is mounted. If a partition exists, but is not set, then you need to define its mount point. Double-click on the partition or click the <span class="guibutton"><strong>Edit</strong></span> button.
			</div></li><li><div class="para">
				<span class="guilabel"><strong>Type</strong></span>: This field shows the partition's file system type (for example, ext2, ext3, ext4, or vfat).
			</div></li><li><div class="para">
				<span class="guilabel"><strong>Format</strong></span>: This field shows if the partition being created will be formatted.
			</div></li><li><div class="para">
				<span class="guilabel"><strong>Size (MB)</strong></span>: This field shows the partition's size (in MB).
			</div></li><li><div class="para">
				<span class="guilabel"><strong>Start</strong></span>: This field shows the cylinder on your hard drive where the partition begins.
			</div></li><li><div class="para">
				<span class="guilabel"><strong>End</strong></span>: This field shows the cylinder on your hard drive where the partition ends.
			</div></li></ul></div><div class="para">
		<span class="guilabel"><strong>Hide RAID device/LVM Volume Group members</strong></span>: Select this option if you do not want to view any RAID device or LVM Volume Group members that have been created.
	</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-diskpartitioning-dd-x86.html"><strong>Prev</strong>7.21.2.Â The partitioning screen</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-diskpartrecommend-x86.html"><strong>Next</strong>7.21.4.Â Recommended Partitioning Scheme</a></li></ul></body></html>


--- NEW FILE ch07s21s05.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.21.5.Â Adding Partitions</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-diskpartitioning-x86.html" title="7.21.Â Partitioning Your System" /><link rel="prev" href="s2-diskpartrecommend-x86.html" title="7.21.4.Â Recommended Partitioning Scheme" /><link rel="next" href="ch07s21s06.html" title="7.21.6.Â Editing Partitions" /></head><body class="draft "><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 Sit
 e" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-diskpartrecommend-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch07s21s06.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id928191">7.21.5.Â Adding Partitions</h3></div></div></div><a id="id877067" class="indexterm"></a><a id="id926623" class="indexterm"></a><a id="id800430" class="indexterm"></a><div class="para">
		To add a new partition, select the <span class="guibutton"><strong>New</strong></span> button. A dialog box appears (refer to <a class="xref" href="ch07s21s05.html#fig-diskpartitioning-part-add-x86" title="FigureÂ 7.24.Â Creating a New Partition">FigureÂ 7.24, â€œCreating a New Partitionâ€</a>).
	</div><div class="note"><h2>Note</h2><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.html" title="AppendixÂ A.Â An Introduction to Disk Partitions">AppendixÂ A, <i>An Introduction to Disk Partitions</i></a>.
		</div></div><div class="figure" id="fig-diskpartitioning-part-add-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/diskpartitioning/part-add.png" alt="Creating a New Partition" /><div class="longdesc"><div class="para">
					Creating a new partition.
				</div></div></div></div><h6>FigureÂ 7.24.Â Creating a New Partition</h6></div><br class="figure-break" /><div class="itemizedlist"><ul><li><div class="para">
		<span class="guilabel"><strong>Mount Point</strong></span>: Enter the partition's mount point. For example, if this partition should be the root partition, enter <strong class="userinput"><code>/</code></strong>; enter <strong class="userinput"><code>/boot</code></strong> for the <code class="filename">/boot</code> partition, and so on. You can also use the pull-down menu to choose the correct mount point for your partition. For a swap partition the mount point should not be set - setting the filesystem type to swap is sufficient.
	</div></li><li><div class="para">
				<span class="guilabel"><strong>File System Type</strong></span>: Using the pull-down menu, select the appropriate file system type for this partition. For more information on file system types, refer to <a class="xref" href="ch07s21s05.html#s3-diskpartitioning-file-x86" title="7.21.5.1.Â File System Types">SectionÂ 7.21.5.1, â€œFile System Typesâ€</a>.
			</div></li><li><div class="para">
		<span class="guilabel"><strong>Allowable Drives</strong></span>: This field contains a list of the hard disks installed on your system. If a hard disk's box is highlighted, then a desired partition can be created on that hard disk. If the box is <span class="emphasis"><em>not</em></span> checked, then the partition will <span class="emphasis"><em>never</em></span> be created on that hard disk. By using different checkbox settings, you can have <span class="application"><strong>anaconda</strong></span> place partitions where you need them, or let <span class="application"><strong>anaconda</strong></span> decide where partitions should go.
	</div></li><li><div class="para">
		<span class="guilabel"><strong>Size (MB)</strong></span>: Enter the size (in megabytes) of the partition. Note, this field starts with 100 MB; unless changed, only a 100 MB partition will be created.
	</div></li><li><div class="para">
		<span class="guilabel"><strong>Additional Size Options</strong></span>: Choose whether to keep this partition at a fixed size, to allow it to "grow" (fill up the available hard drive space) to a certain point, or to allow it to grow to fill any remaining hard drive space available.
	</div><div class="para">
		If you choose <span class="guilabel"><strong>Fill all space up to (MB)</strong></span>, you must give size constraints in the field to the right of this option. This allows you to keep a certain amount of space free on your hard drive for future use.
	</div></li><li><div class="para">
				<span class="guilabel"><strong>Force to be a primary partition</strong></span>: Select whether the partition you are creating should be one of the first four partitions on the hard drive. If unselected, the partition is created as a logical partition. Refer to <a class="xref" href="ch-partitions-x86.html#s2-partitions-overview-extended-x86" title="A.1.3.Â Partitions within Partitions â€” An Overview of Extended Partitions">SectionÂ A.1.3, â€œPartitions within Partitions â€” An Overview of Extended Partitionsâ€</a>, for more information.
			</div></li><li><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><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" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="s3-diskpartitioning-file-x86">7.21.5.1.Â File System Types</h4></div></div></div><a id="id817492" class="indexterm"></a><a id="id886522" class="indexterm"></a><a id="id832734" class="indexterm"></a><a id="id938034" class="indexterm"></a><div class="para">
	Fedora allows you to create different partition types, based on the file system they will use. The following is a brief description of the different file systems available, and how they can be utilized.
</div><div class="itemizedlist"><ul><li><div class="para">
		<span class="guilabel"><strong>Btrfs</strong></span> â€” Btrfs is under development as a file system capable of addressing and managing more files, larger files, and larger volumes than the ext2, ext3, and ext4 file systems. Btrfs is designed to make the file system tolerant of errors, and to facilitate the detection and repair of errors when they occur. It uses checksums to ensure the validity of data and metadata, and maintains snapshots of the file system that can be used for backup or repair.
	</div><div class="para">
		Because Btrfs is still experimental and under development, the installation program does not offer it by default. If you want to create a Btrfs partition on a drive, you must commence the installation process with the boot option <code class="command"> icantbelieveitsnotbtr</code>. Refer to <a class="xref" href="ap-admin-options.html" title="ChapterÂ 9.Â Boot Options">ChapterÂ 9, <i>Boot Options</i></a> for instructions.
	</div><div class="warning"><h2>Btrfs is still experimental</h2><div class="para">
			Fedora 11 includes Btrfs as a technology preview to allow you to experiment with this file system. You should not choose Btrfs for partitions that will contain valuable data or that are essential for the operation of important systems.
		</div></div></li><li><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><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="id856182" href="#ftn.id856182" class="footnote">3</a>]</sup> the file system.
	</div></li><li><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 journalling. The ext4 file system is selected by default and is highly recommended.
	</div></li><li><div class="para">
		<span class="guilabel"><strong>physical volume (LVM)</strong></span> â€” Creating one or more physical volume (LVM) partitions allows you to create an LVM logical volume. LVM can improve performance when using physical disks. 
	</div></li><li><div class="para">
		<span class="guilabel"><strong>software RAID</strong></span> â€” Creating two or more software RAID partitions allows you to create a RAID device. 
	</div></li><li><div class="para">
		<span class="guilabel"><strong>swap</strong></span> â€” Swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing. 
	</div></li><li><div class="para">
		<span class="guilabel"><strong>vfat</strong></span> â€” The VFAT file system is a Linux file system that is compatible with Microsoft Windows long filenames on the FAT file system. This file system must be used for the <code class="filename">/boot/efi/</code> partition on Itanium systems.
	</div></li></ul></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id856182" href="#id856182" 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.
		</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-diskpartrecommend-x86.html"><strong>Prev</strong>7.21.4.Â Recommended Partitioning Scheme</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch07s21s06.html"><strong>Next</strong>7.21.6.Â Editing Partitions</a></li></ul></body></html>


--- NEW FILE ch07s21s06.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.21.6.Â Editing Partitions</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-diskpartitioning-x86.html" title="7.21.Â Partitioning Your System" /><link rel="prev" href="ch07s21s05.html" title="7.21.5.Â Adding Partitions" /><link rel="next" href="s2-diskpartdelete-x86.html" title="7.21.7.Â Deleting a Partition" /></head><body class="draft "><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><
 ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s21s05.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-diskpartdelete-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id832705">7.21.6.Â Editing Partitions</h3></div></div></div><a id="id914401" class="indexterm"></a><a id="id832599" class="indexterm"></a><div class="para">
		To edit a partition, select the <span class="guibutton"><strong>Edit</strong></span> button or double-click on the existing partition.
	</div><div class="note"><h2>Note</h2><div class="para">
			If the partition already exists on your disk, you can only change the partition's mount point. To make any other changes, you must delete the partition and recreate it.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s21s05.html"><strong>Prev</strong>7.21.5.Â Adding Partitions</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-diskpartdelete-x86.html"><strong>Next</strong>7.21.7.Â Deleting a Partition</a></li></ul></body></html>


--- NEW FILE ch08s02.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2.Â Trouble Beginning the Installation</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-trouble-x86.html" title="ChapterÂ 8.Â Troubleshooting Installation on an Intel or AMD System" /><link rel="prev" href="ch-trouble-x86.html" title="ChapterÂ 8.Â Troubleshooting Installation on an Intel or AMD System" /><link rel="next" href="s1-trouble-install-x86.html" title="8.3.Â Trouble During the Installation" /></head><body class="draft "><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.fedoraproj
 ect.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-trouble-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-trouble-install-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="id832256">8.2.Â Trouble Beginning the Installation</h2></div></div></div><a id="id874552" class="indexterm"></a><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id914845">8.2.1.Â Problems with Booting into the Graphical Installation</h3></div></div></div><a id="id968077" class="indexterm"></a><a id="id965692" 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 try using 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, it should be reported as a bug as the installer has failed to autodetect your videocard. Refer to <a class="xref" href="ap-admin-options.html" title="ChapterÂ 9.Â Boot Options">ChapterÂ 9, <i>Boot Options</i></a> for more information on boot options.
			</div><div class="note"><h2>Note</h2><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-trouble-x86.html"><strong>Prev</strong>ChapterÂ 8.Â Troubleshooting Installation on an Int...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-trouble-install-x86.html"><strong>Next</strong>8.3.Â Trouble During the Installation</a></li></ul></body></html>


--- NEW FILE ch08s03s06.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.3.6.Â Are You Seeing Python Errors?</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-trouble-install-x86.html" title="8.3.Â Trouble During the Installation" /><link rel="prev" href="s2-trouble-completeparts-x86.html" title="8.3.5.Â Other Partitioning Problems" /><link rel="next" href="ch08s04.html" title="8.4.Â Problems After Installation" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-trouble-completeparts-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch08s04.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id810224">8.3.6.Â Are You Seeing Python Errors?</h3></div></div></div><a id="id811177" class="indexterm"></a><div class="para">
		During some upgrades or installations of Fedora, the installation program (also known as <span class="application"><strong>anaconda</strong></span>) may fail with a Python or traceback error. This error may occur after the selection of individual packages or while trying to save the upgrade log in the <code class="filename">/tmp/</code>directory. The error may look similar to:
	</div><pre class="screen">
Traceback (innermost last):
File "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/progress_gui.py", line 20, in run
rc = self.todo.doInstall ()    
File "/var/tmp/anaconda-7.1//usr/lib/anaconda/todo.py", line 1468, in doInstall 
self.fstab.savePartitions ()    
File "fstab.py", line 221, in savePartitions      
sys.exit(0)  
SystemExit: 0   
Local variables in innermost frame:  
self: <fstab.GuiFstab instance at 8446fe0>  
sys: <module 'sys' (built-in)>  
ToDo object:  (itodo  ToDo  p1  (dp2  S'method'  p3  (iimage  CdromInstallMethod  
p4  (dp5  S'progressWindow'  p6   <failed>
</pre><div class="para">
		This error occurs in some systems where links to <code class="filename">/tmp/</code> are symbolic to other locations or have been changed since creation. These symbolic or changed links are invalid during the installation process, so the installation program cannot write information and fails.
	</div><div class="para">
		If you experience such an error, first try to download any available updates for <span class="application"><strong>anaconda</strong></span>. Updates for <span class="application"><strong>anaconda</strong></span> and instructions for using them can be found at:
	</div><pre class="screen">
<a href="http://fedoraproject.org/wiki/Anaconda/Updates">http://fedoraproject.org/wiki/Anaconda/Updates</a>
</pre><div class="para">
		The <span class="application"><strong>anaconda</strong></span> website may also be a useful reference and can be found online at:
	</div><pre class="screen">
<a href="http://fedoraproject.org/wiki/Anaconda">http://fedoraproject.org/wiki/Anaconda</a>
</pre><div class="para">
		You can also search for bug reports related to this problem. To search Red Hat's bug tracking system, go to:
	</div><pre class="screen">
<a href="http://bugzilla.redhat.com/bugzilla/">http://bugzilla.redhat.com/bugzilla/</a>
</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-trouble-completeparts-x86.html"><strong>Prev</strong>8.3.5.Â Other Partitioning Problems</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch08s04.html"><strong>Next</strong>8.4.Â Problems After Installation</a></li></ul></body></html>


--- NEW FILE ch08s04.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.4.Â Problems After Installation</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-trouble-x86.html" title="ChapterÂ 8.Â Troubleshooting Installation on an Intel or AMD System" /><link rel="prev" href="ch08s03s06.html" title="8.3.6.Â Are You Seeing Python Errors?" /><link rel="next" href="ch08s04s02.html" title="8.4.2.Â Booting into a Graphical Environment" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s03s06.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch08s04s02.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="id970233">8.4.Â Problems After Installation</h2></div></div></div><a id="id800019" class="indexterm"></a><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-trouble-grub">8.4.1.Â Trouble With the Graphical GRUB Screen on an x86-based System?</h3></div></div></div><a id="id829487" 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.
	</div><div class="para">
		Press <span class="keycap"><strong>Enter</strong></span> to exit the editing mode.
	</div><div class="para">
		Once the boot loader screen has returned, type <code class="command">b</code> to boot the system.
	</div><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s03s06.html"><strong>Prev</strong>8.3.6.Â Are You Seeing Python Errors?</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch08s04s02.html"><strong>Next</strong>8.4.2.Â Booting into a Graphical Environment</a></li></ul></body></html>


--- NEW FILE ch08s04s02.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.4.2.Â Booting into a Graphical Environment</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch08s04.html" title="8.4.Â Problems After Installation" /><link rel="prev" href="ch08s04.html" title="8.4.Â Problems After Installation" /><link rel="next" href="ch08s04s03.html" title="8.4.3.Â Problems with the X Window System (GUI)" /></head><body class="draft "><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 Sit
 e" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s04.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch08s04s03.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id830557">8.4.2.Â Booting into a Graphical Environment</h3></div></div></div><a id="id815489" class="indexterm"></a><a id="id816467" class="indexterm"></a><a id="id847936" 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.
</div><div class="para">
	Note, however, that this is just a one-time fix and does not change the log in process for future log ins.
</div><div class="para">
	To set up your system so that you can log in at a graphical login screen, you must edit one file, <code class="filename">/etc/inittab</code>, by changing just one number in the runlevel section. When you are finished, reboot the computer. The next time you log in, you are presented with a graphical login prompt.
</div><div class="para">
	Open a shell prompt. If you are in your user account, become root by typing the <code class="command">su</code> command.
</div><div class="para">
	Now, type <code class="command">gedit /etc/inittab</code> to edit the file with <span class="application"><strong>gedit</strong></span>. The file <code class="filename">/etc/inittab</code> opens. Within the first screen, a section of the file which looks like the following appears:
</div><pre class="screen"># Default runlevel. The runlevels used are: 
#   0 - halt (Do NOT set initdefault to this) 
#   1 - Single user mode 
#   2 - Multiuser, without NFS (The same as 3, if you do not have networking) 
#   3 - Full multiuser mode 
#   4 - unused 
#   5 - X11 
#   6 - reboot (Do NOT set initdefault to this) 
#  id:3:initdefault:
</pre><div class="para">
	To change from a console to a graphical login, you should change the number in the line <code class="computeroutput">id:3:initdefault:</code> from a <code class="computeroutput">3</code> to a <code class="computeroutput">5</code>.
</div><div class="warning"><h2>Warning</h2><div class="para">
		Change <span class="emphasis"><em>only</em></span> the number of the default runlevel from <code class="filename">3</code> to <code class="filename">5</code>.
	</div></div><div class="para">
	Your changed line should look like the following:
</div><pre class="screen">
	<code class="computeroutput"> id:5:initdefault: </code>
</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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s04.html"><strong>Prev</strong>8.4.Â Problems After Installation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch08s04s03.html"><strong>Next</strong>8.4.3.Â Problems with the X Window System (GUI)</a></li></ul></body></html>


--- NEW FILE ch08s04s03.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.4.3.Â Problems with the X Window System (GUI)</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch08s04.html" title="8.4.Â Problems After Installation" /><link rel="prev" href="ch08s04s02.html" title="8.4.2.Â Booting into a Graphical Environment" /><link rel="next" href="ch08s04s04.html" title="8.4.4.Â Problems with the X Server Crashing and Non-Root Users" /></head><body class="draft "><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_r
 ight.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s04s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch08s04s04.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id892393">8.4.3.Â Problems with the X Window System (GUI)</h3></div></div></div><a id="id787853" class="indexterm"></a><div class="para">
		If you are having trouble getting X (the X Window System) to start, you may not have installed it during your installation.
	</div><div class="para">
		If you want X, you can either install the packages from the Fedora installation media or perform an upgrade.
	</div><div class="para">
		If you elect to upgrade, select the X Window System packages, and choose GNOME, KDE, or both, during the upgrade package selection process.
	</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s04s02.html"><strong>Prev</strong>8.4.2.Â Booting into a Graphical Environment</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch08s04s04.html"><strong>Next</strong>8.4.4.Â Problems with the X Server Crashing and No...</a></li></ul></body></html>


--- NEW FILE ch08s04s04.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.4.4.Â Problems with the X Server Crashing and Non-Root Users</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch08s04.html" title="8.4.Â Problems After Installation" /><link rel="prev" href="ch08s04s03.html" title="8.4.3.Â Problems with the X Window System (GUI)" /><link rel="next" href="ch08s04s05.html" title="8.4.5.Â Problems When You Try to Log In" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s04s03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch08s04s05.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id868582">8.4.4.Â Problems with the X Server Crashing and Non-Root Users</h3></div></div></div><a id="id852273" class="indexterm"></a><div class="para">
		If you are having trouble with the X server crashing when anyone other than root 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:
	</div><pre class="screen">df -h
</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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s04s03.html"><strong>Prev</strong>8.4.3.Â Problems with the X Window System (GUI)</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch08s04s05.html"><strong>Next</strong>8.4.5.Â Problems When You Try to Log In</a></li></ul></body></html>


--- NEW FILE ch08s04s05.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.4.5.Â Problems When You Try to Log In</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch08s04.html" title="8.4.Â Problems After Installation" /><link rel="prev" href="ch08s04s04.html" title="8.4.4.Â Problems with the X Server Crashing and Non-Root Users" /><link rel="next" href="s2-trouble-ram.html" title="8.4.6.Â Is Your RAM Not Being Recognized?" /></head><body class="draft "><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.pn
 g" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s04s04.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-trouble-ram.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id801708">8.4.5.Â Problems When You Try to Log In</h3></div></div></div><a id="id848920" class="indexterm"></a><div class="para">
	If you did not create a user account in the <span class="application"><strong>firstboot</strong></span> screens, 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>.
</div><div class="para">
	If you are using an x86-based system and GRUB is your installed boot loader, type <code class="command">e</code> for edit when the GRUB boot screen has loaded. You are presented with a list of items in the configuration file for the boot label you have selected.
</div><div class="para">
	Choose the line that starts with <code class="filename">kernel</code> and type <code class="command">e</code> to edit this boot entry.
</div><div class="para">
	At the end of the <code class="filename">kernel</code> line, add:
</div><pre class="screen">
	<strong class="userinput"><code>single</code></strong>
</pre><div class="para">
	Press <span class="keycap"><strong>Enter</strong></span> to exit edit mode.
</div><div class="para">
	Once the boot loader screen has returned, type <code class="command">b</code> to boot the system.
</div><div class="para">
	Once you have booted into single user mode and have access to the <code class="prompt">#</code> prompt, you must type <code class="command">passwd root</code>, which allows you to enter a new password for root. At this point you can type <code class="command">shutdown -r now</code> to reboot the system with the new root password.
</div><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. Linuxquestions.org maintains a Hardware Compatibility List at:
</div><pre class="screen">
	<a href="http://www.linuxquestions.org/hcl/index.php">http://www.linuxquestions.org/hcl/index.php</a>

</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s04s04.html"><strong>Prev</strong>8.4.4.Â Problems with the X Server Crashing and No...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-trouble-ram.html"><strong>Next</strong>8.4.6.Â Is Your RAM Not Being Recognized?</a></li></ul></body></html>


--- NEW FILE ch08s04s07.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.4.7.Â Your Printer Does Not Work</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch08s04.html" title="8.4.Â Problems After Installation" /><link rel="prev" href="s2-trouble-ram.html" title="8.4.6.Â Is Your RAM Not Being Recognized?" /><link rel="next" href="s2-trouble-sound.html" title="8.4.8.Â Problems with Sound Configuration" /></head><body class="draft "><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="Documentatio
 n Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-trouble-ram.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-trouble-sound.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id845392">8.4.7.Â Your Printer Does Not Work</h3></div></div></div><a id="id929235" 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><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-trouble-ram.html"><strong>Prev</strong>8.4.6.Â Is Your RAM Not Being Recognized?</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-trouble-sound.html"><strong>Next</strong>8.4.8.Â Problems with Sound Configuration</a></li></ul></body></html>


--- NEW FILE ch08s04s09.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.4.9.Â Apache-based httpd service/Sendmail Hangs During Startup</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch08s04.html" title="8.4.Â Problems After Installation" /><link rel="prev" href="s2-trouble-sound.html" title="8.4.8.Â Problems with Sound Configuration" /><link rel="next" href="pt-Advanced_installation_options.html" title="PartÂ III.Â Advanced installation options" /></head><body class="draft "><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_C
 ontent/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-trouble-sound.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="pt-Advanced_installation_options.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id787934">8.4.9.Â Apache-based <code class="command">httpd</code> service/Sendmail Hangs During Startup</h3></div></div></div><a id="id873824" class="indexterm"></a><a id="id942700" class="indexterm"></a><div class="para">
		If you are having trouble with the Apache-based <code class="command">httpd</code> service or Sendmail hanging at 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><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-trouble-sound.html"><strong>Prev</strong>8.4.8.Â Problems with Sound Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="pt-Advanced_installation_options.html"><strong>Next</strong>PartÂ III.Â Advanced installation options</a></li></ul></body></html>


--- NEW FILE ch11s05s05.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.5.5.Â Configuring the DHCP Server</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="sn-pxe-server-manual.html" title="11.5.Â Manually configure a PXE server" /><link rel="prev" href="s1-netboot-tftp.html" title="11.5.4.Â TFTPD" /><link rel="next" href="s2-netboot-custom-msg.html" title="11.5.6.Â Adding a Custom Boot Message" /></head><body class="draft "><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 Sit
 e" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-netboot-tftp.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-netboot-custom-msg.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id871072">11.5.5.Â Configuring the DHCP Server</h3></div></div></div><a id="id871080" class="indexterm"></a><a id="id871094" class="indexterm"></a><a id="id844589" class="indexterm"></a><a id="id844603" class="indexterm"></a><div class="para">
		If a DHCP server does not already exist on the network, configure one. Refer to the Red Hat Enterprise Linux Deployment Guide for details. Make sure the configuration file contains the following so that PXE booting is enabled for systems which support it:
	</div><div class="para">
		<code class="computeroutput">allow booting; allow bootp; class "pxeclients" { match if substring(option vendor-class-identifier, 0, 9) = "PXEClient"; next-server <em class="replaceable"><code><server-ip></code></em>; filename "linux-install/pxelinux.0"; }</code>
	</div><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-netboot-tftp.html"><strong>Prev</strong>11.5.4.Â TFTPD</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-netboot-custom-msg.html"><strong>Next</strong>11.5.6.Â Adding a Custom Boot Message</a></li></ul></body></html>


--- NEW FILE ch18s02.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.2.Â Upgrading Your System</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-upgrade-x86.html" title="ChapterÂ 18.Â Upgrading Your Current System" /><link rel="prev" href="ch-upgrade-x86.html" title="ChapterÂ 18.Â Upgrading Your Current System" /><link rel="next" href="ch-x86-uninstall.html" title="ChapterÂ 19.Â Removing Fedora" /></head><body class="draft "><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="Documentati
 on Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-upgrade-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-x86-uninstall.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="id838696">18.2.Â Upgrading Your System</h2></div></div></div><div class="para">
	The <span class="guilabel"><strong>Upgrade Examine</strong></span> screen appears if you have instructed the installation program to perform an upgrade.
</div><div class="note"><h2>Note</h2><div class="para">
		If the contents of your <code class="filename">/etc/fedora-release</code> file have been changed from the default, your Fedora installation may not be found when attempting an upgrade to Fedora 11.
	</div><div class="para">
		You can relax some of the checks against this file by booting with the following boot command:
	</div><pre class="screen">linux upgradeany
</pre><div class="para">
		Use the <code class="command">linux upgradeany</code> command if your Fedora installation was not given as an option to upgrade.
	</div></div><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.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems">ChapterÂ 7, <i>Installing on Intel and AMD Systems</i></a> for further instructions.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-upgrade-x86.html"><strong>Prev</strong>ChapterÂ 18.Â Upgrading Your Current System</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-x86-uninstall.html"><strong>Next</strong>ChapterÂ 19.Â Removing Fedora</a></li></ul></body></html>


--- NEW FILE index.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Installation Guide</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><meta name="description" content="Provides documentation for the installation process." /><link rel="home" href="index.html" title="Installation Guide" /><link rel="next" href="Installation-Guide-Preface.html" title="Preface" /></head><body class="draft "><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><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" href="Installation-Guide-Pre
 face.html"><strong>Next</strong></a></li></ul><div class="book" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div class="producttitle"><span class="productname">Fedora</span> <span class="productnumber">11</span></div><div><h1 id="id738697" class="title">Installation Guide</h1></div><div><h2 class="subtitle">Installing Fedora 11 on x86, AMD64, and <span class="trademark">Intel</span>Â® 64 architectures</h2></div><p class="edition">Edition 1.0</p><div><h3 class="corpauthor">
				<span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> Logo</object></span>
			</h3></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Fedora</span> <span class="surname">Documentation Project</span></h3><code class="email"><a class="email" href="mailto:fedora-docs-list at redhat.com">fedora-docs-list at redhat.com</a></code></div></div></div><div><p class="copyright">Copyright Â© 2009 Red Hat, Inc. and others</p></div><hr /><div><div id="id816040" class="legalnotice"><h1 class="legalnotice">Legal Notice</h1><div class="para">
		Copyright <span class="trademark"></span>Â© 2009 Red Hat, Inc. and others. This material may only be distributed subject to the terms and conditions set forth in the Open Publication License, V1.0, (the latest version is presently available at <a href="http://www.opencontent.org/openpub/">http://www.opencontent.org/openpub/</a>).
	</div><div class="para">
		Fedora and the Fedora Infinity Design logo are trademarks or registered trademarks of Red Hat, Inc., in the U.S. and other countries.
	</div><div class="para">
		Red Hat and the Red Hat "Shadow Man" logo are registered trademarks of Red Hat Inc. in the United States and other countries.
	</div><div class="para">
		All other trademarks and copyrights referred to are the property of their respective owners.
	</div><div class="para">
		Documentation, as with software itself, may be subject to export control. Read about Fedora Project export controls at <a href="http://fedoraproject.org/wiki/Legal/Export">http://fedoraproject.org/wiki/Legal/Export</a>. 
	</div></div></div><div><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.html">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="Installation-Guide-Preface.html#id822194">1. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="Installation-Guide-Preface.html#id820721">1.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="Installation-Guide-Preface.html#id813569">1.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="Installation-Guide-Preface.html#id833572">1.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="section"><a href="pr01s02.html">2. We Need Feedback!</a></span></dt></dl></dd><dt><span class="preface"><a href="ch-introduction.html">Introduction</a></span></dt><dd><dl><dt><span class="secti
 on"><a href="ch-introduction.html#sn-background">1. Background</a></span></dt><dd><dl><dt><span class="section"><a href="ch-introduction.html#sn-about-fedora">1.1. About Fedora</a></span></dt><dt><span class="section"><a href="ch-introduction.html#sn-additional-help">1.2. Getting Additional Help</a></span></dt></dl></dd><dt><span class="section"><a href="sn-about-document.html">2. About This Document</a></span></dt><dd><dl><dt><span class="section"><a href="sn-about-document.html#sn-goals">2.1. Goals</a></span></dt><dt><span class="section"><a href="sn-audience.html">2.2. Audience</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-experts-quickstart.html">1. Quick Start for Experts</a></span></dt><dd><dl><dt><span class="section"><a href="ch-experts-quickstart.html#sn-expert-overview">1.1. Overview</a></span></dt><dt><span class="section"><a href="sn-expert-download.html">1.2. Download Files</a></span></dt><dt><span class="section"><a href="sn-expert-pr
 epare.html">1.3. Prepare for Installation</a></span></dt><dt><span class="section"><a href="sn-expert-install.html">1.4. Install Fedora</a></span></dt><dt><span class="section"><a href="sn-expert-post-install.html">1.5. Perform Post-installation Steps</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-new-users.html">2. New Users</a></span></dt><dd><dl><dt><span class="section"><a href="ch-new-users.html#sn-howto-download">2.1. How Do I Download Installation Files?</a></span></dt><dd><dl><dt><span class="section"><a href="ch-new-users.html#sn-which-download-mirror">2.1.1. From a Mirror</a></span></dt><dt><span class="section"><a href="ch-new-users.html#sn-which-download-bt">2.1.2. From BitTorrent</a></span></dt></dl></dd><dt><span class="section"><a href="sn-which-arch.html">2.2. Which Architecture Is My Computer?</a></span></dt><dt><span class="section"><a href="sn-which-files.html">2.3. Which Files Do I Download?</a></span></dt><dt><span class="section"><a href
 ="sn-making-media.html">2.4. How Do I Make Fedora Media?</a></span></dt><dd><dl><dt><span class="section"><a href="sn-making-media.html#sn-making-disc-media">2.4.1. Making CD or DVD Discs</a></span></dt><dt><span class="section"><a href="ch02s04s02.html">2.4.2. Making USB Media</a></span></dt></dl></dd><dt><span class="section"><a href="sn-cannot-download.html">2.5. What If I Cannot Download Fedora?</a></span></dt><dt><span class="section"><a href="sn-start-installation.html">2.6. How Do I Start the Installation Program?</a></span></dt></dl></dd><dt><span class="part"><a href="pt-Before_you_begin.html">I. Before you begin</a></span></dt><dd><dl><dt><span class="chapter"><a href="ch-steps-x86.html">3. Steps to Get You Started</a></span></dt><dd><dl><dt><span class="section"><a href="ch-steps-x86.html#id787237">3.1. Upgrade or Install?</a></span></dt><dt><span class="section"><a href="sn-Is_Your_Hardware_Compatible-x86.html">3.2. Is Your Hardware Compatible?</a></span></dt><dt
 ><span class="section"><a href="ch03s03.html">3.3. Do You Have Enough Disk Space?</a></span></dt><dt><span class="section"><a href="ch03s04.html">3.4. Can You Install Using the CD-ROM or DVD?</a></span></dt><dd><dl><dt><span class="section"><a href="ch03s04.html#id825179">3.4.1. Alternative Boot Methods</a></span></dt><dt><span class="section"><a href="s2-steps-make-cd.html">3.4.2. Making an Installation Boot CD-ROM</a></span></dt></dl></dd><dt><span class="section"><a href="s1-steps-network-installs-x86.html">3.5. Preparing for a Network Installation</a></span></dt><dd><dl><dt><span class="section"><a href="s1-steps-network-installs-x86.html#id799943">3.5.1. Preparing for FTP and HTTP installation</a></span></dt><dt><span class="section"><a href="ch03s05s02.html">3.5.2. Preparing for an NFS install</a></span></dt></dl></dd><dt><span class="section"><a href="ch03s06.html">3.6. Preparing for a Hard Drive Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href=
 "ch-ent-table.html">4. System Specifications List</a></span></dt><dt><span class="chapter"><a href="ch-driverdisk-x86.html">5. Driver Media for Intel and AMD Systems</a></span></dt><dd><dl><dt><span class="section"><a href="ch-driverdisk-x86.html#id808556">5.1. Why Do I Need Driver Media?</a></span></dt><dt><span class="section"><a href="ch05s02.html">5.2. So What Is Driver Media Anyway?</a></span></dt><dt><span class="section"><a href="ch05s03.html">5.3. How Do I Obtain Driver Media?</a></span></dt><dd><dl><dt><span class="section"><a href="ch05s03.html#id806929">5.3.1. Creating a Driver Diskette from an Image File</a></span></dt></dl></dd><dt><span class="section"><a href="ch05s04.html">5.4. Using a Driver Image During Installation</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="pt-The_installation_process.html">II. The installation process</a></span></dt><dd><dl><dt><span class="chapter"><a href="ch-beginninginstallation.html">6. Beginning the Installat
 ion</a></span></dt><dd><dl><dt><span class="section"><a href="ch-beginninginstallation.html#sn-boot-menu">6.1. The Boot Menu</a></span></dt><dt><span class="section"><a href="sn-install-diff-source.html">6.2. Installing from a Different Source</a></span></dt><dt><span class="section"><a href="sn-verifying-media.html">6.3. Verifying Media</a></span></dt><dd><dl><dt><span class="section"><a href="sn-verifying-media.html#sn-verifying-livecd">6.3.1. Verifying the Live CD</a></span></dt><dt><span class="section"><a href="sn-verifying-dvd.html">6.3.2. Verifying the DVD</a></span></dt></dl></dd><dt><span class="section"><a href="sn-booting-from-pxe.html">6.4. Booting from the Network using PXE</a></span></dt><dt><span class="section"><a href="sn-graphics-problem.html">6.5. Graphical and Text Interfaces</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-guimode-x86.html">7. Installing on Intel and AMD Systems</a></span></dt><dd><dl><dt><span class="section"><a href="ch-g
 uimode-x86.html#s1-guimode-interface-x86">7.1. The Graphical Installation Program User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="ch-guimode-x86.html#sn-guimode-virtual-consoles-x86">7.1.1. A Note about Virtual Consoles</a></span></dt></dl></dd><dt><span class="section"><a href="s1-guimode-textinterface-x86.html">7.2. The Text Mode Installation Program User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="s1-guimode-textinterface-x86.html#id834187">7.2.1. Using the Keyboard to Navigate</a></span></dt></dl></dd><dt><span class="section"><a href="s1-x86-starting.html">7.3. Starting the Installation Program</a></span></dt><dd><dl><dt><span class="section"><a href="s1-x86-starting.html#s2-x86-starting-booting">7.3.1. Booting the Installation Program on x86, AMD64, and Intel 64 Systems</a></span></dt><dt><span class="section"><a href="s2-x86-starting-bootopts.html">7.3.2. Additional Boot Options</a></span></dt></dl></dd><dt><span class=
 "section"><a href="s1-installmethod.html">7.4. Selecting an Installation Method</a></span></dt><dt><span class="section"><a href="s1-begininstall-cd-inst-x86.html">7.5. Installing from DVD/CD-ROM</a></span></dt><dd><dl><dt><span class="section"><a href="s1-begininstall-cd-inst-x86.html#s2-begininstall-unrec-ide-x86">7.5.1. What If the IDE CD-ROM Was Not Found?</a></span></dt></dl></dd><dt><span class="section"><a href="s1-begininstall-hd-x86.html">7.6. Installing from a Hard Drive</a></span></dt><dt><span class="section"><a href="s1-begininstall-perform-nfs-x86.html">7.7. Performing a Network Installation</a></span></dt><dt><span class="section"><a href="s1-begininstall-nfs-x86.html">7.8. Installing via NFS</a></span></dt><dt><span class="section"><a href="s1-begininstall-url-x86.html">7.9. Installing via FTP or HTTP</a></span></dt><dt><span class="section"><a href="sn-welcome-x86.html">7.10. Welcome to Fedora</a></span></dt><dt><span class="section"><a href="s1-langselectio
 n-x86.html">7.11. Language Selection</a></span></dt><dt><span class="section"><a href="ch07s12.html">7.12. Keyboard Configuration</a></span></dt><dt><span class="section"><a href="sn-initialize-hdd.html">7.13. Initializing the Hard Disk</a></span></dt><dt><span class="section"><a href="sn-upgrading-system.html">7.14. Upgrading an Existing System</a></span></dt><dd><dl><dt><span class="section"><a href="sn-upgrading-system.html#sn-upgrade-examine">7.14.1. Upgrade Examine</a></span></dt><dt><span class="section"><a href="sn-upgrade-tree.html">7.14.2. Upgrading Using the Installer</a></span></dt><dt><span class="section"><a href="sn-upgrading-bootloader.html">7.14.3. Upgrading Boot Loader Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="sn-networkconfig-fedora.html">7.15. Network Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="sn-networkconfig-fedora.html#sn-networkconfig-fedora_manual-configuration">7.15.1. Manual configuration<
 /a></span></dt></dl></dd><dt><span class="section"><a href="s1-timezone-x86.html">7.16. Time Zone Configuration</a></span></dt><dt><span class="section"><a href="sn-account_configuration.html">7.17. Set the Root Password</a></span></dt><dt><span class="section"><a href="s1-diskpartsetup-x86.html">7.18. Disk Partitioning Setup</a></span></dt><dd><dl><dt><span class="section"><a href="s1-diskpartsetup-x86.html#sn-partitioning-raid">7.18.1. RAID and Other Disk Devices</a></span></dt></dl></dd><dt><span class="section"><a href="s1-advanced-storage-x86.html">7.19.  Advanced Storage Options </a></span></dt><dt><span class="section"><a href="s1-diskpartauto-x86.html">7.20. Create Default Layout</a></span></dt><dt><span class="section"><a href="s1-diskpartitioning-x86.html">7.21. Partitioning Your System</a></span></dt><dd><dl><dt><span class="section"><a href="s1-diskpartitioning-x86.html#id888157">7.21.1. Graphical Display of Hard Drive(s)</a></span></dt><dt><span class="section">
 <a href="s2-diskpartitioning-dd-x86.html">7.21.2. The partitioning screen</a></span></dt><dt><span class="section"><a href="ch07s21s03.html">7.21.3. Partition Fields</a></span></dt><dt><span class="section"><a href="s2-diskpartrecommend-x86.html">7.21.4. Recommended Partitioning Scheme</a></span></dt><dt><span class="section"><a href="ch07s21s05.html">7.21.5. Adding Partitions</a></span></dt><dt><span class="section"><a href="ch07s21s06.html">7.21.6. Editing Partitions</a></span></dt><dt><span class="section"><a href="s2-diskpartdelete-x86.html">7.21.7. Deleting a Partition</a></span></dt></dl></dd><dt><span class="section"><a href="s1-x86-bootloader.html">7.22. x86, AMD64, and Intel 64 Boot Loader Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="s1-x86-bootloader.html#x86-bootloader-adv">7.22.1. Advanced Boot Loader Configuration</a></span></dt><dt><span class="section"><a href="s2-x86-bootloader-rescue.html">7.22.2. Rescue Mode</a></span></dt><dt><sp
 an class="section"><a href="s2-x86-bootloader-alt.html">7.22.3. Alternative Boot Loaders</a></span></dt></dl></dd><dt><span class="section"><a href="s1-pkgselection-x86.html">7.23. Package Group Selection</a></span></dt><dd><dl><dt><span class="section"><a href="s1-pkgselection-x86.html#sn-additional-repos">7.23.1. Installing from Additional Repositories</a></span></dt><dt><span class="section"><a href="sn-package-selection.html">7.23.2. Customizing the Software Selection</a></span></dt></dl></dd><dt><span class="section"><a href="s1-preparetoinstall-x86.html">7.24. Preparing to Install</a></span></dt><dd><dl><dt><span class="section"><a href="s1-preparetoinstall-x86.html#id838976">7.24.1.  Prepare to Install </a></span></dt></dl></dd><dt><span class="section"><a href="s1-installpkgs-x86.html">7.25. Installing Packages</a></span></dt><dt><span class="section"><a href="s1-complete-x86.html">7.26. Installation Complete</a></span></dt></dl></dd><dt><span class="chapter"><a href
 ="ch-trouble-x86.html">8. Troubleshooting Installation on an Intel or AMD System</a></span></dt><dd><dl><dt><span class="section"><a href="ch-trouble-x86.html#id888245">8.1. You are unable to boot Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="ch-trouble-x86.html#id842934">8.1.1. Are You Unable to Boot With Your RAID Card?</a></span></dt><dt><span class="section"><a href="ch-trouble-x86.html#id835915">8.1.2. Is Your System Displaying Signal 11 Errors?</a></span></dt></dl></dd><dt><span class="section"><a href="ch08s02.html">8.2. Trouble Beginning the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="ch08s02.html#id914845">8.2.1. Problems with Booting into the Graphical Installation</a></span></dt></dl></dd><dt><span class="section"><a href="s1-trouble-install-x86.html">8.3. Trouble During the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="s1-trouble-install-x86.html#s2-trouble-nodevicefound-x86">8.3.1. No devices
  found to install Fedora  Error Message</a></span></dt><dt><span class="section"><a href="s2-trouble-tracebacks-x86.html">8.3.2. Saving traceback messages without removeable media</a></span></dt><dt><span class="section"><a href="s2-trouble-part-tables-x86.html">8.3.3. Trouble with Partition Tables</a></span></dt><dt><span class="section"><a href="s2-trouble-space-x86.html">8.3.4. Using Remaining Space</a></span></dt><dt><span class="section"><a href="s2-trouble-completeparts-x86.html">8.3.5. Other Partitioning Problems</a></span></dt><dt><span class="section"><a href="ch08s03s06.html">8.3.6. Are You Seeing Python Errors?</a></span></dt></dl></dd><dt><span class="section"><a href="ch08s04.html">8.4. Problems After Installation</a></span></dt><dd><dl><dt><span class="section"><a href="ch08s04.html#s2-trouble-grub">8.4.1. Trouble With the Graphical GRUB Screen on an x86-based System?</a></span></dt><dt><span class="section"><a href="ch08s04s02.html">8.4.2. Booting into a Graph
 ical Environment</a></span></dt><dt><span class="section"><a href="ch08s04s03.html">8.4.3. Problems with the X Window System (GUI)</a></span></dt><dt><span class="section"><a href="ch08s04s04.html">8.4.4. Problems with the X Server Crashing and Non-Root Users</a></span></dt><dt><span class="section"><a href="ch08s04s05.html">8.4.5. Problems When You Try to Log In</a></span></dt><dt><span class="section"><a href="s2-trouble-ram.html">8.4.6. Is Your RAM Not Being Recognized?</a></span></dt><dt><span class="section"><a href="ch08s04s07.html">8.4.7. Your Printer Does Not Work</a></span></dt><dt><span class="section"><a href="s2-trouble-sound.html">8.4.8. Problems with Sound Configuration</a></span></dt><dt><span class="section"><a href="ch08s04s09.html">8.4.9. Apache-based httpd service/Sendmail Hangs During Startup</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="pt-Advanced_installation_options.html">III. Advanced installation options</a></span></dt
 ><dd><dl><dt><span class="chapter"><a href="ap-admin-options.html">9. Boot Options</a></span></dt><dd><dl><dt><span class="section"><a href="ap-admin-options.html#sn-bootoptions-installer">9.1. Configuring the Installation System at the Boot Menu</a></span></dt><dd><dl><dt><span class="section"><a href="ap-admin-options.html#sn-boot-options-language">9.1.1. Specifying the Language</a></span></dt><dt><span class="section"><a href="ap-admin-options.html#sn-boot-options-interface">9.1.2. Configuring the Interface</a></span></dt><dt><span class="section"><a href="ap-admin-options.html#sn-boot-options-update">9.1.3. Updating anaconda</a></span></dt><dt><span class="section"><a href="ap-admin-options.html#sn-boot-options-installmethod">9.1.4. Specifying the Installation Method</a></span></dt><dt><span class="section"><a href="ap-admin-options.html#sn-boot-options-network">9.1.5. Manually Configuring the Network Settings</a></span></dt></dl></dd><dt><span class="section"><a href="s
 n-remoteaccess-installation.html">9.2. Enabling Remote Access to the Installation System</a></span></dt><dd><dl><dt><span class="section"><a href="sn-remoteaccess-installation.html#sn-remoteaccess-installation-vnc">9.2.1. Enabling Remote Access with VNC</a></span></dt><dt><span class="section"><a href="sn-remoteaccess-installation-vnclistener.html">9.2.2. Connecting the Installation System to a VNC Listener</a></span></dt><dt><span class="section"><a href="sn-telnet-installation.html">9.2.3. Enabling Remote Access with Telnet</a></span></dt></dl></dd><dt><span class="section"><a href="sn-remote-logging.html">9.3. Logging to a Remote System During the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="sn-remote-logging.html#sn-remote-logging-logserver">9.3.1. Configuring a Log Server</a></span></dt></dl></dd><dt><span class="section"><a href="sn-automating-installation.html">9.4. Automating the Installation with Kickstart</a></span></dt><dt><span class="se
 ction"><a href="sn-bootoptions-hardware.html">9.5. Enhancing Hardware Support</a></span></dt><dd><dl><dt><span class="section"><a href="sn-bootoptions-hardware.html#sn-bootoptions-driverdisks">9.5.1. Adding Hardware Support with Driver Disks</a></span></dt><dt><span class="section"><a href="sn-bootoptions-hwdetection.html">9.5.2. Overriding Automatic Hardware Detection</a></span></dt></dl></dd><dt><span class="section"><a href="sn-boot-modes.html">9.6. Using the Maintenance Boot Modes</a></span></dt><dd><dl><dt><span class="section"><a href="sn-boot-modes.html#sn-memtest">9.6.1. Loading the Memory (RAM) Testing Mode</a></span></dt><dt><span class="section"><a href="sn-boot-mediacheck.html">9.6.2. Verifying boot media</a></span></dt><dt><span class="section"><a href="sn-mode-rescue.html">9.6.3. Booting Your Computer with the Rescue Mode</a></span></dt><dt><span class="section"><a href="sn-mode-upgradeany.html">9.6.4. Upgrading your computer</a></span></dt></dl></dd></dl></dd>
 <dt><span class="chapter"><a href="ap-medialess-install.html">10. Installing Without Media</a></span></dt><dd><dl><dt><span class="section"><a href="ap-medialess-install.html#sn-medialess-getting-files">10.1. Retrieving Boot Files</a></span></dt><dt><span class="section"><a href="sn-medialess-editing-grub-conf.html">10.2. Editing the GRUB Configuration</a></span></dt><dt><span class="section"><a href="sn-medialess-booting.html">10.3. Booting to Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="ap-install-server.html">11. Setting Up an Installation Server</a></span></dt><dd><dl><dt><span class="section"><a href="ap-install-server.html#sn-install-cobbler">11.1. Setting Up cobbler</a></span></dt><dt><span class="section"><a href="sn-cobbler-setup-distro.html">11.2. Setting Up the Distribution</a></span></dt><dt><span class="section"><a href="sn-cobbler-mirror.html">11.3. Mirroring a Network Location</a></span></dt><dt><span class="section"><a href="sn-cob
 bler-import.html">11.4. Importing the Distribution</a></span></dt><dt><span class="section"><a href="sn-pxe-server-manual.html">11.5. Manually configure a PXE server</a></span></dt><dd><dl><dt><span class="section"><a href="sn-pxe-server-manual.html#s1-netboot-netserver">11.5.1. Setting up the Network Server</a></span></dt><dt><span class="section"><a href="s1-netboot-pxe-config.html">11.5.2. PXE Boot Configuration</a></span></dt><dt><span class="section"><a href="s1-netboot-add-hosts.html">11.5.3. Adding PXE Hosts</a></span></dt><dt><span class="section"><a href="s1-netboot-tftp.html">11.5.4. TFTPD</a></span></dt><dt><span class="section"><a href="ch11s05s05.html">11.5.5. Configuring the DHCP Server</a></span></dt><dt><span class="section"><a href="s2-netboot-custom-msg.html">11.5.6. Adding a Custom Boot Message</a></span></dt><dt><span class="section"><a href="netboot-performing.html">11.5.7. Performing the PXE Installation</a></span></dt></dl></dd></dl></dd><dt><span clas
 s="chapter"><a href="vncwhitepaperadded.html">12. Installing Through VNC</a></span></dt><dd><dl><dt><span class="section"><a href="vncwhitepaperadded.html#VNC_Whitepaper-vnc-viewer">12.1. VNC Viewer</a></span></dt><dt><span class="section"><a href="VNC_Whitepaper-vnc-modes-in-anaconda.html">12.2. VNC Modes in Anaconda</a></span></dt><dd><dl><dt><span class="section"><a href="VNC_Whitepaper-vnc-modes-in-anaconda.html#VNC_Whitepaper-vnc-direct-mode">12.2.1. Direct Mode</a></span></dt><dt><span class="section"><a href="VNC_Whitepaper-vnc-connect-mode.html">12.2.2. Connect Mode</a></span></dt></dl></dd><dt><span class="section"><a href="VNC_Whitepaper-installation.html">12.3. Installation Using VNC</a></span></dt><dd><dl><dt><span class="section"><a href="VNC_Whitepaper-installation.html#VNC_Whitepaper-installation-example">12.3.1. Installation Example</a></span></dt><dt><span class="section"><a href="VNC_Whitepaper-kickstart-installation.html">12.3.2. Kickstart Considerations</
 a></span></dt><dt><span class="section"><a href="VNC_Whitepaper-firewall-considerations.html">12.3.3. Firewall Considerations</a></span></dt></dl></dd><dt><span class="section"><a href="VNC_Whitepaper-references.html">12.4. References</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-kickstart2.html">13. Kickstart Installations</a></span></dt><dd><dl><dt><span class="section"><a href="ch-kickstart2.html#s1-kickstart2-whatis">13.1. What are Kickstart Installations?</a></span></dt><dt><span class="section"><a href="s1-kickstart2-howuse.html">13.2. How Do You Perform a Kickstart Installation?</a></span></dt><dt><span class="section"><a href="s1-kickstart2-file.html">13.3. Creating the Kickstart File</a></span></dt><dt><span class="section"><a href="s1-kickstart2-options.html">13.4. Kickstart Options</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kickstart2-options.html#s2-kickstart2-options-part-examples">13.4.1. Advanced Partitioning Example</a></spa
 n></dt></dl></dd><dt><span class="section"><a href="s1-kickstart2-packageselection.html">13.5. Package Selection</a></span></dt><dt><span class="section"><a href="s1-kickstart2-preinstallconfig.html">13.6. Pre-installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kickstart2-preinstallconfig.html#s2-kickstart2-prescript-example">13.6.1. Example</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kickstart2-postinstallconfig.html">13.7. Post-installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kickstart2-postinstallconfig.html#s2-kickstart2-post-examples">13.7.1. Examples</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kickstart2-putkickstarthere.html">13.8. Making the Kickstart File Available</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kickstart2-putkickstarthere.html#s2-kickstart2-boot-media">13.8.1. Creating Kickstart Boot Media</a></span></dt><dt><span class="section"><a href=
 "s2-kickstart2-networkbased.html">13.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.html">13.9. Making the Installation Tree Available</a></span></dt><dt><span class="section"><a href="s1-kickstart2-startinginstall.html">13.10. Starting a Kickstart Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-redhat-config-kickstart.html">14. Kickstart Configurator</a></span></dt><dd><dl><dt><span class="section"><a href="ch-redhat-config-kickstart.html#s1-redhat-config-kickstart-basic">14.1. Basic Configuration</a></span></dt><dt><span class="section"><a href="s1-redhat-config-kickstart-install.html">14.2. Installation Method</a></span></dt><dt><span class="section"><a href="s1-redhat-config-kickstart-bootloader.html">14.3. Boot Loader Options</a></span></dt><dt><span class="section"><a href="s1-redhat-config-kickstart-partitions.html">14.4. Partition Information</a
 ></span></dt><dd><dl><dt><span class="section"><a href="s1-redhat-config-kickstart-partitions.html#s2-redhat-config-kickstart-create-part">14.4.1. Creating Partitions</a></span></dt></dl></dd><dt><span class="section"><a href="s1-redhat-config-kickstart-network.html">14.5. Network Configuration</a></span></dt><dt><span class="section"><a href="s1-redhat-config-kickstart-auth.html">14.6. Authentication</a></span></dt><dt><span class="section"><a href="s1-redhat-config-kickstart-firewall.html">14.7. Firewall Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="s1-redhat-config-kickstart-firewall.html#s2-redhat-config-kickstart-firewall-selinux">14.7.1. SELinux Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="s1-redhat-config-kickstart-xconfig.html">14.8. Display Configuration</a></span></dt><dt><span class="section"><a href="s1-redhat-config-kickstart-pkgs.html">14.9. Package Selection</a></span></dt><dt><span class="section"><a href
 ="s1-redhat-config-kickstart-prescript.html">14.10. Pre-Installation Script</a></span></dt><dt><span class="section"><a href="s1-redhat-config-kickstart-postinstall.html">14.11. Post-Installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="s1-redhat-config-kickstart-postinstall.html#s2-redhat-config-kickstart-nochroot">14.11.1. Chroot Environment</a></span></dt><dt><span class="section"><a href="s2-redhat-config-kickstart-interpreter.html">14.11.2. Use an Interpreter</a></span></dt></dl></dd><dt><span class="section"><a href="s1-redhat-config-kickstart-savefile.html">14.12. Saving the File</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="pt-After_installation.html">IV. After installation</a></span></dt><dd><dl><dt><span class="chapter"><a href="ch-firstboot.html">15. Firstboot</a></span></dt><dd><dl><dt><span class="section"><a href="ch-firstboot.html#sn-firstboot-license">15.1. License Agreement</a></span></dt><dt><span class="section"
 ><a href="sn-firstboot-systemuser.html">15.2. System User</a></span></dt><dt><span class="section"><a href="sn-firstboot-datetime.html">15.3. Date and Time</a></span></dt><dt><span class="section"><a href="sn-smolt.html">15.4. Hardware Profile</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-next-steps.html">16. Your Next Steps</a></span></dt><dd><dl><dt><span class="section"><a href="ch-next-steps.html#sn-system-updating">16.1. Updating Your System</a></span></dt><dt><span class="section"><a href="sn-finishing-upgrade.html">16.2. Finishing an Upgrade</a></span></dt><dt><span class="section"><a href="sn-switching-to-gui-login.html">16.3. Switching to a Graphical Login</a></span></dt><dt><span class="section"><a href="sn-news-subscriptions.html">16.4. Subscribing to Fedora Announcements and News</a></span></dt><dt><span class="section"><a href="sn-web-help.html">16.5. Finding Documentation and Support</a></span></dt><dt><span class="section"><a href="sn-communit
 y.html">16.6. Joining the Fedora Community</a></span></dt></dl></dd><dt><span class="chapter"><a href="ap-rescuemode.html">17. Basic System Recovery</a></span></dt><dd><dl><dt><span class="section"><a href="ap-rescuemode.html#s1-rescuemode-common-problems">17.1. Common Problems</a></span></dt><dd><dl><dt><span class="section"><a href="ap-rescuemode.html#s2-rescuemode-whatis-unable-boot">17.1.1. Unable to Boot into Fedora</a></span></dt><dt><span class="section"><a href="ap-rescuemode.html#s2-rescuemode-hardware-troubles">17.1.2. Hardware/Software Problems</a></span></dt><dt><span class="section"><a href="ap-rescuemode.html#s2-rescuemode-root-password">17.1.3. Root Password</a></span></dt></dl></dd><dt><span class="section"><a href="s1-rescuemode-boot.html">17.2. Booting into Rescue Mode</a></span></dt><dd><dl><dt><span class="section"><a href="s1-rescuemode-boot.html#s2-rescuemode-boot-reinstall-bootloader">17.2.1. Reinstalling the Boot Loader</a></span></dt></dl></dd><dt><s
 pan class="section"><a href="s1-rescuemode-booting-single.html">17.3. Booting into Single-User Mode</a></span></dt><dt><span class="section"><a href="s1-rescuemode-booting-emergency.html">17.4. Booting into Emergency Mode</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-upgrade-x86.html">18. Upgrading Your Current System</a></span></dt><dd><dl><dt><span class="section"><a href="ch-upgrade-x86.html#id840127">18.1. Determining Whether to Upgrade or Re-Install</a></span></dt><dt><span class="section"><a href="ch18s02.html">18.2. Upgrading Your System</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-x86-uninstall.html">19. Removing Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="ch-x86-uninstall.html#sn-x86-uninstall-single">19.1. Fedora is the only operating system on the computer</a></span></dt><dt><span class="section"><a href="sn-x86-uninstall-dual.html">19.2. Your computer dual-boots Fedora and another operating system</a></span>
 </dt><dd><dl><dt><span class="section"><a href="sn-x86-uninstall-dual.html#sn-x86-uninstall-dual-windows">19.2.1. Your computer dual-boots Fedora and a Microsoft Windows operating system</a></span></dt><dt><span class="section"><a href="sn-x86-uninstall-dual-mac.html">19.2.2. Your computer dual-boots Fedora and Mac OS X</a></span></dt><dt><span class="section"><a href="sn-x86-uninstall-dual-linux.html">19.2.3. Your computer dual-boots Fedora and a different Linux distribution</a></span></dt></dl></dd><dt><span class="section"><a href="sn-x86-uninstall-legacy.html">19.3. Replacing Fedora with MS-DOS or legacy versions of Microsoft Windows</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="pt-Technical_appendixes.html">V. Technical appendixes</a></span></dt><dd><dl><dt><span class="appendix"><a href="ch-partitions-x86.html">A. An Introduction to Disk Partitions</a></span></dt><dd><dl><dt><span class="section"><a href="ch-partitions-x86.html#s1-partitions-concep
 ts-x86">A.1. Hard Disk Basic Concepts</a></span></dt><dd><dl><dt><span class="section"><a href="ch-partitions-x86.html#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="ch-partitions-x86.html#s2-partitions-partitioning-x86">A.1.2. Partitions: Turning One Drive Into Many</a></span></dt><dt><span class="section"><a href="ch-partitions-x86.html#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="ch-partitions-x86.html#s2-partitions-make-room-x86">A.1.4. Making Room For Fedora</a></span></dt><dt><span class="section"><a href="ch-partitions-x86.html#s2-partitions-part-name-x86">A.1.5. Partition Naming Scheme</a></span></dt><dt><span class="section"><a href="ch-partitions-x86.html#s2-partitions-other-os-x86">A.1.6. Disk Partitions and Other Operating Systems</a></span></dt><dt><span class
 ="section"><a href="ch-partitions-x86.html#s2-partitions-mt-points-x86">A.1.7. Disk Partitions and Mount Points</a></span></dt><dt><span class="section"><a href="ch-partitions-x86.html#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.html">B. ISCSI disks</a></span></dt><dd><dl><dt><span class="section"><a href="ISCSI_disks.html#sn-iSCSI_in_Fedora-iSCSI_disks_in_anaconda">B.1. iSCSI disks in anaconda</a></span></dt><dt><span class="section"><a href="sn-iSCSI_disks_during_start_up.html">B.2. iSCSI disks during start up</a></span></dt></dl></dd><dt><span class="appendix"><a href="Disk_Encryption_Guide.html">C. Disk Encryption Guide</a></span></dt><dd><dl><dt><span class="section"><a href="Disk_Encryption_Guide.html#id873270">C.1. What is block device encryption? </a></span></dt><dt><span class="section"><a href="apcs02.html">C.2. Encrypting block devices using dm-crypt/LUKS </a></span></dt
 ><dd><dl><dt><span class="section"><a href="apcs02.html#id785142">C.2.1. Overview of LUKS </a></span></dt><dt><span class="section"><a href="apcs02s02.html">C.2.2. How will I access the encrypted devices after installation? (System Startup) </a></span></dt><dt><span class="section"><a href="apcs02s03.html">C.2.3. Choosing a Good Passphrase </a></span></dt></dl></dd><dt><span class="section"><a href="apcs03.html">C.3. Creating Encrypted Block Devices in Anaconda </a></span></dt><dd><dl><dt><span class="section"><a href="apcs03.html#id906052">C.3.1. What Kinds of Block Devices Can Be Encrypted? </a></span></dt><dt><span class="section"><a href="apcs03s02.html">C.3.2. Limitations of Anaconda's Block Device Encryption Support </a></span></dt></dl></dd><dt><span class="section"><a href="apcs04.html">C.4. Creating Encrypted Block Devices on the Installed System After Installation </a></span></dt><dd><dl><dt><span class="section"><a href="apcs04.html#id885513">C.4.1. Create the blo
 ck devices </a></span></dt><dt><span class="section"><a href="randomize_device.html">C.4.2. Optional: Fill the device with random data</a></span></dt><dt><span class="section"><a href="apcs04s03.html">C.4.3. Format the device as a dm-crypt/LUKS encrypted device </a></span></dt><dt><span class="section"><a href="apcs04s04.html">C.4.4. Create a mapping to allow access to the device's decrypted contents </a></span></dt><dt><span class="section"><a href="apcs04s05.html">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="apcs04s06.html">C.4.6. Add the mapping information to /etc/crypttab</a></span></dt><dt><span class="section"><a href="apcs04s07.html">C.4.7. Add an entry to /etc/fstab</a></span></dt></dl></dd><dt><span class="section"><a href="apcs05.html">C.5. Common Post-Installation Tasks </a></span></dt><dd><dl><dt><span class="section"><a href="apcs05.html
 #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="apcs05s02.html">C.5.2. Add a new passphrase to an existing device </a></span></dt><dt><span class="section"><a href="apcs05s03.html">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.html">D. Understanding LVM</a></span></dt><dt><span class="appendix"><a href="ch-grub.html">E. The GRUB Boot Loader</a></span></dt><dd><dl><dt><span class="section"><a href="ch-grub.html#s1-grub-whatis">E.1. GRUB</a></span></dt><dd><dl><dt><span class="section"><a href="ch-grub.html#s2-grub-whatis-booting">E.1.1. GRUB and the x86 Boot Process</a></span></dt><dt><span class="section"><a href="ch-grub.html#s2-grub-whatis-features">E.1.2. Features of GRUB</a></span></dt></dl></dd><dt><span class="section"><a href="s1-grub-installing.html">E.2. Installing GRUB<
 /a></span></dt><dt><span class="section"><a href="s1-grub-terminology.html">E.3. GRUB Terminology</a></span></dt><dd><dl><dt><span class="section"><a href="s1-grub-terminology.html#s2-grub-terminology-devices">E.3.1. Device Names</a></span></dt><dt><span class="section"><a href="s2-grub-terminology-files.html">E.3.2. File Names and Blocklists</a></span></dt><dt><span class="section"><a href="s2-grub-terminology-rootfs.html">E.3.3. The Root File System and GRUB</a></span></dt></dl></dd><dt><span class="section"><a href="s1-grub-interfaces.html">E.4. GRUB Interfaces</a></span></dt><dd><dl><dt><span class="section"><a href="s1-grub-interfaces.html#s2-grub-interfaces-orderofuse">E.4.1. Interfaces Load Order</a></span></dt></dl></dd><dt><span class="section"><a href="s1-grub-commands.html">E.5. GRUB Commands</a></span></dt><dt><span class="section"><a href="s1-grub-configfile.html">E.6. GRUB Menu Configuration File</a></span></dt><dd><dl><dt><span class="section"><a href="s1-grub
 -configfile.html#s2-grub-configfile-structure">E.6.1. Configuration File Structure</a></span></dt><dt><span class="section"><a href="s2-grub-configfile-commands.html">E.6.2. Configuration File Directives</a></span></dt></dl></dd><dt><span class="section"><a href="s1-grub-runlevels.html">E.7. Changing Runlevels at Boot Time</a></span></dt><dt><span class="section"><a href="s1-grub-additional-resources.html">E.8. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-grub-additional-resources.html#s2-grub-installed-documentation">E.8.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-grub-useful-websites.html">E.8.2. Useful Websites</a></span></dt><dt><span class="section"><a href="s2-grub-related-books.html">E.8.3. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="ch-boot-init-shutdown.html">F. Boot Process, Init, and Shutdown</a></span></dt><dd><dl><dt><span class="section"><a href="ch
 -boot-init-shutdown.html#s1-boot-process-basics">F.1. The Boot Process</a></span></dt><dt><span class="section"><a href="s1-boot-init-shutdown-process.html">F.2. A Detailed Look at the Boot Process</a></span></dt><dd><dl><dt><span class="section"><a href="s1-boot-init-shutdown-process.html#s2-boot-init-shutdown-bios">F.2.1. The BIOS</a></span></dt><dt><span class="section"><a href="s2-boot-init-shutdown-loader.html">F.2.2. The Boot Loader</a></span></dt><dt><span class="section"><a href="s2-boot-init-shutdown-kernel.html">F.2.3. The Kernel</a></span></dt><dt><span class="section"><a href="s2-boot-init-shutdown-init.html">F.2.4. The /sbin/init Program</a></span></dt></dl></dd><dt><span class="section"><a href="s1-boot-init-shutdown-run-boot.html">F.3. Running Additional Programs at Boot Time</a></span></dt><dt><span class="section"><a href="s1-boot-init-shutdown-sysv.html">F.4. SysV Init Runlevels</a></span></dt><dd><dl><dt><span class="section"><a href="s1-boot-init-shutdown
 -sysv.html#s2-init-boot-shutdown-rl">F.4.1. Runlevels</a></span></dt><dt><span class="section"><a href="s2-boot-init-shutdown-sysv-util.html">F.4.2. Runlevel Utilities</a></span></dt></dl></dd><dt><span class="section"><a href="s1-boot-init-shutdown-shutdown.html">F.5. Shutting Down</a></span></dt></dl></dd><dt><span class="appendix"><a href="ap-techref.html">G. Other Technical Documentation</a></span></dt></dl></dd><dt><span class="appendix"><a href="ch-Contributors_and_production_methods.html">H. Contributors and production methods</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Contributors_and_production_methods.html#sn-Contributors">H.1. Contributors</a></span></dt><dt><span class="section"><a href="sn-Production_methods.html">H.2. Production methods</a></span></dt></dl></dd><dt><span class="appendix"><a href="appe-Publican-Revision_History.html">I. Revision History</a></span></dt><dt><span class="index"><a href="ix01.html">Index</a></span></dt></dl></div><
 /div><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" href="Installation-Guide-Preface.html"><strong>Next</strong>Preface</a></li></ul></body></html>


--- NEW FILE ix01.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Index</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="index.html" title="Installation Guide" /><link rel="prev" href="appe-Publican-Revision_History.html" title="AppendixÂ I.Â Revision History" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="appe-Publican-Revision_History.html"><strong>Prev</strong>
 </a></li><li class="next"></li></ul><div class="index"><div class="titlepage"><div><div><h2 class="title" id="id739507">Index</h2></div></div></div><div class="index"><div class="indexdiv"><h3>Symbols</h3><dl><dt>/boot/ partition</dt><dd><dl><dt>recommended partitioning, <a class="indexterm" href="s2-diskpartrecommend-x86.html">Recommended Partitioning Scheme</a></dt></dl></dd><dt>/root/install.log</dt><dd><dl><dt>install log file location, <a class="indexterm" href="s1-preparetoinstall-x86.html#id838976"> Prepare to Install </a></dt></dl></dd><dt>/var/ partition</dt><dd><dl><dt>recommended partitioning, <a class="indexterm" href="s2-diskpartrecommend-x86.html">Recommended Partitioning Scheme</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>A</h3><dl><dt>adding partitions, <a class="indexterm" href="ch07s21s05.html">Adding Partitions</a></dt><dd><dl><dt>file system type, <a class="indexterm" href="ch07s21s05.html#s3-diskpartitioning-file-x86">File System Types</a></dt>
 </dl></dd><dt>Anaconda, <a class="indexterm" href="ap-techref.html">Other Technical Documentation</a></dt><dt>architecture, <a class="indexterm" href="sn-which-arch.html">Which Architecture Is My Computer?</a></dt><dd><dl><dt>determining, <a class="indexterm" href="sn-which-arch.html">Which Architecture Is My Computer?</a></dt></dl></dd><dt>array (see RAID)</dt><dt>ATAPI CD-ROM</dt><dd><dl><dt>unrecognized, problems with, <a class="indexterm" href="s1-begininstall-cd-inst-x86.html#s2-begininstall-unrec-ide-x86">What If the IDE CD-ROM Was Not Found?</a></dt></dl></dd><dt>automatic partitioning, <a class="indexterm" href="s1-diskpartsetup-x86.html">Disk Partitioning Setup</a>, <a class="indexterm" href="s1-diskpartauto-x86.html">Create Default Layout</a></dt></dl></div><div class="indexdiv"><h3>B</h3><dl><dt>Basic Input/Output System (see BIOS)</dt><dt>BIOS</dt><dd><dl><dt>definition of, <a class="indexterm" href="s1-boot-init-shutdown-process.html#s2-boot-init-shutdown-bios">
 The BIOS</a></dt><dd><dl><dt>(see also boot process)</dt></dl></dd></dl></dd><dt>BIOS (Basic Input/Output System), <a class="indexterm" href="sn-start-installation.html">How Do I Start the Installation Program?</a></dt><dt>BitTorrent, <a class="indexterm" href="ch-new-users.html#sn-which-download-bt">From BitTorrent</a></dt><dd><dl><dt>seeding, <a class="indexterm" href="ch-new-users.html#sn-which-download-bt">From BitTorrent</a></dt></dl></dd><dt>boot CD-ROM, <a class="indexterm" href="ch03s04.html#id825179">Alternative Boot Methods</a></dt><dd><dl><dt>creating, <a class="indexterm" href="s2-steps-make-cd.html">Making an Installation Boot CD-ROM</a></dt></dl></dd><dt>boot loader, <a class="indexterm" href="sn-upgrading-bootloader.html">Upgrading Boot Loader Configuration</a>, <a class="indexterm" href="s1-x86-bootloader.html">x86, AMD64, and Intel 64 Boot Loader Configuration</a></dt><dd><dl><dt>(see also GRUB)</dt><dt>configuration, <a class="indexterm" href="s1-x86-bootlo
 ader.html">x86, AMD64, and Intel 64 Boot Loader Configuration</a></dt><dt>GRUB, <a class="indexterm" href="s1-x86-bootloader.html">x86, AMD64, and Intel 64 Boot Loader Configuration</a></dt><dt>installing on boot partition, <a class="indexterm" href="s1-x86-bootloader.html#x86-bootloader-adv">Advanced Boot Loader Configuration</a></dt><dt>MBR, <a class="indexterm" href="s1-x86-bootloader.html#x86-bootloader-adv">Advanced Boot Loader Configuration</a></dt><dt>password, <a class="indexterm" href="s1-x86-bootloader.html">x86, AMD64, and Intel 64 Boot Loader Configuration</a></dt><dt>upgrading, <a class="indexterm" href="sn-upgrading-bootloader.html">Upgrading Boot Loader Configuration</a></dt></dl></dd><dt>boot loader password, <a class="indexterm" href="s1-x86-bootloader.html">x86, AMD64, and Intel 64 Boot Loader Configuration</a></dt><dt>boot loaders, <a class="indexterm" href="ch-grub.html#s1-grub-whatis">GRUB</a></dt><dd><dl><dt>(see also GRUB)</dt><dt>definition of, <a cla
 ss="indexterm" href="ch-grub.html">The GRUB Boot Loader</a></dt></dl></dd><dt>boot methods</dt><dd><dl><dt>boot CD-ROM, <a class="indexterm" href="ch03s04.html#id825179">Alternative Boot Methods</a></dt><dt>USB pen drive, <a class="indexterm" href="ch03s04.html#id825179">Alternative Boot Methods</a></dt></dl></dd><dt>boot options, <a class="indexterm" href="s2-x86-starting-bootopts.html">Additional Boot Options</a></dt><dd><dl><dt>boot.iso, <a class="indexterm" href="s2-x86-starting-bootopts.html">Additional Boot Options</a></dt><dt>linux mediacheck, <a class="indexterm" href="ch03s06.html">Preparing for a Hard Drive Installation</a></dt><dt>mediacheck, <a class="indexterm" href="s2-x86-starting-bootopts.html">Additional Boot Options</a></dt><dt>serial mode, <a class="indexterm" href="s2-x86-starting-bootopts.html">Additional Boot Options</a></dt><dd><dl><dt>UTF-8, <a class="indexterm" href="s2-x86-starting-bootopts.html">Additional Boot Options</a></dt></dl></dd><dt>text mo
 de, <a class="indexterm" href="s2-x86-starting-bootopts.html">Additional Boot Options</a></dt></dl></dd><dt>boot process, <a class="indexterm" href="ch-boot-init-shutdown.html">Boot Process, Init, and Shutdown</a>, <a class="indexterm" href="s1-boot-init-shutdown-process.html">A Detailed Look at the Boot Process</a></dt><dd><dl><dt>(see also boot loaders)</dt><dt>chain loading, <a class="indexterm" href="ch-grub.html#s2-grub-whatis-booting">GRUB and the x86 Boot Process</a></dt><dt>direct loading, <a class="indexterm" href="ch-grub.html#s2-grub-whatis-booting">GRUB and the x86 Boot Process</a></dt><dt>for x86, <a class="indexterm" href="s1-boot-init-shutdown-process.html">A Detailed Look at the Boot Process</a></dt><dt>stages of, <a class="indexterm" href="ch-boot-init-shutdown.html#s1-boot-process-basics">The Boot Process</a>, <a class="indexterm" href="s1-boot-init-shutdown-process.html">A Detailed Look at the Boot Process</a></dt><dd><dl><dt>/sbin/init command, <a class="
 indexterm" href="s2-boot-init-shutdown-init.html">The /sbin/init Program</a></dt><dt>BIOS, <a class="indexterm" href="s1-boot-init-shutdown-process.html#s2-boot-init-shutdown-bios">The BIOS</a></dt><dt>boot loader, <a class="indexterm" href="s2-boot-init-shutdown-loader.html">The Boot Loader</a></dt><dt>EFI shell, <a class="indexterm" href="s1-boot-init-shutdown-process.html#s2-boot-init-shutdown-bios">The BIOS</a></dt><dt>kernel, <a class="indexterm" href="s2-boot-init-shutdown-kernel.html">The Kernel</a></dt></dl></dd></dl></dd><dt>boot.iso, <a class="indexterm" href="s2-steps-make-cd.html">Making an Installation Boot CD-ROM</a>, <a class="indexterm" href="s2-x86-starting-bootopts.html">Additional Boot Options</a></dt><dt>booting</dt><dd><dl><dt>emergency mode, <a class="indexterm" href="s1-rescuemode-booting-emergency.html">Booting into Emergency Mode</a></dt><dt>installation program</dt><dd><dl><dt>x86, AMD64 and Intel 64, <a class="indexterm" href="s1-x86-starting.html#
 s2-x86-starting-booting">Booting the Installation Program on x86, AMD64, and Intel 64 Systems</a></dt></dl></dd><dt>rescue mode, <a class="indexterm" href="s1-rescuemode-boot.html">Booting into Rescue Mode</a></dt><dt>single-user mode, <a class="indexterm" href="s1-rescuemode-booting-single.html">Booting into Single-User Mode</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>C</h3><dl><dt>canceling the installation, <a class="indexterm" href="s1-begininstall-cd-inst-x86.html">Installing from DVD/CD-ROM</a></dt><dt>CD-ROM</dt><dd><dl><dt>ATAPI, <a class="indexterm" href="s1-begininstall-cd-inst-x86.html">Installing from DVD/CD-ROM</a></dt><dd><dl><dt>unrecognized, problems with, <a class="indexterm" href="s1-begininstall-cd-inst-x86.html#s2-begininstall-unrec-ide-x86">What If the IDE CD-ROM Was Not Found?</a></dt></dl></dd><dt>boot CD-ROM, creating, <a class="indexterm" href="s2-steps-make-cd.html">Making an Installation Boot CD-ROM</a></dt><dt>IDE, <a class="indexterm" 
 href="s1-begininstall-cd-inst-x86.html">Installing from DVD/CD-ROM</a></dt><dd><dl><dt>unrecognized, problems with, <a class="indexterm" href="s1-begininstall-cd-inst-x86.html#s2-begininstall-unrec-ide-x86">What If the IDE CD-ROM Was Not Found?</a></dt></dl></dd><dt>installation from, <a class="indexterm" href="s1-begininstall-cd-inst-x86.html">Installing from DVD/CD-ROM</a></dt><dt>SCSI, <a class="indexterm" href="s1-begininstall-cd-inst-x86.html">Installing from DVD/CD-ROM</a></dt></dl></dd><dt>CD/DVD media</dt><dd><dl><dt>booting, <a class="indexterm" href="sn-start-installation.html">How Do I Start the Installation Program?</a></dt><dt>downloading, <a class="indexterm" href="ch-new-users.html#sn-howto-download">How Do I Download Installation Files?</a></dt><dd><dl><dt>(see also ISO images)</dt></dl></dd></dl></dd><dt>chkconfig, <a class="indexterm" href="s2-boot-init-shutdown-sysv-util.html">Runlevel Utilities</a></dt><dd><dl><dt>(see also services)</dt></dl></dd><dt>clo
 ck, <a class="indexterm" href="s1-timezone-x86.html">Time Zone Configuration</a></dt><dt>configuration</dt><dd><dl><dt>clock, <a class="indexterm" href="s1-timezone-x86.html">Time Zone Configuration</a></dt><dt>GRUB, <a class="indexterm" href="s1-x86-bootloader.html">x86, AMD64, and Intel 64 Boot Loader Configuration</a></dt><dt>hardware, <a class="indexterm" href="ch-ent-table.html">System Specifications List</a></dt><dt>time, <a class="indexterm" href="s1-timezone-x86.html">Time Zone Configuration</a></dt><dt>time zone, <a class="indexterm" href="s1-timezone-x86.html">Time Zone Configuration</a></dt></dl></dd><dt>consoles, virtual, <a class="indexterm" href="ch-guimode-x86.html#sn-guimode-virtual-consoles-x86">A Note about Virtual Consoles</a></dt></dl></div><div class="indexdiv"><h3>D</h3><dl><dt>DHCP</dt><dd><dl><dt>diskless environment, <a class="indexterm" href="ch11s05s05.html">Configuring the DHCP Server</a></dt><dt>PXE installations, <a class="indexterm" href="ch11s
 05s05.html">Configuring the DHCP Server</a></dt></dl></dd><dt>DHCP (Dynamic Host Configuration Protocol), <a class="indexterm" href="sn-networkconfig-fedora.html">Network Configuration</a></dt><dt>Disk Partitioner</dt><dd><dl><dt>adding partitions, <a class="indexterm" href="ch07s21s05.html">Adding Partitions</a></dt></dl></dd><dt>disk partitioning, <a class="indexterm" href="s1-diskpartsetup-x86.html">Disk Partitioning Setup</a></dt><dt>disk space, <a class="indexterm" href="ch03s03.html">Do You Have Enough Disk Space?</a></dt><dt>diskette</dt><dd><dl><dt>media, <a class="indexterm" href="ch-driverdisk-x86.html">Driver Media for Intel and AMD Systems</a></dt></dl></dd><dt>diskless environment</dt><dd><dl><dt>DHCP configuration, <a class="indexterm" href="ch11s05s05.html">Configuring the DHCP Server</a></dt></dl></dd><dt>dmraid</dt><dd><dl><dt>installation, <a class="indexterm" href="s1-advanced-storage-x86.html"> Advanced Storage Options </a></dt></dl></dd><dt>domain name, 
 <a class="indexterm" href="sn-networkconfig-fedora.html">Network Configuration</a></dt><dt>driver diskette, <a class="indexterm" href="s1-x86-starting.html">Starting the Installation Program</a></dt><dt>driver disks, <a class="indexterm" href="sn-bootoptions-hardware.html#sn-bootoptions-driverdisks">Adding Hardware Support with Driver Disks</a></dt><dt>driver media, <a class="indexterm" href="ch-driverdisk-x86.html">Driver Media for Intel and AMD Systems</a></dt><dd><dl><dt>creating diskette from image, <a class="indexterm" href="ch05s03.html#id806929">Creating a Driver Diskette from an Image File</a></dt><dt>produced by others, <a class="indexterm" href="ch05s03.html">How Do I Obtain Driver Media?</a></dt><dt>produced by Red Hat, <a class="indexterm" href="ch05s03.html">How Do I Obtain Driver Media?</a></dt><dt>using a driver image, <a class="indexterm" href="ch05s04.html">Using a Driver Image During Installation</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>E</h3>
 <dl><dt>EFI shell</dt><dd><dl><dt>definition of, <a class="indexterm" href="s1-boot-init-shutdown-process.html#s2-boot-init-shutdown-bios">The BIOS</a></dt><dd><dl><dt>(see also boot process)</dt></dl></dd></dl></dd><dt>emergency mode, <a class="indexterm" href="s1-rescuemode-booting-emergency.html">Booting into Emergency Mode</a></dt><dt>ext2 (see file systems)</dt><dt>ext3 (see file systems)</dt><dt>ext4 (see file systems)</dt><dt>extended partitions, <a class="indexterm" href="ch-partitions-x86.html#s2-partitions-overview-extended-x86">Partitions within Partitions â€” An Overview of Extended Partitions</a></dt><dt>Extensible Firmware Interface shell (see EFI shell)</dt></dl></div><div class="indexdiv"><h3>F</h3><dl><dt>feedback</dt><dd><dl><dt>contact information for this manual, <a class="indexterm" href="pr01s02.html">We Need Feedback!</a></dt></dl></dd><dt>file system</dt><dd><dl><dt>formats, overview of, <a class="indexterm" href="ch-partitions-x86.html#s2-partitions-
 filesystem-x86">It is Not What You Write, it is How You Write It</a></dt></dl></dd><dt>file system types, <a class="indexterm" href="ch07s21s05.html#s3-diskpartitioning-file-x86">File System Types</a></dt><dt>file systems</dt><dd><dl><dt>ext2, <a class="indexterm" href="s1-begininstall-hd-x86.html">Installing from a Hard Drive</a></dt><dt>ext3, <a class="indexterm" href="s1-begininstall-hd-x86.html">Installing from a Hard Drive</a></dt><dt>ext4, <a class="indexterm" href="s1-begininstall-hd-x86.html">Installing from a Hard Drive</a></dt><dt>vfat, <a class="indexterm" href="s1-begininstall-hd-x86.html">Installing from a Hard Drive</a></dt></dl></dd><dt>firewall</dt><dd><dl><dt>documentation, <a class="indexterm" href="ap-techref.html">Other Technical Documentation</a></dt></dl></dd><dt>Firstboot, <a class="indexterm" href="ch-firstboot.html">Firstboot</a></dt><dt>FTP</dt><dd><dl><dt>installation, <a class="indexterm" href="s1-steps-network-installs-x86.html">Preparing for a N
 etwork Installation</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>G</h3><dl><dt>GRUB, <a class="indexterm" href="s1-x86-bootloader.html">x86, AMD64, and Intel 64 Boot Loader Configuration</a>, <a class="indexterm" href="s2-boot-init-shutdown-loader.html">The Boot Loader</a></dt><dd><dl><dt>(see also boot loaders)</dt><dt>additional resources, <a class="indexterm" href="s1-grub-additional-resources.html">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="s1-grub-additional-resources.html#s2-grub-installed-documentation">Installed Documentation</a></dt><dt>related books, <a class="indexterm" href="s2-grub-related-books.html">Related Books</a></dt><dt>useful websites, <a class="indexterm" href="s2-grub-useful-websites.html">Useful Websites</a></dt></dl></dd><dt>alternatives to, <a class="indexterm" href="s2-x86-bootloader-alt.html">Alternative Boot Loaders</a></dt><dt>boot process, <a class="indexterm" href="ch-grub.html#s2-gru
 b-whatis-booting">GRUB and the x86 Boot Process</a></dt><dt>Changing Runlevels at Boot Time, <a class="indexterm" href="s1-grub-runlevels.html">Changing Runlevels at Boot Time</a></dt><dt>changing runlevels with, <a class="indexterm" href="s1-grub-interfaces.html">GRUB Interfaces</a></dt><dt>commands, <a class="indexterm" href="s1-grub-commands.html">GRUB Commands</a></dt><dt>configuration, <a class="indexterm" href="s1-x86-bootloader.html">x86, AMD64, and Intel 64 Boot Loader Configuration</a></dt><dt>configuration file</dt><dd><dl><dt>/boot/grub/grub.conf, <a class="indexterm" href="s1-grub-configfile.html#s2-grub-configfile-structure">Configuration File Structure</a></dt><dt>structure, <a class="indexterm" href="s1-grub-configfile.html#s2-grub-configfile-structure">Configuration File Structure</a></dt></dl></dd><dt>definition of, <a class="indexterm" href="ch-grub.html#s1-grub-whatis">GRUB</a></dt><dt>documentation, <a class="indexterm" href="ap-techref.html">Other Techni
 cal Documentation</a></dt><dt>features, <a class="indexterm" href="ch-grub.html#s2-grub-whatis-features">Features of GRUB</a></dt><dt>installing, <a class="indexterm" href="s1-grub-installing.html">Installing GRUB</a></dt><dt>interfaces, <a class="indexterm" href="s1-grub-interfaces.html">GRUB Interfaces</a></dt><dd><dl><dt>command line, <a class="indexterm" href="s1-grub-interfaces.html">GRUB Interfaces</a></dt><dt>menu, <a class="indexterm" href="s1-grub-interfaces.html">GRUB Interfaces</a></dt><dt>menu entry editor, <a class="indexterm" href="s1-grub-interfaces.html">GRUB Interfaces</a></dt><dt>order of, <a class="indexterm" href="s1-grub-interfaces.html#s2-grub-interfaces-orderofuse">Interfaces Load Order</a></dt></dl></dd><dt>menu configuration file, <a class="indexterm" href="s1-grub-configfile.html">GRUB Menu Configuration File</a></dt><dd><dl><dt>directives, <a class="indexterm" href="s2-grub-configfile-commands.html">Configuration File Directives</a></dt></dl></dd><
 dt>role in boot process, <a class="indexterm" href="s2-boot-init-shutdown-loader.html">The Boot Loader</a></dt><dt>terminology, <a class="indexterm" href="s1-grub-terminology.html">GRUB Terminology</a></dt><dd><dl><dt>devices, <a class="indexterm" href="s1-grub-terminology.html#s2-grub-terminology-devices">Device Names</a></dt><dt>files, <a class="indexterm" href="s2-grub-terminology-files.html">File Names and Blocklists</a></dt><dt>root file system, <a class="indexterm" href="s2-grub-terminology-rootfs.html">The Root File System and GRUB</a></dt></dl></dd></dl></dd><dt>grub.conf, <a class="indexterm" href="s1-grub-configfile.html#s2-grub-configfile-structure">Configuration File Structure</a></dt><dd><dl><dt>(see also GRUB)</dt></dl></dd></dl></div><div class="indexdiv"><h3>H</h3><dl><dt>halt, <a class="indexterm" href="s1-boot-init-shutdown-shutdown.html">Shutting Down</a></dt><dd><dl><dt>(see also shutdown)</dt></dl></dd><dt>Hard disk</dt><dd><dl><dt>initializing, <a class
 ="indexterm" href="sn-initialize-hdd.html">Initializing the Hard Disk</a></dt></dl></dd><dt>hard disk</dt><dd><dl><dt>basic concepts, <a class="indexterm" href="ch-partitions-x86.html#s1-partitions-concepts-x86">Hard Disk Basic Concepts</a></dt><dt>extended partitions, <a class="indexterm" href="ch-partitions-x86.html#s2-partitions-overview-extended-x86">Partitions within Partitions â€” An Overview of Extended Partitions</a></dt><dt>file system formats, <a class="indexterm" href="ch-partitions-x86.html#s2-partitions-filesystem-x86">It is Not What You Write, it is How You Write It</a></dt><dt>partition introduction, <a class="indexterm" href="ch-partitions-x86.html#s2-partitions-partitioning-x86">Partitions: Turning One Drive Into Many</a></dt><dt>partition types, <a class="indexterm" href="ch-partitions-x86.html#s2-partitions-partitioning-x86">Partitions: Turning One Drive Into Many</a></dt><dt>partitioning of, <a class="indexterm" href="ch-partitions-x86.html">An Introducti
 on to Disk Partitions</a></dt></dl></dd><dt>hard drive installation, <a class="indexterm" href="s1-begininstall-hd-x86.html">Installing from a Hard Drive</a></dt><dd><dl><dt>preparing for, <a class="indexterm" href="ch03s06.html">Preparing for a Hard Drive Installation</a></dt></dl></dd><dt>hardware</dt><dd><dl><dt>compatibility, <a class="indexterm" href="sn-Is_Your_Hardware_Compatible-x86.html">Is Your Hardware Compatible?</a></dt><dt>configuration, <a class="indexterm" href="ch-ent-table.html">System Specifications List</a></dt></dl></dd><dt>hostname, <a class="indexterm" href="sn-networkconfig-fedora.html">Network Configuration</a></dt><dt>HTTP</dt><dd><dl><dt>installation, <a class="indexterm" href="s1-steps-network-installs-x86.html">Preparing for a Network Installation</a>, <a class="indexterm" href="s1-begininstall-url-x86.html">Installing via FTP or HTTP</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>I</h3><dl><dt>IDE CD-ROM</dt><dd><dl><dt>unrecognized, pro
 blems with, <a class="indexterm" href="s1-begininstall-cd-inst-x86.html#s2-begininstall-unrec-ide-x86">What If the IDE CD-ROM Was Not Found?</a></dt></dl></dd><dt>init command, <a class="indexterm" href="s2-boot-init-shutdown-init.html">The /sbin/init Program</a></dt><dd><dl><dt>(see also boot process)</dt><dt>configuration files</dt><dd><dl><dt>/etc/inittab, <a class="indexterm" href="s1-boot-init-shutdown-sysv.html">SysV Init Runlevels</a></dt></dl></dd><dt>role in boot process, <a class="indexterm" href="s2-boot-init-shutdown-init.html">The /sbin/init Program</a></dt><dd><dl><dt>(see also boot process)</dt></dl></dd><dt>runlevels</dt><dd><dl><dt>directories for, <a class="indexterm" href="s1-boot-init-shutdown-sysv.html">SysV Init Runlevels</a></dt></dl></dd><dt>runlevels accessed by, <a class="indexterm" href="s1-boot-init-shutdown-sysv.html#s2-init-boot-shutdown-rl">Runlevels</a></dt><dt>SysV init</dt><dd><dl><dt>definition of, <a class="indexterm" href="s1-boot-init-sh
 utdown-sysv.html">SysV Init Runlevels</a></dt></dl></dd></dl></dd><dt>install log file</dt><dd><dl><dt>/root/install.log, <a class="indexterm" href="s1-preparetoinstall-x86.html#id838976"> Prepare to Install </a></dt></dl></dd><dt>installation</dt><dd><dl><dt>aborting, <a class="indexterm" href="s1-begininstall-cd-inst-x86.html">Installing from DVD/CD-ROM</a></dt><dt>can you install with a CD-ROM or DVD, <a class="indexterm" href="ch03s04.html">Can You Install Using the CD-ROM or DVD?</a></dt><dt>CD-ROM, <a class="indexterm" href="s1-begininstall-cd-inst-x86.html">Installing from DVD/CD-ROM</a></dt><dt>disk space, <a class="indexterm" href="ch03s03.html">Do You Have Enough Disk Space?</a></dt><dt>FTP, <a class="indexterm" href="s1-steps-network-installs-x86.html">Preparing for a Network Installation</a></dt><dt>GUI</dt><dd><dl><dt>CD-ROM, <a class="indexterm" href="ch-guimode-x86.html">Installing on Intel and AMD Systems</a></dt></dl></dd><dt>hard drive, <a class="indexterm"
  href="ch03s06.html">Preparing for a Hard Drive Installation</a>, <a class="indexterm" href="s1-begininstall-hd-x86.html">Installing from a Hard Drive</a></dt><dt>HTTP, <a class="indexterm" href="s1-steps-network-installs-x86.html">Preparing for a Network Installation</a>, <a class="indexterm" href="s1-begininstall-url-x86.html">Installing via FTP or HTTP</a></dt><dt>keyboard navigation, <a class="indexterm" href="s1-guimode-textinterface-x86.html#id834187">Using the Keyboard to Navigate</a></dt><dt>kickstart (see kickstart installations)</dt><dt>mediacheck, <a class="indexterm" href="s2-x86-starting-bootopts.html">Additional Boot Options</a></dt><dt>method</dt><dd><dl><dt>CD-ROM, <a class="indexterm" href="s1-installmethod.html">Selecting an Installation Method</a></dt><dt>hard drive, <a class="indexterm" href="s1-installmethod.html">Selecting an Installation Method</a></dt><dt>NFS image, <a class="indexterm" href="s1-installmethod.html">Selecting an Installation Method</a>
 </dt><dt>selecting, <a class="indexterm" href="s1-installmethod.html">Selecting an Installation Method</a></dt><dt>URL, <a class="indexterm" href="s1-installmethod.html">Selecting an Installation Method</a></dt></dl></dd><dt>network, <a class="indexterm" href="s1-steps-network-installs-x86.html">Preparing for a Network Installation</a></dt><dt>NFS, <a class="indexterm" href="s1-steps-network-installs-x86.html">Preparing for a Network Installation</a>, <a class="indexterm" href="s1-begininstall-nfs-x86.html">Installing via NFS</a></dt><dd><dl><dt>server information, <a class="indexterm" href="s1-begininstall-nfs-x86.html">Installing via NFS</a></dt></dl></dd><dt>partitioning, <a class="indexterm" href="s1-diskpartitioning-x86.html">Partitioning Your System</a></dt><dt>problems</dt><dd><dl><dt>IDE CD-ROM related, <a class="indexterm" href="s1-begininstall-cd-inst-x86.html#s2-begininstall-unrec-ide-x86">What If the IDE CD-ROM Was Not Found?</a></dt></dl></dd><dt>program</dt><dd
 ><dl><dt>graphical user interface, <a class="indexterm" href="ch-guimode-x86.html#s1-guimode-interface-x86">The Graphical Installation Program User Interface</a></dt><dt>starting, <a class="indexterm" href="s1-x86-starting.html">Starting the Installation Program</a></dt><dt>text mode user interface, <a class="indexterm" href="s1-guimode-textinterface-x86.html">The Text Mode Installation Program User Interface</a></dt><dt>virtual consoles, <a class="indexterm" href="ch-guimode-x86.html#sn-guimode-virtual-consoles-x86">A Note about Virtual Consoles</a></dt></dl></dd><dt>serial mode, <a class="indexterm" href="s2-x86-starting-bootopts.html">Additional Boot Options</a></dt><dd><dl><dt>UTF-8, <a class="indexterm" href="s2-x86-starting-bootopts.html">Additional Boot Options</a></dt></dl></dd><dt>starting, <a class="indexterm" href="s1-begininstall-cd-inst-x86.html">Installing from DVD/CD-ROM</a></dt><dt>text mode, <a class="indexterm" href="s2-x86-starting-bootopts.html">Additiona
 l Boot Options</a></dt></dl></dd><dt>installation media</dt><dd><dl><dt>testing, <a class="indexterm" href="ch03s06.html">Preparing for a Hard Drive Installation</a></dt></dl></dd><dt>installation program</dt><dd><dl><dt>x86, AMD64 and Intel 64</dt><dd><dl><dt>booting, <a class="indexterm" href="s1-x86-starting.html#s2-x86-starting-booting">Booting the Installation Program on x86, AMD64, and Intel 64 Systems</a></dt></dl></dd></dl></dd><dt>installing packages, <a class="indexterm" href="s1-pkgselection-x86.html">Package Group Selection</a></dt><dt>IPv4, <a class="indexterm" href="sn-networkconfig-fedora.html">Network Configuration</a></dt><dt>iscsi</dt><dd><dl><dt>installation, <a class="indexterm" href="s1-advanced-storage-x86.html"> Advanced Storage Options </a></dt></dl></dd><dt>ISO images</dt><dd><dl><dt>downloading, <a class="indexterm" href="sn-expert-download.html">Download Files</a>, <a class="indexterm" href="ch-new-users.html#sn-howto-download">How Do I Download In
 stallation Files?</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>K</h3><dl><dt>kernel</dt><dd><dl><dt>role in boot process, <a class="indexterm" href="s2-boot-init-shutdown-kernel.html">The Kernel</a></dt></dl></dd><dt>kernel options, <a class="indexterm" href="s2-x86-starting-bootopts.html#s3-x86-starting-kernelopts">Kernel Options</a></dt><dt>keyboard</dt><dd><dl><dt>configuration, <a class="indexterm" href="ch07s12.html">Keyboard Configuration</a></dt><dt>navigating the installation program using, <a class="indexterm" href="s1-guimode-textinterface-x86.html#id834187">Using the Keyboard to Navigate</a></dt></dl></dd><dt>keymap</dt><dd><dl><dt>selecting type of keyboard, <a class="indexterm" href="ch07s12.html">Keyboard Configuration</a></dt></dl></dd><dt>Kickstart, <a class="indexterm" href="sn-automating-installation.html">Automating the Installation with Kickstart</a></dt><dt>kickstart</dt><dd><dl><dt>how the file is found, <a class="indexterm" href="s1-kickstart
 2-startinginstall.html">Starting a Kickstart Installation</a></dt></dl></dd><dt>Kickstart Configurator, <a class="indexterm" href="ch-redhat-config-kickstart.html">Kickstart Configurator</a></dt><dd><dl><dt>%post script, <a class="indexterm" href="s1-redhat-config-kickstart-postinstall.html">Post-Installation Script</a></dt><dt>%pre script, <a class="indexterm" href="s1-redhat-config-kickstart-prescript.html">Pre-Installation Script</a></dt><dt>authentication options, <a class="indexterm" href="s1-redhat-config-kickstart-auth.html">Authentication</a></dt><dt>basic options, <a class="indexterm" href="ch-redhat-config-kickstart.html#s1-redhat-config-kickstart-basic">Basic Configuration</a></dt><dt>boot loader, <a class="indexterm" href="s1-redhat-config-kickstart-bootloader.html">Boot Loader Options</a></dt><dt>boot loader options, <a class="indexterm" href="s1-redhat-config-kickstart-bootloader.html">Boot Loader Options</a></dt><dt>Display configuration, <a class="indexterm" 
 href="s1-redhat-config-kickstart-xconfig.html">Display Configuration</a></dt><dt>firewall configuration, <a class="indexterm" href="s1-redhat-config-kickstart-firewall.html">Firewall Configuration</a></dt><dt>installation method selection, <a class="indexterm" href="s1-redhat-config-kickstart-install.html">Installation Method</a></dt><dt>interactive, <a class="indexterm" href="ch-redhat-config-kickstart.html#s1-redhat-config-kickstart-basic">Basic Configuration</a></dt><dt>keyboard, <a class="indexterm" href="ch-redhat-config-kickstart.html#s1-redhat-config-kickstart-basic">Basic Configuration</a></dt><dt>language, <a class="indexterm" href="ch-redhat-config-kickstart.html#s1-redhat-config-kickstart-basic">Basic Configuration</a></dt><dt>network configuration, <a class="indexterm" href="s1-redhat-config-kickstart-network.html">Network Configuration</a></dt><dt>package selection, <a class="indexterm" href="s1-redhat-config-kickstart-pkgs.html">Package Selection</a></dt><dt>pa
 rtitioning, <a class="indexterm" href="s1-redhat-config-kickstart-partitions.html">Partition Information</a></dt><dd><dl><dt>software RAID, <a class="indexterm" href="s1-redhat-config-kickstart-partitions.html#s3-redhat-config-kickstart-raid">Creating Software RAID Partitions</a></dt></dl></dd><dt>preview, <a class="indexterm" href="ch-redhat-config-kickstart.html">Kickstart Configurator</a></dt><dt>reboot, <a class="indexterm" href="ch-redhat-config-kickstart.html#s1-redhat-config-kickstart-basic">Basic Configuration</a></dt><dt>root password, <a class="indexterm" href="ch-redhat-config-kickstart.html#s1-redhat-config-kickstart-basic">Basic Configuration</a></dt><dd><dl><dt>encrypt, <a class="indexterm" href="ch-redhat-config-kickstart.html#s1-redhat-config-kickstart-basic">Basic Configuration</a></dt></dl></dd><dt>saving, <a class="indexterm" href="s1-redhat-config-kickstart-savefile.html">Saving the File</a></dt><dt>SELinux configuration, <a class="indexterm" href="s1-red
 hat-config-kickstart-firewall.html#s2-redhat-config-kickstart-firewall-selinux">SELinux Configuration</a></dt><dt>text mode installation, <a class="indexterm" href="ch-redhat-config-kickstart.html#s1-redhat-config-kickstart-basic">Basic Configuration</a></dt><dt>time zone, <a class="indexterm" href="ch-redhat-config-kickstart.html#s1-redhat-config-kickstart-basic">Basic Configuration</a></dt></dl></dd><dt>kickstart file</dt><dd><dl><dt>%include, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>%post, <a class="indexterm" href="s1-kickstart2-postinstallconfig.html">Post-installation Script</a></dt><dt>%pre, <a class="indexterm" href="s1-kickstart2-preinstallconfig.html">Pre-installation Script</a></dt><dt>auth, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>authconfig, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>autopart, <a class="indexterm" href="s1-kickstart2-
 options.html">Kickstart Options</a></dt><dt>autostep, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>bootloader, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>CD-ROM-based, <a class="indexterm" href="s1-kickstart2-putkickstarthere.html#s2-kickstart2-boot-media">Creating Kickstart Boot Media</a></dt><dt>clearpart, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>cmdline, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>creating, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>device, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>diskette-based, <a class="indexterm" href="s1-kickstart2-putkickstarthere.html#s2-kickstart2-boot-media">Creating Kickstart Boot Media</a></dt><dt>driverdisk, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Option
 s</a></dt><dt>firewall, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>firstboot, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>flash-based, <a class="indexterm" href="s1-kickstart2-putkickstarthere.html#s2-kickstart2-boot-media">Creating Kickstart Boot Media</a></dt><dt>format of, <a class="indexterm" href="s1-kickstart2-file.html">Creating the Kickstart File</a></dt><dt>graphical, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>halt, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>ignoredisk, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>include contents of another file, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>install, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>installation methods, <a class="indexter
 m" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>interactive, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>iscsi, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>key, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>keyboard, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>lang, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>langsupport, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>logging, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>logvol, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>mediacheck, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>mouse, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Op
 tions</a></dt><dt>multipath, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>network, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>network-based, <a class="indexterm" href="s2-kickstart2-networkbased.html">Making the Kickstart File Available on the Network</a>, <a class="indexterm" href="s1-kickstart2-install-tree.html">Making the Installation Tree Available</a></dt><dt>options, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dd><dl><dt>partitioning examples, <a class="indexterm" href="s1-kickstart2-options.html#s2-kickstart2-options-part-examples">Advanced Partitioning Example</a></dt></dl></dd><dt>package selection specification, <a class="indexterm" href="s1-kickstart2-packageselection.html">Package Selection</a></dt><dt>part, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>partition, <a class="indexterm" href="s1-kickstart2-o
 ptions.html">Kickstart Options</a></dt><dt>post-installation configuration, <a class="indexterm" href="s1-kickstart2-postinstallconfig.html">Post-installation Script</a></dt><dt>poweroff, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>pre-installation configuration, <a class="indexterm" href="s1-kickstart2-preinstallconfig.html">Pre-installation Script</a></dt><dt>raid, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>reboot, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>rootpw, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>selinux, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>services, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>shutdown, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>skipx, <a class="indext
 erm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>text, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>timezone, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>upgrade, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>user, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>vnc, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>volgroup, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>what it looks like, <a class="indexterm" href="s1-kickstart2-file.html">Creating the Kickstart File</a></dt><dt>xconfig, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>zerombr, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dt>zfcp, <a class="indexterm" href="s1-kickstart2-options.html">Kic
 kstart Options</a></dt></dl></dd><dt>kickstart installations, <a class="indexterm" href="ch-kickstart2.html">Kickstart Installations</a></dt><dd><dl><dt>CD-ROM-based, <a class="indexterm" href="s1-kickstart2-putkickstarthere.html#s2-kickstart2-boot-media">Creating Kickstart Boot Media</a></dt><dt>diskette-based, <a class="indexterm" href="s1-kickstart2-putkickstarthere.html#s2-kickstart2-boot-media">Creating Kickstart Boot Media</a></dt><dt>file format, <a class="indexterm" href="s1-kickstart2-file.html">Creating the Kickstart File</a></dt><dt>file locations, <a class="indexterm" href="s1-kickstart2-putkickstarthere.html">Making the Kickstart File Available</a></dt><dt>flash-based, <a class="indexterm" href="s1-kickstart2-putkickstarthere.html#s2-kickstart2-boot-media">Creating Kickstart Boot Media</a></dt><dt>installation tree, <a class="indexterm" href="s1-kickstart2-install-tree.html">Making the Installation Tree Available</a></dt><dt>LVM, <a class="indexterm" href="s1-ki
 ckstart2-options.html">Kickstart Options</a></dt><dt>network-based, <a class="indexterm" href="s2-kickstart2-networkbased.html">Making the Kickstart File Available on the Network</a>, <a class="indexterm" href="s1-kickstart2-install-tree.html">Making the Installation Tree Available</a></dt><dt>starting, <a class="indexterm" href="s1-kickstart2-startinginstall.html">Starting a Kickstart Installation</a></dt><dd><dl><dt>from a boot CD-ROM, <a class="indexterm" href="s1-kickstart2-startinginstall.html">Starting a Kickstart Installation</a></dt><dt>from CD-ROM #1 with a diskette, <a class="indexterm" href="s1-kickstart2-startinginstall.html">Starting a Kickstart Installation</a></dt></dl></dd></dl></dd></dl></div><div class="indexdiv"><h3>L</h3><dl><dt>language</dt><dd><dl><dt>selecting, <a class="indexterm" href="s1-langselection-x86.html">Language Selection</a></dt></dl></dd><dt>LILO, <a class="indexterm" href="s2-boot-init-shutdown-loader.html">The Boot Loader</a></dt><dd><dl
 ><dt>(see also boot loaders)</dt><dt>role in boot process, <a class="indexterm" href="s2-boot-init-shutdown-loader.html">The Boot Loader</a></dt></dl></dd><dt>LVM</dt><dd><dl><dt>documentation, <a class="indexterm" href="ap-techref.html">Other Technical Documentation</a></dt><dt>logical volume, <a class="indexterm" href="sn-partitioning-lvm.html">Understanding LVM</a></dt><dt>physical volume, <a class="indexterm" href="sn-partitioning-lvm.html">Understanding LVM</a></dt><dt>understanding, <a class="indexterm" href="sn-partitioning-lvm.html">Understanding LVM</a></dt><dt>volume group, <a class="indexterm" href="sn-partitioning-lvm.html">Understanding LVM</a></dt><dt>with kickstart, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>M</h3><dl><dt>master boot record, <a class="indexterm" href="s1-x86-bootloader.html">x86, AMD64, and Intel 64 Boot Loader Configuration</a></dt><dt>Master Boot Record, <a 
 class="indexterm" href="ap-rescuemode.html#s2-rescuemode-whatis-unable-boot">Unable to Boot into Fedora</a> (see MBR)</dt><dd><dl><dt>reinstalling, <a class="indexterm" href="s1-rescuemode-boot.html#s2-rescuemode-boot-reinstall-bootloader">Reinstalling the Boot Loader</a></dt></dl></dd><dt>MBR</dt><dd><dl><dt>definition of, <a class="indexterm" href="s1-boot-init-shutdown-process.html">A Detailed Look at the Boot Process</a>, <a class="indexterm" href="s1-boot-init-shutdown-process.html#s2-boot-init-shutdown-bios">The BIOS</a></dt><dd><dl><dt>(see also boot loaders)</dt><dt>(see also boot process)</dt></dl></dd><dt>installing boot loader on, <a class="indexterm" href="s1-x86-bootloader.html#x86-bootloader-adv">Advanced Boot Loader Configuration</a></dt></dl></dd><dt>memory testing mode, <a class="indexterm" href="sn-boot-modes.html#sn-memtest">Loading the Memory (RAM) Testing Mode</a></dt><dt>mirror, <a class="indexterm" href="ch-new-users.html#sn-which-download-mirror">From
  a Mirror</a></dt><dt>modem, <a class="indexterm" href="sn-networkconfig-fedora.html">Network Configuration</a></dt><dt>mount points</dt><dd><dl><dt>partitions and, <a class="indexterm" href="ch-partitions-x86.html#s2-partitions-mt-points-x86">Disk Partitions and Mount Points</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>N</h3><dl><dt>network</dt><dd><dl><dt>installations</dt><dd><dl><dt>HTTP, <a class="indexterm" href="s1-begininstall-url-x86.html">Installing via FTP or HTTP</a></dt><dt>NFS, <a class="indexterm" href="s1-begininstall-nfs-x86.html">Installing via NFS</a></dt></dl></dd></dl></dd><dt>network installation</dt><dd><dl><dt>performing, <a class="indexterm" href="s1-begininstall-perform-nfs-x86.html">Performing a Network Installation</a></dt><dt>preparing for, <a class="indexterm" href="s1-steps-network-installs-x86.html">Preparing for a Network Installation</a></dt></dl></dd><dt>NFS</dt><dd><dl><dt>installation, <a class="indexterm" href="s1-steps-network
 -installs-x86.html">Preparing for a Network Installation</a>, <a class="indexterm" href="s1-begininstall-nfs-x86.html">Installing via NFS</a></dt></dl></dd><dt>NFS (Network File System)</dt><dd><dl><dt>install from, <a class="indexterm" href="s1-begininstall-perform-nfs-x86.html">Performing a Network Installation</a></dt></dl></dd><dt>NTFS partitions</dt><dd><dl><dt>resizing, <a class="indexterm" href="sn-expert-prepare.html">Prepare for Installation</a></dt></dl></dd><dt>NTP (Network Time Protocol), <a class="indexterm" href="s1-timezone-x86.html">Time Zone Configuration</a>, <a class="indexterm" href="sn-firstboot-datetime.html">Date and Time</a></dt><dt>ntsysv, <a class="indexterm" href="s2-boot-init-shutdown-sysv-util.html">Runlevel Utilities</a></dt><dd><dl><dt>(see also services)</dt></dl></dd></dl></div><div class="indexdiv"><h3>O</h3><dl><dt>OpenSSH, <a class="indexterm" href="ap-techref.html">Other Technical Documentation</a></dt><dd><dl><dt>(see also SSH)</dt></dl>
 </dd><dt>OS/2 boot manager, <a class="indexterm" href="s1-x86-bootloader.html#x86-bootloader-adv">Advanced Boot Loader Configuration</a></dt></dl></div><div class="indexdiv"><h3>P</h3><dl><dt>package groups, <a class="indexterm" href="sn-package-selection.html">Customizing the Software Selection</a></dt><dt>packages</dt><dd><dl><dt>groups, <a class="indexterm" href="s1-pkgselection-x86.html">Package Group Selection</a></dt><dd><dl><dt>selecting, <a class="indexterm" href="s1-pkgselection-x86.html">Package Group Selection</a></dt></dl></dd><dt>installing, <a class="indexterm" href="s1-pkgselection-x86.html">Package Group Selection</a></dt><dt>selecting, <a class="indexterm" href="s1-pkgselection-x86.html">Package Group Selection</a></dt></dl></dd><dt>parted partitioning utility, <a class="indexterm" href="ch-partitions-x86.html#s4-partitions-create-new-x86">Create new partition(s)</a></dt><dt>partition</dt><dd><dl><dt>extended, <a class="indexterm" href="ch-partitions-x86.htm
 l#s2-partitions-overview-extended-x86">Partitions within Partitions â€” An Overview of Extended Partitions</a></dt><dt>illegal, <a class="indexterm" href="s2-diskpartitioning-dd-x86.html">The partitioning screen</a></dt><dt>root, <a class="indexterm" href="s2-diskpartitioning-dd-x86.html">The partitioning screen</a></dt></dl></dd><dt>partitioning, <a class="indexterm" href="s1-diskpartitioning-x86.html">Partitioning Your System</a></dt><dd><dl><dt>automatic, <a class="indexterm" href="s1-diskpartauto-x86.html">Create Default Layout</a></dt><dt>basic concepts, <a class="indexterm" href="ch-partitions-x86.html">An Introduction to Disk Partitions</a></dt><dt>creating new, <a class="indexterm" href="ch07s21s05.html">Adding Partitions</a></dt><dd><dl><dt>file system type, <a class="indexterm" href="ch07s21s05.html#s3-diskpartitioning-file-x86">File System Types</a></dt></dl></dd><dt>deleting, <a class="indexterm" href="s2-diskpartdelete-x86.html">Deleting a Partition</a></dt><dt>
 destructive, <a class="indexterm" href="ch-partitions-x86.html#s3-partitions-active-part-x86">Using Free Space from an Active Partition</a></dt><dt>editing, <a class="indexterm" href="ch07s21s06.html">Editing Partitions</a></dt><dt>extended partitions, <a class="indexterm" href="ch-partitions-x86.html#s2-partitions-overview-extended-x86">Partitions within Partitions â€” An Overview of Extended Partitions</a></dt><dt>how many partitions, <a class="indexterm" href="ch-partitions-x86.html#s2-partitions-partitioning-x86">Partitions: Turning One Drive Into Many</a>, <a class="indexterm" href="ch-partitions-x86.html#s2-partitions-how-many-x86">How Many Partitions?</a></dt><dt>introduction to, <a class="indexterm" href="ch-partitions-x86.html#s2-partitions-partitioning-x86">Partitions: Turning One Drive Into Many</a></dt><dt>making room for partitions, <a class="indexterm" href="ch-partitions-x86.html#s2-partitions-make-room-x86">Making Room For Fedora</a></dt><dt>mount points and,
  <a class="indexterm" href="ch-partitions-x86.html#s2-partitions-mt-points-x86">Disk Partitions and Mount Points</a></dt><dt>naming partitions, <a class="indexterm" href="ch-partitions-x86.html#s2-partitions-part-name-x86">Partition Naming Scheme</a></dt><dt>non-destructive, <a class="indexterm" href="ch-partitions-x86.html#s3-partitions-active-part-x86">Using Free Space from an Active Partition</a></dt><dt>numbering partitions, <a class="indexterm" href="ch-partitions-x86.html#s2-partitions-part-name-x86">Partition Naming Scheme</a></dt><dt>other operating systems, <a class="indexterm" href="ch-partitions-x86.html#s2-partitions-other-os-x86">Disk Partitions and Other Operating Systems</a></dt><dt>primary partitions, <a class="indexterm" href="ch-partitions-x86.html#s2-partitions-partitioning-x86">Partitions: Turning One Drive Into Many</a></dt><dt>recommended, <a class="indexterm" href="s2-diskpartrecommend-x86.html">Recommended Partitioning Scheme</a></dt><dt>types of part
 itions, <a class="indexterm" href="ch-partitions-x86.html#s2-partitions-partitioning-x86">Partitions: Turning One Drive Into Many</a></dt><dt>using free space, <a class="indexterm" href="ch-partitions-x86.html#s3-partitions-free-space-x86">Using Unpartitioned Free Space</a></dt><dt>using in-use partition, <a class="indexterm" href="ch-partitions-x86.html#s3-partitions-active-part-x86">Using Free Space from an Active Partition</a></dt><dt>using unused partition, <a class="indexterm" href="ch-partitions-x86.html#s3-partitions-unused-part-x86">Using Space from an Unused Partition</a></dt></dl></dd><dt>Partitioning, <a class="indexterm" href="s1-diskpartitioning-x86.html">Partitioning Your System</a></dt><dd><dl><dt>adding partitions</dt><dd><dl><dt>file system type, <a class="indexterm" href="ch07s21s05.html#s3-diskpartitioning-file-x86">File System Types</a></dt></dl></dd><dt>buttons, <a class="indexterm" href="s2-diskpartitioning-dd-x86.html">The partitioning screen</a></dt><
 dt>deleting partitions, <a class="indexterm" href="s2-diskpartdelete-x86.html">Deleting a Partition</a></dt><dt>editing partitions, <a class="indexterm" href="ch07s21s06.html">Editing Partitions</a></dt></dl></dd><dt>password</dt><dd><dl><dt>boot loader, <a class="indexterm" href="s1-x86-bootloader.html">x86, AMD64, and Intel 64 Boot Loader Configuration</a></dt><dt>setting root, <a class="indexterm" href="sn-account_configuration.html">Set the Root Password</a></dt></dl></dd><dt>programs</dt><dd><dl><dt>running at boot time, <a class="indexterm" href="s1-boot-init-shutdown-run-boot.html">Running Additional Programs at Boot Time</a></dt></dl></dd><dt>PulseAudio, <a class="indexterm" href="ap-techref.html">Other Technical Documentation</a></dt><dt>PXE (Pre-boot eXecution Environment), <a class="indexterm" href="sn-booting-from-pxe.html">Booting from the Network using PXE</a></dt><dt>PXE installations</dt><dd><dl><dt>adding hosts, <a class="indexterm" href="s1-netboot-add-host
 s.html">Adding PXE Hosts</a></dt><dt>boot message, custom, <a class="indexterm" href="s2-netboot-custom-msg.html">Adding a Custom Boot Message</a></dt><dt>configuration, <a class="indexterm" href="s1-netboot-pxe-config.html">PXE Boot Configuration</a></dt><dt>DHCP configuration, <a class="indexterm" href="ch11s05s05.html">Configuring the DHCP Server</a></dt><dt>overview, <a class="indexterm" href="sn-pxe-server-manual.html">Manually configure a PXE server</a></dt><dt>performing, <a class="indexterm" href="netboot-performing.html">Performing the PXE Installation</a></dt><dt>setting up the network server, <a class="indexterm" href="sn-pxe-server-manual.html#s1-netboot-netserver">Setting up the Network Server</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>R</h3><dl><dt>RAID</dt><dd><dl><dt>creating a software RAID, <a class="indexterm" href="s2-diskpartitioning-dd-x86.html">The partitioning screen</a></dt><dt>hardware, <a class="indexterm" href="s1-diskpartsetup-x86.htm
 l#sn-partitioning-raid">RAID and Other Disk Devices</a></dt><dt>kickstart installations, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt><dd><dl><dt>Kickstart Configurator, <a class="indexterm" href="s1-redhat-config-kickstart-partitions.html#s3-redhat-config-kickstart-raid">Creating Software RAID Partitions</a></dt></dl></dd><dt>partitioning a RAID, <a class="indexterm" href="s2-diskpartitioning-dd-x86.html">The partitioning screen</a></dt><dt>software, <a class="indexterm" href="s1-diskpartsetup-x86.html#sn-partitioning-raid">RAID and Other Disk Devices</a></dt><dt>system unbootable after disk failure, <a class="indexterm" href="s1-grub-installing.html">Installing GRUB</a></dt><dt>trouble booting from drive attached to RAID card, <a class="indexterm" href="ch-trouble-x86.html#id842934">Are You Unable to Boot With Your RAID Card?</a></dt></dl></dd><dt>rc.local</dt><dd><dl><dt>modifying, <a class="indexterm" href="s1-boot-init-shutdown-run-bo
 ot.html">Running Additional Programs at Boot Time</a></dt></dl></dd><dt>rc.serial, <a class="indexterm" href="s1-boot-init-shutdown-run-boot.html">Running Additional Programs at Boot Time</a></dt><dd><dl><dt>(see also setserial command)</dt></dl></dd><dt>re-installation, <a class="indexterm" href="ch-upgrade-x86.html#id840127">Determining Whether to Upgrade or Re-Install</a></dt><dt>removing</dt><dd><dl><dt>Fedora, <a class="indexterm" href="ch-x86-uninstall.html">Removing Fedora</a></dt></dl></dd><dt>rescue discs, <a class="indexterm" href="sn-mode-rescue.html">Booting Your Computer with the Rescue Mode</a></dt><dt>rescue mode, <a class="indexterm" href="s2-x86-bootloader-rescue.html">Rescue Mode</a>, <a class="indexterm" href="sn-mode-rescue.html">Booting Your Computer with the Rescue Mode</a></dt><dd><dl><dt>definition of, <a class="indexterm" href="s1-rescuemode-boot.html">Booting into Rescue Mode</a></dt><dt>utilities available, <a class="indexterm" href="s1-rescuemode-
 boot.html">Booting into Rescue Mode</a></dt></dl></dd><dt>root / partition</dt><dd><dl><dt>recommended partitioning, <a class="indexterm" href="s2-diskpartrecommend-x86.html">Recommended Partitioning Scheme</a></dt></dl></dd><dt>root password, <a class="indexterm" href="sn-account_configuration.html">Set the Root Password</a></dt><dt>runlevel 1, <a class="indexterm" href="s1-rescuemode-booting-single.html">Booting into Single-User Mode</a></dt><dt>runlevels (see init command)</dt><dd><dl><dt>changing with GRUB, <a class="indexterm" href="s1-grub-interfaces.html">GRUB Interfaces</a></dt><dt>configuration of, <a class="indexterm" href="s2-boot-init-shutdown-sysv-util.html">Runlevel Utilities</a></dt><dd><dl><dt>(see also services)</dt></dl></dd></dl></dd></dl></div><div class="indexdiv"><h3>S</h3><dl><dt>scp, <a class="indexterm" href="ap-techref.html">Other Technical Documentation</a></dt><dd><dl><dt>(see also SSH)</dt></dl></dd><dt>selecting</dt><dd><dl><dt>packages, <a clas
 s="indexterm" href="s1-pkgselection-x86.html">Package Group Selection</a></dt></dl></dd><dt>SELinux</dt><dd><dl><dt>documentation, <a class="indexterm" href="ap-techref.html">Other Technical Documentation</a></dt></dl></dd><dt>serial console, <a class="indexterm" href="ap-admin-options.html#sn-boot-options-interface">Configuring the Interface</a></dt><dt>serial ports (see setserial command)</dt><dt>services</dt><dd><dl><dt>configuring with chkconfig, <a class="indexterm" href="s2-boot-init-shutdown-sysv-util.html">Runlevel Utilities</a></dt><dt>configuring with ntsysv, <a class="indexterm" href="s2-boot-init-shutdown-sysv-util.html">Runlevel Utilities</a></dt><dt>configuring with Services Configuration Tool, <a class="indexterm" href="s2-boot-init-shutdown-sysv-util.html">Runlevel Utilities</a></dt></dl></dd><dt>Services Configuration Tool, <a class="indexterm" href="s2-boot-init-shutdown-sysv-util.html">Runlevel Utilities</a></dt><dd><dl><dt>(see also services)</dt></dl></d
 d><dt>setserial command</dt><dd><dl><dt>configuring, <a class="indexterm" href="s1-boot-init-shutdown-run-boot.html">Running Additional Programs at Boot Time</a></dt></dl></dd><dt>Setup Agent</dt><dd><dl><dt>via Kickstart, <a class="indexterm" href="s1-kickstart2-options.html">Kickstart Options</a></dt></dl></dd><dt>shutdown, <a class="indexterm" href="s1-boot-init-shutdown-shutdown.html">Shutting Down</a></dt><dd><dl><dt>(see also halt)</dt></dl></dd><dt>single-user mode, <a class="indexterm" href="s1-rescuemode-booting-single.html">Booting into Single-User Mode</a></dt><dt>SSH (Secure SHell)</dt><dd><dl><dt>documentation, <a class="indexterm" href="ap-techref.html">Other Technical Documentation</a></dt></dl></dd><dt>starting</dt><dd><dl><dt>installation, <a class="indexterm" href="s1-x86-starting.html">Starting the Installation Program</a>, <a class="indexterm" href="s1-begininstall-cd-inst-x86.html">Installing from DVD/CD-ROM</a></dt></dl></dd><dt>steps</dt><dd><dl><dt>di
 sk space, <a class="indexterm" href="ch03s03.html">Do You Have Enough Disk Space?</a></dt><dt>hardware compatibility, <a class="indexterm" href="sn-Is_Your_Hardware_Compatible-x86.html">Is Your Hardware Compatible?</a></dt><dt>installing with CD-ROM or DVD, <a class="indexterm" href="ch03s04.html">Can You Install Using the CD-ROM or DVD?</a></dt></dl></dd><dt>swap file</dt><dd><dl><dt>upgrade, <a class="indexterm" href="ch-upgrade-x86.html#id840127">Determining Whether to Upgrade or Re-Install</a></dt></dl></dd><dt>swap partition</dt><dd><dl><dt>recommended partitioning, <a class="indexterm" href="s2-diskpartrecommend-x86.html">Recommended Partitioning Scheme</a></dt></dl></dd><dt>syslog, <a class="indexterm" href="sn-remote-logging.html">Logging to a Remote System During the Installation</a></dt><dt>system recovery, <a class="indexterm" href="ap-rescuemode.html">Basic System Recovery</a></dt><dd><dl><dt>common problems, <a class="indexterm" href="ap-rescuemode.html#s1-rescu
 emode-common-problems">Common Problems</a></dt><dd><dl><dt>forgetting the root password, <a class="indexterm" href="ap-rescuemode.html#s2-rescuemode-root-password">Root Password</a></dt><dt>hardware/software problems, <a class="indexterm" href="ap-rescuemode.html#s2-rescuemode-hardware-troubles">Hardware/Software Problems</a></dt><dt>reinstalling the boot loader, <a class="indexterm" href="s1-rescuemode-boot.html#s2-rescuemode-boot-reinstall-bootloader">Reinstalling the Boot Loader</a></dt><dt>unable to boot into Fedora, <a class="indexterm" href="ap-rescuemode.html#s2-rescuemode-whatis-unable-boot">Unable to Boot into Fedora</a></dt></dl></dd></dl></dd><dt>system-config-kickstart (see Kickstart Configurator)</dt><dt>SysV init (see init command)</dt></dl></div><div class="indexdiv"><h3>T</h3><dl><dt>TCP/IP configuration, <a class="indexterm" href="s1-begininstall-perform-nfs-x86.html">Performing a Network Installation</a></dt><dt>Telnet, <a class="indexterm" href="sn-telnet-
 installation.html">Enabling Remote Access with Telnet</a></dt><dt>text interface, <a class="indexterm" href="ap-admin-options.html#sn-boot-options-interface">Configuring the Interface</a></dt><dt>tftp, <a class="indexterm" href="s1-netboot-tftp.html#id896172">Starting the tftp Server</a></dt><dt>time zone</dt><dd><dl><dt>configuration, <a class="indexterm" href="s1-timezone-x86.html">Time Zone Configuration</a></dt></dl></dd><dt>traceback messages</dt><dd><dl><dt>saving traceback messages without removeable media, <a class="indexterm" href="s2-trouble-tracebacks-x86.html">Saving traceback messages without removeable media</a></dt></dl></dd><dt>troubleshooting, <a class="indexterm" href="ch-trouble-x86.html">Troubleshooting Installation on an Intel or AMD System</a></dt><dd><dl><dt>after the installation, <a class="indexterm" href="ch08s04.html">Problems After Installation</a></dt><dd><dl><dt>Apache-based httpd service hangs during startup, <a class="indexterm" href="ch08s04s
 09.html">Apache-based httpd service/Sendmail Hangs During Startup</a></dt><dt>booting into a graphical environment, <a class="indexterm" href="ch08s04s02.html">Booting into a Graphical Environment</a></dt><dt>booting into GNOME or KDE, <a class="indexterm" href="ch08s04s02.html">Booting into a Graphical Environment</a></dt><dt>booting into the X Window System, <a class="indexterm" href="ch08s04s02.html">Booting into a Graphical Environment</a></dt><dt>graphical GRUB screen, <a class="indexterm" href="ch08s04.html#s2-trouble-grub">Trouble With the Graphical GRUB Screen on an x86-based System?</a></dt><dt>logging in, <a class="indexterm" href="ch08s04s05.html">Problems When You Try to Log In</a></dt><dt>printers, <a class="indexterm" href="ch08s04s07.html">Your Printer Does Not Work</a></dt><dt>RAM not recognized, <a class="indexterm" href="s2-trouble-ram.html">Is Your RAM Not Being Recognized?</a></dt><dt>Sendmail hangs during startup, <a class="indexterm" href="ch08s04s09.ht
 ml">Apache-based httpd service/Sendmail Hangs During Startup</a></dt><dt>sound configuration, <a class="indexterm" href="s2-trouble-sound.html">Problems with Sound Configuration</a></dt><dt>X (X Window System), <a class="indexterm" href="ch08s04s03.html">Problems with the X Window System (GUI)</a></dt><dt>X server crashes, <a class="indexterm" href="ch08s04s04.html">Problems with the X Server Crashing and Non-Root Users</a></dt></dl></dd><dt>beginning the installation, <a class="indexterm" href="ch08s02.html">Trouble Beginning the Installation</a></dt><dd><dl><dt>frame buffer, disabling, <a class="indexterm" href="ch08s02.html#id914845">Problems with Booting into the Graphical Installation</a></dt><dt>GUI installation method unavailable, <a class="indexterm" href="ch08s02.html#id914845">Problems with Booting into the Graphical Installation</a></dt></dl></dd><dt>booting, <a class="indexterm" href="ch-trouble-x86.html#id888245">You are unable to boot Fedora</a></dt><dd><dl><dt
 >RAID cards, <a class="indexterm" href="ch-trouble-x86.html#id842934">Are You Unable to Boot With Your RAID Card?</a></dt><dt>signal 11 error, <a class="indexterm" href="ch-trouble-x86.html#id835915">Is Your System Displaying Signal 11 Errors?</a></dt></dl></dd><dt>CD-ROM failure</dt><dd><dl><dt>CD-ROM verification, <a class="indexterm" href="ch03s06.html">Preparing for a Hard Drive Installation</a>, <a class="indexterm" href="s2-x86-starting-bootopts.html">Additional Boot Options</a></dt></dl></dd><dt>during the installation, <a class="indexterm" href="s1-trouble-install-x86.html">Trouble During the Installation</a></dt><dd><dl><dt>completing partitions, <a class="indexterm" href="s2-trouble-completeparts-x86.html">Other Partitioning Problems</a></dt><dt>No devices found to install Fedora error message, <a class="indexterm" href="s1-trouble-install-x86.html#s2-trouble-nodevicefound-x86">No devices found to install Fedora  Error Message</a></dt><dt>partition tables, <a class
 ="indexterm" href="s2-trouble-part-tables-x86.html">Trouble with Partition Tables</a></dt><dt>Python errors, <a class="indexterm" href="ch08s03s06.html">Are You Seeing Python Errors?</a></dt><dt>saving traceback messages without removeable media, <a class="indexterm" href="s2-trouble-tracebacks-x86.html">Saving traceback messages without removeable media</a></dt><dt>using remaining hard drive space, <a class="indexterm" href="s2-trouble-space-x86.html">Using Remaining Space</a></dt></dl></dd></dl></dd></dl></div><div class="indexdiv"><h3>U</h3><dl><dt>uninstalling, <a class="indexterm" href="ch-x86-uninstall.html">Removing Fedora</a></dt><dt>Update System, <a class="indexterm" href="ch-next-steps.html#sn-system-updating">Updating Your System</a></dt><dt>upgrade, <a class="indexterm" href="ch-upgrade-x86.html#id840127">Determining Whether to Upgrade or Re-Install</a></dt><dd><dl><dt>adding a swap file, <a class="indexterm" href="ch-upgrade-x86.html#id840127">Determining Wheth
 er to Upgrade or Re-Install</a></dt></dl></dd><dt>USB flash media</dt><dd><dl><dt>booting, <a class="indexterm" href="sn-start-installation.html">How Do I Start the Installation Program?</a></dt><dt>downloading, <a class="indexterm" href="ch-new-users.html#sn-howto-download">How Do I Download Installation Files?</a></dt></dl></dd><dt>USB pen card</dt><dd><dl><dt>driver image, <a class="indexterm" href="ch05s03.html#id806929">Creating a Driver Diskette from an Image File</a></dt></dl></dd><dt>USB pen drive</dt><dd><dl><dt>boot methods, <a class="indexterm" href="ch03s04.html#id825179">Alternative Boot Methods</a></dt></dl></dd><dt>user interface, graphical</dt><dd><dl><dt>installation program, <a class="indexterm" href="ch-guimode-x86.html#s1-guimode-interface-x86">The Graphical Installation Program User Interface</a></dt></dl></dd><dt>user interface, text mode</dt><dd><dl><dt>installation program, <a class="indexterm" href="s1-guimode-textinterface-x86.html">The Text Mode In
 stallation Program User Interface</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>V</h3><dl><dt>vfat (see file systems)</dt><dt>virtual consoles, <a class="indexterm" href="ch-guimode-x86.html#sn-guimode-virtual-consoles-x86">A Note about Virtual Consoles</a></dt><dt>Virtualization</dt><dd><dl><dt>documentation, <a class="indexterm" href="ap-techref.html">Other Technical Documentation</a></dt></dl></dd><dt>VNC (Virtual Network Computing), <a class="indexterm" href="sn-remoteaccess-installation.html">Enabling Remote Access to the Installation System</a></dt><dd><dl><dt>documentation, <a class="indexterm" href="ap-techref.html">Other Technical Documentation</a></dt><dt>enabling, <a class="indexterm" href="sn-remoteaccess-installation.html#sn-remoteaccess-installation-vnc">Enabling Remote Access with VNC</a></dt><dt>installing client, <a class="indexterm" href="sn-remoteaccess-installation.html">Enabling Remote Access to the Installation System</a></dt><dt>listening mode
 , <a class="indexterm" href="sn-remoteaccess-installation-vnclistener.html">Connecting the Installation System to a VNC Listener</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>X</h3><dl><dt>Xorg, <a class="indexterm" href="ap-techref.html">Other Technical Documentation</a></dt></dl></div><div class="indexdiv"><h3>Y</h3><dl><dt>yum, <a class="indexterm" href="ch-next-steps.html#sn-system-updating">Updating Your System</a></dt><dd><dl><dt>documentation, <a class="indexterm" href="ap-techref.html">Other Technical Documentation</a></dt></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="appe-Publican-Revision_History.html"><strong>Prev</strong>AppendixÂ I.Â Revision History</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li></ul></body></html>


--- NEW FILE netboot-performing.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.5.7.Â Performing the PXE Installation</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="sn-pxe-server-manual.html" title="11.5.Â Manually configure a PXE server" /><link rel="prev" href="s2-netboot-custom-msg.html" title="11.5.6.Â Adding a Custom Boot Message" /><link rel="next" href="vncwhitepaperadded.html" title="ChapterÂ 12.Â Installing Through VNC" /></head><body class="draft "><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_righ
 t.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-netboot-custom-msg.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="vncwhitepaperadded.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="netboot-performing">11.5.7.Â Performing the PXE Installation</h3></div></div></div><a id="id789880" 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">
			After the system boots the installation program, refer to the <a class="xref" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems">ChapterÂ 7, <i>Installing on Intel and AMD Systems</i></a>.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-netboot-custom-msg.html"><strong>Prev</strong>11.5.6.Â Adding a Custom Boot Message</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="vncwhitepaperadded.html"><strong>Next</strong>ChapterÂ 12.Â Installing Through VNC</a></li></ul></body></html>


--- NEW FILE pr01s02.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.Â We Need Feedback!</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="Installation-Guide-Preface.html" title="Preface" /><link rel="prev" href="Installation-Guide-Preface.html" title="Preface" /><link rel="next" href="ch-introduction.html" title="Introduction" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="
 p" href="Installation-Guide-Preface.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-introduction.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="id840214">2.Â We Need Feedback!</h2></div></div></div><a id="id840222" class="indexterm"></a><div class="para">
		If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in Bugzilla: <a href="http://bugzilla.redhat.com/bugzilla/">http://bugzilla.redhat.com/bugzilla/</a>
		against the product <span class="application"><strong>Fedora.</strong></span>
	</div><div class="para">
		When submitting a bug report, be sure to mention the manual's identifier: <em class="citetitle">Installation_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><ul class="docnav"><li class="previous"><a accesskey="p" href="Installation-Guide-Preface.html"><strong>Prev</strong>Preface</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-introduction.html"><strong>Next</strong>Introduction</a></li></ul></body></html>


--- NEW FILE pt-Advanced_installation_options.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>PartÂ III.Â Advanced installation options</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="index.html" title="Installation Guide" /><link rel="prev" href="ch08s04s09.html" title="8.4.9.Â Apache-based httpd service/Sendmail Hangs During Startup" /><link rel="next" href="ap-admin-options.html" title="ChapterÂ 9.Â Boot Options" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s04s09.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ap-admin-options.html"><strong>Next</strong></a></li></ul><div class="part" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h1 class="title" id="pt-Advanced_installation_options">PartÂ III.Â Advanced installation options</h1></div></div></div><div class="partintro" lang="en-US" xml:lang="en-US"><div></div><div class="para">
				This part of the <em class="citetitle">Fedora Installation Guide</em> covers more complex and uncommon methods of installing Fedora, including:
			</div><div class="itemizedlist"><ul><li><div class="para">
						boot options.
					</div></li><li><div class="para">
						installing without media.
					</div></li><li><div class="para">
						installing through VNC.
					</div></li><li><div class="para">
						using <span class="application"><strong>kickstart</strong></span> to automate the installation process.
					</div></li></ul></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="ap-admin-options.html">9. Boot Options</a></span></dt><dd><dl><dt><span class="section"><a href="ap-admin-options.html#sn-bootoptions-installer">9.1. Configuring the Installation System at the Boot Menu</a></span></dt><dd><dl><dt><span class="section"><a href="ap-admin-options.html#sn-boot-options-language">9.1.1. Specifying the Language</a></span></dt><dt><span class="section"><a href="ap-admin-options.html#sn-boot-options-interface">9.1.2. Configuring the Interface</a></span></dt><dt><span class="section"><a href="ap-admin-options.html#sn-boot-options-update">9.1.3. Updating anaconda</a></span></dt><dt><span class="section"><a href="ap-admin-options.html#sn-boot-options-installmethod">9.1.4. Specifying the Installation Method</a></span></dt><dt><span class="section"><a href="ap-admin-options.html#sn-boot-options-network">9.1.5. Manually Configuring the Network S
 ettings</a></span></dt></dl></dd><dt><span class="section"><a href="sn-remoteaccess-installation.html">9.2. Enabling Remote Access to the Installation System</a></span></dt><dd><dl><dt><span class="section"><a href="sn-remoteaccess-installation.html#sn-remoteaccess-installation-vnc">9.2.1. Enabling Remote Access with VNC</a></span></dt><dt><span class="section"><a href="sn-remoteaccess-installation-vnclistener.html">9.2.2. Connecting the Installation System to a VNC Listener</a></span></dt><dt><span class="section"><a href="sn-telnet-installation.html">9.2.3. Enabling Remote Access with Telnet</a></span></dt></dl></dd><dt><span class="section"><a href="sn-remote-logging.html">9.3. Logging to a Remote System During the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="sn-remote-logging.html#sn-remote-logging-logserver">9.3.1. Configuring a Log Server</a></span></dt></dl></dd><dt><span class="section"><a href="sn-automating-installation.html">9.4. Automati
 ng the Installation with Kickstart</a></span></dt><dt><span class="section"><a href="sn-bootoptions-hardware.html">9.5. Enhancing Hardware Support</a></span></dt><dd><dl><dt><span class="section"><a href="sn-bootoptions-hardware.html#sn-bootoptions-driverdisks">9.5.1. Adding Hardware Support with Driver Disks</a></span></dt><dt><span class="section"><a href="sn-bootoptions-hwdetection.html">9.5.2. Overriding Automatic Hardware Detection</a></span></dt></dl></dd><dt><span class="section"><a href="sn-boot-modes.html">9.6. Using the Maintenance Boot Modes</a></span></dt><dd><dl><dt><span class="section"><a href="sn-boot-modes.html#sn-memtest">9.6.1. Loading the Memory (RAM) Testing Mode</a></span></dt><dt><span class="section"><a href="sn-boot-mediacheck.html">9.6.2. Verifying boot media</a></span></dt><dt><span class="section"><a href="sn-mode-rescue.html">9.6.3. Booting Your Computer with the Rescue Mode</a></span></dt><dt><span class="section"><a href="sn-mode-upgradeany.htm
 l">9.6.4. Upgrading your computer</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ap-medialess-install.html">10. Installing Without Media</a></span></dt><dd><dl><dt><span class="section"><a href="ap-medialess-install.html#sn-medialess-getting-files">10.1. Retrieving Boot Files</a></span></dt><dt><span class="section"><a href="sn-medialess-editing-grub-conf.html">10.2. Editing the GRUB Configuration</a></span></dt><dt><span class="section"><a href="sn-medialess-booting.html">10.3. Booting to Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="ap-install-server.html">11. Setting Up an Installation Server</a></span></dt><dd><dl><dt><span class="section"><a href="ap-install-server.html#sn-install-cobbler">11.1. Setting Up cobbler</a></span></dt><dt><span class="section"><a href="sn-cobbler-setup-distro.html">11.2. Setting Up the Distribution</a></span></dt><dt><span class="section"><a href="sn-cobbler-mirror.html">11.3. Mirroring a Netw
 ork Location</a></span></dt><dt><span class="section"><a href="sn-cobbler-import.html">11.4. Importing the Distribution</a></span></dt><dt><span class="section"><a href="sn-pxe-server-manual.html">11.5. Manually configure a PXE server</a></span></dt><dd><dl><dt><span class="section"><a href="sn-pxe-server-manual.html#s1-netboot-netserver">11.5.1. Setting up the Network Server</a></span></dt><dt><span class="section"><a href="s1-netboot-pxe-config.html">11.5.2. PXE Boot Configuration</a></span></dt><dt><span class="section"><a href="s1-netboot-add-hosts.html">11.5.3. Adding PXE Hosts</a></span></dt><dt><span class="section"><a href="s1-netboot-tftp.html">11.5.4. TFTPD</a></span></dt><dt><span class="section"><a href="ch11s05s05.html">11.5.5. Configuring the DHCP Server</a></span></dt><dt><span class="section"><a href="s2-netboot-custom-msg.html">11.5.6. Adding a Custom Boot Message</a></span></dt><dt><span class="section"><a href="netboot-performing.html">11.5.7. Performing t
 he PXE Installation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="vncwhitepaperadded.html">12. Installing Through VNC</a></span></dt><dd><dl><dt><span class="section"><a href="vncwhitepaperadded.html#VNC_Whitepaper-vnc-viewer">12.1. VNC Viewer</a></span></dt><dt><span class="section"><a href="VNC_Whitepaper-vnc-modes-in-anaconda.html">12.2. VNC Modes in Anaconda</a></span></dt><dd><dl><dt><span class="section"><a href="VNC_Whitepaper-vnc-modes-in-anaconda.html#VNC_Whitepaper-vnc-direct-mode">12.2.1. Direct Mode</a></span></dt><dt><span class="section"><a href="VNC_Whitepaper-vnc-connect-mode.html">12.2.2. Connect Mode</a></span></dt></dl></dd><dt><span class="section"><a href="VNC_Whitepaper-installation.html">12.3. Installation Using VNC</a></span></dt><dd><dl><dt><span class="section"><a href="VNC_Whitepaper-installation.html#VNC_Whitepaper-installation-example">12.3.1. Installation Example</a></span></dt><dt><span class="section"><a href="VNC_White
 paper-kickstart-installation.html">12.3.2. Kickstart Considerations</a></span></dt><dt><span class="section"><a href="VNC_Whitepaper-firewall-considerations.html">12.3.3. Firewall Considerations</a></span></dt></dl></dd><dt><span class="section"><a href="VNC_Whitepaper-references.html">12.4. References</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-kickstart2.html">13. Kickstart Installations</a></span></dt><dd><dl><dt><span class="section"><a href="ch-kickstart2.html#s1-kickstart2-whatis">13.1. What are Kickstart Installations?</a></span></dt><dt><span class="section"><a href="s1-kickstart2-howuse.html">13.2. How Do You Perform a Kickstart Installation?</a></span></dt><dt><span class="section"><a href="s1-kickstart2-file.html">13.3. Creating the Kickstart File</a></span></dt><dt><span class="section"><a href="s1-kickstart2-options.html">13.4. Kickstart Options</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kickstart2-options.html#s2-kickstart2-
 options-part-examples">13.4.1. Advanced Partitioning Example</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kickstart2-packageselection.html">13.5. Package Selection</a></span></dt><dt><span class="section"><a href="s1-kickstart2-preinstallconfig.html">13.6. Pre-installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kickstart2-preinstallconfig.html#s2-kickstart2-prescript-example">13.6.1. Example</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kickstart2-postinstallconfig.html">13.7. Post-installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kickstart2-postinstallconfig.html#s2-kickstart2-post-examples">13.7.1. Examples</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kickstart2-putkickstarthere.html">13.8. Making the Kickstart File Available</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kickstart2-putkickstarthere.html#s2-kickstart2-boot-media">13.8.1. Creating K
 ickstart Boot Media</a></span></dt><dt><span class="section"><a href="s2-kickstart2-networkbased.html">13.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.html">13.9. Making the Installation Tree Available</a></span></dt><dt><span class="section"><a href="s1-kickstart2-startinginstall.html">13.10. Starting a Kickstart Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-redhat-config-kickstart.html">14. Kickstart Configurator</a></span></dt><dd><dl><dt><span class="section"><a href="ch-redhat-config-kickstart.html#s1-redhat-config-kickstart-basic">14.1. Basic Configuration</a></span></dt><dt><span class="section"><a href="s1-redhat-config-kickstart-install.html">14.2. Installation Method</a></span></dt><dt><span class="section"><a href="s1-redhat-config-kickstart-bootloader.html">14.3. Boot Loader Options</a></span></dt><dt><span class="section"><a href="s1-re
 dhat-config-kickstart-partitions.html">14.4. Partition Information</a></span></dt><dd><dl><dt><span class="section"><a href="s1-redhat-config-kickstart-partitions.html#s2-redhat-config-kickstart-create-part">14.4.1. Creating Partitions</a></span></dt></dl></dd><dt><span class="section"><a href="s1-redhat-config-kickstart-network.html">14.5. Network Configuration</a></span></dt><dt><span class="section"><a href="s1-redhat-config-kickstart-auth.html">14.6. Authentication</a></span></dt><dt><span class="section"><a href="s1-redhat-config-kickstart-firewall.html">14.7. Firewall Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="s1-redhat-config-kickstart-firewall.html#s2-redhat-config-kickstart-firewall-selinux">14.7.1. SELinux Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="s1-redhat-config-kickstart-xconfig.html">14.8. Display Configuration</a></span></dt><dt><span class="section"><a href="s1-redhat-config-kickstart-pkgs.html">14.
 9. Package Selection</a></span></dt><dt><span class="section"><a href="s1-redhat-config-kickstart-prescript.html">14.10. Pre-Installation Script</a></span></dt><dt><span class="section"><a href="s1-redhat-config-kickstart-postinstall.html">14.11. Post-Installation Script</a></span></dt><dd><dl><dt><span class="section"><a href="s1-redhat-config-kickstart-postinstall.html#s2-redhat-config-kickstart-nochroot">14.11.1. Chroot Environment</a></span></dt><dt><span class="section"><a href="s2-redhat-config-kickstart-interpreter.html">14.11.2. Use an Interpreter</a></span></dt></dl></dd><dt><span class="section"><a href="s1-redhat-config-kickstart-savefile.html">14.12. Saving the File</a></span></dt></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s04s09.html"><strong>Prev</strong>8.4.9.Â Apache-based httpd service/Sendmail Hangs ...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a ac
 cesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ap-admin-options.html"><strong>Next</strong>ChapterÂ 9.Â Boot Options</a></li></ul></body></html>


--- NEW FILE pt-After_installation.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>PartÂ IV.Â After installation</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="index.html" title="Installation Guide" /><link rel="prev" href="s1-redhat-config-kickstart-savefile.html" title="14.12.Â Saving the File" /><link rel="next" href="ch-firstboot.html" title="ChapterÂ 15.Â Firstboot" /></head><body class="draft "><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><ul class="docnav"><li 
 class="previous"><a accesskey="p" href="s1-redhat-config-kickstart-savefile.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-firstboot.html"><strong>Next</strong></a></li></ul><div class="part" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h1 class="title" id="pt-After_installation">PartÂ IV.Â After installation</h1></div></div></div><div class="partintro" lang="en-US" xml:lang="en-US"><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><div class="para">
						using a Fedora installation disk to rescue a damaged system.
					</div></li><li><div class="para">
						upgrading to a new version of Fedora.
					</div></li><li><div class="para">
						removing Fedora from your computer.
					</div></li></ul></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="ch-firstboot.html">15. Firstboot</a></span></dt><dd><dl><dt><span class="section"><a href="ch-firstboot.html#sn-firstboot-license">15.1. License Agreement</a></span></dt><dt><span class="section"><a href="sn-firstboot-systemuser.html">15.2. System User</a></span></dt><dt><span class="section"><a href="sn-firstboot-datetime.html">15.3. Date and Time</a></span></dt><dt><span class="section"><a href="sn-smolt.html">15.4. Hardware Profile</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-next-steps.html">16. Your Next Steps</a></span></dt><dd><dl><dt><span class="section"><a href="ch-next-steps.html#sn-system-updating">16.1. Updating Your System</a></span></dt><dt><span class="section"><a href="sn-finishing-upgrade.html">16.2. Finishing an Upgrade</a></span></dt><dt><span class="section"><a href="sn-switching-to-gui-login.html">16.3. Switching to a Graphi
 cal Login</a></span></dt><dt><span class="section"><a href="sn-news-subscriptions.html">16.4. Subscribing to Fedora Announcements and News</a></span></dt><dt><span class="section"><a href="sn-web-help.html">16.5. Finding Documentation and Support</a></span></dt><dt><span class="section"><a href="sn-community.html">16.6. Joining the Fedora Community</a></span></dt></dl></dd><dt><span class="chapter"><a href="ap-rescuemode.html">17. Basic System Recovery</a></span></dt><dd><dl><dt><span class="section"><a href="ap-rescuemode.html#s1-rescuemode-common-problems">17.1. Common Problems</a></span></dt><dd><dl><dt><span class="section"><a href="ap-rescuemode.html#s2-rescuemode-whatis-unable-boot">17.1.1. Unable to Boot into Fedora</a></span></dt><dt><span class="section"><a href="ap-rescuemode.html#s2-rescuemode-hardware-troubles">17.1.2. Hardware/Software Problems</a></span></dt><dt><span class="section"><a href="ap-rescuemode.html#s2-rescuemode-root-password">17.1.3. Root Password
 </a></span></dt></dl></dd><dt><span class="section"><a href="s1-rescuemode-boot.html">17.2. Booting into Rescue Mode</a></span></dt><dd><dl><dt><span class="section"><a href="s1-rescuemode-boot.html#s2-rescuemode-boot-reinstall-bootloader">17.2.1. Reinstalling the Boot Loader</a></span></dt></dl></dd><dt><span class="section"><a href="s1-rescuemode-booting-single.html">17.3. Booting into Single-User Mode</a></span></dt><dt><span class="section"><a href="s1-rescuemode-booting-emergency.html">17.4. Booting into Emergency Mode</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-upgrade-x86.html">18. Upgrading Your Current System</a></span></dt><dd><dl><dt><span class="section"><a href="ch-upgrade-x86.html#id840127">18.1. Determining Whether to Upgrade or Re-Install</a></span></dt><dt><span class="section"><a href="ch18s02.html">18.2. Upgrading Your System</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-x86-uninstall.html">19. Removing Fedora</a></span>
 </dt><dd><dl><dt><span class="section"><a href="ch-x86-uninstall.html#sn-x86-uninstall-single">19.1. Fedora is the only operating system on the computer</a></span></dt><dt><span class="section"><a href="sn-x86-uninstall-dual.html">19.2. Your computer dual-boots Fedora and another operating system</a></span></dt><dd><dl><dt><span class="section"><a href="sn-x86-uninstall-dual.html#sn-x86-uninstall-dual-windows">19.2.1. Your computer dual-boots Fedora and a Microsoft Windows operating system</a></span></dt><dt><span class="section"><a href="sn-x86-uninstall-dual-mac.html">19.2.2. Your computer dual-boots Fedora and Mac OS X</a></span></dt><dt><span class="section"><a href="sn-x86-uninstall-dual-linux.html">19.2.3. Your computer dual-boots Fedora and a different Linux distribution</a></span></dt></dl></dd><dt><span class="section"><a href="sn-x86-uninstall-legacy.html">19.3. Replacing Fedora with MS-DOS or legacy versions of Microsoft Windows</a></span></dt></dl></dd></dl></div
 ></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-redhat-config-kickstart-savefile.html"><strong>Prev</strong>14.12.Â Saving the File</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-firstboot.html"><strong>Next</strong>ChapterÂ 15.Â Firstboot</a></li></ul></body></html>


--- NEW FILE pt-Before_you_begin.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>PartÂ I.Â Before you begin</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="index.html" title="Installation Guide" /><link rel="prev" href="sn-start-installation.html" title="2.6.Â How Do I Start the Installation Program?" /><link rel="next" href="ch-steps-x86.html" title="ChapterÂ 3.Â Steps to Get You Started" /></head><body class="draft "><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><ul
  class="docnav"><li class="previous"><a accesskey="p" href="sn-start-installation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-steps-x86.html"><strong>Next</strong></a></li></ul><div class="part" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h1 class="title" id="pt-Before_you_begin">PartÂ I.Â Before you begin</h1></div></div></div><div class="partintro" lang="en-US" xml:lang="en-US"><div></div><div class="para">
				This part of the <em class="citetitle">Fedora Installation Guide</em> covers decisions that you should make and resources that you should gather before installing Fedora, including:
			</div><div class="itemizedlist"><ul><li><div class="para">
						the decision whether to upgrade an existing installation of Fedora or install a new copy.
					</div></li><li><div class="para">
						hardware considerations, and hardware details that you may need during installation.
					</div></li><li><div class="para">
						preparing to install Fedora over a network.
					</div></li><li><div class="para">
						preparing driver media.
					</div></li></ul></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="ch-steps-x86.html">3. Steps to Get You Started</a></span></dt><dd><dl><dt><span class="section"><a href="ch-steps-x86.html#id787237">3.1. Upgrade or Install?</a></span></dt><dt><span class="section"><a href="sn-Is_Your_Hardware_Compatible-x86.html">3.2. Is Your Hardware Compatible?</a></span></dt><dt><span class="section"><a href="ch03s03.html">3.3. Do You Have Enough Disk Space?</a></span></dt><dt><span class="section"><a href="ch03s04.html">3.4. Can You Install Using the CD-ROM or DVD?</a></span></dt><dd><dl><dt><span class="section"><a href="ch03s04.html#id825179">3.4.1. Alternative Boot Methods</a></span></dt><dt><span class="section"><a href="s2-steps-make-cd.html">3.4.2. Making an Installation Boot CD-ROM</a></span></dt></dl></dd><dt><span class="section"><a href="s1-steps-network-installs-x86.html">3.5. Preparing for a Network Installation</a></span></dt><d
 d><dl><dt><span class="section"><a href="s1-steps-network-installs-x86.html#id799943">3.5.1. Preparing for FTP and HTTP installation</a></span></dt><dt><span class="section"><a href="ch03s05s02.html">3.5.2. Preparing for an NFS install</a></span></dt></dl></dd><dt><span class="section"><a href="ch03s06.html">3.6. Preparing for a Hard Drive Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-ent-table.html">4. System Specifications List</a></span></dt><dt><span class="chapter"><a href="ch-driverdisk-x86.html">5. Driver Media for Intel and AMD Systems</a></span></dt><dd><dl><dt><span class="section"><a href="ch-driverdisk-x86.html#id808556">5.1. Why Do I Need Driver Media?</a></span></dt><dt><span class="section"><a href="ch05s02.html">5.2. So What Is Driver Media Anyway?</a></span></dt><dt><span class="section"><a href="ch05s03.html">5.3. How Do I Obtain Driver Media?</a></span></dt><dd><dl><dt><span class="section"><a href="ch05s03.html#id806929">5.3.
 1. Creating a Driver Diskette from an Image File</a></span></dt></dl></dd><dt><span class="section"><a href="ch05s04.html">5.4. Using a Driver Image During Installation</a></span></dt></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-start-installation.html"><strong>Prev</strong>2.6.Â How Do I Start the Installation Program?</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-steps-x86.html"><strong>Next</strong>ChapterÂ 3.Â Steps to Get You Started</a></li></ul></body></html>


--- NEW FILE pt-Technical_appendixes.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>PartÂ V.Â Technical appendixes</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="index.html" title="Installation Guide" /><link rel="prev" href="sn-x86-uninstall-legacy.html" title="19.3.Â Replacing Fedora with MS-DOS or legacy versions of Microsoft Windows" /><link rel="next" href="ch-partitions-x86.html" title="AppendixÂ A.Â An Introduction to Disk Partitions" /></head><body class="draft "><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/imag
 e_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-x86-uninstall-legacy.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-partitions-x86.html"><strong>Next</strong></a></li></ul><div class="part" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h1 class="title" id="pt-Technical_appendixes">PartÂ V.Â Technical appendixes</h1></div></div></div><div class="partintro" lang="en-US" xml:lang="en-US"><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><b>Table of Contents</b></p><dl><dt><span class="appendix"><a href="ch-partitions-x86.html">A. An Introduction to Disk Partitions</a></span></dt><dd><dl><dt><span class="section"><a href="ch-partitions-x86.html#s1-partitions-concepts-x86">A.1. Hard Disk Basic Concepts</a></span></dt><dd><dl><dt><span class="section"><a href="ch-partitions-x86.html#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="ch-partitions-x86.html#s2-partitions-partitioning-x86">A.1.2. Partitions: Turning One Drive Into Many</a></span></dt><dt><span class="section"><a href="ch-partitions-x86.html#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="ch-partitions-x86.html#s2-partitions-make-room-x86">A.1.4. Making Room For Fedora</a></span></dt><dt><span class="section"><a href="ch-par
 titions-x86.html#s2-partitions-part-name-x86">A.1.5. Partition Naming Scheme</a></span></dt><dt><span class="section"><a href="ch-partitions-x86.html#s2-partitions-other-os-x86">A.1.6. Disk Partitions and Other Operating Systems</a></span></dt><dt><span class="section"><a href="ch-partitions-x86.html#s2-partitions-mt-points-x86">A.1.7. Disk Partitions and Mount Points</a></span></dt><dt><span class="section"><a href="ch-partitions-x86.html#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.html">B. ISCSI disks</a></span></dt><dd><dl><dt><span class="section"><a href="ISCSI_disks.html#sn-iSCSI_in_Fedora-iSCSI_disks_in_anaconda">B.1. iSCSI disks in anaconda</a></span></dt><dt><span class="section"><a href="sn-iSCSI_disks_during_start_up.html">B.2. iSCSI disks during start up</a></span></dt></dl></dd><dt><span class="appendix"><a href="Disk_Encryption_Guide.html">C. Disk Encryption Guide</a>
 </span></dt><dd><dl><dt><span class="section"><a href="Disk_Encryption_Guide.html#id873270">C.1. What is block device encryption? </a></span></dt><dt><span class="section"><a href="apcs02.html">C.2. Encrypting block devices using dm-crypt/LUKS </a></span></dt><dd><dl><dt><span class="section"><a href="apcs02.html#id785142">C.2.1. Overview of LUKS </a></span></dt><dt><span class="section"><a href="apcs02s02.html">C.2.2. How will I access the encrypted devices after installation? (System Startup) </a></span></dt><dt><span class="section"><a href="apcs02s03.html">C.2.3. Choosing a Good Passphrase </a></span></dt></dl></dd><dt><span class="section"><a href="apcs03.html">C.3. Creating Encrypted Block Devices in Anaconda </a></span></dt><dd><dl><dt><span class="section"><a href="apcs03.html#id906052">C.3.1. What Kinds of Block Devices Can Be Encrypted? </a></span></dt><dt><span class="section"><a href="apcs03s02.html">C.3.2. Limitations of Anaconda's Block Device Encryption Suppor
 t </a></span></dt></dl></dd><dt><span class="section"><a href="apcs04.html">C.4. Creating Encrypted Block Devices on the Installed System After Installation </a></span></dt><dd><dl><dt><span class="section"><a href="apcs04.html#id885513">C.4.1. Create the block devices </a></span></dt><dt><span class="section"><a href="randomize_device.html">C.4.2. Optional: Fill the device with random data</a></span></dt><dt><span class="section"><a href="apcs04s03.html">C.4.3. Format the device as a dm-crypt/LUKS encrypted device </a></span></dt><dt><span class="section"><a href="apcs04s04.html">C.4.4. Create a mapping to allow access to the device's decrypted contents </a></span></dt><dt><span class="section"><a href="apcs04s05.html">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="apcs04s06.html">C.4.6. Add the mapping information to /etc/crypttab</a></span></dt><dt><
 span class="section"><a href="apcs04s07.html">C.4.7. Add an entry to /etc/fstab</a></span></dt></dl></dd><dt><span class="section"><a href="apcs05.html">C.5. Common Post-Installation Tasks </a></span></dt><dd><dl><dt><span class="section"><a href="apcs05.html#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="apcs05s02.html">C.5.2. Add a new passphrase to an existing device </a></span></dt><dt><span class="section"><a href="apcs05s03.html">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.html">D. Understanding LVM</a></span></dt><dt><span class="appendix"><a href="ch-grub.html">E. The GRUB Boot Loader</a></span></dt><dd><dl><dt><span class="section"><a href="ch-grub.html#s1-grub-whatis">E.1. GRUB</a></span></dt><dd><dl><dt><span class="section"><a href="ch-grub.html#s2-grub-whatis-booti
 ng">E.1.1. GRUB and the x86 Boot Process</a></span></dt><dt><span class="section"><a href="ch-grub.html#s2-grub-whatis-features">E.1.2. Features of GRUB</a></span></dt></dl></dd><dt><span class="section"><a href="s1-grub-installing.html">E.2. Installing GRUB</a></span></dt><dt><span class="section"><a href="s1-grub-terminology.html">E.3. GRUB Terminology</a></span></dt><dd><dl><dt><span class="section"><a href="s1-grub-terminology.html#s2-grub-terminology-devices">E.3.1. Device Names</a></span></dt><dt><span class="section"><a href="s2-grub-terminology-files.html">E.3.2. File Names and Blocklists</a></span></dt><dt><span class="section"><a href="s2-grub-terminology-rootfs.html">E.3.3. The Root File System and GRUB</a></span></dt></dl></dd><dt><span class="section"><a href="s1-grub-interfaces.html">E.4. GRUB Interfaces</a></span></dt><dd><dl><dt><span class="section"><a href="s1-grub-interfaces.html#s2-grub-interfaces-orderofuse">E.4.1. Interfaces Load Order</a></span></dt></
 dl></dd><dt><span class="section"><a href="s1-grub-commands.html">E.5. GRUB Commands</a></span></dt><dt><span class="section"><a href="s1-grub-configfile.html">E.6. GRUB Menu Configuration File</a></span></dt><dd><dl><dt><span class="section"><a href="s1-grub-configfile.html#s2-grub-configfile-structure">E.6.1. Configuration File Structure</a></span></dt><dt><span class="section"><a href="s2-grub-configfile-commands.html">E.6.2. Configuration File Directives</a></span></dt></dl></dd><dt><span class="section"><a href="s1-grub-runlevels.html">E.7. Changing Runlevels at Boot Time</a></span></dt><dt><span class="section"><a href="s1-grub-additional-resources.html">E.8. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-grub-additional-resources.html#s2-grub-installed-documentation">E.8.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-grub-useful-websites.html">E.8.2. Useful Websites</a></span></dt><dt><span class="sec
 tion"><a href="s2-grub-related-books.html">E.8.3. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="ch-boot-init-shutdown.html">F. Boot Process, Init, and Shutdown</a></span></dt><dd><dl><dt><span class="section"><a href="ch-boot-init-shutdown.html#s1-boot-process-basics">F.1. The Boot Process</a></span></dt><dt><span class="section"><a href="s1-boot-init-shutdown-process.html">F.2. A Detailed Look at the Boot Process</a></span></dt><dd><dl><dt><span class="section"><a href="s1-boot-init-shutdown-process.html#s2-boot-init-shutdown-bios">F.2.1. The BIOS</a></span></dt><dt><span class="section"><a href="s2-boot-init-shutdown-loader.html">F.2.2. The Boot Loader</a></span></dt><dt><span class="section"><a href="s2-boot-init-shutdown-kernel.html">F.2.3. The Kernel</a></span></dt><dt><span class="section"><a href="s2-boot-init-shutdown-init.html">F.2.4. The /sbin/init Program</a></span></dt></dl></dd><dt><span class="section"><a href="s1-boot-ini
 t-shutdown-run-boot.html">F.3. Running Additional Programs at Boot Time</a></span></dt><dt><span class="section"><a href="s1-boot-init-shutdown-sysv.html">F.4. SysV Init Runlevels</a></span></dt><dd><dl><dt><span class="section"><a href="s1-boot-init-shutdown-sysv.html#s2-init-boot-shutdown-rl">F.4.1. Runlevels</a></span></dt><dt><span class="section"><a href="s2-boot-init-shutdown-sysv-util.html">F.4.2. Runlevel Utilities</a></span></dt></dl></dd><dt><span class="section"><a href="s1-boot-init-shutdown-shutdown.html">F.5. Shutting Down</a></span></dt></dl></dd><dt><span class="appendix"><a href="ap-techref.html">G. Other Technical Documentation</a></span></dt></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-x86-uninstall-legacy.html"><strong>Prev</strong>19.3.Â Replacing Fedora with MS-DOS or legacy vers...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html">
 <strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-partitions-x86.html"><strong>Next</strong>AppendixÂ A.Â An Introduction to Disk Partitions</a></li></ul></body></html>


--- NEW FILE pt-The_installation_process.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>PartÂ II.Â The installation process</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="index.html" title="Installation Guide" /><link rel="prev" href="ch05s04.html" title="5.4.Â Using a Driver Image During Installation" /><link rel="next" href="ch-beginninginstallation.html" title="ChapterÂ 6.Â Beginning the Installation" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch05s04.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-beginninginstallation.html"><strong>Next</strong></a></li></ul><div class="part" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h1 class="title" id="pt-The_installation_process">PartÂ II.Â The installation process</h1></div></div></div><div class="partintro" lang="en-US" xml:lang="en-US"><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><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="ch-beginninginstallation.html">6. Beginning the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="ch-beginninginstallation.html#sn-boot-menu">6.1. The Boot Menu</a></span></dt><dt><span class="section"><a href="sn-install-diff-source.html">6.2. Installing from a Different Source</a></span></dt><dt><span class="section"><a href="sn-verifying-media.html">6.3. Verifying Media</a></span></dt><dd><dl><dt><span class="section"><a href="sn-verifying-media.html#sn-verifying-livecd">6.3.1. Verifying the Live CD</a></span></dt><dt><span class="section"><a href="sn-verifying-dvd.html">6.3.2. Verifying the DVD</a></span></dt></dl></dd><dt><span class="section"><a href="sn-booting-from-pxe.html">6.4. Booting from the Network using PXE</a></span></dt><dt><span class="section"><a href="sn-graphics-problem.html">6.5. Graphical and Text Interfaces</a></span></dt></dl></dd><dt><
 span class="chapter"><a href="ch-guimode-x86.html">7. Installing on Intel and AMD Systems</a></span></dt><dd><dl><dt><span class="section"><a href="ch-guimode-x86.html#s1-guimode-interface-x86">7.1. The Graphical Installation Program User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="ch-guimode-x86.html#sn-guimode-virtual-consoles-x86">7.1.1. A Note about Virtual Consoles</a></span></dt></dl></dd><dt><span class="section"><a href="s1-guimode-textinterface-x86.html">7.2. The Text Mode Installation Program User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="s1-guimode-textinterface-x86.html#id834187">7.2.1. Using the Keyboard to Navigate</a></span></dt></dl></dd><dt><span class="section"><a href="s1-x86-starting.html">7.3. Starting the Installation Program</a></span></dt><dd><dl><dt><span class="section"><a href="s1-x86-starting.html#s2-x86-starting-booting">7.3.1. Booting the Installation Program on x86, AMD64, and Intel 64 Systems</
 a></span></dt><dt><span class="section"><a href="s2-x86-starting-bootopts.html">7.3.2. Additional Boot Options</a></span></dt></dl></dd><dt><span class="section"><a href="s1-installmethod.html">7.4. Selecting an Installation Method</a></span></dt><dt><span class="section"><a href="s1-begininstall-cd-inst-x86.html">7.5. Installing from DVD/CD-ROM</a></span></dt><dd><dl><dt><span class="section"><a href="s1-begininstall-cd-inst-x86.html#s2-begininstall-unrec-ide-x86">7.5.1. What If the IDE CD-ROM Was Not Found?</a></span></dt></dl></dd><dt><span class="section"><a href="s1-begininstall-hd-x86.html">7.6. Installing from a Hard Drive</a></span></dt><dt><span class="section"><a href="s1-begininstall-perform-nfs-x86.html">7.7. Performing a Network Installation</a></span></dt><dt><span class="section"><a href="s1-begininstall-nfs-x86.html">7.8. Installing via NFS</a></span></dt><dt><span class="section"><a href="s1-begininstall-url-x86.html">7.9. Installing via FTP or HTTP</a></spa
 n></dt><dt><span class="section"><a href="sn-welcome-x86.html">7.10. Welcome to Fedora</a></span></dt><dt><span class="section"><a href="s1-langselection-x86.html">7.11. Language Selection</a></span></dt><dt><span class="section"><a href="ch07s12.html">7.12. Keyboard Configuration</a></span></dt><dt><span class="section"><a href="sn-initialize-hdd.html">7.13. Initializing the Hard Disk</a></span></dt><dt><span class="section"><a href="sn-upgrading-system.html">7.14. Upgrading an Existing System</a></span></dt><dd><dl><dt><span class="section"><a href="sn-upgrading-system.html#sn-upgrade-examine">7.14.1. Upgrade Examine</a></span></dt><dt><span class="section"><a href="sn-upgrade-tree.html">7.14.2. Upgrading Using the Installer</a></span></dt><dt><span class="section"><a href="sn-upgrading-bootloader.html">7.14.3. Upgrading Boot Loader Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="sn-networkconfig-fedora.html">7.15. Network Configuration</a></span>
 </dt><dd><dl><dt><span class="section"><a href="sn-networkconfig-fedora.html#sn-networkconfig-fedora_manual-configuration">7.15.1. Manual configuration</a></span></dt></dl></dd><dt><span class="section"><a href="s1-timezone-x86.html">7.16. Time Zone Configuration</a></span></dt><dt><span class="section"><a href="sn-account_configuration.html">7.17. Set the Root Password</a></span></dt><dt><span class="section"><a href="s1-diskpartsetup-x86.html">7.18. Disk Partitioning Setup</a></span></dt><dd><dl><dt><span class="section"><a href="s1-diskpartsetup-x86.html#sn-partitioning-raid">7.18.1. RAID and Other Disk Devices</a></span></dt></dl></dd><dt><span class="section"><a href="s1-advanced-storage-x86.html">7.19.  Advanced Storage Options </a></span></dt><dt><span class="section"><a href="s1-diskpartauto-x86.html">7.20. Create Default Layout</a></span></dt><dt><span class="section"><a href="s1-diskpartitioning-x86.html">7.21. Partitioning Your System</a></span></dt><dd><dl><dt><s
 pan class="section"><a href="s1-diskpartitioning-x86.html#id888157">7.21.1. Graphical Display of Hard Drive(s)</a></span></dt><dt><span class="section"><a href="s2-diskpartitioning-dd-x86.html">7.21.2. The partitioning screen</a></span></dt><dt><span class="section"><a href="ch07s21s03.html">7.21.3. Partition Fields</a></span></dt><dt><span class="section"><a href="s2-diskpartrecommend-x86.html">7.21.4. Recommended Partitioning Scheme</a></span></dt><dt><span class="section"><a href="ch07s21s05.html">7.21.5. Adding Partitions</a></span></dt><dt><span class="section"><a href="ch07s21s06.html">7.21.6. Editing Partitions</a></span></dt><dt><span class="section"><a href="s2-diskpartdelete-x86.html">7.21.7. Deleting a Partition</a></span></dt></dl></dd><dt><span class="section"><a href="s1-x86-bootloader.html">7.22. x86, AMD64, and Intel 64 Boot Loader Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="s1-x86-bootloader.html#x86-bootloader-adv">7.22.1. Advanc
 ed Boot Loader Configuration</a></span></dt><dt><span class="section"><a href="s2-x86-bootloader-rescue.html">7.22.2. Rescue Mode</a></span></dt><dt><span class="section"><a href="s2-x86-bootloader-alt.html">7.22.3. Alternative Boot Loaders</a></span></dt></dl></dd><dt><span class="section"><a href="s1-pkgselection-x86.html">7.23. Package Group Selection</a></span></dt><dd><dl><dt><span class="section"><a href="s1-pkgselection-x86.html#sn-additional-repos">7.23.1. Installing from Additional Repositories</a></span></dt><dt><span class="section"><a href="sn-package-selection.html">7.23.2. Customizing the Software Selection</a></span></dt></dl></dd><dt><span class="section"><a href="s1-preparetoinstall-x86.html">7.24. Preparing to Install</a></span></dt><dd><dl><dt><span class="section"><a href="s1-preparetoinstall-x86.html#id838976">7.24.1.  Prepare to Install </a></span></dt></dl></dd><dt><span class="section"><a href="s1-installpkgs-x86.html">7.25. Installing Packages</a></s
 pan></dt><dt><span class="section"><a href="s1-complete-x86.html">7.26. Installation Complete</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-trouble-x86.html">8. Troubleshooting Installation on an Intel or AMD System</a></span></dt><dd><dl><dt><span class="section"><a href="ch-trouble-x86.html#id888245">8.1. You are unable to boot Fedora</a></span></dt><dd><dl><dt><span class="section"><a href="ch-trouble-x86.html#id842934">8.1.1. Are You Unable to Boot With Your RAID Card?</a></span></dt><dt><span class="section"><a href="ch-trouble-x86.html#id835915">8.1.2. Is Your System Displaying Signal 11 Errors?</a></span></dt></dl></dd><dt><span class="section"><a href="ch08s02.html">8.2. Trouble Beginning the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="ch08s02.html#id914845">8.2.1. Problems with Booting into the Graphical Installation</a></span></dt></dl></dd><dt><span class="section"><a href="s1-trouble-install-x86.html">8.3. Trouble Durin
 g the Installation</a></span></dt><dd><dl><dt><span class="section"><a href="s1-trouble-install-x86.html#s2-trouble-nodevicefound-x86">8.3.1. No devices found to install Fedora  Error Message</a></span></dt><dt><span class="section"><a href="s2-trouble-tracebacks-x86.html">8.3.2. Saving traceback messages without removeable media</a></span></dt><dt><span class="section"><a href="s2-trouble-part-tables-x86.html">8.3.3. Trouble with Partition Tables</a></span></dt><dt><span class="section"><a href="s2-trouble-space-x86.html">8.3.4. Using Remaining Space</a></span></dt><dt><span class="section"><a href="s2-trouble-completeparts-x86.html">8.3.5. Other Partitioning Problems</a></span></dt><dt><span class="section"><a href="ch08s03s06.html">8.3.6. Are You Seeing Python Errors?</a></span></dt></dl></dd><dt><span class="section"><a href="ch08s04.html">8.4. Problems After Installation</a></span></dt><dd><dl><dt><span class="section"><a href="ch08s04.html#s2-trouble-grub">8.4.1. Troub
 le With the Graphical GRUB Screen on an x86-based System?</a></span></dt><dt><span class="section"><a href="ch08s04s02.html">8.4.2. Booting into a Graphical Environment</a></span></dt><dt><span class="section"><a href="ch08s04s03.html">8.4.3. Problems with the X Window System (GUI)</a></span></dt><dt><span class="section"><a href="ch08s04s04.html">8.4.4. Problems with the X Server Crashing and Non-Root Users</a></span></dt><dt><span class="section"><a href="ch08s04s05.html">8.4.5. Problems When You Try to Log In</a></span></dt><dt><span class="section"><a href="s2-trouble-ram.html">8.4.6. Is Your RAM Not Being Recognized?</a></span></dt><dt><span class="section"><a href="ch08s04s07.html">8.4.7. Your Printer Does Not Work</a></span></dt><dt><span class="section"><a href="s2-trouble-sound.html">8.4.8. Problems with Sound Configuration</a></span></dt><dt><span class="section"><a href="ch08s04s09.html">8.4.9. Apache-based httpd service/Sendmail Hangs During Startup</a></span></d
 t></dl></dd></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch05s04.html"><strong>Prev</strong>5.4.Â Using a Driver Image During Installation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-beginninginstallation.html"><strong>Next</strong>ChapterÂ 6.Â Beginning the Installation</a></li></ul></body></html>


--- NEW FILE randomize_device.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>C.4.2.Â Optional: Fill the device with random data</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="apcs04.html" title="C.4.Â Creating Encrypted Block Devices on the Installed System After Installation" /><link rel="prev" href="apcs04.html" title="C.4.Â Creating Encrypted Block Devices on the Installed System After Installation" /><link rel="next" href="apcs04s03.html" title="C.4.3.Â Format the device as a dm-crypt/LUKS encrypted device" /></head><body class="draft "><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="ri
 ght" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs04.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apcs04s03.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="randomize_device">C.4.2.Â Optional: Fill the device with random data</h3></div></div></div><div class="para">
				Filling <device> (eg: <code class="filename">/dev/sda3</code>) with random data before encrypting it greatly increases the strength of the encryption. The downside is that it can take a very long time.
			</div><div class="para">
				<div class="warning"><h2>Warning</h2><div class="para">
						The commands below will destroy any existing data on the device.
					</div></div>
			</div><div class="itemizedlist"><ul><li><div class="para">
						The best way, which provides high quality random data but takes a long time (several minutes per gigabyte on most systems):
<pre class="programlisting">dd if=/dev/urandom of=<device>
</pre>
					</div></li><li><div class="para">
						Fastest way, which provides lower quality random data:
<pre class="programlisting">badblocks -c 10240 -s -w -t random -v <device>
</pre>
					</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs04.html"><strong>Prev</strong>C.4.Â Creating Encrypted Block Devices on the Inst...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="apcs04s03.html"><strong>Next</strong>C.4.3.Â Format the device as a dm-crypt/LUKS encry...</a></li></ul></body></html>


--- NEW FILE s1-advanced-storage-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.19.Â  Advanced Storage Options</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="s1-diskpartsetup-x86.html" title="7.18.Â Disk Partitioning Setup" /><link rel="next" href="s1-diskpartauto-x86.html" title="7.20.Â Create Default Layout" /></head><body class="draft "><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="Documen
 tation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-diskpartsetup-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-diskpartauto-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-advanced-storage-x86">7.19.Â  Advanced Storage Options </h2></div></div></div><a id="id849176" class="indexterm"></a><a id="id833213" class="indexterm"></a><div class="figure" id="id834049"><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.
			</div></div></div></div><h6>FigureÂ 7.16.Â Advanced Storage Options</h6></div><br class="figure-break" /><div class="para">
	From this screen you can choose to disable a dmraid device, in which case the individual elements of the dmraid device will appear as separate hard drives. You can also choose to configure an iSCSI (SCSI over TCP/IP) target. See <a class="xref" href="ISCSI_disks.html" title="AppendixÂ B.Â ISCSI disks">AppendixÂ B, <i>ISCSI disks</i></a> for an introduction to iSCSI.
</div><div class="para">
	To configure an ISCSI target invoke the 'Configure ISCSI Parameters' dialog by selecting 'Add ISCSI target' and clicking on the 'Add Drive' button. Fill in the details for the ISCSI target IP and provide a unique ISCSI initiator name to identify this system. If the ISCSI target uses CHAP (Challenge Handshake Authentication Protocol) for authentication, enter the CHAP username and password. If your enviroment uses 2-way CHAP (also called "Mutual CHAP"), also enter the reverse CHAP username and password. Click the 'Add target' button to attempt connection to the ISCSI target using this information.
</div><div class="figure" id="id863928"><div class="figure-contents"><div class="mediaobject"><img src="images/diskpartadvanced/iscsi-config.png" alt="Configure ISCSI Parameters" /><div class="longdesc"><div class="para">
				Configure ISCSI Parameters.
			</div></div></div></div><h6>FigureÂ 7.17.Â Configure ISCSI Parameters</h6></div><br class="figure-break" /><div class="para">
	Please note that you will be able to reattempt with a different ISCSI target IP should you enter it incorrectly, but in order to change the ISCSI initiator name you will need to restart the installation.
</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-diskpartsetup-x86.html"><strong>Prev</strong>7.18.Â Disk Partitioning Setup</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-diskpartauto-x86.html"><strong>Next</strong>7.20.Â Create Default Layout</a></li></ul></body></html>


--- NEW FILE s1-begininstall-cd-inst-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.5.Â Installing from DVD/CD-ROM</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="s1-installmethod.html" title="7.4.Â Selecting an Installation Method" /><link rel="next" href="s1-begininstall-hd-x86.html" title="7.6.Â Installing from a Hard Drive" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-installmethod.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-begininstall-hd-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-begininstall-cd-inst-x86">7.5.Â Installing from DVD/CD-ROM</h2></div></div></div><a id="id944093" class="indexterm"></a><a id="id867897" class="indexterm"></a><a id="id877570" class="indexterm"></a><a id="id887212" class="indexterm"></a><a id="id853948" class="indexterm"></a><a id="id827917" class="indexterm"></a><div class="para">
	To install Fedora from a DVD/CD-ROM, place the DVD or CD #1 in your DVD/CD-ROM drive and boot your system from the DVD/CD-ROM. Even if you booted from alternative media, you can still install Fedora from CD or DVD media.
</div><div class="para">
		The installation program then probes your system and attempts to identify your CD-ROM drive. It starts by looking for an IDE (also known as an ATAPI) CD-ROM drive.
	</div><div class="note"><h2>Note</h2><a id="id905961" class="indexterm"></a><a id="id842191" 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>About to Install</strong></span> screen. Refer to <a class="xref" href="s1-preparetoinstall-x86.html" title="7.24.Â Preparing to Install">SectionÂ 7.24, â€œPreparing to Installâ€</a> for more information.
		</div></div><a id="id871675" class="indexterm"></a><div class="para">
	If your CD-ROM drive is not detected, and it is a SCSI CD-ROM, 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/CD-ROM drive is found and the driver loaded, the installer will present you with the option to perform a media check on the DVD/CD-ROM. 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-welcome-x86.html" title="7.10.Â Welcome to Fedora">SectionÂ 7.10, â€œWelcome to Fedoraâ€</a>).
	</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-begininstall-unrec-ide-x86">7.5.1.Â What If the IDE CD-ROM Was Not Found?</h3></div></div></div><a id="id924342" class="indexterm"></a><a id="id885651" class="indexterm"></a><a id="id830571" class="indexterm"></a><a id="id844675" class="indexterm"></a><a id="id845710" class="indexterm"></a><div class="para">
	If you have an IDE (ATAPI) DVD/CD-ROM but the installation program fails to find it and asks you what type of DVD/CD-ROM drive you have, try the following boot command. Restart the installation, and at the <code class="prompt">boot:</code> prompt enter <strong class="userinput"><code>linux hd<em class="replaceable"><code>X</code></em>=cdrom</code></strong>. Replace <strong class="userinput"><code><em class="replaceable"><code>X</code></em></code></strong> with one of the following letters, depending on the interface the unit is connected to, and whether it is configured as master or slave (also known as primary and secondary):
</div><div class="itemizedlist"><ul><li><div class="para">
			<code class="command">a</code> â€” first IDE controller, master
		</div></li><li><div class="para">
			<code class="command">b</code> â€” first IDE controller, slave
		</div></li><li><div class="para">
			<code class="command">c</code> â€” second IDE controller, master
		</div></li><li><div class="para">
			<code class="command">d</code> â€” second IDE controller, slave
		</div></li></ul></div><div class="para">
	If you have a third and/or fourth controller, continue assigning letters in alphabetical order, going from controller to controller, and master to slave.
</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-installmethod.html"><strong>Prev</strong>7.4.Â Selecting an Installation Method</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-begininstall-hd-x86.html"><strong>Next</strong>7.6.Â Installing from a Hard Drive</a></li></ul></body></html>


--- NEW FILE s1-begininstall-hd-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.6.Â Installing from a Hard Drive</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="s1-begininstall-cd-inst-x86.html" title="7.5.Â Installing from DVD/CD-ROM" /><link rel="next" href="s1-begininstall-perform-nfs-x86.html" title="7.7.Â Performing a Network Installation" /></head><body class="draft "><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/im
 ages/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-begininstall-cd-inst-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-begininstall-perform-nfs-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-begininstall-hd-x86">7.6.Â Installing from a Hard Drive</h2></div></div></div><a id="id849517" class="indexterm"></a><a id="id853731" class="indexterm"></a><a id="id791295" class="indexterm"></a><a id="id933014" class="indexterm"></a><a id="id855815" class="indexterm"></a><a id="id853809" class="indexterm"></a><a id="id875527" class="indexterm"></a><a id="id866784" class="indexterm"></a><a id="id800136" class="indexterm"></a><a id="id834078" 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, if 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.
</div><div class="para">
	The ISO files must be located on a hard drive that is either internal to the computer, or attached to the machine by USB. In addition the <code class="filename">install.img</code> file from within the ISO files must be copied to a directory named <code class="filename">images</code> Use this option to install Fedora on computers that are without a network connection or CD/DVD drives.
</div><div class="para">
	To extract the <code class="filename">install.img</code> from the ISO follow the procedure:
</div><pre class="screen">
  <code class="command">mount -t iso9660 /path/to/Fedora11.iso /mnt/point -o loop,ro</code>
  <code class="command">cp -pr /mnt/point/images /path/images/</code>
  <code class="command">umount /mnt/point</code>
</pre><div class="para">
	Before you begin installation from a hard drive, check the partition type to ensure that Fedora can read it. To check a partition's file system under Windows, use the <span class="application"><strong>Disk Management</strong></span> tool. To check a partition's file system under Linux, use the <code class="command">fdisk</code> utility.
</div><div class="important"><h2>Cannot Install from LVM Partitions</h2><div class="para">
		You cannot use ISO files on partitions controlled by LVM (Logical Volume Management).
	</div></div><div class="figure" id="id837896"><div class="figure-contents"><div class="mediaobject"><img src="images/begininstall/hd.png" alt="Selecting Partition Dialog for Hard Drive Installation" /><div class="longdesc"><div class="para">
				Selecting partition dialog for a hard drive installation.
			</div></div></div></div><h6>FigureÂ 7.3.Â Selecting Partition Dialog for Hard Drive Installation</h6></div><br class="figure-break" /><div class="para">
	Select the partition containing the ISO files from the list of available partitions. Internal IDE, SATA, SCSI, and USB drive device names begin with <code class="filename">/dev/sd</code>. Each individual drive has its own letter, for example <code class="filename">/dev/sda</code>. Each partition on a drive is numbered, for example <code class="filename">/dev/sda1</code>.
</div><div class="para">
	Also specify the <span class="guilabel"><strong>Directory holding images</strong></span>. Enter the full directory path from the drive that contains the ISO image files. The following table shows some examples of how to enter this information:
</div><div class="table" id="table-Location_of_ISO_images"><div class="table-contents"><table summary="Location of ISO images for different partition types" border="1"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th align="left">
					Partition type
				</th><th align="left">
					Volume
				</th><th align="left">
					Original path to files
				</th><th align="left">
					Directory to use
				</th></tr></thead><tbody><tr><td align="left">
					VFAT
				</td><td align="left">
					D:\
				</td><td align="left">
					D:\Downloads\F11
				</td><td align="left">
					/Downloads/F11
				</td></tr><tr><td align="left">
					ext2, ext3, ext4
				</td><td align="left">
					/home
				</td><td align="left">
					/home/user1/F11
				</td><td align="left">
					/user1/F11
				</td></tr></tbody></table></div><h6>TableÂ 7.2.Â Location of ISO images for different partition types</h6></div><br class="table-break" /><div class="para">
	If the ISO images are in the root (top-level) directory of a partition, enter a <code class="filename">/</code>. If the ISO images are located in a subdirectory of a mounted partition, enter the name of the directory holding the ISO images within that partition. For example, if the partition on which the ISO images is normally mounted as <code class="filename">/home/</code>, and the images are in <code class="filename">/home/new/</code>, you would enter <code class="filename">/new/</code>.
</div><div class="important"><h2>Use a leading slash</h2><div class="para">
		An entry without a leading slash may cause the installation to fail.
	</div></div><div class="para">
	Select <span class="guibutton"><strong>OK</strong></span> to continue. Proceed with <a class="xref" href="sn-welcome-x86.html" title="7.10.Â Welcome to Fedora">SectionÂ 7.10, â€œWelcome to Fedoraâ€</a>.
</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-begininstall-cd-inst-x86.html"><strong>Prev</strong>7.5.Â Installing from DVD/CD-ROM</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-begininstall-perform-nfs-x86.html"><strong>Next</strong>7.7.Â Performing a Network Installation</a></li></ul></body></html>


--- NEW FILE s1-begininstall-nfs-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.8.Â Installing via NFS</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="s1-begininstall-perform-nfs-x86.html" title="7.7.Â Performing a Network Installation" /><link rel="next" href="s1-begininstall-url-x86.html" title="7.9.Â Installing via FTP or HTTP" /></head><body class="draft "><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_rig
 ht.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-begininstall-perform-nfs-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-begininstall-url-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-begininstall-nfs-x86">7.8.Â Installing via NFS</h2></div></div></div><a id="id886475" class="indexterm"></a><a id="id866821" class="indexterm"></a><a id="id876032" class="indexterm"></a><div class="para">
	The NFS dialog applies only if you are installing from an NFS server (if you selected <span class="guimenuitem"><strong>NFS Image</strong></span> in the <span class="guilabel"><strong>Installation Method</strong></span> dialog).
</div><div class="para">
	Enter the domain name or IP address of your NFS server. For example, if you are installing from a host named <code class="filename">eastcoast</code> in the domain <code class="filename">example.com</code>, enter <code class="filename">eastcoast.example.com</code> in the <span class="guilabel"><strong>NFS Server</strong></span> field.
</div><div class="para">
		Next, enter the name of the exported directory. If you followed the setup described in <a class="xref" href="s1-steps-network-installs-x86.html" title="3.5.Â Preparing for a Network Installation">SectionÂ 3.5, â€œPreparing for a Network Installationâ€</a>, you would enter the directory <code class="filename"><em class="replaceable"><code>/export/directory/</code></em></code>.
	</div><div class="para">
	If the NFS server is exporting a mirror of the Fedora installation tree, enter the directory which contains the root of the installation tree. You will enter an Installation Key later on in the process which will determine which subdirectories are used to install from. If everything was specified properly, a message appears indicating that the installation program for Fedora is running.
</div><div class="figure" id="id935990"><div class="figure-contents"><div class="mediaobject"><img src="images/begininstall/nfs.png" alt="NFS Setup Dialog" /><div class="longdesc"><div class="para">
				NFS setup dialog.
			</div></div></div></div><h6>FigureÂ 7.5.Â NFS Setup Dialog</h6></div><br class="figure-break" /><a id="id828372" class="indexterm"></a><div class="para">
	If the NFS server is exporting the ISO images of the Fedora CD-ROMs, enter the directory which contains the ISO images.
</div><div class="para">
	Next, the <span class="guilabel"><strong>Welcome</strong></span> dialog appears.
</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-begininstall-perform-nfs-x86.html"><strong>Prev</strong>7.7.Â Performing a Network Installation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-begininstall-url-x86.html"><strong>Next</strong>7.9.Â Installing via FTP or HTTP</a></li></ul></body></html>


--- NEW FILE s1-begininstall-perform-nfs-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.7.Â Performing a Network Installation</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="s1-begininstall-hd-x86.html" title="7.6.Â Installing from a Hard Drive" /><link rel="next" href="s1-begininstall-nfs-x86.html" title="7.8.Â Installing via NFS" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-begininstall-hd-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-begininstall-nfs-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-begininstall-perform-nfs-x86">7.7.Â Performing a Network Installation</h2></div></div></div><a id="id864289" class="indexterm"></a><a id="id844871" class="indexterm"></a><a id="id847100" class="indexterm"></a><div class="para">
	The installation program is network-aware and can use network settings for a number of functions. For instance, you can install Fedora from a network server using FTP, HTTP, or NFS protocols. You can also instruct the installation program to consult additional software repositories later in the process.
</div><div class="para">
	If you are performing a network installation, the <span class="guilabel"><strong>Configure TCP/IP</strong></span> dialog appears. This dialog asks for your IP and other network addresses. You can choose to configure the IP address and Netmask of the device via DHCP or manually.
</div><div class="para">
	By default, the installation program uses DHCP to automatically provide network settings. If you use a cable or DSL modem, router, firewall, or other network hardware to communicate with the Internet, DHCP is a suitable option. If your network has no DHCP server, clear the check box labeled <span class="guilabel"><strong>Use dynamic IP configuration (DHCP)</strong></span>.
</div><div class="para">
	Enter the IP address you are using during installation and press <span class="keycap"><strong>Enter</strong></span>.
</div><div class="para">
	The installation program supports only the IPv4 protocol. Refer also to <a class="xref" href="sn-networkconfig-fedora.html" title="7.15.Â Network Configuration">SectionÂ 7.15, â€œNetwork Configurationâ€</a> for more information on configuring your network.
</div><div class="figure" id="fig-x86-configuretcpip"><div class="figure-contents"><div class="mediaobject"><img src="images/begininstall/configure_tcp.png" alt="TCP/IP Configuration" /><div class="longdesc"><div class="para">
					Configure the network device address(es) for installation.
				</div></div></div></div><h6>FigureÂ 7.4.Â TCP/IP Configuration</h6></div><br class="figure-break" /><div class="para">
	When the installation process completes, it will transfer these settings to your system.
</div><div class="para">
	You can install from a Web, FTP, or NFS server either on your local network or, if you are connected, on the Internet. You may install Fedora from your own private mirror, or use one of the public mirrors maintained by members of the community. To ensure that the connection is as fast and reliable as possible, use a server that is close to your own geographical location.
</div><div class="para">
	The Fedora Project maintains a list of Web and FTP public mirrors, sorted by region, at <a href="http://fedoraproject.org/wiki/Mirrors">http://fedoraproject.org/wiki/Mirrors</a>. To determine the complete directory path for the installation files, add <code class="filename">/11/Fedora/<em class="replaceable"><code>architecture</code></em>/os/</code> to the path shown on the web page. A correct mirror location for an <code class="systemitem">i386</code> system resembles the URL <code class="literal">http://mirror.example.com/pub/fedora/linux/releases/11/Fedora/i386/os</code>.
</div><div class="itemizedlist"><ul><li><div class="para">
			If you are installing via NFS, proceed to <a class="xref" href="s1-begininstall-nfs-x86.html" title="7.8.Â Installing via NFS">SectionÂ 7.8, â€œInstalling via NFSâ€</a>.
		</div></li><li><div class="para">
			If you are installing via Web or FTP, proceed to <a class="xref" href="s1-begininstall-url-x86.html" title="7.9.Â Installing via FTP or HTTP">SectionÂ 7.9, â€œInstalling via FTP or HTTPâ€</a>.
		</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-begininstall-hd-x86.html"><strong>Prev</strong>7.6.Â Installing from a Hard Drive</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-begininstall-nfs-x86.html"><strong>Next</strong>7.8.Â Installing via NFS</a></li></ul></body></html>


--- NEW FILE s1-begininstall-url-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.9.Â Installing via FTP or HTTP</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="s1-begininstall-nfs-x86.html" title="7.8.Â Installing via NFS" /><link rel="next" href="sn-welcome-x86.html" title="7.10.Â Welcome to Fedora" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-begininstall-nfs-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-welcome-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-begininstall-url-x86">7.9.Â Installing via FTP or HTTP</h2></div></div></div><a id="id804257" class="indexterm"></a><a id="id827809" class="indexterm"></a><a id="id827895" class="indexterm"></a><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.
</div><div class="para">
	Enter the name or IP address of the FTP or HTTP site you are installing from, and the name of the directory containing your architecture. For example, if the FTP or HTTP site contains the directory <code class="filename">/mirrors/Fedora/<em class="replaceable"><code>arch</code></em>/</code>, enter <code class="filename">/mirrors/Fedora/<em class="replaceable"><code>arch</code></em>/</code> (where <em class="replaceable"><code>arch</code></em> is replaced with the architecture type of your system, such as i386). If everything was specified properly, a message box appears indicating that files are being retrieved from the server.
</div><div class="figure" id="id788711"><div class="figure-contents"><div class="mediaobject"><img src="images/begininstall/url.png" alt="URL Setup Dialog" /><div class="longdesc"><div class="para">
				URL setup dialog.
			</div></div></div></div><h6>FigureÂ 7.6.Â URL Setup Dialog</h6></div><br class="figure-break" /><div class="para">
	Next, the <span class="guilabel"><strong>Welcome</strong></span> dialog appears.
</div><div class="note"><h2>Note</h2><div class="para">
		You can save disk space by using the ISO images you have already copied to the server. To accomplish this, install Fedora using ISO images without copying them into a single tree by loopback mounting them. For each ISO image:
	</div><div class="para">
		<code class="command">mkdir disc<em class="replaceable"><code>X</code></em></code>
	</div><div class="para">
		<code class="command">mount -o loop Fedora11-disc<em class="replaceable"><code>X</code></em>.iso disc<em class="replaceable"><code>X</code></em></code>
	</div><div class="para">
		Replace <code class="command">X</code> with the corresponding disc number.
	</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-begininstall-nfs-x86.html"><strong>Prev</strong>7.8.Â Installing via NFS</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-welcome-x86.html"><strong>Next</strong>7.10.Â Welcome to Fedora</a></li></ul></body></html>


--- NEW FILE s1-boot-init-shutdown-process.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.2.Â A Detailed Look at the Boot Process</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-boot-init-shutdown.html" title="AppendixÂ F.Â Boot Process, Init, and Shutdown" /><link rel="prev" href="ch-boot-init-shutdown.html" title="AppendixÂ F.Â Boot Process, Init, and Shutdown" /><link rel="next" href="s2-boot-init-shutdown-loader.html" title="F.2.2.Â The Boot Loader" /></head><body class="draft "><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/i
 mages/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-boot-init-shutdown.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-boot-init-shutdown-loader.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-boot-init-shutdown-process">F.2.Â A Detailed Look at the Boot Process</h2></div></div></div><a id="id863377" class="indexterm"></a><a id="id933751" class="indexterm"></a><a id="id933764" class="indexterm"></a><a id="id928568" class="indexterm"></a><a id="id928581" class="indexterm"></a><div class="para">
			The beginning of the boot process varies depending on the hardware platform being used. However, once the kernel is found and loaded by the boot loader, the default boot process is identical across all architectures. This chapter focuses primarily on the x86 architecture.
		</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-boot-init-shutdown-bios">F.2.1.Â The BIOS</h3></div></div></div><a id="id791508" class="indexterm"></a><a id="id791521" class="indexterm"></a><a id="id791538" class="indexterm"></a><a id="id939167" class="indexterm"></a><a id="id939184" class="indexterm"></a><a id="id939198" class="indexterm"></a><a id="id797038" class="indexterm"></a><a id="id797052" class="indexterm"></a><div class="para">
				When an x86 computer is booted, the processor looks at the end of system memory for the <em class="firstterm">Basic Input/Output System</em> or <em class="firstterm">BIOS</em> program and runs it. The BIOS controls not only the first step of the boot process, but also provides the lowest level interface to peripheral devices. For this reason it is written into read-only, permanent memory and is always available for use.
			</div><div class="para">
				Other platforms use different programs to perform low-level tasks roughly equivalent to those of the BIOS on an x86 system. For instance, Itanium-based computers use the <em class="firstterm">Extensible Firmware Interface</em> (<em class="firstterm">EFI</em>) <em class="firstterm">Shell</em>.
			</div><div class="para">
				Once loaded, the BIOS tests the system, looks for and checks peripherals, and then locates a valid device with which to boot the system. Usually, it checks any diskette drives and CD-ROM drives present for bootable media, then, failing that, looks to the system's hard drives. In most cases, the order of the drives searched while booting is controlled with a setting in the BIOS, and it looks on the master IDE device on the primary IDE bus. The BIOS then loads into memory whatever program is residing in the first sector of this device, called the <em class="firstterm">Master Boot Record</em> or <em class="firstterm">MBR</em>. The MBR is only 512 bytes in size and contains machine code instructions for booting the machine, called a boot loader, along with the partition table. Once the BIOS finds and loads the boot loader program into memory, it yields control of the boot process to it.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-boot-init-shutdown.html"><strong>Prev</strong>AppendixÂ F.Â Boot Process, Init, and Shutdown</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-boot-init-shutdown-loader.html"><strong>Next</strong>F.2.2.Â The Boot Loader</a></li></ul></body></html>


--- NEW FILE s1-boot-init-shutdown-run-boot.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.3.Â Running Additional Programs at Boot Time</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-boot-init-shutdown.html" title="AppendixÂ F.Â Boot Process, Init, and Shutdown" /><link rel="prev" href="s2-boot-init-shutdown-init.html" title="F.2.4.Â The /sbin/init Program" /><link rel="next" href="s1-boot-init-shutdown-sysv.html" title="F.4.Â SysV Init Runlevels" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-boot-init-shutdown-init.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-boot-init-shutdown-sysv.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-boot-init-shutdown-run-boot">F.3.Â Running Additional Programs at Boot Time</h2></div></div></div><a id="id831249" class="indexterm"></a><a id="id831262" class="indexterm"></a><a id="id1042877" class="indexterm"></a><a id="id1042895" class="indexterm"></a><a id="id1042916" class="indexterm"></a><div class="para">
			The <code class="filename">/etc/rc.d/rc.local</code> script is executed by the <code class="command">init</code> command at boot time or when changing runlevels. Adding commands to the bottom of this script is an easy way to perform necessary tasks like starting special services or initialize devices without writing complex initialization scripts in the <code class="filename">/etc/rc.d/init.d/</code> directory and creating symbolic links.
		</div><div class="para">
			The <code class="filename">/etc/rc.serial</code> script is used if serial ports must be setup at boot time. This script runs <code class="command">setserial</code> commands to configure the system's serial ports. Refer to the <code class="command">setserial</code> man page for more information.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-boot-init-shutdown-init.html"><strong>Prev</strong>F.2.4.Â The /sbin/init Program</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-boot-init-shutdown-sysv.html"><strong>Next</strong>F.4.Â SysV Init Runlevels</a></li></ul></body></html>


--- NEW FILE s1-boot-init-shutdown-shutdown.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.5.Â Shutting Down</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-boot-init-shutdown.html" title="AppendixÂ F.Â Boot Process, Init, and Shutdown" /><link rel="prev" href="s2-boot-init-shutdown-sysv-util.html" title="F.4.2.Â Runlevel Utilities" /><link rel="next" href="ap-techref.html" title="AppendixÂ G.Â Other Technical Documentation" /></head><body class="draft "><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="Do
 cumentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-boot-init-shutdown-sysv-util.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ap-techref.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-boot-init-shutdown-shutdown">F.5.Â Shutting Down</h2></div></div></div><a id="id884412" class="indexterm"></a><a id="id884425" class="indexterm"></a><div class="para">
			To shut down Fedora, the root user may issue the <code class="command">/sbin/shutdown</code> command. The <code class="command">shutdown</code> man page has a complete list of options, but the two most common uses are:
		</div><pre class="screen">
<code class="command">/sbin/shutdown -h now</code> <code class="command">/sbin/shutdown -r now</code>
</pre><div class="para">
			After shutting everything down, the <code class="command">-h</code> option halts the machine, and the <code class="command">-r</code> option reboots.
		</div><div class="para">
			PAM console users can use the <code class="command">reboot</code> and <code class="command">halt</code> commands to shut down the system while in runlevels 1 through 5. For more information about PAM console users, refer to the Red Hat Enterprise Linux Deployment Guide.
		</div><div class="para">
			If the computer does not power itself down, be careful not to turn off the computer until a message appears indicating that the system is halted.
		</div><div class="para">
			Failure to wait for this message can mean that not all the hard drive partitions are unmounted, which can lead to file system corruption.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-boot-init-shutdown-sysv-util.html"><strong>Prev</strong>F.4.2.Â Runlevel Utilities</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ap-techref.html"><strong>Next</strong>AppendixÂ G.Â Other Technical Documentation</a></li></ul></body></html>


--- NEW FILE s1-boot-init-shutdown-sysv.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.4.Â SysV Init Runlevels</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-boot-init-shutdown.html" title="AppendixÂ F.Â Boot Process, Init, and Shutdown" /><link rel="prev" href="s1-boot-init-shutdown-run-boot.html" title="F.3.Â Running Additional Programs at Boot Time" /><link rel="next" href="s2-boot-init-shutdown-sysv-util.html" title="F.4.2.Â Runlevel Utilities" /></head><body class="draft "><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/im
 ages/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-boot-init-shutdown-run-boot.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-boot-init-shutdown-sysv-util.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-boot-init-shutdown-sysv">F.4.Â SysV Init Runlevels</h2></div></div></div><a id="id903653" class="indexterm"></a><a id="id966426" class="indexterm"></a><a id="id966448" class="indexterm"></a><a id="id966470" class="indexterm"></a><div class="para">
			The SysV init runlevel system provides a standard process for controlling which programs <code class="command">init</code> launches or halts when initializing a runlevel. SysV init was chosen because it is easier to use and more flexible than the traditional BSD-style init process.
		</div><div class="para">
			The configuration files for SysV init are located in the <code class="filename">/etc/rc.d/</code> directory. Within this directory, are the <code class="filename">rc</code>, <code class="filename">rc.local</code>, <code class="filename">rc.sysinit</code>, and, optionally, the <code class="filename">rc.serial</code> scripts as well as the following directories:
		</div><pre class="screen">
<code class="computeroutput">init.d/ rc0.d/ rc1.d/ rc2.d/ rc3.d/ rc4.d/ rc5.d/ rc6.d/</code>
</pre><div class="para">
			The <code class="filename">init.d/</code> directory contains the scripts used by the <code class="command">/sbin/init</code> command when controlling services. Each of the numbered directories represent the six runlevels configured by default under Fedora.
		</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-init-boot-shutdown-rl">F.4.1.Â Runlevels</h3></div></div></div><a id="id863726" class="indexterm"></a><a id="id863745" class="indexterm"></a><div class="para">
				The idea behind SysV init runlevels revolves around the idea that different systems can be used in different ways. For example, a server runs more efficiently without the drag on system resources created by the X Window System. Or there may be times when a system administrator may need to operate the system at a lower runlevel to perform diagnostic tasks, like fixing disk corruption in runlevel 1.
			</div><div class="para">
				The characteristics of a given runlevel determine which services are halted and started by <code class="command">init</code>. For instance, runlevel 1 (single user mode) halts any network services, while runlevel 3 starts these services. By assigning specific services to be halted or started on a given runlevel, <code class="command">init</code> can quickly change the mode of the machine without the user manually stopping and starting services.
			</div><div class="para">
				The following runlevels are defined by default under Fedora:
			</div><div class="blockquote"><blockquote class="blockquote"><div class="itemizedlist"><ul><li><div class="para">
							<code class="command">0</code> â€” Halt
						</div></li><li><div class="para">
							<code class="command">1</code> â€” Single-user text mode
						</div></li><li><div class="para">
							<code class="command">2</code> â€” Not used (user-definable)
						</div></li><li><div class="para">
							<code class="command">3</code> â€” Full multi-user text mode
						</div></li><li><div class="para">
							<code class="command">4</code> â€” Not used (user-definable)
						</div></li><li><div class="para">
							<code class="command">5</code> â€” Full multi-user graphical mode (with an X-based login screen)
						</div></li><li><div class="para">
							<code class="command">6</code> â€” Reboot
						</div></li></ul></div></blockquote></div><div class="para">
				In general, users operate Fedora at runlevel 3 or runlevel 5 â€” both full multi-user modes. Users sometimes customize runlevels 2 and 4 to meet specific needs, since they are not used.
			</div><div class="para">
				The default runlevel for the system is listed in <code class="filename">/etc/inittab</code>. To find out the default runlevel for a system, look for the line similar to the following near the top of <code class="filename">/etc/inittab</code>:
			</div><pre class="screen">
<code class="computeroutput">id:5:initdefault:</code>
</pre><div class="para">
				The default runlevel listed in this example is five, as the number after the first colon indicates. To change it, edit <code class="filename">/etc/inittab</code> as root.
			</div><div class="warning"><h2>Warning</h2><div class="para">
					Be very careful when editing <code class="filename">/etc/inittab</code>. Simple typos can cause the system to become unbootable. If this happens, either use a boot diskette, enter single-user mode, or enter rescue mode to boot the computer and repair the file.
				</div><div class="para">
					For more information on single-user and rescue mode, refer to the chapter titled <em class="citetitle">Basic System Recovery</em> in the <em class="citetitle">Red Hat Enterprise Linux Deployment Guide</em>.
				</div></div><div class="para">
				It is possible to change the default runlevel at boot time by modifying the arguments passed by the boot loader to the kernel. For information on changing the runlevel at boot time, refer to <a class="xref" href="s1-grub-runlevels.html" title="E.7.Â Changing Runlevels at Boot Time">SectionÂ E.7, â€œChanging Runlevels at Boot Timeâ€</a>.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-boot-init-shutdown-run-boot.html"><strong>Prev</strong>F.3.Â Running Additional Programs at Boot Time</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-boot-init-shutdown-sysv-util.html"><strong>Next</strong>F.4.2.Â Runlevel Utilities</a></li></ul></body></html>


--- NEW FILE s1-complete-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.26.Â Installation Complete</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="s1-installpkgs-x86.html" title="7.25.Â Installing Packages" /><link rel="next" href="ch-trouble-x86.html" title="ChapterÂ 8.Â Troubleshooting Installation on an Intel or AMD System" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-installpkgs-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-trouble-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-complete-x86">7.26.Â Installation Complete</h2></div></div></div><div class="para">
	Congratulations! Your Fedora installation is now complete!
</div><div class="para">
	The installation program prompts you to prepare your system for reboot. Remember to remove any installation media if it is not ejected automatically upon reboot.
</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-installpkgs-x86.html"><strong>Prev</strong>7.25.Â Installing Packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-trouble-x86.html"><strong>Next</strong>ChapterÂ 8.Â Troubleshooting Installation on an Int...</a></li></ul></body></html>


--- NEW FILE s1-diskpartauto-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.20.Â Create Default Layout</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="s1-advanced-storage-x86.html" title="7.19.Â  Advanced Storage Options" /><link rel="next" href="s1-diskpartitioning-x86.html" title="7.21.Â Partitioning Your System" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-advanced-storage-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-diskpartitioning-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-diskpartauto-x86">7.20.Â Create Default Layout</h2></div></div></div><a id="id842781" class="indexterm"></a><a id="id846379" class="indexterm"></a><div class="para">
	Create default layout allows you to have some control concerning what data is removed (if any) from your system. Your options are:
</div><div class="itemizedlist"><ul><li><div class="para">
			<span class="guilabel"><strong>Remove all partitions on selected drives and create default layout</strong></span> â€” select this option to remove all partitions on your hard drive(s) (this includes partitions created by other operating systems such as Windows VFAT or NTFS partitions).
		</div><div class="warning"><h2>Warning</h2><div class="para">
				If you select this option, all data on the selected hard drive(s) is removed by the installation program. Do not select this option if you have information that you want to keep on the hard drive(s) where you are installing Fedora.
			</div></div></li><li><div class="para">
			<span class="guilabel"><strong>Remove Linux partitions on selected drives and create default layout</strong></span> â€” select this option to remove only Linux partitions (partitions created from a previous Linux installation). This does not remove other partitions you may have on your hard drive(s) (such as VFAT or FAT32 partitions).
		</div></li><li><div class="para">
			<span class="guilabel"><strong>Use free space on selected drives and create default layout</strong></span> â€” select this option to retain your current data and partitions, assuming you have enough free space available on your hard drive(s).
		</div></li></ul></div><div class="figure" id="id914292"><div class="figure-contents"><div class="mediaobject"><img src="images/diskpartauto/autopart.png" alt="Create Default Layout" /><div class="longdesc"><div class="para">
				Automatic partitioning.
			</div></div></div></div><h6>FigureÂ 7.18.Â Create Default Layout</h6></div><br class="figure-break" /><div class="para">
	Using your mouse, choose the storage drive(s) on which you want Fedora to be installed. If you have two or more drives, you can choose which drive(s) should contain this installation. Unselected drives, and any data on them, are not touched.
</div><div class="warning"><h2>Warning</h2><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 drive(s). Mistakes do happen and can result in the loss of all your data.
	</div></div><div class="note"><h2>Note</h2><div class="para">
	If you have a RAID card, be aware that some BIOSes do not support booting from the RAID card. In cases such as these, the <code class="filename">/boot/</code> partition must be created on a partition outside of the RAID array, such as on a separate hard drive. An internal hard drive is necessary to use for partition creation with problematic RAID cards.
</div><div class="para">
	A <code class="filename">/boot/</code> partition is also necessary for software RAID setups.
</div><div class="para">
	If you have chosen to automatically partition your system, you should select <span class="guilabel"><strong>Review</strong></span> and manually edit your <code class="filename">/boot/</code> partition.
</div></div><div class="para">
	Select <span class="guilabel"><strong>Encrypt system</strong></span> to encrypt all partitions except the <code class="filename">/boot</code> partition.
</div><div class="para">
	Use the <span class="guilabel"><strong>Advanced storage options</strong></span> option if: 
	<div class="itemizedlist"><ul><li><div class="para">
				You want to install Fedora to a drive connected through the <em class="firstterm">iSCSI</em> protocol. Select <span class="guilabel"><strong>Advanced storage options</strong></span>, then select <span class="guilabel"><strong>Add iSCSI target</strong></span>, then select <span class="guilabel"><strong>Add drive</strong></span>. Provide an IP address and the iSCSI initiator name, and select <span class="guilabel"><strong>Add drive</strong></span>.
			</div></li><li><div class="para">
				You want to disable a <em class="firstterm">dmraid</em> device that was detected at boot time. 
			</div></li></ul></div>
</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"><h2>Installing in text mode</h2><div class="para">
		If you install Fedora in text mode, you can only use the default partitioning schemes described in this section. Therefore, although you can choose to use a whole drive, to remove existing Linux partitions, or to use the free space on the drive, you cannot customize the partition layout. That is, you cannot add or remove partitions or file systems beyond those that the installer automatically adds or removes. If you require a customized layout at installation time, you should perform a graphical installation over a VNC connection or a kickstart installation.
	</div><div class="para">
		Furthermore, advanced options such as LVM, encrypted filesystems, and resizable filesystems are available only in graphical mode and kickstart.
	</div></div><div class="para">
	Click <span class="guibutton"><strong>Next</strong></span> once you have made your selections to proceed.
</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-advanced-storage-x86.html"><strong>Prev</strong>7.19.Â  Advanced Storage Options </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-diskpartitioning-x86.html"><strong>Next</strong>7.21.Â Partitioning Your System</a></li></ul></body></html>


--- NEW FILE s1-diskpartitioning-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.21.Â Partitioning Your System</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="s1-diskpartauto-x86.html" title="7.20.Â Create Default Layout" /><link rel="next" href="s2-diskpartitioning-dd-x86.html" title="7.21.2.Â The partitioning screen" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-diskpartauto-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-diskpartitioning-dd-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-diskpartitioning-x86">7.21.Â Partitioning Your System</h2></div></div></div><a id="id877346" class="indexterm"></a><a id="id844737" class="indexterm"></a><a id="id865685" class="indexterm"></a><div class="para">
		If you chose one of the three automatic partitioning options and did not select <span class="guilabel"><strong>Review</strong></span>, skip ahead to  <a class="xref" href="s1-pkgselection-x86.html" title="7.23.Â Package Group Selection">SectionÂ 7.23, â€œ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.
</div><div class="note"><h2>Note</h2><div class="para">
		Please note that in the text mode installation it is not possible to work with LVM (Logical Volumes) beyond viewing the existing setup. LVM can only be set up during graphical installation.
	</div></div><div class="para">
		If you chose to create a custom layout, you must tell the installation program where to install Fedora. This is done by defining mount points for one or more disk partitions in which Fedora is installed. You may also need to create and/or delete partitions at this time.
	</div><div class="note"><h2>Note</h2><div class="para">
			If you have not yet planned how to set up your partitions, refer to <a class="xref" href="ch-partitions-x86.html" title="AppendixÂ A.Â An Introduction to Disk Partitions">AppendixÂ A, <i>An Introduction to Disk Partitions</i></a> and <a class="xref" href="s2-diskpartrecommend-x86.html" title="7.21.4.Â Recommended Partitioning Scheme">SectionÂ 7.21.4, â€œRecommended Partitioning Schemeâ€</a>. At a bare minimum, you need an appropriately-sized root partition, and a swap partition equal to twice the amount of RAM you have on the system. Itanium system users should have a <code class="filename">/boot/efi/</code> partition of approximately 100 MB and of type FAT (VFAT), a swap partition of at least 512 MB, and an appropriately-sized root (<code class="filename">/</code>) partition.
		</div></div><div class="figure" id="fig-diskpart-ddmain-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/diskpartitioning/ddmain.png" alt="Partitioning on x86, AMD64, and Intel 64 Systems" /><div class="longdesc"><div class="para">
					The main partitioning screen.
				</div></div></div></div><h6>FigureÂ 7.19.Â Partitioning on x86, AMD64, and <span class="trademark">Intel</span>Â® 64 Systems</h6></div><br class="figure-break" /><div class="para">
	With the exception of certain esoteric situations, <span class="application"><strong>anaconda</strong></span> can handle the partitioning requirements for a typical installation.
</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id888157">7.21.1.Â Graphical Display of Hard Drive(s)</h3></div></div></div><div class="para">
	The partitioning screen offers a graphical representation of your hard drive(s).
</div><div class="para">
	Using your mouse, click once to highlight a particular field in the graphical display. Double-click to edit an existing partition or to create a partition out of existing free space.
</div><div class="para">
	Above the display, you can review the <span class="guilabel"><strong>Drive</strong></span> name (such as /dev/hda), the <span class="guilabel"><strong>Geom</strong></span> (which shows the hard disk's geometry and consists of three numbers representing the number of cylinders, heads, and sectors as reported by the hard disk), and the <span class="guilabel"><strong>Model</strong></span> of the hard drive as detected by the installation program.
</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-diskpartauto-x86.html"><strong>Prev</strong>7.20.Â Create Default Layout</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-diskpartitioning-dd-x86.html"><strong>Next</strong>7.21.2.Â The partitioning screen</a></li></ul></body></html>


--- NEW FILE s1-diskpartsetup-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.18.Â Disk Partitioning Setup</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="sn-account_configuration.html" title="7.17.Â Set the Root Password" /><link rel="next" href="s1-advanced-storage-x86.html" title="7.19.Â  Advanced Storage Options" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-account_configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-advanced-storage-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-diskpartsetup-x86">7.18.Â Disk Partitioning Setup</h2></div></div></div><a id="id872041" class="indexterm"></a><a id="id896400" class="indexterm"></a><a id="id939917" class="indexterm"></a><div class="para">
		Partitioning allows you to divide your hard drive into isolated sections, where each section behaves as its own hard drive. Partitioning is particularly useful if you run multiple operating systems. If you are not sure how you want your system to be partitioned, read <a class="xref" href="ch-partitions-x86.html" title="AppendixÂ A.Â An Introduction to Disk Partitions">AppendixÂ A, <i>An Introduction to Disk Partitions</i></a> for more information.
	</div><div class="para">
	On this screen you can choose to create the default layout or choose to manual partition using the <span class="guimenuitem"><strong>Create custom layout</strong></span> option.
</div><div class="para">
	The first three options allow you to perform an automated installation without having to partition your drive(s) yourself. If you do not feel comfortable with partitioning your system, it is recommended that you <span class="emphasis"><em>do not</em></span> choose to create a custom layout and instead let the installation program partition for you.
</div><div class="para">
		You can configure an iSCSI target for installation, or disable a dmraid device from this screen by clicking on the 'Advanced storage configuration' button. For more information refer to <a class="xref" href="s1-advanced-storage-x86.html" title="7.19.Â  Advanced Storage Options">SectionÂ 7.19, â€œ Advanced Storage Options â€</a>.
	</div><div class="warning"><h2>Warning</h2><div class="para">
		The  <span class="application"><strong>PackageKit</strong></span> update software downloads updated packages to <code class="filename">/var/cache/yum/</code> by default. If you partition the system manually, and create a separate <code class="filename">/var/</code> partition, be sure to create the partition large enough (3.0 GB or more) to download package updates.
	</div></div><div class="figure" id="id790534"><div class="figure-contents"><div class="mediaobject"><img src="images/diskpartsetup/disk-setup.png" alt="Disk Partitioning Setup" /><div class="longdesc"><div class="para">
				Choose automatic partitioning or manual partitioning.
			</div></div></div></div><h6>FigureÂ 7.15.Â Disk Partitioning Setup</h6></div><br class="figure-break" /><div class="para">
		If you choose to create a custom layout, refer to <a class="xref" href="s1-diskpartitioning-x86.html" title="7.21.Â Partitioning Your System">SectionÂ 7.21, â€œPartitioning Your Systemâ€</a>.
	</div><div class="warning"><h2>Warning</h2><div class="para">
	If you receive an error after the <span class="guilabel"><strong>Disk Partitioning Setup</strong></span> phase of the installation saying something similar to:
</div><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."
</div><div class="para">
	you may not have a partition table on that drive or the partition table on the drive may not be recognizable by the partitioning software used in the installation program.
</div><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).
		</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" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-partitioning-raid">7.18.1.Â RAID and Other Disk Devices</h3></div></div></div><a id="id914946" class="indexterm"></a><a id="id804312" class="indexterm"></a><a id="id832495" class="indexterm"></a><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="sn-partitioning-raid-hw">7.18.1.1.Â Hardware RAID</h4></div></div></div><div class="para">
			RAID, or Redundant Array of Independent Disks, allows a group, or array, of drives to act as a single device. Configure any RAID functions provided by the mainboard of your computer, or attached controller cards, before you begin the installation process. Each active RAID array appears as one drive within Fedora.
		</div><div class="para">
			On systems with more than one hard drive you may configure Fedora to operate several of the drives as a Linux RAID array without requiring any additional hardware.
		</div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="sn-partitioning-raid-sw">7.18.1.2.Â Software RAID</h4></div></div></div><div class="para">
			You can use the Fedora installation program to create Linux software RAID arrays, where RAID functions are controlled by the operating system rather than dedicated hardware. These functions are explained in detail in <a class="xref" href="s1-diskpartitioning-x86.html" title="7.21.Â Partitioning Your System">SectionÂ 7.21, â€œPartitioning Your Systemâ€</a>.
		</div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="sn-partitioning-fw-usb">7.18.1.3.Â FireWire and USB Disks</h4></div></div></div><div class="para">
			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"><h2>Post-installation Usage</h2><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-account_configuration.html"><strong>Prev</strong>7.17.Â Set the Root Password</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-advanced-storage-x86.html"><strong>Next</strong>7.19.Â  Advanced Storage Options </a></li></ul></body></html>


--- NEW FILE s1-grub-additional-resources.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.8.Â Additional Resources</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-grub.html" title="AppendixÂ E.Â The GRUB Boot Loader" /><link rel="prev" href="s1-grub-runlevels.html" title="E.7.Â Changing Runlevels at Boot Time" /><link rel="next" href="s2-grub-useful-websites.html" title="E.8.2.Â Useful Websites" /></head><body class="draft "><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><
 ul class="docnav"><li class="previous"><a accesskey="p" href="s1-grub-runlevels.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-grub-useful-websites.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-grub-additional-resources">E.8.Â Additional Resources</h2></div></div></div><a id="id809692" class="indexterm"></a><div class="para">
			This chapter is only intended as an introduction to GRUB. Consult the following resources to discover more about how GRUB works.
		</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-grub-installed-documentation">E.8.1.Â Installed Documentation</h3></div></div></div><a id="id809719" class="indexterm"></a><div class="itemizedlist"><ul><li><div class="para">
						<code class="filename">/usr/share/doc/grub-<em class="replaceable"><code><version-number></code></em>/</code> â€” This directory contains good information about using and configuring GRUB, where <em class="replaceable"><code><version-number></code></em> corresponds to the version of the GRUB package installed.
					</div></li><li><div class="para">
						<code class="command">info grub</code> â€” The GRUB info page contains a tutorial, a user reference manual, a programmer reference manual, and a FAQ document about GRUB and its usage.
					</div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-grub-runlevels.html"><strong>Prev</strong>E.7.Â Changing Runlevels at Boot Time</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-grub-useful-websites.html"><strong>Next</strong>E.8.2.Â Useful Websites</a></li></ul></body></html>


--- NEW FILE s1-grub-commands.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.5.Â GRUB Commands</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-grub.html" title="AppendixÂ E.Â The GRUB Boot Loader" /><link rel="prev" href="s1-grub-interfaces.html" title="E.4.Â GRUB Interfaces" /><link rel="next" href="s1-grub-configfile.html" title="E.6.Â GRUB Menu Configuration File" /></head><body class="draft "><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><ul class="docnav
 "><li class="previous"><a accesskey="p" href="s1-grub-interfaces.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-grub-configfile.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-grub-commands">E.5.Â GRUB Commands</h2></div></div></div><a id="id901062" class="indexterm"></a><div class="para">
			GRUB allows a number of useful commands in its command line interface. Some of the commands accept options after their name; these options should be separated from the command and other options on that line by space characters.
		</div><div class="para">
			The following is a list of useful commands:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<code class="command">boot</code> â€” Boots the operating system or chain loader that was last loaded.
				</div></li><li><div class="para">
					<code class="command">chainloader <em class="replaceable"><code></path/to/file></code></em></code> â€” Loads the specified file as a chain loader. If the file is located on the first sector of the specified partition, use the blocklist notation, <code class="command">+1</code>, instead of the file name.
				</div><div class="para">
					The following is an example <code class="command">chainloader</code> command:
				</div><pre class="screen">
<code class="command">chainloader +1</code>
</pre></li><li><div class="para">
					<code class="command">displaymem</code> â€” Displays the current use of memory, based on information from the BIOS. This is useful to determine how much RAM a system has prior to booting it.
				</div></li><li><div class="para">
					<code class="command">initrd <em class="replaceable"><code></path/to/initrd></code></em></code> â€” Enables users to specify an initial RAM disk to use when booting. An <code class="filename">initrd</code> is necessary when the kernel needs certain modules in order to boot properly, such as when the root partition is formatted with the ext3 or ext4 file system.
				</div><div class="para">
					The following is an example <code class="command">initrd</code> command:
				</div><pre class="screen">
<code class="command">initrd /initrd-2.6.8-1.523.img</code>
</pre></li><li><div class="para">
					<code class="command">install <em class="replaceable"><code><stage-1></code></em> <em class="replaceable"><code><install-disk></code></em> <em class="replaceable"><code><stage-2></code></em> <code class="option">p</code> <em class="replaceable"><code>config-file</code></em></code> â€” Installs GRUB to the system MBR.
				</div><div class="itemizedlist"><ul><li><div class="para">
							<code class="command"><em class="replaceable"><code><stage-1></code></em></code> â€” Signifies a device, partition, and file where the first boot loader image can be found, such as <code class="command">(hd0,0)/grub/stage1</code>.
						</div></li><li><div class="para">
							<code class="command"><em class="replaceable"><code><install-disk></code></em></code> â€” Specifies the disk where the stage 1 boot loader should be installed, such as <code class="command">(hd0)</code>.
						</div></li><li><div class="para">
							<code class="command"><em class="replaceable"><code><stage-2></code></em></code> â€” Passes the stage 2 boot loader location to the stage 1 boot loader, such as <code class="command">(hd0,0)/grub/stage2</code>.
						</div></li><li><div class="para">
							<code class="option">p</code> <code class="command"><em class="replaceable"><code><config-file></code></em></code> â€” This option tells the <code class="command">install</code> command to look for the menu configuration file specified by <code class="command"><em class="replaceable"><code><config-file></code></em></code>, such as <code class="command">(hd0,0)/grub/grub.conf</code>.
						</div></li></ul></div><div class="warning"><h2>Warning</h2><div class="para">
						The <code class="command">install</code> command overwrites any information already located on the MBR.
					</div></div></li><li><div class="para">
					<code class="command">kernel <em class="replaceable"><code></path/to/kernel></code></em> <em class="replaceable"><code><option-1></code></em> <em class="replaceable"><code><option-N></code></em></code> ... â€” Specifies the kernel file to load when booting the operating system. Replace <em class="replaceable"><code></path/to/kernel></code></em> with an absolute path from the partition specified by the root command. Replace <em class="replaceable"><code><option-1></code></em> with options for the Linux kernel, such as <code class="command">root=/dev/VolGroup00/LogVol00</code> to specify the device on which the root partition for the system is located. Multiple options can be passed to the kernel in a space separated list.
				</div><div class="para">
					The following is an example <code class="command">kernel</code> command:
				</div><pre class="screen">
<code class="command">kernel /vmlinuz-2.6.8-1.523 ro root=/dev/VolGroup00/LogVol00</code>
</pre><div class="para">
					The option in the previous example specifies that the root file system for Linux is located on the <code class="command">hda5</code> partition.
				</div></li><li><div class="para">
					<code class="command">root (<em class="replaceable"><code><device-type></code></em><em class="replaceable"><code><device-number></code></em>,<em class="replaceable"><code><partition></code></em>)</code> â€” Configures the root partition for GRUB, such as <code class="command">(hd0,0)</code>, and mounts the partition.
				</div><div class="para">
					The following is an example <code class="command">root</code> command:
				</div><pre class="screen">
<code class="command">root (hd0,0)</code>
</pre></li><li><div class="para">
					<code class="command">rootnoverify (<em class="replaceable"><code><device-type></code></em><em class="replaceable"><code><device-number></code></em>,<em class="replaceable"><code><partition></code></em>)</code> â€” Configures the root partition for GRUB, just like the <code class="command">root</code> command, but does not mount the partition.
				</div></li></ul></div><div class="para">
			Other commands are also available; type <code class="command">help --all</code> for a full list of commands. For a description of all GRUB commands, refer to the documentation available online at <a href="http://www.gnu.org/software/grub/manual/">http://www.gnu.org/software/grub/manual/</a>.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-grub-interfaces.html"><strong>Prev</strong>E.4.Â GRUB Interfaces</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-grub-configfile.html"><strong>Next</strong>E.6.Â GRUB Menu Configuration File</a></li></ul></body></html>


--- NEW FILE s1-grub-configfile.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.6.Â GRUB Menu Configuration File</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-grub.html" title="AppendixÂ E.Â The GRUB Boot Loader" /><link rel="prev" href="s1-grub-commands.html" title="E.5.Â GRUB Commands" /><link rel="next" href="s2-grub-configfile-commands.html" title="E.6.2.Â Configuration File Directives" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-grub-commands.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-grub-configfile-commands.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-grub-configfile">E.6.Â GRUB Menu Configuration File</h2></div></div></div><a id="id871245" class="indexterm"></a><div class="para">
			The configuration file (<code class="filename">/boot/grub/grub.conf</code>), which is used to create the list of operating systems to boot in GRUB's menu interface, essentially allows the user to select a pre-set group of commands to execute. The commands given in <a class="xref" href="s1-grub-commands.html" title="E.5.Â GRUB Commands">SectionÂ E.5, â€œGRUB Commandsâ€</a> can be used, as well as some special commands that are only available in the configuration file.
		</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-grub-configfile-structure">E.6.1.Â Configuration File Structure</h3></div></div></div><a id="id846776" class="indexterm"></a><a id="id846793" class="indexterm"></a><a id="id846813" class="indexterm"></a><div class="para">
				The GRUB menu interface configuration file is <code class="filename">/boot/grub/grub.conf</code>. The commands to set the global preferences for the menu interface are placed at the top of the file, followed by stanzas for each operating kernel or operating system listed in the menu.
			</div><div class="para">
				The following is a very basic GRUB menu configuration file designed to boot either Fedora or Microsoft Windows Vista:
			</div><pre class="screen">default=0 
timeout=10 
splashimage=(hd0,0)/grub/splash.xpm.gz 
hiddenmenu 
title Fedora (2.6.27.19-170.2.35.fc10.i686)
root (hd0,1)
kernel /vmlinuz-2.6.27.19-170.2.35.fc10.i686 ro root=UUID=04a07c13-e6bf-6d5a-b207-002689545705 rhgb quiet
initrd /initrd-2.6.27.19-170.2.35.fc10.i686.img 

# section to load Windows 
title Windows         
rootnoverify (hd0,0)         
chainloader +1
</pre><div class="para">
				This file configures GRUB to build a menu with Fedora as the default operating system and sets it to autoboot after 10 seconds. Two sections are given, one for each operating system entry, with commands specific to the system disk partition table.
			</div><div class="note"><h2>Note</h2><div class="para">
					Note that the default is specified as an integer. This refers to the first <code class="command">title</code> line in the GRUB configuration file. For the <code class="command">Windows</code> section to be set as the default in the previous example, change the <code class="command">default=0</code> to <code class="command">default=1</code>.
				</div></div><div class="para">
				Configuring a GRUB menu configuration file to boot multiple operating systems is beyond the scope of this chapter. Consult <a class="xref" href="s1-grub-additional-resources.html" title="E.8.Â Additional Resources">SectionÂ E.8, â€œAdditional Resourcesâ€</a> for a list of additional resources.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-grub-commands.html"><strong>Prev</strong>E.5.Â GRUB Commands</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-grub-configfile-commands.html"><strong>Next</strong>E.6.2.Â Configuration File Directives</a></li></ul></body></html>


--- NEW FILE s1-grub-installing.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.2.Â Installing GRUB</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-grub.html" title="AppendixÂ E.Â The GRUB Boot Loader" /><link rel="prev" href="ch-grub.html" title="AppendixÂ E.Â The GRUB Boot Loader" /><link rel="next" href="s1-grub-terminology.html" title="E.3.Â GRUB Terminology" /></head><body class="draft "><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><ul class="docnav"><li c
 lass="previous"><a accesskey="p" href="ch-grub.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-grub-terminology.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-grub-installing">E.2.Â Installing GRUB</h2></div></div></div><a id="id824708" class="indexterm"></a><div class="para">
			If GRUB was not installed during the installation process, it can be installed afterward. Once installed, it automatically becomes the default boot loader.
		</div><div class="para">
			Before installing GRUB, make sure to use the latest GRUB package available or use the GRUB package from the installation CD-ROMs. 
		</div><div class="para">
			Once the GRUB package is installed, open a root shell prompt and run the command <code class="command">/sbin/grub-install <em class="replaceable"><code><location></code></em></code>, where <em class="replaceable"><code><location></code></em> is the location that the GRUB Stage 1 boot loader should be installed. For example, the following command installs GRUB to the MBR of the master IDE device on the primary IDE bus:
		</div><pre class="screen">
<code class="command">/sbin/grub-install /dev/hda</code>
</pre><div class="para">
			The next time the system boots, the GRUB graphical boot loader menu appears before the kernel loads into memory.
		</div><div class="important"><h2>Important</h2><a id="id927719" class="indexterm"></a><div class="para">
				If GRUB is installed on a RAID 1 array, the system may become unbootable in the event of disk failure. 
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-grub.html"><strong>Prev</strong>AppendixÂ E.Â The GRUB Boot Loader</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-grub-terminology.html"><strong>Next</strong>E.3.Â GRUB Terminology</a></li></ul></body></html>


--- NEW FILE s1-grub-interfaces.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.4.Â GRUB Interfaces</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-grub.html" title="AppendixÂ E.Â The GRUB Boot Loader" /><link rel="prev" href="s2-grub-terminology-rootfs.html" title="E.3.3.Â The Root File System and GRUB" /><link rel="next" href="s1-grub-commands.html" title="E.5.Â GRUB Commands" /></head><body class="draft "><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><ul clas
 s="docnav"><li class="previous"><a accesskey="p" href="s2-grub-terminology-rootfs.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-grub-commands.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-grub-interfaces">E.4.Â GRUB Interfaces</h2></div></div></div><a id="id833701" class="indexterm"></a><a id="id833715" class="indexterm"></a><a id="id833732" class="indexterm"></a><a id="id833749" class="indexterm"></a><a id="id909460" class="indexterm"></a><a id="id909474" class="indexterm"></a><div class="para">
			GRUB features three interfaces which provide different levels of functionality. Each of these interfaces allows users to boot the Linux kernel or another operating system.
		</div><div class="para">
			The interfaces are as follows:
		</div><div class="note"><h2>Note</h2><div class="para">
				The following GRUB interfaces can only be accessed by pressing any key within the three seconds of the GRUB menu bypass screen.
			</div></div><div class="variablelist"><dl><dt><span class="term"><span class="emphasis"><em>Menu Interface</em></span></span></dt><dd><div class="para">
						This is the default interface shown when GRUB is configured by the installation program. A menu of operating systems or preconfigured kernels are displayed as a list, ordered by name. Use the arrow keys to select an operating system or kernel version and press the <span class="keycap"><strong>Enter</strong></span> key to boot it. If you do nothing on this screen, then after the time out period expires GRUB will load the default option.
					</div><div class="para">
						Press the <span class="keycap"><strong>e</strong></span> key to enter the entry editor interface or the <span class="keycap"><strong>c</strong></span> key to load a command line interface.
					</div><div class="para">
						Refer to <a class="xref" href="s1-grub-configfile.html" title="E.6.Â GRUB Menu Configuration File">SectionÂ E.6, â€œGRUB Menu Configuration Fileâ€</a> for more information on configuring this interface.
					</div></dd><dt><span class="term"><span class="emphasis"><em>Menu Entry Editor Interface</em></span></span></dt><dd><div class="para">
						To access the menu entry editor, press the <span class="keycap"><strong>e</strong></span> key from the boot loader menu. The GRUB commands for that entry are displayed here, and users may alter these command lines before booting the operating system by adding a command line (<span class="keycap"><strong>o</strong></span> inserts a new line after the current line and <span class="keycap"><strong>O</strong></span> inserts a new line before it), editing one (<span class="keycap"><strong>e</strong></span>), or deleting one (<span class="keycap"><strong>d</strong></span>).
					</div><div class="para">
						After all changes are made, the <span class="keycap"><strong>b</strong></span> key executes the commands and boots the operating system. The <span class="keycap"><strong>Esc</strong></span> key discards any changes and reloads the standard menu interface. The <span class="keycap"><strong>c</strong></span> key loads the command line interface.
					</div><div class="note"><h2>Note</h2><div class="para">
							For information about changing runlevels using the GRUB menu entry editor, refer to <a class="xref" href="s1-grub-runlevels.html" title="E.7.Â Changing Runlevels at Boot Time">SectionÂ E.7, â€œChanging Runlevels at Boot Timeâ€</a>.
						</div></div></dd><dt><span class="term"><span class="emphasis"><em>Command Line Interface</em></span></span></dt><dd><div class="para">
						The command line interface is the most basic GRUB interface, but it is also the one that grants the most control. The command line makes it possible to type any relevant GRUB commands followed by the <span class="keycap"><strong>Enter</strong></span> key to execute them. This interface features some advanced shell-like features, including <span class="keycap"><strong>Tab</strong></span> key completion based on context, and <span class="keycap"><strong>Ctrl</strong></span> key combinations when typing commands, such as <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>a</strong></span> to move to the beginning of a line and <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>e</strong></span> to move to the end of a line. In addition, the arrow, <span class="keycap"><strong>Home</strong></span>, <span class="keycap"><strong>End</strong></span>, and <span class="keycap"><strong>Delete</strong></span> keys work as the
 y do in the <code class="command">bash</code> shell.
					</div><div class="para">
						Refer to <a class="xref" href="s1-grub-commands.html" title="E.5.Â GRUB Commands">SectionÂ E.5, â€œGRUB Commandsâ€</a> for a list of common commands.
					</div></dd></dl></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-grub-interfaces-orderofuse">E.4.1.Â Interfaces Load Order</h3></div></div></div><a id="id966555" class="indexterm"></a><div class="para">
				When GRUB loads its second stage boot loader, it first searches for its configuration file. Once found, the menu interface bypass screen is displayed. If a key is pressed within three seconds, GRUB builds a menu list and displays the menu interface. If no key is pressed, the default kernel entry in the GRUB menu is used.
			</div><div class="para">
				If the configuration file cannot be found, or if the configuration file is unreadable, GRUB loads the command line interface, allowing the user to type commands to complete the boot process.
			</div><div class="para">
				If the configuration file is not valid, GRUB prints out the error and asks for input. This helps the user see precisely where the problem occurred. Pressing any key reloads the menu interface, where it is then possible to edit the menu option and correct the problem based on the error reported by GRUB. If the correction fails, GRUB reports an error and reloads the menu interface.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-grub-terminology-rootfs.html"><strong>Prev</strong>E.3.3.Â The Root File System and GRUB</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-grub-commands.html"><strong>Next</strong>E.5.Â GRUB Commands</a></li></ul></body></html>


--- NEW FILE s1-grub-runlevels.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.7.Â Changing Runlevels at Boot Time</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-grub.html" title="AppendixÂ E.Â The GRUB Boot Loader" /><link rel="prev" href="s2-grub-configfile-commands.html" title="E.6.2.Â Configuration File Directives" /><link rel="next" href="s1-grub-additional-resources.html" title="E.8.Â Additional Resources" /></head><body class="draft "><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="Do
 cumentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-grub-configfile-commands.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-grub-additional-resources.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-grub-runlevels">E.7.Â Changing Runlevels at Boot Time</h2></div></div></div><a id="id819350" class="indexterm"></a><div class="para">
			Under Fedora, it is possible to change the default runlevel at boot time.
		</div><div class="para">
			To change the runlevel of a single boot session, use the following instructions:
		</div><div class="itemizedlist"><ul><li><div class="para">
					When the GRUB menu bypass screen appears at boot time, press any key to enter the GRUB menu (within the first three seconds).
				</div></li><li><div class="para">
					Press the <span class="keycap"><strong>a</strong></span> key to append to the <code class="command">kernel</code> command.
				</div></li><li><div class="para">
					Add <code class="command"><space><em class="replaceable"><code><runlevel></code></em></code> at the end of the boot options line to boot to the desired runlevel. For example, the following entry would initiate a boot process into runlevel 3:
				</div><pre class="screen">
<code class="command">grub append> ro root=/dev/VolGroup00/LogVol00 rhgb quiet 3</code>
</pre></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-grub-configfile-commands.html"><strong>Prev</strong>E.6.2.Â Configuration File Directives</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-grub-additional-resources.html"><strong>Next</strong>E.8.Â Additional Resources</a></li></ul></body></html>


--- NEW FILE s1-grub-terminology.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.3.Â GRUB Terminology</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-grub.html" title="AppendixÂ E.Â The GRUB Boot Loader" /><link rel="prev" href="s1-grub-installing.html" title="E.2.Â Installing GRUB" /><link rel="next" href="s2-grub-terminology-files.html" title="E.3.2.Â File Names and Blocklists" /></head><body class="draft "><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><ul clas
 s="docnav"><li class="previous"><a accesskey="p" href="s1-grub-installing.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-grub-terminology-files.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-grub-terminology">E.3.Â GRUB Terminology</h2></div></div></div><a id="id967777" class="indexterm"></a><div class="para">
			One of the most important things to understand before using GRUB is how the program refers to devices, such as hard drives and partitions. This information is particularly important when configuring GRUB to boot multiple operating systems.
		</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-grub-terminology-devices">E.3.1.Â Device Names</h3></div></div></div><a id="id967806" class="indexterm"></a><div class="para">
				When referring to a specific device with GRUB, do so using the following format (note that the parentheses and comma are very important syntactically):
			</div><div class="para">
				<code class="command"> (<em class="replaceable"><code><type-of-device><bios-device-number></code></em>,<em class="replaceable"><code><partition-number></code></em>) </code>
			</div><div class="para">
				The <em class="replaceable"><code><type-of-device></code></em> specifies the type of device from which GRUB boots. The two most common options are <code class="command">hd</code> for a hard disk or <code class="command">fd</code> for a 3.5 diskette. A lesser used device type is also available called <code class="command">nd</code> for a network disk. Instructions on configuring GRUB to boot over the network are available online at <a href="http://www.gnu.org/software/grub/manual/">http://www.gnu.org/software/grub/manual/</a>.
			</div><div class="para">
				The <em class="replaceable"><code><bios-device-number></code></em> is the BIOS device number. The primary IDE hard drive is numbered <code class="command">0</code> and a secondary IDE hard drive is numbered <code class="command">1</code>. This syntax is roughly equivalent to that used for devices by the kernel. For example, the <code class="command">a</code> in <code class="command">hda</code> for the kernel is analogous to the <code class="command">0</code> in <code class="command">hd0</code> for GRUB, the <code class="command">b</code> in <code class="command">hdb</code> is analogous to the <code class="command">1</code> in <code class="command">hd1</code>, and so on.
			</div><div class="para">
				The <em class="replaceable"><code><partition-number></code></em> specifies the number of a partition on a device. Like the <em class="replaceable"><code><bios-device-number></code></em>, most types of partitions are numbered starting at <code class="command">0</code>. However, BSD partitions are specified using letters, with <code class="command">a</code> corresponding to <code class="command">0</code>, <code class="command">b</code> corresponding to <code class="command">1</code>, and so on.
			</div><div class="note"><h2>Note</h2><div class="para">
					The numbering system for devices under GRUB always begins with <code class="command">0</code>, not <code class="command">1</code>. Failing to make this distinction is one of the most common mistakes made by new users.
				</div></div><div class="para">
				To give an example, if a system has more than one hard drive, GRUB refers to the first hard drive as <code class="command">(hd0)</code> and the second as <code class="command">(hd1)</code>. Likewise, GRUB refers to the first partition on the first drive as <code class="command">(hd0,0)</code> and the third partition on the second hard drive as <code class="command">(hd1,2)</code>.
			</div><div class="para">
				In general the following rules apply when naming devices and partitions under GRUB:
			</div><div class="itemizedlist"><ul><li><div class="para">
						It does not matter if system hard drives are IDE or SCSI, all hard drives begin with the letters <code class="command">hd</code>. The letters <code class="command">fd</code> are used to specify 3.5 diskettes.
					</div></li><li><div class="para">
						To specify an entire device without respect to partitions, leave off the comma and the partition number. This is important when telling GRUB to configure the MBR for a particular disk. For example, <code class="command">(hd0)</code> specifies the MBR on the first device and <code class="command">(hd3)</code> specifies the MBR on the fourth device.
					</div></li><li><div class="para">
						If a system has multiple drive devices, it is very important to know how the drive boot order is set in the BIOS. This is a simple task if a system has only IDE or SCSI drives, but if there is a mix of devices, it becomes critical that the type of drive with the boot partition be accessed first.
					</div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-grub-installing.html"><strong>Prev</strong>E.2.Â Installing GRUB</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-grub-terminology-files.html"><strong>Next</strong>E.3.2.Â File Names and Blocklists</a></li></ul></body></html>


--- NEW FILE s1-guimode-textinterface-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2.Â The Text Mode Installation Program User Interface</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="next" href="s1-x86-starting.html" title="7.3.Â Starting the Installation Program" /></head><body class="draft "><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_Co
 ntent/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-guimode-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-x86-starting.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-guimode-textinterface-x86">7.2.Â The Text Mode Installation Program User Interface</h2></div></div></div><a id="id833151" class="indexterm"></a><a id="id869674" class="indexterm"></a><div class="note"><h2>Note</h2><div class="para">
			Graphical installation remains the recommended method for installing Fedora. 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.html" title="ChapterÂ 12.Â Installing Through VNC">ChapterÂ 12, <i>Installing Through VNC</i></a>.
		</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 â€“ see <a class="xref" href="ap-admin-options.html" title="ChapterÂ 9.Â Boot Options">ChapterÂ 9, <i>Boot Options</i></a>
		</div></div><div class="para">
		The Fedora text mode installation program uses a screen-based interface that includes most of the on-screen <em class="wordasword">widgets</em> commonly found on graphical user interfaces. <a class="xref" href="s1-guimode-textinterface-x86.html#fig-install-widget1-x86" title="FigureÂ 7.1.Â Installation Program Widgets as seen in Boot Loader Configuration">FigureÂ 7.1, â€œInstallation Program Widgets as seen in Boot Loader Configurationâ€</a>, and <a class="xref" href="s1-guimode-textinterface-x86.html#fig-install-widget2-x86" title="FigureÂ 7.2.Â Installation Program Widgets as seen in the partitioning screen">FigureÂ 7.2, â€œInstallation Program Widgets as seen in the partitioning screenâ€</a>, illustrate the screens that appear during the installation process.
	</div><div class="para">
		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.
	</div><div class="note"><h2>Note</h2><div class="para">
		While text mode installations are not explicitly documented, those using the text mode installation program can easily follow the GUI installation instructions. However, because text mode presents you with a simpler, more streamlined insatallation process, certain options that are available in graphical mode are not also available in text mode. These differences are noted in the description of the installation process in this guide, and include: 
		<div class="itemizedlist"><ul><li><div class="para">
					customizing the partition layout.
				</div></li><li><div class="para">
					customizing the bootloader configuration.
				</div></li><li><div class="para">
					selecting packages during installation.
				</div></li></ul></div>
		 Note also that manipulation of LVM (Logical Volume Management) disk volumes is only possible in graphical mode. In text mode it is only possible to view and accept the default LVM setup.
	</div></div><div class="note"><h2>Note</h2><div class="para">
		Not every language supported in graphical installation mode is also supported in text mode. Specifically, languages written with a character set other than the Latin or Cyrillic alphabets are not available in text mode. If you choose a language written with a character set that is not supported in text mode, the installation program will present you with the English versions of the screens.
	</div></div><div class="figure" id="fig-install-widget1-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/guimode/widget1.png" alt="Installation Program Widgets as seen in Boot Loader Configuration" /><div class="longdesc"><div class="para">
					Installation Program Widgets as seen in <span class="guilabel"><strong>Boot Loader Configuration</strong></span>
				</div></div></div></div><h6>FigureÂ 7.1.Â Installation Program Widgets as seen in <span class="guilabel">Boot Loader Configuration</span></h6></div><br class="figure-break" /><div class="orderedlist"><h6>Legend</h6><ol><li><div class="para">
		Window â€” Windows (usually referred to as <em class="firstterm">dialogs</em> in this manual) appear on your screen throughout the installation process. At times, one window may overlay another; in these cases, you can only interact with the window on top. When you are finished in that window, it disappears, allowing you to continue working in the window underneath.
	</div></li><li><div class="para">
		Checkbox â€” Checkboxes allow you to select or deselect a feature. The box displays either an asterisk (selected) or a space (unselected). When the cursor is within a checkbox, press <span class="keycap"><strong>Space</strong></span> to select or deselect a feature.
	</div></li><li><div class="para">
		Text Input â€” Text input lines are regions where you can enter information required by the installation program. When the cursor rests on a text input line, you may enter and/or edit information on that line.
	</div></li></ol></div><div class="figure" id="fig-install-widget2-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/guimode/widget2.png" alt="Installation Program Widgets as seen in the partitioning screen" /><div class="longdesc"><div class="para">
					Installation Program Widgets as seen in the partitioning screen
				</div></div></div></div><h6>FigureÂ 7.2.Â Installation Program Widgets as seen in the partitioning screen</h6></div><br class="figure-break" /><div class="orderedlist"><h6>Legend</h6><ol><li><div class="para">
		Text Widget â€” Text widgets are regions of the screen for the display of text. At times, text widgets may also contain other widgets, such as checkboxes. If a text widget contains more information than can be displayed in the space reserved for it, a scroll bar appears; if you position the cursor within the text widget, you can then use the <span class="keycap"><strong>Up</strong></span> and <span class="keycap"><strong>Down</strong></span> arrow keys to scroll through all the information available. Your current position is shown on the scroll bar by a <span class="guiicon"><strong>#</strong></span> character, which moves up and down the scroll bar as you scroll.
	</div></li><li><div class="para">
		Scroll Bar â€” Scroll bars appear on the side or bottom of a window to control which part of a list or document is currently in the window's frame. The scroll bar makes it easy to move to any part of a file.
	</div></li><li><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></ol></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id834187">7.2.1.Â Using the Keyboard to Navigate</h3></div></div></div><a id="id848103" class="indexterm"></a><a id="id831537" 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.
	</div><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"><h2>Warning</h2><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-guimode-x86.html"><strong>Prev</strong>ChapterÂ 7.Â Installing on Intel and AMD Systems</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-x86-starting.html"><strong>Next</strong>7.3.Â Starting the Installation Program</a></li></ul></body></html>


--- NEW FILE s1-installmethod.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.4.Â Selecting an Installation Method</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="s2-x86-starting-bootopts.html" title="7.3.2.Â Additional Boot Options" /><link rel="next" href="s1-begininstall-cd-inst-x86.html" title="7.5.Â Installing from DVD/CD-ROM" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-x86-starting-bootopts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-begininstall-cd-inst-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-installmethod">7.4.Â Selecting an Installation Method</h2></div></div></div><a id="id903824" 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="id853787" class="indexterm"></a><div class="variablelist"><dl><dt><span class="term"> DVD/CD-ROM </span></dt><dd><div class="para">
					If you have a DVD/CD-ROM drive and the Fedora CD-ROMs or DVD you can use this method. Refer to <a class="xref" href="s1-begininstall-cd-inst-x86.html" title="7.5.Â Installing from DVD/CD-ROM">SectionÂ 7.5, â€œInstalling from DVD/CD-ROMâ€</a>, for DVD/CD-ROM installation instructions.
				</div></dd><dt><span class="term"> Hard Drive </span></dt><dd><a id="id926561" 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> boot option). Refer to <a class="xref" href="s1-begininstall-hd-x86.html" title="7.6.Â Installing from a Hard Drive">SectionÂ 7.6, â€œInstalling from a Hard Driveâ€</a>, for hard drive installation instructions.
				</div></dd><dt><span class="term"> NFS </span></dt><dd><a id="id853719" 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> boot option). Refer to <a class="xref" href="s1-begininstall-nfs-x86.html" title="7.8.Â Installing via NFS">SectionÂ 7.8, â€œInstalling via NFSâ€</a> for network installation instructions. Note that NFS installations may also be performed in GUI mode.
				</div></dd><dt><span class="term"> URL </span></dt><dd><a id="id837962" 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> boot option). Refer to <a class="xref" href="s1-begininstall-url-x86.html" title="7.9.Â Installing via FTP or HTTP">SectionÂ 7.9, â€œ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="sn-welcome-x86.html" title="7.10.Â Welcome to Fedora">SectionÂ 7.10, â€œWelcome to Fedoraâ€</a>.
	</div><div class="note"><h2>CD/DVD Activity</h2><div class="para">
			If you boot any Fedora installation media, 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><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-x86-starting-bootopts.html"><strong>Prev</strong>7.3.2.Â Additional Boot Options</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-begininstall-cd-inst-x86.html"><strong>Next</strong>7.5.Â Installing from DVD/CD-ROM</a></li></ul></body></html>


--- NEW FILE s1-installpkgs-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.25.Â Installing Packages</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="s1-preparetoinstall-x86.html" title="7.24.Â Preparing to Install" /><link rel="next" href="s1-complete-x86.html" title="7.26.Â Installation Complete" /></head><body class="draft "><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 Sit
 e" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-preparetoinstall-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-complete-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-installpkgs-x86">7.25.Â Installing Packages</h2></div></div></div><div class="para">
	At this point there is nothing left for you to do until all the packages have been installed. How quickly this happens depends on the number of packages you have selected and your computer's speed.
</div><div class="para">
	Fedora reports the installation progress on the screen as it writes the selected packages to your system. Network and DVD installations require no further action. If you are using CDs to install, Fedora prompts you to change discs periodically. After you insert a disc, select <span class="guibutton"><strong>OK</strong></span> to resume the installation.
</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.
</div><div class="note"><h2>Installing from a Live Image</h2><div class="para">
		If you install from a Fedora Live image, no reboot prompt appears. You may continue to use the Live image as desired, and reboot the system at any time to enjoy the newly installed Fedora system.
	</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-preparetoinstall-x86.html"><strong>Prev</strong>7.24.Â Preparing to Install</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-complete-x86.html"><strong>Next</strong>7.26.Â Installation Complete</a></li></ul></body></html>


--- NEW FILE s1-kickstart2-file.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.3.Â Creating the Kickstart File</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-kickstart2.html" title="ChapterÂ 13.Â Kickstart Installations" /><link rel="prev" href="s1-kickstart2-howuse.html" title="13.2.Â How Do You Perform a Kickstart Installation?" /><link rel="next" href="s1-kickstart2-options.html" title="13.4.Â Kickstart Options" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kickstart2-howuse.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-kickstart2-options.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-kickstart2-file">13.3.Â Creating the Kickstart File</h2></div></div></div><a id="id802744" class="indexterm"></a><a id="id800667" class="indexterm"></a><a id="id895216" 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:
		</div><div class="itemizedlist"><ul><li><div class="para">
					Sections must be specified <span class="emphasis"><em>in order</em></span>. Items within the sections do not have to be in a specific order unless otherwise specified. The section order is:
				</div><div class="itemizedlist"><ul><li><div class="para">
							Command section â€” Refer to <a class="xref" href="s1-kickstart2-options.html" title="13.4.Â Kickstart Options">SectionÂ 13.4, â€œKickstart Optionsâ€</a> for a list of kickstart options. You must include the required options.
						</div></li><li><div class="para">
							The <code class="command">%packages</code> section â€” Refer to <a class="xref" href="s1-kickstart2-packageselection.html" title="13.5.Â Package Selection">SectionÂ 13.5, â€œPackage Selectionâ€</a> for details.
						</div></li><li><div class="para">
							The <code class="command">%pre</code> and <code class="command">%post</code> sections â€” These two sections can be in any order and are not required. Refer to <a class="xref" href="s1-kickstart2-preinstallconfig.html" title="13.6.Â Pre-installation Script">SectionÂ 13.6, â€œPre-installation Scriptâ€</a> and <a class="xref" href="s1-kickstart2-postinstallconfig.html" title="13.7.Â Post-installation Script">SectionÂ 13.7, â€œPost-installation Scriptâ€</a> for details.
						</div></li></ul></div></li><li><div class="para">
					Items that are not required can be omitted.
				</div></li><li><div class="para">
					Omitting any required item results in the installation program prompting the user for an answer to the related item, just as the user would be prompted during a typical installation. Once the answer is given, the installation continues unattended (unless it finds another missing item).
				</div></li><li><div class="para">
					Lines starting with a pound (also known as hash) sign (#) are treated as comments and are ignored.
				</div></li><li><div class="para">
					For kickstart <span class="emphasis"><em>upgrades</em></span>, the following items are required:
				</div><div class="itemizedlist"><ul><li><div class="para">
							Language
						</div></li><li><div class="para">
							Installation method
						</div></li><li><div class="para">
							Device specification (if device is needed to perform the installation)
						</div></li><li><div class="para">
							Keyboard setup
						</div></li><li><div class="para">
							The <code class="command">upgrade</code> keyword
						</div></li><li><div class="para">
							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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kickstart2-howuse.html"><strong>Prev</strong>13.2.Â How Do You Perform a Kickstart Installation?</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-kickstart2-options.html"><strong>Next</strong>13.4.Â Kickstart Options</a></li></ul></body></html>


--- NEW FILE s1-kickstart2-howuse.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.2.Â How Do You Perform a Kickstart Installation?</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-kickstart2.html" title="ChapterÂ 13.Â Kickstart Installations" /><link rel="prev" href="ch-kickstart2.html" title="ChapterÂ 13.Â Kickstart Installations" /><link rel="next" href="s1-kickstart2-file.html" title="13.3.Â Creating the Kickstart File" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-kickstart2.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-kickstart2-file.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-kickstart2-howuse">13.2.Â How Do You Perform a Kickstart Installation?</h2></div></div></div><div class="para">
			Kickstart installations can be performed using a local CD-ROM, a local hard drive, or via NFS, FTP, or HTTP.
		</div><div class="para">
			To use kickstart, you must:
		</div><div class="orderedlist"><ol><li><div class="para">
					Create a kickstart file.
				</div></li><li><div class="para">
					Create a boot media with the kickstart file or make the kickstart file available on the network.
				</div></li><li><div class="para">
					Make the installation tree available.
				</div></li><li><div class="para">
					Start the kickstart installation.
				</div></li></ol></div><div class="para">
			This chapter explains these steps in detail.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-kickstart2.html"><strong>Prev</strong>ChapterÂ 13.Â Kickstart Installations</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-kickstart2-file.html"><strong>Next</strong>13.3.Â Creating the Kickstart File</a></li></ul></body></html>


--- NEW FILE s1-kickstart2-install-tree.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.9.Â Making the Installation Tree Available</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-kickstart2.html" title="ChapterÂ 13.Â Kickstart Installations" /><link rel="prev" href="s2-kickstart2-networkbased.html" title="13.8.2.Â Making the Kickstart File Available on the Network" /><link rel="next" href="s1-kickstart2-startinginstall.html" title="13.10.Â Starting a Kickstart Installation" /></head><body class="draft "><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"><i
 mg src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kickstart2-networkbased.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-kickstart2-startinginstall.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-kickstart2-install-tree">13.9.Â Making the Installation Tree Available</h2></div></div></div><a id="id930742" 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 CD-ROMs with the same directory structure.
		</div><div class="para">
			If you are performing a CD-based installation, insert the Fedora CD-ROM #1 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 CD-ROMs are on a hard drive in the computer.
		</div><a id="id930772" class="indexterm"></a><a id="id930786" class="indexterm"></a><div class="para">
			If you are performing a network-based (NFS, FTP, or HTTP) installation, you must make the installation tree available over the network. Refer to <a class="xref" href="s1-steps-network-installs-x86.html" title="3.5.Â Preparing for a Network Installation">SectionÂ 3.5, â€œPreparing for a Network Installationâ€</a> for details.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kickstart2-networkbased.html"><strong>Prev</strong>13.8.2.Â Making the Kickstart File Available on th...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-kickstart2-startinginstall.html"><strong>Next</strong>13.10.Â Starting a Kickstart Installation</a></li></ul></body></html>


--- NEW FILE s1-kickstart2-options.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.4.Â Kickstart Options</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-kickstart2.html" title="ChapterÂ 13.Â Kickstart Installations" /><link rel="prev" href="s1-kickstart2-file.html" title="13.3.Â Creating the Kickstart File" /><link rel="next" href="s1-kickstart2-packageselection.html" title="13.5.Â Package Selection" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kickstart2-file.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-kickstart2-packageselection.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-kickstart2-options">13.4.Â Kickstart Options</h2></div></div></div><a id="id832079" class="indexterm"></a><a id="id784621" 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.html" title="ChapterÂ 14.Â Kickstart Configurator">ChapterÂ 14, <i>Kickstart Configurator</i></a> for details.
		</div><div class="note"><h2>Note</h2><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 class="variablelist"><dl><dt><span class="term"><code class="command">autopart</code> (optional) </span></dt><dd><div class="para">
						<a id="id874501" 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><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.
							</div></li><li><div class="para">
								<code class="command">--passphrase=</code> â€” Provide a default system-wide passphrase for all encrypted devices.
							</div></li></ul></div></dd><dt><span class="term"><code class="command">ignoredisk</code> (optional) </span></dt><dd><div class="para">
						<a id="id927249" 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 <code class="literal">ignoredisk</code> option is also useful if you have multiple paths to your disks.
					</div><div class="para">
						The syntax is:
					</div><pre class="screen">ignoredisk --drives=<em class="replaceable"><code>drive1,drive2</code></em>,...
</pre><div class="para">
						where <em class="replaceable"><code>driveN</code></em> is one of <code class="literal">sda</code>, <code class="literal">sdb</code>,..., <code class="literal">hda</code>,... etc.
					</div></dd><dt><span class="term"><code class="command">autostep</code> (optional) </span></dt><dd><div class="para">
						<a id="id922349" 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><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><span class="term"><code class="command">auth</code> or <code class="command">authconfig</code> (required) </span></dt><dd><div class="para">
						<a id="id866227" class="indexterm"></a>
						<a id="id866244" 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><div class="para">
								<code class="command">--enablemd5</code> â€” Use md5 encryption for user passwords.
							</div></li><li><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.
							</div></li><li><div class="para">
								<code class="command">--nisdomain=</code> â€” NIS domain name to use for NIS services.
							</div></li><li><div class="para">
								<code class="command">--nisserver=</code> â€” Server to use for NIS services (broadcasts by default).
							</div></li><li><div class="para">
								<code class="command">--useshadow</code> or <code class="command">--enableshadow</code> â€” Use shadow passwords.
							</div></li><li><div class="para">
								<code class="command">--enableldap</code> â€” Turns on LDAP support in <code class="filename">/etc/nsswitch.conf</code>, allowing your system to retrieve information about users (UIDs, home directories, shells, etc.) from an LDAP directory. To use this option, you must install the <code class="filename">nss_ldap</code> package. You must also specify a server and a base DN (distinguished name) with <code class="command">--ldapserver=</code> and <code class="command">--ldapbasedn=</code>.
							</div></li><li><div class="para">
								<code class="command">--enableldapauth</code> â€” Use LDAP as an authentication method. This enables the <code class="filename">pam_ldap</code> module for authentication and changing passwords, using an LDAP directory. To use this option, you must have the <code class="filename">nss_ldap</code> package installed. You must also specify a server and a base DN with <code class="command">--ldapserver=</code> and <code class="command">--ldapbasedn=</code>.
							</div></li><li><div class="para">
								<code class="command">--ldapserver=</code> â€” If you specified either <code class="command">--enableldap</code> or <code class="command">--enableldapauth</code>, use this option to specify the name of the LDAP server to use. This option is set in the <code class="filename">/etc/ldap.conf</code> file.
							</div></li><li><div class="para">
								<code class="command">--ldapbasedn=</code> â€” If you specified either <code class="command">--enableldap</code> or <code class="command">--enableldapauth</code>, use this option to specify the DN in your LDAP directory tree under which user information is stored. This option is set in the <code class="filename">/etc/ldap.conf</code> file.
							</div></li><li><div class="para">
								<code class="command">--enableldaptls</code> â€” Use TLS (Transport Layer Security) lookups. This option allows LDAP to send encrypted usernames and passwords to an LDAP server before authentication.
							</div></li><li><div class="para">
								<code class="command">--enablekrb5</code> â€” Use Kerberos 5 for authenticating users. Kerberos itself does not know about home directories, UIDs, or shells. If you enable Kerberos, you must make users' accounts known to this workstation by enabling LDAP, NIS, or Hesiod or by using the <code class="command">/usr/sbin/useradd</code> command. If you use this option, you must have the <code class="filename">pam_krb5</code> package installed.
							</div></li><li><div class="para">
								<code class="command">--krb5realm=</code> â€” The Kerberos 5 realm to which your workstation belongs.
							</div></li><li><div class="para">
								<code class="command">--krb5kdc=</code> â€” The KDC (or KDCs) that serve requests for the realm. If you have multiple KDCs in your realm, separate their names with commas (,).
							</div></li><li><div class="para">
								<code class="command">--krb5adminserver=</code> â€” The KDC in your realm that is also running kadmind. This server handles password changing and other administrative requests. This server must be run on the master KDC if you have more than one KDC.
							</div></li><li><div class="para">
								<code class="command">--enablehesiod</code> â€” Enable Hesiod support for looking up user home directories, UIDs, and shells. More information on setting up and using Hesiod on your network is in <code class="filename">/usr/share/doc/glibc-2.x.x/README.hesiod</code>, which is included in the <code class="filename">glibc</code> package. Hesiod is an extension of DNS that uses DNS records to store information about users, groups, and various other items.
							</div></li><li><div class="para">
								<code class="command">--hesiodlhs</code> â€” The Hesiod LHS ("left-hand side") option, set in <code class="filename">/etc/hesiod.conf</code>. This option is used by the Hesiod library to determine the name to search DNS for when looking up information, similar to LDAP's use of a base DN.
							</div></li><li><div class="para">
								<code class="command">--hesiodrhs</code> â€” The Hesiod RHS ("right-hand side") option, set in <code class="filename">/etc/hesiod.conf</code>. This option is used by the Hesiod library to determine the name to search DNS for when looking up information, similar to LDAP's use of a base DN.
							</div><div class="note"><h2>Note</h2><div class="para">
									To look up user information for "jim", the Hesiod library looks up <span class="emphasis"><em>jim.passwd<LHS><RHS></em></span>, which should resolve to a TXT record that looks like what his passwd entry would look like (<code class="computeroutput">jim:*:501:501:Jungle Jim:/home/jim:/bin/bash</code>). For groups, the situation is identical, except <span class="emphasis"><em>jim.group<LHS><RHS></em></span> would be used.
								</div><div class="para">
									Looking up users and groups by number is handled by making "501.uid" a CNAME for "jim.passwd", and "501.gid" a CNAME for "jim.group". Note that the library does not place a period <span class="keycap"><strong>.</strong></span> in front of the LHS and RHS values when performing a search. Therefore the LHS and RHS values need to have a period placed in front of them in order if they require this.
								</div></div></li><li><div class="para">
								<code class="command">--enablesmbauth</code> â€” Enables authentication of users against an SMB server (typically a Samba or Windows server). SMB authentication support does not know about home directories, UIDs, or shells. If you enable SMB, you must make users' accounts known to the workstation by enabling LDAP, NIS, or Hesiod or by using the <code class="command">/usr/sbin/useradd</code> command to make their accounts known to the workstation. To use this option, you must have the <code class="filename">pam_smb</code> package installed.
							</div></li><li><div class="para">
								<code class="command">--smbservers=</code> â€” The name of the server(s) to use for SMB authentication. To specify more than one server, separate the names with commas (,).
							</div></li><li><div class="para">
								<code class="command">--smbworkgroup=</code> â€” The name of the workgroup for the SMB servers.
							</div></li><li><div class="para">
								<code class="command">--enablecache</code> â€” Enables the <code class="command">nscd</code> service. The <code class="command">nscd</code> service caches information about users, groups, and various other types of information. Caching is especially helpful if you choose to distribute information about users and groups over your network using NIS, LDAP, or hesiod.
							</div></li></ul></div></dd><dt><span class="term"><code class="command">bootloader</code> (required)</span></dt><dd><div class="para">
						<a id="id801064" class="indexterm"></a>
						 Specifies how the boot loader should be installed. This option is required for both installations and upgrades.
					</div><div class="important"><h2>Important</h2><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 class="itemizedlist"><ul><li><div class="para">
								<code class="command">--append=</code> â€” Specifies kernel parameters. To specify multiple parameters, separate them with spaces. For example:
							</div><pre class="screen">bootloader --location=mbr --append="hdd=ide-scsi ide=nodma"
</pre></li><li><div class="para">
								<code class="command">--driveorder</code> â€” Specify which drive is first in the BIOS boot order. For example:
							</div><pre class="screen">bootloader --driveorder=sda,hda
</pre></li><li><div class="para">
								<code class="command">--location=</code> â€” Specifies where the boot record is written. Valid values are the following: <code class="command">mbr</code> (the default), <code class="command">partition</code> (installs the boot loader on the first sector of the partition containing the kernel), or <code class="command">none</code> (do not install the boot loader).
							</div></li><li><div class="para">
								<code class="command">--password=</code> â€” If using GRUB, sets the GRUB boot loader password to the one specified with this option. This should be used to restrict access to the GRUB shell, where arbitrary kernel options can be passed.
							</div></li><li><div class="para">
								<code class="command">--md5pass=</code> â€” If using GRUB, similar to <code class="command">--password=</code> except the password should already be encrypted.
							</div></li><li><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><span class="term"><code class="command">clearpart</code> (optional) </span></dt><dd><div class="para">
						<a id="id847744" class="indexterm"></a>
						 Removes partitions from the system, prior to creation of new partitions. By default, no partitions are removed.
					</div><div class="note"><h2>Note</h2><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.
						</div></div><div class="itemizedlist"><ul><li><div class="para">
								<code class="command">--all</code> â€” Erases all partitions from the system.
							</div></li><li><div class="para">
								<code class="command">--drives=</code> â€” Specifies which drives to clear partitions from. For example, the following clears all the partitions on the first two drives on the primary IDE controller:
							</div><pre class="screen">clearpart --drives=hda,hdb --all
</pre></li><li><div class="para">
								<code class="command">--initlabel</code> â€” Initializes the disk label to the default for your architecture (for example <code class="command">msdos</code> for x86 and <code class="command">gpt</code> for Itanium). It is useful so that the installation program does not ask if it should initialize the disk label if installing to a brand new hard drive.
							</div></li><li><div class="para">
								<code class="command">--linux</code> â€” Erases all Linux partitions.
							</div></li><li><div class="para">
								<code class="command">--none</code> (default) â€” Do not remove any partitions.
							</div></li></ul></div></dd><dt><span class="term"><code class="command">cmdline</code> (optional) </span></dt><dd><div class="para">
						<a id="id933951" class="indexterm"></a>
						 Perform the installation in a completely non-interactive command line mode. Any prompts for interaction halts the install. This mode is useful on IBM System z systems with the x3270 console.
					</div></dd><dt><span class="term"><code class="command">device</code> (optional) </span></dt><dd><div class="para">
						<a id="id843409" 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><type></code></em> <em class="replaceable"><code><moduleName></code></em> --opts=<em class="replaceable"><code><options></code></em>
</pre><div class="itemizedlist"><ul><li><div class="para">
								<em class="replaceable"><code><type></code></em> â€” Replace with either <code class="command">scsi</code> or <code class="command">eth</code>.
							</div></li><li><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><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><span class="term"><code class="command">driverdisk</code> (optional) </span></dt><dd><div class="para">
						<a id="id942556" 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> [--type=<em class="replaceable"><code><fstype></code></em>]
</pre><div class="para">
						Alternatively, a network location can be specified for the driver diskette:
					</div><pre class="screen">driverdisk --source=ftp://path/to/dd.img
driverdisk --source=http://path/to/dd.img
driverdisk --source=nfs:host:/path/to/img
</pre><div class="itemizedlist"><ul><li><div class="para">
								<em class="replaceable"><code><partition></code></em> â€” Partition containing the driver disk.
							</div></li><li><div class="para">
								<code class="command">--type=</code> â€” File system type (for example, vfat or ext2).
							</div></li></ul></div></dd><dt><span class="term"><code class="command">firewall</code> (optional) </span></dt><dd><div class="para">
						<a id="id924886" 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><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.
							</div></li><li><div class="para">
								<code class="command">--disabled</code> or <code class="command">--disable</code> â€” Do not configure any iptables rules.
							</div></li><li><div class="para">
								<code class="command">--trust=</code> â€” Listing a device here, such as eth0, allows all traffic coming from that device to go through the firewall. To list more than one device, use <code class="command">--trust eth0 --trust eth1</code>. Do NOT use a comma-separated format such as <code class="command">--trust eth0, eth1</code>.
							</div></li><li><div class="para">
								<em class="replaceable"><code><incoming></code></em> â€” Replace with one or more of the following to allow the specified services through the firewall.
							</div><div class="itemizedlist"><ul><li><div class="para">
										<code class="command">--ssh</code>
									</div></li><li><div class="para">
										<code class="command">--telnet</code>
									</div></li><li><div class="para">
										<code class="command">--smtp</code>
									</div></li><li><div class="para">
										<code class="command">--http</code>
									</div></li><li><div class="para">
										<code class="command">--ftp</code>
									</div></li></ul></div></li><li><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><span class="term"><code class="command">firstboot</code> (optional) </span></dt><dd><div class="para">
						<a id="id943532" class="indexterm"></a>
						<a id="id864687" class="indexterm"></a>
						 Determine whether the <span class="application"><strong>Setup Agent</strong></span> starts the first time the system is booted. If enabled, the <code class="command">firstboot</code> package must be installed. If not specified, this option is disabled by default.
					</div><div class="itemizedlist"><ul><li><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.
							</div></li><li><div class="para">
								<code class="command">--disable</code> or <code class="command">--disabled</code> â€” The <span class="application"><strong>Setup Agent</strong></span> is not started the first time the system boots.
							</div></li><li><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><span class="term"><code class="command">halt</code> (optional) </span></dt><dd><div class="para">
						<a id="id828976" 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, the <code class="command">reboot</code> option is used as default.
					</div><div class="para">
						The <code class="command">halt</code> option is roughly 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><span class="term"><code class="command">graphical</code> (optional) </span></dt><dd><div class="para">
						<a id="id834906" class="indexterm"></a>
						 Perform the kickstart installation in graphical mode. This is the default.
					</div></dd><dt><span class="term"><code class="command">install</code> (optional) </span></dt><dd><div class="para">
						<a id="id885022" 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="id885072" class="indexterm"></a><div class="itemizedlist"><ul><li><div class="para">
								<code class="command">cdrom</code> â€” Install from the first CD-ROM drive on the system.
							</div></li><li><div class="para">
								<code class="command">harddrive</code> â€” Install from a Red Hat installation tree on a local drive, which must be either vfat or ext2.
							</div><div class="itemizedlist"><ul><li><div class="para">
										<code class="command">--biospart=</code>
									</div><div class="para">
										BIOS partition to install from (such as 82).
									</div></li><li><div class="para">
										<code class="command">--partition=</code>
									</div><div class="para">
										Partition to install from (such as sdb2).
									</div></li><li><div class="para">
										<code class="command">--dir=</code>
									</div><div class="para">
										Directory containing the <code class="filename"><em class="replaceable"><code>variant</code></em></code> directory of the installation tree.
									</div></li></ul></div><div class="para">
								For example:
							</div><pre class="screen">harddrive --partition=hdb2 --dir=/tmp/install-tree
</pre></li><li><div class="para">
								<code class="command">nfs</code> â€” Install from the NFS server specified.
							</div><div class="itemizedlist"><ul><li><div class="para">
										<code class="command">--server=</code>
									</div><div class="para">
										Server from which to install (hostname or IP).
									</div></li><li><div class="para">
										<code class="command">--dir=</code>
									</div><div class="para">
										Directory containing the <code class="filename"><em class="replaceable"><code>variant</code></em></code> directory of the installation tree.
									</div></li><li><div class="para">
										<code class="command">--opts=</code>
									</div><div class="para">
										Mount options to use for mounting the NFS export. (optional)
									</div></li></ul></div><div class="para">
								For example:
							</div><pre class="screen">nfs --server=nfsserver.example.com --dir=/tmp/install-tree
</pre></li><li><div class="para">
								<code class="command">url</code> â€” Install from an installation tree on a remote server via FTP or HTTP.
							</div><div class="para">
								For example:
							</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><span class="term"><code class="command">interactive</code> (optional) </span></dt><dd><div class="para">
						<a id="id941437" class="indexterm"></a>
						 Uses the information provided in the kickstart file during the installation, but allow for inspection and modification of the values given. You are presented with each screen of the installation program with the values from the kickstart file. Either accept the values by clicking <span class="guibutton"><strong>Next</strong></span> or change the values and click <span class="guibutton"><strong>Next</strong></span> to continue. Refer to the <code class="command">autostep</code> command.
					</div></dd><dt><span class="term"><code class="command">iscsi</code> (optional)</span></dt><dd><div class="para">
						<a id="id822843" class="indexterm"></a>
						 issci --ipaddr= [options].
					</div><div class="itemizedlist"><ul><li><div class="para">
								<code class="command">--target</code> â€”
							</div></li><li><div class="para">
								<code class="command">--port=</code> â€”
							</div></li><li><div class="para">
								<code class="command">--user=</code> â€”
							</div></li><li><div class="para">
								<code class="command">--password=</code> â€”
							</div></li></ul></div></dd><dt><span class="term"><code class="command">key</code> (optional)</span></dt><dd><div class="para">
						<a id="id836702" class="indexterm"></a>
						 Specify an installation key, which is needed to aid in package selection and identify your system for support purposes. This command is specific to Red Hat Enterprise Linux; it has no meaning for Fedora and will be ignored.
					</div><div class="itemizedlist"><ul><li><div class="para">
								<code class="command">--skip</code> â€” Skip entering a key. Usually if the key command is not given, anaconda will pause at this step to prompt for a key. This option allows automated installation to continue if you do not have a key or do not want to provide one.
							</div></li></ul></div></dd><dt><span class="term"><code class="command">keyboard</code> (required) </span></dt><dd><div class="para">
						<a id="id854733" class="indexterm"></a>
						 Sets system keyboard type. Here is the list of available keyboards on i386, Itanium, and Alpha machines:
					</div><pre class="screen">
be-latin1, bg, br-abnt2, cf, cz-lat2, cz-us-qwertz, de, de-latin1, 
de-latin1-nodeadkeys, dk, dk-latin1, dvorak, es, et, fi, fi-latin1, 
fr, fr-latin0, fr-latin1, fr-pc, fr_CH, fr_CH-latin1, gr, hu, hu101, 
is-latin1, it, it-ibm, it2, jp106, la-latin1, mk-utf, no, no-latin1, 
pl, pt-latin1, ro_win, ru, ru-cp1251, ru-ms, ru1, ru2,  ru_win, 
se-latin1, sg, sg-latin1, sk-qwerty, slovene, speakup,  speakup-lt, 
sv-latin1, sg, sg-latin1, sk-querty, slovene, trq, ua,  uk, us, us-acentos
</pre><div class="para">
						The file <code class="filename">/usr/lib/python2.2/site-packages/rhpl/keyboard_models.py</code> also contains this list and is part of the <code class="filename">rhpl</code> package.
					</div></dd><dt><span class="term"><code class="command">lang</code> (required) 
				<a id="id854789" 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">
						The file <code class="filename">/usr/share/system-config-language/locale-list</code> provides a list of the valid language codes in the first column of each line and is part of the <code class="filename">system-config-language</code> package.
					</div><div class="para">
						Certain languages (mainly Chinese, Japanese, Korean, and Indic languages) are not supported during text mode installation. If one of these languages is specified using the lang command, installation will continue in English though the running system will have the specified langauge by default.
					</div></dd><dt><span class="term"><code class="command">langsupport</code> (deprecated) 
				<a id="id844325" 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><span class="term"><code class="command">logvol</code> (optional) 
				<a id="id844382" class="indexterm"></a>
				<a id="id869788" class="indexterm"></a>
				<a id="id869801" 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">
						The options are as follows:
					</div><div class="itemizedlist"><ul><li><div class="para">
								<code class="command">--noformat</code> â€” Use an existing logical volume and do not format it.
							</div></li><li><div class="para">
								<code class="command">--useexisting</code> â€” Use an existing logical volume and reformat it.
							</div></li><li><div class="para">
								<code class="command">--fstype=</code> â€” Sets the file system type for the logical volume. Valid values are <code class="command">xfs</code>, <code class="command">ext2</code>, <code class="command">ext3</code>, <code class="command">ext4</code>, <code class="command">swap</code>, <code class="command">vfat</code>, and <code class="command">hfs</code>.
							</div></li><li><div class="para">
								<code class="command">--fsoptions=</code> â€” Specifies a free form string of options to be used when mounting the filesystem. This string will be copied into the <code class="filename">/etc/fstab</code> file of the installed system and should be enclosed in quotes.
							</div></li><li><div class="para">
								<code class="command">--bytes-per-inode=</code> â€” Specifies the size of inodes on the filesystem to be made on the logical volume. Not all filesystems support this option, so it is silently ignored for those cases.
							</div></li><li><div class="para">
								<code class="command">--grow=</code> â€” Tells the logical volume to grow to fill available space (if any), or up to the maximum size setting.
							</div></li><li><div class="para">
								<code class="command">--maxsize=</code> â€” The maximum size in megabytes when the logical volume is set to grow. Specify an integer value here, and do not append the number with MB.
							</div></li><li><div class="para">
								<code class="command">--recommended=</code> â€” Determine the size of the logical volume automatically.
							</div></li><li><div class="para">
								<code class="command">--percent=</code> â€” Specify the size of the logical volume as a percentage of available space in the volume group.
							</div></li></ul></div><div class="para">
						Create the partition first, create the logical volume group, and then create the logical volume. For example:
					</div><pre class="screen">part pv.01 --size 3000 
volgroup myvg pv.01
logvol / --vgname=myvg --size=2000 --name=rootvol
</pre></dd><dt><span class="term"><code class="command">logging</code> (optional) 
				<a id="id904460" 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><div class="para">
								<code class="command">--host=</code> â€” Send logging information to the given remote host, which must be running a syslogd process configured to accept remote logging.
							</div></li><li><div class="para">
								<code class="command">--port=</code> â€” If the remote syslogd process uses a port other than the default, it may be specified with this option.
							</div></li><li><div class="para">
								<code class="command">--level=</code> â€” One of debug, info, warning, error, or critical.
							</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><span class="term"><code class="command">mediacheck</code> (optional) 
				<a id="id804536" 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><span class="term"><code class="command">monitor</code> (optional) 
				<a id="id967860" 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><div class="para">
								<code class="command">--hsync=</code> â€” Specifies the horizontal sync frequency of the monitor.
							</div></li><li><div class="para">
								<code class="command">--monitor=</code> â€” Use specified monitor; monitor name should be from the list of monitors in /usr/share/hwdata/MonitorsDB from the hwdata package. The list of monitors can also be found on the X Configuration screen of the Kickstart Configurator. This is ignored if --hsync or --vsync is provided. If no monitor information is provided, the installation program tries to probe for it automatically.
							</div></li><li><div class="para">
								<code class="command">--noprobe=</code> â€” Do not try to probe the monitor.
							</div></li><li><div class="para">
								<code class="command">--vsync=</code> â€” Specifies the vertical sync frequency of the monitor.
							</div></li></ul></div></dd><dt><span class="term"><code class="command">mouse</code> (deprecated) 
				<a id="id832515" class="indexterm"></a>
				</span></dt><dd><div class="para">
						The mouse keyword is deprecated.
					</div></dd><dt><span class="term"><code class="command">network</code> (optional) 
				<a id="id832552" class="indexterm"></a>
				</span></dt><dd><div class="para">
						Configures network information for the system. If the kickstart installation does not require networking (in other words, it is not installed over NFS, HTTP, or FTP), networking is not configured for the system. If the installation does require networking and network information is not provided in the kickstart file, the installation program assumes that the installation should be done over eth0 via a dynamic IP address (BOOTP/DHCP), and configures the final, installed system to determine its IP address dynamically. The <code class="command">network</code> option configures networking information for kickstart installations via a network as well as for the installed system.
					</div><div class="itemizedlist"><ul><li><div class="para">
								<code class="command">--bootproto=</code> â€” One of <code class="command">dhcp</code>, <code class="command">bootp</code>, or <code class="command">static</code>.
							</div><div class="para">
								It defaults to <code class="command">dhcp</code>. <code class="command">bootp</code> and <code class="command">dhcp</code> are treated the same.
							</div><div class="para">
								The DHCP method uses a DHCP server system to obtain its networking configuration. As you might guess, the BOOTP method is similar, requiring a BOOTP server to supply the networking configuration. To direct a system to use DHCP:
							</div><pre class="screen">network --bootproto=dhcp
</pre><div class="para">
								To direct a machine to use BOOTP to obtain its networking configuration, use the following line in the kickstart file:
							</div><pre class="screen">network --bootproto=bootp
</pre><div class="para">
								The static method requires that you enter all the required networking information in the kickstart file. As the name implies, this information is static and are used during and after the installation. The line for static networking is more complex, as you must include all network configuration information on one line. You must specify the IP address, netmask, gateway, and nameserver. For example: (the "\" indicates that this should be read as one continuous line):
							</div><pre class="screen">network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0 \
--gateway=10.0.2.254 --nameserver=10.0.2.1
</pre><div class="para">
								If you use the static method, be aware of the following two restrictions:
							</div><div class="itemizedlist"><ul><li><div class="para">
										All static networking configuration information must be specified on <span class="emphasis"><em>one</em></span> line; you cannot wrap lines using a backslash, for example.
									</div></li><li><div class="para">
										You can also configure multiple nameservers here. To do so, specify them as a comma-delimited list in the command line. For example:
									</div><pre class="screen">network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0 \
--gateway=10.0.2.254 --nameserver 192.168.2.1,192.168.3.1
</pre></li></ul></div></li><li><div class="para">
								<code class="command">--device=</code> â€” Used to select a specific Ethernet device for installation. Note that using <code class="command">--device=</code> is not effective unless the kickstart file is a local file (such as <code class="command">ks=floppy</code>), since the installation program configures the network to find the kickstart file. For example:
							</div><pre class="screen">network --bootproto=dhcp --device=eth0
</pre></li><li><div class="para">
								<code class="command">--ip=</code> â€” IP address for the machine to be installed.
							</div></li><li><div class="para">
								<code class="command">--gateway=</code> â€” Default gateway as an IP address.
							</div></li><li><div class="para">
								<code class="command">--nameserver=</code> â€” Primary nameserver, as an IP address.
							</div></li><li><div class="para">
								<code class="command">--nodns</code> â€” Do not configure any DNS server.
							</div></li><li><div class="para">
								<code class="command">--netmask=</code> â€” Netmask for the installed system.
							</div></li><li><div class="para">
								<code class="command">--hostname=</code> â€” Hostname for the installed system.
							</div></li><li><div class="para">
								<code class="command">--ethtool=</code> â€” Specifies additional low-level settings for the network device which will be passed to the ethtool program.
							</div></li><li><div class="para">
								<code class="command">--essid=</code> â€” The network ID for wireless networks.
							</div></li><li><div class="para">
								<code class="command">--wepkey=</code> â€” The encryption key for wireless networks.
							</div></li><li><div class="para">
								<code class="command">--onboot=</code> â€” Whether or not to enable the device at boot time.
							</div></li><li><div class="para">
								<code class="command">--class=</code> â€” The DHCP class.
							</div></li><li><div class="para">
								<code class="command">--mtu=</code> â€” The MTU of the device.
							</div></li><li><div class="para">
								<code class="command">--noipv4</code> â€” Disable IPv4 on this device.
							</div></li><li><div class="para">
								<code class="command">--noipv6</code> â€” Disable IPv6 on this device.
							</div></li></ul></div></dd><dt><span class="term"><code class="command">multipath</code> (optional) 
				<a id="id837117" class="indexterm"></a>
				</span></dt><dd><div class="para">
						multipath --name= --device= --rule=
					</div></dd><dt><span class="term"> <a id="id837148" class="indexterm"></a>
				<a id="id837165" 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">
						If more than one Fedora installation exists on the system on different partitions, the installation program prompts the user and asks which installation to upgrade.
					</div><div class="warning"><h2>Warning</h2><div class="para">
							All partitions created are formatted as part of the installation process unless <code class="command">--noformat</code> and <code class="command">--onpart</code> are used.
						</div></div><div class="important"><h2>Important</h2><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 class="para">
						For a detailed example of <code class="command">part</code> in action, refer to <a class="xref" href="s1-kickstart2-options.html#s2-kickstart2-options-part-examples" title="13.4.1.Â Advanced Partitioning Example">SectionÂ 13.4.1, â€œAdvanced Partitioning Exampleâ€</a>.
					</div><div class="itemizedlist"><ul><li><div class="para">
								<em class="replaceable"><code><mntpoint></code></em> â€” The <em class="replaceable"><code><mntpoint></code></em> is where the partition is mounted and must be of one of the following forms:
							</div><div class="itemizedlist"><ul><li><div class="para">
										<code class="filename">/<em class="replaceable"><code><path></code></em></code>
									</div><div class="para">
										For example, <code class="command">/</code>, <code class="command">/usr</code>, <code class="command">/home</code>
									</div></li><li><div class="para">
										<code class="command">swap</code>
									</div><div class="para">
										The partition is used as swap space.
									</div><div class="para">
										To determine the size of the swap partition automatically, use the <code class="command">--recommended</code> option:
									</div><pre class="screen">swap --recommended
</pre><div class="para">
										The recommended maximum swap size for machines with less than 2GB of RAM is twice the amount of RAM. For machines with 2GB or more, this recommendation changes to 2GB plus the amount of RAM.
									</div></li><li><div class="para">
										<code class="command">raid.<em class="replaceable"><code><id></code></em></code>
									</div><div class="para">
										The partition is used for software RAID (refer to <code class="command">raid</code>).
									</div></li><li><div class="para">
										<code class="command">pv.<em class="replaceable"><code><id></code></em></code>
									</div><div class="para">
										The partition is used for LVM (refer to <code class="command">logvol</code>).
									</div></li></ul></div></li><li><div class="para">
								<code class="command">--size=</code> â€” The minimum partition size in megabytes. Specify an integer value here such as 500. Do not append the number with MB.
							</div></li><li><div class="para">
								<code class="command">--grow</code> â€” Tells the partition to grow to fill available space (if any), or up to the maximum size setting.
							</div><div class="note"><h2>Note</h2><div class="para">
									If you use <code class="command">--grow=</code> without setting <code class="command">--maxsize=</code> on a swap partition, <span class="application"><strong>Anaconda</strong></span> will limit the maximum size of the swap partition. For systems that have less than 2GB of physical memory, the imposed limit is twice the amount of physical memory. For systems with more than 2GB, the imposed limit is the size of physical memory plus 2GB.
								</div></div></li><li><div class="para">
								<code class="command">--maxsize=</code> â€” The maximum partition size in megabytes when the partition is set to grow. Specify an integer value here, and do not append the number with MB.
							</div></li><li><div class="para">
								<code class="command">--noformat</code> â€” Tells the installation program not to format the partition, for use with the <code class="command">--onpart</code> command.
							</div></li><li><div class="para">
								<code class="command">--onpart=</code> or <code class="command">--usepart=</code> â€” Put the partition on the <span class="emphasis"><em>already existing</em></span> device. For example:
							</div><pre class="screen">partition /home --onpart=hda1
</pre><div class="para">
								puts <code class="filename">/home</code> on <code class="filename">/dev/hda1</code>, which must already exist.
							</div></li><li><div class="para">
								<code class="command">--ondisk=</code> or <code class="command">--ondrive=</code> â€” Forces the partition to be created on a particular disk. For example, <code class="command">--ondisk=sdb</code> puts the partition on the second SCSI disk on the system.
							</div></li><li><div class="para">
								<code class="command">--asprimary</code> â€” Forces automatic allocation of the partition as a primary partition, or the partitioning fails.
							</div></li><li><div class="para">
								<code class="command">--type=</code> (replaced by <code class="command">fstype</code>) â€” This option is no longer available. Use <code class="command">fstype</code>.
							</div></li><li><div class="para">
								<code class="command">--fstype=</code> â€” Sets the file system type for the partition. Valid values are <code class="command">xfs</code>, <code class="command">ext2</code>, <code class="command">ext3</code>, <code class="command">ext4</code>, <code class="command">swap</code>, <code class="command">vfat</code>, and <code class="command">hfs</code>.
							</div></li><li><div class="para">
								<code class="command">--start=</code> â€” Specifies the starting cylinder for the partition. It requires that a drive be specified with <code class="command">--ondisk=</code> or <code class="command">ondrive=</code>. It also requires that the ending cylinder be specified with <code class="command">--end=</code> or the partition size be specified with <code class="command">--size=</code>.
							</div></li><li><div class="para">
								<code class="command">--end=</code> â€” Specifies the ending cylinder for the partition. It requires that the starting cylinder be specified with <code class="command">--start=</code>.
							</div></li><li><div class="para">
								<code class="command">--bytes-per-inode=</code> â€” Specifies the size of inodes on the filesystem to be made on the partition. Not all filesystems support this option, so it is silently ignored for those cases.
							</div></li><li><div class="para">
								<code class="command">--recommended</code> â€” Determine the size of the partition automatically.
							</div></li><li><div class="para">
								<code class="command">--onbiosdisk</code> â€” Forces the partition to be created on a particular disk as discovered by the BIOS.
							</div></li><li><div class="para">
								<code class="command">--encrypted</code> â€” Specifies that this partition should be encrypted.
							</div></li><li><div class="para">
								<code class="command">--passphrase=</code> â€” Specifies the passphrase to use when encrypting this partition. Without the above <code class="command">--encrypted</code> option, this option does nothing. If no passphrase is specified, the default system-wide one is used, or the installer will stop and prompt if there is no default.
							</div></li></ul></div><div class="note"><h2>Note</h2><div class="para">
							If partitioning fails for any reason, diagnostic messages appear on virtual console 3.
						</div></div></dd><dt><span class="term">
				<a id="id894431" 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">reboot</code> option is used as default.
					</div><div class="para">
						The <code class="command">poweroff</code> option is roughly equivalent to the <code class="command">shutdown -p</code> command.
					</div><div class="note"><h2>Note</h2><div class="para">
							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 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><span class="term">
				<a id="id807744" class="indexterm"></a>
				<a id="id965931" 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><div class="para">
								<em class="replaceable"><code><mntpoint></code></em> â€” Location where the RAID file system is mounted. If it is <code class="filename">/</code>, the RAID level must be 1 unless a boot partition (<code class="filename">/boot</code>) is present. If a boot partition is present, the <code class="filename">/boot</code> partition must be level 1 and the root (<code class="filename">/</code>) partition can be any of the available types. The <em class="replaceable"><code><partitions*></code></em> (which denotes that multiple partitions can be listed) lists the RAID identifiers to add to the RAID array.
							</div></li><li><div class="para">
								<code class="command">--level=</code> â€” RAID level to use (0, 1, or 5).
							</div></li><li><div class="para">
								<code class="command">--device=</code> â€” Name of the RAID device to use (such as md0 or md1). RAID devices range from md0 to md15, and each may only be used once.
							</div></li><li><div class="para">
								<code class="command">--bytes-per-inode=</code> â€” Specifies the size of inodes on the filesystem to be made on the RAID device. Not all filesystems support this option, so it is silently ignored for those cases.
							</div></li><li><div class="para">
								<code class="command">--spares=</code> â€” Specifies the number of spare drives allocated for the RAID array. Spare drives are used to rebuild the array in case of drive failure.
							</div></li><li><div class="para">
								<code class="command">--fstype=</code> â€” Sets the file system type for the RAID array. Valid values are <code class="command">xfs</code>, <code class="command">ext2</code>, <code class="command">ext3</code>, <code class="command">ext4</code>, <code class="command">swap</code>, <code class="command">vfat</code>, and <code class="command">hfs</code>.
							</div></li><li><div class="para">
								<code class="command">--fsoptions=</code> â€” Specifies a free form string of options to be used when mounting the filesystem. This string will be copied into the /etc/fstab file of the installed system and should be enclosed in quotes.
							</div></li><li><div class="para">
								<code class="command">--noformat</code> â€” Use an existing RAID device and do not format the RAID array.
							</div></li><li><div class="para">
								<code class="command">--useexisting</code> â€” Use an existing RAID device and reformat it.
							</div></li><li><div class="para">
								<code class="command">--encrypted</code> â€” Specifies that this RAID device should be encrypted.
							</div></li><li><div class="para">
								<code class="command">--passphrase=</code> â€” Specifies the passphrase to use when encrypting this RAID device. Without the above <code class="command">--encrypted</code> option, this option does nothing. If no passphrase is specified, the default system-wide one is used, or the installer will stop and prompt if there is no default.
							</div></li></ul></div><div class="para">
						The following example shows how to create a RAID level 1 partition for <code class="filename">/</code>, and a RAID level 5 for <code class="filename">/usr</code>, assuming there are three SCSI disks on the system. It also creates three swap partitions, one on each drive.
					</div><pre class="screen">part raid.01 --size=60 --ondisk=sda
part raid.02 --size=60 --ondisk=sdb 
part raid.03 --size=60 --ondisk=sdc
</pre><pre class="screen">part swap --size=128 --ondisk=sda  
part swap --size=128 --ondisk=sdb  
part swap --size=128 --ondisk=sdc
</pre><pre class="screen">part raid.11 --size=1 --grow --ondisk=sda  
part raid.12 --size=1 --grow --ondisk=sdb  
part raid.13 --size=1 --grow --ondisk=sdc
</pre><pre class="screen">raid / --level=1 --device=md0 raid.01 raid.02 raid.03  
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="s1-kickstart2-options.html#s2-kickstart2-options-part-examples" title="13.4.1.Â Advanced Partitioning Example">SectionÂ 13.4.1, â€œAdvanced Partitioning Exampleâ€</a>.
					</div></dd><dt><span class="term"> <a id="id842101" 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">
						The <code class="command">reboot</code> option is roughly equivalent to the <code class="command">shutdown -r</code> command.
					</div><div class="note"><h2>Note</h2><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 class="para">
							The <code class="command">reboot</code> option is the default completion method if no other methods are explicitly specified in the kickstart file.
						</div></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">shutdown</code> kickstart options.
					</div></dd><dt><span class="term"><code class="command">repo</code> (optional) 
				<a id="id869712" 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>]
</pre><div class="itemizedlist"><ul><li><div class="para">
								<code class="command">--name=</code> â€” The repo id. This option is required.
							</div></li><li><div class="para">
								<code class="command">--baseurl=</code> â€” The URL 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 --mirrorlist, not both.
							</div></li><li><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><span class="term"><code class="command">rootpw</code> (required) </span></dt><dd><div class="para">
						<a id="id799370" 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><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><span class="term"><code class="command">selinux</code> (optional) </span></dt><dd><div class="para">
						<a id="id909005" 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><div class="para">
								<code class="command">--enforcing</code> â€” Enables SELinux with the default targeted policy being enforced.
							</div><div class="note"><h2>Note</h2><div class="para">
									If the <code class="command">selinux</code> option is not present in the kickstart file, SELinux is enabled and set to <code class="command">--enforcing</code> by default.
								</div></div></li><li><div class="para">
								<code class="command">--permissive</code> â€” Outputs warnings based on the SELinux policy, but does not actually enforce the policy.
							</div></li><li><div class="para">
								<code class="command">--disabled</code> â€” Disables SELinux completely on the system.
							</div></li></ul></div><div class="para">
						For complete information regarding SELinux for Fedora, refer to the <em class="citetitle">Fedora 11 Security-Enhanced Linux User Guide</em>.
					</div></dd><dt><span class="term"><code class="command">services</code> (optional) </span></dt><dd><div class="para">
						<a id="id867000" class="indexterm"></a>
						 Modifies the default set of services that will run under the default runlevel. The services listed in the disabled list will be disabled before the services listed in the enabled list are enabled.
					</div><div class="itemizedlist"><ul><li><div class="para">
								<code class="command">--disabled</code> â€” Disable the services given in the comma separated list.
							</div></li><li><div class="para">
								<code class="command">--enabled</code> â€” Enable the services given in the comma separated list.
							</div></li></ul></div><div class="important"><h2>Do not include spaces in the list of services</h2><div class="para">
							If you include spaces in the comma-separated list, kickstart will enable or disable only the services up to the first space. For example:
						</div><div class="para">
							<code class="command">services --disabled auditd, cups,smartd, nfslock</code>
						</div><div class="para">
							will disable only the <span class="application"><strong>auditd</strong></span> service. To disable all four services, this entry should include no spaces between services:
						</div><div class="para">
							<code class="command">services --disabled auditd,cups,smartd,nfslock</code>
						</div></div></dd><dt><span class="term"><code class="command">shutdown</code> (optional) </span></dt><dd><div class="para">
						<a id="id837717" 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">reboot</code> option is used as default.
					</div><div class="para">
						The <code class="command">shutdown</code> option is roughly 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><span class="term"><code class="command">skipx</code> (optional) </span></dt><dd><div class="para">
						<a id="id807115" class="indexterm"></a>
						 If present, X is not configured on the installed system.
					</div></dd><dt><span class="term"><code class="command">text</code> (optional) </span></dt><dd><div class="para">
						<a id="id793297" class="indexterm"></a>
						 Perform the kickstart installation in text mode. Kickstart installations are performed in graphical mode by default.
					</div><div class="important"><h2>Important</h2><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></dd><dt><span class="term"><code class="command">timezone</code> (required) </span></dt><dd><div class="para">
						<a id="id822624" 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><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><span class="term"><code class="command">upgrade</code> (optional) </span></dt><dd><div class="para">
						<a id="id826788" 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><span class="term"><code class="command">user</code> (optional) </span></dt><dd><div class="para">
						<a id="id788092" 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><div class="para">
								<code class="command">--name=</code> â€” Provides the name of the user. This option is required.
							</div></li><li><div class="para">
								<code class="command">--groups=</code> â€” In addition to the default group, a comma separated list of group names the user should belong to.
							</div></li><li><div class="para">
								<code class="command">--homedir=</code> â€” The home directory for the user. If not provided, this defaults to /home/<em class="replaceable"><code><username></code></em>.
							</div></li><li><div class="para">
								<code class="command">--password=</code> â€” The new user's password. If not provided, the account will be locked by default.
							</div></li><li><div class="para">
								<code class="command">--iscrypted=</code> â€” Is the password provided by --password already encrypted or not?
							</div></li><li><div class="para">
								<code class="command">--shell=</code> â€” The user's login shell. If not provided, this defaults to the system default.
							</div></li><li><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><span class="term"><code class="command">vnc</code> (optional) </span></dt><dd><div class="para">
						<a id="id808393" 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><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.
							</div></li><li><div class="para">
								<code class="command">--port=</code> â€” Provide a port that the remote VNC viewer process is listening on. If not provided, anaconda will use the VNC default.
							</div></li><li><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><span class="term"><code class="command">volgroup</code> (optional) </span></dt><dd><div class="para">
						<a id="id811733" 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:
					</div><div class="itemizedlist"><ul><li><div class="para">
								<code class="command">--noformat</code> â€” Use an existing volume group and do not format it.
							</div></li><li><div class="para">
								<code class="command">--useexisting</code> â€” Use an existing volume group and reformat it.
							</div></li><li><div class="para">
								<code class="command">--pesize=</code> â€” Set the size of the physical extents.
							</div></li></ul></div><div class="para">
						Create the partition first, create the logical volume group, and then create the logical volume. For example:
					</div><pre class="screen">part pv.01 --size 3000 
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="s1-kickstart2-options.html#s2-kickstart2-options-part-examples" title="13.4.1.Â Advanced Partitioning Example">SectionÂ 13.4.1, â€œAdvanced Partitioning Exampleâ€</a>.
					</div></dd><dt><span class="term"><code class="command">xconfig</code> (optional) </span></dt><dd><div class="para">
						<a id="id960351" class="indexterm"></a>
						 Configures the X Window System. If this option is not given, the user must configure X manually during the installation, if X was installed; this option should not be used if X is not installed on the final system.
					</div><div class="itemizedlist"><ul><li><div class="para">
								<code class="command">--driver</code> â€” Specify the X driver to use for the video hardware.
							</div></li><li><div class="para">
								<code class="command">--videoram=</code> â€” Specifies the amount of video RAM the video card has.
							</div></li><li><div class="para">
								<code class="command">--defaultdesktop=</code> â€” Specify either GNOME or KDE to set the default desktop (assumes that GNOME Desktop Environment and/or KDE Desktop Environment has been installed through <code class="command">%packages</code>).
							</div></li><li><div class="para">
								<code class="command">--startxonboot</code> â€” Use a graphical login on the installed system.
							</div></li><li><div class="para">
								<code class="command">--resolution=</code> â€” Specify the default resolution for the X Window System on the installed system. Valid values are 640x480, 800x600, 1024x768, 1152x864, 1280x1024, 1400x1050, 1600x1200. Be sure to specify a resolution that is compatible with the video card and monitor.
							</div></li><li><div class="para">
								<code class="command">--depth=</code> â€” Specify the default color depth for the X Window System on the installed system. Valid values are 8, 16, 24, and 32. Be sure to specify a color depth that is compatible with the video card and monitor.
							</div></li></ul></div></dd><dt><span class="term"><code class="command">zerombr</code> (optional) </span></dt><dd><div class="para">
						<a id="id876239" 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><span class="term"><code class="command">zfcp</code> (optional) </span></dt><dd><div class="para">
						<a id="id800176" class="indexterm"></a>
						 Define a Fiber channel device (IBM System z).
					</div><div class="para">
						<code class="command">zfcp [--devnum=<em class="replaceable"><code><devnum></code></em>] [--fcplun=<em class="replaceable"><code><fcplun></code></em>] [--scsiid=<em class="replaceable"><code><scsiid></code></em>] [--scsilun=<em class="replaceable"><code><scsilun></code></em>] [--wwpn=<em class="replaceable"><code><wwpn></code></em>]</code>
					</div></dd><dt><span class="term"><code class="command">%include</code> (optional)</span></dt><dd><div class="para">
						<a id="id868520" class="indexterm"></a>
						<a id="id868534" 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" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-kickstart2-options-part-examples">13.4.1.Â Advanced Partitioning Example</h3></div></div></div><a id="id787866" 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 
part raid.11    --size 1000     --asprimary     --ondrive=hda 
part raid.12    --size 1000     --asprimary     --ondrive=hda 
part raid.13    --size 2000     --asprimary     --ondrive=hda 
part raid.14    --size 8000                     --ondrive=hda 
part raid.15    --size 1 --grow                 --ondrive=hda             
part raid.21    --size 1000     --asprimary     --ondrive=hdc 
part raid.22    --size 1000     --asprimary     --ondrive=hdc 
part raid.23    --size 2000     --asprimary     --ondrive=hdc 
part raid.24    --size 8000                     --ondrive=hdc 
part raid.25    --size 1 --grow                 --ondrive=hdc  

# You can add --spares=x  
raid /          --fstype ext3 --device md0 --level=RAID1 raid.11 raid.21 
raid /safe      --fstype ext3 --device md1 --level=RAID1 raid.12 raid.22 
raid swap       --fstype swap --device md2 --level=RAID1 raid.13 raid.23 
raid /usr       --fstype ext3 --device md3 --level=RAID1 raid.14 raid.24 
raid pv.01      --fstype ext3 --device md4 --level=RAID1 raid.15 raid.25  

# LVM configuration so that we can resize /var and /usr/local later 
volgroup sysvg pv.01     
logvol /var             --vgname=sysvg  --size=8000     --name=var 
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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kickstart2-file.html"><strong>Prev</strong>13.3.Â Creating the Kickstart File</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-kickstart2-packageselection.html"><strong>Next</strong>13.5.Â Package Selection</a></li></ul></body></html>


--- NEW FILE s1-kickstart2-packageselection.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.5.Â Package Selection</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-kickstart2.html" title="ChapterÂ 13.Â Kickstart Installations" /><link rel="prev" href="s1-kickstart2-options.html" title="13.4.Â Kickstart Options" /><link rel="next" href="s1-kickstart2-preinstallconfig.html" title="13.6.Â Pre-installation Script" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kickstart2-options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-kickstart2-preinstallconfig.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-kickstart2-packageselection">13.5.Â Package Selection</h2></div></div></div><a id="id848533" class="indexterm"></a><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).
		</div><div class="para">
			Packages can be specified by group or by individual package name, including with globs using the asterisk. The installation program defines several groups that contain related packages. Refer to the <code class="filename"><em class="replaceable"><code>variant</code></em>/repodata/comps-*.xml</code> file on the first Fedora CD-ROM for a list of groups. Each group has an id, user visibility value, name, description, and package list. In the package list, the packages marked as mandatory are always installed if the group is selected, the packages marked default are selected by default if the group is selected, and the packages marked optional must be specifically selected even if the group is selected to be installed.
		</div><div class="para">
			In most cases, it is only necessary to list the desired groups and not individual packages. Note that the <code class="command">Core</code> and <code class="command">Base</code> groups are always selected by default, so it is not necessary to specify them in the <code class="command">%packages</code> section.
		</div><div class="para">
			Here is an example <code class="command">%packages</code> selection:
		</div><pre class="screen">%packages 
@ X Window System 
@ GNOME Desktop Environment 
@ Graphical Internet 
@ Sound and Video dhcp
</pre><div class="para">
			As you can see, groups are specified, one to a line, starting with an <code class="command">@</code> symbol, a space, and then the full group name as given in the <code class="filename">comps.xml</code> file. Groups can also be specified using the id for the group, such as <code class="computeroutput">gnome-desktop</code>. Specify individual packages with no additional characters (the <code class="filename">dhcp</code> line in the example above is an individual package).
		</div><div class="para">
			You can also specify which packages not to install from the default package list:
		</div><pre class="screen">-autofs
</pre><div class="para">
			The following options are available for the <code class="command">%packages</code> option:
		</div><div class="variablelist"><dl><dt><span class="term"><code class="command">--nobase</code></span></dt><dd><div class="para">
						Do not install the @Base group. Use this option if you are trying to create a very small system.
					</div></dd><dt><span class="term"><code class="command">--resolvedeps</code></span></dt><dd><div class="para">
						The --resolvedeps option has been deprecated. Dependencies are resolved automatically every time now.
					</div></dd><dt><span class="term"><code class="command">--ignoredeps</code></span></dt><dd><div class="para">
						The --ignoredeps option has been deprecated. Dependencies are resolved automatically every time now.
					</div></dd><dt><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kickstart2-options.html"><strong>Prev</strong>13.4.Â Kickstart Options</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-kickstart2-preinstallconfig.html"><strong>Next</strong>13.6.Â Pre-installation Script</a></li></ul></body></html>


--- NEW FILE s1-kickstart2-postinstallconfig.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.7.Â Post-installation Script</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-kickstart2.html" title="ChapterÂ 13.Â Kickstart Installations" /><link rel="prev" href="s1-kickstart2-preinstallconfig.html" title="13.6.Â Pre-installation Script" /><link rel="next" href="s1-kickstart2-putkickstarthere.html" title="13.8.Â Making the Kickstart File Available" /></head><body class="draft "><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_r
 ight.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kickstart2-preinstallconfig.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-kickstart2-putkickstarthere.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-kickstart2-postinstallconfig">13.7.Â Post-installation Script</h2></div></div></div><a id="id845980" class="indexterm"></a><a id="id845994" 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 at the end of the kickstart file and must start with the <code class="command">%post</code> command. This section is useful for functions such as installing additional software and configuring an additional nameserver.
		</div><div class="note"><h2>Note</h2><div class="para">
				If you configured the network with static IP information, including a nameserver, you can access the network and resolve IP addresses in the <code class="command">%post</code> section. If you configured the network for DHCP, the <code class="filename">/etc/resolv.conf</code> file has not been completed when the installation executes the <code class="command">%post</code> section. You can access the network, but you can not resolve IP addresses. Thus, if you are using DHCP, you must specify IP addresses in the <code class="command">%post</code> section.
			</div></div><div class="note"><h2>Note</h2><div class="para">
				The post-install script is run in a chroot environment; therefore, performing tasks such as copying scripts or RPMs from the installation media do not work.
			</div></div><div class="variablelist"><dl><dt><span class="term"><code class="command">--nochroot</code></span></dt><dd><div class="para">
						Allows you to specify commands that you would like to run outside of the chroot environment.
					</div><div class="para">
						The following example copies the file <code class="filename">/etc/resolv.conf</code> to the file system that was just installed.
					</div><pre class="screen">%post --nochroot cp /etc/resolv.conf /mnt/sysimage/etc/resolv.conf
</pre></dd><dt><span class="term"><code class="command">--interpreter <em class="replaceable"><code>/usr/bin/python</code></em></code></span></dt><dd><div class="para">
						Allows you to specify a different scripting language, such as Python. Replace <em class="replaceable"><code>/usr/bin/python</code></em> with the scripting language of your choice.
					</div></dd></dl></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-kickstart2-post-examples">13.7.1.Â Examples</h3></div></div></div><div class="para">
				Register the system to a Red Hat Network Satellite:
			</div><pre class="screen">%post
( # Note that in this example we run the entire %post section as a subshell for logging.
wget -O- http://proxy-or-sat.example.com/pub/bootstrap_script | /bin/bash
/usr/sbin/rhnreg_ks --activationkey=<em class="replaceable"><code><activationkey></code></em>
# End the subshell and capture any output to a post-install log file.
) 1>/root/post_install.log 2>&1
</pre><div class="para">
				Run a script named <code class="filename">runme</code> from an NFS share:
			</div><pre class="screen">mkdir /mnt/temp 
mount -o nolock 10.10.0.2:/usr/new-machines /mnt/temp open -s -w -- 
/mnt/temp/runme 
umount /mnt/temp
</pre><div class="note"><h2>Note</h2><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></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kickstart2-preinstallconfig.html"><strong>Prev</strong>13.6.Â Pre-installation Script</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-kickstart2-putkickstarthere.html"><strong>Next</strong>13.8.Â Making the Kickstart File Available</a></li></ul></body></html>


--- NEW FILE s1-kickstart2-preinstallconfig.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.6.Â Pre-installation Script</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-kickstart2.html" title="ChapterÂ 13.Â Kickstart Installations" /><link rel="prev" href="s1-kickstart2-packageselection.html" title="13.5.Â Package Selection" /><link rel="next" href="s1-kickstart2-postinstallconfig.html" title="13.7.Â Post-installation Script" /></head><body class="draft "><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="Do
 cumentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kickstart2-packageselection.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-kickstart2-postinstallconfig.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-kickstart2-preinstallconfig">13.6.Â Pre-installation Script</h2></div></div></div><a id="id941508" class="indexterm"></a><a id="id941522" 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 at the end of the kickstart file (after the commands) and must start with the <code class="command">%pre</code> command. 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.
		</div><div class="note"><h2>Note</h2><div class="para">
				Note that the pre-install script is not run in the change root environment.
			</div></div><div class="variablelist"><dl><dt><span class="term"><code class="command">--interpreter <em class="replaceable"><code>/usr/bin/python</code></em></code></span></dt><dd><div class="para">
						Allows you to specify a different scripting language, such as Python. Replace <em class="replaceable"><code>/usr/bin/python</code></em> with the scripting language of your choice.
					</div></dd></dl></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-kickstart2-prescript-example">13.6.1.Â Example</h3></div></div></div><div class="para">
				Here is an example <code class="command">%pre</code> section:
			</div><pre class="screen">%pre  
#!/bin/sh  
hds="" 
mymedia=""  
for file in /proc/ide/h* do   
	mymedia=`cat $file/media`   
	if [ $mymedia == "disk" ] ; then       
		hds="$hds `basename $file`"   
	fi 
done  
set $hds 
numhd=`echo $#`  
drive1=`echo $hds | cut -d' ' -f1` 
drive2=`echo $hds | cut -d' ' -f2`  
#Write out partition scheme based on whether there are 1 or 2 hard drives  
if [ $numhd == "2" ] ; then   
	#2 drives   
	echo "#partitioning scheme generated in %pre for 2 drives" > /tmp/part-include   
	echo "clearpart --all" >> /tmp/part-include   
	echo "part /boot --fstype ext3 --size 75 --ondisk hda" >> /tmp/part-include   
	echo "part / --fstype ext3 --size 1 --grow --ondisk hda" >> /tmp/part-include   
	echo "part swap --recommended --ondisk $drive1" >> /tmp/part-include   
	echo "part /home --fstype ext3 --size 1 --grow --ondisk hdb" >> /tmp/part-include 
else   
	#1 drive   
	echo "#partitioning scheme generated in %pre for 1 drive" > /tmp/part-include   
	echo "clearpart --all" >> /tmp/part-include   
	echo "part /boot --fstype ext3 --size 75" >> /tmp/part-includ   
	echo "part swap --recommended" >> /tmp/part-include   
	echo "part / --fstype ext3 --size 2048" >> /tmp/part-include   
	echo "part /home --fstype ext3 --size 2048 --grow" >> /tmp/part-include 
fi
</pre><div class="para">
				This script determines the number of hard drives in the system and writes a text file with a different partitioning scheme depending on whether it has one or two drives. Instead of having a set of partitioning commands in the kickstart file, include the line:
			</div><pre class="screen">%include /tmp/part-include
</pre><div class="para">
				The partitioning commands selected in the script are used.
			</div><div class="note"><h2>Note</h2><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kickstart2-packageselection.html"><strong>Prev</strong>13.5.Â Package Selection</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-kickstart2-postinstallconfig.html"><strong>Next</strong>13.7.Â Post-installation Script</a></li></ul></body></html>


--- NEW FILE s1-kickstart2-putkickstarthere.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.8.Â Making the Kickstart File Available</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-kickstart2.html" title="ChapterÂ 13.Â Kickstart Installations" /><link rel="prev" href="s1-kickstart2-postinstallconfig.html" title="13.7.Â Post-installation Script" /><link rel="next" href="s2-kickstart2-networkbased.html" title="13.8.2.Â Making the Kickstart File Available on the Network" /></head><body class="draft "><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="Com
 mon_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kickstart2-postinstallconfig.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-kickstart2-networkbased.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-kickstart2-putkickstarthere">13.8.Â Making the Kickstart File Available</h2></div></div></div><a id="id823242" class="indexterm"></a><div class="para">
			A kickstart file must be placed in one of the following locations:
		</div><div class="itemizedlist"><ul><li><div class="para">
					On a boot diskette
				</div></li><li><div class="para">
					On a boot CD-ROM
				</div></li><li><div class="para">
					On a network
				</div></li></ul></div><div class="para">
			Normally a kickstart file is copied to the boot diskette, 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" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-kickstart2-boot-media">13.8.1.Â Creating Kickstart Boot Media</h3></div></div></div><a id="id895963" class="indexterm"></a><a id="id895976" 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>.
			</div><a id="id896001" class="indexterm"></a><a id="id849541" class="indexterm"></a><div class="para">
				To perform a CD-ROM-based kickstart installation, the kickstart file must be named <code class="filename">ks.cfg</code> and must be located in the boot CD-ROM's top-level directory. Since a CD-ROM is read-only, the file must be added to the directory used to create the image that is written to the CD-ROM. Refer to <a class="xref" href="s2-steps-make-cd.html" title="3.4.2.Â Making an Installation Boot CD-ROM">SectionÂ 3.4.2, â€œMaking an Installation Boot CD-ROMâ€</a> for instructions on creating boot media; however, before making the <code class="filename">file.iso</code> image file, copy the <code class="filename">ks.cfg</code> kickstart file to the <code class="filename">isolinux/</code> directory.
			</div><a id="id849588" class="indexterm"></a><a id="id849602" 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">
				For example, the following transfers a boot image to the pen drive (<code class="filename">/dev/sda</code>) using the <code class="command">dd</code> command:
			</div><pre class="screen">dd if=diskboot.img of=/dev/sda bs=1M
</pre><div class="note"><h2>Note</h2><div class="para">
					Creation of USB flash memory pen drives 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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kickstart2-postinstallconfig.html"><strong>Prev</strong>13.7.Â Post-installation Script</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-kickstart2-networkbased.html"><strong>Next</strong>13.8.2.Â Making the Kickstart File Available on th...</a></li></ul></body></html>


--- NEW FILE s1-kickstart2-startinginstall.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.10.Â Starting a Kickstart Installation</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-kickstart2.html" title="ChapterÂ 13.Â Kickstart Installations" /><link rel="prev" href="s1-kickstart2-install-tree.html" title="13.9.Â Making the Installation Tree Available" /><link rel="next" href="ch-redhat-config-kickstart.html" title="ChapterÂ 14.Â Kickstart Configurator" /></head><body class="draft "><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/ima
 ges/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kickstart2-install-tree.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-redhat-config-kickstart.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-kickstart2-startinginstall">13.10.Â Starting a Kickstart Installation</h2></div></div></div><a id="id814202" class="indexterm"></a><a id="id814216" class="indexterm"></a><div class="para">
			To begin a kickstart installation, you must boot the system from boot media you have made or the Fedora CD-ROM #1, 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><span class="term">CD-ROM #1 and Diskette</span></dt><dd><div class="para">
						<a id="id839326" class="indexterm"></a>
						 The <strong class="userinput"><code>linux ks=floppy</code></strong> command also works if the <code class="filename">ks.cfg</code> file is located on a vfat or ext2 file system on a diskette and you boot from the Fedora CD-ROM #1.
					</div><div class="para">
						An alternate boot command is to boot off the Fedora CD-ROM #1 and have the kickstart file on a vfat or ext2 file system on a diskette. To do so, enter the following command at the <code class="prompt">boot:</code> prompt:
					</div><pre class="screen">linux ks=hd:fd0:/ks.cfg
</pre></dd></dl></div><div class="variablelist"><dl><dt><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, to boot off a boot diskette and use a driver disk, enter the following command at the <code class="prompt">boot:</code> prompt:
					</div><pre class="screen">linux ks=floppy dd
</pre></dd><dt><span class="term">Boot CD-ROM</span></dt><dd><div class="para">
						<a id="id839140" class="indexterm"></a>
						 If the kickstart file is on a boot CD-ROM as described in <a class="xref" href="s1-kickstart2-putkickstarthere.html#s2-kickstart2-boot-media" title="13.8.1.Â Creating Kickstart Boot Media">SectionÂ 13.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:
		</div><div class="variablelist"><dl><dt><span class="term"><code class="command">askmethod</code></span></dt><dd><div class="para">
						Do not automatically use the CD-ROM as the install source if we detect a Fedora CD in your CD-ROM drive.
					</div></dd><dt><span class="term"><code class="command">autostep</code></span></dt><dd><div class="para">
						Make kickstart non-interactive.
					</div></dd><dt><span class="term"><code class="command">debug</code></span></dt><dd><div class="para">
						Start up pdb immediately.
					</div></dd><dt><span class="term"><code class="command">dd</code></span></dt><dd><div class="para">
						Use a driver disk.
					</div></dd><dt><span class="term"><code class="command">dhcpclass=<em class="replaceable"><code><class></code></em></code></span></dt><dd><div class="para">
						Sends a custom DHCP vendor class identifier. ISC's dhcpcd can inspect this value using "option vendor-class-identifier".
					</div></dd><dt><span class="term"><code class="command">dns=<em class="replaceable"><code><dns></code></em></code></span></dt><dd><div class="para">
						Comma separated list of nameservers to use for a network installation.
					</div></dd><dt><span class="term"><code class="command">driverdisk</code></span></dt><dd><div class="para">
						Same as 'dd'.
					</div></dd><dt><span class="term"><code class="command">expert</code></span></dt><dd><div class="para">
						Turns on special features: 
						<div class="itemizedlist"><ul><li><div class="para">
									allows partitioning of removable media
								</div></li><li><div class="para">
									prompts for a driver disk
								</div></li></ul></div>
					</div></dd><dt><span class="term"><code class="command">gateway=<em class="replaceable"><code><gw></code></em></code></span></dt><dd><div class="para">
						Gateway to use for a network installation.
					</div></dd><dt><span class="term"><code class="command">graphical</code></span></dt><dd><div class="para">
						Force graphical install. Required to have ftp/http use GUI.
					</div></dd><dt><span class="term"><code class="command">isa</code></span></dt><dd><div class="para">
						Prompt user for ISA devices configuration.
					</div></dd><dt><span class="term"><code class="command">ip=<em class="replaceable"><code><ip></code></em></code></span></dt><dd><div class="para">
						IP to use for a network installation, use 'dhcp' for DHCP.
					</div></dd><dt><span class="term"><code class="command">keymap=<em class="replaceable"><code><keymap></code></em></code></span></dt><dd><div class="para">
						Keyboard layout to use. Valid values are those which can be used for the 'keyboard' kickstart command.
					</div></dd><dt><span class="term"><code class="command">ks=nfs:<em class="replaceable"><code><server></code></em>:/<em class="replaceable"><code><path></code></em></code></span></dt><dd><div class="para">
						The installation program looks for the kickstart file on the NFS server <em class="replaceable"><code><server></code></em>, as file <em class="replaceable"><code><path></code></em>. The installation program uses DHCP to configure the Ethernet card. For example, if your NFS server is server.example.com and the kickstart file is in the NFS share <code class="filename">/mydir/ks.cfg</code>, the correct boot command would be <code class="command">ks=nfs:server.example.com:/mydir/ks.cfg</code>.
					</div></dd><dt><span class="term"><code class="command">ks=http://<em class="replaceable"><code><server></code></em>/<em class="replaceable"><code><path></code></em></code></span></dt><dd><div class="para">
						The installation program looks for the kickstart file on the HTTP server <em class="replaceable"><code><server></code></em>, as file <em class="replaceable"><code><path></code></em>. The installation program uses DHCP to configure the Ethernet card. For example, if your HTTP server is server.example.com and the kickstart file is in the HTTP directory <code class="filename">/mydir/ks.cfg</code>, the correct boot command would be <code class="command">ks=http://server.example.com/mydir/ks.cfg</code>.
					</div></dd><dt><span class="term"><code class="command">ks=floppy</code></span></dt><dd><div class="para">
						The installation program looks for the file <code class="filename">ks.cfg</code> on a vfat or ext2 file system on the diskette in <code class="filename">/dev/fd0</code>.
					</div></dd><dt><span class="term"><code class="command">ks=floppy:/<em class="replaceable"><code><path></code></em></code></span></dt><dd><div class="para">
						The installation program looks for the kickstart file on the diskette in <code class="filename">/dev/fd0</code>, as file <em class="replaceable"><code><path></code></em>.
					</div></dd><dt><span class="term"><code class="command">ks=hd:<em class="replaceable"><code><device></code></em>:/<em class="replaceable"><code><file></code></em></code></span></dt><dd><div class="para">
						The installation program mounts the file system on <em class="replaceable"><code><device></code></em> (which must be vfat or ext2), and look for the kickstart configuration file as <em class="replaceable"><code><file></code></em> in that file system (for example, <code class="command">ks=hd:sda3:/mydir/ks.cfg</code>).
					</div></dd><dt><span class="term"><code class="command">ks=file:/<em class="replaceable"><code><file></code></em></code></span></dt><dd><div class="para">
						The installation program tries to read the file <em class="replaceable"><code><file></code></em> from the file system; no mounts are done. This is normally used if the kickstart file is already on the <code class="filename">initrd</code> image.
					</div></dd><dt><span class="term"><code class="command">ks=cdrom:/<em class="replaceable"><code><path></code></em></code></span></dt><dd><div class="para">
						The installation program looks for the kickstart file on CD-ROM, as file <em class="replaceable"><code><path></code></em>.
					</div></dd><dt><span class="term"><code class="command">ks</code></span></dt><dd><div class="para">
						If <code class="command">ks</code> is used alone, the installation program configures the Ethernet card to use DHCP. The kickstart file is read from the "bootServer" from the DHCP response as if it is an NFS server sharing the kickstart file. By default, the bootServer is the same as the DHCP server. The name of the kickstart file is one of the following:
					</div><div class="itemizedlist"><ul><li><div class="para">
								If DHCP is specified and the boot file begins with a <code class="filename">/</code>, the boot file provided by DHCP is looked for on the NFS server.
							</div></li><li><div class="para">
								If DHCP is specified and the boot file begins with something other than a <code class="computeroutput">/</code>, the boot file provided by DHCP is looked for in the <code class="filename">/kickstart</code> directory on the NFS server.
							</div></li><li><div class="para">
								If DHCP did not specify a boot file, then the installation program tries to read the file <code class="filename">/kickstart/1.2.3.4-kickstart</code>, where <em class="replaceable"><code>1.2.3.4</code></em> is the numeric IP address of the machine being installed.
							</div></li></ul></div></dd><dt><span class="term"><code class="command">ksdevice=<em class="replaceable"><code><device></code></em></code></span></dt><dd><div class="para">
						The installation program uses this network device to connect to the network. For example, consider a system connected to an NFS server through the eth1 device. To perform a kickstart installation on this system using a kickstart file from the NFS server, you would use the command <code class="command">ks=nfs:<em class="replaceable"><code><server></code></em>:/<em class="replaceable"><code><path></code></em> ksdevice=eth1</code> at the <code class="prompt">boot:</code> prompt.
					</div></dd><dt><span class="term"><code class="command">kssendmac</code></span></dt><dd><div class="para">
						Adds HTTP headers to ks=http:// request that can be helpful for provisioning systems. Includes MAC address of all nics in CGI environment variables of the form: "X-RHN-Provisioning-MAC-0: eth0 01:23:45:67:89:ab".
					</div></dd><dt><span class="term"><code class="command">lang=<em class="replaceable"><code><lang></code></em></code></span></dt><dd><div class="para">
						Language to use for the installation. This should be a language which is valid to be used with the 'lang' kickstart command.
					</div></dd><dt><span class="term"><code class="command">loglevel=<em class="replaceable"><code><level></code></em></code></span></dt><dd><div class="para">
						Set the minimum level required for messages to be logged. Values for <level> are debug, info, warning, error, and critical. The default value is info.
					</div></dd><dt><span class="term"><code class="command">lowres</code></span></dt><dd><div class="para">
						Force GUI installer to run at 640x480.
					</div></dd><dt><span class="term"><code class="command">mediacheck</code></span></dt><dd><div class="para">
						Activates loader code to give user option of testing integrity of install source (if an ISO-based method).
					</div></dd><dt><span class="term"><code class="command">method=cdrom</code></span></dt><dd><div class="para">
						Do a CDROM based installation.
					</div></dd><dt><span class="term"><code class="command">method=ftp://<em class="replaceable"><code><path></code></em></code></span></dt><dd><div class="para">
						Use <path> for an FTP installation.
					</div></dd><dt><span class="term"><code class="command">method=hd:<em class="replaceable"><code><dev></code></em>:<em class="replaceable"><code><path></code></em></code></span></dt><dd><div class="para">
						Use <path> on <dev> for a hard drive installation.
					</div></dd><dt><span class="term"><code class="command">method=http://<em class="replaceable"><code><path></code></em></code></span></dt><dd><div class="para">
						Use <path> for an HTTP installation.
					</div></dd><dt><span class="term"><code class="command">method=nfs:<em class="replaceable"><code><path></code></em></code></span></dt><dd><div class="para">
						Use <path> for an NFS installation.
					</div></dd><dt><span class="term"><code class="command">netmask=<em class="replaceable"><code><nm></code></em></code></span></dt><dd><div class="para">
						Netmask to use for a network installation.
					</div></dd><dt><span class="term"><code class="command">nofallback</code></span></dt><dd><div class="para">
						If GUI fails exit.
					</div></dd><dt><span class="term"><code class="command">nofb</code></span></dt><dd><div class="para">
						Do not load the VGA16 framebuffer required for doing text-mode installation in some languages.
					</div></dd><dt><span class="term"><code class="command">nofirewire</code></span></dt><dd><div class="para">
						Do not load support for firewire devices.
					</div></dd><dt><span class="term"><code class="command">noipv6</code></span></dt><dd><div class="para">
						Disable IPv6 networking during installation.
					</div></dd><dt><span class="term"><code class="command">nokill</code></span></dt><dd><div class="para">
						A debugging option that prevents anaconda from terminating all running programs when a fatal error occurs.
					</div></dd><dt><span class="term"><code class="command">nomount</code></span></dt><dd><div class="para">
						Don't automatically mount any installed Linux partitions in rescue mode.
					</div></dd><dt><span class="term"><code class="command">nonet</code></span></dt><dd><div class="para">
						Do not auto-probe network devices.
					</div></dd><dt><span class="term"><code class="command">noparport</code></span></dt><dd><div class="para">
						Do not attempt to load support for parallel ports.
					</div></dd><dt><span class="term"><code class="command">nopass</code></span></dt><dd><div class="para">
						Don't pass keyboard/mouse info to stage 2 installer, good for testing keyboard and mouse config screens in stage2 installer during network installs.
					</div></dd><dt><span class="term"><code class="command">nopcmcia</code></span></dt><dd><div class="para">
						Ignore PCMCIA controller in system.
					</div></dd><dt><span class="term"><code class="command">noprobe</code></span></dt><dd><div class="para">
						Do not attempt to detect hw, prompts user instead.
					</div></dd><dt><span class="term"><code class="command">noshell</code></span></dt><dd><div class="para">
						Do not put a shell on tty2 during install.
					</div></dd><dt><span class="term"><code class="command">nostorage</code></span></dt><dd><div class="para">
						Do not auto-probe storage devices (SCSI, IDE, RAID).
					</div></dd><dt><span class="term"><code class="command">nousb</code></span></dt><dd><div class="para">
						Do not load USB support (helps if install hangs early sometimes).
					</div></dd><dt><span class="term"><code class="command">nousbstorage</code></span></dt><dd><div class="para">
						Do not load usbstorage module in loader. May help with device ordering on SCSI systems.
					</div></dd><dt><span class="term"><code class="command">rescue</code></span></dt><dd><div class="para">
						Run rescue environment.
					</div></dd><dt><span class="term"><code class="command">resolution=<em class="replaceable"><code><mode></code></em></code></span></dt><dd><div class="para">
						Run installer in mode specified, '1024x768' for example.
					</div></dd><dt><span class="term"><code class="command">serial</code></span></dt><dd><div class="para">
						Turns on serial console support.
					</div></dd><dt><span class="term"><code class="command">skipddc</code></span></dt><dd><div class="para">
						Skips DDC probe of monitor, may help if it's hanging system.
					</div></dd><dt><span class="term"><code class="command">syslog=<em class="replaceable"><code><host></code></em>[:<em class="replaceable"><code><port></code></em>]</code></span></dt><dd><div class="para">
						Once installation is up and running, send log messages to the syslog process on <em class="replaceable"><code><host></code></em>, and optionally, on port <em class="replaceable"><code><port></code></em>. Requires the remote syslog process to accept connections (the -r option).
					</div></dd><dt><span class="term"><code class="command">text</code></span></dt><dd><div class="para">
						Force text mode install.
					</div><div class="important"><h2>Important</h2><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></dd><dt><span class="term"><code class="command">updates</code></span></dt><dd><div class="para">
						Prompt for floppy containing updates (bug fixes).
					</div></dd><dt><span class="term"><code class="command">updates=ftp://<em class="replaceable"><code><path></code></em></code></span></dt><dd><div class="para">
						Image containing updates over FTP.
					</div></dd><dt><span class="term"><code class="command">updates=http://<em class="replaceable"><code><path></code></em></code></span></dt><dd><div class="para">
						Image containing updates over HTTP.
					</div></dd><dt><span class="term"><code class="command">upgradeany</code></span></dt><dd><div class="para">
						Don't require an /etc/redhat-release that matches the expected syntax to upgrade.
					</div></dd><dt><span class="term"><code class="command">vnc</code></span></dt><dd><div class="para">
						Enable vnc-based installation. You will need to connect to the machine using a vnc client application.
					</div></dd><dt><span class="term"><code class="command">vncconnect=<em class="replaceable"><code><host></code></em>[:<em class="replaceable"><code><port></code></em>]</code></span></dt><dd><div class="para">
						Once installation is up and running, connect to the vnc client named <em class="replaceable"><code><host></code></em>, and optionally use port <em class="replaceable"><code><port></code></em>.
					</div><div class="para">
						Requires 'vnc' option to be specified as well.
					</div></dd><dt><span class="term"><code class="command">vncpassword=<em class="replaceable"><code><password></code></em></code></span></dt><dd><div class="para">
						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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kickstart2-install-tree.html"><strong>Prev</strong>13.9.Â Making the Installation Tree Available</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-redhat-config-kickstart.html"><strong>Next</strong>ChapterÂ 14.Â Kickstart Configurator</a></li></ul></body></html>


--- NEW FILE s1-langselection-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.11.Â Language Selection</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="sn-welcome-x86.html" title="7.10.Â Welcome to Fedora" /><link rel="next" href="ch07s12.html" title="7.12.Â Keyboard Configuration" /></head><body class="draft "><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><ul cla
 ss="docnav"><li class="previous"><a accesskey="p" href="sn-welcome-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch07s12.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-langselection-x86">7.11.Â Language Selection</h2></div></div></div><a id="id939907" class="indexterm"></a><div class="para">
		Using your mouse, select a language to use for the installation (refer to <a class="xref" href="s1-langselection-x86.html#fig-langselection-x86" title="FigureÂ 7.7.Â Language Selection">FigureÂ 7.7, â€œLanguage Selectionâ€</a>).
	</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.
</div><div class="para">
	To add support for additional languages, customize the installation at the package selection stage. For more information, refer to <a class="xref" href="sn-lang-packages.html" title="7.23.2.2.Â Additional Language Support">SectionÂ 7.23.2.2, â€œAdditional Language Supportâ€</a>.
</div><div class="figure" id="fig-langselection-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/langselection/lang.png" alt="Language Selection" /><div class="longdesc"><div class="para">
					Language selection screen.
				</div></div></div></div><h6>FigureÂ 7.7.Â 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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-welcome-x86.html"><strong>Prev</strong>7.10.Â Welcome to Fedora</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch07s12.html"><strong>Next</strong>7.12.Â Keyboard Configuration</a></li></ul></body></html>


--- NEW FILE s1-netboot-add-hosts.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.5.3.Â Adding PXE Hosts</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="sn-pxe-server-manual.html" title="11.5.Â Manually configure a PXE server" /><link rel="prev" href="s1-netboot-pxe-config.html" title="11.5.2.Â PXE Boot Configuration" /><link rel="next" href="s1-netboot-tftp.html" title="11.5.4.Â TFTPD" /></head><body class="draft "><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><ul 
 class="docnav"><li class="previous"><a accesskey="p" href="s1-netboot-pxe-config.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-netboot-tftp.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s1-netboot-add-hosts">11.5.3.Â Adding PXE Hosts</h3></div></div></div><a id="id911278" class="indexterm"></a><div class="para">
			After configuring the network server, the interface as shown in <a class="xref" href="s1-netboot-add-hosts.html#fig-netboot-add-hosts" title="FigureÂ 11.1.Â Add Hosts">FigureÂ 11.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" alt="Add Hosts" /><div class="longdesc"><div class="para">
						Add Hosts
					</div></div></div></div><h6>FigureÂ 11.1.Â Add Hosts</h6></div><br class="figure-break" /><div class="para">
			The next step is to configure which hosts are allowed to connect to the PXE boot server. 
		</div><div class="para">
			To add hosts, click the <span class="guibutton"><strong>New</strong></span> button.
		</div><div class="figure" id="fig-netboot-add-host-dialog"><div class="figure-contents"><div class="mediaobject"><img src="images/pxe/netboot-add-host-dialog.png" alt="Add a Host" /><div class="longdesc"><div class="para">
						Add a Host
					</div></div></div></div><h6>FigureÂ 11.2.Â Add a Host</h6></div><br class="figure-break" /><div class="para">
			Enter the following information:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<span class="guilabel"><strong>Hostname or IP Address/Subnet</strong></span> â€” The IP address, fully qualified hostname, or a subnet of systems that should be allowed to connect to the PXE server for installations.
				</div></li><li><div class="para">
					<span class="guilabel"><strong>Operating System</strong></span> â€” The operating system identifier to install on this client. The list is populated from the network install instances created from the <span class="guilabel"><strong>Network Installation Dialog</strong></span>.
				</div></li><li><div class="para">
					<span class="guilabel"><strong>Serial Console</strong></span> â€” This option allows use of a serial console.
				</div></li><li><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.html" title="ChapterÂ 14.Â Kickstart Configurator">ChapterÂ 14, <i>Kickstart Configurator</i></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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-netboot-pxe-config.html"><strong>Prev</strong>11.5.2.Â PXE Boot Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-netboot-tftp.html"><strong>Next</strong>11.5.4.Â TFTPD</a></li></ul></body></html>


--- NEW FILE s1-netboot-pxe-config.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.5.2.Â PXE Boot Configuration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="sn-pxe-server-manual.html" title="11.5.Â Manually configure a PXE server" /><link rel="prev" href="sn-pxe-server-manual.html" title="11.5.Â Manually configure a PXE server" /><link rel="next" href="s1-netboot-add-hosts.html" title="11.5.3.Â Adding PXE Hosts" /></head><body class="draft "><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="Docume
 ntation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-pxe-server-manual.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-netboot-add-hosts.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s1-netboot-pxe-config">11.5.2.Â PXE Boot Configuration</h3></div></div></div><a id="id836366" 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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-pxe-server-manual.html"><strong>Prev</strong>11.5.Â Manually configure a PXE server</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-netboot-add-hosts.html"><strong>Next</strong>11.5.3.Â Adding PXE Hosts</a></li></ul></body></html>


--- NEW FILE s1-netboot-tftp.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.5.4.Â TFTPD</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="sn-pxe-server-manual.html" title="11.5.Â Manually configure a PXE server" /><link rel="prev" href="s1-netboot-add-hosts.html" title="11.5.3.Â Adding PXE Hosts" /><link rel="next" href="ch11s05s05.html" title="11.5.5.Â Configuring the DHCP Server" /></head><body class="draft "><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><ul c
 lass="docnav"><li class="previous"><a accesskey="p" href="s1-netboot-add-hosts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch11s05s05.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s1-netboot-tftp">11.5.4.Â TFTPD</h3></div></div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="id896172">11.5.4.1.Â Starting the <code class="command">tftp</code> Server</h4></div></div></div><a id="id885487" 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 /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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-netboot-add-hosts.html"><strong>Prev</strong>11.5.3.Â Adding PXE Hosts</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch11s05s05.html"><strong>Next</strong>11.5.5.Â Configuring the DHCP Server</a></li></ul></body></html>


--- NEW FILE s1-pkgselection-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.23.Â Package Group Selection</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="s2-x86-bootloader-alt.html" title="7.22.3.Â Alternative Boot Loaders" /><link rel="next" href="sn-package-selection.html" title="7.23.2.Â Customizing the Software Selection" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-x86-bootloader-alt.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-package-selection.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-pkgselection-x86">7.23.Â Package Group Selection</h2></div></div></div><a id="id827937" class="indexterm"></a><a id="id913993" class="indexterm"></a><a id="id906811" class="indexterm"></a><a id="id884785" class="indexterm"></a><a id="id847379" class="indexterm"></a><a id="id891628" 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.
</div><div class="important"><h2>Installing from a Live Image</h2><div class="para">
		If you install from a Fedora Live image, you cannot make package selections. This installation method transfers a copy of the Live image rather than installing packages from a repository. To change the package selection, complete the installation, then use the <span class="application"><strong>Add/Remove Software</strong></span> application to make desired changes.
	</div></div><div class="important"><h2>Installing in text mode</h2><div class="para">
		If you install Fedora in text mode, you cannot make package selections. The installer automatically selects packages only from the base and core groups. These packages are sufficient to ensure that the system is operational at the end of the installation process, ready to install updates and new packages. To change the package selection, complete the installation, then use the <span class="application"><strong>Add/Remove Software</strong></span> application to make desired changes.
	</div></div><div class="figure" id="fig-pkgselection-group-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/pkgselection/pkg-group.png" alt="Package Group Selection" /><div class="longdesc"><div class="para">
	Choose which package groups you want to install.
</div></div></div></div><h6>FigureÂ 7.27.Â Package Group Selection</h6></div><br class="figure-break" /><div class="para">
	By default, the Fedora installation process loads a selection of software that is suitable for a desktop system. To include or remove software for common tasks, select the relevant items from the list:
</div><div class="variablelist"><dl><dt><span class="term">Office and Productivity</span></dt><dd><div class="para">
				This option provides the OpenOffice.org productivity suite, the Planner project management application, graphical tools such as the GIMP, and multimedia applications.
			</div></dd><dt><span class="term">Software Development</span></dt><dd><div class="para">
				This option provides the necessary tools to compile software on your Fedora system.
			</div></dd><dt><span class="term">Web server</span></dt><dd><div class="para">
				This option provides the Apache Web server.
			</div></dd></dl></div><div class="para">
		If you choose to accept the current package list, skip ahead to <a class="xref" href="s1-preparetoinstall-x86.html" title="7.24.Â Preparing to Install">SectionÂ 7.24, â€œPreparing to Installâ€</a>.
	</div><div class="para">
		To select a component, click on the checkbox beside it (refer to <a class="xref" href="s1-pkgselection-x86.html#fig-pkgselection-group-x86" title="FigureÂ 7.27.Â Package Group Selection">FigureÂ 7.27, â€œ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 class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-additional-repos">7.23.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:
	</div><div class="itemizedlist"><ul><li><div class="para">
				The <span class="guilabel"><strong>Installation Repo</strong></span> repository is automatically selected for you. This represents the collection of software available on your installation CD or DVD.
			</div></li><li><div class="para">
				The <span class="guilabel"><strong>Fedora 11 - i386</strong></span> repository contains the complete collection of software that was released as Fedora 11, with the various pieces of software in their versions that were current at the time of release. If you are installing from the Fedora 11 DVD or <span class="emphasis"><em>set</em></span> of CDs, this option does not offer you anything extra. However, if you are installing from a Fedora Live CD, this option provides access to far more software than is included on the disk. Note that the computer must have access to the internet to use this option.
			</div></li><li><div class="para">
				The <span class="guilabel"><strong>Fedora 11 - i386 - Updates</strong></span> repository contains the complete collection of software that was released as Fedora 11, with the various pieces of software in their most current stable versions. This option not only installs the software that you select, but makes sure that it is fully updated as well. Note that the computer must have access to the internet to use this option.
			</div></li></ul></div><div class="figure" id="fig-pkgselection-repos-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/pkgselection/pkg-group-repos.png" alt="Adding a software repository" /><div class="longdesc"><div class="para">
	Enter the details of additional software repositories.
</div></div></div></div><h6>FigureÂ 7.28.Â Adding a software repository</h6></div><br class="figure-break" /><div class="para">
		To include software from <em class="firstterm">repositories</em> other than the Fedora package collection, select <span class="guilabel"><strong>Add additional software repositories</strong></span>. You may provide the location of a repository of third-party software. Depending on the configuration of that repository, you may be able to select non-Fedora software during installation.
	</div><div class="para">
		To edit an existing software repository location, select the repository in the list and then select <span class="guilabel"><strong>Modify repository</strong></span>.
	</div><div class="note"><h2>Network Access Required</h2><div class="para">
			If you change the repository information during a non-network installation, such as from a Fedora DVD, the installer prompts you for network configuration information.
		</div></div><div class="para">
		If you select <span class="guilabel"><strong>Add additional software repositories</strong></span>, the <span class="guilabel"><strong>Edit repository</strong></span> dialog appears. Provide a <span class="guilabel"><strong>Repository name</strong></span> and the <span class="guilabel"><strong>Repository URL</strong></span> for its location.
	</div><div class="note"><h2>Fedora Software Mirrors</h2><div class="para">
			To find a Fedora software mirror near you, refer to <a href="http://fedoraproject.org/wiki/Mirrors">http://fedoraproject.org/wiki/Mirrors</a>.
		</div></div><div class="para">
		Once you have located a mirror, to determine the URL to use, find the directory on the mirror that <span class="emphasis"><em>contains</em></span> a directory named <code class="filename">repodata</code>. For instance, the "Everything" repository for Fedora is typically located in a directory tree <code class="filename">releases/11/Everything/<em class="replaceable"><code>arch</code></em>/os</code>, where <em class="replaceable"><code>arch</code></em> is a system architecture name.
	</div><div class="para">
		Once you provide information for an additional repository, the installer reads the package metadata over the network. Software that is specially marked is then included in the package group selection system. See <a class="xref" href="sn-package-selection.html" title="7.23.2.Â Customizing the Software Selection">SectionÂ 7.23.2, â€œCustomizing the Software Selectionâ€</a> for more information on selecting packages.
	</div><div class="note"><h2>Backtracking Removes Repository Metadata</h2><div class="para">
			If you choose <span class="guilabel"><strong>Back</strong></span> from the package selection screen, any extra repository data you may have entered is lost. This allows you to effectively cancel extra repositories. Currently there is no way to cancel only a single repository once entered.
		</div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-x86-bootloader-alt.html"><strong>Prev</strong>7.22.3.Â Alternative Boot Loaders</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-package-selection.html"><strong>Next</strong>7.23.2.Â Customizing the Software Selection</a></li></ul></body></html>


--- NEW FILE s1-preparetoinstall-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.24.Â Preparing to Install</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="sn-mandatory-services.html" title="7.23.2.3.Â Core Network Services" /><link rel="next" href="s1-installpkgs-x86.html" title="7.25.Â Installing Packages" /></head><body class="draft "><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="Documentatio
 n Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-mandatory-services.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-installpkgs-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-preparetoinstall-x86">7.24.Â Preparing to Install</h2></div></div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id838976">7.24.1.Â  Prepare to Install </h3></div></div></div><div class="para">
		A screen preparing you for the installation of Fedora now appears.
	</div><div class="para">
		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><a id="id913888" class="indexterm"></a><a id="id904724" class="indexterm"></a><div class="para">
		To cancel this installation process, press your computer's Reset button or use the <span class="keycap"><strong>Control</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Delete</strong></span> key combination to restart your machine.
	</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-mandatory-services.html"><strong>Prev</strong>7.23.2.3.Â Core Network Services</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-installpkgs-x86.html"><strong>Next</strong>7.25.Â Installing Packages</a></li></ul></body></html>


--- NEW FILE s1-redhat-config-kickstart-auth.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.6.Â Authentication</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-redhat-config-kickstart.html" title="ChapterÂ 14.Â Kickstart Configurator" /><link rel="prev" href="s1-redhat-config-kickstart-network.html" title="14.5.Â Network Configuration" /><link rel="next" href="s1-redhat-config-kickstart-firewall.html" title="14.7.Â Firewall Configuration" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-redhat-config-kickstart-network.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-redhat-config-kickstart-firewall.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-redhat-config-kickstart-auth">14.6.Â Authentication</h2></div></div></div><a id="id797584" 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" alt="Authentication" /><div class="longdesc"><div class="para">
						Authentication for Kickstart
					</div></div></div></div><h6>FigureÂ 14.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.
		</div><div class="para">
			The <span class="guilabel"><strong>Authentication Configuration</strong></span> options allow you to configure the following methods of authentication:
		</div><div class="itemizedlist"><ul><li><div class="para">
					NIS
				</div></li><li><div class="para">
					LDAP
				</div></li><li><div class="para">
					Kerberos 5
				</div></li><li><div class="para">
					Hesiod
				</div></li><li><div class="para">
					SMB
				</div></li><li><div class="para">
					Name Switch Cache
				</div></li></ul></div><div class="para">
			These methods are not enabled by default. To enable one or more of these methods, click the appropriate tab, click the checkbox next to <span class="guilabel"><strong>Enable</strong></span>, and enter the appropriate information for the authentication method. Refer to the Red Hat Enterprise Linux Deployment Guide for more information about the options.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-redhat-config-kickstart-network.html"><strong>Prev</strong>14.5.Â Network Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-redhat-config-kickstart-firewall.html"><strong>Next</strong>14.7.Â Firewall Configuration</a></li></ul></body></html>


--- NEW FILE s1-redhat-config-kickstart-bootloader.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.3.Â Boot Loader Options</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-redhat-config-kickstart.html" title="ChapterÂ 14.Â Kickstart Configurator" /><link rel="prev" href="s1-redhat-config-kickstart-install.html" title="14.2.Â Installation Method" /><link rel="next" href="s1-redhat-config-kickstart-partitions.html" title="14.4.Â Partition Information" /></head><body class="draft "><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_r
 ight.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-redhat-config-kickstart-install.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-redhat-config-kickstart-partitions.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-redhat-config-kickstart-bootloader">14.3.Â Boot Loader Options</h2></div></div></div><div class="figure" id="redhat-config-kickstart-bootloader-fig"><div class="figure-contents"><a id="id828290" class="indexterm"></a><div class="mediaobject"><img src="images/ksconfig/ksconfig-bootloader.png" alt="Boot Loader Options" /><div class="longdesc"><div class="para">
						Boot Loader Options
					</div></div></div></div><h6>FigureÂ 14.3.Â Boot Loader Options</h6></div><br class="figure-break" /><a id="id814588" 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.
		</div><div class="para">
			You must choose where to install the boot loader (the Master Boot Record or the first sector of the <code class="filename">/boot</code> partition). Install the boot loader on the MBR if you plan to use it as your boot loader.
		</div><div class="para">
			To pass any special parameters to the kernel to be used when the system boots, enter them in the <span class="guilabel"><strong>Kernel parameters</strong></span> text field. For example, if you have an IDE CD-ROM Writer, you can tell the kernel to use the SCSI emulation driver that must be loaded before using <code class="command">cdrecord</code> by configuring <strong class="userinput"><code>hdd=ide-scsi</code></strong> as a kernel parameter (where <strong class="userinput"><code>hdd</code></strong> is the CD-ROM device).
		</div><div class="para">
			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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-redhat-config-kickstart-install.html"><strong>Prev</strong>14.2.Â Installation Method</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-redhat-config-kickstart-partitions.html"><strong>Next</strong>14.4.Â Partition Information</a></li></ul></body></html>


--- NEW FILE s1-redhat-config-kickstart-firewall.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.7.Â Firewall Configuration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-redhat-config-kickstart.html" title="ChapterÂ 14.Â Kickstart Configurator" /><link rel="prev" href="s1-redhat-config-kickstart-auth.html" title="14.6.Â Authentication" /><link rel="next" href="s1-redhat-config-kickstart-xconfig.html" title="14.8.Â Display Configuration" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-redhat-config-kickstart-auth.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-redhat-config-kickstart-xconfig.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-redhat-config-kickstart-firewall">14.7.Â Firewall Configuration</h2></div></div></div><a id="id824408" 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" alt="Firewall Configuration" /><div class="longdesc"><div class="para">
						Firewall Configuration for Kickstart
					</div></div></div></div><h6>FigureÂ 14.10.Â Firewall Configuration</h6></div><br class="figure-break" /><div class="para">
			If <span class="guilabel"><strong>Disable firewall</strong></span> is selected, the system allows complete access to any active services and ports. No connections to the system are refused or denied.
		</div><div class="para">
			Selecting <span class="guilabel"><strong>Enable firewall</strong></span> configures the system to 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 required, you can choose to allow specific services through the firewall.
		</div><div class="para">
			Only devices configured in the <span class="guilabel"><strong>Network Configuration</strong></span> section are listed as available <span class="guilabel"><strong>Trusted devices</strong></span>. Connections from any devices selected in the list are accepted by the system. For example, if <span class="guilabel"><strong>eth1</strong></span> only receives connections from internal system, you might want to allow connections from it.
		</div><div class="para">
			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" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-redhat-config-kickstart-firewall-selinux">14.7.1.Â SELinux Configuration</h3></div></div></div><a id="id806186" 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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-redhat-config-kickstart-auth.html"><strong>Prev</strong>14.6.Â Authentication</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-redhat-config-kickstart-xconfig.html"><strong>Next</strong>14.8.Â Display Configuration</a></li></ul></body></html>


--- NEW FILE s1-redhat-config-kickstart-install.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.2.Â Installation Method</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-redhat-config-kickstart.html" title="ChapterÂ 14.Â Kickstart Configurator" /><link rel="prev" href="ch-redhat-config-kickstart.html" title="ChapterÂ 14.Â Kickstart Configurator" /><link rel="next" href="s1-redhat-config-kickstart-bootloader.html" title="14.3.Â Boot Loader Options" /></head><body class="draft "><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_r
 ight.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-redhat-config-kickstart.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-redhat-config-kickstart-bootloader.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-redhat-config-kickstart-install">14.2.Â Installation Method</h2></div></div></div><a id="id810937" 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" alt="Installation Method" /><div class="longdesc"><div class="para">
						Kickstart Installation Method
					</div></div></div></div><h6>FigureÂ 14.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.
		</div><div class="para">
			Choose the type of kickstart installation or upgrade from the following options:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<span class="guilabel"><strong>CD-ROM</strong></span> â€” Choose this option to install or upgrade from the Fedora CD-ROMs.
				</div></li><li><div class="para">
					<span class="guilabel"><strong>NFS</strong></span> â€” Choose this option to install or upgrade from an NFS shared directory. In the text field for the the NFS server, enter a fully-qualified domain name or IP address. For the NFS directory, enter the name of the NFS directory that contains the <code class="filename"><em class="replaceable"><code>variant</code></em></code> directory of the installation tree. For example, if the NFS server contains the directory <code class="filename">/mirrors/redhat/i386/Server/</code>, enter <code class="filename">/mirrors/redhat/i386/</code> for the NFS directory.
				</div></li><li><div class="para">
					<span class="guilabel"><strong>FTP</strong></span> â€” Choose this option to install or upgrade from an FTP server. In the FTP server text field, enter a fully-qualified domain name or IP address. For the FTP directory, enter the name of the FTP directory that contains the <code class="filename"><em class="replaceable"><code>variant</code></em></code> directory. For example, if the FTP server contains the directory <code class="filename">/mirrors/redhat/i386/Server/</code>, enter <code class="filename">/mirrors/redhat/i386/Server/</code> for the FTP directory. If the FTP server requires a username and password, specify them as well.
				</div></li><li><div class="para">
					<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><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 (or CD-ROM) 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-verifying-media.html" title="6.3.Â Verifying Media">SectionÂ 6.3, â€œVerifying 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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-redhat-config-kickstart.html"><strong>Prev</strong>ChapterÂ 14.Â Kickstart Configurator</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-redhat-config-kickstart-bootloader.html"><strong>Next</strong>14.3.Â Boot Loader Options</a></li></ul></body></html>


--- NEW FILE s1-redhat-config-kickstart-network.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.5.Â Network Configuration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-redhat-config-kickstart.html" title="ChapterÂ 14.Â Kickstart Configurator" /><link rel="prev" href="s1-redhat-config-kickstart-partitions.html" title="14.4.Â Partition Information" /><link rel="next" href="s1-redhat-config-kickstart-auth.html" title="14.6.Â Authentication" /></head><body class="draft "><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.p
 ng" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-redhat-config-kickstart-partitions.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-redhat-config-kickstart-auth.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-redhat-config-kickstart-network">14.5.Â Network Configuration</h2></div></div></div><a id="id786641" 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" alt="Network Configuration" /><div class="longdesc"><div class="para">
						Network Configuration for Kickstart
					</div></div></div></div><h6>FigureÂ 14.8.Â Network Configuration</h6></div><br class="figure-break" /><div class="para">
			If the system to be installed via kickstart does not have an Ethernet card, do not configure one on the <span class="guilabel"><strong>Network Configuration</strong></span> page.
		</div><div class="para">
			Networking is only required if you choose a networking-based installation method (NFS, FTP, or HTTP). Networking can always be configured after installation with the <span class="application"><strong>Network Administration Tool</strong></span> (<code class="command">system-config-network</code>). Refer to the Red Hat Enterprise Linux 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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-redhat-config-kickstart-partitions.html"><strong>Prev</strong>14.4.Â Partition Information</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-redhat-config-kickstart-auth.html"><strong>Next</strong>14.6.Â Authentication</a></li></ul></body></html>


--- NEW FILE s1-redhat-config-kickstart-partitions.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.4.Â Partition Information</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-redhat-config-kickstart.html" title="ChapterÂ 14.Â Kickstart Configurator" /><link rel="prev" href="s1-redhat-config-kickstart-bootloader.html" title="14.3.Â Boot Loader Options" /><link rel="next" href="s1-redhat-config-kickstart-network.html" title="14.5.Â Network Configuration" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-redhat-config-kickstart-bootloader.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-redhat-config-kickstart-network.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-redhat-config-kickstart-partitions">14.4.Â Partition Information</h2></div></div></div><a id="id738328" 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" alt="Partition Information" /><div class="longdesc"><div class="para">
						Kickstart Partition Information
					</div></div></div></div><h6>FigureÂ 14.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.
		</div><div class="para">
			To initialize the disk label to the default for the architecture of the system (for example, <code class="command">msdos</code> for x86 and <code class="command">gpt</code> for Itanium), select <span class="guilabel"><strong>Initialize the disk label</strong></span> if you are installing on a brand new hard drive.
		</div><div class="note"><h2>Note</h2><div class="para">
				Although <code class="command">anaconda</code> and <code class="command">kickstart</code> support Logical Volume Management (LVM), at present there is no mechanism for configuring this using the <span class="application"><strong>Kickstart Configurator</strong></span>.
			</div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-redhat-config-kickstart-create-part">14.4.1.Â Creating Partitions</h3></div></div></div><div class="para">
				To create a partition, click the <span class="guibutton"><strong>Add</strong></span> button. The <span class="guilabel"><strong>Partition Options</strong></span> window shown in <a class="xref" href="s1-redhat-config-kickstart-partitions.html#redhat-config-kickstart-add-part-fig" title="FigureÂ 14.5.Â Creating Partitions">FigureÂ 14.5, â€œCreating Partitionsâ€</a> appears. Choose the mount point, file system type, and partition size for the new partition. Optionally, you can also choose from the following:
			</div><div class="itemizedlist"><ul><li><div class="para">
						In the <span class="guilabel"><strong>Additional Size Options</strong></span> section, choose to make the partition a fixed size, up to a chosen size, or fill the remaining space on the hard drive. If you selected swap as the file system type, you can select to have the installation program create the swap partition with the recommended size instead of specifying a size.
					</div></li><li><div class="para">
						Force the partition to be created as a primary partition.
					</div></li><li><div class="para">
						Create the partition on a specific hard drive. For example, to make the partition on the first IDE hard disk (<code class="filename">/dev/hda</code>), specify <strong class="userinput"><code>hda</code></strong> as the drive. Do not include <code class="filename">/dev</code> in the drive name.
					</div></li><li><div class="para">
						Use an existing partition. For example, to make the partition on the first partition on the first IDE hard disk (<code class="filename">/dev/hda1</code>), specify <strong class="userinput"><code>hda1</code></strong> as the partition. Do not include <code class="filename">/dev</code> in the partition name.
					</div></li><li><div class="para">
						Format the partition as the chosen file system type.
					</div></li></ul></div><div class="figure" id="redhat-config-kickstart-add-part-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/ksconfig/ksconfig-part-options.png" alt="Creating Partitions" /><div class="longdesc"><div class="para">
							Creating Partitions for Kickstart
						</div></div></div></div><h6>FigureÂ 14.5.Â Creating Partitions</h6></div><br class="figure-break" /><div class="para">
				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="s1-redhat-config-kickstart-partitions.html#redhat-config-kickstart-add-part-fig" title="FigureÂ 14.5.Â Creating Partitions">FigureÂ 14.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" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="s3-redhat-config-kickstart-raid">14.4.1.1.Â Creating Software RAID Partitions</h4></div></div></div><a id="id811579" class="indexterm"></a><a id="id811599" class="indexterm"></a><div class="para">
					To create a software RAID partition, use the following steps:
				</div><div class="orderedlist"><ol><li><div class="para">
							Click the <span class="guibutton"><strong>RAID</strong></span> button.
						</div></li><li><div class="para">
							Select <span class="guilabel"><strong>Create a software RAID partition</strong></span>.
						</div></li><li><div class="para">
							Configure the partitions as previously described, except select <span class="guilabel"><strong>Software RAID</strong></span> as the file system type. Also, you must specify a hard drive on which to make the partition or specify an existing partition to use.
						</div></li></ol></div><div class="figure" id="fig-kickstart-raid"><div class="figure-contents"><div class="mediaobject"><img src="images/ksconfig/ksconfig-raid-new.png" alt="Creating a Software RAID Partition" /><div class="longdesc"><div class="para">
								Software RAID Partition
							</div></div></div></div><h6>FigureÂ 14.6.Â Creating a Software RAID Partition</h6></div><br class="figure-break" /><div class="para">
					Repeat these steps to create as many partitions as needed for your RAID setup. All of your partitions do not have to be RAID partitions.
				</div><div class="para">
					After creating all the partitions needed to form a RAID device, follow these steps:
				</div><div class="orderedlist"><ol><li><div class="para">
							Click the <span class="guibutton"><strong>RAID</strong></span> button.
						</div></li><li><div class="para">
							Select <span class="guilabel"><strong>Create a RAID device</strong></span>.
						</div></li><li><div class="para">
							Select a mount point, file system type, RAID device name, RAID level, RAID members, number of spares for the software RAID device, and whether to format the RAID device.
						</div><div class="figure" id="fig-redhat-config-kickstart-md0"><div class="figure-contents"><div class="mediaobject"><img src="images/ksconfig/ksconfig-raid-device.png" alt="Creating a Software RAID Device" /><div class="longdesc"><div class="para">
										Software RAID Device
									</div></div></div></div><h6>FigureÂ 14.7.Â Creating a Software RAID Device</h6></div><br class="figure-break" /></li><li><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-redhat-config-kickstart-bootloader.html"><strong>Prev</strong>14.3.Â Boot Loader Options</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-redhat-config-kickstart-network.html"><strong>Next</strong>14.5.Â Network Configuration</a></li></ul></body></html>


--- NEW FILE s1-redhat-config-kickstart-pkgs.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.9.Â Package Selection</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-redhat-config-kickstart.html" title="ChapterÂ 14.Â Kickstart Configurator" /><link rel="prev" href="s1-redhat-config-kickstart-xconfig.html" title="14.8.Â Display Configuration" /><link rel="next" href="s1-redhat-config-kickstart-prescript.html" title="14.10.Â Pre-Installation Script" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-redhat-config-kickstart-xconfig.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-redhat-config-kickstart-prescript.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-redhat-config-kickstart-pkgs">14.9.Â Package Selection</h2></div></div></div><a id="id808760" 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" alt="Package Selection" /><div class="longdesc"><div class="para">
						Package Selection for Kickstart
					</div></div></div></div><h6>FigureÂ 14.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.
		</div><div class="para">
			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.html" title="13.5.Â Package Selection">SectionÂ 13.5, â€œPackage Selectionâ€</a> for details.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-redhat-config-kickstart-xconfig.html"><strong>Prev</strong>14.8.Â Display Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-redhat-config-kickstart-prescript.html"><strong>Next</strong>14.10.Â Pre-Installation Script</a></li></ul></body></html>


--- NEW FILE s1-redhat-config-kickstart-postinstall.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.11.Â Post-Installation Script</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-redhat-config-kickstart.html" title="ChapterÂ 14.Â Kickstart Configurator" /><link rel="prev" href="s1-redhat-config-kickstart-prescript.html" title="14.10.Â Pre-Installation Script" /><link rel="next" href="s2-redhat-config-kickstart-interpreter.html" title="14.11.2.Â Use an Interpreter" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-redhat-config-kickstart-prescript.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-redhat-config-kickstart-interpreter.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-redhat-config-kickstart-postinstall">14.11.Â Post-Installation Script</h2></div></div></div><a id="id872466" 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" alt="Post-Installation Script" /><div class="longdesc"><div class="para">
						Post-Installation Script for Kickstart
					</div></div></div></div><h6>FigureÂ 14.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.
		</div><div class="warning"><h2>Warning</h2><div class="para">
				Do not include the <code class="command">%post</code> command. It is added for you.
			</div></div><div class="para">
			For example, to change the message of the day for the newly installed system, add the following command to the <code class="command">%post</code> section:
		</div><pre class="screen">
<code class="command">echo "Hackers will be punished!" > /etc/motd</code>
</pre><div class="note"><h2>Note</h2><div class="para">
				More examples can be found in <a class="xref" href="s1-kickstart2-postinstallconfig.html#s2-kickstart2-post-examples" title="13.7.1.Â Examples">SectionÂ 13.7.1, â€œExamplesâ€</a>.
			</div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-redhat-config-kickstart-nochroot">14.11.1.Â Chroot Environment</h3></div></div></div><div class="para">
				To run the post-installation script outside of the chroot environment, click the checkbox next to this option on the top of the <span class="guilabel"><strong>Post-Installation</strong></span> window. This is equivalent to using the <code class="command">--nochroot</code> option in the <code class="command">%post</code> section.
			</div><div class="para">
				To make changes to the newly installed file system, within the post-installation section, but outside of the chroot environment, you must prepend the directory name with <code class="filename">/mnt/sysimage/</code>.
			</div><div class="para">
				For example, if you select <span class="guilabel"><strong>Run outside of the chroot environment</strong></span>, the previous example must be changed to the following:
			</div><pre class="screen">
<code class="command">echo "Hackers will be punished!" > /mnt/sysimage/etc/motd</code>
</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-redhat-config-kickstart-prescript.html"><strong>Prev</strong>14.10.Â Pre-Installation Script</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-redhat-config-kickstart-interpreter.html"><strong>Next</strong>14.11.2.Â Use an Interpreter</a></li></ul></body></html>


--- NEW FILE s1-redhat-config-kickstart-prescript.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.10.Â Pre-Installation Script</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-redhat-config-kickstart.html" title="ChapterÂ 14.Â Kickstart Configurator" /><link rel="prev" href="s1-redhat-config-kickstart-pkgs.html" title="14.9.Â Package Selection" /><link rel="next" href="s1-redhat-config-kickstart-postinstall.html" title="14.11.Â Post-Installation Script" /></head><body class="draft "><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/im
 age_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-redhat-config-kickstart-pkgs.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-redhat-config-kickstart-postinstall.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-redhat-config-kickstart-prescript">14.10.Â Pre-Installation Script</h2></div></div></div><a id="id805666" 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" alt="Pre-Installation Script" /><div class="longdesc"><div class="para">
						Pre-Installation Script for Kickstart
					</div></div></div></div><h6>FigureÂ 14.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.
		</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.4</code></strong> can be specified for a Python script. This option corresponds to using <code class="command">%pre --interpreter <em class="replaceable"><code>/usr/bin/python2.4</code></em></code> in your kickstart file.
		</div><div class="para">
			Many of the commands that are available in the pre-installation environment are provided by a version of <span class="application"><strong>busybox</strong></span> called <span class="application"><strong>busybox-anaconda</strong></span>. <span class="application"><strong>Busybox</strong></span>-supplied commands do not provide all features, but supply only the most commonly used features. The following list of available commands include commands provided by <span class="application"><strong>busybox</strong></span>:
		</div><div class="para">
			<code class="command">addgroup</code>, <code class="command">adduser</code>, <code class="command">adjtimex</code>, <code class="command">ar</code>, <code class="command">arping</code>, <code class="command">ash</code>, <code class="command">awk</code>, <code class="command">basename</code>, <code class="command">bbconfig</code>, <code class="command">bunzip2</code>, <code class="command">busybox</code>, <code class="command">bzcat</code>, <code class="command">cal</code>, <code class="command">cat</code>, <code class="command">catv</code>, <code class="command">chattr</code>, <code class="command">chgrp</code>, <code class="command">chmod</code>, <code class="command">chown</code>, <code class="command">chroot</code>, <code class="command">chvt</code>, <code class="command">cksum</code>, <code class="command">clear</code>, <code class="command">cmp</code>, <code class="command">comm</code>, <code class="command">cp</code>, <code class="command">cpio</code>, <code class="c
 ommand">crond</code>, <code class="command">crontab</code>, <code class="command">cut</code>, <code class="command">date</code>, <code class="command">dc</code>, <code class="command">dd</code>, <code class="command">deallocvt</code>, <code class="command">delgroup</code>, <code class="command">deluser</code>, <code class="command">devfsd</code>, <code class="command">df</code>, <code class="command">diff</code>, <code class="command">dirname</code>, <code class="command">dmesg</code>, <code class="command">dnsd</code>, <code class="command">dos2unix</code>, <code class="command">dpkg</code>, <code class="command">dpkg-deb</code>, <code class="command">du</code>, <code class="command">dumpkmap</code>, <code class="command">dumpleases</code>, <code class="command">e2fsck</code>, <code class="command">e2label</code>, <code class="command">echo</code>, <code class="command">ed</code>, <code class="command">egrep</code>, <code class="command">eject</code>, <code class="command">
 env</code>, <code class="command">ether-wake</code>, <code class="command">expr</code>, <code class="command">fakeidentd</code>, <code class="command">false</code>, <code class="command">fbset</code>, <code class="command">fdflush</code>, <code class="command">fdformat</code>, <code class="command">fdisk</code>, <code class="command">fgrep</code>, <code class="command">find</code>, <code class="command">findfs</code>, <code class="command">fold</code>, <code class="command">free</code>, <code class="command">freeramdisk</code>, <code class="command">fsck</code>, <code class="command">fsck.ext2</code>, <code class="command">fsck.ext3</code>, <code class="command">fsck.ext4</code>, <code class="command">fsck.minix</code>, <code class="command">ftpget</code>, <code class="command">ftpput</code>, <code class="command">fuser</code>, <code class="command">getopt</code>, <code class="command">getty</code>, <code class="command">grep</code>, <code class="command">gunzip</code>, <cod
 e class="command">gzip</code>, <code class="command">hdparm</code>, <code class="command">head</code>, <code class="command">hexdump</code>, <code class="command">hostid</code>, <code class="command">hostname</code>, <code class="command">httpd</code>, <code class="command">hush</code>, <code class="command">hwclock</code>, <code class="command">id</code>, <code class="command">ifconfig</code>, <code class="command">ifdown</code>, <code class="command">ifup</code>, <code class="command">inetd</code>, <code class="command">insmod</code>, <code class="command">install</code>, <code class="command">ip</code>, <code class="command">ipaddr</code>, <code class="command">ipcalc</code>, <code class="command">ipcrm</code>, <code class="command">ipcs</code>, <code class="command">iplink</code>, <code class="command">iproute</code>, <code class="command">iptunnel</code>, <code class="command">kill</code>, <code class="command">killall</code>, <code class="command">lash</code>, <code cl
 ass="command">last</code>, <code class="command">length</code>, <code class="command">less</code>, <code class="command">linux32</code>, <code class="command">linux64</code>, <code class="command">ln</code>, <code class="command">load_policy</code>, <code class="command">loadfont</code>, <code class="command">loadkmap</code>, <code class="command">login</code>, <code class="command">logname</code>, <code class="command">losetup</code>, <code class="command">ls</code>, <code class="command">lsattr</code>, <code class="command">lsmod</code>, <code class="command">lzmacat</code>, <code class="command">makedevs</code>, <code class="command">md5sum</code>, <code class="command">mdev</code>, <code class="command">mesg</code>, <code class="command">mkdir</code>, <code class="command">mke2fs</code>, <code class="command">mkfifo</code>, <code class="command">mkfs.ext2</code>, <code class="command">mkfs.ext3</code>, <code class="command">mkfs.ext4</code>, <code class="command">mkfs.mi
 nix</code>, <code class="command">mknod</code>, <code class="command">mkswap</code>, <code class="command">mktemp</code>, <code class="command">modprobe</code>, <code class="command">more</code>, <code class="command">mount</code>, <code class="command">mountpoint</code>, <code class="command">msh</code>, <code class="command">mt</code>, <code class="command">mv</code>, <code class="command">nameif</code>, <code class="command">nc</code>, <code class="command">netstat</code>, <code class="command">nice</code>, <code class="command">nohup</code>, <code class="command">nslookup</code>, <code class="command">od</code>, <code class="command">openvt</code>, <code class="command">passwd</code>, <code class="command">patch</code>, <code class="command">pidof</code>, <code class="command">ping</code>, <code class="command">ping6</code>, <code class="command">pipe_progress</code>, <code class="command">pivot_root</code>, <code class="command">printenv</code>, <code class="command">pr
 intf</code>, <code class="command">ps</code>, <code class="command">pwd</code>, <code class="command">rdate</code>, <code class="command">readlink</code>, <code class="command">readprofile</code>, <code class="command">realpath</code>, <code class="command">renice</code>, <code class="command">reset</code>, <code class="command">rm</code>, <code class="command">rmdir</code>, <code class="command">rmmod</code>, <code class="command">route</code>, <code class="command">rpm</code>, <code class="command">rpm2cpio</code>, <code class="command">run-parts</code>, <code class="command">runlevel</code>, <code class="command">rx</code>, <code class="command">sed</code>, <code class="command">seq</code>, <code class="command">setarch</code>, <code class="command">setconsole</code>, <code class="command">setkeycodes</code>, <code class="command">setlogcons</code>, <code class="command">setsid</code>, <code class="command">sh</code>, <code class="command">sha1sum</code>, <code class="com
 mand">sleep</code>, <code class="command">sort</code>, <code class="command">start-stop-daemon</code>, <code class="command">stat</code>, <code class="command">strings</code>, <code class="command">stty</code>, <code class="command">su</code>, <code class="command">sulogin</code>, <code class="command">sum</code>, <code class="command">swapoff</code>, <code class="command">swapon</code>, <code class="command">switch_root</code>, <code class="command">sync</code>, <code class="command">sysctl</code>, <code class="command">tail</code>, <code class="command">tar</code>, <code class="command">tee</code>, <code class="command">telnet</code>, <code class="command">telnetd</code>, <code class="command">test</code>, <code class="command">tftp</code>, <code class="command">time</code>, <code class="command">top</code>, <code class="command">touch</code>, <code class="command">tr</code>, <code class="command">traceroute</code>, <code class="command">true</code>, <code class="command">
 tty</code>, <code class="command">tune2fs</code>, <code class="command">udhcpc</code>, <code class="command">udhcpd</code>, <code class="command">umount</code>, <code class="command">uname</code>, <code class="command">uncompress</code>, <code class="command">uniq</code>, <code class="command">unix2dos</code>, <code class="command">unlzma</code>, <code class="command">unzip</code>, <code class="command">uptime</code>, <code class="command">usleep</code>, <code class="command">uudecode</code>, <code class="command">uuencode</code>, <code class="command">vconfig</code>, <code class="command">vi</code>, <code class="command">vlock</code>, <code class="command">watch</code>, <code class="command">watchdog</code>, <code class="command">wc</code>, <code class="command">wget</code>, <code class="command">which</code>, <code class="command">who</code>, <code class="command">whoami</code>, <code class="command">xargs</code>, <code class="command">yes</code>, <code class="command">zca
 t</code>, <code class="command">zcip</code>
		</div><div class="para">
			For a description of any of these commands, run:
		</div><div class="para">
			<code class="command">busybox <em class="replaceable"><code>command</code></em> --help</code>
		</div><div class="para">
			In addition to the aforementioned commands, the following commands are provided in their full featured versions:
		</div><div class="para">
			<code class="command">anaconda</code>, <code class="command">bash</code>, <code class="command">bzip2</code>, <code class="command">jmacs</code>, <code class="command">ftp</code>, <code class="command">head</code>, <code class="command">joe</code>, <code class="command">kudzu-probe</code>, <code class="command">list-harddrives</code>, <code class="command">loadkeys</code>, <code class="command">mtools</code>, <code class="command">mbchk</code>, <code class="command">mtools</code>, <code class="command">mini-wm</code>, <code class="command">mtools</code>, <code class="command">jpico</code>, <code class="command">pump</code>, <code class="command">python</code>, <code class="command">python2.4</code>, <code class="command">raidstart</code>, <code class="command">raidstop</code>, <code class="command">rcp</code>, <code class="command">rlogin</code>, <code class="command">rsync</code>, <code class="command">setxkbmap</code>, <code class="command">sftp</code>, <code class="comm
 and">shred</code>, <code class="command">ssh</code>, <code class="command">syslinux</code>, <code class="command">syslogd</code>, <code class="command">tac</code>, <code class="command">termidx</code>, <code class="command">vncconfig</code>, <code class="command">vncpasswd</code>, <code class="command">xkbcomp</code>, <code class="command">Xorg</code>, <code class="command">Xvnc</code>, <code class="command">zcat</code>
		</div><div class="warning"><h2>Warning</h2><div class="para">
				Do not include the <code class="command">%pre</code> command. It is added for you.
			</div></div><div class="note"><h2>Note</h2><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-redhat-config-kickstart-pkgs.html"><strong>Prev</strong>14.9.Â Package Selection</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-redhat-config-kickstart-postinstall.html"><strong>Next</strong>14.11.Â Post-Installation Script</a></li></ul></body></html>


--- NEW FILE s1-redhat-config-kickstart-savefile.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.12.Â Saving the File</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-redhat-config-kickstart.html" title="ChapterÂ 14.Â Kickstart Configurator" /><link rel="prev" href="s2-redhat-config-kickstart-interpreter.html" title="14.11.2.Â Use an Interpreter" /><link rel="next" href="pt-After_installation.html" title="PartÂ IV.Â After installation" /></head><body class="draft "><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" al
 t="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-redhat-config-kickstart-interpreter.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="pt-After_installation.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-redhat-config-kickstart-savefile">14.12.Â Saving the File</h2></div></div></div><a id="id871905" 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
					</div></div></div></div><h6>FigureÂ 14.15.Â Preview</h6></div><br class="figure-break" /><div class="para">
			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.html" title="13.10.Â Starting a Kickstart Installation">SectionÂ 13.10, â€œStarting a Kickstart Installationâ€</a> for information on how to start the kickstart installation.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-redhat-config-kickstart-interpreter.html"><strong>Prev</strong>14.11.2.Â Use an Interpreter</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="pt-After_installation.html"><strong>Next</strong>PartÂ IV.Â After installation</a></li></ul></body></html>


--- NEW FILE s1-redhat-config-kickstart-xconfig.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.8.Â Display Configuration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-redhat-config-kickstart.html" title="ChapterÂ 14.Â Kickstart Configurator" /><link rel="prev" href="s1-redhat-config-kickstart-firewall.html" title="14.7.Â Firewall Configuration" /><link rel="next" href="s1-redhat-config-kickstart-pkgs.html" title="14.9.Â Package Selection" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-redhat-config-kickstart-firewall.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-redhat-config-kickstart-pkgs.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-redhat-config-kickstart-xconfig">14.8.Â Display Configuration</h2></div></div></div><a id="id789500" 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="s1-redhat-config-kickstart-xconfig.html#xconfig-fig" title="FigureÂ 14.11.Â X Configuration">FigureÂ 14.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" alt="X Configuration" /><div class="longdesc"><div class="para">
						X Configuration for Kickstart
					</div></div></div></div><h6>FigureÂ 14.11.Â X Configuration</h6></div><br class="figure-break" /><div class="para">
			Also select whether to start the <span class="application"><strong>Setup Agent</strong></span> the first time the system is rebooted. It 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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-redhat-config-kickstart-firewall.html"><strong>Prev</strong>14.7.Â Firewall Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-redhat-config-kickstart-pkgs.html"><strong>Next</strong>14.9.Â Package Selection</a></li></ul></body></html>


--- NEW FILE s1-rescuemode-boot.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.2.Â Booting into Rescue Mode</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ap-rescuemode.html" title="ChapterÂ 17.Â Basic System Recovery" /><link rel="prev" href="ap-rescuemode.html" title="ChapterÂ 17.Â Basic System Recovery" /><link rel="next" href="s1-rescuemode-booting-single.html" title="17.3.Â Booting into Single-User Mode" /></head><body class="draft "><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="Documen
 tation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ap-rescuemode.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-rescuemode-booting-single.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-rescuemode-boot">17.2.Â Booting into Rescue Mode</h2></div></div></div><a id="id927352" 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="id863482" 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">4</a>]</sup>:
		</div><div class="itemizedlist"><ul><li><div class="para">
					By booting the system from an installation boot CD-ROM or DVD.
				</div></li><li><div class="para">
					By booting the system from other installation boot media, such as USB flash devices.
				</div></li><li><div class="para">
					By booting the system from the Fedora CD-ROM #1 or DVD.
				</div></li></ul></div><div class="para">
			Once you have booted using one of the described methods, add the keyword <strong class="userinput"><code>rescue</code></strong> as a kernel parameter. For example, for an x86 system, type the following command at the installation boot prompt:
		</div><pre class="screen">
<strong class="userinput"><code>linux rescue</code></strong>
</pre><div class="para">
			You are prompted to answer a few basic questions, including which language to use. It also prompts you to select where a valid rescue image is located. Select from <span class="guilabel"><strong>Local CD-ROM</strong></span>, <span class="guilabel"><strong>Hard Drive</strong></span>, <span class="guilabel"><strong>NFS image</strong></span>, <span class="guilabel"><strong>FTP</strong></span>, or <span class="guilabel"><strong>HTTP</strong></span>. The location selected must contain a valid installation tree, and the installation tree must be for the same version of Fedora as the Fedora disk from which you booted. If you used a boot CD-ROM or other media to start rescue mode, the installation tree must be from the same tree from which the media was created. For more information about how to setup an installation tree on a hard drive, NFS server, FTP server, or HTTP server, refer to the earlier section of this guide.
		</div><div class="para">
			If you select a rescue image that does not require a network connection, you are asked whether or not you want to establish a network connection. A network connection is useful if you need to backup files to a different computer or install some RPM packages from a shared network location, for example.
		</div><div class="para">
			The following message is displayed:
		</div><div class="para">
			<code class="computeroutput">The rescue environment will now attempt to find your Linux installation and mount it under the directory /mnt/sysimage. You can then make any changes required to your system. If you want to proceed with this step choose 'Continue'. You can also choose to mount your file systems read-only instead of read-write by choosing 'Read-only'. If for some reason this process fails you can choose 'Skip' and this step will be skipped and you will go directly to a command shell.</code>
		</div><div class="para">
			If you select <span class="guibutton"><strong>Continue</strong></span>, it attempts to mount your file system under the directory <code class="filename">/mnt/sysimage/</code>. If it fails to mount a partition, it notifies you. If you select <span class="guibutton"><strong>Read-Only</strong></span>, it attempts to mount your file system under the directory <code class="filename">/mnt/sysimage/</code>, but in read-only mode. If you select <span class="guibutton"><strong>Skip</strong></span>, your file system is not mounted. Choose <span class="guibutton"><strong>Skip</strong></span> if you think your file system is corrupted.
		</div><div class="para">
			Once you have your system in rescue mode, a prompt appears on VC (virtual console) 1 and VC 2 (use the <span class="keycap"><strong>Ctrl</strong></span>-<span class="keycap"><strong>Alt</strong></span>-<span class="keycap"><strong>F1</strong></span> key combination to access VC 1 and <span class="keycap"><strong>Ctrl</strong></span>-<span class="keycap"><strong>Alt</strong></span>-<span class="keycap"><strong>F2</strong></span> to access VC 2):
		</div><pre class="screen">
<code class="prompt">sh-3.00b#</code>
</pre><div class="para">
			If you selected <span class="guibutton"><strong>Continue</strong></span> to mount your partitions automatically and they were mounted successfully, you are in single-user mode.
		</div><div class="para">
			Even if your file system is mounted, the default root partition while in rescue mode is a temporary root partition, not the root partition of the file system used during normal user mode (runlevel 3 or 5). If you selected to mount your file system and it mounted successfully, you can change the root partition of the rescue mode environment to the root partition of your file system by executing the following command:
		</div><pre class="screen">
<code class="command">chroot /mnt/sysimage</code>
</pre><div class="para">
			This is useful if you need to run commands such as <code class="command">rpm</code> that require your root partition to be mounted as <code class="filename">/</code>. To exit the <code class="command">chroot</code> environment, type <code class="command">exit</code> to return to the prompt.
		</div><div class="para">
			If you selected <span class="guibutton"><strong>Skip</strong></span>, you can still try to mount a partition or LVM2 logical volume manually inside rescue mode by creating a directory such as <code class="filename"><em class="replaceable"><code>/foo</code></em></code>, and typing the following command:
		</div><pre class="screen">
<code class="command">mount -t ext4 <em class="replaceable"><code>/dev/mapper/VolGroup00-LogVol02 /foo</code></em></code>
</pre><div class="para">
			In the above command, <code class="filename"><em class="replaceable"><code>/foo</code></em></code> is a directory that you have created and <code class="command"><em class="replaceable"><code>/dev/mapper/VolGroup00-LogVol02</code></em></code> is the LVM2 logical volume you want to mount. If the partition is of type <code class="command">ext2</code> or <code class="command">ext3</code> replace <code class="command">ext4</code> with <code class="command">ext2</code> or <code class="command">ext3</code> respectively.
		</div><div class="para">
			If you do not know the names of all physical partitions, use the following command to list them:
		</div><pre class="screen">
<code class="command">fdisk -l</code>
</pre><div class="para">
			If you do not know the names of all LVM2 physical volumes, volume groups, or logical volumes, use the following commands to list them:
		</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="id834295" class="indexterm"></a><div class="para">
			From the prompt, you can run many useful commands, such as:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<code class="command">ssh</code>, <code class="command">scp</code>, and <code class="command">ping</code> if the network is started
				</div></li><li><div class="para">
					<code class="command">dump</code> and <code class="command">restore</code> for users with tape drives
				</div></li><li><div class="para">
					<code class="command">parted</code> and <code class="command">fdisk</code> for managing partitions
				</div></li><li><div class="para">
					<code class="command">rpm</code> for installing or upgrading software
				</div></li><li><div class="para">
					<code class="command">joe</code> for editing configuration files
				</div><div class="note"><h2>Note</h2><div class="para">
						If you try to start other popular editors such as <code class="command">emacs</code>, <code class="command">pico</code>, or <code class="command">vi</code>, the <code class="command">joe</code> editor is started.
					</div></div></li></ul></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-rescuemode-boot-reinstall-bootloader">17.2.1.Â Reinstalling the Boot Loader</h3></div></div></div><a id="id827982" class="indexterm"></a><a id="id884640" 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:
			</div><div class="itemizedlist"><ul><li><div class="para">
						Boot the system from an installation boot medium.
					</div></li><li><div class="para">
						Type <code class="command">linux rescue</code> at the installation boot prompt to enter the rescue environment.
					</div></li><li><div class="para">
						Type <code class="command">chroot /mnt/sysimage</code> to mount the root partition.
					</div></li><li><div class="para">
						Type <code class="command">/sbin/grub-install /dev/hda</code> to reinstall the GRUB boot loader, where <code class="command">/dev/hda</code> is the boot partition.
					</div></li><li><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><div class="para">
						Reboot the system.
					</div></li></ul></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.boot-media" href="#boot-media" class="para">4</a>] </sup>
				Refer to the earlier sections of this guide for more details.
			</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ap-rescuemode.html"><strong>Prev</strong>ChapterÂ 17.Â Basic System Recovery</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-rescuemode-booting-single.html"><strong>Next</strong>17.3.Â Booting into Single-User Mode</a></li></ul></body></html>


--- NEW FILE s1-rescuemode-booting-emergency.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.4.Â Booting into Emergency Mode</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ap-rescuemode.html" title="ChapterÂ 17.Â Basic System Recovery" /><link rel="prev" href="s1-rescuemode-booting-single.html" title="17.3.Â Booting into Single-User Mode" /><link rel="next" href="ch-upgrade-x86.html" title="ChapterÂ 18.Â Upgrading Your Current System" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-rescuemode-booting-single.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-upgrade-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-rescuemode-booting-emergency">17.4.Â Booting into Emergency Mode</h2></div></div></div><a id="id851521" class="indexterm"></a><a id="id851534" 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.html" title="17.3.Â Booting into Single-User Mode">SectionÂ 17.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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-rescuemode-booting-single.html"><strong>Prev</strong>17.3.Â Booting into Single-User Mode</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-upgrade-x86.html"><strong>Next</strong>ChapterÂ 18.Â Upgrading Your Current System</a></li></ul></body></html>


--- NEW FILE s1-rescuemode-booting-single.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.3.Â Booting into Single-User Mode</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ap-rescuemode.html" title="ChapterÂ 17.Â Basic System Recovery" /><link rel="prev" href="s1-rescuemode-boot.html" title="17.2.Â Booting into Rescue Mode" /><link rel="next" href="s1-rescuemode-booting-emergency.html" title="17.4.Â Booting into Emergency Mode" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-rescuemode-boot.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-rescuemode-booting-emergency.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-rescuemode-booting-single">17.3.Â Booting into Single-User Mode</h2></div></div></div><a id="id840431" class="indexterm"></a><a id="id840445" class="indexterm"></a><a id="id840454" 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.
		</div><div class="para">
			In single-user mode, your computer boots to runlevel 1. Your local file systems are mounted, but your network is not activated. You have a usable system maintenance shell. Unlike rescue mode, single-user mode automatically tries to mount your file system. <span class="emphasis"><em>Do not use single-user mode if your file system cannot be mounted successfully.</em></span> You cannot use single-user mode if the runlevel 1 configuration on your system is corrupted.
		</div><div class="para">
			On an x86 system using GRUB, use the following steps to boot into single-user mode:
		</div><div class="orderedlist"><ol><li><div class="para">
					At the GRUB splash screen at boot time, press any key to enter the GRUB interactive menu.
				</div></li><li><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><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-rescuemode-boot.html"><strong>Prev</strong>17.2.Â Booting into Rescue Mode</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-rescuemode-booting-emergency.html"><strong>Next</strong>17.4.Â Booting into Emergency Mode</a></li></ul></body></html>


--- NEW FILE s1-steps-network-installs-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.5.Â Preparing for a Network Installation</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-steps-x86.html" title="ChapterÂ 3.Â Steps to Get You Started" /><link rel="prev" href="s2-steps-make-cd.html" title="3.4.2.Â Making an Installation Boot CD-ROM" /><link rel="next" href="ch03s05s02.html" title="3.5.2.Â Preparing for an NFS install" /></head><body class="draft "><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="Doc
 umentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-steps-make-cd.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch03s05s02.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-steps-network-installs-x86">3.5.Â Preparing for a Network Installation</h2></div></div></div><a id="id848301" class="indexterm"></a><a id="id789459" class="indexterm"></a><a id="id869367" class="indexterm"></a><a id="id873094" class="indexterm"></a><a id="id852878" class="indexterm"></a><a id="id845664" class="indexterm"></a><a id="id874822" class="indexterm"></a><a id="id854952" class="indexterm"></a><div class="note"><h2>Note</h2><div class="para">
		Make sure an installation CD (or any other type of CD) is not in your system's CD/DVD drive if you are performing a network-based installation. Having a CD in the drive may cause unexpected errors.
	</div></div><div class="para">
	The Fedora installation media must be available for either a network installation (via NFS, FTP, or HTTP) or installation via local storage. Use the following steps if you are performing an NFS, FTP, or HTTP installation.
</div><div class="para">
	The NFS, FTP, or HTTP server to be used for installation over the network must be a separate machine which can provide the complete contents of the installation DVD-ROM or the installation CD-ROMs.
</div><div class="note"><h2>Note</h2><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 CDs). 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 class="note"><h2>Note</h2><div class="para">
		In the following examples, the directory on the installation staging server that will contain the installation files will be specified as <code class="filename"><em class="replaceable"><code>/location/of/disk/space</code></em></code>. The directory that will be made publicly available via FTP, NFS, or HTTP will be specified as <em class="replaceable"><code>/publicly/available/directory</code></em>. For example, <code class="filename"><em class="replaceable"><code>/location/of/disk/space</code></em></code> may be a directory you create called <code class="filename">/var/isos</code>. <code class="filename"><em class="replaceable"><code>/publicly/available/directory</code></em></code> might be <code class="filename">/var/www/html/f11</code>, for an HTTP install.
	</div></div><div class="para">
	To copy the files from the installation DVD or CD-ROMs to a Linux machine which acts as an installation staging server, perform the following steps:
</div><div class="itemizedlist"><ul><li><div class="para">
			Create an iso image from the installation disk(s) using the following command (for DVDs):
		</div><div class="para">
			<code class="command"> dd if=/dev/<em class="replaceable"><code>dvd</code></em> of=<em class="replaceable"><code>/location/of/disk/space/</code></em>f11.iso </code>
		</div><div class="para">
			where <em class="replaceable"><code>dvd</code></em> refers to your DVD drive device.
		</div><div class="para">
			For instructions on how to prepare a network installation using CD-ROMs, refer to the instructions on the <code class="filename">README-en</code> file in <code class="filename">disk1</code>.
		</div></li></ul></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="id799943">3.5.1.Â Preparing for FTP and HTTP installation</h3></div></div></div><div class="para">
		Extract the files from the iso image of the installation DVD or the iso images of the installation CDs and place them in a directory that is shared over FTP or HTTP.
	</div><div class="para">
		Next, make sure that the  directory is shared via FTP or HTTP, and verify client access. You can check to see whether the directory is accessible from the server itself, and then from another machine on the same subnet that you will be installing to.
	</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-steps-make-cd.html"><strong>Prev</strong>3.4.2.Â Making an Installation Boot CD-ROM</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch03s05s02.html"><strong>Next</strong>3.5.2.Â Preparing for an NFS install</a></li></ul></body></html>


--- NEW FILE s1-timezone-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.16.Â Time Zone Configuration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="sn-networkconfig-fedora.html" title="7.15.Â Network Configuration" /><link rel="next" href="sn-account_configuration.html" title="7.17.Â Set the Root Password" /></head><body class="draft "><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="Doc
 umentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-networkconfig-fedora.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-account_configuration.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-timezone-x86">7.16.Â Time Zone Configuration</h2></div></div></div><a id="id788386" class="indexterm"></a><a id="id856236" class="indexterm"></a><a id="id845038" class="indexterm"></a><a id="id833682" class="indexterm"></a><a id="id846315" class="indexterm"></a><a id="id867026" class="indexterm"></a><a id="id864465" class="indexterm"></a><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.
</div><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.
</div><div class="para">
	From here there are two ways for you to select your time zone:
</div><div class="itemizedlist"><ul><li><div class="para">
			Using your mouse, click on the interactive map to select a specific city (represented by a yellow dot). A red <span class="guilabel"><strong>X</strong></span> appears indicating your selection.
		</div></li><li><div class="para">
			You can also scroll through the list at the bottom of the screen to select your time zone. Using your mouse, click on a location to highlight your selection.
		</div></li></ul></div><div class="figure" id="id867669"><div class="figure-contents"><div class="mediaobject"><img src="images/timezone/timezone.png" alt="Configuring the Time Zone" /><div class="longdesc"><div class="para">
				Time zone configuration screen.
			</div></div></div></div><h6>FigureÂ 7.13.Â Configuring the Time Zone</h6></div><br class="figure-break" /><div class="para">
	If Fedora is the only operating system on your computer, select <span class="guilabel"><strong>System clock uses UTC</strong></span>. The system clock is a piece of hardware on your computer system. Fedora uses the timezone setting to determine the offset between the local time and UTC on the system clock. This behavior is standard for UNIX-like operating systems.
</div><div class="warning"><h2>Windows and the System Clock</h2><div class="para">
		Do not enable the <span class="guilabel"><strong>System clock uses UTC</strong></span> option if your machine also runs Microsoft Windows. Microsoft operating systems change the BIOS clock to match local time rather than UTC. This may cause unexpected behavior under Fedora.
	</div></div><div class="note"><h2>Note</h2><div class="para">
		To change your time zone configuration after you have completed the installation, use the <span class="application"><strong>Time and Date Properties Tool</strong></span>.
	</div><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 class="para">
	Select <span class="guibutton"><strong>Next</strong></span> to proceed.
</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-networkconfig-fedora.html"><strong>Prev</strong>7.15.Â Network Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-account_configuration.html"><strong>Next</strong>7.17.Â Set the Root Password</a></li></ul></body></html>


--- NEW FILE s1-trouble-install-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.3.Â Trouble During the Installation</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-trouble-x86.html" title="ChapterÂ 8.Â Troubleshooting Installation on an Intel or AMD System" /><link rel="prev" href="ch08s02.html" title="8.2.Â Trouble Beginning the Installation" /><link rel="next" href="s2-trouble-tracebacks-x86.html" title="8.3.2.Â Saving traceback messages without removeable media" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-trouble-tracebacks-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-trouble-install-x86">8.3.Â Trouble During the Installation</h2></div></div></div><a id="id907206" class="indexterm"></a><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-trouble-nodevicefound-x86">8.3.1.Â <code class="computeroutput">No devices found to install Fedora </code> Error Message</h3></div></div></div><a id="id996225" 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 class="para">
			Check your hardware vendor's website to determine if a driver diskette image is available that fixes your problem. For more general information on driver diskettes, refer to <a class="xref" href="ch-driverdisk-x86.html" title="ChapterÂ 5.Â Driver Media for Intel and AMD Systems">ChapterÂ 5, <i>Driver Media for Intel and AMD Systems</i></a>.
		</div><div class="para">
	You can also refer to the LinuxQuestions.org Hardware Compatibility List, available online at:
</div><div class="para">
	<a href="http://www.linuxquestions.org/hcl/index.php">http://www.linuxquestions.org/hcl/index.php</a>
</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02.html"><strong>Prev</strong>8.2.Â Trouble Beginning the Installation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-trouble-tracebacks-x86.html"><strong>Next</strong>8.3.2.Â Saving traceback messages without removeab...</a></li></ul></body></html>


--- NEW FILE s1-x86-bootloader.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.22.Â x86, AMD64, and Intel 64 Boot Loader Configuration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="s2-diskpartdelete-x86.html" title="7.21.7.Â Deleting a Partition" /><link rel="next" href="s2-x86-bootloader-rescue.html" title="7.22.2.Â Rescue Mode" /></head><body class="draft "><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_r
 ight.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-diskpartdelete-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-x86-bootloader-rescue.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-x86-bootloader">7.22.Â x86, AMD64, and <span class="trademark">Intel</span>Â® 64 Boot Loader Configuration</h2></div></div></div><a id="id934001" class="indexterm"></a><a id="id834866" class="indexterm"></a><a id="id972436" class="indexterm"></a><a id="id892516" class="indexterm"></a><a id="id834518" class="indexterm"></a><a id="id864883" class="indexterm"></a><a id="id864896" 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"><h2>Installing in text mode</h2><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 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 DOS or Windows, by loading another boot loader).
	</div><div class="note"><h2>The GRUB boot menu</h2><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 class="figure" id="fig-x86-bootloader"><div class="figure-contents"><div class="mediaobject"><img src="images/x86-bootloader/x86-bootloader.png" alt="Boot Loader Configuration" /><div class="longdesc"><div class="para">
					Configure how you would like to boot the system.
				</div></div></div></div><h6>FigureÂ 7.25.Â Boot Loader Configuration</h6></div><br class="figure-break" /><div class="para">
		If there are no other operating systems on your computer, or you are completely removing any other operating systems the installation program will install <span class="application"><strong>GRUB</strong></span> as your boot loader without any intervention. In that case you may continue on to <a class="xref" href="s1-pkgselection-x86.html" title="7.23.Â Package Group Selection">SectionÂ 7.23, â€œPackage Group Selectionâ€</a>.
	</div><div class="para">
		You may have a boot loader installed on your system already. An operating system may install its own preferred boot loader, or you may have installed a third-party boot loader.If your boot loader does not recognize Linux partitions, you may not be able to boot Fedora. Use <span class="application"><strong>GRUB</strong></span> as your boot loader to boot Linux and most other operating systems. Follow the directions in this chapter to install <span class="application"><strong>GRUB</strong></span>.
	</div><div class="warning"><h2>Installing GRUB</h2><div class="para">
			If you install GRUB, it may overwrite your existing boot loader.
		</div></div><div class="para">
		By default, the installation program installs GRUB in the master boot record or <abbr class="abbrev">MBR</abbr>, of the device for the root file system. To decline installation of a new boot loader, unselect <span class="guilabel"><strong>Install boot loader on /dev/sda</strong></span>.
	</div><div class="warning"><h2>Warning</h2><div class="para">
			If you choose not to install GRUB for any reason, you will not be able to boot the system directly, and you must use another boot method (such as a commercial boot loader application). Use this option only if you are sure you have another way of booting the system!
		</div></div><div class="para">
		If you have other operating systems already installed, Fedora attempts to automatically detect and configure <span class="application"><strong>GRUB</strong></span> to boot them. You may manually configure any additional operating systems if <span class="application"><strong>GRUB</strong></span> does not detect them.
	</div><div class="para">
		To add, remove, or change the detected operating system settings, use the options provided.
	</div><div class="variablelist"><dl><dt><span class="term"><span class="guibutton"><strong>Add</strong></span></span></dt><dd><div class="para">
					Select <span class="guibutton"><strong>Add</strong></span> to include an additional operating system in GRUB.
				</div><div class="para">
					Select the disk partition which contains the bootable operating system from the drop-down list and give the entry a label. <span class="application"><strong>GRUB</strong></span> displays this label in its boot menu.
				</div></dd><dt><span class="term"><span class="guibutton"><strong>Edit</strong></span></span></dt><dd><div class="para">
					To change an entry in the GRUB boot menu, select the entry and then select <span class="guibutton"><strong>Edit</strong></span>.
				</div></dd><dt><span class="term"><span class="guibutton"><strong>Delete</strong></span></span></dt><dd><div class="para">
					To remove an entry from the GRUB boot menu, select the entry and then select <span class="guibutton"><strong>Delete</strong></span>.
				</div></dd></dl></div><div class="para">
		Select <span class="guilabel"><strong>Default</strong></span> beside the preferred boot partition to choose your default bootable OS. You cannot move forward in the installation unless you choose a default boot image.
	</div><div class="note"><h2>Note</h2><div class="para">
			The <span class="guilabel"><strong>Label</strong></span> column lists what you must enter at the boot prompt, in non-graphical boot loaders, in order to boot the desired operating system.
		</div><div class="para">
			Once you have loaded the GRUB boot screen, use the arrow keys to choose a boot label or type <span class="keycap"><strong>e</strong></span> for edit. You are presented with a list of items in the configuration file for the boot label you have selected.
		</div></div><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, or USB media if the BIOS supports it. Security plans which include boot loader passwords should also address alternate boot methods.
	</div><a id="id851098" class="indexterm"></a><a id="id789432" class="indexterm"></a><a id="id845688" class="indexterm"></a><div class="note"><h2>GRUB Passwords Not Required</h2><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 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>.
	</div><div class="para">
		Once selected, enter a password and confirm it.
	</div><div class="para">
		<span class="application"><strong>GRUB</strong></span> stores the password in encrypted form, so it <span class="emphasis"><em>cannot</em></span> be read or recovered. If you forget the boot password, boot the system normally and then change the password entry in the <code class="filename">/boot/grub/grub.conf</code> file. If you cannot boot, you may be able to use the "rescue" mode on the first Fedora installation disc to reset the GRUB password.
	</div><div class="para">
		If you do need to change the <span class="application"><strong>GRUB</strong></span> password, use the <code class="command">grub-md5-crypt</code> utility. For information on using this utility, use the command <code class="command">man grub-md5-crypt</code> in a terminal window to read the manual pages.
	</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" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="x86-bootloader-adv">7.22.1.Â Advanced Boot Loader Configuration</h3></div></div></div><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><a id="id866144" class="indexterm"></a><a id="id914525" class="indexterm"></a><a id="id855969" class="indexterm"></a><div class="itemizedlist"><ul><li><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><div class="para">
					<a id="id876483" 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"><h2>GRUB as a Secondary Boot Loader</h2><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.
					</div></div></li></ul></div><div class="figure" id="fig-x86-adv-bootloader"><div class="figure-contents"><div class="mediaobject"><img src="images/x86-bootloader/x86-adv-bootloader.png" alt="Boot Loader Installation" /><div class="longdesc"><div class="para">
						Choose where to install a boot loader and how to configure it.
					</div></div></div></div><h6>FigureÂ 7.26.Â Boot Loader Installation</h6></div><br class="figure-break" /><div class="note"><h2>Note</h2><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 boot loader <span class="emphasis"><em>should not</em></span> be installed on the MBR of the RAID array. Rather, the boot loader should be installed on the MBR of the same drive as the <code class="filename">/boot/</code> partition was created.
			</div></div><div class="para">
			If your system only uses Fedora, you should choose the MBR.
		</div><div class="para">
			Click the <span class="guibutton"><strong>Change Drive Order</strong></span> button if you would like to rearrange the drive order or if your BIOS does not return the correct drive order. Changing the drive order may be useful if you have multiple SCSI adapters, or both SCSI and IDE adapters, and you want to boot from the SCSI device.
		</div><div class="note"><h2>Note</h2><div class="para">
		While partitioning your hard drive, keep in mind that the BIOS in some older systems cannot access more than the first 1024 cylinders on a hard drive. If this is the case, leave enough room for the <code class="filename">/boot</code> Linux partition on the first 1024 cylinders of your hard drive to boot Linux. The other Linux partitions can be after cylinder 1024.
	</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><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-diskpartdelete-x86.html"><strong>Prev</strong>7.21.7.Â Deleting a Partition</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-x86-bootloader-rescue.html"><strong>Next</strong>7.22.2.Â Rescue Mode</a></li></ul></body></html>


--- NEW FILE s1-x86-starting.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.Â Starting the Installation Program</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="s1-guimode-textinterface-x86.html" title="7.2.Â The Text Mode Installation Program User Interface" /><link rel="next" href="s2-x86-starting-bootopts.html" title="7.3.2.Â Additional Boot Options" /></head><body class="draft "><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="Com
 mon_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-guimode-textinterface-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-x86-starting-bootopts.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="s1-x86-starting">7.3.Â Starting the Installation Program</h2></div></div></div><a id="id905524" class="indexterm"></a><a id="id890270" class="indexterm"></a><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.html" title="ChapterÂ 3.Â Steps to Get You Started">ChapterÂ 3, <i>Steps to Get You Started</i></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 CD-ROM #1 or any boot media that you have created.
	</div><div class="note"><h2>Note</h2><a id="id804084" class="indexterm"></a><div class="para">
			Occasionally, some hardware components require a <em class="firstterm">driver diskette</em> during the installation. A driver diskette adds support for hardware that is not otherwise supported by the installation program. Refer to <a class="xref" href="ch-driverdisk-x86.html" title="ChapterÂ 5.Â Driver Media for Intel and AMD Systems">ChapterÂ 5, <i>Driver Media for Intel and AMD Systems</i></a> for more information.
		</div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-x86-starting-booting">7.3.1.Â Booting the Installation Program on x86, AMD64, and <span class="trademark">Intel</span>Â® 64 Systems</h3></div></div></div><a id="id914396" class="indexterm"></a><a id="id864410" 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><div class="para">
					<span class="emphasis"><em>Fedora DVD/CD-ROM</em></span> â€” Your machine supports a bootable DVD/CD-ROM drive and you have the Fedora CD-ROM set or DVD.
				</div></li><li><div class="para">
					<span class="emphasis"><em>Boot CD-ROM</em></span> â€” Your machine supports a bootable CD-ROM drive and you want to perform network or hard drive installation.
				</div></li><li><div class="para">
					<span class="emphasis"><em>USB pen drive</em></span> â€” Your machine supports booting from a USB device.
				</div></li><li><div class="para">
					<span class="emphasis"><em>PXE boot via network</em></span> â€” Your machine supports booting from the network. This is an advanced installation path. Refer to <a class="xref" href="ap-install-server.html" title="ChapterÂ 11.Â Setting Up an Installation Server">ChapterÂ 11, <i>Setting Up an Installation Server</i></a> for additional information on this method.
				</div></li></ul></div><div class="para">
			To create a boot CD-ROM or to prepare your USB pen drive for installation, refer to <a class="xref" href="s2-steps-make-cd.html" title="3.4.2.Â Making an Installation Boot CD-ROM">SectionÂ 3.4.2, â€œMaking an Installation Boot CD-ROMâ€</a>.
		</div><div class="para">
			Insert the boot media and reboot the system. Your BIOS settings may need to be changed to allow you to boot from the CD-ROM or USB device.
		</div><div class="note"><h2>Note</h2><div class="para">
				To change your BIOS settings on an x86, AMD64, or <span class="trademark">Intel</span>Â® 64 system, watch the instructions provided on your display when your computer first boots. A line of text appears, telling you which key to press to enter the BIOS settings.
			</div><div class="para">
				Once you have entered your BIOS setup program, find the section where you can alter your boot sequence. The default is often C, A or A, C (depending on whether you boot from your hard drive [C] or a diskette drive [A]). Change this sequence so that the CD-ROM is first in your boot order and that C or A (whichever is your typical boot default) is second. This instructs the computer to first look at the CD-ROM drive for bootable media; if it does not find bootable media on the CD-ROM drive, it then checks your hard drive or diskette drive.
			</div><div class="para">
				Save your changes before exiting the BIOS. For more information, refer to the documentation that came with your system.
			</div></div><div class="para">
			After a short delay, a screen containing the <code class="prompt">boot:</code> prompt should appear. The screen contains information on a variety of boot options. Each boot option also has one or more help screens associated with it. To access a help screen, press the appropriate function key as listed in the line at the bottom of the screen.
		</div><div class="para">
			As you boot the installation program, be aware of two issues:
		</div><div class="itemizedlist"><ul><li><div class="para">
					Once the <code class="prompt">boot:</code> prompt appears, the installation program automatically begins if you take no action within the first minute. To disable this feature, press one of the help screen function keys.
				</div></li><li><div class="para">
					If you press a help screen function key, there is a slight delay while the help screen is read from the boot media.
				</div></li></ul></div><div class="para">
			Normally, you only need to press <span class="keycap"><strong>Enter</strong></span> to boot. Be sure to watch the boot messages to review if the Linux kernel detects your hardware. If your hardware is properly detected, continue to the next section. If it does not properly detect your hardware, you may need to restart the installation and use one of the boot options provided in <a class="xref" href="ap-admin-options.html" title="ChapterÂ 9.Â Boot Options">ChapterÂ 9, <i>Boot Options</i></a>.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-guimode-textinterface-x86.html"><strong>Prev</strong>7.2.Â The Text Mode Installation Program User Inte...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-x86-starting-bootopts.html"><strong>Next</strong>7.3.2.Â Additional Boot Options</a></li></ul></body></html>


--- NEW FILE s2-boot-init-shutdown-init.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.2.4.Â The /sbin/init Program</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-boot-init-shutdown-process.html" title="F.2.Â A Detailed Look at the Boot Process" /><link rel="prev" href="s2-boot-init-shutdown-kernel.html" title="F.2.3.Â The Kernel" /><link rel="next" href="s1-boot-init-shutdown-run-boot.html" title="F.3.Â Running Additional Programs at Boot Time" /></head><body class="draft "><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/image
 s/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-boot-init-shutdown-kernel.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-boot-init-shutdown-run-boot.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-boot-init-shutdown-init">F.2.4.Â The <code class="command">/sbin/init</code> Program</h3></div></div></div><a id="id819224" class="indexterm"></a><a id="id819246" class="indexterm"></a><a id="id842858" class="indexterm"></a><div class="para">
				The <code class="command">/sbin/init</code> program (also called <code class="command">init</code>) coordinates the rest of the boot process and configures the environment for the user.
			</div><div class="para">
				When the <code class="command">init</code> command starts, it becomes the parent or grandparent of all of the processes that start up automatically on the system. First, it runs the <code class="filename">/etc/rc.d/rc.sysinit</code> script, which sets the environment path, starts swap, checks the file systems, and executes all other steps required for system initialization. For example, most systems use a clock, so <code class="filename">rc.sysinit</code> reads the <code class="filename">/etc/sysconfig/clock</code> configuration file to initialize the hardware clock. Another example is if there are special serial port processes which must be initialized, <code class="filename">rc.sysinit</code> executes the <code class="filename">/etc/rc.serial</code> file.
			</div><div class="para">
				The <code class="command">init</code> command then runs the <code class="filename">/etc/inittab</code> script, which describes how the system should be set up in each <em class="firstterm">SysV init runlevel</em>. Runlevels are a state, or <em class="firstterm">mode</em>, defined by the services listed in the SysV <code class="filename">/etc/rc.d/rc<em class="replaceable"><code><x></code></em>.d/</code> directory, where <em class="replaceable"><code><x></code></em> is the number of the runlevel. For more information on SysV init runlevels, refer to <a class="xref" href="s1-boot-init-shutdown-sysv.html" title="F.4.Â SysV Init Runlevels">SectionÂ F.4, â€œSysV Init Runlevelsâ€</a>.
			</div><div class="para">
				Next, the <code class="command">init</code> command sets the source function library, <code class="filename">/etc/rc.d/init.d/functions</code>, for the system, which configures how to start, kill, and determine the PID of a program.
			</div><div class="para">
				The <code class="command">init</code> program starts all of the background processes by looking in the appropriate <code class="filename">rc</code> directory for the runlevel specified as the default in <code class="filename">/etc/inittab</code>. The <code class="filename">rc</code> directories are numbered to correspond to the runlevel they represent. For instance, <code class="filename">/etc/rc.d/rc5.d/</code> is the directory for runlevel 5.
			</div><div class="para">
				When booting to runlevel 5, the <code class="command">init</code> program looks in the <code class="filename">/etc/rc.d/rc5.d/</code> directory to determine which processes to start and stop.
			</div><div class="para">
				Below is an example listing of the <code class="filename">/etc/rc.d/rc5.d/</code> directory:
			</div><pre class="screen">
K05innd -> ../init.d/innd 
K05saslauthd -> ../init.d/saslauthd 
K10dc_server -> ../init.d/dc_server 
K10psacct -> ../init.d/psacct 
K10radiusd -> ../init.d/radiusd 
K12dc_client -> ../init.d/dc_client 
K12FreeWnn -> ../init.d/FreeWnn 
K12mailman -> ../init.d/mailman 
K12mysqld -> ../init.d/mysqld 
K15httpd -> ../init.d/httpd 
K20netdump-server -> ../init.d/netdump-server 
K20rstatd -> ../init.d/rstatd 
K20rusersd -> ../init.d/rusersd 
K20rwhod -> ../init.d/rwhod 
K24irda -> ../init.d/irda 
K25squid -> ../init.d/squid 
K28amd -> ../init.d/amd 
K30spamassassin -> ../init.d/spamassassin 
K34dhcrelay -> ../init.d/dhcrelay 
K34yppasswdd -> ../init.d/yppasswdd 
K35dhcpd -> ../init.d/dhcpd 
K35smb -> ../init.d/smb 
K35vncserver -> ../init.d/vncserver 
K36lisa -> ../init.d/lisa 
K45arpwatch -> ../init.d/arpwatch 
K45named -> ../init.d/named 
K46radvd -> ../init.d/radvd 
K50netdump -> ../init.d/netdump 
K50snmpd -> ../init.d/snmpd 
K50snmptrapd -> ../init.d/snmptrapd 
K50tux -> ../init.d/tux 
K50vsftpd -> ../init.d/vsftpd 
K54dovecot -> ../init.d/dovecot 
K61ldap -> ../init.d/ldap 
K65kadmin -> ../init.d/kadmin 
K65kprop -> ../init.d/kprop 
K65krb524 -> ../init.d/krb524 
K65krb5kdc -> ../init.d/krb5kdc 
K70aep1000 -> ../init.d/aep1000 
K70bcm5820 -> ../init.d/bcm5820 
K74ypserv -> ../init.d/ypserv 
K74ypxfrd -> ../init.d/ypxfrd 
K85mdmpd -> ../init.d/mdmpd 
K89netplugd -> ../init.d/netplugd 
K99microcode_ctl -> ../init.d/microcode_ctl 
S04readahead_early -> ../init.d/readahead_early 
S05kudzu -> ../init.d/kudzu 
S06cpuspeed -> ../init.d/cpuspeed 
S08ip6tables -> ../init.d/ip6tables 
S08iptables -> ../init.d/iptables 
S09isdn -> ../init.d/isdn 
S10network -> ../init.d/network 
S12syslog -> ../init.d/syslog 
S13irqbalance -> ../init.d/irqbalance 
S13portmap -> ../init.d/portmap 
S15mdmonitor -> ../init.d/mdmonitor 
S15zebra -> ../init.d/zebra 
S16bgpd -> ../init.d/bgpd 
S16ospf6d -> ../init.d/ospf6d 
S16ospfd -> ../init.d/ospfd 
S16ripd -> ../init.d/ripd 
S16ripngd -> ../init.d/ripngd 
S20random -> ../init.d/random 
S24pcmcia -> ../init.d/pcmcia 
S25netfs -> ../init.d/netfs 
S26apmd -> ../init.d/apmd 
S27ypbind -> ../init.d/ypbind 
S28autofs -> ../init.d/autofs 
S40smartd -> ../init.d/smartd 
S44acpid -> ../init.d/acpid 
S54hpoj -> ../init.d/hpoj 
S55cups -> ../init.d/cups 
S55sshd -> ../init.d/sshd 
S56rawdevices -> ../init.d/rawdevices 
S56xinetd -> ../init.d/xinetd 
S58ntpd -> ../init.d/ntpd 
S75postgresql -> ../init.d/postgresql 
S80sendmail -> ../init.d/sendmail 
S85gpm -> ../init.d/gpm 
S87iiim -> ../init.d/iiim 
S90canna -> ../init.d/canna 
S90crond -> ../init.d/crond 
S90xfs -> ../init.d/xfs 
S95atd -> ../init.d/atd 
S96readahead -> ../init.d/readahead 
S97messagebus -> ../init.d/messagebus 
S97rhnsd -> ../init.d/rhnsd 
S99local -> ../rc.local
</pre><div class="para">
				As illustrated in this listing, none of the scripts that actually start and stop the services are located in the <code class="filename">/etc/rc.d/rc5.d/</code> directory. Rather, all of the files in <code class="filename">/etc/rc.d/rc5.d/</code> are <em class="firstterm">symbolic links</em> pointing to scripts located in the <code class="filename">/etc/rc.d/init.d/</code> directory. Symbolic links are used in each of the <code class="filename">rc</code> directories so that the runlevels can be reconfigured by creating, modifying, and deleting the symbolic links without affecting the actual scripts they reference.
			</div><div class="para">
				The name of each symbolic link begins with either a <code class="computeroutput">K</code> or an <code class="computeroutput">S</code>. The <code class="computeroutput">K</code> links are processes that are killed on that runlevel, while those beginning with an <code class="computeroutput">S</code> are started.
			</div><div class="para">
				The <code class="command">init</code> command first stops all of the <code class="computeroutput">K</code> symbolic links in the directory by issuing the <code class="command">/etc/rc.d/init.d/<em class="replaceable"><code><command></code></em> stop</code> command, where <em class="replaceable"><code><command></code></em> is the process to be killed. It then starts all of the <code class="computeroutput">S</code> symbolic links by issuing <code class="command">/etc/rc.d/init.d/<em class="replaceable"><code><command></code></em> start</code>.
			</div><div class="note"><h2>Note</h2><div class="para">
					After the system is finished booting, it is possible to log in as root and execute these same scripts to start and stop services. For instance, the command <code class="command">/etc/rc.d/init.d/httpd stop</code> stops the Apache HTTP Server.
				</div></div><div class="para">
				Each of the symbolic links are numbered to dictate start order. The order in which the services are started or stopped can be altered by changing this number. The lower the number, the earlier it is started. Symbolic links with the same number are started alphabetically.
			</div><div class="note"><h2>Note</h2><div class="para">
					One of the last things the <code class="command">init</code> program executes is the <code class="filename">/etc/rc.d/rc.local</code> file. This file is useful for system customization. Refer to <a class="xref" href="s1-boot-init-shutdown-run-boot.html" title="F.3.Â Running Additional Programs at Boot Time">SectionÂ F.3, â€œRunning Additional Programs at Boot Timeâ€</a> for more information about using the <code class="filename">rc.local</code> file.
				</div></div><div class="para">
				After the <code class="command">init</code> command has progressed through the appropriate <code class="filename">rc</code> directory for the runlevel, the <code class="filename">/etc/inittab</code> script forks an <code class="command">/sbin/mingetty</code> process for each virtual console (login prompt) allocated to the runlevel. Runlevels 2 through 5 have all six virtual consoles, while runlevel 1 (single user mode) has one, and runlevels 0 and 6 have none. The <code class="command">/sbin/mingetty</code> process opens communication pathways to <em class="firstterm">tty</em> devices<sup>[<a id="id943711" href="#ftn.id943711" class="footnote">8</a>]</sup>, sets their modes, prints the login prompt, accepts the user's username and password, and initiates the login process.
			</div><div class="para">
				In runlevel 5, the <code class="filename">/etc/inittab</code> runs a script called <code class="filename">/etc/X11/prefdm</code>. The <code class="filename">prefdm</code> script executes the preferred X display manager<sup>[<a id="id943748" href="#ftn.id943748" class="footnote">9</a>]</sup> â€” <code class="command">gdm</code>, <code class="command">kdm</code>, or <code class="command">xdm</code>, depending on the contents of the <code class="filename">/etc/sysconfig/desktop</code> file.
			</div><div class="para">
				Once finished, the system operates on runlevel 5 and displays a login screen.
			</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id943711" href="#id943711" class="para">8</a>] </sup>
					Refer to the Red Hat Enterprise Linux Deployment Guide for more information about <code class="filename">tty</code> devices.
				</p></div><div class="footnote"><p><sup>[<a id="ftn.id943748" href="#id943748" class="para">9</a>] </sup>
					Refer to the Red Hat Enterprise Linux Deployment Guide for more information about display managers.
				</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-boot-init-shutdown-kernel.html"><strong>Prev</strong>F.2.3.Â The Kernel</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-boot-init-shutdown-run-boot.html"><strong>Next</strong>F.3.Â Running Additional Programs at Boot Time</a></li></ul></body></html>


--- NEW FILE s2-boot-init-shutdown-kernel.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.2.3.Â The Kernel</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-boot-init-shutdown-process.html" title="F.2.Â A Detailed Look at the Boot Process" /><link rel="prev" href="s2-boot-init-shutdown-loader.html" title="F.2.2.Â The Boot Loader" /><link rel="next" href="s2-boot-init-shutdown-init.html" title="F.2.4.Â The /sbin/init Program" /></head><body class="draft "><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="Doc
 umentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-boot-init-shutdown-loader.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-boot-init-shutdown-init.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-boot-init-shutdown-kernel">F.2.3.Â The Kernel</h3></div></div></div><a id="id899330" class="indexterm"></a><a id="id899347" class="indexterm"></a><div class="para">
				When the kernel is loaded, it immediately initializes and configures the computer's memory and configures the various hardware attached to the system, including all processors, I/O subsystems, and storage devices. It then looks for the compressed <code class="filename">initramfs</code> image(s) in a predetermined location in memory, decompresses it directly to <code class="filename">/sysroot/</code>, and loads all necessary drivers. Next, it initializes virtual devices related to the file system, such as LVM or software RAID, before completing the <code class="filename">initramfs</code> processes and freeing up all the memory the disk image once occupied.
			</div><div class="para">
				The kernel then creates a root device, mounts the root partition read-only, and frees any unused memory.
			</div><div class="para">
				At this point, the kernel is loaded into memory and operational. However, since there are no user applications that allow meaningful input to the system, not much can be done with the system.
			</div><div class="para">
				To set up the user environment, the kernel executes the <code class="command">/sbin/init</code> program.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-boot-init-shutdown-loader.html"><strong>Prev</strong>F.2.2.Â The Boot Loader</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-boot-init-shutdown-init.html"><strong>Next</strong>F.2.4.Â The /sbin/init Program</a></li></ul></body></html>


--- NEW FILE s2-boot-init-shutdown-loader.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.2.2.Â The Boot Loader</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-boot-init-shutdown-process.html" title="F.2.Â A Detailed Look at the Boot Process" /><link rel="prev" href="s1-boot-init-shutdown-process.html" title="F.2.Â A Detailed Look at the Boot Process" /><link rel="next" href="s2-boot-init-shutdown-kernel.html" title="F.2.3.Â The Kernel" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-boot-init-shutdown-process.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-boot-init-shutdown-kernel.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-boot-init-shutdown-loader">F.2.2.Â The Boot Loader</h3></div></div></div><a id="id891198" class="indexterm"></a><a id="id891216" class="indexterm"></a><a id="id891229" class="indexterm"></a><a id="id870303" class="indexterm"></a><a id="id870317" class="indexterm"></a><div class="para">
				This section looks at the default boot loader for the x86 platform, GRUB.  For more information about configuring and using GRUB, see <a class="xref" href="ch-grub.html" title="AppendixÂ E.Â The GRUB Boot Loader">AppendixÂ E, <i>The GRUB Boot Loader</i></a>.
			</div><div class="para">
				A boot loader for the x86 platform is broken into at least two stages. The first stage is a small machine code binary on the MBR. Its sole job is to locate the second stage boot loader and load the first part of it into memory.
			</div><div class="para">
				GRUB has the advantage of being able to read ext2 and ext3 <sup>[<a id="id870350" href="#ftn.id870350" class="footnote">7</a>]</sup> partitions and load its configuration file â€” <code class="filename">/boot/grub/grub.conf</code> â€” at boot time. Refer to <a class="xref" href="s1-grub-configfile.html" title="E.6.Â GRUB Menu Configuration File">SectionÂ E.6, â€œGRUB Menu Configuration Fileâ€</a> for information on how to edit this file.
			</div><div class="important"><h2>ext4 and Btrfs</h2><div class="para">
					The <span class="application"><strong>GRUB</strong></span> bootloader does not support the ext4 or Btrfs file systems.
				</div></div><div class="note"><h2>Note</h2><div class="para">
					If upgrading the kernel using the <span class="application"><strong>Red Hat Update Agent</strong></span>, the boot loader configuration file is updated automatically. More information on Red Hat Network can be found online at the following URL: <a href="https://rhn.redhat.com/">https://rhn.redhat.com/</a>.
				</div></div><div class="para">
				Once the second stage boot loader is in memory, it presents the user with a graphical screen showing the different operating systems or kernels it has been configured to boot. On this screen a user can use the arrow keys to choose which operating system or kernel they wish to boot and press <span class="keycap"><strong>Enter</strong></span>. If no key is pressed, the boot loader loads the default selection after a configurable period of time has passed.
			</div><div class="para">
				Once the second stage boot loader has determined which kernel to boot, it locates the corresponding kernel binary in the <code class="filename">/boot/</code> directory. The kernel binary is named using the following format â€” <code class="filename">/boot/vmlinuz-<em class="replaceable"><code><kernel-version></code></em></code> file (where <code class="filename"><em class="replaceable"><code><kernel-version></code></em></code> corresponds to the kernel version specified in the boot loader's settings).
			</div><div class="para">
				For instructions on using the boot loader to supply command line arguments to the kernel, refer to <a class="xref" href="ch-grub.html" title="AppendixÂ E.Â The GRUB Boot Loader">AppendixÂ E, <i>The GRUB Boot Loader</i></a>. For information on changing the runlevel at the boot loader prompt, refer <a class="xref" href="s1-grub-runlevels.html" title="E.7.Â Changing Runlevels at Boot Time">SectionÂ E.7, â€œChanging Runlevels at Boot Timeâ€</a>.
			</div><div class="para">
				The boot loader then places one or more appropriate <em class="firstterm">initramfs</em> images into memory. Next, the kernel decompresses these images from memory to <code class="filename">/sysroot/</code>, a RAM-based virtual file system, via <code class="command">cpio</code>. The <code class="filename">initramfs</code> is used by the kernel to load drivers and modules necessary to boot the system. This is particularly important if SCSI hard drives are present or if the systems use the ext3 or ext4 file system.
			</div><div class="para">
				Once the kernel and the <code class="filename">initramfs</code> image(s) are loaded into memory, the boot loader hands control of the boot process to the kernel.
			</div><div class="para">
				For a more detailed overview of the GRUB boot loader, refer to <a class="xref" href="ch-grub.html" title="AppendixÂ E.Â The GRUB Boot Loader">AppendixÂ E, <i>The GRUB Boot Loader</i></a>.
			</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id870350" href="#id870350" class="para">7</a>] </sup>
					GRUB reads ext3 file systems as ext2, disregarding the journal file. Refer to the chapter titled <em class="citetitle">The ext3 File System</em> in the <em class="citetitle">Red Hat Enterprise Linux Deployment Guide</em> for more information on the ext3 file system.
				</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-boot-init-shutdown-process.html"><strong>Prev</strong>F.2.Â A Detailed Look at the Boot Process</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-boot-init-shutdown-kernel.html"><strong>Next</strong>F.2.3.Â The Kernel</a></li></ul></body></html>


--- NEW FILE s2-boot-init-shutdown-sysv-util.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.4.2.Â Runlevel Utilities</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-boot-init-shutdown-sysv.html" title="F.4.Â SysV Init Runlevels" /><link rel="prev" href="s1-boot-init-shutdown-sysv.html" title="F.4.Â SysV Init Runlevels" /><link rel="next" href="s1-boot-init-shutdown-shutdown.html" title="F.5.Â Shutting Down" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-boot-init-shutdown-sysv.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-boot-init-shutdown-shutdown.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-boot-init-shutdown-sysv-util">F.4.2.Â Runlevel Utilities</h3></div></div></div><a id="id892628" class="indexterm"></a><a id="id791182" class="indexterm"></a><a id="id791199" class="indexterm"></a><a id="id791217" class="indexterm"></a><a id="id791234" class="indexterm"></a><a id="id904523" class="indexterm"></a><a id="id904541" class="indexterm"></a><div class="para">
				One of the best ways to configure runlevels is to use an <em class="firstterm">initscript utility</em>. These tools are designed to simplify the task of maintaining files in the SysV init directory hierarchy and relieves system administrators from having to directly manipulate the numerous symbolic links in the subdirectories of <code class="filename">/etc/rc.d/</code>.
			</div><div class="para">
				Fedora provides three such utilities:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<code class="command">/sbin/chkconfig</code> â€” The <code class="command">/sbin/chkconfig</code> utility is a simple command line tool for maintaining the <code class="filename">/etc/rc.d/init.d/</code> directory hierarchy.
					</div></li><li><div class="para">
						<span class="application"><strong>/usr/sbin/ntsysv</strong></span> â€” The ncurses-based <span class="application"><strong>/sbin/ntsysv</strong></span> utility provides an interactive text-based interface, which some find easier to use than <code class="command">chkconfig</code>.
					</div></li><li><div class="para">
						<span class="application"><strong>Services Configuration Tool</strong></span> â€” The graphical <span class="application"><strong>Services Configuration Tool</strong></span> (<code class="command">system-config-services</code>) program is a flexible utility for configuring runlevels.
					</div></li></ul></div><div class="para">
				Refer to the chapter titled <em class="citetitle">Controlling Access to Services</em> in the <em class="citetitle">Red Hat Enterprise Linux Deployment Guide</em> for more information regarding these tools.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-boot-init-shutdown-sysv.html"><strong>Prev</strong>F.4.Â SysV Init Runlevels</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-boot-init-shutdown-shutdown.html"><strong>Next</strong>F.5.Â Shutting Down</a></li></ul></body></html>


--- NEW FILE s2-diskpartdelete-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.21.7.Â Deleting a Partition</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-diskpartitioning-x86.html" title="7.21.Â Partitioning Your System" /><link rel="prev" href="ch07s21s06.html" title="7.21.6.Â Editing Partitions" /><link rel="next" href="s1-x86-bootloader.html" title="7.22.Â x86, AMD64, and Intel 64 Boot Loader Configuration" /></head><body class="draft "><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="Docu
 mentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s21s06.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-x86-bootloader.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-diskpartdelete-x86">7.21.7.Â Deleting a Partition</h3></div></div></div><a id="id841880" class="indexterm"></a><a id="id828248" class="indexterm"></a><div class="para">
	To delete a partition, highlight it in the <span class="guilabel"><strong>Partitions</strong></span> section and click the <span class="guibutton"><strong>Delete</strong></span> button. Confirm the deletion when prompted.
</div><div class="para">
		For further installation instructions for x86, AMD64, and <span class="trademark">Intel</span>Â® 64 systems, skip to <a class="xref" href="s1-x86-bootloader.html" title="7.22.Â x86, AMD64, and Intel 64 Boot Loader Configuration">SectionÂ 7.22, â€œx86, AMD64, and Intel 64 Boot Loader Configurationâ€</a>.
	</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s21s06.html"><strong>Prev</strong>7.21.6.Â Editing Partitions</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-x86-bootloader.html"><strong>Next</strong>7.22.Â x86, AMD64, and Intel 64 Boot Loader Config...</a></li></ul></body></html>


--- NEW FILE s2-diskpartitioning-dd-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.21.2.Â The partitioning screen</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-diskpartitioning-x86.html" title="7.21.Â Partitioning Your System" /><link rel="prev" href="s1-diskpartitioning-x86.html" title="7.21.Â Partitioning Your System" /><link rel="next" href="ch07s21s03.html" title="7.21.3.Â Partition Fields" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-diskpartitioning-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch07s21s03.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-diskpartitioning-dd-x86">7.21.2.Â The partitioning screen</h3></div></div></div><a id="id855861" class="indexterm"></a><a id="id840636" class="indexterm"></a><a id="id868831" class="indexterm"></a><div class="para">
	These buttons are used to change the attributes of a partition (for example the file system type and mount point) and also to create RAID devices. Buttons on this screen are also used to accept the changes you have made, or to exit the partitioning screen. For further explanation, take a look at each button in order:
</div><div class="itemizedlist"><ul><li><div class="para">
		<span class="guibutton"><strong>New</strong></span>: Select this option to add a partition or LVM physical volume to the disk. In the <span class="guilabel"><strong>Add partition</strong></span> dialog, choose a mount point and a partition type. If you have more than one disk on the system, choose which disks the partition may inhabit. Indicate a size in megabytes for the partition. If you wish to encrypt the partition, select that option.
	</div><div class="important"><h2>Illegal Partitions</h2><div class="para">
			<a id="id847284" class="indexterm"></a>
			 You cannot create separate partitions for the <code class="filename">/bin/</code>, <code class="filename">/dev/</code>, <code class="filename">/etc/</code>, <code class="filename">/lib/</code>, <code class="filename">/proc/</code>, <code class="filename">/root/</code>, and <code class="filename">/sbin/</code> directories. These directories must reside on the 
			<a id="id790644" class="indexterm"></a>
			 <code class="filename">/</code> (root) partition.
		</div><div class="para">
			The <code class="filename">/boot</code> partition may not reside on an LVM volume group. Create the <code class="filename">/boot</code> partition before configuring any volume groups. Furthermore, you cannot use the ext4 or btrfs filesystems for the <code class="filename">/boot</code> partition.
		</div><div class="para">
			Avoid placing <code class="filename">/usr</code> on a separate partition. If <code class="filename">/usr</code> does not reside on the <code class="filename">/</code> (root) partition, the boot process becomes more complex and some systems (for example, those with iSCSI storage) will fail to boot.
		</div></div><div class="para">
		You may also choose from three options for sizing your partition:
	</div><div class="variablelist"><dl><dt><span class="term"><span class="guilabel"><strong>Fixed size</strong></span></span></dt><dd><div class="para">
					Use a fixed size as close to your entry as possible.
				</div></dd><dt><span class="term"><span class="guilabel"><strong>Fill all space up to</strong></span></span></dt><dd><div class="para">
					Grow the partition to a maximum size of your choice.
				</div></dd><dt><span class="term"><span class="guilabel"><strong>Fill to maximum allowable size</strong></span></span></dt><dd><div class="para">
					Grow the partition until it fills the remainder of the selected disks.
				</div></dd></dl></div><div class="note"><h2>Partition Sizes</h2><div class="para">
			The actual partition on the disk may be slightly smaller or larger than your choice. Disk geometry issues cause this effect, not an error or bug.
		</div></div><div class="para">
		Select the <span class="guilabel"><strong>Encrypt partition</strong></span> option to encrypt all information on the disk partition.
	</div><div class="para">
		After you enter the details for your partition, select <span class="guibutton"><strong>OK</strong></span> to continue. If you chose to encrypt the partition, the installer prompts you to assign a passphrase by typing it twice. For hints on using good passphrases, refer to <a class="xref" href="sn-account_configuration.html" title="7.17.Â Set the Root Password">SectionÂ 7.17, â€œSet the Root Passwordâ€</a>.
	</div></li><li><div class="para">
	<span class="guibutton"><strong>Edit</strong></span>: Used to modify attributes of the partition currently selected in the <span class="guilabel"><strong>Partitions</strong></span> section. Selecting <span class="guibutton"><strong>Edit</strong></span> opens a dialog box. Some or all of the fields can be edited, depending on whether the partition information has already been written to disk.
</div><div class="para">
	You can also edit free space as represented in the graphical display to create a new partition within that space. Either highlight the free space and then select the <span class="guibutton"><strong>Edit</strong></span> button, or double-click on the free space to edit it.
</div></li><li><div class="para">
		To make a RAID device, you must first create (or reuse existing) software RAID partitions. Once you have created two or more software RAID partitions, select <span class="guibutton"><strong>Make RAID</strong></span> to join the software RAID partitions into a RAID device.
	</div></li><li><div class="para">
		<span class="guibutton"><strong>Delete</strong></span>: Used to remove the partition currently highlighted in the <span class="guilabel"><strong>Current Disk Partitions</strong></span> section. You will be asked to confirm the deletion of any partition.
	</div><div class="para">
		To delete an LVM physical volume, first delete any volume groups of which that physical volume is a member.
	</div><div class="para">
		If you make a mistake, use the <span class="guilabel"><strong>Reset</strong></span> option to abandon all the changes you have made.
	</div></li><li><div class="para">
		<span class="guibutton"><strong>Reset</strong></span>: Used to restore the partitioning screen to its original state. All changes made will be lost if you <span class="guibutton"><strong>Reset</strong></span> the partitions.
	</div></li><li><div class="para">
		<span class="guibutton"><strong>RAID</strong></span>: Used to provide redundancy to any or all disk partitions. <span class="emphasis"><em>It should only be used if you have experience using RAID.</em></span> 
	</div><div class="para">
		To make a RAID device, you must first create software RAID partitions. Once you have created two or more software RAID partitions, select <span class="guibutton"><strong>RAID</strong></span> to join the software RAID partitions into a RAID device.
	</div><div class="figure" id="fig-diskpart-makeraid-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/diskpartitioning/raid-options.png" alt="RAID options" /><div class="longdesc"><div class="para">
					The RAID options dialog.
				</div></div></div></div><h6>FigureÂ 7.20.Â RAID options</h6></div><br class="figure-break" /><div class="variablelist"><dl><dt><span class="term"><span class="guilabel"><strong>Create a software RAID partition</strong></span></span></dt><dd><div class="para">
					Choose this option to add a partition for software RAID. This option is the only choice available if your disk contains no software RAID partitions.
				</div><div class="figure" id="fig-diskpart-software-raid-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/diskpartitioning/software-raid.png" alt="Create a software RAID partition" /><div class="longdesc"><div class="para">
								The create a software RAID partition dialog.
							</div></div></div></div><h6>FigureÂ 7.21.Â Create a software RAID partition</h6></div><br class="figure-break" /></dd><dt><span class="term"><span class="guilabel"><strong>Create a RAID device</strong></span></span></dt><dd><div class="para">
					Choose this option to construct a RAID device from two or more existing software RAID partitions. This option is available if two or more software RAID partitions have been configured.
				</div><div class="figure" id="fig-diskpart-raid-device-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/diskpartitioning/raid-device.png" alt="Create a RAID device" /><div class="longdesc"><div class="para">
								The create a RAID device dialog.
							</div></div></div></div><h6>FigureÂ 7.22.Â Create a RAID device</h6></div><br class="figure-break" /></dd><dt><span class="term"><span class="guilabel"><strong>Clone a drive to create a RAID device</strong></span></span></dt><dd><div class="para">
					Choose this option to set up a RAID <em class="firstterm">mirror</em> of an existing disk. This option is available if two or more disks are attached to the system.
				</div><div class="figure" id="fig-diskpart-clone-raid-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/diskpartitioning/raid-clone.png" alt="Clone a RAID device" /><div class="longdesc"><div class="para">
								The clone a RAID device dialog.
							</div></div></div></div><h6>FigureÂ 7.23.Â Clone a RAID device</h6></div><br class="figure-break" /></dd></dl></div></li><li><div class="para">
		<span class="guibutton"><strong>LVM</strong></span>: Allows you to create an LVM logical volume. The role of LVM (Logical Volume Manager) is to present a simple logical view of underlying physical storage space, such as a hard drive(s). LVM manages individual physical disks â€” or to be more precise, the individual partitions present on them. <span class="emphasis"><em>It should only be used if you have experience using LVM.</em></span>  Note, LVM is only available in the graphical installation program.
	</div><div class="para">
		To assign one or more physical volumes to a volume group, first name the volume group. Then select the physical volumes to be used in the volume group. Finally, configure logical volumes on any volume groups using the <span class="guilabel"><strong>Add</strong></span>, <span class="guilabel"><strong>Edit</strong></span> and <span class="guilabel"><strong>Delete</strong></span> options.
	</div><div class="para">
		You may not remove a physical volume from a volume group if doing so would leave insufficient space for that group's logical volumes. Take for example a volume group made up of two 5 GB LVM physical volume partitions, which contains an 8 GB logical volume. The installer would not allow you to remove either of the component physical volumes, since that would leave only 5 GB in the group for an 8 GB logical volume. If you reduce the total size of any logical volumes appropriately, you may then remove a physical volume from the volume group. In the example, reducing the size of the logical volume to 4 GB would allow you to remove one of the 5 GB physical volumes.
	</div><div class="important"><h2>LVM Unavailable in Text Installs</h2><div class="para">
			LVM initial set up is not available in a text-mode installation. The installer allows you to edit pre-configured LVM volumes. If you need to create an LVM configuration from scratch, hit <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F2</strong></span> to use the terminal, and run the <code class="command">lvm</code> command. To return to the text-mode installation, hit <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F1</strong></span>.
		</div></div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-diskpartitioning-x86.html"><strong>Prev</strong>7.21.Â Partitioning Your System</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch07s21s03.html"><strong>Next</strong>7.21.3.Â Partition Fields</a></li></ul></body></html>


--- NEW FILE s2-diskpartrecommend-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.21.4.Â Recommended Partitioning Scheme</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-diskpartitioning-x86.html" title="7.21.Â Partitioning Your System" /><link rel="prev" href="ch07s21s03.html" title="7.21.3.Â Partition Fields" /><link rel="next" href="ch07s21s05.html" title="7.21.5.Â Adding Partitions" /></head><body class="draft "><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><ul
  class="docnav"><li class="previous"><a accesskey="p" href="ch07s21s03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch07s21s05.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-diskpartrecommend-x86">7.21.4.Â Recommended Partitioning Scheme</h3></div></div></div><a id="id855854" class="indexterm"></a><a id="id844929" class="indexterm"></a><a id="id902780" class="indexterm"></a><a id="id867330" class="indexterm"></a><a id="id868213" class="indexterm"></a><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="id804382">7.21.4.1.Â x86, AMD64, and <span class="trademark">Intel</span>Â® 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 <span class="trademark">Intel</span>Â® 64 systems</em></span>:
	</div><div class="itemizedlist"><ul><li><div class="para">
				A <code class="systemitem">swap</code> partition
			</div></li><li><div class="para">
				A <code class="filename">/boot</code> partition
			</div></li><li><div class="para">
				A <code class="filename">/</code> partition
			</div></li></ul></div><div class="itemizedlist"><ul><li><div class="formalpara"><h5 class="formalpara" id="id972444">A swap partition (at least 256 MB)</h5>
			Swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing. In addition, certain power management features store all of the memory for a suspended system in the available swap partitions.
		</div><div class="para">
		If you are unsure about what size swap partition to create, make it twice the amount of RAM on your machine. It must be of type swap.
	</div><div class="para">
		Creation of the proper amount of swap space varies depending on a number of factors including the following (in descending order of importance):
	</div><div class="itemizedlist"><ul><li><div class="para">
				The applications running on the machine.
			</div></li><li><div class="para">
				The amount of physical RAM installed on the machine.
			</div></li><li><div class="para">
				The version of the OS.
			</div></li></ul></div><div class="para">
		Swap should equal 2x physical RAM for up to 2 GB of physical RAM, and then an additional 1x physical RAM for any amount above 2 GB, but never less than 32 MB.
	</div><div class="para">
		So, if:
	</div><div class="para">
		M = Amount of RAM in GB, and S = Amount of swap in GB, then
	</div><pre class="screen">If M < 2
	S = M *2
Else
	S = M + 2
</pre><div class="para">
		Using this formula, a system with 2 GB of physical RAM would have 4 GB of swap, while one with 3 GB of physical RAM would have 5 GB of swap. Creating a large swap space partition can be especially helpful if you plan to upgrade your RAM at a later time.
	</div><div class="para">
		For systems with really large amounts of RAM (more than 32 GB) you can likely get away with a smaller swap partition (around 1x, or less, of physical RAM).
	</div></li><li><div class="formalpara"><h5 class="formalpara" id="id899282">A <code class="filename">/boot/</code> partition (100 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. Due to limitations, creating a native ext3 partition to hold these files is required. For most users, a 100 MB boot partition is sufficient.
	</div><div class="important"><h2>ext4 and Btrfs</h2><div class="para">
					The <span class="application"><strong>GRUB</strong></span> bootloader does not support the ext4 or Btrfs file systems. You cannot use an ext4 or Btrfs partition for /boot/.
				</div></div><div class="note"><h2>Note</h2><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 class="note"><h2>Note</h2><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></li><li><div class="formalpara"><h5 class="formalpara" id="id837620">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"><h2>Root and /root</h2><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></li></ul></div><div class="para">
		Many systems have more partitions than the minimum listed above. Choose partitions based on your particular system needs. For example, consider creating a separate <code class="filename">/home</code> partition on systems that store user data. Refer to <a class="xref" href="s2-diskpartrecommend-x86.html#sn-partitioning-advice" title="7.21.4.1.1.Â Advice on Partitions">SectionÂ 7.21.4.1.1, â€œAdvice on Partitionsâ€</a> for more information.
	</div><div class="para">
		If you create many partitions instead of one large <code class="filename">/</code> partition, upgrades become easier. Refer to the description the Edit option in <a class="xref" href="s2-diskpartitioning-dd-x86.html" title="7.21.2.Â The partitioning screen">SectionÂ 7.21.2, â€œThe partitioning screenâ€</a> for more information.
	</div><div class="para">
		The following table summarizes minimum partition sizes for the partitions containing the listed directories. You <span class="emphasis"><em>do not</em></span> have to make a separate partition for each of these directories. For instance, if the partition containing <code class="filename">/foo</code> must be at least 500 MB, and you do not make a separate <code class="filename">/foo</code> partition, then the <code class="filename">/</code> (root) partition must be at least 500 MB.
	</div><div class="table" id="tb-Minumum_partition_sizes"><div class="table-contents"><table summary="Minimum partition sizes" border="1"><colgroup><col /><col /></colgroup><thead><tr><th align="left">
						Directory
					</th><th align="left">
						Minimum size
					</th></tr></thead><tbody><tr><td align="left">
						<code class="filename">/</code>
					</td><td align="left">
						250 MB
					</td></tr><tr><td align="left">
						<code class="filename">/usr</code>
					</td><td align="left">
						250 MB, but avoid placing this on a separate partition
					</td></tr><tr><td align="left">
						<code class="filename">/tmp</code>
					</td><td align="left">
						50 MB
					</td></tr><tr><td align="left">
						<code class="filename">/var</code>
					</td><td align="left">
						384 MB
					</td></tr><tr><td align="left">
						<code class="filename">/home</code>
					</td><td align="left">
						100 MB
					</td></tr><tr><td align="left">
						<code class="filename">/boot</code>
					</td><td align="left">
						75 MB
					</td></tr></tbody></table></div><h6>TableÂ 7.3.Â Minimum partition sizes</h6></div><br class="table-break" /><div class="note"><h2>Leave Excess Capacity Unallocated</h2><div class="para">
			Only assign storage capacity to those partitions you require immediately. You may allocate free space at any time, to meet needs as they occur. To learn about a more flexible method for storage management, refer to <a class="xref" href="sn-partitioning-lvm.html" title="AppendixÂ D.Â Understanding LVM">AppendixÂ D, <i>Understanding LVM</i></a>.
		</div></div><div class="para">
		If you are not sure how best to configure the partitions for your computer, accept the default partition layout.
	</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h5 class="title" id="sn-partitioning-advice">7.21.4.1.1.Â Advice on Partitions</h5></div></div></div><div class="para">
		Optimal partition setup depends on the usage for the Linux system in question. The following tips may help you decide how to allocate your disk space.
	</div><div class="itemizedlist"><ul><li><div class="para">
				If you expect that you or other users will store data on the system, create a separate partition for the <code class="filename">/home</code> directory within a volume group. With a separate <code class="filename">/home</code> partition, you may upgrade or reinstall Fedora without erasing user data files.
			</div></li><li><div class="para">
				Each kernel installed on your system requires approximately 10 MB on the <code class="filename">/boot</code> partition. Unless you plan to install a great many kernels, the default partition size of 100 MB for <code class="filename">/boot</code> should suffice.
			</div><div class="important"><h2>ext4 and Btrfs</h2><div class="para">
					The <span class="application"><strong>GRUB</strong></span> bootloader does not support the ext4 or Btrfs file systems. You cannot use an ext4 or btrfs partition for <code class="filename">/boot</code>.
				</div></div></li><li><div class="para">
				The <code class="filename">/var</code> directory holds content for a number of applications, including the <span class="application"><strong>Apache</strong></span> web server. It also is used to store downloaded update packages on a temporary basis. Ensure that the partition containing the <code class="filename">/var</code> directory has enough space to download pending updates and hold your other content.
			</div><div class="important"><h2>Pending Updates</h2><div class="para">
					Because Fedora is a rapidly progressing collection of software, many updates may be available late in a release cycle. You can add an update repository to the sources for installation later to minimize this issue. Refer to <a class="xref" href="s1-pkgselection-x86.html#sn-additional-repos" title="7.23.1.Â Installing from Additional Repositories">SectionÂ 7.23.1, â€œInstalling from Additional Repositoriesâ€</a> for more information.
				</div></div></li><li><div class="para">
				The <code class="filename">/usr</code> directory holds the majority of software content on a Fedora system. For an installation of the default set of software, allocate at least 4 GB of space. If you are a software developer or plan to use your Fedora system to learn software development skills, you may want to at least double this allocation.
			</div><div class="important"><h2>Do not place /usr on a separate partition</h2><div class="para">
					If <code class="filename">/usr</code> is on a separate partition from <code class="filename">/</code>, the boot process becomes much more complex, and in some situations (like installations on iSCSI drives), might not work at all.
				</div></div></li><li><div class="para">
				Consider leaving a portion of the space in an LVM volume group unallocated. This unallocated space gives you flexibility if your space requirements change but you do not wish to remove data from other partitions to reallocate storage.
			</div></li><li><div class="para">
				If you separate subdirectories into partitions, you can retain content in those subdirectories if you decide to install a new version of Fedora over your current system. For instance, if you intend to run a <span class="application"><strong>MySQL</strong></span> database in <code class="filename">/var/lib/mysql</code>, make a separate partition for that directory in case you need to reinstall later.
			</div></li></ul></div><div class="para">
		The following table is a possible partition setup for a system with a single, new 80 GB hard disk and 1 GB of RAM. Note that approximately 10 GB of the volume group is unallocated to allow for future growth.
	</div><div class="note"><h2>Example Usage</h2><div class="para">
			This setup is not optimal for all use cases.
		</div></div><div class="example" id="ex-partitioning-80g"><div class="example-contents"><div class="para">
			<div class="table" id="id834029"><div class="table-contents"><table summary="Example partition setup" border="1"><colgroup><col /><col /></colgroup><thead><tr><th align="left">
								Partition
							</th><th align="left">
								Size and type
							</th></tr></thead><tbody><tr><td align="left">
								<code class="filename">/boot</code>
							</td><td align="left">
								100 MB <code class="systemitem">ext3</code> partition
							</td></tr><tr><td align="left">
								<code class="filename">swap</code>
							</td><td align="left">
								2 GB swap
							</td></tr><tr><td align="left">
								LVM physical volume
							</td><td align="left">
								Remaining space, as one LVM volume group
							</td></tr></tbody></table></div><h6>TableÂ 7.4.Â Example partition setup</h6></div><br class="table-break" />
		</div><div class="para">
			The physical volume is assigned to the default volume group and divided into the following logical volumes:
		</div><div class="para">
			<div class="table" id="id807188"><div class="table-contents"><table summary="Example partition setup: LVM physical volume" border="1"><colgroup><col /><col /></colgroup><thead><tr><th align="left">
								Partition
							</th><th align="left">
								Size and type
							</th></tr></thead><tbody><tr><td align="left">
								<code class="filename">/</code>
							</td><td align="left">
								13 GB ext4
							</td></tr><tr><td align="left">
								<code class="filename">/var</code>
							</td><td align="left">
								4 GB ext4
							</td></tr><tr><td align="left">
								<code class="filename">/home</code>
							</td><td align="left">
								50 GB ext4
							</td></tr></tbody></table></div><h6>TableÂ 7.5.Â Example partition setup: LVM physical volume</h6></div><br class="table-break" />
		</div></div><h6>ExampleÂ 7.1.Â Example partition setup</h6></div><br class="example-break" /></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s21s03.html"><strong>Prev</strong>7.21.3.Â Partition Fields</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch07s21s05.html"><strong>Next</strong>7.21.5.Â Adding Partitions</a></li></ul></body></html>


--- NEW FILE s2-grub-configfile-commands.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.6.2.Â Configuration File Directives</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-grub-configfile.html" title="E.6.Â GRUB Menu Configuration File" /><link rel="prev" href="s1-grub-configfile.html" title="E.6.Â GRUB Menu Configuration File" /><link rel="next" href="s1-grub-runlevels.html" title="E.7.Â Changing Runlevels at Boot Time" /></head><body class="draft "><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="Doc
 umentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-grub-configfile.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-grub-runlevels.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-grub-configfile-commands">E.6.2.Â Configuration File Directives</h3></div></div></div><a id="id789148" class="indexterm"></a><div class="para">
				The following are directives commonly used in the GRUB menu configuration file:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<code class="command">chainloader <em class="replaceable"><code></path/to/file></code></em></code> â€” Loads the specified file as a chain loader. Replace <em class="replaceable"><code></path/to/file></code></em> with the absolute path to the chain loader. If the file is located on the first sector of the specified partition, use the blocklist notation, <code class="command">+1</code>.
					</div></li><li><div class="para">
						<code class="command">color <em class="replaceable"><code><normal-color></code></em> <em class="replaceable"><code><selected-color></code></em></code> â€” Allows specific colors to be used in the menu, where two colors are configured as the foreground and background. Use simple color names such as <code class="command">red/black</code>. For example:
					</div><pre class="screen">
<code class="command">color red/black green/blue</code>
</pre></li><li><div class="para">
						<code class="command">default=<em class="replaceable"><code><integer></code></em></code> â€” Replace <em class="replaceable"><code><integer></code></em> with the default entry title number to be loaded if the menu interface times out.
					</div></li><li><div class="para">
						<code class="command">fallback=<em class="replaceable"><code><integer></code></em></code> â€” Replace <em class="replaceable"><code><integer></code></em> with the entry title number to try if the first attempt fails.
					</div></li><li><div class="para">
						<code class="command">hiddenmenu</code> â€” Prevents the GRUB menu interface from being displayed, loading the <code class="command">default</code> entry when the <code class="command">timeout</code> period expires. The user can see the standard GRUB menu by pressing the <span class="keycap"><strong>Esc</strong></span> key.
					</div></li><li><div class="para">
						<code class="command">initrd <em class="replaceable"><code></path/to/initrd></code></em></code> â€” Enables users to specify an initial RAM disk to use when booting. Replace <em class="replaceable"><code></path/to/initrd></code></em> with the absolute path to the initial RAM disk.
					</div></li><li><div class="para">
						<code class="command">kernel <em class="replaceable"><code></path/to/kernel></code></em> <em class="replaceable"><code><option-1></code></em> <em class="replaceable"><code><option-N></code></em></code> â€” Specifies the kernel file to load when booting the operating system. Replace <em class="replaceable"><code></path/to/kernel></code></em> with an absolute path from the partition specified by the root directive. Multiple options can be passed to the kernel when it is loaded.
					</div></li><li><div class="para">
						<code class="command">password=<em class="replaceable"><code><password></code></em></code> â€” Prevents a user who does not know the password from editing the entries for this menu option.
					</div><div class="para">
						Optionally, it is possible to specify an alternate menu configuration file after the <code class="command">password=<em class="replaceable"><code><password></code></em></code> directive. In this case, GRUB restarts the second stage boot loader and uses the specified alternate configuration file to build the menu. If an alternate menu configuration file is left out of the command, a user who knows the password is allowed to edit the current configuration file.
					</div><div class="para">
						For more information about securing GRUB, refer to the chapter titled <em class="citetitle">Workstation Security</em> in the <em class="citetitle">Red Hat Enterprise Linux Deployment Guide</em>.
					</div></li><li><div class="para">
						<code class="command">root (<em class="replaceable"><code><device-type></code></em><em class="replaceable"><code><device-number></code></em>,<em class="replaceable"><code><partition></code></em>)</code> â€” Configures the root partition for GRUB, such as <code class="command">(hd0,0)</code>, and mounts the partition.
					</div></li><li><div class="para">
						<code class="command">rootnoverify (<em class="replaceable"><code><device-type></code></em><em class="replaceable"><code><device-number></code></em>,<em class="replaceable"><code><partition></code></em>)</code> â€” Configures the root partition for GRUB, just like the <code class="command">root</code> command, but does not mount the partition.
					</div></li><li><div class="para">
						<code class="command">timeout=<em class="replaceable"><code><integer></code></em></code> â€” Specifies the interval, in seconds, that GRUB waits before loading the entry designated in the <code class="command">default</code> command.
					</div></li><li><div class="para">
						<code class="command">splashimage=<em class="replaceable"><code><path-to-image></code></em></code> â€” Specifies the location of the splash screen image to be used when GRUB boots.
					</div></li><li><div class="para">
						<code class="command">title <em class="replaceable"><code>group-title</code></em></code> â€” Specifies a title to be used with a particular group of commands used to load a kernel or operating system.
					</div></li></ul></div><div class="para">
				To add human-readable comments to the menu configuration file, begin the line with the hash mark character (<code class="command">#</code>).
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-grub-configfile.html"><strong>Prev</strong>E.6.Â GRUB Menu Configuration File</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-grub-runlevels.html"><strong>Next</strong>E.7.Â Changing Runlevels at Boot Time</a></li></ul></body></html>


--- NEW FILE s2-grub-related-books.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.8.3.Â Related Books</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-grub-additional-resources.html" title="E.8.Â Additional Resources" /><link rel="prev" href="s2-grub-useful-websites.html" title="E.8.2.Â Useful Websites" /><link rel="next" href="ch-boot-init-shutdown.html" title="AppendixÂ F.Â Boot Process, Init, and Shutdown" /></head><body class="draft "><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="Documentat
 ion Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-grub-useful-websites.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-boot-init-shutdown.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-grub-related-books">E.8.3.Â Related Books</h3></div></div></div><a id="id903559" class="indexterm"></a><div class="itemizedlist"><ul><li><div class="para">
						<em class="citetitle">Red Hat Enterprise Linux Deployment Guide</em>; Red Hat, Inc. â€” The <em class="citetitle">Workstation Security</em> chapter explains, in a concise manner, how to secure the GRUB boot loader.
					</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-grub-useful-websites.html"><strong>Prev</strong>E.8.2.Â Useful Websites</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-boot-init-shutdown.html"><strong>Next</strong>AppendixÂ F.Â Boot Process, Init, and Shutdown</a></li></ul></body></html>


--- NEW FILE s2-grub-terminology-files.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.3.2.Â File Names and Blocklists</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-grub-terminology.html" title="E.3.Â GRUB Terminology" /><link rel="prev" href="s1-grub-terminology.html" title="E.3.Â GRUB Terminology" /><link rel="next" href="s2-grub-terminology-rootfs.html" title="E.3.3.Â The Root File System and GRUB" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-grub-terminology.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-grub-terminology-rootfs.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-grub-terminology-files">E.3.2.Â File Names and Blocklists</h3></div></div></div><a id="id789826" class="indexterm"></a><div class="para">
				When typing commands to GRUB that reference a file, such as a menu list, it is necessary to specify an absolute file path immediately after the device and partition numbers.
			</div><div class="para">
				The following illustrates the structure of such a command:
			</div><div class="para">
				<code class="command"> (<em class="replaceable"><code><device-type><device-number></code></em>,<em class="replaceable"><code><partition-number></code></em>)<em class="replaceable"><code></path/to/file></code></em> </code>
			</div><div class="para">
				In this example, replace <em class="replaceable"><code><device-type></code></em> with <code class="command">hd</code>, <code class="command">fd</code>, or <code class="command">nd</code>. Replace <em class="replaceable"><code><device-number></code></em> with the integer for the device. Replace <em class="replaceable"><code></path/to/file></code></em> with an absolute path relative to the top-level of the device.
			</div><div class="para">
				It is also possible to specify files to GRUB that do not actually appear in the file system, such as a chain loader that appears in the first few blocks of a partition. To load such files, provide a <em class="firstterm">blocklist</em> that specifies block by block where the file is located in the partition. Since a file is often comprised of several different sets of blocks, blocklists use a special syntax. Each block containing the file is specified by an offset number of blocks, followed by the number of blocks from that offset point. Block offsets are listed sequentially in a comma-delimited list.
			</div><div class="para">
				The following is a sample blocklist:
			</div><pre class="screen">
<code class="command">0+50,100+25,200+1</code>
</pre><div class="para">
				This sample blocklist specifies a file that starts at the first block on the partition and uses blocks 0 through 49, 100 through 124, and 200.
			</div><div class="para">
				Knowing how to write blocklists is useful when using GRUB to load operating systems which require chain loading. It is possible to leave off the offset number of blocks if starting at block 0. As an example, the chain loading file in the first partition of the first hard drive would have the following name:
			</div><pre class="screen">
<code class="command">(hd0,0)+1</code>
</pre><div class="para">
				The following shows the <code class="command">chainloader</code> command with a similar blocklist designation at the GRUB command line after setting the correct device and partition as root:
			</div><pre class="screen">
<code class="command">chainloader +1</code>
</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-grub-terminology.html"><strong>Prev</strong>E.3.Â GRUB Terminology</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-grub-terminology-rootfs.html"><strong>Next</strong>E.3.3.Â The Root File System and GRUB</a></li></ul></body></html>


--- NEW FILE s2-grub-terminology-rootfs.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.3.3.Â The Root File System and GRUB</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-grub-terminology.html" title="E.3.Â GRUB Terminology" /><link rel="prev" href="s2-grub-terminology-files.html" title="E.3.2.Â File Names and Blocklists" /><link rel="next" href="s1-grub-interfaces.html" title="E.4.Â GRUB Interfaces" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-grub-terminology-files.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-grub-interfaces.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-grub-terminology-rootfs">E.3.3.Â The Root File System and GRUB</h3></div></div></div><a id="id845341" class="indexterm"></a><div class="para">
				The use of the term <span class="emphasis"><em>root file system</em></span> has a different meaning in regard to GRUB. It is important to remember that GRUB's root file system has nothing to do with the Linux root file system.
			</div><div class="para">
				The GRUB root file system is the top level of the specified device. For example, the image file <code class="command">(hd0,0)/grub/splash.xpm.gz</code> is located within the <code class="filename">/grub/</code> directory at the top-level (or root) of the <code class="command">(hd0,0)</code> partition (which is actually the <code class="filename">/boot/</code> partition for the system).
			</div><div class="para">
				Next, the <code class="command">kernel</code> command is executed with the location of the kernel file as an option. Once the Linux kernel boots, it sets up the root file system that Linux users are familiar with. The original GRUB root file system and its mounts are forgotten; they only existed to boot the kernel file.
			</div><div class="para">
				Refer to the <code class="command">root</code> and <code class="command">kernel</code> commands in <a class="xref" href="s1-grub-commands.html" title="E.5.Â GRUB Commands">SectionÂ E.5, â€œGRUB Commandsâ€</a> for more information.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-grub-terminology-files.html"><strong>Prev</strong>E.3.2.Â File Names and Blocklists</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-grub-interfaces.html"><strong>Next</strong>E.4.Â GRUB Interfaces</a></li></ul></body></html>


--- NEW FILE s2-grub-useful-websites.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.8.2.Â Useful Websites</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-grub-additional-resources.html" title="E.8.Â Additional Resources" /><link rel="prev" href="s1-grub-additional-resources.html" title="E.8.Â Additional Resources" /><link rel="next" href="s2-grub-related-books.html" title="E.8.3.Â Related Books" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-grub-additional-resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-grub-related-books.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-grub-useful-websites">E.8.2.Â Useful Websites</h3></div></div></div><a id="id834800" class="indexterm"></a><div class="itemizedlist"><ul><li><div class="para">
						<a href="http://www.gnu.org/software/grub">http://www.gnu.org/software/grub/</a> â€” The home page of the GNU GRUB project. This site contains information concerning the state of GRUB development and an FAQ.
					</div></li><li><div class="para">
						<a href="http://kbase.redhat.com/faq/docs/DOC-6864">http://kbase.redhat.com/faq/docs/DOC-6864</a> â€” Details booting operating systems other than Linux.
					</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-grub-additional-resources.html"><strong>Prev</strong>E.8.Â Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-grub-related-books.html"><strong>Next</strong>E.8.3.Â Related Books</a></li></ul></body></html>


--- NEW FILE s2-kickstart2-networkbased.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.8.2.Â Making the Kickstart File Available on the Network</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-kickstart2-putkickstarthere.html" title="13.8.Â Making the Kickstart File Available" /><link rel="prev" href="s1-kickstart2-putkickstarthere.html" title="13.8.Â Making the Kickstart File Available" /><link rel="next" href="s1-kickstart2-install-tree.html" title="13.9.Â Making the Installation Tree Available" /></head><body class="draft "><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://do
 cs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kickstart2-putkickstarthere.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-kickstart2-install-tree.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-kickstart2-networkbased">13.8.2.Â Making the Kickstart File Available on the Network</h3></div></div></div><a id="id793884" class="indexterm"></a><a id="id818694" class="indexterm"></a><div class="para">
				Network installations using kickstart are quite common, because system administrators can easily automate the installation on many networked computers quickly and painlessly. 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">
				To perform a network-based kickstart installation, you must have a BOOTP/DHCP server on your network, and it must include configuration information for the machine on which you are attempting to install Fedora. The BOOTP/DHCP server provides the client with its networking information as well as the location of the kickstart file.
			</div><div class="para">
				If a kickstart file is specified by the BOOTP/DHCP server, the client system attempts an NFS mount of the file's path, and copies the specified file to the client, using it as the kickstart file. The exact settings required vary depending on the BOOTP/DHCP server you use.
			</div><div class="para">
				Here is an example of a line from the <code class="filename">dhcpd.conf</code> file for the DHCP server:
			</div><pre class="screen"><code class="filename">filename</code> <em class="replaceable"><code>"/usr/new-machine/kickstart/"</code></em>; next-server <em class="replaceable"><code>blarg.redhat.com;</code></em>
</pre><div class="para">
				Note that you should replace the value after <code class="computeroutput">filename</code> with the name of the kickstart file (or the directory in which the kickstart file resides) and the value after <code class="computeroutput">next-server</code> with the NFS server name.
			</div><div class="para">
				If the file name returned by the BOOTP/DHCP server ends with a slash ("/"), then it is interpreted as a path only. In this case, the client system mounts that path using NFS, and searches for a particular file. The file name the client searches for is:
			</div><pre class="screen"><code class="filename"><em class="replaceable"><code><ip-addr></code></em>-kickstart</code>
</pre><div class="para">
				The <code class="filename"><em class="replaceable"><code><ip-addr></code></em></code> section of the file name should be replaced with the client's IP address in dotted decimal notation. For example, the file name for a computer with an IP address of 10.10.0.1 would be <code class="filename">10.10.0.1-kickstart</code>.
			</div><div class="para">
				Note that if you do not specify a server name, then the client system attempts to use the server that answered the BOOTP/DHCP request as its NFS server. If you do not specify a path or file name, the client system tries to mount <code class="filename">/kickstart</code> from the BOOTP/DHCP server and tries to find the kickstart file using the same <code class="filename"><em class="replaceable"><code><ip-addr></code></em>-kickstart</code> file name as described above.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kickstart2-putkickstarthere.html"><strong>Prev</strong>13.8.Â Making the Kickstart File Available</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-kickstart2-install-tree.html"><strong>Next</strong>13.9.Â Making the Installation Tree Available</a></li></ul></body></html>


--- NEW FILE s2-netboot-custom-msg.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.5.6.Â Adding a Custom Boot Message</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="sn-pxe-server-manual.html" title="11.5.Â Manually configure a PXE server" /><link rel="prev" href="ch11s05s05.html" title="11.5.5.Â Configuring the DHCP Server" /><link rel="next" href="netboot-performing.html" title="11.5.7.Â Performing the PXE Installation" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s05s05.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="netboot-performing.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-netboot-custom-msg">11.5.6.Â Adding a Custom Boot Message</h3></div></div></div><a id="id841998" 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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s05s05.html"><strong>Prev</strong>11.5.5.Â Configuring the DHCP Server</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="netboot-performing.html"><strong>Next</strong>11.5.7.Â Performing the PXE Installation</a></li></ul></body></html>


--- NEW FILE s2-redhat-config-kickstart-interpreter.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.11.2.Â Use an Interpreter</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-redhat-config-kickstart-postinstall.html" title="14.11.Â Post-Installation Script" /><link rel="prev" href="s1-redhat-config-kickstart-postinstall.html" title="14.11.Â Post-Installation Script" /><link rel="next" href="s1-redhat-config-kickstart-savefile.html" title="14.12.Â Saving the File" /></head><body class="draft "><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/i
 mages/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-redhat-config-kickstart-postinstall.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-redhat-config-kickstart-savefile.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-redhat-config-kickstart-interpreter">14.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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-redhat-config-kickstart-postinstall.html"><strong>Prev</strong>14.11.Â Post-Installation Script</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-redhat-config-kickstart-savefile.html"><strong>Next</strong>14.12.Â Saving the File</a></li></ul></body></html>


--- NEW FILE s2-steps-make-cd.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.4.2.Â Making an Installation Boot CD-ROM</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch03s04.html" title="3.4.Â Can You Install Using the CD-ROM or DVD?" /><link rel="prev" href="ch03s04.html" title="3.4.Â Can You Install Using the CD-ROM or DVD?" /><link rel="next" href="s1-steps-network-installs-x86.html" title="3.5.Â Preparing for a Network Installation" /></head><body class="draft "><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/i
 mage_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s04.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-steps-network-installs-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-steps-make-cd">3.4.2.Â Making an Installation Boot CD-ROM</h3></div></div></div><a id="id828158" class="indexterm"></a><a id="id795186" class="indexterm"></a><a id="id836000" class="indexterm"></a><div class="para">
			The <code class="filename">images/</code> directory on the installation DVD contains the <code class="filename">boot.iso</code> file. This file is an image of a disc that you can burn to a CD and use to boot the installation program. To use this boot CD, your computer must be able to boot from its CD-ROM drive, and its BIOS settings must be configured to do so.
		</div><div class="important"><h2>Choose an option to burn a CD from an image</h2><div class="para">
				When you burn the <code class="filename">boot.iso</code> image, make sure that you select the option to <code class="literal">burn an image file to disc</code> in your CD burning software. The exact wording of this option varies, depending on the software that you use, but should contain the word "image". Note that not all CD burning software includes this option. In particular, the CD burning software built into Microsoft Windows XP and Windows Vista does not offer this capability. There are many programs available that add this capability to Windows operating systems; <span class="application"><strong>Infrarecorder</strong></span> is a free and open-source example available from <a href="http://www.infrarecorder.org/">http://www.infrarecorder.org/</a>.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s04.html"><strong>Prev</strong>3.4.Â Can You Install Using the CD-ROM or DVD?</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-steps-network-installs-x86.html"><strong>Next</strong>3.5.Â Preparing for a Network Installation</a></li></ul></body></html>


--- NEW FILE s2-trouble-completeparts-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.3.5.Â Other Partitioning Problems</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-trouble-install-x86.html" title="8.3.Â Trouble During the Installation" /><link rel="prev" href="s2-trouble-space-x86.html" title="8.3.4.Â Using Remaining Space" /><link rel="next" href="ch08s03s06.html" title="8.3.6.Â Are You Seeing Python Errors?" /></head><body class="draft "><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="Document
 ation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-trouble-space-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch08s03s06.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-trouble-completeparts-x86">8.3.5.Â Other Partitioning Problems</h3></div></div></div><a id="id825624" 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:
</div><div class="itemizedlist"><ul><li><div class="para">
		A <code class="filename">/</code> (root) partition
	</div></li><li><div class="para">
		A <swap> partition of type swap
	</div></li></ul></div><div class="note"><h2>Note</h2><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-trouble-space-x86.html"><strong>Prev</strong>8.3.4.Â Using Remaining Space</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch08s03s06.html"><strong>Next</strong>8.3.6.Â Are You Seeing Python Errors?</a></li></ul></body></html>


--- NEW FILE s2-trouble-part-tables-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.3.3.Â Trouble with Partition Tables</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-trouble-install-x86.html" title="8.3.Â Trouble During the Installation" /><link rel="prev" href="s2-trouble-tracebacks-x86.html" title="8.3.2.Â Saving traceback messages without removeable media" /><link rel="next" href="s2-trouble-space-x86.html" title="8.3.4.Â Using Remaining Space" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-trouble-tracebacks-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-trouble-space-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-trouble-part-tables-x86">8.3.3.Â Trouble with Partition Tables</h3></div></div></div><a id="id871034" class="indexterm"></a><a id="id941401" 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.html" title="7.18.Â Disk Partitioning Setup">SectionÂ 7.18, â€œDisk Partitioning Setupâ€</a>) phase of the installation saying something similar to
		</div><div class="para">
	<span class="guilabel"><strong>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.</strong></span>
</div><div class="para">
	you may not have a partition table on that drive or the partition table on the drive may not be recognizable by the partitioning software used in the installation program.
</div><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-trouble-tracebacks-x86.html"><strong>Prev</strong>8.3.2.Â Saving traceback messages without removeab...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-trouble-space-x86.html"><strong>Next</strong>8.3.4.Â Using Remaining Space</a></li></ul></body></html>


--- NEW FILE s2-trouble-ram.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.4.6.Â Is Your RAM Not Being Recognized?</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch08s04.html" title="8.4.Â Problems After Installation" /><link rel="prev" href="ch08s04s05.html" title="8.4.5.Â Problems When You Try to Log In" /><link rel="next" href="ch08s04s07.html" title="8.4.7.Â Your Printer Does Not Work" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s04s05.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch08s04s07.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-trouble-ram">8.4.6.Â Is Your RAM Not Being Recognized?</h3></div></div></div><a id="id808478" 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>:
	</div><pre class="screen">
<strong class="userinput"><code>mem=<em class="replaceable"><code>xx</code></em>M</code></strong>
</pre><div class="para">
		Replace <em class="replaceable"><code>xx</code></em> with the amount of RAM you have in megabytes.
	</div><div class="para">
		In <code class="filename">/boot/grub/grub.conf</code>, the above example would look similar to the following:
	</div><pre class="screen">
# NOTICE: You have a /boot partition. This means that 
#  all kernel paths are relative to /boot/ 
default=0 
timeout=30 
splashimage=(hd0,0)/grub/splash.xpm.gz 
 title Fedora (2.6.27.19-170.2.35.fc10.i686)
root (hd0,1)
kernel /vmlinuz-2.6.27.19-170.2.35.fc10.i686 ro root=UUID=04a07c13-e6bf-6d5a-b207-002689545705 mem=1024M
initrd /initrd-2.6.27.19-170.2.35.fc10.i686.img
</pre><div class="para">
		Once you reboot, the changes made to <code class="filename">grub.conf</code> are reflected on your system.
	</div><div class="para">
		Once you have loaded the GRUB boot screen, type <code class="command">e</code> for edit. You are presented with a list of items in the configuration file for the boot label you have selected.
	</div><div class="para">
		Choose the line that starts with <code class="computeroutput">kernel</code> and type <code class="command">e</code> to edit this boot entry.
	</div><div class="para">
		At the end of the <code class="computeroutput">kernel</code> line, add
	</div><pre class="screen">
<strong class="userinput"><code>mem=<em class="replaceable"><code>xx</code></em>M</code></strong>
</pre><div class="para">
		where <em class="replaceable"><code>xx</code></em> equals the amount of RAM in your system.
	</div><div class="para">
		Press <span class="keycap"><strong>Enter</strong></span> to exit edit mode.
	</div><div class="para">
		Once the boot loader screen has returned, type <code class="command">b</code> to boot the system.
	</div><div class="para">
		Itanium users must enter boot commands with <code class="command">elilo</code> followed by the boot command.
	</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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s04s05.html"><strong>Prev</strong>8.4.5.Â Problems When You Try to Log In</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch08s04s07.html"><strong>Next</strong>8.4.7.Â Your Printer Does Not Work</a></li></ul></body></html>


--- NEW FILE s2-trouble-sound.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.4.8.Â Problems with Sound Configuration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch08s04.html" title="8.4.Â Problems After Installation" /><link rel="prev" href="ch08s04s07.html" title="8.4.7.Â Your Printer Does Not Work" /><link rel="next" href="ch08s04s09.html" title="8.4.9.Â Apache-based httpd service/Sendmail Hangs During Startup" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s04s07.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch08s04s09.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-trouble-sound">8.4.8.Â Problems with Sound Configuration</h3></div></div></div><a id="id800304" class="indexterm"></a><div class="para">
		If, for some reason, you do not hear sound and know that you do have a sound card installed, you can run the <span class="application"><strong>Sound Card Configuration Tool</strong></span> (<code class="command">system-config-soundcard</code>) utility.
	</div><div class="para">
		To use the <span class="application"><strong>Sound Card Configuration Tool</strong></span>, choose <span class="guimenu"><strong>Main Menu</strong></span> => <span class="guimenuitem"><strong>System </strong></span> => <span class="guimenuitem"><strong>Administration </strong></span> => <span class="guimenuitem"><strong>Soundcard Detection</strong></span> in GNOME, or <span class="guimenu"><strong>Main Menu</strong></span> => <span class="guimenuitem"><strong>Computer </strong></span> => <span class="guimenuitem"><strong>System Settings</strong></span> => <span class="guimenuitem"><strong>Multimedia</strong></span> in KDE. A small text box pops up prompting you for your root password.
	</div><div class="para">
		You can also type the <code class="command">system-config-soundcard</code> command at a shell prompt to launch the <span class="application"><strong>Sound Card Configuration Tool</strong></span>. If you are not root, it prompts you for the root password to continue.
	</div><div class="para">
		If the <span class="application"><strong>Sound Card Configuration Tool</strong></span> does not work (if the sample does not play and you still do not have audio sounds), it is likely that your sound card is not yet supported in Fedora.
	</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s04s07.html"><strong>Prev</strong>8.4.7.Â Your Printer Does Not Work</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch08s04s09.html"><strong>Next</strong>8.4.9.Â Apache-based httpd service/Sendmail Hangs ...</a></li></ul></body></html>


--- NEW FILE s2-trouble-space-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.3.4.Â Using Remaining Space</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-trouble-install-x86.html" title="8.3.Â Trouble During the Installation" /><link rel="prev" href="s2-trouble-part-tables-x86.html" title="8.3.3.Â Trouble with Partition Tables" /><link rel="next" href="s2-trouble-completeparts-x86.html" title="8.3.5.Â Other Partitioning Problems" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-trouble-part-tables-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-trouble-completeparts-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-trouble-space-x86">8.3.4.Â Using Remaining Space</h3></div></div></div><a id="id933387" 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><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-trouble-part-tables-x86.html"><strong>Prev</strong>8.3.3.Â Trouble with Partition Tables</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-trouble-completeparts-x86.html"><strong>Next</strong>8.3.5.Â Other Partitioning Problems</a></li></ul></body></html>


--- NEW FILE s2-trouble-tracebacks-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.3.2.Â Saving traceback messages without removeable media</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-trouble-install-x86.html" title="8.3.Â Trouble During the Installation" /><link rel="prev" href="s1-trouble-install-x86.html" title="8.3.Â Trouble During the Installation" /><link rel="next" href="s2-trouble-part-tables-x86.html" title="8.3.3.Â Trouble with Partition Tables" /></head><body class="draft "><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="Com
 mon_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-trouble-install-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-trouble-part-tables-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-trouble-tracebacks-x86">8.3.2.Â Saving traceback messages without removeable media</h3></div></div></div><a id="id908444" class="indexterm"></a><a id="id834874" class="indexterm"></a><a id="id888207" class="indexterm"></a><div class="para">
	If you receive a traceback error message during installation, you can usually save it to removeable media, for example a USB flash drive or a floppy disk.
</div><div class="para">
	If you do not have removeable media available on your system, you can <code class="command">scp</code> the error message to a remote system.
</div><div class="para">
	When the traceback dialog appears, the traceback error message is automatically written to a file named <code class="filename">/tmp/anacdump.txt</code>. Once the dialog appears, switch over to a new tty (virtual console) by pressing the keys <code class="command"><span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F2</strong></span></code> and <code class="command">scp</code> the message written to <code class="filename">/tmp/anacdump.txt</code> to a known working remote system.
</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-trouble-install-x86.html"><strong>Prev</strong>8.3.Â Trouble During the Installation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-trouble-part-tables-x86.html"><strong>Next</strong>8.3.3.Â Trouble with Partition Tables</a></li></ul></body></html>


--- NEW FILE s2-x86-bootloader-alt.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.22.3.Â Alternative Boot Loaders</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-x86-bootloader.html" title="7.22.Â x86, AMD64, and Intel 64 Boot Loader Configuration" /><link rel="prev" href="s2-x86-bootloader-rescue.html" title="7.22.2.Â Rescue Mode" /><link rel="next" href="s1-pkgselection-x86.html" title="7.23.Â Package Group Selection" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-x86-bootloader-rescue.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-pkgselection-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-x86-bootloader-alt">7.22.3.Â Alternative Boot Loaders</h3></div></div></div><a id="id873630" 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>, <span class="application"><strong>Acronis Disk Director Suite</strong></span>, and <span class="application"><strong>Apple Boot Camp</strong></span>.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-x86-bootloader-rescue.html"><strong>Prev</strong>7.22.2.Â Rescue Mode</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-pkgselection-x86.html"><strong>Next</strong>7.23.Â Package Group Selection</a></li></ul></body></html>


--- NEW FILE s2-x86-bootloader-rescue.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.22.2.Â Rescue Mode</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-x86-bootloader.html" title="7.22.Â x86, AMD64, and Intel 64 Boot Loader Configuration" /><link rel="prev" href="s1-x86-bootloader.html" title="7.22.Â x86, AMD64, and Intel 64 Boot Loader Configuration" /><link rel="next" href="s2-x86-bootloader-alt.html" title="7.22.3.Â Alternative Boot Loaders" /></head><body class="draft "><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/image
 s/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-x86-bootloader.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-x86-bootloader-alt.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-x86-bootloader-rescue">7.22.2.Â Rescue Mode</h3></div></div></div><a id="id849282" 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><div class="para">
					Using the CD-ROM to boot an x86, AMD64, or <span class="trademark">Intel</span>Â® 64 system, type <strong class="userinput"><code>linux rescue</code></strong> at the installation boot prompt. 
				</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-x86-bootloader.html"><strong>Prev</strong>7.22.Â x86, AMD64, and Intel 64 Boot Loader Config...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-x86-bootloader-alt.html"><strong>Next</strong>7.22.3.Â Alternative Boot Loaders</a></li></ul></body></html>


--- NEW FILE s2-x86-starting-bootopts.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.2.Â Additional Boot Options</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-x86-starting.html" title="7.3.Â Starting the Installation Program" /><link rel="prev" href="s1-x86-starting.html" title="7.3.Â Starting the Installation Program" /><link rel="next" href="s1-installmethod.html" title="7.4.Â Selecting an Installation Method" /></head><body class="draft "><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="Docum
 entation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-x86-starting.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-installmethod.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s2-x86-starting-bootopts">7.3.2.Â Additional Boot Options</h3></div></div></div><a id="id791309" class="indexterm"></a><div class="para">
			While it is easiest to boot using a CD-ROM or 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 <span class="trademark">Intel</span>Â® 64 system, use the instructions as provided in the boot loader option samples below.
		</div><div class="note"><h2>Note</h2><div class="para">
				Refer to <a class="xref" href="ap-admin-options.html" title="ChapterÂ 9.Â Boot Options">ChapterÂ 9, <i>Boot Options</i></a> for additional boot options not covered in this section.
			</div></div><div class="itemizedlist"><ul><li><div class="para">
					<a id="id804186" class="indexterm"></a>
					<a id="id869622" 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><div class="para">
					<a id="id908775" class="indexterm"></a>
					<a id="id795606" class="indexterm"></a>
					<a id="id847648" class="indexterm"></a>
					 ISO images have an md5sum 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 CD 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 CD and does not have to be performed in a specific order (for example, CD #1 does not have to be the first CD you verify). It is strongly recommended to perform this operation on any Fedora CD that was created from downloaded ISO images. This command works with the CD, DVD, hard drive ISO, and NFS ISO installation methods.
				</div></li><li><div class="para">
					<a id="id817219" class="indexterm"></a>
					<a id="id869598" class="indexterm"></a>
					 Also in the <code class="filename">images/</code> directory is the <code class="filename">boot.iso</code> file. This file is an ISO image than can be used to boot the installation program. To use the <code class="filename">boot.iso</code>, your computer must be able to boot from its CD-ROM drive, and its BIOS settings must be configured to do so. You must then burn the <code class="filename">boot.iso</code> file onto a recordable/rewriteable CD-ROM.
				</div></li><li><div class="para">
					<a id="id839035" class="indexterm"></a>
					<a id="id790247" class="indexterm"></a>
					<a id="id827746" class="indexterm"></a>
					<a id="id884604" 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">
					For text mode installations, use:
				</div><pre class="screen">
<strong class="userinput"><code>linux text console=<em class="replaceable"><code><device></code></em></code></strong>
</pre><div class="para">
					In the above command, <em class="replaceable"><code><device></code></em> should be the device you are using (such as ttyS0 or ttyS1). For example, <code class="command">linux text console=ttyS0</code>.
				</div><div class="para">
					Text mode installations using a serial terminal work best when the terminal supports UTF-8. Under UNIX and Linux, Kermit supports UTF-8. For Windows, Kermit '95 works well. Non-UTF-8 capable terminals works as long as only English is used during the installation process. An enhanced serial display can be used by passing the <code class="command">utf8</code> command as a boot-time option to the installation program. For example:
				</div><pre class="screen">
<code class="command">linux console=ttyS0 utf8</code>
</pre></li></ul></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="s3-x86-starting-kernelopts">7.3.2.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 floppy disk enter:
			</div><a id="id831293" 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">
<strong class="userinput"><code>linux text updates</code></strong>
</pre><div class="para">
				This command will prompt you to insert a floppy diskette containing updates for anaconda. It is not needed if you are performing a network installation and have already placed the updates image contents in <code class="command">rhupdates/</code> on the server.
			</div><div class="para">
				After entering any options, press <span class="keycap"><strong>Enter</strong></span> to boot using those options.
			</div><div class="para">
				If you need to specify boot options to identify your hardware, please write them down. The boot options are needed during the boot loader configuration portion of the installation (refer to <a class="xref" href="s1-x86-bootloader.html" title="7.22.Â x86, AMD64, and Intel 64 Boot Loader Configuration">SectionÂ 7.22, â€œx86, AMD64, and Intel 64 Boot Loader Configurationâ€</a> for more information).
			</div><div class="para">
				For more information on kernel options refer to <a class="xref" href="ap-admin-options.html" title="ChapterÂ 9.Â Boot Options">ChapterÂ 9, <i>Boot Options</i></a>.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-x86-starting.html"><strong>Prev</strong>7.3.Â Starting the Installation Program</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-installmethod.html"><strong>Next</strong>7.4.Â Selecting an Installation Method</a></li></ul></body></html>


--- NEW FILE sn-Is_Your_Hardware_Compatible-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2.Â Is Your Hardware Compatible?</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-steps-x86.html" title="ChapterÂ 3.Â Steps to Get You Started" /><link rel="prev" href="ch-steps-x86.html" title="ChapterÂ 3.Â Steps to Get You Started" /><link rel="next" href="ch03s03.html" title="3.3.Â Do You Have Enough Disk Space?" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-steps-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch03s03.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-Is_Your_Hardware_Compatible-x86">3.2.Â Is Your Hardware Compatible?</h2></div></div></div><a id="id813868" class="indexterm"></a><a id="id806067" 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 11 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 11, available at <a href="http://docs.fedoraproject.org/release-notes">http://docs.fedoraproject.org/release-notes</a> .
	</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-steps-x86.html"><strong>Prev</strong>ChapterÂ 3.Â Steps to Get You Started</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch03s03.html"><strong>Next</strong>3.3.Â Do You Have Enough Disk Space?</a></li></ul></body></html>


--- NEW FILE sn-Production_methods.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.2.Â Production methods</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-Contributors_and_production_methods.html" title="AppendixÂ H.Â Contributors and production methods" /><link rel="prev" href="ch-Contributors_and_production_methods.html" title="AppendixÂ H.Â Contributors and production methods" /><link rel="next" href="appe-Publican-Revision_History.html" title="AppendixÂ I.Â Revision History" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Contributors_and_production_methods.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="appe-Publican-Revision_History.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-Production_methods">H.2.Â Production methods</h2></div></div></div><div class="para">
			Writers produce the Install Guide directly in DocBook XML in a revision control repository. They collaborate with other subject matter experts during the beta release phase of Fedora to explain the installation process. The editorial team ensures consistency and quality of the finished guide. At this point, the team of translators produces other language versions of the release notes, and then they become available to the general public as part of Fedora. The publication team also makes the guide, and subsequent errata, available via the Web.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Contributors_and_production_methods.html"><strong>Prev</strong>AppendixÂ H.Â Contributors and production methods</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="appe-Publican-Revision_History.html"><strong>Next</strong>AppendixÂ I.Â Revision History</a></li></ul></body></html>


--- NEW FILE sn-about-document.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.Â About This Document</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-introduction.html" title="Introduction" /><link rel="prev" href="ch-introduction.html" title="Introduction" /><link rel="next" href="sn-audience.html" title="2.2.Â Audience" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-
 introduction.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-audience.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-about-document">2.Â About This Document</h2></div></div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-goals">2.1.Â Goals</h3></div></div></div><div class="para">
				This guide helps a reader:
			</div><div class="orderedlist"><ol><li><div class="para">
						Understand how to locate the Fedora distribution online
					</div></li><li><div class="para">
						Create configuration data that allows a computer to boot Fedora
					</div></li><li><div class="para">
						Understand and interact with the Fedora installation program
					</div></li><li><div class="para">
						Complete basic post-installation configuration of a Fedora system
					</div></li></ol></div><div class="note"><h2>Other Sources of Documentation</h2><div class="para">
					This guide does not cover use of Fedora. To learn how to use an installed Fedora system, refer to <a href="http://docs.fedoraproject.org/">http://docs.fedoraproject.org/</a> for other documentation.
				</div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-introduction.html"><strong>Prev</strong>Introduction</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-audience.html"><strong>Next</strong>2.2.Â Audience</a></li></ul></body></html>


--- NEW FILE sn-account_configuration.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.17.Â Set the Root Password</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="s1-timezone-x86.html" title="7.16.Â Time Zone Configuration" /><link rel="next" href="s1-diskpartsetup-x86.html" title="7.18.Â Disk Partitioning Setup" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-timezone-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-diskpartsetup-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-account_configuration">7.17.Â Set the Root Password</h2></div></div></div><a id="id849270" class="indexterm"></a><a id="id864364" class="indexterm"></a><div class="para">
		Setting up a root account and password is one of the most important steps during your installation. Your root account is similar to the administrator account used on Microsoft Windows machines. 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"><h2>Note</h2><div class="para">
			The root user (also known as the superuser) has complete access to the entire system; for this reason, logging in as the root user is best done <span class="emphasis"><em>only</em></span> to perform system maintenance or administration.
		</div></div><div class="figure" id="id838224"><div class="figure-contents"><div class="mediaobject"><img src="images/accountconfig/rootpassword.png" alt="Root Password" /><div class="longdesc"><div class="para">
					Setting your root password.
				</div></div></div></div><h6>FigureÂ 7.14.Â Root Password</h6></div><br class="figure-break" /><div class="para">
		Use the root account only for system administration. Create a non-root account for your general use and <code class="command">su -</code> to root when you need to fix something quickly. These basic rules minimize the chances of a typo or an incorrect command doing damage to your system.
	</div><div class="note"><h2>Note</h2><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 class="para">
		The installation program prompts you to set a root password<sup>[<a id="id909112" href="#ftn.id909112" 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">
		You should make the root password something you can remember, but not something that is easy for someone else to guess. Your name, your phone number, <em class="firstterm">qwerty</em>, <em class="firstterm">password, root</em>, <em class="firstterm">123456</em>, and <em class="firstterm">anteater</em> are all examples of bad passwords. Good passwords mix numerals with upper and lower case letters and do not contain dictionary words: <em class="firstterm">Aard387vark</em> or <em class="firstterm">420BMttNT</em>, for example. Remember that the password is case-sensitive. If you write down your password, keep it in a secure place. However, it is recommended that you do not write down this or any password you create.
	</div><div class="note"><h2>Note</h2><div class="para">
			Do not use one of the example passwords offered in this manual. Using one of these passwords could be considered a security risk.
		</div></div><div class="note"><h2>Note</h2><div class="para">
			To change your root password after you have completed the installation, use the <span class="application"><strong>Root Password Tool</strong></span>.
		</div><div class="para">
			Type the <code class="command">system-config-rootpassword</code> command in a shell prompt to launch the <span class="application"><strong>Root Password Tool</strong></span>. If you are not root, it prompts you for the root password to continue.
		</div></div><div class="para">
	 Enter the <code class="systemitem">root</code> password into the <span class="guilabel"><strong>Root Password</strong></span> field. Fedora displays the characters as asterisks for security. Type the same password into the <span class="guilabel"><strong>Confirm</strong></span> field to ensure it is set correctly. After you set the root password, select <span class="guibutton"><strong>Next</strong></span> to proceed.
</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id909112" href="#id909112" 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.
		</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-timezone-x86.html"><strong>Prev</strong>7.16.Â Time Zone Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-diskpartsetup-x86.html"><strong>Next</strong>7.18.Â Disk Partitioning Setup</a></li></ul></body></html>


--- NEW FILE sn-audience.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.Â Audience</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="sn-about-document.html" title="2.Â About This Document" /><link rel="prev" href="sn-about-document.html" title="2.Â About This Document" /><link rel="next" href="ch-experts-quickstart.html" title="ChapterÂ 1.Â Quick Start for Experts" /></head><body class="draft "><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><ul class="docnav
 "><li class="previous"><a accesskey="p" href="sn-about-document.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-experts-quickstart.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-audience">2.2.Â Audience</h3></div></div></div><div class="para">
				This guide is intended for new and intermediate Fedora users. Advanced Fedora users with questions about detailed operation of expert installation features should consult the Anaconda development mailing list at <a href="http://www.redhat.com/archives/anaconda-devel-list/">http://www.redhat.com/archives/anaconda-devel-list/</a>.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-about-document.html"><strong>Prev</strong>2.Â About This Document</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-experts-quickstart.html"><strong>Next</strong>ChapterÂ 1.Â Quick Start for Experts</a></li></ul></body></html>


--- NEW FILE sn-automating-installation.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.4.Â Automating the Installation with Kickstart</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ap-admin-options.html" title="ChapterÂ 9.Â Boot Options" /><link rel="prev" href="sn-remote-logging.html" title="9.3.Â Logging to a Remote System During the Installation" /><link rel="next" href="sn-bootoptions-hardware.html" title="9.5.Â Enhancing Hardware Support" /></head><body class="draft "><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/ima
 ge_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-remote-logging.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-bootoptions-hardware.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-automating-installation">9.4.Â Automating the Installation with Kickstart</h2></div></div></div><div class="para">
			A 
			<a id="id788380" 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"><h2>Every Installation Produces a Kickstart File</h2><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.
			</div></div><div class="para">
			Fedora includes a graphical application to create and modify Kickstart files by selecting the options that you require. Use the package <code class="filename">system-config-kickstart</code> to install this utility. To load the Fedora Kickstart editor, choose <span class="guimenu"><strong>Applications</strong></span> â†’ <span class="guisubmenu"><strong>System Tools</strong></span> â†’ <span class="guimenuitem"><strong>Kickstart</strong></span>.
		</div><div class="para">
			Kickstart files list installation settings in plain text, with one option per line. This format lets you modify your Kickstart files with any text editor, and write scripts or applications that generate custom Kickstart files for your systems.
		</div><div class="para">
			To automate the installation process with a Kickstart file, use the <code class="option">ks</code> option to specify the name and location of the file:
		</div><pre class="screen">
 <strong class="userinput"><code>linux ks=<em class="replaceable"><code>location/kickstart-file.cfg</code></em></code></strong>
</pre><div class="para">
			You may use Kickstart files that are held on either removable storage, a hard drive, or a network server. Refer to <a class="xref" href="sn-automating-installation.html#tb-kssources" title="TableÂ 9.2.Â Kickstart sources">TableÂ 9.2, â€œKickstart sourcesâ€</a> for the supported Kickstart sources.
		</div><div class="table" id="tb-kssources"><div class="table-contents"><table summary="Kickstart sources" border="1"><colgroup><col align="left" /><col align="left" /></colgroup><thead><tr><th align="left">
							Kickstart source
						</th><th align="left">
							Option format
						</th></tr></thead><tbody><tr><td align="left">
							CD or DVD drive
						</td><td align="left">
							<code class="option">ks=<em class="replaceable"><code>cdrom:/directory/ks.cfg</code></em></code>
						</td></tr><tr><td align="left">
							Hard Drive
						</td><td align="left">
							<code class="option">ks=<em class="replaceable"><code>hd:/device/directory/ks.cfg</code></em></code>
						</td></tr><tr><td align="left">
							Other Device
						</td><td align="left">
							<code class="option">ks=<em class="replaceable"><code>file:/device/directory/ks.cfg</code></em></code>
						</td></tr><tr><td align="left">
							HTTP Server
						</td><td align="left">
							<code class="option">ks=<em class="replaceable"><code>http://server.mydomain.com/directory/ks.cfg</code></em></code>
						</td></tr><tr><td align="left">
							FTP Server
						</td><td align="left">
							<code class="option">ks=<em class="replaceable"><code>ftp://server.mydomain.com/directory/ks.cfg</code></em></code>
						</td></tr><tr><td align="left">
							NFS Server
						</td><td align="left">
							<code class="option">ks=<em class="replaceable"><code>nfs:server.mydomain.com:/directory/ks.cfg</code></em></code>
						</td></tr></tbody></table></div><h6>TableÂ 9.2.Â Kickstart sources</h6></div><br class="table-break" /><div class="para">
			To obtain a Kickstart file from a script or application on a Web server, specify the URL of the application with the <code class="option">ks=</code> option. If you add the option <code class="option">kssendmac</code>, the request also sends HTTP headers to the Web application. Your application can use these headers to identify the computer. This line sends a request with headers to the application <em class="wordasword">http://server.mydomain.com/kickstart.cgi</em>:
		</div><pre class="screen">
<strong class="userinput"><code>linux ks=http://server.mydomain.com/kickstart.cgi kssendmac</code></strong>
</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-remote-logging.html"><strong>Prev</strong>9.3.Â Logging to a Remote System During the Instal...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-bootoptions-hardware.html"><strong>Next</strong>9.5.Â Enhancing Hardware Support</a></li></ul></body></html>


--- NEW FILE sn-boot-mediacheck.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.6.2.Â Verifying boot media</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="sn-boot-modes.html" title="9.6.Â Using the Maintenance Boot Modes" /><link rel="prev" href="sn-boot-modes.html" title="9.6.Â Using the Maintenance Boot Modes" /><link rel="next" href="sn-mode-rescue.html" title="9.6.3.Â Booting Your Computer with the Rescue Mode" /></head><body class="draft "><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="Docu
 mentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-boot-modes.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-mode-rescue.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-boot-mediacheck">9.6.2.Â Verifying boot media</h3></div></div></div><div class="para">
				You can test the integrity of an ISO-based installation source before using it to install Fedora. These sources include CD, DVD, and ISO images stored on a local hard drive or on an NFS server. Verifying that the ISO images are instace before you attempt an installation helps to avoid problems that are often encountered during installation.
			</div><div class="para">
				Fedora offers you three ways to test installation ISOs:
			</div><div class="itemizedlist"><ul><li><div class="para">
						select the <span class="guilabel"><strong>Verify and Boot</strong></span> option on the Fedora Live CD. To access the Live CD boot menu, press any key within ten seconds of the splash screen appearing.
					</div></li><li><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 distribution CD set or DVD
					</div></li><li><div class="para">
						boot Fedora with the option <code class="option">mediacheck</code> option.
					</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-boot-modes.html"><strong>Prev</strong>9.6.Â Using the Maintenance Boot Modes</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-mode-rescue.html"><strong>Next</strong>9.6.3.Â Booting Your Computer with the Rescue Mode</a></li></ul></body></html>


--- NEW FILE sn-boot-modes.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.6.Â Using the Maintenance Boot Modes</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ap-admin-options.html" title="ChapterÂ 9.Â Boot Options" /><link rel="prev" href="sn-bootoptions-hwdetection.html" title="9.5.2.Â Overriding Automatic Hardware Detection" /><link rel="next" href="sn-boot-mediacheck.html" title="9.6.2.Â Verifying boot media" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-bootoptions-hwdetection.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-boot-mediacheck.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-boot-modes">9.6.Â Using the Maintenance Boot Modes</h2></div></div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-memtest">9.6.1.Â Loading the Memory (RAM) Testing Mode</h3></div></div></div><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="id797193" 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">
				To halt the tests and reboot your computer, enter <span class="keycap"><strong>Esc</strong></span> at any time.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-bootoptions-hwdetection.html"><strong>Prev</strong>9.5.2.Â Overriding Automatic Hardware Detection</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-boot-mediacheck.html"><strong>Next</strong>9.6.2.Â Verifying boot media</a></li></ul></body></html>


--- NEW FILE sn-booting-from-pxe.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.4.Â Booting from the Network using PXE</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-beginninginstallation.html" title="ChapterÂ 6.Â Beginning the Installation" /><link rel="prev" href="sn-verifying-dvd.html" title="6.3.2.Â Verifying the DVD" /><link rel="next" href="sn-graphics-problem.html" title="6.5.Â Graphical and Text Interfaces" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-verifying-dvd.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-graphics-problem.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-booting-from-pxe">6.4.Â Booting from the Network using PXE</h2></div></div></div><div class="para">
			To boot with 
			<a id="id800756" 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.html" title="ChapterÂ 11.Â Setting Up an Installation Server">ChapterÂ 11, <i>Setting Up an Installation Server</i></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.
		</div><div class="para">
			To boot a computer from a PXE server:
		</div><div class="procedure"><ol class="1"><li><div class="para">
					Ensure that the network cable is attached. The link indicator light on the network socket should be lit, even if the computer is not switched on.
				</div></li><li><div class="para">
					Switch on the computer.
				</div></li><li><div class="para">
					A menu screen appears. Press the number key that corresponds to the desired option.
				</div></li></ol></div><div class="note"><h2>PXE Troubleshooting</h2><div class="para">
				If your PC does not boot from the netboot server, ensure that the BIOS is configured to boot first from the correct network interface. Some BIOS systems specify the network interface as a possible boot device, but do not support the PXE standard. Refer to your hardware documentation for more information.
			</div></div><div class="note"><h2>Multiple NICs and PXE installation </h2><div class="para">
				Some servers with multiple network interfaces may not assign eth0 to the first network interface as BIOS knows it, which can cause the installer to try using a different network interface than was used by PXE. To change this behavior, use the following in <code class="filename">pxelinux.cfg/*</code> config files:
			</div><div class="para">
				<code class="option">IPAPPEND 2</code>
			</div><div class="para">
				<code class="option">APPEND ksdevice=bootif</code>
			</div><div class="para">
				The configuration options above causes the installer to use the same network interface as BIOS and PXE use. You can also use the following option:
			</div><div class="para">
				<code class="option">ksdevice=link</code>
			</div><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-verifying-dvd.html"><strong>Prev</strong>6.3.2.Â Verifying the DVD</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-graphics-problem.html"><strong>Next</strong>6.5.Â Graphical and Text Interfaces</a></li></ul></body></html>


--- NEW FILE sn-bootoptions-hardware.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.5.Â Enhancing Hardware Support</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ap-admin-options.html" title="ChapterÂ 9.Â Boot Options" /><link rel="prev" href="sn-automating-installation.html" title="9.4.Â Automating the Installation with Kickstart" /><link rel="next" href="sn-bootoptions-hwdetection.html" title="9.5.2.Â Overriding Automatic Hardware Detection" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-automating-installation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-bootoptions-hwdetection.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-bootoptions-hardware">9.5.Â Enhancing Hardware Support</h2></div></div></div><div class="para">
			By default, Fedora attempts to automatically detect and configure support for all of the components of your computer. Fedora supports the majority of hardware in common use with the software <em class="firstterm">drivers</em> that are included with the operating system. To support other devices you may supply additional drivers during the installation process, or at a later time.
		</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-bootoptions-driverdisks">9.5.1.Â Adding Hardware Support with Driver Disks</h3></div></div></div><div class="para">
				The installation system can load drivers from disks, pen drives, or network servers to configure support for new devices. After the installation is complete, remove any driver disks and store them for later use.
			</div><div class="para">
				Hardware manufacturers may supply 
				<a id="id872859" class="indexterm"></a>
				 driver disks for Fedora with the device, or provide image files to prepare the disks. To obtain the latest drivers, download the correct file from the website of the manufacturer.
			</div><div class="note"><h2>Driver Disks Supplied as Zipped Files</h2><div class="para">
					Driver disk images may be distributed as compressed archives, or zip files. For identification, the names of zip files include the extensions <code class="filename">.zip</code>, or <code class="filename">.tar.gz</code>. To extract the contents of a zipped file with a Fedora system, choose <span class="guimenu"><strong>Applications</strong></span> â†’ <span class="guisubmenu"><strong>Accessories</strong></span> â†’ <span class="guimenuitem"><strong>Archive Manager</strong></span>.
				</div></div><div class="para">
				To format a disk or pen drive with an image file, use the <code class="command">dd</code> utility. For example, to prepare a diskette with the image file <code class="filename">drivers.img</code>, enter this command in a terminal window:
			</div><pre class="screen">
 <strong class="userinput"><code>dd if=drivers.img of=/dev/fd0</code></strong>
</pre><div class="para">
				To use a driver disk in the installation process, specify the <code class="option">dd</code> option at the <code class="prompt">boot:</code> prompt:
			</div><pre class="screen">
 <strong class="userinput"><code>linux dd</code></strong>
</pre><div class="para">
				Note that the <code class="option">dd</code> option is interchangeable with the <code class="option">driverdisk</code> option.
			</div><div class="para">
				When prompted, select <span class="guibutton"><strong>Yes</strong></span> to provide a driver disk. Choose the drive that holds the driver disk from the list on the <span class="guilabel"><strong>Driver Disk Source</strong></span> text screen.
			</div><div class="para">
				The installation system can also read drivers from disk images that are held on network servers. Refer to <a class="xref" href="sn-bootoptions-hardware.html#tb-driversources" title="TableÂ 9.3.Â Driver disk image sources">TableÂ 9.3, â€œDriver disk image sourcesâ€</a> for the supported sources of driver disk image files.
			</div><div class="table" id="tb-driversources"><div class="table-contents"><table summary="Driver disk image sources" border="1"><colgroup><col align="left" /><col align="left" /></colgroup><thead><tr><th align="left">
								Image source
							</th><th align="left">
								Option format
							</th></tr></thead><tbody><tr><td align="left">
								Select a drive or device
							</td><td align="left">
								<code class="option">dd</code>
							</td></tr><tr><td align="left">
								HTTP Server
							</td><td align="left">
								<code class="option">dd=<em class="replaceable"><code>http://server.mydomain.com/directory/drivers.img</code></em></code>
							</td></tr><tr><td align="left">
								FTP Server
							</td><td align="left">
								<code class="option">dd=<em class="replaceable"><code>ftp://server.mydomain.com/directory/drivers.img</code></em></code>
							</td></tr><tr><td align="left">
								NFS Server
							</td><td align="left">
								<code class="option">dd=<em class="replaceable"><code>nfs:server.mydomain.com:/directory/drivers.img</code></em></code>
							</td></tr></tbody></table></div><h6>TableÂ 9.3.Â Driver disk image sources</h6></div><br class="table-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-automating-installation.html"><strong>Prev</strong>9.4.Â Automating the Installation with Kickstart</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-bootoptions-hwdetection.html"><strong>Next</strong>9.5.2.Â Overriding Automatic Hardware Detection</a></li></ul></body></html>


--- NEW FILE sn-bootoptions-hwdetection.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.5.2.Â Overriding Automatic Hardware Detection</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="sn-bootoptions-hardware.html" title="9.5.Â Enhancing Hardware Support" /><link rel="prev" href="sn-bootoptions-hardware.html" title="9.5.Â Enhancing Hardware Support" /><link rel="next" href="sn-boot-modes.html" title="9.6.Â Using the Maintenance Boot Modes" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-bootoptions-hardware.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-boot-modes.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-bootoptions-hwdetection">9.5.2.Â Overriding Automatic Hardware Detection</h3></div></div></div><div class="para">
				For some models of device automatic hardware configuration may fail, or cause instability. In these cases, you may need to disable automatic configuration for that type of device, and take additional steps to manually configure the device after the installation process is complete.
			</div><div class="note"><h2>Check the Release Notes</h2><div class="para">
					Refer to the Release Notes for information on known issues with specific devices.
				</div></div><div class="para">
				To override the automatic hardware detection, use one or more of the following options:
			</div><div class="table" id="tb-hardwareoptions"><div class="table-contents"><table summary="Hardware Options" border="1"><colgroup><col align="left" /><col align="left" /></colgroup><thead><tr><th align="left">
								Compatibility
							</th><th align="left">
								Option
							</th></tr></thead><tbody><tr><td align="left">
								Disable all hardware detection
							</td><td align="left">
								<code class="option">noprobe</code>
							</td></tr><tr><td align="left">
								Disable graphics, keyboard, and mouse detection
							</td><td align="left">
								<code class="option">headless</code>
							</td></tr><tr><td align="left">
								Disable passing keyboard and mouse information to stage 2 of the installation program
							</td><td align="left">
								<code class="option">nopass</code>
							</td></tr><tr><td align="left">
								Use basic VESA driver for video
							</td><td align="left">
								<code class="option">xdriver=vesa</code>
							</td></tr><tr><td align="left">
								Disable shell access on virtual console 2 during installation
							</td><td align="left">
								<code class="option">noshell</code>
							</td></tr><tr><td align="left">
								Disable advanced configuration and power interface (ACPI)
							</td><td align="left">
								<code class="option">acpi=off</code>
							</td></tr><tr><td align="left">
								Disable machine check exception (MCE) CPU self-diagnosis.
							</td><td align="left">
								<code class="option">nomce</code>
							</td></tr><tr><td align="left">
								Disable non-uniform menory access on the AMD64 architecture
							</td><td align="left">
								<code class="option">numa-off</code>
							</td></tr><tr><td align="left">
								Force kernel to detect a specific amount of memory, where <em class="replaceable"><code>xxx</code></em> is a value in megabytes
							</td><td align="left">
								<code class="option">mem=<em class="replaceable"><code>xxx</code></em>m</code>
							</td></tr><tr><td align="left">
								Enable DMA only for IDE and SATA drives
							</td><td align="left">
								<code class="option">libata.dma=1</code>
							</td></tr><tr><td align="left">
								Disable BIOS-assisted RAID
							</td><td align="left">
								<code class="option">nodmraid</code>
							</td></tr><tr><td align="left">
								Disable Firewire device detection
							</td><td align="left">
								<code class="option">nofirewire</code>
							</td></tr><tr><td align="left">
								Disable parallel port detection
							</td><td align="left">
								<code class="option">noparport</code>
							</td></tr><tr><td align="left">
								Disable PC Card (PCMCIA) device detection
							</td><td align="left">
								<code class="option">nopcmcia</code>
							</td></tr><tr><td align="left">
								Disable USB storage device detection
							</td><td align="left">
								<code class="option">nousbstorage</code>
							</td></tr><tr><td align="left">
								Disable all USB device detection
							</td><td align="left">
								<code class="option">nousb</code>
							</td></tr><tr><td align="left">
								Disable all probing of network hardware
							</td><td align="left">
								<code class="option">nonet</code>
							</td></tr></tbody></table></div><h6>TableÂ 9.4.Â Hardware Options</h6></div><br class="table-break" /><div class="note"><h2>Additional Screen</h2><div class="para">
					The <code class="option">isa</code> option causes the system to display an additional text screen at the beginning of the installation process. Use this screen to configure the ISA devices on your computer.
				</div></div><div class="important"><h2>Important</h2><div class="para">
					Other kernel boot options have no particular meaning for <span class="application"><strong>anaconda</strong></span> and do not affect the installation process. However, if you use these options to boot the installation system, <span class="application"><strong>anaconda</strong></span> will preserve them in the bootloader configuration.
				</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-bootoptions-hardware.html"><strong>Prev</strong>9.5.Â Enhancing Hardware Support</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-boot-modes.html"><strong>Next</strong>9.6.Â Using the Maintenance Boot Modes</a></li></ul></body></html>


--- NEW FILE sn-cannot-download.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.Â What If I Cannot Download Fedora?</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-new-users.html" title="ChapterÂ 2.Â New Users" /><link rel="prev" href="ch02s04s02s02.html" title="2.4.2.2.Â USB Image Creation in Linux" /><link rel="next" href="sn-start-installation.html" title="2.6.Â How Do I Start the Installation Program?" /></head><body class="draft "><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="Document
 ation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch02s04s02s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-start-installation.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-cannot-download">2.5.Â What If I Cannot Download Fedora?</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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch02s04s02s02.html"><strong>Prev</strong>2.4.2.2.Â USB Image Creation in Linux</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-start-installation.html"><strong>Next</strong>2.6.Â How Do I Start the Installation Program?</a></li></ul></body></html>


--- NEW FILE sn-cobbler-import.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.4.Â Importing the Distribution</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ap-install-server.html" title="ChapterÂ 11.Â Setting Up an Installation Server" /><link rel="prev" href="sn-cobbler-mirror.html" title="11.3.Â Mirroring a Network Location" /><link rel="next" href="sn-pxe-server-manual.html" title="11.5.Â Manually configure a PXE server" /></head><body class="draft "><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.p
 ng" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-cobbler-mirror.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-pxe-server-manual.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-cobbler-import">11.4.Â Importing the Distribution</h2></div></div></div><div class="para">
			To offer a distribution through more than one installation method, perform additional <code class="command">cobbler import</code> tasks using a different name for each method. For best results, use the installation method as part of the name, so it appears in the client's boot menu.
		</div><div class="procedure"><ol class="1"><li><div class="para">
					To import the DVD disc or ISO distribution into <code class="command">cobbler</code>, run this command:
				</div><pre class="screen"><code class="command">cobbler import --path=/mnt/dvd --name=<em class="replaceable"><code>distro_name</code></em></code>
</pre><div class="para">
					For <em class="replaceable"><code>distro_name</code></em>, substitute a meaningful name for the distribution.
				</div><div class="para">
					To import a local or remote network distribution into <code class="command">cobbler</code>, run this command. Replace <em class="replaceable"><code>network_URI</code></em> with the URI you found in <a class="xref" href="sn-cobbler-mirror.html" title="11.3.Â Mirroring a Network Location">SectionÂ 11.3, â€œMirroring a Network Locationâ€</a>, and <em class="replaceable"><code>distro_name</code></em> as above:
				</div><pre class="screen"><code class="command">cobbler import --mirror=<em class="replaceable"><code>network_URI</code></em> --name=<em class="replaceable"><code>distro_name</code></em></code>
</pre><div class="important"><h2>Importing a Source</h2><div class="para">
						When <code class="command">cobbler</code> imports a distribution with the commands above, it copies all the files to the server's local storage, which may take some time.
					</div></div><div class="para">
					If you do not want to make local copies of the distribution because clients can already reach its location, use the <code class="option">--available-as</code> option.
				</div><pre class="screen"><code class="command">cobbler import --path=/mnt/dvd --name=<em class="replaceable"><code>distro_name</code></em> --available-as=<em class="replaceable"><code>network_URI</code></em></code>
<code class="command">cobbler import --mirror=<em class="replaceable"><code>network_URI</code></em> --name=<em class="replaceable"><code>distro_name</code></em> --available-as=<em class="replaceable"><code>network_URI</code></em></code>
</pre><div class="para">
					For <em class="replaceable"><code>nework_URI</code></em>, substitute the appropriate network location of the distribution. This URI indicates how the server makes the distribution available to its clients. The examples above assume that your <code class="command">cobbler</code> server reaches the mirror location at the same URI as the clients. If not, substitute an appropriate URI for the <code class="option">--mirror</code> option. The following examples are URI locations that work if you have been following the procedures in this section, and your server's IP address is <code class="systemitem">192.168.1.1</code>:
				</div><div class="itemizedlist"><ul><li><div class="para">
							<code class="uri">nfs://<em class="replaceable"><code>192.168.1.1</code></em>:/mnt/dvd</code>
						</div></li><li><div class="para">
							<code class="uri">http://<em class="replaceable"><code>192.168.1.1</code></em>:/distro</code>
						</div></li></ul></div><div class="para">
					If necessary, replace <em class="replaceable"><code>192.168.1.1</code></em> with the IP address for your <code class="command">cobbler</code> server.
				</div></li><li><div class="para">
					Run the command <code class="command">cobbler sync</code> to apply the changes. To check that your <code class="command">cobbler</code> server is listening on the correct ports, use the <code class="command">netstat -lp</code> command.
				</div><div class="important"><h2>Firewall Considerations</h2><div class="para">
						Depending on your server's configuration, you may need to use the <code class="command">system-config-securitylevel</code> command to permit access to some or all of these network services:
					</div><div class="itemizedlist"><ul><li><div class="para">
								67 or bootps, for the DHCP/BOOTP server
							</div></li><li><div class="para">
								69 or tftp, for providing the PXE loader
							</div></li><li><div class="para">
								80 or http, if the <code class="command">cobbler</code> server is to provide HTTP installation service
							</div></li><li><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><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></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-cobbler-mirror.html"><strong>Prev</strong>11.3.Â Mirroring a Network Location</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-pxe-server-manual.html"><strong>Next</strong>11.5.Â Manually configure a PXE server</a></li></ul></body></html>


--- NEW FILE sn-cobbler-mirror.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.3.Â Mirroring a Network Location</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ap-install-server.html" title="ChapterÂ 11.Â Setting Up an Installation Server" /><link rel="prev" href="sn-cobbler-setup-distro.html" title="11.2.Â Setting Up the Distribution" /><link rel="next" href="sn-cobbler-import.html" title="11.4.Â Importing the Distribution" /></head><body class="draft "><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.pn
 g" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-cobbler-setup-distro.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-cobbler-import.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-cobbler-mirror">11.3.Â Mirroring a Network Location</h2></div></div></div><div class="para">
			If you do not have discs or ISO images for a distribution, you can use <code class="command">cobbler</code> to create an installation server. The <code class="command">cobbler</code> command can fetch the distribution over the network as part of the import process.
		</div><div class="para">
			Locate the distribution on the network. The location may be on the local network or reached at a remote site via FTP, HTTP, or rsync protocols. Note the URI, which will be in one of the following forms:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<code class="uri">http://mirror.example.com/pub/fedora/linux/releases/11/Fedora/<em class="replaceable"><code>arch</code></em>/os</code>
				</div></li><li><div class="para">
					<code class="uri">ftp://mirror.example.com/pub/fedora/linux/releases/11/Fedora/<em class="replaceable"><code>arch</code></em>/os</code>
				</div></li><li><div class="para">
					<code class="uri">rsync://mirror.example.com/fedora/linux/releases/11/Fedora/<em class="replaceable"><code>arch</code></em>/os</code>
				</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-cobbler-setup-distro.html"><strong>Prev</strong>11.2.Â Setting Up the Distribution</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-cobbler-import.html"><strong>Next</strong>11.4.Â Importing the Distribution</a></li></ul></body></html>


--- NEW FILE sn-cobbler-setup-distro.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.2.Â Setting Up the Distribution</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ap-install-server.html" title="ChapterÂ 11.Â Setting Up an Installation Server" /><link rel="prev" href="ap-install-server.html" title="ChapterÂ 11.Â Setting Up an Installation Server" /><link rel="next" href="sn-cobbler-mirror.html" title="11.3.Â Mirroring a Network Location" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ap-install-server.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-cobbler-mirror.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-cobbler-setup-distro">11.2.Â Setting Up the Distribution</h2></div></div></div><div class="para">
			To set up a distribution from a full Fedora DVD or ISO image, use this procedure.
		</div><div class="note"><h2>Network Locations</h2><div class="para">
				To create a local mirror from an existing network source, skip this section and refer instead to <a class="xref" href="sn-cobbler-mirror.html" title="11.3.Â Mirroring a Network Location">SectionÂ 11.3, â€œMirroring a Network Locationâ€</a>.
			</div></div><div class="procedure"><ol class="1"><li><div class="para">
					If you are using a DVD disc or ISO image, Create a directory mount point:
				</div><pre class="screen"><code class="command">mkdir /mnt/dvd</code>
</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><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:
				</div><pre class="screen"><code class="command">/sbin/service rpcbind start /sbin/service nfs start</code>
</pre></li><li><div class="para">
					To support HTTP installation, use <code class="command">yum</code> to install the Apache web server if it is not already installed:
				</div><pre class="screen"><code class="command">yum -y install httpd</code>
</pre><div class="para">
					Make a link to the mounted disc in the Apache public content area:
				</div><pre class="screen"><code class="command">ln -s /mnt/dvd /var/www/html/<em class="replaceable"><code>distro</code></em></code>
</pre></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ap-install-server.html"><strong>Prev</strong>ChapterÂ 11.Â Setting Up an Installation Server</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-cobbler-mirror.html"><strong>Next</strong>11.3.Â Mirroring a Network Location</a></li></ul></body></html>


--- NEW FILE sn-community.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.6.Â Joining the Fedora Community</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-next-steps.html" title="ChapterÂ 16.Â Your Next Steps" /><link rel="prev" href="sn-web-help.html" title="16.5.Â Finding Documentation and Support" /><link rel="next" href="ap-rescuemode.html" title="ChapterÂ 17.Â Basic System Recovery" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-web-help.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ap-rescuemode.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-community">16.6.Â Joining the Fedora Community</h2></div></div></div><div class="para">
			The Fedora Project is driven by the individuals that contribute to it. Community members provide support and documentation to other users, help to improve the software included in Fedora by testing, and develop new software alongside the programmers employed by Red Hat. The results of this work are available to all.
		</div><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-web-help.html"><strong>Prev</strong>16.5.Â Finding Documentation and Support</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ap-rescuemode.html"><strong>Next</strong>ChapterÂ 17.Â Basic System Recovery</a></li></ul></body></html>


--- NEW FILE sn-expert-download.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.Â Download Files</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-experts-quickstart.html" title="ChapterÂ 1.Â Quick Start for Experts" /><link rel="prev" href="ch-experts-quickstart.html" title="ChapterÂ 1.Â Quick Start for Experts" /><link rel="next" href="sn-expert-prepare.html" title="1.3.Â Prepare for Installation" /></head><body class="draft "><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 Sit
 e" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-experts-quickstart.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-expert-prepare.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-expert-download">1.2.Â Download Files</h2></div></div></div><div class="para">
			Do any one of the following:
		</div><div class="note"><h2>Verify your downloads</h2><div class="para">
				Downloads may fail for any number of reasons. Always verify the sha1sum of the downloaded files.
			</div></div><div class="orderedlist"><ol><li><a id="id797537" 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><div class="para">
					Download the ISO images for the full distribution on CD or DVD. Create CD or DVD media from the ISO files using your preferred application, or put the images on a Windows FAT32 or Linux ext2/ext3 partition.
				</div></li><li><div class="para">
					Download the <code class="filename">boot.iso</code> image for a minimal boot CD or USB flash drive. Write the image to the approriate physical media to create bootable media. The boot media contains no packages but must be pointed at a hard disk or online repository to complete the installation.
				</div></li><li><div class="para">
					Download the <code class="filename">netinst.iso</code> image for a reduced-size boot CD. Write the image to the appropriate physical media to create bootable media.
				</div></li><li><div class="para">
					Download the <code class="filename">vmlinuz</code> kernel file and the <code class="filename">initrd.img</code> ramdisk image from the distribution's <code class="filename">isolinux/</code> directory. Configure your operating system to boot the kernel and load the ramdisk image. For further information on installation without media, refer to <a class="xref" href="ap-medialess-install.html" title="ChapterÂ 10.Â Installing Without Media">ChapterÂ 10, <i>Installing Without Media</i></a>.
				</div><div class="para">
					For information on setting up a network boot server from which you can install Fedora, refer to <a class="xref" href="ap-install-server.html" title="ChapterÂ 11.Â Setting Up an Installation Server">ChapterÂ 11, <i>Setting Up an Installation Server</i></a>.
				</div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-experts-quickstart.html"><strong>Prev</strong>ChapterÂ 1.Â Quick Start for Experts</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-expert-prepare.html"><strong>Next</strong>1.3.Â Prepare for Installation</a></li></ul></body></html>


--- NEW FILE sn-expert-install.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.4.Â Install Fedora</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-experts-quickstart.html" title="ChapterÂ 1.Â Quick Start for Experts" /><link rel="prev" href="sn-expert-prepare.html" title="1.3.Â Prepare for Installation" /><link rel="next" href="sn-expert-post-install.html" title="1.5.Â Perform Post-installation Steps" /></head><body class="draft "><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 S
 ite" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-expert-prepare.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-expert-post-install.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-expert-install">1.4.Â Install Fedora</h2></div></div></div><div class="para">
			Boot from the desired media, with any options appropriate for your hardware and installation mode. Refer to <a class="xref" href="ap-admin-options.html" title="ChapterÂ 9.Â Boot Options">ChapterÂ 9, <i>Boot Options</i></a> for more information about boot options. If you boot from the Live CD, select the "Install to Hard Disk" option from the desktop to run the installation program. If you boot from minimal media or a downloaded kernel, select a network or hard disk resource from which to install.
		</div><div class="para">
			Proceed through all the steps of the installation program. The installation program does not change your system until you make a final confirmation to proceed. When installation is finished, reboot your system.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-expert-prepare.html"><strong>Prev</strong>1.3.Â Prepare for Installation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-expert-post-install.html"><strong>Next</strong>1.5.Â Perform Post-installation Steps</a></li></ul></body></html>


--- NEW FILE sn-expert-post-install.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.5.Â Perform Post-installation Steps</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-experts-quickstart.html" title="ChapterÂ 1.Â Quick Start for Experts" /><link rel="prev" href="sn-expert-install.html" title="1.4.Â Install Fedora" /><link rel="next" href="ch-new-users.html" title="ChapterÂ 2.Â New Users" /></head><body class="draft "><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><ul
  class="docnav"><li class="previous"><a accesskey="p" href="sn-expert-install.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-new-users.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-expert-post-install">1.5.Â Perform Post-installation Steps</h2></div></div></div><div class="para">
			After the system reboots, it displays additional configuration options. Make appropriate changes to your system and proceed to the login prompt.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-expert-install.html"><strong>Prev</strong>1.4.Â Install Fedora</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-new-users.html"><strong>Next</strong>ChapterÂ 2.Â New Users</a></li></ul></body></html>


--- NEW FILE sn-expert-prepare.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.Â Prepare for Installation</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-experts-quickstart.html" title="ChapterÂ 1.Â Quick Start for Experts" /><link rel="prev" href="sn-expert-download.html" title="1.2.Â Download Files" /><link rel="next" href="sn-expert-install.html" title="1.4.Â Install Fedora" /></head><body class="draft "><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><ul cl
 ass="docnav"><li class="previous"><a accesskey="p" href="sn-expert-download.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-expert-install.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-expert-prepare">1.3.Â Prepare for Installation</h2></div></div></div><a id="id811883" class="indexterm"></a><div class="para">
			Back up any user data you need to preserve.
		</div><div class="note"><h2>Resizing Partitions</h2><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.html" title="7.21.Â Partitioning Your System">SectionÂ 7.21, â€œPartitioning Your Systemâ€</a> for more information.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-expert-download.html"><strong>Prev</strong>1.2.Â Download Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-expert-install.html"><strong>Next</strong>1.4.Â Install Fedora</a></li></ul></body></html>


--- NEW FILE sn-finishing-upgrade.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.2.Â Finishing an Upgrade</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-next-steps.html" title="ChapterÂ 16.Â Your Next Steps" /><link rel="prev" href="ch-next-steps.html" title="ChapterÂ 16.Â Your Next Steps" /><link rel="next" href="sn-switching-to-gui-login.html" title="16.3.Â Switching to a Graphical Login" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-next-steps.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-switching-to-gui-login.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-finishing-upgrade">16.2.Â Finishing an Upgrade</h2></div></div></div><div class="important"><h2>System Updates Recommended</h2><div class="para">
				Once you have rebooted your system after performing an upgrade, you should also perform a manual system update. Consult <a class="xref" href="ch-next-steps.html#sn-system-updating" title="16.1.Â Updating Your System">SectionÂ 16.1, â€œUpdating Your Systemâ€</a> for more information.
			</div></div><div class="para">
			If you chose to upgrade your system from a previous release rather than perform a fresh installation, you may want to examine the differences in the package set. <a class="xref" href="sn-upgrade-tree.html" title="7.14.2.Â Upgrading Using the Installer">SectionÂ 7.14.2, â€œUpgrading Using the Installerâ€</a> advised you to create a package listing for your original system. You can now use that listing to determine how to bring your new system close to the original system state.
		</div><div class="para">
			Most software repository configurations are stored in packages that end with the term <code class="literal">release</code>. Check the old package list for the repositories that were installed:
		</div><pre class="screen"><code class="command">awk '{print $1}' ~/old-pkglist.txt | grep 'release$'</code>
</pre><div class="para">
			If necessary, retrieve and install these software repository packages from their original sources on the Internet. Follow the instructions at the originating site to install the repository configuration packages for use by <code class="command">yum</code> and other software management tools on your Fedora system.
		</div><div class="para">
			Then run the following commands to make a list of other missing software packages:
		</div><pre class="screen"><code class="command">awk '{print $1}' ~/old-pkglist.txt | sort | uniq > ~/old-pkgnames.txt</code>
<code class="command">rpm -qa --qf '%{NAME}\n' | sort | uniq > ~/new-pkgnames.txt</code>
<code class="command">diff -u ~/old-pkgnames.txt ~/new-pkgnames.txt | grep '^-' | sed 's/^-//' > /tmp/pkgs-to-install.txt</code>
</pre><div class="para">
			Now use the file <code class="filename">/tmp/pkgs-to-install.txt</code> with the <code class="command">yum</code> command to restore most or all of your old software:
		</div><pre class="screen"><code class="command">su -c 'yum install `cat /tmp/pkgs-to-install.txt`'</code>
</pre><div class="important"><h2>Missing Software</h2><div class="para">
				Due to changes in package complements between Fedora releases, it is possible this method may not restore all the software on your system. You can use the routines above to again compare the software on your system, and remedy any problems you find.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-next-steps.html"><strong>Prev</strong>ChapterÂ 16.Â Your Next Steps</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-switching-to-gui-login.html"><strong>Next</strong>16.3.Â Switching to a Graphical Login</a></li></ul></body></html>


--- NEW FILE sn-firstboot-datetime.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.3.Â Date and Time</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-firstboot.html" title="ChapterÂ 15.Â Firstboot" /><link rel="prev" href="sn-firstboot-systemuser.html" title="15.2.Â System User" /><link rel="next" href="sn-smolt.html" title="15.4.Â Hardware Profile" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><
 a accesskey="p" href="sn-firstboot-systemuser.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-smolt.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-firstboot-datetime">15.3.Â Date and Time</h2></div></div></div><div class="para">
			If your system does not have Internet access or a network time server, manually set the date and time for your system on this screen. Otherwise, use 
			<a id="id965743" class="indexterm"></a>
			<em class="firstterm">NTP</em> (Network Time Protocol) servers to maintain the accuracy of the clock. NTP provides time synchronization service to computers on the same network. The Internet contains many computers that offer public NTP services.
		</div><div class="para">
			The initial display enables you to set the date and time of your system manually.
		</div><div class="figure" id="id886553"><div class="figure-contents"><div class="mediaobject"><img src="images/firstboot/fb-datetime.png" alt="Firstboot date and time screen" /><div class="longdesc"><div class="para">
						Firstboot date and time screen
					</div></div></div></div><h6>FigureÂ 15.4.Â Firstboot date and time screen</h6></div><br class="figure-break" /><div class="para">
			Select the <span class="guilabel"><strong>Network Time Protocol</strong></span> tab to configure your system to use NTP servers instead.
		</div><div class="note"><h2>Setting the Clock</h2><div class="para">
				To change these settings later, choose <span class="guimenu"><strong>System</strong></span> â†’ <span class="guisubmenu"><strong>Administration</strong></span> â†’ <span class="guimenuitem"><strong>Date & Time</strong></span>.
			</div></div><div class="para">
			To configure your system to use network time servers, select the <span class="guilabel"><strong>Enable Network Time Protocol</strong></span> option. This option disables the settings on the <span class="guilabel"><strong>Date and Time</strong></span> tab and enables the other settings on this screen.
		</div><div class="figure" id="id863959"><div class="figure-contents"><div class="mediaobject"><img src="images/firstboot/fb-ntp.png" alt="Firstboot Network Time Protocol screen" /><div class="longdesc"><div class="para">
						Firstboot Network Time Protocol screen
					</div></div></div></div><h6>FigureÂ 15.5.Â Firstboot Network Time Protocol screen</h6></div><br class="figure-break" /><div class="para">
			By default, Fedora is configured to use three separate groups, or <em class="firstterm">pools</em>, of time servers. Time server pools create redundancy, so if one time server is unavailable, your system synchronizes with another server.
		</div><div class="para">
			To use an additional time server, select <span class="guilabel"><strong>Add</strong></span>, and type the DNS name of the server into the box. To remove a server or server pool from the list, select the name and click <span class="guilabel"><strong>Delete</strong></span>.
		</div><div class="para">
			If your machine is always connected to the Internet through a wired connection, select the <span class="guilabel"><strong>Synchronize system clock before starting service</strong></span> option. This option may cause a short delay during startup but ensures accurate time on your system even if the clock is significantly wrong at boot time.
		</div><div class="important"><h2>Laptops and NTP</h2><div class="para">
				Do not use this option with laptop computers that sometimes use wireless networks.
			</div></div><div class="para">
			If the hardware clock in your computer is highly inaccurate, you may turn off your local time source entirely. To turn off the local time source, select <span class="guilabel"><strong>Show advanced options</strong></span> and then deselect the <span class="guilabel"><strong>Use Local Time Source</strong></span> option. If you turn off your local time source, the NTP servers take priority over the internal clock.
		</div><div class="para">
			If you enable the <span class="guilabel"><strong>Enable NTP Broadcast</strong></span> advanced option, Fedora attempts to automatically locate time servers on the network.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-firstboot-systemuser.html"><strong>Prev</strong>15.2.Â System User</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-smolt.html"><strong>Next</strong>15.4.Â Hardware Profile</a></li></ul></body></html>


--- NEW FILE sn-firstboot-systemuser.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.2.Â System User</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-firstboot.html" title="ChapterÂ 15.Â Firstboot" /><link rel="prev" href="ch-firstboot.html" title="ChapterÂ 15.Â Firstboot" /><link rel="next" href="sn-firstboot-datetime.html" title="15.3.Â Date and Time" /></head><body class="draft "><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><ul class="docnav"><li class="previous"
 ><a accesskey="p" href="ch-firstboot.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-firstboot-datetime.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-firstboot-systemuser">15.2.Â System User</h2></div></div></div><div class="para">
			Create a user account for yourself with this screen. Always use this account to log in to your Fedora system, rather than using the <code class="systemitem">root</code> account.
		</div><div class="figure" id="id873445"><div class="figure-contents"><div class="mediaobject"><img src="images/firstboot/fb-createuser.png" alt="Firstboot create user screen" /><div class="longdesc"><div class="para">
						Firstboot create user screen
					</div></div></div></div><h6>FigureÂ 15.3.Â Firstboot create user screen</h6></div><br class="figure-break" /><div class="para">
			Enter a user name and your full name, and then enter your chosen password. Type your password once more in the <span class="guilabel"><strong>Confirm Password</strong></span> box to ensure that it is correct. Refer to <a class="xref" href="sn-account_configuration.html" title="7.17.Â Set the Root Password">SectionÂ 7.17, â€œSet the Root Passwordâ€</a> for guidelines on selecting a secure password.
		</div><div class="note"><h2>Creating Extra User Accounts</h2><div class="para">
				To add additional user accounts to your system after the installation is complete, choose <span class="guimenu"><strong>System</strong></span> â†’ <span class="guisubmenu"><strong>Administration</strong></span> â†’ <span class="guimenuitem"><strong>Users & Groups</strong></span>.
			</div></div><div class="para">
			To configure Fedora to use network services for authentication or user information, select <span class="guibutton"><strong>Use Network Login...</strong></span>.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-firstboot.html"><strong>Prev</strong>ChapterÂ 15.Â Firstboot</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-firstboot-datetime.html"><strong>Next</strong>15.3.Â Date and Time</a></li></ul></body></html>


--- NEW FILE sn-graphics-problem.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.5.Â Graphical and Text Interfaces</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-beginninginstallation.html" title="ChapterÂ 6.Â Beginning the Installation" /><link rel="prev" href="sn-booting-from-pxe.html" title="6.4.Â Booting from the Network using PXE" /><link rel="next" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /></head><body class="draft "><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/i
 mage_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-booting-from-pxe.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-guimode-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-graphics-problem">6.5.Â Graphical and Text Interfaces</h2></div></div></div><div class="para">
			Fedora 11 supports graphical and text-based installations. However, the installer image must either fit in RAM or appear on local storage, such as the installation DVD or Live Media. Therefore, only systems with more than 192Â MB of RAM or that boot from the installation DVD or Live Media can use the graphical installer. Systems with 192Â MB RAM or less automatically scale back to using the text-based installer. Note that you must still have a minimum of 64Â MB of RAM for installation to proceed in text mode. If you prefer to use the text-based installer, type <code class="option">linux text</code> at the <code class="prompt">boot:</code> prompt.
		</div><div class="para">
			If one of the following situations occurs, the installation program uses a text mode:
		</div><div class="itemizedlist"><ul><li><div class="para">
					The installation system fails to identify the display hardware on your computer
				</div></li><li><div class="para">
					Your computer has less than 192 MB of RAM
				</div></li><li><div class="para">
					You choose the text mode installation from the boot menu
				</div></li></ul></div><div class="para">
			The text screens provide most of the same functions as the standard screens, although disk partitioning is simplified, and bootloader configuration and package selection are handled automatically in text mode. If you choose to install Fedora in text mode, you can still configure your system to use a graphical interface after installation.
		</div><div class="important"><h2>Graphical Interface Usage</h2><div class="para">
				Installing in text mode does <span class="strong strong"><strong>not</strong></span> prevent you from using a graphical interface on your system once it is installed. If you have trouble configuring your system for graphical interface use, consult other sources for troubleshooting help as shown in <a class="xref" href="ch-introduction.html#sn-additional-help" title="1.2.Â Getting Additional Help">SectionÂ 1.2, â€œGetting Additional Helpâ€</a>.
			</div></div><div class="important"><h2>Installation requires at least 64 MB of RAM</h2><div class="para">
				If your system has less than 64 MB of RAM, installation will not continue.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-booting-from-pxe.html"><strong>Prev</strong>6.4.Â Booting from the Network using PXE</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-guimode-x86.html"><strong>Next</strong>ChapterÂ 7.Â Installing on Intel and AMD Systems</a></li></ul></body></html>


--- NEW FILE sn-iSCSI_disks_during_start_up.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.2.Â iSCSI disks during start up</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ISCSI_disks.html" title="AppendixÂ B.Â ISCSI disks" /><link rel="prev" href="ISCSI_disks.html" title="AppendixÂ B.Â ISCSI disks" /><link rel="next" href="Disk_Encryption_Guide.html" title="AppendixÂ C.Â Disk Encryption Guide" /></head><body class="draft "><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><ul cla
 ss="docnav"><li class="previous"><a accesskey="p" href="ISCSI_disks.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="Disk_Encryption_Guide.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-iSCSI_disks_during_start_up">B.2.Â iSCSI disks during start up</h2></div></div></div><div class="para">
			ISCSI-related events might occur at a number of points while the system starts:
		</div><div class="orderedlist"><ol><li><div class="para">
					The init script in the <span class="application"><strong>initrd</strong></span> will log in to iSCSI targets used for <code class="filename">/</code> (if any). This is done using the <span class="application"><strong>iscsistart</strong></span> utility (which can do this without requiring <span class="application"><strong>iscsid</strong></span> to run).
				</div></li><li><div class="para">
					When the root filesystem has been mounted and the various service initscripts get run, the <span class="application"><strong>iscsid</strong></span> initscript will get called. This script will then start <span class="application"><strong>iscsid</strong></span> if any iSCSI targets are used for <code class="filename">/</code>, or if any targets in the iSCSI database are marked to be logged in to automatically.
				</div></li><li><div class="para">
					After the classic network service script has been run (or would have been run if enabled) the iscsi initscript will run. If the network is accessible, this will log in to any targets in the iSCSI database which are marked to be logged in to automatically. If the network is not accessible, this script will exit quietly.
				</div></li><li><div class="para">
					When using <span class="application"><strong>NetworkManager</strong></span> to access the network (instead of the classic network service script), <span class="application"><strong>NetworkManager</strong></span> will call the iscsi initscript. See: <code class="filename">/etc/NetworkManager/dispatcher.d/04-iscsi</code>
				</div><div class="important"><h2>Important</h2><div class="para">
						Because <span class="application"><strong>NetworkManager</strong></span> is installed in <code class="filename">/usr</code>, you cannot use it to configure network access if <code class="filename">/usr</code> is on network-attached storage such as an iSCSI target.
					</div></div></li></ol></div><div class="para">
			If <span class="application"><strong>iscsid</strong></span> is not needed as the system starts, it will not start automatically. If you start <span class="application"><strong>iscsiadm</strong></span>, <span class="application"><strong>iscsiadm</strong></span> will start <span class="application"><strong>iscsid</strong></span> in turn.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ISCSI_disks.html"><strong>Prev</strong>AppendixÂ B.Â ISCSI disks</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="Disk_Encryption_Guide.html"><strong>Next</strong>AppendixÂ C.Â Disk Encryption Guide</a></li></ul></body></html>


--- NEW FILE sn-initialize-hdd.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.13.Â Initializing the Hard Disk</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="ch07s12.html" title="7.12.Â Keyboard Configuration" /><link rel="next" href="sn-upgrading-system.html" title="7.14.Â Upgrading an Existing System" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s12.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-upgrading-system.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-initialize-hdd">7.13.Â Initializing the Hard Disk</h2></div></div></div><a id="id875108" 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, answer <span class="guilabel"><strong>Yes</strong></span>.
</div><div class="figure" id="fig-initializing-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/initializing/initializing.png" alt="Warning screen â€“ initializing hard drive" /><div class="longdesc"><div class="para">
					Warning screen â€“ initializing hard drive.
				</div></div></div></div><h6>FigureÂ 7.9.Â Warning screen â€“ initializing hard drive</h6></div><br class="figure-break" /><div class="para">
	Certain RAID systems or other nonstandard configurations may be unreadable to the installation program and the prompt to initialize the hard disk may appear. The installation program responds to the physical disk structures it is able to detect.
</div><div class="warning"><h2>Detach Unneeded Disks</h2><div class="para">
		If you have a nonstandard disk configuration that can be detached during installation and detected and configured afterward, power off the system, detach it, and restart the installation.
	</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s12.html"><strong>Prev</strong>7.12.Â Keyboard Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-upgrading-system.html"><strong>Next</strong>7.14.Â Upgrading an Existing System</a></li></ul></body></html>


--- NEW FILE sn-install-diff-source.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.2.Â Installing from a Different Source</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-beginninginstallation.html" title="ChapterÂ 6.Â Beginning the Installation" /><link rel="prev" href="ch-beginninginstallation.html" title="ChapterÂ 6.Â Beginning the Installation" /><link rel="next" href="sn-verifying-media.html" title="6.3.Â Verifying Media" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-beginninginstallation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-verifying-media.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-install-diff-source">6.2.Â Installing from a Different Source</h2></div></div></div><div class="para">
			All boot media except the distribution DVD present a menu that allows you to choose the installation source, such as the network or a hard disk. If you are booting the distribution DVD and do not want to install from the DVD, hit <span class="keycap"><strong>Tab</strong></span> at the boot menu. Add a space and the option <code class="option">linux askmethod</code> to the end of the line that appears below the menu.
		</div><div class="para">
			You can install Fedora from the ISO images stored on hard disk, or from a network using NFS, FTP, or HTTP methods. Experienced users frequently use one of these methods because it is often faster to read data from a hard disk or network server than from a CD or DVD.
		</div><div class="para">
			The following table summarizes the different boot methods and recommended installation methods to use with each:
		</div><div class="table" id="id794100"><div class="table-contents"><table summary="Boot methods and installation methods" border="1"><colgroup><col /><col /></colgroup><thead><tr><th align="left">
							Boot method
						</th><th align="left">
							Installation method
						</th></tr></thead><tbody><tr><td align="left">
							DVD
						</td><td align="left">
							DVD, network, or hard disk
						</td></tr><tr><td align="left">
							Minimal boot CD or USB, rescue CD
						</td><td align="left">
							Network or hard disk
						</td></tr><tr><td align="left">
							Live CD or USB
						</td><td align="left">
							<span class="application"><strong>Install to Hard Disk</strong></span> application
						</td></tr></tbody></table></div><h6>TableÂ 6.1.Â Boot methods and installation methods</h6></div><br class="table-break" /><div class="para">
			<a class="xref" href="s1-installmethod.html" title="7.4.Â Selecting an Installation Method">SectionÂ 7.4, â€œSelecting an Installation Methodâ€</a> contains detailed information about installing from alternate locations.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-beginninginstallation.html"><strong>Prev</strong>ChapterÂ 6.Â Beginning the Installation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-verifying-media.html"><strong>Next</strong>6.3.Â Verifying Media</a></li></ul></body></html>


--- NEW FILE sn-lang-packages.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.23.2.2.Â Additional Language Support</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="sn-package-selection.html" title="7.23.2.Â Customizing the Software Selection" /><link rel="prev" href="sn-package-selection.html" title="7.23.2.Â Customizing the Software Selection" /><link rel="next" href="sn-mandatory-services.html" title="7.23.2.3.Â Core Network Services" /></head><body class="draft "><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/ima
 ge_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-package-selection.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-mandatory-services.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="sn-lang-packages">7.23.2.2.Â Additional Language Support</h4></div></div></div><div class="para">
			Your Fedora system automatically supports the language that you selected at the start of the installation process. To include support for additional languages, select the package group for those languages from the <span class="guilabel"><strong>Languages</strong></span> category.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-package-selection.html"><strong>Prev</strong>7.23.2.Â Customizing the Software Selection</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-mandatory-services.html"><strong>Next</strong>7.23.2.3.Â Core Network Services</a></li></ul></body></html>


--- NEW FILE sn-making-media.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.Â How Do I Make Fedora Media?</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-new-users.html" title="ChapterÂ 2.Â New Users" /><link rel="prev" href="sn-which-files.html" title="2.3.Â Which Files Do I Download?" /><link rel="next" href="ch02s04s02.html" title="2.4.2.Â Making USB Media" /></head><body class="draft "><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><ul class="docnav"><l
 i class="previous"><a accesskey="p" href="sn-which-files.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch02s04s02.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-making-media">2.4.Â How Do I Make Fedora Media?</h2></div></div></div><div class="para">
			A Fedora ISO file can be turned into either CD or DVD discs. You can turn Fedora Live ISO files into bootable USB media, as well as a CD or DVD.
		</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-making-disc-media">2.4.1.Â Making CD or DVD Discs</h3></div></div></div><div class="para">
				To learn how to turn ISO images into CD or DVD media, refer to <a href="http://docs.fedoraproject.org/readme-burning-isos/">http://docs.fedoraproject.org/readme-burning-isos/</a>.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-which-files.html"><strong>Prev</strong>2.3.Â Which Files Do I Download?</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch02s04s02.html"><strong>Next</strong>2.4.2.Â Making USB Media</a></li></ul></body></html>


--- NEW FILE sn-mandatory-services.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.23.2.3.Â Core Network Services</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="sn-package-selection.html" title="7.23.2.Â Customizing the Software Selection" /><link rel="prev" href="sn-lang-packages.html" title="7.23.2.2.Â Additional Language Support" /><link rel="next" href="s1-preparetoinstall-x86.html" title="7.24.Â Preparing to Install" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-lang-packages.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-preparetoinstall-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="sn-mandatory-services">7.23.2.3.Â Core Network Services</h4></div></div></div><div class="para">
			All Fedora installations include the following network services:
		</div><div class="itemizedlist"><ul><li><div class="para">
					centralized logging through syslog
				</div></li><li><div class="para">
					email through SMTP (Simple Mail Transfer Protocol)
				</div></li><li><div class="para">
					network file sharing through NFS (Network File System)
				</div></li><li><div class="para">
					remote access through SSH (Secure SHell)
				</div></li><li><div class="para">
					resource advertising through mDNS (multicast DNS)
				</div></li></ul></div><div class="para">
			The default installation also provides:
		</div><div class="itemizedlist"><ul><li><div class="para">
					network file transfer through HTTP (HyperText Transfer Protocol)
				</div></li><li><div class="para">
					printing through CUPS (Common UNIX Printing System)
				</div></li><li><div class="para">
					remote desktop access through VNC (Virtual Network Computing)
				</div></li></ul></div><div class="para">
			Some automated processes on your Fedora system use the email service to send reports and messages to the system administrator. By default, the email, logging, and printing services do not accept connections from other systems. Fedora installs the NFS sharing, HTTP, and VNC components without enabling those services.
		</div><div class="para">
			You may configure your Fedora system after installation to offer email, file sharing, logging, printing and remote desktop access services. The SSH service is enabled by default. You may use NFS to access files on other systems without enabling the NFS sharing service.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-lang-packages.html"><strong>Prev</strong>7.23.2.2.Â Additional Language Support</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-preparetoinstall-x86.html"><strong>Next</strong>7.24.Â Preparing to Install</a></li></ul></body></html>


--- NEW FILE sn-medialess-booting.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.3.Â Booting to Installation</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ap-medialess-install.html" title="ChapterÂ 10.Â Installing Without Media" /><link rel="prev" href="sn-medialess-editing-grub-conf.html" title="10.2.Â Editing the GRUB Configuration" /><link rel="next" href="ap-install-server.html" title="ChapterÂ 11.Â Setting Up an Installation Server" /></head><body class="draft "><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/i
 mage_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-medialess-editing-grub-conf.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ap-install-server.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-medialess-booting">10.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.html" title="9.2.Â Enabling Remote Access to the Installation System">SectionÂ 9.2, â€œEnabling Remote Access to the Installation Systemâ€</a> for assistance in connecting to the remote system.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-medialess-editing-grub-conf.html"><strong>Prev</strong>10.2.Â Editing the GRUB Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ap-install-server.html"><strong>Next</strong>ChapterÂ 11.Â Setting Up an Installation Server</a></li></ul></body></html>


--- NEW FILE sn-medialess-editing-grub-conf.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.2.Â Editing the GRUB Configuration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ap-medialess-install.html" title="ChapterÂ 10.Â Installing Without Media" /><link rel="prev" href="ap-medialess-install.html" title="ChapterÂ 10.Â Installing Without Media" /><link rel="next" href="sn-medialess-booting.html" title="10.3.Â Booting to Installation" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ap-medialess-install.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-medialess-booting.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-medialess-editing-grub-conf">10.2.Â Editing the <span class="application"><strong>GRUB</strong></span> Configuration</h2></div></div></div><div class="para">
			The <span class="application"><strong>GRUB</strong></span> boot loader uses the configuration file <code class="filename">/boot/grub/grub.conf</code>. To configure <span class="application"><strong>GRUB</strong></span> to boot from the new files, add a boot stanza to <code class="filename">/boot/grub/grub.conf</code>that refers to them.
		</div><div class="para">
			A minimal boot stanza looks like the following listing:
		</div><pre class="screen">title Installation
        root (hd0,0)
        kernel /vmlinuz-install
        initrd /initrd.img-install
</pre><div class="para">
			You may wish to add options to the end of the <code class="option">kernel</code> line of the boot stanza. These options set preliminary options in <span class="application"><strong>Anaconda</strong></span> which the user normally sets interactively. For a list of available installer boot options, refer to <a class="xref" href="ap-admin-options.html" title="ChapterÂ 9.Â Boot Options">ChapterÂ 9, <i>Boot Options</i></a>.
		</div><div class="para">
			The following options are generally useful for medialess installations:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<code class="option">ip=</code>
				</div></li><li><div class="para">
					<code class="option">method=</code>
				</div></li><li><div class="para">
					<code class="option">lang=</code>
				</div></li><li><div class="para">
					<code class="option">keymap=</code>
				</div></li><li><div class="para">
					<code class="option">ksdevice=</code> (if installation requires an interface other than eth0)
				</div></li><li><div class="para">
					<code class="option">vnc</code> and <code class="option">vncpassword=</code> for a remote installation
				</div></li></ul></div><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ap-medialess-install.html"><strong>Prev</strong>ChapterÂ 10.Â Installing Without Media</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-medialess-booting.html"><strong>Next</strong>10.3.Â Booting to Installation</a></li></ul></body></html>


--- NEW FILE sn-mode-rescue.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.6.3.Â Booting Your Computer with the Rescue Mode</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="sn-boot-modes.html" title="9.6.Â Using the Maintenance Boot Modes" /><link rel="prev" href="sn-boot-mediacheck.html" title="9.6.2.Â Verifying boot media" /><link rel="next" href="sn-mode-upgradeany.html" title="9.6.4.Â Upgrading your computer" /></head><body class="draft "><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="Do
 cumentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-boot-mediacheck.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-mode-upgradeany.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-mode-rescue">9.6.3.Â Booting Your Computer with the Rescue Mode</h3></div></div></div><a id="id914249" class="indexterm"></a><div class="para">
				You may boot a command-line Linux system from either a 
				<a id="id914261" 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.
			</div><div class="para">
				Specify the language, keyboard layout and network settings for the rescue system with the screens that follow. The final setup screen configures access to the existing system on your computer.
			</div><div class="para">
				By default, rescue mode attaches an existing operating system to the rescue system under the directory <code class="filename">/mnt/sysimage/</code>.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-boot-mediacheck.html"><strong>Prev</strong>9.6.2.Â Verifying boot media</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-mode-upgradeany.html"><strong>Next</strong>9.6.4.Â Upgrading your computer</a></li></ul></body></html>


--- NEW FILE sn-mode-upgradeany.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.6.4.Â Upgrading your computer</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="sn-boot-modes.html" title="9.6.Â Using the Maintenance Boot Modes" /><link rel="prev" href="sn-mode-rescue.html" title="9.6.3.Â Booting Your Computer with the Rescue Mode" /><link rel="next" href="ap-medialess-install.html" title="ChapterÂ 10.Â Installing Without Media" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-mode-rescue.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ap-medialess-install.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-mode-upgradeany">9.6.4.Â Upgrading your computer</h3></div></div></div><div class="para">
				A previous boot option, <code class="option">upgrade</code>, has been superceded by a stage in the installation process where the installation program prompts you to upgrade or reinstall earlier versions of Fedora that it detects on your system.
			</div><div class="para">
				However, the installation program may not correctly detect a previous version of Fedora if the contents of the <code class="filename">/etc/fedora-release</code> file have changed. The boot option <code class="option">upgradeany</code> relaxes the test that the installation program performs and allows you to upgrade a Fedora installation that the installation program has not correctly identified.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-mode-rescue.html"><strong>Prev</strong>9.6.3.Â Booting Your Computer with the Rescue Mode</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ap-medialess-install.html"><strong>Next</strong>ChapterÂ 10.Â Installing Without Media</a></li></ul></body></html>


--- NEW FILE sn-networkconfig-fedora.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.15.Â Network Configuration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="sn-upgrading-bootloader.html" title="7.14.3.Â Upgrading Boot Loader Configuration" /><link rel="next" href="s1-timezone-x86.html" title="7.16.Â Time Zone Configuration" /></head><body class="draft "><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" a
 lt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-upgrading-bootloader.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-timezone-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-networkconfig-fedora">7.15.Â Network Configuration</h2></div></div></div><a id="id788447" class="indexterm"></a><a id="id908764" class="indexterm"></a><a id="id845695" class="indexterm"></a><a id="id827791" class="indexterm"></a><div class="para">
		Fedora contains support for both IPv4 and IPv6. However, by default, the installation program configures network interfaces on your computer for IPv4, and to use DHCP via <span class="application"><strong>NetworkManager</strong></span>. Currently <span class="application"><strong>NetworkManager</strong></span> does not support IPv6. If your network only supports IPv6 you should use <span class="application"><strong>system-config-network</strong></span> after installation to configure your network interfaces.
	</div><div class="para">
		Setup prompts you to supply a host name and domain name for this computer, in the format <em class="replaceable"><code>hostname</code></em>.<em class="replaceable"><code>domainname</code></em>. Many networks have a DHCP (Dynamic Host Configuration Protocol) service that automatically supplies connected systems with a domain name, leaving the user to enter a hostname.
	</div><div class="figure" id="fig-networkconfig-fedora"><div class="figure-contents"><div class="mediaobject"><img src="images/netconfig/hostname.png" alt="Setting the hostname" /><div class="longdesc"><div class="para">
					Setting the hostname
				</div></div></div></div><h6>FigureÂ 7.11.Â Setting the hostname</h6></div><br class="figure-break" /><div class="para">
		To set up a network that is behind an Internet firewall or router, you may want to use <code class="systemitem"><em class="replaceable"><code>hostname</code></em>.localdomain</code> for your Fedora system. If you have more than one computer on this network, you should give each one a separate host name in this domain.
	</div><div class="note"><h2>Valid Hostnames</h2><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.
		</div></div><div class="para">
		On some networks, the DHCP provider also provides the name of the computer, or hostname. The complete hostname includes both the name of the machine and the name of the domain of which it is a member, such as <code class="systemitem"><em class="replaceable"><code>machine1.example.com</code></em></code>. The machine name (or "short hostname") is <code class="systemitem"><em class="replaceable"><code>machine1</code></em></code>, and the 
		<a id="id811097" class="indexterm"></a>
		 domain name is <code class="systemitem"><em class="replaceable"><code>example.com</code></em></code>.
	</div><div class="para">
		If your Fedora system is connected <span class="emphasis"><em>directly</em></span> to the Internet, you must pay attention to additional considerations to avoid service interruptions or risk action by your upstream service provider. A full discussion of these issues is beyond the scope of this document.
	</div><div class="note"><h2>Modem Configuration</h2><div class="para">
			The installation program does not configure modems. Configure these devices after installation with the <span class="application"><strong>Network</strong></span> utility. The settings for your modem are specific to your particular Internet Service Provider (ISP).
		</div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-networkconfig-fedora_manual-configuration">7.15.1.Â Manual configuration</h3></div></div></div><div class="para">
			Installations that require certain advanced configurations cannot succeed without network connectivity during the installation process, for example, installations on systems with ISCSI drives. In situations where successful installation depends upon correct network settings, the installation program will present you with a dialog that allows you to confirm these details.
		</div><div class="figure" id="fig-networkconfig-net-edit"><div class="figure-contents"><div class="mediaobject"><img src="images/netconfig/net-edit.png" alt="Manual network configuration" /><div class="longdesc"><div class="para">
						Manual network configuration
					</div></div></div></div><h6>FigureÂ 7.12.Â Manual network configuration</h6></div><br class="figure-break" /><div class="para">
			If your network does not have DHCP enabled, or if you need to override the DHCP settings, select the network interface that you plan to use from the <span class="guilabel"><strong>Interfaces</strong></span> menu. Clear the checkbox for <span class="guilabel"><strong>Use dynamic IP configuration (DHCP)</strong></span>. You can now enter an IPv4 address and netmask for this system in the form <em class="replaceable"><code>address</code></em>Â /Â <em class="replaceable"><code>netmask</code></em>, along with the gateway address and nameserver address for your network.
		</div><div class="para">
			Click <span class="guilabel"><strong>OK</strong></span> to accept these settings and continue.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-upgrading-bootloader.html"><strong>Prev</strong>7.14.3.Â Upgrading Boot Loader Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-timezone-x86.html"><strong>Next</strong>7.16.Â Time Zone Configuration</a></li></ul></body></html>


--- NEW FILE sn-news-subscriptions.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.4.Â Subscribing to Fedora Announcements and News</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-next-steps.html" title="ChapterÂ 16.Â Your Next Steps" /><link rel="prev" href="sn-switching-to-gui-login.html" title="16.3.Â Switching to a Graphical Login" /><link rel="next" href="sn-web-help.html" title="16.5.Â Finding Documentation and Support" /></head><body class="draft "><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.pn
 g" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-switching-to-gui-login.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-web-help.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-news-subscriptions">16.4.Â Subscribing to Fedora Announcements and News</h2></div></div></div><div class="para">
			To receive information about package updates, subscribe to either the announcements mailing list, or the RSS feeds.
		</div><div class="variablelist"><dl><dt><span class="term"> Fedora Project announcements mailing list </span></dt><dd><div class="para">
						<a href="https://www.redhat.com/mailman/listinfo/fedora-announce-list">https://www.redhat.com/mailman/listinfo/fedora-announce-list</a>
					</div></dd><dt><span class="term"> Fedora Project RSS feeds </span></dt><dd><div class="para">
						<a href="http://fedoraproject.org/infofeed/">http://fedoraproject.org/infofeed/</a>
					</div></dd></dl></div><div class="para">
			The announcements mailing list also provides you with news on the Fedora Project, and the Fedora community.
		</div><div class="important"><h2>Security Announcements</h2><div class="para">
				Announcements with the keyword <em class="wordasword">[SECURITY]</em> in the title identify package updates that resolve security vulnerabilities.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-switching-to-gui-login.html"><strong>Prev</strong>16.3.Â Switching to a Graphical Login</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-web-help.html"><strong>Next</strong>16.5.Â Finding Documentation and Support</a></li></ul></body></html>


--- NEW FILE sn-package-selection.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.23.2.Â Customizing the Software Selection</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="s1-pkgselection-x86.html" title="7.23.Â Package Group Selection" /><link rel="prev" href="s1-pkgselection-x86.html" title="7.23.Â Package Group Selection" /><link rel="next" href="sn-lang-packages.html" title="7.23.2.2.Â Additional Language Support" /></head><body class="draft "><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="Doc
 umentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-pkgselection-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-lang-packages.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-package-selection">7.23.2.Â Customizing the Software Selection</h3></div></div></div><div class="para">
		Select <span class="guilabel"><strong>Customize now</strong></span> to specify the software packages for your final system in more detail. This option causes the installation process to display an additional customization screen when you select <span class="guibutton"><strong>Next</strong></span>.
	</div><div class="note"><h2>Installing Support for Additional Languages</h2><div class="para">
			Select <span class="guilabel"><strong>Customize now</strong></span> to install support for additional languages. Refer to <a class="xref" href="sn-lang-packages.html" title="7.23.2.2.Â Additional Language Support">SectionÂ 7.23.2.2, â€œAdditional Language Supportâ€</a> for more information on configuring language support.
		</div></div><div class="figure" id="fig-pkgselection-details-x86"><div class="figure-contents"><div class="mediaobject"><img src="images/pkgselection/pkg-group-details.png" alt="Package Group Details" /><div class="longdesc"><div class="para">
	Choose to add or remove optional packages from this package group.
</div></div></div></div><h6>FigureÂ 7.29.Â Package Group Details</h6></div><br class="figure-break" /><div class="para">
		Fedora divides the included software into 
		<a id="id935922" 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.
</div><div class="para">
		To view the package groups for a category, select the category from the list on the left. The list on the right displays the package groups for the currently selected category.
	</div><div class="para">
		To specify a package group for installation, select the check box next to the group. The box at the bottom of the screen displays the details of the package group that is currently highlighted. <span class="emphasis"><em>None</em></span> of the packages from a group will be installed unless the check box for that group is selected.
	</div><div class="para">
		If you select a package group, Fedora automatically installs the base and mandatory packages for that group. To change which optional packages within a selected group will be installed, select the <span class="guibutton"><strong>Optional Packages</strong></span> button under the description of the group. Then use the check box next to an individual package name to change its selection.
	</div><div class="para">
		After you choose the desired packages, select <span class="guilabel"><strong>Next</strong></span> to proceed. Fedora checks your selection, and automatically adds any extra packages required to use the software you select. When you have finished selecting packages, click <span class="guilabel"><strong>Close</strong></span> to save your optional package selections and return to the main package selection screen.
	</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="sn-changing-selection">7.23.2.1.Â Changing Your Mind</h4></div></div></div><div class="para">
			The packages that you select are not permanent. After you boot your system, use the <span class="application"><strong>Add/Remove Software</strong></span> tool to either install new software or remove installed packages. To run this tool, from the main menu, select <span class="guimenu"><strong>System</strong></span> â†’ <span class="guisubmenu"><strong>Administration</strong></span> â†’ <span class="guimenuitem"><strong>Add/Remove Software</strong></span>. The Fedora software management system downloads the latest packages from network servers, rather than using those on the installation discs.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-pkgselection-x86.html"><strong>Prev</strong>7.23.Â Package Group Selection</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-lang-packages.html"><strong>Next</strong>7.23.2.2.Â Additional Language Support</a></li></ul></body></html>


--- NEW FILE sn-partitioning-lvm.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>AppendixÂ D.Â Understanding LVM</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-Technical_appendixes.html" title="PartÂ V.Â Technical appendixes" /><link rel="prev" href="apcs05s03.html" title="C.5.3.Â Remove a passphrase or key from a device" /><link rel="next" href="ch-grub.html" title="AppendixÂ E.Â The GRUB Boot Loader" /></head><body class="draft "><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 Si
 te" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs05s03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-grub.html"><strong>Next</strong></a></li></ul><div class="appendix" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h1 id="sn-partitioning-lvm" class="title">Understanding LVM</h1></div></div></div><a id="id872540" class="indexterm"></a><div class="para">
		LVM (Logical Volume Management) partitions provide a number of advantages over standard partitions. LVM partitions are formatted as 
		<a id="id804300" class="indexterm"></a>
		 <em class="firstterm">physical volumes</em>. One or more physical volumes are combined to form a 
		<a id="id827910" class="indexterm"></a>
		 <em class="firstterm">volume group</em>. Each volume group's total storage is then divided into one or more 
		<a id="id785164" class="indexterm"></a>
		 <em class="firstterm">logical volumes</em>. The logical volumes function much like standard partitions. They have a file system type, such as <code class="systemitem">ext4</code>, and a mount point.
	</div><div class="note"><h2>The /boot Partition and LVM</h2><div class="para">
			The boot loader cannot read LVM volumes. You must make a standard, non-LVM disk partition for your <code class="filename">/boot</code> partition.
		</div></div><div class="para">
		To understand LVM better, imagine the physical volume as a pile of <em class="firstterm">blocks</em>. A block is simply a storage unit used to store data. Several piles of blocks can be combined to make a much larger pile, just as physical volumes are combined to make a volume group. The resulting pile can be subdivided into several smaller piles of arbitrary size, just as a volume group is allocated to several logical volumes.
	</div><div class="para">
		An administrator may grow or shrink logical volumes without destroying data, unlike standard disk partitions. If the physical volumes in a volume group are on separate drives or RAID arrays then administrators may also spread a logical volume across the storage devices.
	</div><div class="para">
		You may lose data if you shrink a logical volume to a smaller capacity than the data on the volume requires. To ensure maximum flexibility, create logical volumes to meet your current needs, and leave excess storage capacity unallocated. You may safely grow logical volumes to use unallocated space, as your needs dictate.
	</div><div class="note"><h2>LVM and the Default Partition Layout</h2><div class="para">
			By default, the installation process creates <code class="filename">/</code> and swap partitions within LVM volumes, with a separate <code class="filename">/boot</code> partition.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apcs05s03.html"><strong>Prev</strong>C.5.3.Â Remove a passphrase or key from a device </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-grub.html"><strong>Next</strong>AppendixÂ E.Â The GRUB Boot Loader</a></li></ul></body></html>


--- NEW FILE sn-pxe-server-manual.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.5.Â Manually configure a PXE server</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ap-install-server.html" title="ChapterÂ 11.Â Setting Up an Installation Server" /><link rel="prev" href="sn-cobbler-import.html" title="11.4.Â Importing the Distribution" /><link rel="next" href="s1-netboot-pxe-config.html" title="11.5.2.Â PXE Boot Configuration" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-cobbler-import.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-netboot-pxe-config.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-pxe-server-manual">11.5.Â Manually configure a PXE server</h2></div></div></div><a id="id825369" class="indexterm"></a><div class="para">
		The following steps must be performed to prepare for a PXE installation:
	</div><div class="orderedlist"><ol><li><div class="para">
				Configure the network (NFS, FTP, HTTP) server to export the installation tree.
			</div></li><li><div class="para">
				Configure the files on the <code class="command">tftp</code> server necessary for PXE booting.
			</div></li><li><div class="para">
				Configure which hosts are allowed to boot from the PXE configuration.
			</div></li><li><div class="para">
				Start the <code class="command">tftp</code> service.
			</div></li><li><div class="para">
				Configure DHCP.
			</div></li><li><div class="para">
				Boot the client, and start the installation.
			</div></li></ol></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="s1-netboot-netserver">11.5.1.Â Setting up the Network Server</h3></div></div></div><a id="id853831" 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.html" title="3.5.Â Preparing for a Network Installation">SectionÂ 3.5, â€œPreparing for a Network Installationâ€</a> for detailed instructions.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-cobbler-import.html"><strong>Prev</strong>11.4.Â Importing the Distribution</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-netboot-pxe-config.html"><strong>Next</strong>11.5.2.Â PXE Boot Configuration</a></li></ul></body></html>


--- NEW FILE sn-remote-logging.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.3.Â Logging to a Remote System During the Installation</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ap-admin-options.html" title="ChapterÂ 9.Â Boot Options" /><link rel="prev" href="sn-telnet-installation.html" title="9.2.3.Â Enabling Remote Access with Telnet" /><link rel="next" href="sn-automating-installation.html" title="9.4.Â Automating the Installation with Kickstart" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-telnet-installation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-automating-installation.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-remote-logging">9.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="id787524" 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.
		</div><div class="para">
			For example, to connect to a syslog service on the system <code class="systemitem">192.168.1.20</code>, enter the following at the <code class="prompt">boot:</code> prompt:
		</div><pre class="screen">
<strong class="userinput"><code>linux syslog=<em class="replaceable"><code>192.168.1.20:514</code></em></code></strong>
</pre><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-remote-logging-logserver">9.3.1.Â Configuring a Log Server</h3></div></div></div><div class="para">
				Fedora uses <code class="command">rsyslog</code> to provide a syslog service. The default configuration of <code class="command">rsyslog</code> rejects messages from remote systems.
			</div><div class="warning"><h2>Only Enable Remote Syslog Access on Secured Networks</h2><div class="para">
					The <code class="command">rsyslog</code> configuration detailed below does not make use of any of the security measures available in <code class="command">rsyslog</code> Crackers may slow or crash systems that permit access to the logging service, by sending large quantities of false log messages. In addition, hostile users may intercept or falsify messages sent to the logging service over the network.
				</div></div><div class="para">
				To configure a Fedora system to accept log messages from other systems on the network, edit the file <code class="filename">/etc/rsyslog.conf</code>. You must use <code class="systemitem">root</code> privileges to edit the file <code class="filename">/etc/rsyslog.conf</code>. Uncomment the following lines by removing the hash preceding them: 
<pre class="screen"><code class="computeroutput">$ModLoad imudp.so</code>
	<code class="computeroutput">$UDPServerRun 514</code>
</pre>
			</div><div class="para">
				Restart the <code class="command">rsyslog</code> service to apply the change:
			</div><pre class="screen">
<strong class="userinput"><code>su -c '/sbin/service rsyslog restart'</code></strong>
</pre><div class="para">
				Enter the <code class="systemitem">root</code> password when prompted.
			</div><div class="note"><h2>Firewall Reconfiguration Required</h2><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-telnet-installation.html"><strong>Prev</strong>9.2.3.Â Enabling Remote Access with Telnet</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-automating-installation.html"><strong>Next</strong>9.4.Â Automating the Installation with Kickstart</a></li></ul></body></html>


--- NEW FILE sn-remoteaccess-installation-vnclistener.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.2.2.Â Connecting the Installation System to a VNC Listener</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="sn-remoteaccess-installation.html" title="9.2.Â Enabling Remote Access to the Installation System" /><link rel="prev" href="sn-remoteaccess-installation.html" title="9.2.Â Enabling Remote Access to the Installation System" /><link rel="next" href="sn-telnet-installation.html" title="9.2.3.Â Enabling Remote Access with Telnet" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-remoteaccess-installation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-telnet-installation.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-remoteaccess-installation-vnclistener">9.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="id790356" 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"><h2>Firewall Reconfiguration Required</h2><div class="para">
					By default, <span class="application"><strong>vncviewer</strong></span> uses TCP port 5500 when in listening mode. 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>5500</code></strong> in the <span class="guilabel"><strong>Port(s)</strong></span> field, and specify <strong class="userinput"><code>tcp</code></strong> as the <span class="guilabel"><strong>Protocol</strong></span>.
				</div></div><div class="para">
				Once the listening client is active, start the installation system and set the VNC options at the <code class="prompt">boot:</code> prompt. In addition to <code class="option">vnc</code> and <code class="option">vncpassword</code> options, use the <code class="option">vncconnect</code> option to specify the name or IP address of the system that has the listening client. To specify the TCP port for the listener, add a colon and the port number to the name of the system.
			</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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-remoteaccess-installation.html"><strong>Prev</strong>9.2.Â Enabling Remote Access to the Installation S...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-telnet-installation.html"><strong>Next</strong>9.2.3.Â Enabling Remote Access with Telnet</a></li></ul></body></html>


--- NEW FILE sn-remoteaccess-installation.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.2.Â Enabling Remote Access to the Installation System</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ap-admin-options.html" title="ChapterÂ 9.Â Boot Options" /><link rel="prev" href="ap-admin-options.html" title="ChapterÂ 9.Â Boot Options" /><link rel="next" href="sn-remoteaccess-installation-vnclistener.html" title="9.2.2.Â Connecting the Installation System to a VNC Listener" /></head><body class="draft "><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="Commo
 n_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ap-admin-options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-remoteaccess-installation-vnclistener.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-remoteaccess-installation">9.2.Â Enabling Remote Access to the Installation System</h2></div></div></div><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 
			<a id="id803795" class="indexterm"></a>
			 VNC (Virtual Network Computing) display protocol. A number of providers offer VNC clients for Microsoft Windows and Mac OS, as well as UNIX-based systems.
		</div><div class="note"><h2>Installing a VNC Client on Fedora</h2><div class="para">
				<a id="id803815" class="indexterm"></a>
				 Fedora includes <span class="application"><strong>vncviewer</strong></span>, the client provided by the developers of VNC. To obtain <span class="application"><strong>vncviewer</strong></span>, install the <code class="filename">vnc</code> package.
			</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" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-remoteaccess-installation-vnc">9.2.1.Â Enabling Remote Access with VNC</h3></div></div></div><div class="para">
				<a id="id813054" 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">
				The <code class="option">vnc</code> option enables the VNC service. The <code class="option">vncpassword</code> option sets a password for remote access. The example shown above sets the password as <strong class="userinput"><code>qwerty</code></strong>.
			</div><div class="note"><h2>VNC Passwords</h2><div class="para">
					The VNC password must be at least six characters long.
				</div></div><div class="para">
				Specify the language, keyboard layout and network settings for the installation system with the screens that follow. You may then access the graphical interface through a VNC client. The installation system displays the correct connection setting for the VNC client:
			</div><pre class="screen">Starting VNC...
The VNC server is now running.
Please connect to computer.mydomain.com:1 to begin the install...
Starting graphical installation...
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><ul class="docnav"><li class="previous"><a accesskey="p" href="ap-admin-options.html"><strong>Prev</strong>ChapterÂ 9.Â Boot Options</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-remoteaccess-installation-vnclistener.html"><strong>Next</strong>9.2.2.Â Connecting the Installation System to a VN...</a></li></ul></body></html>


--- NEW FILE sn-smolt.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.4.Â Hardware Profile</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-firstboot.html" title="ChapterÂ 15.Â Firstboot" /><link rel="prev" href="sn-firstboot-datetime.html" title="15.3.Â Date and Time" /><link rel="next" href="ch-next-steps.html" title="ChapterÂ 16.Â Your Next Steps" /></head><body class="draft "><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><ul class="docnav"><li clas
 s="previous"><a accesskey="p" href="sn-firstboot-datetime.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-next-steps.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-smolt">15.4.Â Hardware Profile</h2></div></div></div><div class="para">
			<span class="application"><strong>Firstboot</strong></span> displays a screen that allows you to submit your hardware information anonymously to the Fedora Project. Developers use these hardware details to guide further support efforts. You can read more about this project and its development at <a href="http://smolts.org/">http://smolts.org/</a>.
		</div><div class="figure" id="id801686"><div class="figure-contents"><div class="mediaobject"><img src="images/firstboot/fb-profile.png" alt="Firstboot hardware profile screen" /><div class="longdesc"><div class="para">
						Firstboot hardware profile screen
					</div></div></div></div><h6>FigureÂ 15.6.Â Firstboot hardware profile screen</h6></div><br class="figure-break" /><div class="para">
			To opt in to this important work, select <span class="guilabel"><strong>Send Profile</strong></span>. If you choose not to submit any profile data, do not change the default. Select <span class="guilabel"><strong>Finish</strong></span> to continue to the login screen.
		</div><div class="important"><h2>Update Your System</h2><div class="para">
				To ensure the security of your system, run a package update after the installation completes. <a class="xref" href="ch-next-steps.html" title="ChapterÂ 16.Â Your Next Steps">ChapterÂ 16, <i>Your Next Steps</i></a> explains how to update your Fedora system.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-firstboot-datetime.html"><strong>Prev</strong>15.3.Â Date and Time</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-next-steps.html"><strong>Next</strong>ChapterÂ 16.Â Your Next Steps</a></li></ul></body></html>


--- NEW FILE sn-start-installation.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.Â How Do I Start the Installation Program?</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-new-users.html" title="ChapterÂ 2.Â New Users" /><link rel="prev" href="sn-cannot-download.html" title="2.5.Â What If I Cannot Download Fedora?" /><link rel="next" href="pt-Before_you_begin.html" title="PartÂ I.Â Before you begin" /></head><body class="draft "><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 Si
 te" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-cannot-download.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="pt-Before_you_begin.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-start-installation">2.6.Â How Do I Start the Installation Program?</h2></div></div></div><a id="id786130" class="indexterm"></a><a id="id786140" class="indexterm"></a><a id="id786153" class="indexterm"></a><div class="para">
			To start the installation program from minimal boot media, a Live image, or the distribution DVD, follow this procedure:
		</div><div class="procedure"><ol class="1"><li><div class="para">
					Power off your computer system.
				</div></li><li><div class="para">
					Disconnect any external FireWire or USB disks that you do not need for installation. Refer to <a class="xref" href="s1-diskpartsetup-x86.html#sn-partitioning-fw-usb" title="7.18.1.3.Â FireWire and USB Disks">SectionÂ 7.18.1.3, â€œFireWire and USB Disksâ€</a> for more information.
				</div></li><li><div class="para">
					Insert the media in your computer and turn it on.
				</div></li></ol></div><div class="para">
			You may need to press a specific key or combination of keys to boot from the media, or configure your system's <em class="firstterm">Basic Input/Output System</em>, or <acronym class="acronym">BIOS</acronym>, to boot from the media. On most computers you must select the boot or BIOS option promptly after turning on the computer. Most Windows-compatible computer systems use a special key such as <span class="keycap"><strong>F1</strong></span>, <span class="keycap"><strong>F2</strong></span>, <span class="keycap"><strong>F12</strong></span>, or <span class="keycap"><strong>Del</strong></span> to start the BIOS configuration menu. On Apple computers, the <span class="keycap"><strong>C</strong></span> key boots the system from the DVD drive. On older Apple hardware you may need to press <span class="keycap"><strong>Cmd</strong></span> +<span class="keycap"><strong>Opt</strong></span>+<span class="keycap"><strong>Shift</strong></span>+<span class="keycap"><strong>Del</strong></
 span> to boot from DVD drive.
		</div><div class="note"><h2>Configuring the BIOS</h2><div class="para">
				If you are not sure what capabilities your computer has, or how to configure the BIOS, consult the documentation provided by the manufacturer. Detailed information on hardware specifications and configuration is beyond the scope of this document.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-cannot-download.html"><strong>Prev</strong>2.5.Â What If I Cannot Download Fedora?</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="pt-Before_you_begin.html"><strong>Next</strong>PartÂ I.Â Before you begin</a></li></ul></body></html>


--- NEW FILE sn-switching-to-gui-login.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.3.Â Switching to a Graphical Login</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-next-steps.html" title="ChapterÂ 16.Â Your Next Steps" /><link rel="prev" href="sn-finishing-upgrade.html" title="16.2.Â Finishing an Upgrade" /><link rel="next" href="sn-news-subscriptions.html" title="16.4.Â Subscribing to Fedora Announcements and News" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-finishing-upgrade.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-news-subscriptions.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-switching-to-gui-login">16.3.Â Switching to a Graphical Login</h2></div></div></div><div class="para">
			If you installed using a text login and wish to switch to a graphical login, follow this procedure.
		</div><div class="procedure"><ol class="1"><li><div class="para">
					Switch users to the <code class="systemitem">root</code> account:
				</div><pre class="screen">su -
</pre><div class="para">
					Provide the administrator password when prompted.
				</div></li><li><div class="para">
					If you have not already done so, install one of the graphical desktop environments. For instance, to install the GNOME desktop environment, use this command:
				</div><pre class="screen">yum groupinstall "GNOME Desktop Environment"
</pre><div class="para">
					This step may take some time as your Fedora system downloads and installs additional software. You may be asked to provide the installation media depending on your original installation source.
				</div></li><li><div class="para">
					Run the following command to edit the <code class="filename">/etc/inittab</code> file:
				</div><pre class="screen">nano /etc/inittab
</pre></li><li><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><div class="para">
					Hit <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>O</strong></span> to write the file to disk, and then hit <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>X</strong></span> to exit the program.
				</div></li><li><div class="para">
					Type <code class="command">exit</code> to logout of the administrator account.
				</div></li></ol></div><div class="para">
			If desired, you can 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, consult one of the help sources listed in <a class="xref" href="ch-introduction.html#sn-additional-help" title="1.2.Â Getting Additional Help">SectionÂ 1.2, â€œGetting Additional Helpâ€</a>.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-finishing-upgrade.html"><strong>Prev</strong>16.2.Â Finishing an Upgrade</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-news-subscriptions.html"><strong>Next</strong>16.4.Â Subscribing to Fedora Announcements and News</a></li></ul></body></html>


--- NEW FILE sn-telnet-installation.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.2.3.Â Enabling Remote Access with Telnet</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="sn-remoteaccess-installation.html" title="9.2.Â Enabling Remote Access to the Installation System" /><link rel="prev" href="sn-remoteaccess-installation-vnclistener.html" title="9.2.2.Â Connecting the Installation System to a VNC Listener" /><link rel="next" href="sn-remote-logging.html" title="9.3.Â Logging to a Remote System During the Installation" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-remoteaccess-installation-vnclistener.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-remote-logging.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-telnet-installation">9.2.3.Â 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="id961602" 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">
				You may then connect to the installation system with the <code class="command">telnet</code> utility. The <code class="command">telnet</code> command requires the name or IP address of the installation system:
			</div><pre class="screen">
<strong class="userinput"><code>telnet computer.mydomain.com</code></strong>
</pre><div class="warning"><h2>Telnet Access Requires No Password</h2><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-remoteaccess-installation-vnclistener.html"><strong>Prev</strong>9.2.2.Â Connecting the Installation System to a VN...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-remote-logging.html"><strong>Next</strong>9.3.Â Logging to a Remote System During the Instal...</a></li></ul></body></html>


--- NEW FILE sn-upgrade-tree.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.14.2.Â Upgrading Using the Installer</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="sn-upgrading-system.html" title="7.14.Â Upgrading an Existing System" /><link rel="prev" href="sn-upgrading-system.html" title="7.14.Â Upgrading an Existing System" /><link rel="next" href="sn-upgrading-bootloader.html" title="7.14.3.Â Upgrading Boot Loader Configuration" /></head><body class="draft "><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_r
 ight.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-upgrading-system.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-upgrading-bootloader.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-upgrade-tree">7.14.2.Â Upgrading Using the Installer</h3></div></div></div><div class="note"><h2>Installations are Recommended</h2><div class="para">
				In general, the Fedora Project recommends that you keep user data on a separate <code class="filename">/home</code> partition and perform a fresh installation. For more information on partitions and how to set them up, refer to <a class="xref" href="s1-diskpartsetup-x86.html" title="7.18.Â Disk Partitioning Setup">SectionÂ 7.18, â€œDisk Partitioning Setupâ€</a>.
			</div></div><div class="para">
			If you choose to upgrade your system using the installation program, any software not provided by Fedora that conflicts with Fedora software is overwritten. Before you begin an upgrade this way, make a list of your system's current packages for later reference:
		</div><pre class="screen"><code class="command">rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' > ~/old-pkglist.txt</code>
</pre><div class="para">
			After installation, consult this list to discover which packages you may need to rebuild or retrieve from non-Fedora software repositories.
		</div><div class="para">
			Next, make a backup of any system configuration data:
		</div><pre class="screen"><code class="command">su -c 'tar czf /tmp/etc-`date +%F`.tar.gz /etc' su -c 'mv /tmp/etc-*.tar.gz /home'</code>
</pre><div class="para">
			Make a complete backup of any important data before performing an upgrade. Important data may include the contents of your entire <code class="filename">/home</code> directory as well as content from services such as an Apache, FTP, or SQL server, or a source code management system. Although upgrades are not destructive, if you perform one improperly there is a small possibility of data loss.
		</div><div class="warning"><h2>Storing Backups</h2><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 class="para">
			For more information on completing the upgrade process later, refer to <a class="xref" href="sn-finishing-upgrade.html" title="16.2.Â Finishing an Upgrade">SectionÂ 16.2, â€œFinishing an Upgradeâ€</a>.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-upgrading-system.html"><strong>Prev</strong>7.14.Â Upgrading an Existing System</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-upgrading-bootloader.html"><strong>Next</strong>7.14.3.Â Upgrading Boot Loader Configuration</a></li></ul></body></html>


--- NEW FILE sn-upgrading-bootloader.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.14.3.Â Upgrading Boot Loader Configuration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="sn-upgrading-system.html" title="7.14.Â Upgrading an Existing System" /><link rel="prev" href="sn-upgrade-tree.html" title="7.14.2.Â Upgrading Using the Installer" /><link rel="next" href="sn-networkconfig-fedora.html" title="7.15.Â Network Configuration" /></head><body class="draft "><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" a
 lt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-upgrade-tree.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-networkconfig-fedora.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-upgrading-bootloader">7.14.3.Â Upgrading Boot Loader Configuration</h3></div></div></div><div class="para">
			<a id="id913385" class="indexterm"></a>
			 Your completed Fedora installation must be registered in the 
			<a id="id865970" class="indexterm"></a>
			 <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="s1-x86-bootloader.html" title="7.22.Â x86, AMD64, and Intel 64 Boot Loader Configuration">SectionÂ 7.22, â€œx86, AMD64, and Intel 64 Boot Loader Configurationâ€</a> for more information about boot loaders.
		</div><div class="para">
			If the existing boot loader was installed by a Linux distribution, the installation system can modify it to load the new Fedora system. To update the existing Linux boot loader, select <span class="guilabel"><strong>Update boot loader configuration</strong></span>. This is the default behavior when you upgrade an existing Fedora or Red Hat Linux installation.
		</div><div class="para">
			<em class="firstterm">GRUB</em> is the standard boot loader for Fedora. If your machine uses another boot loader, such as <span class="trademark">BootMagic</span>â„¢, <span class="trademark">System Commander</span>â„¢, or the loader installed by Microsoft Windows, then the Fedora installation system cannot update it. In this case, select <span class="guilabel"><strong>Skip boot loader updating</strong></span>. When the installation process completes, refer to the documentation for your product for assistance.
		</div><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.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-upgrade-tree.html"><strong>Prev</strong>7.14.2.Â Upgrading Using the Installer</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-networkconfig-fedora.html"><strong>Next</strong>7.15.Â Network Configuration</a></li></ul></body></html>


--- NEW FILE sn-upgrading-system.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.14.Â Upgrading an Existing System</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="sn-initialize-hdd.html" title="7.13.Â Initializing the Hard Disk" /><link rel="next" href="sn-upgrade-tree.html" title="7.14.2.Â Upgrading Using the Installer" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-initialize-hdd.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-upgrade-tree.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-upgrading-system">7.14.Â Upgrading an Existing System</h2></div></div></div><div class="para">
		The installation system automatically detects any existing installation of Fedora. The upgrade process updates the existing system software with new versions, but does not remove any data from users' home directories. The existing partition structure on your hard drives does not change. Your system configuration changes only if a package upgrade demands it. Most package upgrades do not change system configuration, but rather install an additional configuration file for you to examine later.
	</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-upgrade-examine">7.14.1.Â Upgrade Examine</h3></div></div></div><div class="para">
			If your system contains a Fedora or Red Hat Linux installation, a dialog appears asking whether you want to upgrade that installation. To perform an upgrade of an existing system, choose the appropriate installation from the drop-down list and select <span class="guibutton"><strong>Next</strong></span>.
		</div><div class="figure" id="fig-upgrading-fedora"><div class="figure-contents"><div class="mediaobject"><img src="images/upgrading/upgrading.png" alt="The upgrade screen" /><div class="longdesc"><div class="para">
						The upgrade screen.
					</div></div></div></div><h6>FigureÂ 7.10.Â The upgrade screen</h6></div><br class="figure-break" /><div class="note"><h2>Manually Installed Software</h2><div class="para">
				Software you have installed manually on your existing Fedora or Red Hat Linux system may behave differently after an upgrade. You may need to manually reinstall or recompile this software after an upgrade to ensure it performs correctly on the updated system.
			</div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-initialize-hdd.html"><strong>Prev</strong>7.13.Â Initializing the Hard Disk</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-upgrade-tree.html"><strong>Next</strong>7.14.2.Â Upgrading Using the Installer</a></li></ul></body></html>


--- NEW FILE sn-verifying-dvd.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.3.2.Â Verifying the DVD</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="sn-verifying-media.html" title="6.3.Â Verifying Media" /><link rel="prev" href="sn-verifying-media.html" title="6.3.Â Verifying Media" /><link rel="next" href="sn-booting-from-pxe.html" title="6.4.Â Booting from the Network using PXE" /></head><body class="draft "><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><ul cl
 ass="docnav"><li class="previous"><a accesskey="p" href="sn-verifying-media.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-booting-from-pxe.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-verifying-dvd">6.3.2.Â Verifying the DVD</h3></div></div></div><div class="para">
				If you boot from the Fedora distribution DVD, the option to verify the media appears after you choose to install Fedora. 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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-verifying-media.html"><strong>Prev</strong>6.3.Â Verifying Media</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-booting-from-pxe.html"><strong>Next</strong>6.4.Â Booting from the Network using PXE</a></li></ul></body></html>


--- NEW FILE sn-verifying-media.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.3.Â Verifying Media</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-beginninginstallation.html" title="ChapterÂ 6.Â Beginning the Installation" /><link rel="prev" href="sn-install-diff-source.html" title="6.2.Â Installing from a Different Source" /><link rel="next" href="sn-verifying-dvd.html" title="6.3.2.Â Verifying the DVD" /></head><body class="draft "><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="Documentati
 on Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-install-diff-source.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-verifying-dvd.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-verifying-media">6.3.Â Verifying Media</h2></div></div></div><div class="para">
			The distribution DVD media and the Live CD media offer an option to verify the integrity of the media. Recording errors sometimes occur while producing CD or DVD media in home computer equipment. 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="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-verifying-livecd">6.3.1.Â Verifying the Live CD</h3></div></div></div><div class="para">
				If you boot from the Live CD, choose <span class="guilabel"><strong>Verify and Boot</strong></span> from the boot menu. The verification process runs automatically during the boot process, and if it succeeds, the Live CD continues loading. If the verification fails, create a new Live CD using the ISO image you downloaded earlier.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-install-diff-source.html"><strong>Prev</strong>6.2.Â Installing from a Different Source</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-verifying-dvd.html"><strong>Next</strong>6.3.2.Â Verifying the DVD</a></li></ul></body></html>


--- NEW FILE sn-web-help.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.5.Â Finding Documentation and Support</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-next-steps.html" title="ChapterÂ 16.Â Your Next Steps" /><link rel="prev" href="sn-news-subscriptions.html" title="16.4.Â Subscribing to Fedora Announcements and News" /><link rel="next" href="sn-community.html" title="16.6.Â Joining the Fedora Community" /></head><body class="draft "><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" al
 t="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-news-subscriptions.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-community.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-web-help">16.5.Â Finding Documentation and Support</h2></div></div></div><div class="para">
			Members of the Fedora community provide support through mailing lists, Web forums and Linux User Groups (LUGs) across the world.
		</div><div class="para">
			The Web site for the formally endorsed forums is <a href="http://forums.fedoraforum.org/">http://forums.fedoraforum.org/</a>.
		</div><div class="para">
			The following resources provide information on many aspects of Fedora:
		</div><div class="itemizedlist"><ul><li><div class="variablelist"><dl><dt><span class="term"> The FAQ on the Fedora Project website </span></dt><dd><div class="para">
								<a href="http://fedoraproject.org/wiki/FAQ/">http://fedoraproject.org/wiki/FAQ/</a>
							</div></dd></dl></div></li><li><div class="variablelist"><dl><dt><span class="term"> The documents available from the Fedora Documentation Project Web site </span></dt><dd><div class="para">
								<a href="http://docs.fedoraproject.org/">http://docs.fedoraproject.org/</a>
							</div></dd></dl></div></li><li><div class="variablelist"><dl><dt><span class="term"> The Linux Documentation Project (LDP) </span></dt><dd><div class="para">
								<a href="http://www.tldp.org/">http://www.tldp.org/</a>
							</div></dd></dl></div></li><li><div class="variablelist"><dl><dt><span class="term"> The Red Hat Enterprise Linux documentation, much of which also applies to Fedora </span></dt><dd><div class="para">
								<a href="http://www.redhat.com/docs/manuals/enterprise/">http://www.redhat.com/docs/manuals/enterprise/</a>
							</div></dd></dl></div></li></ul></div><div class="para">
			Many other organizations and individuals also provide tutorials and HOWTOs for Fedora on their Web sites. You can locate information on any topic by using Google's Linux search site, located at <a href="http://www.google.com/linux">http://www.google.com/linux</a>.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-news-subscriptions.html"><strong>Prev</strong>16.4.Â Subscribing to Fedora Announcements and News</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-community.html"><strong>Next</strong>16.6.Â Joining the Fedora Community</a></li></ul></body></html>


--- NEW FILE sn-welcome-x86.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.10.Â Welcome to Fedora</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-guimode-x86.html" title="ChapterÂ 7.Â Installing on Intel and AMD Systems" /><link rel="prev" href="s1-begininstall-url-x86.html" title="7.9.Â Installing via FTP or HTTP" /><link rel="next" href="s1-langselection-x86.html" title="7.11.Â Language Selection" /></head><body class="draft "><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="Documentatio
 n Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-begininstall-url-x86.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-langselection-x86.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-welcome-x86">7.10.Â Welcome to Fedora</h2></div></div></div><div class="para">
		The <span class="guilabel"><strong>Welcome</strong></span> screen does not prompt you for any input.
	</div><div class="mediaobject"><img src="images/welcome/welcome.png" /><div class="longdesc"><div class="para">
				Welcome to Fedora 11
			</div></div></div><div class="para">
		Click on the <span class="guibutton"><strong>Next</strong></span> button to continue.
	</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-begininstall-url-x86.html"><strong>Prev</strong>7.9.Â Installing via FTP or HTTP</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-langselection-x86.html"><strong>Next</strong>7.11.Â Language Selection</a></li></ul></body></html>


--- NEW FILE sn-which-arch.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.Â Which Architecture Is My Computer?</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-new-users.html" title="ChapterÂ 2.Â New Users" /><link rel="prev" href="ch-new-users.html" title="ChapterÂ 2.Â New Users" /><link rel="next" href="sn-which-files.html" title="2.3.Â Which Files Do I Download?" /></head><body class="draft "><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><ul class="doc
 nav"><li class="previous"><a accesskey="p" href="ch-new-users.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-which-files.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-which-arch">2.2.Â Which Architecture Is My Computer?</h2></div></div></div><a id="id809154" 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="id809173" class="indexterm"></a><div class="table" id="List-Processor_and_Architecture_Types"><div class="table-contents"><table summary="Processor and architecture types" border="1"><colgroup><col align="left" /><col align="left" /></colgroup><thead><tr><th align="left">
							Processor manufacturer and model
						</th><th align="left">
							Architecture type for Fedora
						</th></tr></thead><tbody><tr><td align="left">
							Intel (except Atom 230, Atom 330, Core 2 Duo, Centrino Core2 Duo, and recent vintage Xeon); AMD (except Athlon 64, Athlon x2, Sempron 64, and Opteron); VIA C3, C7
						</td><td align="left">
							<code class="systemitem">i386</code>
						</td></tr><tr><td align="left">
							Intel Atom 230, Atom 330, Core 2 Duo, Centrino Core 2 Duo, and Xeon; AMD Athlon 64, Athlon x2, Sempron64, and Opteron; Apple MacBook, MacBook Pro, and MacBook Air
						</td><td align="left">
							<code class="systemitem">x86_64</code>
						</td></tr><tr><td align="left">
							Apple Macintosh G3, G4, G5, PowerBook, and other non-Intel models
						</td><td align="left">
							<code class="systemitem">ppc</code>
						</td></tr></tbody></table></div><h6>TableÂ 2.1.Â Processor and architecture types</h6></div><br class="table-break" /><div class="note"><h2>i386 Works for Most Windows Compatible Computers</h2><div class="para">
				If you are unsure what type of processor your computer uses, choose <code class="systemitem">i386</code>.
			</div><div class="para">
				The exception is if your computer is a non-Intel based Apple Macintosh. Refer to <a class="xref" href="sn-which-arch.html#List-Processor_and_Architecture_Types" title="TableÂ 2.1.Â Processor and architecture types">TableÂ 2.1, â€œProcessor and architecture typesâ€</a> for more information.
			</div></div><div class="note"><h2>Intel Atom Processor Architectures Vary</h2><div class="para">
				The N and Z Series Atom processors are based on the <code class="systemitem">i386</code> architecture. The 230 and 330 Series Atom processors are based on the<code class="systemitem">x86_64</code> architecture. Refer to <a href="http://ark.intel.com/cpugroup.aspx?familyID=29035">http://ark.intel.com/cpugroup.aspx?familyID=29035</a> for more details.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-new-users.html"><strong>Prev</strong>ChapterÂ 2.Â New Users</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-which-files.html"><strong>Next</strong>2.3.Â Which Files Do I Download?</a></li></ul></body></html>


--- NEW FILE sn-which-files.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3.Â Which Files Do I Download?</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-new-users.html" title="ChapterÂ 2.Â New Users" /><link rel="prev" href="sn-which-arch.html" title="2.2.Â Which Architecture Is My Computer?" /><link rel="next" href="sn-making-media.html" title="2.4.Â How Do I Make Fedora Media?" /></head><body class="draft "><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><
 ul class="docnav"><li class="previous"><a accesskey="p" href="sn-which-arch.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-making-media.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-which-files">2.3.Â Which Files Do I Download?</h2></div></div></div><div class="para">
			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 11 for x86_64 is named <code class="filename">Fedora-11-x86_64-DVD.iso</code>. Refer to <a class="xref" href="sn-which-arch.html" title="2.2.Â Which Architecture Is My Computer?">SectionÂ 2.2, â€œWhich Architecture Is My Computer?â€</a> if you are unsure of your computer's architecture.
		</div><div class="orderedlist"><ol><li><div class="formalpara"><h5 class="formalpara" id="id803584">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><div class="formalpara"><h5 class="formalpara" id="id803602">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. 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><div class="formalpara"><h5 class="formalpara" id="id803632">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"><h2>Download Size</h2><div class="para">
						Installing the default software for Fedora over the Internet requires more time than the Live image, but less time than the entire DVD distribution. Actual results depend on the software you select and network traffic conditions.
					</div></div></li></ol></div><div class="para">
			The following table explains where to find the desired files on a mirror site. Replace <em class="replaceable"><code>arch</code></em> with the architecture of the computer being installed.
		</div><div class="table" id="tb-Locating_Files"><div class="table-contents"><table summary="Locating files" border="1"><colgroup><col align="left" /><col align="left" /></colgroup><thead><tr><th align="left">
							Media type
						</th><th align="left">
							File locations
						</th></tr></thead><tbody><tr><td align="left">
							Full distribution on DVD
						</td><td align="left">
							<code class="filename">fedora/linux/releases/11/Fedora/<em class="replaceable"><code>arch</code></em>/iso/Fedora-11-<em class="replaceable"><code>arch</code></em>-DVD.iso</code>
						</td></tr><tr><td align="left">
							Live image
						</td><td align="left">
							<code class="filename">fedora/linux/releases/11/Live/<em class="replaceable"><code>arch</code></em>/iso/Fedora-11-<em class="replaceable"><code>arch</code></em>-Live.iso</code>, <code class="filename">fedora/linux/releases/11/Live/<em class="replaceable"><code>arch</code></em>/iso/Fedora-11-KDE-<em class="replaceable"><code>arch</code></em>-Live.iso</code>
						</td></tr><tr><td align="left">
							Minimal CD boot media
						</td><td align="left">
							<code class="filename">fedora/linux/releases/11/Fedora/<em class="replaceable"><code>arch</code></em>/os/images/boot.iso</code>
						</td></tr></tbody></table></div><h6>TableÂ 2.2.Â Locating files</h6></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-which-arch.html"><strong>Prev</strong>2.2.Â Which Architecture Is My Computer?</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-making-media.html"><strong>Next</strong>2.4.Â How Do I Make Fedora Media?</a></li></ul></body></html>


--- NEW FILE sn-x86-uninstall-dual-linux.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.3.Â Your computer dual-boots Fedora and a different Linux distribution</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="sn-x86-uninstall-dual.html" title="19.2.Â Your computer dual-boots Fedora and another operating system" /><link rel="prev" href="sn-x86-uninstall-dual-mac.html" title="19.2.2.Â Your computer dual-boots Fedora and Mac OS X" /><link rel="next" href="sn-x86-uninstall-legacy.html" title="19.3.Â Replacing Fedora with MS-DOS or legacy versions of Microsoft Windows" /></head><body class="draft "><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_le
 ft.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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-x86-uninstall-dual-mac.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-x86-uninstall-legacy.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-x86-uninstall-dual-linux">19.2.3.Â Your computer dual-boots Fedora and a different Linux distribution</h3></div></div></div><div class="note"><h2>Note</h2><div class="para">
			Because of the differences between the many different Linux distributions, these instructions are a general guide only. Specific details will vary according to your chosen distribution and the configuration of your particular computer. This example uses <span class="application"><strong>GParted</strong></span> as a partition editor and <span class="application"><strong>gedit</strong></span> as a text editor, but many other tools are available to perform these tasks. To follow these instructions exactly as written, install <span class="application"><strong>GParted</strong></span> and <span class="application"><strong>gedit</strong></span>.
		</div></div><div class="orderedlist"><ol><li><div class="orderedlist"><h6>Remove Fedora partitions</h6><ol><li><div class="para">
				Boot the Linux version that you want to keep on your computer.
			</div></li><li><div class="para">
				Open <span class="application"><strong>GParted</strong></span>, either from a desktop menu or by typing <code class="command">gparted</code> at the command line and pressing <span class="keycap"><strong>Enter</strong></span>.
			</div></li><li><div class="para">
				<span class="application"><strong>GParted</strong></span> displays the partitions that it detects on your computer, both as a graph and as a table.
			</div><div class="para">
				Right-click the Fedora partitions, then select <span class="guilabel"><strong>Delete</strong></span>.
			</div></li></ol></div></li><li><div class="orderedlist"><h6>Remove Fedora entries from your bootloader</h6><div class="important"><h2> Example only </h2><div class="para">
				These instructions assume that your system uses the <span class="application"><strong>GRUB</strong></span> bootloader. If you use a different bootloader (such as <span class="application"><strong>LILO</strong></span>) consult the documentation for that software to identify and remove Fedora entries from its list of boot targets and to ensure that your default operating system is correctly specified.
			</div></div><ol><li><div class="para">
				At the command line, type <code class="command">suÂ -</code> and press <span class="keycap"><strong>Enter</strong></span>. When the system prompts you for the root password, type the password and press <span class="keycap"><strong>Enter</strong></span>.
			</div></li><li><div class="para">
				Type <code class="command">geditÂ /boot/grub/grub.conf</code> and press <span class="keycap"><strong>Enter</strong></span>. This opens the <code class="filename">grub.conf</code> file in the <span class="application"><strong>gedit</strong></span> text editor.
			</div></li><li><div class="para">
				A typical Fedora entry in the <code class="filename">grub.conf</code> file consists of four lines: 
				<div class="example" id="id894082"><div class="example-contents"><div class="para">
						title Fedora (2.6.27.19-170.2.35.fc10.i686)
					</div><div class="para">
						root (hd0,1)
					</div><div class="para">
						kernel /vmlinuz-2.6.27.19-170.2.35.fc10.i686 ro root=UUID=04a07c13-e6bf-6d5a-b207-002689545705 rhgb quiet
					</div><div class="para">
						initrd /initrd-2.6.27.19-170.2.35.fc10.i686.img
					</div></div><h6>ExampleÂ 19.1.Â Example Fedora entry in <code class="filename">grub.conf</code></h6></div><br class="example-break" />
				 Depending on the configuration of your system, there may be multiple Fedora entries in <code class="filename">grub.conf</code>, each corresponding to a different version of the Linux kernel. Delete each of the Fedora entries from the file.
			</div></li><li><div class="para">
				<code class="filename">Grub.conf</code> contains a line that specifies the default operating system to boot, in the format <code class="literal">default=<em class="replaceable"><code>N</code></em></code> where <em class="replaceable"><code>N</code></em> is a number equal to or greater than 0. If <em class="replaceable"><code>N</code></em> is set to 0, <span class="application"><strong>GRUB</strong></span> will boot the first operating system in the list. If <em class="replaceable"><code>N</code></em> is set to 1, it will boot the second operating system, and so forth.
			</div><div class="para">
				Identify the entry for the operating system that you want <span class="application"><strong>GRUB</strong></span> to boot by default and note its place in the order within the list.
			</div><div class="para">
				Make sure that the <code class="literal">default=</code> line contains the number <span class="emphasis"><em>one below</em></span> the number of your chosen default operating system in the list.
			</div><div class="para">
				Save the updated <code class="filename">grub.conf</code> file and close <span class="application"><strong>gedit</strong></span>
			</div></li></ol></div></li><li><div class="itemizedlist"><h6>Make space available to your operating system</h6><div class="note"><h2>Note</h2><div class="para">
				This step is not required to remove Fedora from your computer. However, if you skip this step, you will leave part of your hard drive's storage capacity unusable by your other Linux operating system. Depending on your configuration, this might be a a significant portion of the storage capacity of the drive.
			</div></div><div class="note"><h2>Note</h2><div class="para">
				To carry out this step, you require live media for a Linux distribution, for example, the Fedora Live CD or the Knoppix DVD.
			</div></div><div class="para">
			The method to make the space freed by removing the Fedora partitions available to your other Linux operating system differs, depending on whether your chosen operating system is installed on disk partitions configured to use Logical Volume Management (LVM) or not.
		</div><ul><li><div class="orderedlist"><h6>If you do not use LVM</h6><ol><li><div class="para">
				Boot your computer from Linux live media, and install <span class="application"><strong>gparted</strong></span> if it is not already present.
			</div></li><li><div class="para">
				Open <span class="application"><strong>GParted</strong></span>, either from a desktop menu or by typing <code class="command">gparted</code> at the command line and pressing <span class="keycap"><strong>Enter</strong></span>.
			</div></li><li><div class="para">
				<span class="application"><strong>GParted</strong></span> displays the partitions on your system both as a graph and as a table. Click on the partition that you want to extend to use the space freed by removing Fedora, and click the <span class="guilabel"><strong>Resize/Move</strong></span> button.
			</div></li><li><div class="para">
				A new dialog opens, allowing you to specify a new size for the partition by entering it as numbers, or by dragging the sides of the graphical representation of the partition so that it fills the available space. Click the <span class="guilabel"><strong>Resize/Move</strong></span> button in this dialog to confirm your choice.
			</div></li><li><div class="para">
				Back in the main <span class="application"><strong>GParted</strong></span> window, click <span class="guilabel"><strong>Apply</strong></span>. Take note of the name of the partition that you just resized, for example, <code class="filename">/dev/sda3</code>.
			</div></li><li><div class="para">
				When <span class="application"><strong>GParted</strong></span> finishes resizing the partition, type <code class="command">e2fsck <em class="replaceable"><code>partition</code></em></code> at a command line and press <span class="keycap"><strong>Enter</strong></span>, where <em class="replaceable"><code>partition</code></em> is the partition that you just resized. For example, if you just resized <code class="filename">/dev/sda3</code>, you would type <code class="command">e2fsckÂ /dev/sda3</code>.
			</div><div class="para">
				Linux now checks the file system of the newly-resized partition.
			</div></li><li><div class="para">
				When the file system check finishes, type <code class="command">resize2fs <em class="replaceable"><code>partition</code></em></code> at a command line and press <span class="keycap"><strong>Enter</strong></span>, where <em class="replaceable"><code>partition</code></em> is the partition that you just resized. For example, if you just resized <code class="filename">/dev/sda3</code>, you would type <code class="command">resize2fsÂ /dev/sda3</code>.
			</div><div class="para">
				Linux now resizes your file system to fill the newly-resized partition.
			</div></li><li><div class="para">
				Restart your computer. The extra space is now available to your Linux installation.
			</div></li></ol></div></li><li><div class="orderedlist"><h6>If you use LVM</h6><ol><li><div class="para">
				Boot your computer from Linux live media and install <span class="application"><strong>gparted</strong></span> and <span class="application"><strong>lvm2</strong></span> if they are not already present.
			</div></li><li><div class="orderedlist"><h6>Create a new partition in the free space on the disk</h6><ol><li><div class="para">
						Open <span class="application"><strong>GParted</strong></span>, either from a desktop menu or by typing <code class="command">gparted</code> at the command line and pressing <span class="keycap"><strong>Enter</strong></span>.
					</div></li><li><div class="para">
						<span class="application"><strong>GParted</strong></span> displays the partitions on your system both as a graph and as a table. The space freed by removing Fedora is labeled <code class="literal">unallocated</code>. Right-click on the unallocated space and select <span class="guilabel"><strong>New</strong></span>. Accept the defaults and <span class="application"><strong>GParted</strong></span> will create a new partition that fills the space available on the drive.
					</div></li><li><div class="para">
						Click <span class="guilabel"><strong>Apply</strong></span>. <span class="application"><strong>GParted</strong></span> writes the changes to your hard drive. Take note of the name of the partition that you just created, and the name of the device that holds the partition. For example, you may have created <code class="filename">/dev/sda3</code> on device <code class="filename">/dev/sda</code>.
					</div></li></ol></div></li><li><div class="orderedlist"><h6>Change the partition type identifier</h6><ol><li><div class="para">
						<span class="application"><strong>Fdisk</strong></span> is a partitioning tool capable of preparing partitions for LVM. At a command line, type <code class="command">fdisk <em class="replaceable"><code>device</code></em></code> and press <span class="keycap"><strong>Enter</strong></span>, where <em class="replaceable"><code>device</code></em> is the name of the device on which you just created a partition. For example, <code class="command">fdisk /dev/sda</code>.
					</div></li><li><div class="para">
						At the prompt <code class="prompt">Command (m for help):</code>, press <span class="keycap"><strong>T</strong></span> and <span class="keycap"><strong>Enter</strong></span> to use <span class="application"><strong>fdisk</strong></span> to change a partition type.
					</div></li><li><div class="para">
						At the prompt <code class="prompt">Partition number (1-4):</code>, type the number of the partition that you just created. For example, if you just created partition <code class="filename">/dev/sda3</code>, type the number <code class="literal">3</code> and press <span class="keycap"><strong>Enter</strong></span>. This identifies the partition whose type <span class="application"><strong>fdisk</strong></span> will change.
					</div></li><li><div class="para">
						At the prompt <code class="prompt">Hex code (type L to list codes):</code>, type the code <code class="literal">8e</code> and press <span class="keycap"><strong>Enter</strong></span>. This is the code for a Linux LVM partition.
					</div></li><li><div class="para">
						At the prompt <code class="prompt">Command (m for help):</code>, press <span class="keycap"><strong>W</strong></span> and <span class="keycap"><strong>Enter</strong></span>. <span class="application"><strong>Fdisk</strong></span> writes the new type code to the partition and exits.
					</div></li></ol></div></li><li><div class="orderedlist"><h6>Expand the volume group</h6><ol><li><div class="para">
						At the command prompt, type <code class="command">lvm</code> and press <span class="keycap"><strong>Enter</strong></span> to start the <span class="application"><strong>lvm2</strong></span> tool.
					</div></li><li><div class="para">
						At the <code class="prompt">lvm></code> prompt, type <code class="command">pvcreate <em class="replaceable"><code>partition</code></em></code> and press <span class="keycap"><strong>Enter</strong></span>, where <em class="replaceable"><code>partition</code></em> is the partition that you recently created. For example, <code class="command">pvcreate /dev/sda3</code>. This creates <code class="filename">/dev/sda3</code> as a physical volume in LVM.
					</div></li><li><div class="para">
						At the <code class="prompt">lvm></code> prompt, type <code class="command">vgextend <em class="replaceable"><code>VolumeGroup</code></em> <em class="replaceable"><code>partition</code></em></code> and press <span class="keycap"><strong>Enter</strong></span>, where <em class="replaceable"><code>VolumeGroup</code></em> is the LVM volume group on which Linux is installed and <em class="replaceable"><code>partition</code></em> is the partition that you recently created. For example, if Linux is installed on <code class="filename">/dev/VolumeGroup00</code>, you would type <code class="command">vgextend /dev/VolumeGroup00 /dev/sda3</code> to extend that volume group to include the physical volume at <code class="filename">/dev/sda3</code>.
					</div></li><li><div class="para">
						At the <code class="prompt">lvm></code> prompt, type <code class="command">lvextend -l +100%FREE <em class="replaceable"><code>LogVol</code></em></code> and press <span class="keycap"><strong>Enter</strong></span>, where <em class="replaceable"><code>LogVol</code></em> is the logical volume that contains your Linux filesystem. For example, to extend <code class="filename">LogVol00</code> to fill the newly-available space in its volume group, <code class="filename">VolGroup00</code>, type <code class="command">lvextend -l +100%FREE /dev/VolGroup00/LogVol00</code>.
					</div></li><li><div class="para">
						At the <code class="prompt">lvm></code> prompt, type <code class="command">exit</code> and press <span class="keycap"><strong>Enter</strong></span> to exit <span class="application"><strong>lvm2</strong></span>
					</div></li></ol></div></li><li><div class="para">
				Type <code class="command">e2fsck <em class="replaceable"><code>LogVol</code></em></code> at the command line and press <span class="keycap"><strong>Enter</strong></span>, where <em class="replaceable"><code>LogVol</code></em> is the logical volume that you just resized. For example, if you just resized <code class="filename">/dev/VolumeGroup00/LogVol00</code>, you would type <code class="command">e2fsckÂ /dev/VolumeGroup00/LogVol00</code>.
			</div><div class="para">
				Linux now checks the file system of the newly-resized logical volume.
			</div></li><li><div class="para">
				When the file system check finishes, type <code class="command">resize2fs <em class="replaceable"><code>LogVol</code></em></code> at a command line and press <span class="keycap"><strong>Enter</strong></span>, where <em class="replaceable"><code>LogVol</code></em> is the partition that you just resized. For example, if you just resized <code class="filename">/dev/VolumeGroup00/LogVol00</code>, you would type <code class="command">resize2fsÂ /dev/VolumeGroup00/LogVol00</code>.
			</div><div class="para">
				Linux now resizes your file system to fill the newly-resized logical volume.
			</div></li><li><div class="para">
				Restart your computer. The extra space is now available to your Linux installation.
			</div></li></ol></div></li></ul></div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-x86-uninstall-dual-mac.html"><strong>Prev</strong>19.2.2.Â Your computer dual-boots Fedora and Mac O...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-x86-uninstall-legacy.html"><strong>Next</strong>19.3.Â Replacing Fedora with MS-DOS or legacy vers...</a></li></ul></body></html>


--- NEW FILE sn-x86-uninstall-dual-mac.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.2.Â Your computer dual-boots Fedora and Mac OS X</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="sn-x86-uninstall-dual.html" title="19.2.Â Your computer dual-boots Fedora and another operating system" /><link rel="prev" href="sn-x86-uninstall-dual.html" title="19.2.Â Your computer dual-boots Fedora and another operating system" /><link rel="next" href="sn-x86-uninstall-dual-linux.html" title="19.2.3.Â Your computer dual-boots Fedora and a different Linux distribution" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-x86-uninstall-dual.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-x86-uninstall-dual-linux.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-x86-uninstall-dual-mac">19.2.2.Â Your computer dual-boots Fedora and Mac OS X</h3></div></div></div><div class="para">
		The procedure to remove Fedora from a system that dual-boots Fedora and Mac OS X varies depending on whether you have installed <span class="application"><strong>Boot Camp</strong></span> on your computer:
	</div><div class="orderedlist"><h6>You are not using <span class="application"><strong>Boot Camp</strong></span> on your computer</h6><ol><li><div class="para">
				Open the <span class="application"><strong>Disk Utility</strong></span> in <code class="filename">/Applications/Utilities</code>.
			</div></li><li><div class="para">
				Select the entry on the left for the disk volume containing Fedora.
			</div></li><li><div class="para">
				Click the <span class="guilabel"><strong>Partition</strong></span> tab on the right side of the dialog.
			</div></li><li><div class="para">
				Select the Fedora partitions and click the minus button below the partition layout diagram.
			</div></li><li><div class="para">
				Resize your OS X partition to include the newly freed space.
			</div></li></ol></div><div class="orderedlist"><h6>You are using <span class="application"><strong>Boot Camp</strong></span> on your computer</h6><ol><li><div class="para">
				Open the <span class="application"><strong>Boot Camp Assistant</strong></span> in <code class="filename">/Applications/Utilities</code>.
			</div></li><li><div class="para">
				Select <span class="guilabel"><strong>Create or remove a Windows partition</strong></span> and click <span class="guilabel"><strong>Next</strong></span>.
			</div></li><li><div class="para">
				If your computer has a single internal disk, click <span class="guilabel"><strong>Restore</strong></span>.
			</div></li><li><div class="para">
				If your computer has multiple internal disks, select the Linux disk, and then select <span class="guilabel"><strong>Restore to a single Mac OS partition</strong></span>. Click <span class="guilabel"><strong>Continue</strong></span>.
			</div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-x86-uninstall-dual.html"><strong>Prev</strong>19.2.Â Your computer dual-boots Fedora and another...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-x86-uninstall-dual-linux.html"><strong>Next</strong>19.2.3.Â Your computer dual-boots Fedora and a dif...</a></li></ul></body></html>


--- NEW FILE sn-x86-uninstall-dual.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.Â Your computer dual-boots Fedora and another operating system</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-x86-uninstall.html" title="ChapterÂ 19.Â Removing Fedora" /><link rel="prev" href="ch-x86-uninstall.html" title="ChapterÂ 19.Â Removing Fedora" /><link rel="next" href="sn-x86-uninstall-dual-mac.html" title="19.2.2.Â Your computer dual-boots Fedora and Mac OS X" /></head><body class="draft "><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><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-x86-uninstall.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sn-x86-uninstall-dual-mac.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-x86-uninstall-dual">19.2.Â Your computer dual-boots Fedora and another operating system</h2></div></div></div><div class="para">
			If your computer is configured to dual-boot Fedora and another operating system, removing Fedora without removing the partitions containing the other operating system and its data is more complicated. Specific instructions for a number of operating systems are set out below. To keep neither Fedora nor the other operating system, follow the steps described for a computer with only Fedora installed: <a class="xref" href="ch-x86-uninstall.html#sn-x86-uninstall-single" title="19.1.Â Fedora is the only operating system on the computer">SectionÂ 19.1, â€œFedora is the only operating system on the computerâ€</a>
		</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-x86-uninstall-dual-windows">19.2.1.Â Your computer dual-boots Fedora and a Microsoft Windows operating system</h3></div></div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="sn-x86-uninstall-dual-windows-2000xp2003">19.2.1.1.Â Windows 2000, Windows Server 2000, Windows XP, and Windows Server 2003</h4></div></div></div><div class="warning"><h2>Warning</h2><div class="para">
	Once you commence this process, your computer may be left in an unbootable state until you complete the entire set of instructions. Carefully read the steps below before beginning the removal process. Consider opening these instructions on another computer or printing them so that you have access to them at all times during the process.
</div><div class="para">
			This procedure relies on the <span class="application"><strong>Windows Recovery Console</strong></span> that loads from the Windows installation disk, so you will not be able to complete the procedure without access to this disk. If you start this procedure and do not complete it, you could leave your computer in a condition where you cannot boot it. The "system restore disk" supplied with some factory-built computers that are sold with Windows pre-installed on them might not include the <span class="application"><strong>Windows Recovery Console</strong></span>.
		</div><div class="para">
			During the process outlined in these instructions, the <span class="application"><strong>Windows Recovery Console</strong></span> will prompt you for the Administrator password for your Windows system. Do not follow these instructions unless you know the Administrator password for your system or are certain that an Administrator password has never been created, even by the computer manufacturer.
		</div></div><div class="orderedlist"><ol><li><div class="para">
	Remove the Fedora partitions
</div><div class="orderedlist"><ol><li><div class="para">
	Boot your computer into your Microsoft Windows environment.
</div></li><li><div class="para">
						Click <span class="guilabel"><strong>Start</strong></span>><span class="guilabel"><strong>Run...</strong></span>, type <code class="command">diskmgmt.msc</code> and press <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>Disk Management</strong></span> tool opens.
					</div><div class="para">
	The tool displays a graphical representation of your disk, with bars representing each partition. The first partition is usually labeled <code class="literal">NTFS</code> and corresponds to your <code class="filename">C:</code> drive. At least two Fedora partitions will be visible. Windows will not display a file system type for these partitions, but may allocate drive letters to some of them.
</div></li><li><div class="para">
	Right-click on one of the Fedora partitions, then click <span class="guilabel"><strong>Delete Partition</strong></span> and click <span class="guilabel"><strong>Yes</strong></span> to confirm the deletion. Repeat this process for the other Fedora partitions on your system. As you delete partitions, Windows labels the space on the hard drive previously occupied by those partitions as <code class="literal">unallocated</code>.
</div></li></ol></div></li><li><div class="para">
	Enable Windows to use the space on your hard drive vacated by Fedora (optional)
</div><div class="note"><h2>Note</h2><div class="para">
		This step is not required to remove Fedora from your computer. However, if you skip this step, you will leave part of your hard drive's storage capacity unusable by Windows. Depending on your configuration, this might be a a significant portion of the storage capacity of the drive.
	</div></div><div class="para">
	Decide whether to extend an existing Windows partition to use the extra space, or create a new Windows partition in that space. If you create new a Windows partition, Windows will allocate a new drive letter to it and will interact with it as if it is a separate hard drive.
</div><div class="orderedlist"><h6>Extending an existing Windows partition</h6><div class="note"><h2>Note</h2><div class="para">
						The <span class="application"><strong>diskpart</strong></span> tool used in this step is installed as part of the Windows XP and Windows 2003 operating systems. If you are performing this step on a computer running Windows 2000 or Windows Server 2000, you can download a version of <span class="application"><strong>diskpart</strong></span> for your operating system from the Microsoft website.
					</div></div><ol><li><div class="para">
						Click <span class="guilabel"><strong>Start</strong></span>><span class="guilabel"><strong>Run...</strong></span>, type <code class="command">diskpart</code> and press <span class="keycap"><strong>Enter</strong></span>. A command window appears.
					</div></li><li><div class="para">
						Type <code class="command">list volume</code> and press <span class="keycap"><strong>Enter</strong></span>. <span class="application"><strong>Diskpart</strong></span> displays a list of the partitions on your system with a volume number, its drive letter, volume label, filesystem type, and size. Identify the Windows partition that you would like to use to occupy the space vacated on your hard drive by Fedora and take note of its volume number (for example, your Windows <code class="filename">C:</code> drive might be "Volume 0").
					</div></li><li><div class="para">
						Type <code class="command">select volume <em class="replaceable"><code>N</code></em></code> (where <em class="replaceable"><code>N</code></em> is the volume number for the Windows partition that you want to extend) and press <span class="keycap"><strong>Enter</strong></span>. Now type <code class="command">extend</code> and press <span class="keycap"><strong>Enter</strong></span>. <span class="application"><strong>Diskpart</strong></span> now extends your chosen partition to fill the remaining space on your hard drive. It will notify you when the operation is complete.
					</div></li></ol></div><div class="orderedlist"><h6>Adding a new Windows partition</h6><ol><li><div class="para">
						In the the <code class="literal">Disk Management</code> window, right-click on disk space that Windows labels as <code class="literal">unallocated</code> and select <code class="literal">New Partition</code> from the menu. The <span class="application"><strong>New Partition Wizard</strong></span> starts.
					</div></li><li><div class="para">
						Follow the prompts presented by the <span class="application"><strong>New Partition Wizard</strong></span>. If you accept the default options, the tool will create a new partition that fills all available space on the hard drive, assigns it the next available drive letter, and formats it with the NTFS file system.
					</div></li></ol></div></li><li><div class="para">
	Restore the Windows bootloader
</div><div class="orderedlist"><ol><li><div class="para">
	Insert the Windows installation disk and restart your computer. As your computer starts, the following message will appear on the screen for a few seconds:
</div><pre class="screen"><code class="prompt">Press any key to boot from CD</code>
</pre><div class="para">
	Press any key while the message is still showing and the Windows installation software will load.
</div></li><li><div class="para">
						When the <code class="literal">Welcome to Setup</code> screen appears, you can start the <span class="application"><strong>Windows Recovery Console</strong></span>. The procedure is slightly different on different versions of Windows:
					</div><div class="itemizedlist"><ul><li><div class="para">
								On Windows 2000 and Windows Server 2000, press the <span class="keycap"><strong>R</strong></span> key, then the <span class="keycap"><strong>C</strong></span> key.
							</div></li><li><div class="para">
								On Windows XP and Windows Server 2003, press the <span class="keycap"><strong>R</strong></span> key.
							</div></li></ul></div></li><li><div class="para">
						The <span class="application"><strong>Windows Recovery Console</strong></span> scans your hard drives for Windows installations, and assigns a number to each one. It displays a list of Windows installations and prompts you to select one. Type the number corresponding to the Windows installation that you want to restore.
					</div></li><li><div class="para">
						The <span class="application"><strong>Windows Recovery Console</strong></span> prompts you for the Administrator password for your Windows installation. Type the Administrator password and press the <span class="keycap"><strong>Enter</strong></span> key. If there is no administrator password for this system, press only the <span class="keycap"><strong>Enter</strong></span> key.
					</div></li><li><div class="para">
						At the prompt, type the command <code class="command">fixmbr</code> and press the <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>fixmbr</strong></span> tool now restores the Master Boot Record for the system.
					</div></li><li><div class="para">
						When the prompt reappears, type <code class="command">exit</code> and press the <span class="keycap"><strong>Enter</strong></span> key.
					</div></li><li><div class="para">
	Your computer will restart and boot your Windows operating system.
</div></li></ol></div></li></ol></div></div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h4 class="title" id="sn-x86-uninstall-dual-windows-vista2008">19.2.1.2.Â Windows Vista and Windows Server 2008</h4></div></div></div><div class="warning"><h2>Warning</h2><div class="para">
	Once you commence this process, your computer may be left in an unbootable state until you complete the entire set of instructions. Carefully read the steps below before beginning the removal process. Consider opening these instructions on another computer or printing them so that you have access to them at all times during the process.
</div><div class="para">
			This procedure relies on the <span class="application"><strong>Windows Recovery Environment</strong></span> that loads from the Windows installation disk and you will not be able to complete the procedure without access to this disk. If you start this procedure and do not complete it, you could leave your computer in a condition where you cannot boot it. The "system restore disk" supplied with some factory-built computers that are sold with Windows pre-installed on them might not include the <span class="application"><strong>Windows Recovery Environment</strong></span>.
		</div></div><div class="orderedlist"><ol><li><div class="para">
	Remove the Fedora partitions
</div><div class="orderedlist"><ol><li><div class="para">
	Boot your computer into your Microsoft Windows environment.
</div></li><li><div class="para">
						Click <span class="guilabel"><strong>Start</strong></span> then type <code class="command">diskmgmt.msc</code> into the <span class="guilabel"><strong>Start Search</strong></span> box and press <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>Disk Management</strong></span> tool opens.
					</div><div class="para">
	The tool displays a graphical representation of your disk, with bars representing each partition. The first partition is usually labeled <code class="literal">NTFS</code> and corresponds to your <code class="filename">C:</code> drive. At least two Fedora partitions will be visible. Windows will not display a file system type for these partitions, but may allocate drive letters to some of them.
</div></li><li><div class="para">
	Right-click on one of the Fedora partitions, then click <span class="guilabel"><strong>Delete Partition</strong></span> and click <span class="guilabel"><strong>Yes</strong></span> to confirm the deletion. Repeat this process for the other Fedora partitions on your system. As you delete partitions, Windows labels the space on the hard drive previously occupied by those partitions as <code class="literal">unallocated</code>.
</div></li></ol></div></li><li><div class="para">
	Enable Windows to use the space on your hard drive vacated by Fedora (optional)
</div><div class="note"><h2>Note</h2><div class="para">
		This step is not required to remove Fedora from your computer. However, if you skip this step, you will leave part of your hard drive's storage capacity unusable by Windows. Depending on your configuration, this might be a a significant portion of the storage capacity of the drive.
	</div></div><div class="para">
	Decide whether to extend an existing Windows partition to use the extra space, or create a new Windows partition in that space. If you create new a Windows partition, Windows will allocate a new drive letter to it and will interact with it as if it is a separate hard drive.
</div><div class="orderedlist"><h6>Extending an existing Windows partition</h6><ol><li><div class="para">
						In the <span class="application"><strong>Disk Management</strong></span> window, right-click on the Windows partition that you want to extend and select <span class="guilabel"><strong>Extend Volume</strong></span> from the menu. The <span class="application"><strong>Extend Volume Wizard</strong></span> opens.
					</div></li><li><div class="para">
						Follow the prompts presented by the <span class="application"><strong>Extend Volume Wizard</strong></span>. If you accept the defaults that it offers you, the tool will extend the selected volume to fill all available space on the hard drive.
					</div></li></ol></div><div class="orderedlist"><h6>Adding a new Windows partition</h6><ol><li><div class="para">
						In the <code class="literal">Disk Management</code> window, right-click on disk space that Windows labels as <code class="literal">unallocated</code> and select <code class="literal">New Simple Volume</code> from the menu. The <span class="application"><strong>New Simple Volume Wizard</strong></span> starts.
					</div></li><li><div class="para">
						Follow the prompts presented by the <span class="application"><strong>New Simple Volume Wizard</strong></span>. If you accept the default options, the tool will create a new partition that fills all available space on the hard drive, assigns it the next available drive letter, and formats it with the NTFS file system.
					</div></li></ol></div></li><li><div class="para">
	Restore the Windows bootloader
</div><div class="orderedlist"><ol><li><div class="para">
	Insert the Windows installation disk and restart your computer. As your computer starts, the following message will appear on the screen for a few seconds:
</div><pre class="screen"><code class="prompt">Press any key to boot from CD or DVD</code>
</pre><div class="para">
	Press any key while the message is still showing and the Windows installation software will load.
</div></li><li><div class="para">
						In the <span class="guilabel"><strong>Install Windows</strong></span> dialog, select a language, time and currency format, and keyboard type. Click <span class="guilabel"><strong>Next</strong></span>
					</div></li><li><div class="para">
						Click <span class="guilabel"><strong>Repair your computer</strong></span>.
					</div></li><li><div class="para">
						The <span class="application"><strong>Windows Recovery Environment</strong></span> (WRE) shows you the Windows installations that it can detect on your system. Select the installation that you want to restore, then click <span class="guilabel"><strong>Next</strong></span>.
					</div></li><li><div class="para">
						Click <span class="guilabel"><strong>Command prompt</strong></span>. A command window will open.
					</div></li><li><div class="para">
						Type <code class="command">bootrec /fixmbr</code> and press <span class="keycap"><strong>Enter</strong></span>.
					</div></li><li><div class="para">
						When the prompt reappears, close the command window, then click <span class="guilabel"><strong>Restart</strong></span>.
					</div></li><li><div class="para">
	Your computer will restart and boot your Windows operating system.
</div></li></ol></div></li></ol></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-x86-uninstall.html"><strong>Prev</strong>ChapterÂ 19.Â Removing Fedora</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sn-x86-uninstall-dual-mac.html"><strong>Next</strong>19.2.2.Â Your computer dual-boots Fedora and Mac O...</a></li></ul></body></html>


--- NEW FILE sn-x86-uninstall-legacy.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.3.Â Replacing Fedora with MS-DOS or legacy versions of Microsoft Windows</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="ch-x86-uninstall.html" title="ChapterÂ 19.Â Removing Fedora" /><link rel="prev" href="sn-x86-uninstall-dual-linux.html" title="19.2.3.Â Your computer dual-boots Fedora and a different Linux distribution" /><link rel="next" href="pt-Technical_appendixes.html" title="PartÂ V.Â Technical appendixes" /></head><body class="draft "><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://d
 ocs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-x86-uninstall-dual-linux.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="pt-Technical_appendixes.html"><strong>Next</strong></a></li></ul><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="sn-x86-uninstall-legacy">19.3.Â Replacing Fedora with MS-DOS or legacy versions of Microsoft Windows</h2></div></div></div><div class="para">
		In DOS and Windows, use the Windows <code class="command">fdisk</code> utility to create a new MBR with the <em class="wordasword">undocumented</em> flag <code class="command">/mbr</code>. This <span class="emphasis"><em>ONLY</em></span> rewrites the MBR to boot the primary DOS partition. The command should look like the following:
	</div><pre class="screen">
<code class="command">fdisk /mbr</code>
</pre><div class="para">
		If you need to remove Linux from a hard drive and have attempted to do this with the default DOS (Windows) <code class="command">fdisk</code>, you will experience the <span class="emphasis"><em>Partitions exist but they do not exist</em></span> problem. The best way to remove non-DOS partitions is with a tool that understands partitions other than DOS.
	</div><div class="para">
		To begin, insert the Fedora CD #1 and boot your system. Once you have booted off the CD, a boot prompt appears. At the boot prompt, type: <strong class="userinput"><code>linux rescue</code></strong>. This starts the rescue mode program.
	</div><div class="para">
		You are prompted for your keyboard and language requirements. Enter these values as you would during the installation of Fedora.
	</div><div class="para">
		Next, a screen appears telling you that the program attempts to find a Fedora install to rescue. Select <span class="guibutton"><strong>Skip</strong></span> on this screen.
	</div><div class="para">
		After selecting <span class="guibutton"><strong>Skip</strong></span>, you are given a command prompt where you can access the partitions you would like to remove.
	</div><div class="para">
		First, type the command <code class="command">list-harddrives</code>. This command lists all hard drives on your system that are recognizable by the installation program, as well as their sizes in megabytes.
	</div><div class="warning"><h2>Warning</h2><div class="para">
			Be careful to remove only the necessary Fedora partitions. Removing other partitions could result in data loss or a corrupted system environment.
		</div></div><div class="para">
		To remove partitions, use the partitioning utility <code class="command">parted</code>. Start <code class="command">parted</code>, where <em class="replaceable"><code>/dev/hda</code></em> is the device on which to remove the partition:
	</div><pre class="screen">parted /dev/hda
</pre><div class="para">
		Using the <code class="command">print</code> command, view the current partition table to determine the minor number of the partition to remove:
	</div><pre class="screen">print
</pre><div class="para">
		The <code class="command">print</code> command also displays the partition's type (such as linux-swap, ext2, ext3, ext4 and so on). Knowing the type of the partition helps you in determining whether to remove the partition.
	</div><div class="para">
		Remove the partition with the command <code class="command">rm</code>. For example, to remove the partition with minor number 3:
	</div><pre class="screen">rm 3
</pre><div class="important"><h2>Important</h2><div class="para">
			The changes start taking place as soon as you press [Enter], so review the command before committing to it.
		</div></div><div class="para">
		After removing the partition, use the <code class="command">print</code> command to confirm that it is removed from the partition table.
	</div><div class="para">
		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><ul class="docnav"><li class="previous"><a accesskey="p" href="sn-x86-uninstall-dual-linux.html"><strong>Prev</strong>19.2.3.Â Your computer dual-boots Fedora and a dif...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="pt-Technical_appendixes.html"><strong>Next</strong>PartÂ V.Â Technical appendixes</a></li></ul></body></html>


--- NEW FILE vncwhitepaperadded.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ChapterÂ 12.Â Installing Through VNC</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="Fedora-Installation_Guide-11-en-US-1.0-1" /><link rel="home" href="index.html" title="Installation Guide" /><link rel="up" href="pt-Advanced_installation_options.html" title="PartÂ III.Â Advanced installation options" /><link rel="prev" href="netboot-performing.html" title="11.5.7.Â Performing the PXE Installation" /><link rel="next" href="VNC_Whitepaper-vnc-modes-in-anaconda.html" title="12.2.Â VNC Modes in Anaconda" /></head><body class="draft "><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_Cont
 ent/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="netboot-performing.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="VNC_Whitepaper-vnc-modes-in-anaconda.html"><strong>Next</strong></a></li></ul><div class="chapter" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="vncwhitepaperadded">ChapterÂ 12.Â Installing Through VNC</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="vncwhitepaperadded.html#VNC_Whitepaper-vnc-viewer">12.1. VNC Viewer</a></span></dt><dt><span class="section"><a href="VNC_Whitepaper-vnc-modes-in-anaconda.html">12.2. VNC Modes in Anaconda</a></span></dt><dd><dl><dt><span class="section"><a href="VNC_Whitepaper-vnc-modes-in-anaconda.html#VNC_Whitepaper-vnc-direct-mode">12.2.1. Direct Mode</a></span></dt><dt><span class="section"><a href="VNC_Whitepaper-vnc-connect-mode.html">12.2.2. Connect Mode
 </a></span></dt></dl></dd><dt><span class="section"><a href="VNC_Whitepaper-installation.html">12.3. Installation Using VNC</a></span></dt><dd><dl><dt><span class="section"><a href="VNC_Whitepaper-installation.html#VNC_Whitepaper-installation-example">12.3.1. Installation Example</a></span></dt><dt><span class="section"><a href="VNC_Whitepaper-kickstart-installation.html">12.3.2. Kickstart Considerations</a></span></dt><dt><span class="section"><a href="VNC_Whitepaper-firewall-considerations.html">12.3.3. Firewall Considerations</a></span></dt></dl></dd><dt><span class="section"><a href="VNC_Whitepaper-references.html">12.4. References</a></span></dt></dl></div><div class="para">
		The Red Hat Enterprise Linux and Fedora installer (<span class="application"><strong>anaconda</strong></span>) offers you two interactive modes of operation. The original mode is a text-based interface. The newer mode uses GTK+ and runs in the X Window environment. This chapter explains how you can use the graphical installation mode in environments where the system lacks a proper display and input devices typically associated with a workstation. This scenario is typical of systems in datacenters, which are often installed in a rack environment and do not have a display, keyboard, or mouse. Additionally, a lot of these systems even lack the ability to connect a graphical display. Given that enterprise hardware rarely needs that ability at the physical system, this hardware configuration is acceptable.
	</div><div class="para">
		Even in these environments, however, the graphical installer remains the recommended method of installation. The text mode environment lacks a lot of capabilities found in the graphical mode. Many users still feel that the text mode interface provides them with additional power or configuration ability not found in the graphical version. The opposite is true. Much less development effort is put in to the text-mode environment and specific things (for example, LVM configuration, partition layout, package selection, and bootloader configuration) are deliberately left out of the text mode environment. The reasons for this are:
	</div><div class="itemizedlist"><ul><li><div class="para">
				Less screen real estate for creating user interfaces similar to those found in the graphical mode.
			</div></li><li><div class="para">
				Difficult internationalization support.
			</div></li><li><div class="para">
				Desire to maintain a single interactive installation code path.
			</div></li></ul></div><div class="para">
		<span class="application"><strong>Anaconda</strong></span> therefore includes a <span class="application"><strong>Virtual Network Computing</strong></span> (VNC) mode that allows the graphical mode of the installer to run locally, but display on a system connected to the network. Installing in VNC mode provides you with the full range of installation options, even in situations where the system lacks a display or input devices.
	</div><div class="section" lang="en-US" xml:lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="VNC_Whitepaper-vnc-viewer">12.1.Â VNC Viewer</h2></div></div></div><div class="para">
		Performing a VNC installation requires a VNC viewer running on your workstation or other terminal computer. Locations where you might want a VNC viewer installed:
	</div><div class="itemizedlist"><ul><li><div class="para">
				Your workstation
			</div></li><li><div class="para">
				Laptop on a datacenter crash cart
			</div></li></ul></div><div class="para">
		VNC is open source software licensed under the GNU General Public License. Versions exist for Linux, Windows, and MacOS X. Here are some recommended VNC viewers:
	</div><div class="itemizedlist"><ul><li><div class="para">
				<code class="command">vncviewer</code> is available on <span class="application"><strong>Red Hat Enterprise Linux</strong></span> and <span class="application"><strong>Fedora Linux</strong></span> by installing the <code class="filename">vnc</code> package:
			</div><div class="para">
				
<pre class="screen">
# <strong class="userinput"><code>yum install vnc</code></strong>
</pre>
			</div></li><li><div class="para">
				TightVNC is available for Windows at <a href="http://www.tightvnc.com/">http://www.tightvnc.com/</a>
			</div></li><li><div class="para">
				MacOS X includes built-in VNC support as of version 10.5. In the <span class="application"><strong>Finder</strong></span>, click the <span class="guilabel"><strong>Go</strong></span> menu and choose <span class="guilabel"><strong>Connect to Server</strong></span>. In the server address field, you can type <code class="command">vnc://<em class="replaceable"><code>SERVER</code></em>:<em class="replaceable"><code>DISPLAY</code></em></code>, where SERVER is the IP address or DNS host name of the VNC server you wish to connect to and DISPLAY is the VNC display number (usually 1), and click <span class="guilabel"><strong>Connect</strong></span>.
			</div></li></ul></div><div class="para">
		Once you have verified you have a VNC viewer available, it's time to start the installation.
	</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="netboot-performing.html"><strong>Prev</strong>11.5.7.Â Performing the PXE Installation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="VNC_Whitepaper-vnc-modes-in-anaconda.html"><strong>Next</strong>12.2.Â VNC Modes in Anaconda</a></li></ul></body></html>