From owner-svn-doc-head@FreeBSD.ORG Thu Apr 24 23:01:57 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 67E031AA; Thu, 24 Apr 2014 23:01:57 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 53B201B2E; Thu, 24 Apr 2014 23:01:57 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s3ON1vWh087536; Thu, 24 Apr 2014 23:01:57 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s3ON1vSW087535; Thu, 24 Apr 2014 23:01:57 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201404242301.s3ON1vSW087535@svn.freebsd.org> From: Dru Lavigne Date: Thu, 24 Apr 2014 23:01:57 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44655 - head/en_US.ISO8859-1/books/handbook/bsdinstall X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Apr 2014 23:01:57 -0000 Author: dru Date: Thu Apr 24 23:01:56 2014 New Revision: 44655 URL: http://svnweb.freebsd.org/changeset/doc/44655 Log: White space fix only. Translators can ignore. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml Thu Apr 24 22:11:46 2014 (r44654) +++ head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml Thu Apr 24 23:01:56 2014 (r44655) @@ -20,8 +20,8 @@ Mock - Restructured, reorganized, and parts - rewritten by + Restructured, reorganized, and parts rewritten + by @@ -79,8 +79,8 @@ sysinstall for installation. This chapter describes the use of bsdinstall. The use of - sysinstall is covered in - . + sysinstall is covered in . After reading this chapter, you will know: @@ -145,14 +145,15 @@ &os;/&arch.i386; &os;/&arch.i386; requires a 486 or better processor and - at least 64 MB of RAM. At least 1.1 GB of free - hard drive space is needed for the most minimal - installation. + at least 64 MB of RAM. At least + 1.1 GB of free hard drive space is needed for the most + minimal installation. - On old computers, increasing RAM and hard drive space - is usually more effective at improving performance than - installing a faster processor. + On old computers, increasing RAM + and hard drive space is usually more effective at + improving performance than installing a faster + processor. @@ -161,9 +162,8 @@ There are two classes of processors capable of running &os;/&arch.amd64;. The first are AMD64 processors, - including the &amd.athlon;64, - &amd.athlon;64-FX, &amd.opteron; or better - processors. + including the &amd.athlon;64, &amd.athlon;64-FX, + &amd.opteron; or better processors. The second class of processors that can use &os;/&arch.amd64; includes those using the @@ -174,22 +174,25 @@ &intel; &xeon; E3, E5 and E7 processors, and the &intel; &core; i3, i5 and i7 processors. - If the system is based on an nVidia nForce3 - Pro-150, the IO APIC must be disabled - in the BIOS setup. If this BIOS option does not exist, - disable ACPI instead. + If the system is based on an nVidia nForce3 Pro-150, the + IO APIC + must be disabled in the + BIOS setup. If this + BIOS option does not exist, disable + ACPI instead. &os;/&arch.powerpc; &apple; &macintosh; All New World &apple; &macintosh; systems with built-in - USB are supported. SMP is supported on machines with + USB are supported. + SMP is supported on machines with multiple CPUs. - A 32-bit kernel can only use the first 2 GB of RAM. - &firewire; is not supported on the Blue & White PowerMac - G3. + A 32-bit kernel can only use the first 2 GB of + RAM. &firewire; is not supported on the + Blue & White PowerMac G3. @@ -224,21 +227,20 @@ Back Up Important Data - Back up all important data on the target computer - where &os; will be installed. Test the backups before - continuing. The &os; installer will ask before making changes - to the disk, but once the process has started it cannot be - undone. + Back up all important data on the target computer where + &os; will be installed. Test the backups before continuing. + The &os; installer will ask before making changes to the disk, + but once the process has started it cannot be undone. Decide Where to Install &os; If &os; will be the only operating system installed, and - will be allowed to use the entire hard disk, the rest of - this section can be skipped. But if &os; will share the disk - with other operating systems, an understanding of disk - layout is useful during the installation. + will be allowed to use the entire hard disk, the rest of this + section can be skipped. But if &os; will share the disk with + other operating systems, an understanding of disk layout is + useful during the installation. Disk Layouts for &os;/&arch.i386; and @@ -250,38 +252,37 @@ <para>There are two ways of dividing a disk into partitions. A traditional <firstterm>Master Boot Record</firstterm> - (<acronym>MBR</acronym>) holds a - partition table defining up to four <firstterm>primary - partitions</firstterm>. For historical reasons, &os; - calls primary partitions <firstterm>slices</firstterm>. A - limit of only four partitions is restrictive for large - disks, so one of these primary partitions can be made into - an <firstterm>extended partition</firstterm>. Multiple - <firstterm>logical partitions</firstterm> may then be - created inside the extended partition. This may sound a - little unwieldy, and it is.</para> + (<acronym>MBR</acronym>) holds a partition table defining up + to four <firstterm>primary partitions</firstterm>. For + historical reasons, &os; calls primary partitions + <firstterm>slices</firstterm>. A limit of only four + partitions is restrictive for large disks, so one of these + primary partitions can be made into an <firstterm>extended + partition</firstterm>. Multiple <firstterm>logical + partitions</firstterm> may then be created inside the + extended partition. This may sound a little unwieldy, and + it is.</para> <para>The <firstterm>GUID Partition Table</firstterm> - (<acronym>GPT</acronym>) is a - newer and simpler method of partitioning a disk. - <acronym>GPT</acronym> is far - more versatile than the traditional <acronym>MBR </acronym>partition table. - Common <acronym>GPT</acronym> implementations allow up to - 128 partitions per disk, eliminating the need for - inconvenient workarounds like logical partitions.</para> + (<acronym>GPT</acronym>) is a newer and simpler method of + partitioning a disk. <acronym>GPT</acronym> is far more + versatile than the traditional <acronym>MBR</acronym> + partition table. Common <acronym>GPT</acronym> + implementations allow up to 128 partitions per disk, + eliminating the need for inconvenient workarounds like + logical partitions.</para> <warning> <para>Some older operating systems, like &windows; XP, are not compatible with the <acronym>GPT</acronym> partition scheme. If &os; will be sharing a disk with - such an operating system, - <acronym>MBR</acronym> + such an operating system, <acronym>MBR</acronym> partitioning is required.</para> </warning> <para>&os;'s standard boot loader requires either a primary or - <acronym>GPT</acronym> partition. Refer to - <xref linkend="boot"/> for more information about the &os; + <acronym>GPT</acronym> partition. Refer to <xref + linkend="boot"/> for more information about the &os; booting process. If all of the primary or <acronym>GPT</acronym> partitions are already in use, one must be freed for &os;.</para> @@ -311,8 +312,8 @@ </warning> <para>Resizing µsoft; Vista partitions can be - difficult. A Vista installation <acronym>CD</acronym> can be useful when - attempting such an operation.</para> + difficult. A Vista installation <acronym>CD</acronym> can + be useful when attempting such an operation.</para> <example> <title>Using an Existing Partition @@ -320,14 +321,14 @@ A &windows; computer has a single 40 GB disk that has been split into two 20 GB partitions. &windows; calls them C: and - D:. The - C: partition contains 10 GB - of data, and the D: partition - contains 5 GB of data. + D:. The C: + partition contains 10 GB of data, and the + D: partition contains 5 GB of + data. Moving the data from D: to - C: frees up the second partition - to be used for &os;. + C: frees up the second partition to + be used for &os;. @@ -372,14 +373,15 @@ Some &os; installation methods need a network connection to download files. To connect to an Ethernet network (or - cable or DSL modem with an Ethernet interface), the installer - will request some information about the network. - - DHCP is commonly - used to provide automatic network configuration. If - DHCP is not available, this network - information must be obtained from the local network - administrator or service provider: + cable or DSL modem with an Ethernet + interface), the installer will request some information about + the network. + + DHCP is commonly used to provide + automatic network configuration. If DHCP + is not available, this network information must be obtained + from the local network administrator or service + provider: Network Information @@ -417,9 +419,9 @@ affect the installation process. As these problems are discovered and fixed, they are noted in the &os; Errata (http://www.freebsd.org/releases/&rel.current;R/errata.html) - on the &os; web site. Check the errata before - installing to make sure that there are no problems that might - affect the installation. + on the &os; web site. Check the errata before installing to + make sure that there are no problems that might affect the + installation. Information and errata for all the releases can be found on the release information section of the &os; web site (Prepare the Installation Media A &os; installation is started by booting the computer - with a &os; installation CD, DVD, or USB memory stick. The - installer is not a program that can be run from within another - operating system. + with a &os; installation CD, + DVD, or USB memory + stick. The installer is not a program that can be run from + within another operating system. In addition to the standard installation media which contains copies of all the &os; installation files, there is a bootonly variant. Bootonly install media does not have copies of the installation files, but downloads them from the network during an install. The bootonly install - CD is consequently much smaller, and reduces bandwidth usage - during the install by only downloading required files. - - Copies of &os; installation media are available at - www.freebsd.org/where.html#download. - Also download - CHECKSUM.SHA256 from the same directory - as the image file, and use it to check the image file's - integrity by calculating a checksum. - &os; provides &man.sha256.1; for this, while other operating - systems have similar programs. Compare the calculated - checksum with the one shown in + CD is consequently much smaller, and + reduces bandwidth usage during the install by only downloading + required files. + + Copies of &os; installation media are available at www.freebsd.org/where.html#download. + Also download CHECKSUM.SHA256 from the + same directory as the image file, and use it to check the + image file's integrity by calculating a + checksum. &os; provides &man.sha256.1; + for this, while other operating systems have similar programs. + Compare the calculated checksum with the one shown in CHECKSUM.SHA256. The checksums must match exactly. If the checksums do not match, the file is corrupt and should be discarded. - If a copy of &os; already exists on CD, DVD, or USB - memory stick, this section can be skipped. + If a copy of &os; already exists on + CD, DVD, or + USB memory stick, this section can be + skipped. - &os; CD and DVD images are bootable ISO files. Only one - CD or DVD is needed for an install. Burn the ISO image to a - bootable CD or DVD using the burning applications - available with the current operating system. On &os;, - recording is provided by cdrecord from - sysutils/cdrtools, installed - from the Ports Collection. + &os; CD and DVD + images are bootable ISO files. Only one + CD or DVD is needed for + an install. Burn the ISO image to a + bootable CD or DVD using + the burning applications available with the current operating + system. On &os;, recording is provided by + cdrecord from + sysutils/cdrtools, installed from the Ports + Collection. To create a bootable memory stick, follow these steps: @@ -481,11 +489,10 @@ directory at ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/arch/arch/ISO-IMAGES/version/&os;-version-RELEASE-arch-memstick.img. Replace arch and - version with the - architecture and the version number to - install, respectively. For example, the memory stick - images for &os;/&arch.i386; 9.0-RELEASE are - available from version with the architecture + and the version number to install, respectively. For + example, the memory stick images for + &os;/&arch.i386; 9.0-RELEASE are available from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/&arch.i386;/ISO-IMAGES/9.0/&os;-9.0-RELEASE-&arch.i386;-memstick.img. @@ -519,8 +526,8 @@ The example below shows /dev/da0 as the target device where the image will be written. Be very careful that - the correct device is used as the output target, as this command will - destroy existing data. + the correct device is used as the output target, as + this command will destroy existing data. @@ -529,10 +536,9 @@ The .img file is not a regular file. It is an image of the complete contents of - the memory stick. It cannot - be copied like a regular file, but must be - written directly to the target device with - &man.dd.1;: + the memory stick. It cannot be + copied like a regular file, but must be written + directly to the target device with &man.dd.1;: &prompt.root; dd if=&os;-9.0-RELEASE-&arch.i386;-memstick.img of=/dev/da0 bs=64k @@ -603,9 +609,9 @@ commit your changes? The install can be exited at any time prior to this warning without changing the contents of the hard drive. If - there is a concern that something is - incorrectly configured, just turn the computer off before this - point, and no damage will be done. + there is a concern that something is incorrectly configured, + just turn the computer off before this point, and no damage + will be done. @@ -616,24 +622,25 @@ commit your changes? - When using a prepared bootable USB stick, - as described in - , - plug in the USB stick before turning on the + When using a prepared bootable USB + stick, as described in , plug in the + USB stick before turning on the computer. - When booting from CD, - turn on the computer and insert the CD at the first - opportunity. + When booting from CD, turn on the + computer and insert the CD at the + first opportunity. - Configure the system to boot from either the CD - or from USB, depending on the media being used for the - installation. BIOS configurations - allow the selection of a specific boot device. Most - systems also provide for selecting a boot device during - startup, typically by pressing F10, + Configure the system to boot from either the + CD or from USB, + depending on the media being used for the installation. + BIOS configurations allow the + selection of a specific boot device. Most systems also + provide for selecting a boot device during startup, + typically by pressing F10, F11, F12, or Escape. @@ -645,31 +652,32 @@ commit your changes? The disks were not inserted early enough in the - boot process. Leave them in, and try restarting - the computer. + boot process. Leave them in, and try restarting the + computer. The BIOS changes earlier did - not work correctly. Redo that step until - the right option is selected. + not work correctly. Redo that step until the right + option is selected. This particular BIOS does not - support booting from the desired media. The + support booting from the desired media. The Plop Boot Manager (http://www.plop.at/en/bootmanager.html) - can be used to boot older - computers from CD or USB media. + can be used to boot older computers from + CD or USB + media. &os; will start to boot. When booting from - CD, messages similar to this will be displayed (version - information omitted): + CD, messages similar to this will be + displayed (version information omitted): Booting from CD-ROM... 645MB medium detected @@ -718,7 +726,8 @@ Loading /boot/defaults/loader.conf Booting for &macintosh; &powerpc; On most machines, holding C on the - keyboard during boot will boot from the CD. Otherwise, hold + keyboard during boot will boot from the + CD. Otherwise, hold Command Option @@ -739,19 +748,16 @@ Loading /boot/defaults/loader.conf For Xserves without keyboards, refer to http://support.apple.com/kb/TA26930 - about booting into Open - Firmware. + about booting into Open Firmware. Booting for &sparc64; Most &sparc64; systems are set up to boot automatically - from disk. To install &os;, booting over the - network or from a CD requires a break into - the - PROM - (OpenFirmware). + from disk. To install &os;, booting over the network or + from a CD requires a break into the + PROM (OpenFirmware). To do this, reboot the system, and wait until the boot message appears. It depends on the model, but should look @@ -763,17 +769,14 @@ OpenBoot 4.2, 128 MB memory installed, S Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. If the system proceeds to boot from disk at this point, - press - L1A - or - StopA on the keyboard, or send a BREAK over the serial console (using for example ~# in &man.tip.1; or &man.cu.1;) to get to the - PROM - prompt. It looks like this: + PROM prompt. It looks like this: ok ok {0} @@ -785,13 +788,14 @@ Ethernet address 0:3:ba:b:92:d4, Host ID - This is the prompt used on SMP systems, the digit - indicates the number of the active CPU. + This is the prompt used on SMP + systems, the digit indicates the number of the active + CPU. - At this point, place the CD into the drive, and from - the PROM prompt, type + At this point, place the CD into the + drive, and from the PROM prompt, type boot cdrom. @@ -803,17 +807,16 @@ Ethernet address 0:3:ba:b:92:d4, Host ID screen are stored and can be reviewed. To review the buffer, press Scroll Lock. - This turns on scrolling in the display. Use the - arrow keys, or PageUp and - PageDown, to view the results. Press - Scroll Lock again to stop scrolling. + This turns on scrolling in the display. Use the arrow keys, + or PageUp and PageDown, to + view the results. Press Scroll Lock again to + stop scrolling. Do this now, to review the text that scrolled off the screen when the kernel was carrying out the device probes. - Text similar to - will be displayed, although the precise - text will differ depending on the devices in - the computer. + Text similar to will be + displayed, although the precise text will differ depending on + the devices in the computer.
Typical Device Probe Results @@ -968,19 +971,19 @@ Trying to mount root from cd9660:/dev/is
Check the probe results carefully to make sure that &os; - found all the devices. If a device was not - found, it will not be listed. Refer to - - for instructions on how to add in support for devices - which are not in the GENERIC - kernel. + found all the devices. If a device was not found, it will not + be listed. Refer to for instructions on + how to add in support for devices which are not in the + GENERIC kernel. After the procedure of device probing, the menu shown in - will be displayed. The install media - can be used in three ways: to install &os;, as a live CD as described in - , or - to access a &os; shell. Use the arrow keys to choose - an option, and Enter to select. + will be displayed. + The install media can be used in three ways: to install &os;, + as a live CD as described in , or to access a &os; shell. Use + the arrow keys to choose an option, and Enter + to select.
Selecting Installation Media Mode @@ -1007,8 +1010,8 @@ Trying to mount root from cd9660:/dev/is &a.kmoore.email;'s pc-sysinstall is included with - PC-BSD and can - be used to install &os; using the instructions at http://wiki.pcbsd.org/index.php/Use_PC-BSD_Installer_to_Install_FreeBSD. Although sometimes confused with bsdinstall, the two are not @@ -1124,8 +1127,9 @@ Trying to mount root from cd9660:/dev/is Deciding which components to install will depend largely on the intended use of the system and the amount of disk space - available. The &os; kernel and userland, collectively known as the - base system, are always installed. + available. The &os; kernel and userland, collectively known + as the base system, are always + installed. Depending on the type of installation, some of these components may not appear. @@ -1141,8 +1145,9 @@ Trying to mount root from cd9660:/dev/is - games - Several traditional BSD - games, including fortune, + games - Several traditional + BSD games, including + fortune, rot13, and others. @@ -1167,9 +1172,9 @@ Trying to mount root from cd9660:/dev/is The installation program does not check for adequate disk space. Select this option only if - sufficient hard disk space is available. The - &os; Ports Collection takes up about &ports.size; of - disk space. + sufficient hard disk space is available. The &os; Ports + Collection takes up about &ports.size; of disk + space. @@ -1242,10 +1247,10 @@ Trying to mount root from cd9660:/dev/is allows advanced users to create customized partitions. The ZFS option, only available in &os; 10 and later, will create an optionally encrypted root-on-ZFS system - with support for Boot Environments. Finally, - there's the option of starting a shell where command-line - programs like &man.gpart.8;, &man.fdisk.8;, and &man.bsdlabel.8; - can be used directly. + with support for Boot Environments. Finally, there's the option + of starting a shell where command-line programs like + &man.gpart.8;, &man.fdisk.8;, and &man.bsdlabel.8; can be used + directly.
Selecting Guided, Manual or Shell Partitioning @@ -1269,12 +1274,12 @@ Trying to mount root from cd9660:/dev/is
- This section describes what to consider when laying - out the disk partitions. It then demonstrates how to use both - the Guided Partitioning and Manual Partitioning screens. - - - Designing the Partition Layout + This section describes what to consider when laying out the + disk partitions. It then demonstrates how to use both the + Guided Partitioning and Manual Partitioning screens. + + + Designing the Partition Layout partition layout @@ -1287,86 +1292,86 @@ Trying to mount root from cd9660:/dev/is /usr - When laying out file systems, remember that hard drives transfer data - faster from the outer tracks to the inner. Thus, smaller - and heavier-accessed file systems should be closer to the - outside of the drive, while larger partitions like - /usr should be placed toward the inner - parts of the disk. It is a good idea to create partitions - in an order similar to: /, swap, - /var, and - /usr. - - The size of the /var partition - reflects the intended machine's usage. This partition is - used to hold mailboxes, log files, and printer spools. - Mailboxes and log files can grow to unexpected sizes - depending on the number of users and how long log files are - kept. On average, most users rarely need more than about a - gigabyte of free disk space in - /var. + When laying out file systems, remember that hard drives + transfer data faster from the outer tracks to the inner. + Thus, smaller and heavier-accessed file systems should be + closer to the outside of the drive, while larger partitions + like /usr should be placed toward the + inner parts of the disk. It is a good idea to create + partitions in an order similar to: /, + swap, /var, and + /usr. + + The size of the /var partition + reflects the intended machine's usage. This partition is + used to hold mailboxes, log files, and printer spools. + Mailboxes and log files can grow to unexpected sizes + depending on the number of users and how long log files are + kept. On average, most users rarely need more than about a + gigabyte of free disk space in + /var. - - Sometimes, a lot of disk space is required in - /var/tmp. When new software is - installed, the packaging tools - extract a temporary copy of the packages under - /var/tmp. Large software packages, - like Firefox, - OpenOffice or - LibreOffice may be tricky to - install if there is not enough disk space under - /var/tmp. - + + Sometimes, a lot of disk space is required in + /var/tmp. When new software is + installed, the packaging tools extract a temporary copy of + the packages under /var/tmp. Large + software packages, like Firefox, + OpenOffice or + LibreOffice may be tricky to + install if there is not enough disk space under + /var/tmp. + + + The /usr partition holds many of the + files which support the system, including the &os; Ports + Collection and system source code. At least 2 gigabytes is + recommended for this partition. + + When selecting partition sizes, keep the space + requirements in mind. Running out of space in one partition + while barely using another can be a hassle. + + + swap sizing + + + swap partition + + + As a rule of thumb, the swap partition should be about + double the size of physical memory (RAM). + Systems with minimal RAM may perform + better with more swap. Configuring too little swap can lead + to inefficiencies in the VM page scanning + code and might create issues later if more memory is + added. + + On larger systems with multiple SCSI + disks or multiple IDE disks operating on + different controllers, it is recommended that swap be + configured on each drive, up to four drives. The swap + partitions should be approximately the same size. The + kernel can handle arbitrary sizes but internal data structures + scale to 4 times the largest swap partition. Keeping the swap + partitions near the same size will allow the kernel to + optimally stripe swap space across disks. Large swap sizes + are fine, even if swap is not used much. It might be easier + to recover from a runaway program before being forced to + reboot. + + By properly partitioning a system, fragmentation + introduced in the smaller write heavy partitions will not + bleed over into the mostly read partitions. Keeping the + write loaded partitions closer to the disk's edge will + increase I/O performance in the + partitions where it occurs the most. While + I/O performance in the larger partitions + may be needed, shifting them more toward the edge of the disk + will not lead to a significant performance improvement over + moving /var to the edge. + - The /usr partition holds many of - the files which support the system, including the &os; Ports - Collection and system source code. At least 2 gigabytes is - recommended for this partition. - - When selecting partition sizes, keep the space - requirements in mind. Running out of space in one partition - while barely using another can be a hassle. - - - swap sizing - - - swap partition - - - As a rule of thumb, the swap partition should be about - double the size of physical memory (RAM). - Systems with minimal RAM may perform - better with more swap. Configuring too little swap can - lead to inefficiencies in the VM page - scanning code and might create issues later if more memory - is added. - - On larger systems with multiple SCSI - disks or multiple IDE disks operating - on different controllers, it is recommended that swap be - configured on each drive, up to four drives. The swap - partitions should be approximately the same size. The - kernel can handle arbitrary sizes but internal data - structures scale to 4 times the largest swap partition. - Keeping the swap partitions near the same size will allow - the kernel to optimally stripe swap space across disks. - Large swap sizes are fine, even if swap is not used much. - It might be easier to recover from a runaway program before - being forced to reboot. - - By properly partitioning a system, fragmentation - introduced in the smaller write heavy partitions will not - bleed over into the mostly read partitions. Keeping the - write loaded partitions closer to the disk's edge will - increase I/O performance in the partitions where it occurs - the most. While I/O performance in the larger partitions - may be needed, shifting them more toward the edge of the - disk will not lead to a significant performance improvement - over moving /var to the edge. - - Guided Partitioning @@ -1384,8 +1389,8 @@ Trying to mount root from cd9660:/dev/is
- The entire disk or a portion of it can be allocated to &os;. - If + The entire disk or a portion of it can be allocated to + &os;. If [ Entire Disk ] is chosen, a general partition layout filling the whole disk is created. Selecting @@ -1441,8 +1446,8 @@ Trying to mount root from cd9660:/dev/is - Highlighting a drive (ada0 in - this example) and selecting + Highlighting a drive (ada0 in this + example) and selecting [ Create ] displays a menu for choosing the type of partitioning scheme. @@ -1480,7 +1485,7 @@ Trying to mount root from cd9660:/dev/is APM Apple Partition Map, used by &powerpc; - &macintosh; (http://support.apple.com/kb/TA21692). @@ -1545,8 +1550,8 @@ Trying to mount root from cd9660:/dev/is - freebsd-ufs - A &os; UFS - file system. + freebsd-ufs - A &os; UFS file + system. @@ -1557,17 +1562,16 @@ Trying to mount root from cd9660:/dev/is Another partition type worth noting is freebsd-zfs, used for partitions that will - contain a &os; ZFS file system. - . &man.gpart.8; shows more - of the available GPT partition - types. + contain a &os; ZFS file system. . &man.gpart.8; shows more of + the available GPT partition types. Multiple file system partitions can be used, and some people may prefer a traditional layout with separate partitions for the /, /var, /tmp, and - /usr file systems. See - for an + /usr file systems. See for an example. Size may be entered with common abbreviations: @@ -1598,10 +1602,10 @@ Trying to mount root from cd9660:/dev/is and partition numbers in files like /etc/fstab makes the system more tolerant of changing hardware. GPT labels appear in - /dev/gpt/ when a disk is attached. - Other partitioning schemes have different label - capabilities, and their labels appear in different directories - in /dev/. + /dev/gpt/ when a disk is attached. Other + partitioning schemes have different label capabilities, and + their labels appear in different directories in + /dev/. Use a unique label on every file system to avoid @@ -1620,14 +1624,14 @@ Trying to mount root from cd9660:/dev/is /, /var, /tmp, and /usr directories are separate file systems on their own - partitions, create a GPT partitioning scheme, then create - the partitions as shown. Partition sizes shown are typical - for a 20G target disk. If more space is available on the - target disk, larger swap or /var - partitions may be useful. Labels shown here are prefixed - with ex for example, but - readers should use other unique label values as described - above. + partitions, create a GPT partitioning + scheme, then create the partitions as shown. Partition + sizes shown are typical for a 20G target disk. If more + space is available on the target disk, larger swap or + /var partitions may be useful. Labels + shown here are prefixed with ex for + example, but readers should use other unique + label values as described above. By default, &os;'s gptboot expects the first UFS partition found to be the @@ -1732,22 +1736,22 @@ Trying to mount root from cd9660:/dev/is - The most important option is selecting the vdev type - and one or more disks that will make up the vdev that will + The most important option is selecting the vdev type and + one or more disks that will make up the vdev that will constitute the pool. The automatic ZFS installer currently only supports the creation of a single top level vdev, except in stripe mode. To create more complex pools, use the instructions in to create - the pool. The installer supports the creation of various - pool types, including stripe (not recommended, no redundancy), - mirror (best performance, least usable space), and RAID-Z 1, - 2, and 3 (with the capability to withstand the concurrent - failure of 1, 2, and 3 disks, respectively). A tooltip across - the bottom of the screen while selecting the pool type - provides advice about the number of required disks for each - type, and in the case of RAID-Z, the optimal number of disks - for each configuration. + linkend="bsdinstall-part-shell"/> to create the pool. The + installer supports the creation of various pool types, + including stripe (not recommended, no redundancy), mirror + (best performance, least usable space), and RAID-Z 1, 2, and 3 + (with the capability to withstand the concurrent failure of 1, + 2, and 3 disks, respectively). A tooltip across the bottom of + the screen while selecting the pool type provides advice about + the number of required disks for each type, and in the case of + RAID-Z, the optimal number of disks for each + configuration.
<acronym>ZFS</acronym> Pool Type @@ -1773,7 +1777,8 @@ Trying to mount root from cd9660:/dev/is - +
@@ -1783,13 +1788,14 @@ Trying to mount root from cd9660:/dev/is - + - If one or more disks are missing from the list, or if disks - were attached after the installer was started, select + If one or more disks are missing from the list, or if + disks were attached after the installer was started, select - Rescan Devices to repopulate the list *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***