From owner-svn-doc-all@FreeBSD.ORG Thu Apr 24 20:50:14 2014 Return-Path: Delivered-To: svn-doc-all@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 9A961D87; Thu, 24 Apr 2014 20:50:14 +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 869FA1C84; Thu, 24 Apr 2014 20:50:14 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s3OKoEBJ032167; Thu, 24 Apr 2014 20:50:14 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s3OKoEql032166; Thu, 24 Apr 2014 20:50:14 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201404242050.s3OKoEql032166@svn.freebsd.org> From: Dru Lavigne Date: Thu, 24 Apr 2014 20:50:14 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44651 - 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-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Apr 2014 20:50:14 -0000 Author: dru Date: Thu Apr 24 20:50:14 2014 New Revision: 44651 URL: http://svnweb.freebsd.org/changeset/doc/44651 Log: Replace "you"usage in 9.x Install chapter. 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 20:17:37 2014 (r44650) +++ head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml Thu Apr 24 20:50:14 2014 (r44651) @@ -101,7 +101,7 @@ The questions bsdinstall will - ask you, what they mean, and how to answer them. + ask, what they mean, and how to answer them. @@ -110,7 +110,7 @@ Read the supported hardware list that shipped with the - version of &os; you are installing, and verify that your + version of &os; to be installed and verify that the system's hardware is supported. @@ -136,9 +136,9 @@ &os; version and the hardware architecture. A summary of this information is given in the following - sections. Depending on the method you choose to install &os;, - you may also need a supported CDROM drive, and in some cases a - network adapter. This will be covered by + sections. Depending upon the method chosen to install &os;, + a supported CDROM drive and, in some cases, a + network adapter may be needed. This will be covered by . @@ -174,12 +174,10 @@ &intel; &xeon; E3, E5 and E7 processors, and the &intel; &core; i3, i5 and i7 processors. - If you have a machine based on an nVidia nForce3 - Pro-150, you must use the BIOS setup to - disable the IO APIC. If you do not have an option to do - this, you will likely have to disable ACPI instead. There - are bugs in the Pro-150 chipset for which we have not yet - found a workaround. + 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. @@ -225,7 +223,7 @@ Pre-Installation Tasks - Back Up Your Data + Back Up Important Data Back up all important data on the target computer where &os; will be installed. Test the backups before @@ -348,7 +346,7 @@ - Back up your &windows; data. Then reinstall + Back up any &windows; data. Then reinstall &windows;, creating a 20 GB partition during the install. @@ -462,14 +460,14 @@ corrupt and should be discarded. - If you already have a copy of &os; on CDROM, DVD, or USB + If a copy of &os; already exists on CDROM, 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 CD recording applications - available with your current operating system. On &os;, + available with the current operating system. On &os;, recording is provided by &man.cdrecord.1; from sysutils/cdrtools, installed from the Ports Collection. @@ -488,7 +486,7 @@ 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 which you want to + architecture and the version number to install, respectively. For example, the memory stick images for &os;/&arch.i386; 9.0-RELEASE are available from 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, or - you may destroy existing data. + the correct device is used as the output target, as this command will + destroy existing data. @@ -549,8 +547,8 @@ Be sure to give the correct drive letter as the - output target, or you may overwrite and destroy - existing data. + output target, as existing data will be overwritten + and destroyed. @@ -600,7 +598,7 @@ By default, the installation will not make any changes to - your disk(s) until you see the following message: + the disk(s) before the following message: Your changes will now be written to disk. If you have chosen to overwrite existing data, it will @@ -609,8 +607,8 @@ commit your changes? The install can be exited at any time prior to this warning without changing the contents of the hard drive. If - you are concerned that you have configured something - incorrectly you can just turn the computer off before this + there is a concern that something is + incorrectly configured, just turn the computer off before this point, and no damage will be done. @@ -622,19 +620,19 @@ commit your changes? - If you prepared a bootable USB stick, + When using a prepared bootable USB stick, as described in - , then - plug in your USB stick before turning on the + , + plug in the USB stick before turning on the computer. - If you are booting from CDROM, then you will need to - turn on the computer, and insert the CDROM at the first + When booting from CDROM, + turn on the computer and insert the CDROM at the first opportunity. - Configure your machine to boot from either the CDROM + Configure the system to boot from either the CDROM or from USB, depending on the media being used for the installation. BIOS configurations allow the selection of a specific boot device. Most @@ -645,24 +643,24 @@ commit your changes? - If your computer starts up as normal and loads your + If the computer starts up as normal and loads an existing operating system, then either: The disks were not inserted early enough in the boot process. Leave them in, and try restarting - your computer. + the computer. The BIOS changes earlier did - not work correctly. You should redo that step until - you get the right option. + not work correctly. Redo that step until + the right option is selected. - Your particular BIOS does not + This particular BIOS does not support booting from the desired media. The Plop Boot Manager can be used to boot older @@ -672,8 +670,8 @@ commit your changes? - &os; will start to boot. If you are booting from - CDROM you will see a display similar to this (version + &os; will start to boot. When booting from + CDROM, messages similar to this will be displayed (version information omitted): Booting from CD-ROM... @@ -752,8 +750,8 @@ Loading /boot/defaults/loader.conf Booting for &sparc64; Most &sparc64; systems are set up to boot automatically - from disk. To install &os;, you need to boot over the - network or from a CDROM, which requires you to break into + from disk. To install &os;, booting over the + network or from a CDROM requires a break into the PROM (OpenFirmware). @@ -767,8 +765,8 @@ Copyright 1998-2001 Sun Microsystems, In OpenBoot 4.2, 128 MB memory installed, Serial #51090132. Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. - If your system proceeds to boot from disk at this point, - you need to press + If the system proceeds to boot from disk at this point, + press L1A or @@ -795,7 +793,7 @@ Ethernet address 0:3:ba:b:92:d4, Host ID - At this point, place the CDROM into your drive, and from + At this point, place the CDROM into the drive, and from the PROM prompt, type boot cdrom. @@ -808,17 +806,17 @@ 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. You can then use the + This turns on scrolling in the display. Use the arrow keys, or PageUp and - PageDown to view the results. Press + 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. - You will see text similar to - , although the precise - text will differ depending on the devices that you have in - your computer. + Text similar to + will be displayed, although the precise + text will differ depending on the devices in + the computer.
Typical Device Probe Results @@ -973,15 +971,15 @@ Trying to mount root from cd9660:/dev/is
Check the probe results carefully to make sure that &os; - found all the devices you expected. If a device was not - found, then it will not be listed. + found all the devices. If a device was not + found, it will not be listed. Refer to Kernel - modules allows you to add in support for devices + modules for instructions on how to add in support for devices which are not in the GENERIC kernel. - After the procedure of device probing, you will see - . The install media + After the procedure of device probing, + will be displayed. The install media can be used in three ways: to install &os;, as a live CD, or to simply access a &os; shell. Use the arrow keys to choose @@ -1170,12 +1168,11 @@ Trying to mount root from cd9660:/dev/is to use the ports collection. - The installation program does not check to see if - you have adequate space. Select this option only if you - have adequate hard disk space. As of &os; 9.0, the + 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. You can safely assume a larger value for - more recent versions of &os;. + disk space. @@ -1803,7 +1800,7 @@ Trying to mount root from cd9660:/dev/is - Rescan Devices to repopulate the list of available disks. To ensure that the correct disk is selected, so as not to accidently destroy the wrong disks, the - - Disk Info menu allows you to inspect + - Disk Info menu can be used to inspect each disk, including its partition table, and various other information, including the device model number and serial number, if available. @@ -2310,13 +2307,13 @@ Trying to mount root from cd9660:/dev/is Setting the Time Zone - Setting the time zone for your machine will allow it to + Setting the time zone for the machine will allow it to automatically correct for any regional time changes and perform other time zone related functions properly. The example shown is for a machine located in the Eastern - time zone of the United States. Your selections will vary - according to your geographical location. + time zone of the United States. The selections will vary + according to the geographical location.
Select Local or UTC Clock @@ -2332,7 +2329,7 @@ Trying to mount root from cd9660:/dev/is Select [ Yes ] or [ No ] according to how the machine's clock is configured and press - Enter. If you do not know whether the system + Enter. If it is not known whether the system uses UTC or local time, select [ No ] to choose the more commonly-used local time. @@ -2661,7 +2658,7 @@ Trying to mount root from cd9660:/dev/is Handbook - Download and install the - &os; Handbook (which is what you are reading now). + &os; Handbook. @@ -2957,23 +2954,23 @@ login: Due to various limitations of the PC architecture, it is impossible for probing to be 100% reliable, however, there are - a few things you can do if it fails. + a few things to try if it fails. Check the Hardware - Notes document for your version of &os; to make sure + Notes document for the version of &os; to make sure your hardware is supported. - If your hardware is supported and you still experience - lock-ups or other problems, you will need to build a - custom kernel. This will - allow you to add in support for devices which are not present + If the hardware is supported and + lock-ups or other problems occur, build a + custom kernel which + adds support for devices which are not present in the GENERIC kernel. The kernel on the boot disks is configured assuming that most hardware devices are in their factory default configuration in terms of IRQs, - IO addresses, and DMA channels. If your hardware has been - reconfigured, you will most likely need to edit the kernel - configuration and recompile to tell &os; where to find + IO addresses, and DMA channels. If the hardware has been + reconfigured, a custom kernel + configuration file can tell &os; where to find things. It is also possible that a probe for a device not present