From owner-svn-doc-head@FreeBSD.ORG Tue May 20 20:46:30 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 585E3EB7; Tue, 20 May 2014 20:46:30 +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 434172105; Tue, 20 May 2014 20:46:30 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s4KKkUqe079609; Tue, 20 May 2014 20:46:30 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s4KKkUIR079608; Tue, 20 May 2014 20:46:30 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201405202046.s4KKkUIR079608@svn.freebsd.org> From: Dru Lavigne Date: Tue, 20 May 2014 20:46:30 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44890 - 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.18 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: Tue, 20 May 2014 20:46:30 -0000 Author: dru Date: Tue May 20 20:46:29 2014 New Revision: 44890 URL: http://svnweb.freebsd.org/changeset/doc/44890 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 Tue May 20 20:08:17 2014 (r44889) +++ head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml Tue May 20 20:46:29 2014 (r44890) @@ -80,22 +80,21 @@ program used by &os; 8.x, is covered in . - In general, the installation instructions in this chapter are written - for the &i386; and AMD64 architectures. - Where applicable, instructions specific to other - platforms will be listed. There may be minor differences - between the installer and what is shown here, so use this - chapter as a general guide rather than as a set of literal - instructions. + In general, the installation instructions in this chapter + are written for the &i386; and AMD64 + architectures. Where applicable, instructions specific to other + platforms will be listed. There may be minor differences + between the installer and what is shown here, so use this + chapter as a general guide rather than as a set of literal + instructions. Users who prefer to install &os; using a graphical - installer may be interested in + installer may be interested in pc-sysinstall, the installer used - by the - PC-BSD Project. It can be used to install either a graphical - desktop (PC-BSD) or a command line version of &os;. Refer to - the PC-BSD Users Handbook for details (http://wiki.pcbsd.org/index.php/PC-BSD%C2%AE_Users_Handbook/10.1). @@ -141,135 +140,136 @@ Minimum Hardware Requirements - The hardware requirements to install &os; vary by the - &os; version and the hardware architecture. Hardware - architectures and devices supported by a &os; - release are listed in the Hardware Notes file. Usually named - HARDWARE.TXT, the file is located in the - root directory of the release media. Copies of the supported - hardware list are also available on the Release Information - page of the &os; web site (http://www.FreeBSD.org/releases/index.html). - - A &os; installation will require at least 64 MB of - RAM and 1.1 GB of free hard drive - space for the most minimal installation. However, that is a - very minimal install, leaving almost no - free space. A more realistic minimum is 3 GB without a - graphical environment, and 5 GB or more if a graphical - user interface will be used. Third-party application - software requires more space. It is recommended to - increase RAM and hard drive space to meet - the needs of the applications that will be used and the amount - of data that will be stored. + The hardware requirements to install &os; vary by the &os; + version and the hardware architecture. Hardware architectures + and devices supported by a &os; release are listed in the + Hardware Notes file. Usually named + HARDWARE.TXT, the file is located in the + root directory of the release media. Copies of the supported + hardware list are also available on the Release Information page + of the &os; web site (http://www.FreeBSD.org/releases/index.html). + + A &os; installation will require at least 64 MB of + RAM and 1.1 GB of free hard drive space + for the most minimal installation. However, that is a + very minimal install, leaving almost no + free space. A more realistic minimum is 3 GB without a + graphical environment, and 5 GB or more if a graphical user + interface will be used. Third-party application software + requires more space. It is recommended to increase + RAM and hard drive space to meet the needs of + the applications that will be used and the amount of data that + will be stored. - The processor requirements for - each architecture can be summarized as follows: + The processor requirements for each architecture can be + summarized as follows: - + &arch.amd64; - There are two classes of processors capable of running - &arch.amd64;. The first are AMD64 processors, - including the &amd.athlon;64 and - &amd.opteron; processors. - - The second class of processors includes those using the - &intel; EM64T architecture. Examples of these - processors include all multi-core &intel; &xeon; - processors except Sossaman, the single-core - &intel; &xeon; processors Nocona, Irwindale, Potomac, - and Cranford, the &intel; &core; 2 (not Core Duo) - and later processors, all &intel; &pentium; D processors, the - &intel; &pentium; 4s and Celeron Ds using the Cedar - Mill core, and some &intel; &pentium; 4s and Celeron Ds - using the Prescott core. - - Both Uniprocessor (UP) and Symmetric - Multi-processor (SMP) configurations are - supported. - + There are two classes of processors capable of running + &arch.amd64;. The first are AMD64 + processors, including the &amd.athlon;64 and &amd.opteron; + processors. + + The second class of processors includes those using + the &intel; EM64T architecture. Examples of these + processors include all multi-core &intel; &xeon; + processors except Sossaman, the single-core + &intel; &xeon; processors Nocona, Irwindale, Potomac, + and Cranford, the &intel; &core; 2 (not Core + Duo) and later processors, all &intel; &pentium; D + processors, the &intel; &pentium; 4s and Celeron Ds + using the Cedar Mill core, and some &intel; &pentium; + 4s and Celeron Ds using the Prescott core. + + Both Uniprocessor (UP) and + Symmetric Multi-processor (SMP) + configurations are supported. + - - &arch.i386; - - Almost all i386-compatible processors with a floating - point unit are supported. All &intel; processors - 486 or higher are supported. - - &os; will take advantage of Physical Address Extensions - (PAE) support on CPUs - that support this feature. A kernel with the - PAE feature enabled will detect memory - above 4 GB and allow it to be used by the system. - This feature places constraints on the device drivers and - other features of &os; which may be used; refer to - &man.pae.4; for details. - + + &arch.i386; + + Almost all i386-compatible processors with a floating + point unit are supported. All &intel; processors 486 or + higher are supported. + + &os; will take advantage of Physical Address + Extensions (PAE) support on + CPUs that support this feature. A + kernel with the PAE feature enabled + will detect memory above 4 GB and allow it to be used + by the system. This feature places constraints on the + device drivers and other features of &os; which may be + used; refer to &man.pae.4; for details. ia64 - Currently supported processors are the &itanium; and the - &itanium; 2. Supported chipsets include the HP zx1, &intel; - 460GX, and &intel; E8870. Both Uniprocessor - (UP) and Symmetric Multi-processor - (SMP) configurations are supported. - + Currently supported processors are the &itanium; and + the &itanium; 2. Supported chipsets include the HP zx1, + &intel; 460GX, and &intel; E8870. Both Uniprocessor + (UP) and Symmetric Multi-processor + (SMP) configurations are + supported. + pc98 - NEC PC-9801/9821 series with almost all i386-compatible - processors, including 80486, &pentium;, &pentium; Pro, and - &pentium; II, are all supported. All i386-compatible processors - by AMD, Cyrix, IBM, and IDT are also supported. EPSON - PC-386/486/586 series, which are compatible with NEC PC-9801 - series, are supported. The NEC FC-9801/9821 and NEC SV-98 - series should be supported. - - High-resolution mode is not supported. NEC - PC-98XA/XL/RL/XL^2, and NEC PC-H98 series are supported in - normal (PC-9801 compatible) mode only. The - SMP-related features of &os; are not - supported. The New Extend Standard Architecture - (NESA) bus used in the PC-H98, SV-H98, - and FC-H98 series, is not supported. - + NEC PC-9801/9821 series with almost all + i386-compatible processors, including 80486, &pentium;, + &pentium; Pro, and &pentium; II, are all supported. All + i386-compatible processors by AMD, Cyrix, IBM, and IDT are + also supported. EPSON PC-386/486/586 series, which are + compatible with NEC PC-9801 series, are supported. The + NEC FC-9801/9821 and NEC SV-98 series should be + supported. + + High-resolution mode is not supported. NEC + PC-98XA/XL/RL/XL^2, and NEC PC-H98 series are supported in + normal (PC-9801 compatible) mode only. The + SMP-related features of &os; are not + supported. The New Extend Standard Architecture + (NESA) bus used in the PC-H98, SV-H98, + and FC-H98 series, is not supported. + &arch.powerpc; - All New World ROM &apple; &macintosh; systems with built-in - USB are supported. - SMP is supported on machines with - multiple CPUs. + All New World ROM &apple; + &macintosh; systems with built-in USB + are supported. SMP is supported on + machines with multiple CPUs. - A 32-bit kernel can only use the first 2 GB of - RAM. - + A 32-bit kernel can only use the first 2 GB of + RAM. + - + &arch.sparc64; - Systems supported by &os;/&arch.sparc64; are listed at - the FreeBSD/sparc64 Project (http://www.freebsd.org/platforms/sparc.html). - - SMP is supported on all systems with - more than 1 processor. A dedicated disk is required as - it is not possible to share a disk with another operating - system at this time. - - - + Systems supported by &os;/&arch.sparc64; are listed at + the FreeBSD/sparc64 Project (http://www.freebsd.org/platforms/sparc.html). + + SMP is supported on all systems + with more than 1 processor. A dedicated disk is required + as it is not possible to share a disk with another + operating system at this time. + + + @@ -283,38 +283,40 @@ checklist: - - Back Up Important Data + + Back Up Important Data - Before installing any operating system, - always backup all important data first. - Do not store the backup on the system being installed. - Instead, save the data to a removable disk such as a - USB drive, another system on the network, - or an online backup service. Test the backup before - starting the installation to make sure it contains all of the - needed files. Once the installer formats the system's disk, - all data stored on that disk will be lost. - - - - Decide Where to Install &os; - - If &os; will be the only operating system installed, this - step can be skipped. But if &os; will share the disk with - another operating system, decide which disk or partition will - be used for &os;. + Before installing any operating system, + always backup all important data first. + Do not store the backup on the system being installed. + Instead, save the data to a removable disk such as a + USB drive, another system on the network, + or an online backup service. Test the backup before + starting the installation to make sure it contains all of + the needed files. Once the installer formats the system's + disk, all data stored on that disk will be lost. + + + + Decide Where to Install &os; + + If &os; will be the only operating system installed, + this step can be skipped. But if &os; will share the disk + with another operating system, decide which disk or + partition will be used for &os;. In the &arch.i386; and &arch.amd64; architectures, disks can be divided into multiple partitions using one of two - partitioning schemes. A traditional Master Boot Record - (MBR) holds a partition table defining up - to four primary partitions. For - historical reasons, &os; calls these primary partitions - slices. One of these - primary partitions can be made into an extended - partition containing multiple logical - partitions. The GUID Partition Table + partitioning schemes. A traditional Master Boot + Record (MBR) holds a + partition table defining up to four primary + partitions. For historical reasons, &os; + calls these primary partition + slices. One of these primary + partitions can be made into an extended + partition containing multiple + logical partitions. The + GUID Partition Table (GPT) is a newer and simpler method of partitioning a disk. Common GPT implementations allow up to 128 partitions per disk, @@ -344,84 +346,86 @@ is a free live CD which includes the GParted partition editor. GParted is also included with - many other Linux live CD distributions. + many other Linux live CD + distributions. When used properly, disk shrinking utilities can - safely create space for creating a new partition. - Since the possibility of selecting the wrong partition - exists, always backup any important data - and verify the integrity of the backup before modifying disk - partitions. + safely create space for creating a new partition. Since + the possibility of selecting the wrong partition exists, + always backup any important data and verify the integrity + of the backup before modifying disk partitions. Disk partitions containing different operating systems - make it possible to install multiple operating systems on one computer. - An alternative is to use virtualization () which allows - multiple operating systems to run at the same time without - modifying any disk partitions. - - - - Collect Network Information - - Some &os; installation methods require a network connection - in order to download the installation files. After any - installation, the installer will offer to setup the system's - network interfaces. + make it possible to install multiple operating systems on + one computer. An alternative is to use virtualization + () which allows multiple + operating systems to run at the same time without modifying + any disk partitions. + + + + Collect Network Information + + Some &os; installation methods require a network + connection in order to download the installation files. + After any installation, the installer will offer to setup + the system's network interfaces. + + If the network has a DHCP server, it + can be used to provide automatic network configuration. If + DHCP is not available, the follwoing + network information for the system must be obtained from the + local network administrator or Internet service + provider: - If the network has a DHCP server, it can be used to provide - automatic network configuration. If DHCP - is not available, the follwoing network information for the system must be obtained - from the local network administrator or Internet service - provider: + + Required Network Information - - Required Network Information - - - IP - address - - - - Subnet mask - + + IP address + - - IP address of default - gateway - + + Subnet mask + - - Domain name of the network - + + IP address of default + gateway + - - IP addresses of the network's - DNS servers - - - + + Domain name of the network + - - Check for &os; Errata + + IP addresses of the network's + DNS servers + + + + + + Check for &os; Errata + + Although the &os; Project strives to ensure that + each release of &os; is as stable as possible, bugs + occasionally creep into the process. On very rare occasions + those bugs 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. - Although the &os; Project strives to ensure that each - release of &os; is as stable as possible, bugs occasionally - creep into the process. On very rare occasions those bugs - 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. - - Information and errata for all the releases can be found - on the release information section of the &os; web site (http://www.freebsd.org/releases/index.html). - + Information and errata for all the releases can be found + on the release information section of the &os; web site + (http://www.freebsd.org/releases/index.html). + @@ -620,131 +624,125 @@ commit your changes? configure the system to boot from the inserted media depends upon the architecture. - - Booting on &i386; and &arch.amd64; + + Booting on &i386; and &arch.amd64; - These architectures provide a - BIOS menu for selecting the - boot device. Depending upon the installation media - being used, select the - CD/DVD or - USB device as the first boot device. - Most systems also - provide a key for selecting the boot device during - startup without having to enter the BIOS. - Typically, the key is either F10, - F11, F12, or - Escape. - - If the computer loads the - existing operating system instead of the &os; installer, then either: - - - - The installation media was not inserted early enough in the - boot process. Leave the media inserted and try restarting the - computer. - - - - The BIOS changes were incorrect or not saved. - Double-check that the right boot device - is selected as the first boot device. - - - - This system is too old to - support booting from the chosen media. In this case, the - Plop Boot Manager (http://www.plop.at/en/bootmanager.html) - can be used to boot the system from the selected - media. - - - - - - Booting on &powerpc; - - On most machines, holding C on the - keyboard during boot will boot from the - CD. Otherwise, hold - - Command - Option - O - F - , - or - - Windows - Alt - O - F - - on non-&apple; keyboards. At the 0 > - prompt, enter - - boot cd:,\ppc\loader cd:0 - - - - Booting on &sparc64; - - Most &sparc64; systems are set up to boot automatically - from disk. To install &os; - from a CD requires a break into the - PROM. - - To do this, reboot the system and wait until the boot - message appears. The message depends on the model, but should look - something like this: + These architectures provide a BIOS + menu for selecting the boot device. Depending upon the + installation media being used, select the + CD/DVD or + USB device as the first boot device. Most + systems also provide a key for selecting the boot device + during startup without having to enter the + BIOS. Typically, the key is either + F10, F11, + F12, or Escape. - Sun Blade 100 (UltraSPARC-IIe), Keyboard Present + If the computer loads the existing operating system + instead of the &os; installer, then either: + + + + The installation media was not inserted early enough + in the boot process. Leave the media inserted and try + restarting the computer. + + + + The BIOS changes were incorrect or + not saved. Double-check that the right boot device is + selected as the first boot device. + + + + This system is too old to support booting from the + chosen media. In this case, the Plop Boot + Manager (http://www.plop.at/en/bootmanager.html) + can be used to boot the system from the selected + media. + + + + + + Booting on &powerpc; + + On most machines, holding C on the + keyboard during boot will boot from the CD. + Otherwise, hold + Command + Option + O + F + , or + + Windows + Alt + O + F + on non-&apple; keyboards. At the + 0 > prompt, enter + + boot cd:,\ppc\loader cd:0 + + + + Booting on &sparc64; + + Most &sparc64; systems are set up to boot automatically + from disk. To install &os; from a CD + requires a break into the PROM. + + To do this, reboot the system and wait until the boot + message appears. The message depends on the model, but should + look something like this: + + Sun Blade 100 (UltraSPARC-IIe), Keyboard Present Copyright 1998-2001 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.2, 128 MB memory installed, Serial #51090132. 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. When using tip - or cu, ~# will - issue a BREAK. The PROM prompt will be - ok on systems with one - CPU and ok {0} on SMP - systems, where the digit indicates the number of the active - CPU. - - At this point, place the CD into the - drive and type boot cdrom from the - PROM prompt. + 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. When using tip or + cu, ~# will + issue a BREAK. The PROM prompt will be + ok on systems with one + CPU and ok {0} on + SMP systems, where the digit indicates the + number of the active CPU. + + At this point, place the CD into the + drive and type boot cdrom from the + PROM prompt. &os; Boot Menu - Once the system boots from the installation media, - a menu similar to the following will be displayed: + Once the system boots from the installation media, a menu + similar to the following will be displayed: -
- &os; Boot Loader Menu +
+ &os; Boot Loader Menu - - - - - -
- - By default, the menu will wait ten seconds for user - input before booting into the &os; installer or, if &os; is - already installed, before booting into &os;. To pause the - boot timer in order to review the selections, press + + + + + +
+ + By default, the menu will wait ten seconds for user input + before booting into the &os; installer or, if &os; is already + installed, before booting into &os;. To pause the boot timer + in order to review the selections, press Space. To select an option, press its highlighted number, character, or key. The following options are available. @@ -784,18 +782,18 @@ Ethernet address 0:3:ba:b:92:d4, Host ID menu shown in, and described under, . - + -
- &os; Boot Options Menu +
+ &os; Boot Options Menu - - - - - -
+ + + + + +
The boot options menu is divided into two sections. The first section can be used to either return to the main boot @@ -834,19 +832,19 @@ Ethernet address 0:3:ba:b:92:d4, Host ID Verbose: Toggle this option to On to see more detailed messages during - the boot process. This can be useful when troubleshooting + the boot process. This can be useful when troubleshooting a piece of hardware. - + After making the needed selections, press 1 or Backspace to return to - the main boot menu, then press Enter to - continue booting into &os;. A series of boot messages will - appear as &os; carries out its hardware device probes and - loads the installation program. Once the boot is complete, - the welcome menu shown in - will be displayed. + the main boot menu, then press Enter to + continue booting into &os;. A series of boot messages will + appear as &os; carries out its hardware device probes and + loads the installation program. Once the boot is complete, + the welcome menu shown in will be displayed.
Welcome Menu @@ -859,10 +857,10 @@ Ethernet address 0:3:ba:b:92:d4, Host ID
Press Enter to select the default of - [ Install ] to - enter the installer. The rest of this chapter describes how - to use this installer. Otherwise, use the right or left arrows - or the colorized letter to select the desired menu item. The + [ Install ] to enter the + installer. The rest of this chapter describes how to use this + installer. Otherwise, use the right or left arrows or the + colorized letter to select the desired menu item. The [ Shell ] can be used to access a &os; shell in order to use command line utilities to prepare the disks before installation. The @@ -871,13 +869,14 @@ Ethernet address 0:3:ba:b:92:d4, Host ID is described in . - To review the boot messages, including the hardware device - probe, press the upper- or lower-case S and - then Enter to access a shell. At the shell - prompt, type more /var/run/dmesg.boot and - use the space bar to scroll through the messages. When - finished, type exit to return to the - welcome menu. + To review the boot messages, including the hardware + device probe, press the upper- or lower-case + S and then Enter to access + a shell. At the shell prompt, type more + /var/run/dmesg.boot and use the space bar to + scroll through the messages. When finished, type + exit to return to the welcome + menu. @@ -889,9 +888,9 @@ Ethernet address 0:3:ba:b:92:d4, Host ID bsdinstall menus and the type of information that will be asked before the system is installed. Use the up and down arrows to highlight a menu option, then the - Space key to select or deselect a - menu item. Then, use Enter to save the selection - and move onto the next screen. + Space key to select or deselect a menu item. + Then, use Enter to save the selection and move + onto the next screen. Selecting the Keymap Menu @@ -979,8 +978,8 @@ Ethernet address 0:3:ba:b:92:d4, Host ID - Type in a hostname that is unique for the network. It should be a fully-qualified hostname, - such as Type in a hostname that is unique for the network. It + should be a fully-qualified hostname, such as machine3.example.com. @@ -1004,15 +1003,15 @@ Ethernet address 0:3:ba:b:92:d4, Host ID 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. Depending on the architecture, some of these - components may not appear: + as the base system, are always installed. + Depending on the architecture, some of these components may + not appear: doc - Additional documentation, mostly of historical interest, to install into - /usr/share/doc. The documentation + /usr/share/doc. The documentation provided by the FreeBSD Documentation Project may be installed later using the instructions in .