From owner-svn-doc-projects@FreeBSD.ORG Mon May 6 11:53:22 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EB86FEBB; Mon, 6 May 2013 11:53:22 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id DCDA7EB3; Mon, 6 May 2013 11:53:22 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r46BrMS9069788; Mon, 6 May 2013 11:53:22 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r46BrMX7069787; Mon, 6 May 2013 11:53:22 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201305061153.r46BrMX7069787@svn.freebsd.org> From: Dru Lavigne Date: Mon, 6 May 2013 11:53:22 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41554 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/install X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 May 2013 11:53:23 -0000 Author: dru Date: Mon May 6 11:53:22 2013 New Revision: 41554 URL: http://svnweb.freebsd.org/changeset/doc/41554 Log: First pass to cleanup this chapter: - &os; and "you" - dir tags and some (not all) acronyms - fixes broken URLs, grammos, typos, outdated info - removes 3.13.5 which assumes a boot floppy - removes references to deprecated utilities partition magic, xcopy, fdimage, doublespace - removes unrecommended tip in Q&A - removes 3.13.3 as floppies were covered earlier for pc98 Approved by: bcr (mentor) Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/install/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/install/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/install/chapter.xml Mon May 6 11:34:28 2013 (r41553) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/install/chapter.xml Mon May 6 11:53:22 2013 (r41554) @@ -27,39 +27,40 @@ - Installing &os; 8.<replaceable>X</replaceable> and Earlier + Installing &os; 8.<replaceable>X</replaceable> Synopsis installation - FreeBSD is provided with a text-based, easy to use installation + &os; provides a text-based, easy to use installation program. &os; 9.0-RELEASE and later use the installation program - known as bsdinstall, with releases prior - to 9.0-RELEASE using sysinstall for - installation. This chapter describes the use of sysinstall - to install &os;. The use of bsdinstall + known as &man.bsdinstall.8; + while &os; 8.X uses + &man.sysinstall.8;. This chapter describes + how to use &man.sysinstall.8;. + The use of &man.bsdinstall.8; is covered in . After reading this chapter, you will know: - How to create the FreeBSD installation disks. + How to create the &os; installation media. - How FreeBSD refers to, and subdivides, your hard disks. + How &os; refers to and subdivides hard disks. - How to start sysinstall. + How to start &man.sysinstall.8;. - The questions sysinstall will ask - you, what they mean, and how to answer them. + The questions &man.sysinstall.8; asks, + what they mean, and how to answer them. @@ -68,19 +69,18 @@ Read the supported hardware list that shipped with the version - of FreeBSD you are installing, and verify that your hardware is + of &os; to install, and verify that the system's hardware is supported. In general, these installation instructions are written - for &i386; (PC compatible) architecture - computers. Where applicable, instructions specific to other - platforms will be listed. Although this - guide is kept as up to date as possible, you may find minor - differences between the installer and what is shown here. It is - suggested that you use this chapter as a general guide rather + for the &i386; and &os;/&arch.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. + This chapter should be used as a general guide rather than a literal installation manual. @@ -96,23 +96,24 @@ &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 floppy drive, a supported CDROM drive, and in some - case a network adapter. This will be covered by the . + Depending on the method chosen to install &os;, + a floppy drive, CDROM drive, or + network adapter may be needed. Instructions on how to + prepare the installation media can be found in + . &os;/&arch.i386; and &os;/&arch.pc98; Both &os;/&arch.i386; and &os;/&arch.pc98; require a 486 or - better processor and at least 24 MB of RAM. You will - need at least 150 MB of free hard drive space for the + better processor, at least 24 MB of RAM, and at + least 150 MB of free hard drive space for the most minimal installation. - In case of old configurations, most of time, getting - more RAM and more hard drive space is more important than - getting a faster processor. + In the case of older hardware, installing more RAM and + more hard drive space is often more important than + a faster processor. @@ -122,33 +123,32 @@ 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 + &amd.athlon;64-FX, and &amd.opteron; or better processors. - The second class of processors that can use - &os;/&arch.amd64; includes those using the &intel; EM64T + The second class of processors + includes those using the &intel; EM64T architecture. Examples of these processors include the &intel; &core; 2 Duo, Quad, Extreme processor families, and the &intel; &xeon; 3000, 5000, and 7000 sequences of 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 that we have not found a - workaround for yet. + If the machine is based on an nVidia nForce3 + Pro-150, the BIOS setup must be used to + disable the IO APIC. If this option does not exist, + disable ACPI instead as there + are bugs in the Pro-150 chipset. &os;/&arch.sparc64; - To install &os;/&arch.sparc64;, you will need a supported + To install &os;/&arch.sparc64;, use a supported platform (see ). - You will need a dedicated disk for &os;/&arch.sparc64;. It - is not possible to share a disk with another operating + A dedicated disk is needed for &os;/&arch.sparc64; as + it is not possible to share a disk with another operating system at this time. @@ -159,14 +159,14 @@ A list of supported hardware is provided with each &os; release in the &os; Hardware Notes. This document can usually be found in a file named HARDWARE.TXT, in - the top-level directory of a CDROM or FTP distribution or in - sysinstall's documentation menu. - It lists, for a given architecture, what hardware devices are + the top-level directory of a CDROM or FTP distribution, or in + &man.sysinstall.8;'s documentation menu. + It lists, for a given architecture, which hardware devices are known to be supported by each release of &os;. Copies of the supported hardware list for various releases and architectures can also be found on the Release - Information page of the &os; Web site. + Information page of the &os; website. @@ -174,28 +174,35 @@ Pre-installation Tasks - Inventory Your Computer + Inventory the Computer - Before installing &os; you should attempt to inventory the - components in your computer. The &os; installation routines will - show you the components (hard disks, network cards, CDROM drives, and - so forth) with their model number and manufacturer. &os; will also + Before installing &os; it is recommended to inventory the + components in the computer. The &os; installation routines + will show components such as hard disks, network cards, + and CDROM drives with their model number and manufacturer. + &os; will also attempt to determine the correct configuration for these devices, - which includes information about IRQ and IO port usage. Due to the - vagaries of PC hardware this process is not always completely - successful, and you may need to correct &os;'s determination of - your configuration. - - If you already have another operating system installed, such as - &windows; or Linux, it is a good idea to use the facilities provided - by those operating systems to see how your hardware is already - configured. If you are not sure what settings an expansion - card is using, you may find it printed on the card itself. Popular IRQ - numbers are 3, 5, and 7, and IO port addresses are normally written as - hexadecimal numbers, such as 0x330. + including information about IRQ and I/O port usage. Due + to the + vagaries of computer hardware, this process is not always + completely + successful, and &os; may need some manual + configuration. - We recommend you print or write down this information before - installing &os;. It may help to use a table, like this: + If another operating system is already installed, + use the facilities provided + by that operating systems to view the hardware configuration. + If the settings of an expansion + card are not obvious, check if they are printed on the + card itself. Popular IRQ + numbers are 3, 5, and 7, and I/O port addresses are normally + written as + hexadecimal numbers, such as 0x330. + + It is recommended to print or write down this information + before + installing &os;. It may help to use a table, as seen in this + example: Sample Device Inventory @@ -211,7 +218,7 @@ IRQ - IO port(s) + I/O port(s)Notes @@ -285,43 +292,44 @@
- Once the inventory of the components in your computer is - done, you have to check if they match the hardware - requirements of the &os; release you want to install. + Once the inventory of the components in the computer is + complete, check if it matches the hardware + requirements of the &os; release to install. - Backup Your Data + Make a Backup - If the computer you will be installing &os; on contains - valuable data, then ensure you have it backed up, and that you have - tested the backups before installing &os;. The &os; - installation routine will prompt you before writing any - data to your disk, but once that process has started it cannot be + If the computer contains + valuable data, ensure it is backed up, and that the backup + has been + tested before installing &os;. The &os; + installer will prompt before writing any + data to disk, but once that process has started, it cannot be undone. Decide Where to Install &os; - If you want &os; to use your entire hard disk, then there is nothing - more to concern yourself with at this point — you can skip this + If &os; is to be installed on the entire hard disk, + skip this section. - However, if you need &os; to co-exist with other operating - systems then you need to have a rough understanding of how data is - laid out on the disk, and how this affects you. + However, if &os; will co-exist with other operating + systems, a rough understanding of how data is + laid out on the disk is useful. Disk Layouts for &os;/&arch.i386; - A PC disk can be divided into discrete chunks. These chunks are - called partitions. Since - &os; internally also has partitions, the naming - can become confusing very quickly, therefore these - disk chunks are referred to as disk slices or simply slices - in &os; itself. For example, the &os; utility - fdisk which operates on the PC disk partitions, + A PC disk can be divided into discrete chunks known as + partitions. Since + &os; also has partitions, naming + can quickly become confusing. Therefore, these + disk chunks are referred to as slices + in &os;. For example, the &os; version of + &man.fdisk.8; refers to slices instead of partitions. By design, the PC only supports four partitions per disk. These partitions are called primary partitions. To work around this @@ -335,74 +343,71 @@ a number used to identify the type of data on the partition. &os; partitions have the partition ID of 165. - In general, each operating system that you use will identify - partitions in a particular way. For example, &ms-dos;, and its - descendants, like &windows;, assign each primary and logical partition a + In general, each operating system will identify + partitions in a particular way. For example, + &windows;, assigns each primary and logical partition a drive letter, starting with C:. - &os; must be installed into a primary partition. &os; can - keep all its data, including any files that you create, on this one - partition. However, if you have multiple disks, then you can create a - &os; partition on all, or some, of them. When you install &os;, - you must have one partition available. This might be a blank - partition that you have prepared, or it might be an existing partition - that contains data that you no longer care about. - - If you are already using all the partitions on all your disks, then - you will have to free one of them for &os; using the tools - provided by the other operating systems you use (e.g., - fdisk on &ms-dos; or &windows;). - - If you have a spare partition then you can use that. However, you - may need to shrink one or more of your existing partitions - first. + &os; must be installed into a primary partition. If + there are multiple disks, a &os; + partition can be created + on all, or some, of them. When &os; is installed, at least + one partition must be available. This might be a blank + partition or it might be an existing partition whose + data can be overwritten. + + If all the partitions on all the disks are in use, + free one of them for &os; using the tools + provided by an existing operating system, such as &windows; + fdisk. + + If there is a spare partition, use that. If it is too + small, + shrink one or more existing partitions to create more + available space. A minimal installation of &os; takes as little as 100 MB of disk space. However, that is a very minimal install, - leaving almost no space for your own files. A more realistic minimum + leaving almost no space for files. A more realistic minimum is 250 MB without a graphical environment, and 350 MB or - more if you - want a graphical user interface. If you intend to install a lot of - third-party software as well, then you will need more space. - - You can use a commercial tool such as &partitionmagic;, - or a free tool such as GParted, - to resize your partitions and make space for - &os;. Both - &partitionmagic; and - GParted are known to work on - NTFS. GParted - is available on a number of Live CD Linux distributions, such as - SystemRescueCD. - - Problems have been reported resizing µsoft; Vista - partitions. Having a Vista installation CDROM handy when - attempting such an operation is recommended. As with all - such disk maintenance tasks, a current set of backups is - also strongly advised. + more for + a graphical user interface. If other + third-party software will be installed, + even more space is needed. + + Use a tool such as GParted + to resize the partitions and make space for + &os;. When resizing µsoft; partitions, having a + &windows; installation disc handy is recommended. As with all + disk maintenance tasks, a current set of backups is also + strongly advised. - Incorrect use of these tools can delete the data on your disk. - Be sure that you have recent, working backups before using - them. + Incorrect use of a shrinking tool can delete the data + on the disk. + Always have a recent, working backup before using this + type of tool. Using an Existing Partition Unchanged - Suppose that you have a computer with a single 4 GB disk + Consider a computer with a single 4 GB disk that - already has a version of &windows; installed, and you have split the - disk into two drive letters, C: and + already has a version of &windows; installed, where the + disk has been split into two drive letters, + C: and D:, each of which is 2 GB in size. - You have 1 GB of data on C:, and + There is 1 GB of data on C:, + and 0.5 GB of data on D:. - This means that your disk has two partitions on it, one per - drive letter. You can copy all your existing data from + This disk has two partitions, one per + drive letter. Copy all existing data from D: to C:, which will free up the second partition, ready for &os;. @@ -410,25 +415,28 @@ Shrinking an Existing Partition - Suppose that you have a computer with a single 4 GB disk - that already has a version of &windows; installed. When you installed - &windows; you created one large partition, giving you a - C: drive that is 4 GB in size. You are - currently using 1.5 GB of space, and want &os; to have 2 GB + Consider a computer with a single 4 GB disk + that already has a version of &windows; installed. When + &windows; was installed, it created one large partition, + a + C: drive that is 4 GB in size. + Currently, 1.5 GB of space is used, and &os; should + have 2 GB of space. - In order to install &os; you will need to either: + In order to install &os;, either: - Backup your &windows; data, and then reinstall &windows;, + Backup the &windows; data and then reinstall + &windows;, asking for a 2 GB partition at install time. - Use one of the tools such as &partitionmagic;, - described above, to shrink your &windows; - partition. + Use a tool + to shrink the &windows; + partition. @@ -437,21 +445,24 @@ - Collect Your Network Configuration Details + Collect the Network Configuration Details - If you intend to connect to a network as part of your &os; - installation (for example, if you will be installing from an FTP + Before + installing from an FTP site or an - NFS server), then you need to know your network configuration. You - will be prompted for this information during the installation so that - &os; can connect to the network to complete the install. + NFS server, make note of the network + configuration. The + installer + will prompt for this information so that + it can connect to the network to complete the + installation. Connecting to an Ethernet Network or Cable/DSL Modem - If you connect to an Ethernet network, or you have an Internet - connection using an Ethernet adapter via cable or DSL, then you will - need the following information: + If using an Ethernet network or an Internet + connection using an Ethernet adapter via cable or DSL, the + following information is needed: @@ -475,32 +486,35 @@ - If you do not know this information, then ask your system - administrator or service provider. They may say that this - information is assigned automatically, using - DHCP. If so, make a note of this. + If this information is unknown, ask the system + administrator or service provider. Make note if this + information is assigned automatically using + DHCP. Connecting Using a Modem - If you dial up to an ISP using a regular modem then you can - still install &os; over the Internet, it will just take a very + If using a dialup modem, + &os; can still be installed over the Internet, it will just + take a very long time. You will need to know: - The phone number to dial for your ISP + The phone number to dial the Internet Service + Provider (ISP) - The COM: port your modem is connected to + The COM: port the modem is connected to - The username and password for your ISP account + The username and password for the + ISP account @@ -508,28 +522,30 @@ Check for &os; Errata - Although the &os; project strives to ensure that each release + Although the &os; Project strives to ensure that each + release of &os; is as stable as possible, bugs do occasionally creep into - the process. On very rare occasions those bugs affect the + the process. On rare occasions those bugs affect the installation process. As these problems are discovered and fixed, they are noted in the &os; Errata, - which is found on the &os; web site. You - should check the errata before installing to make sure that there are - no late-breaking problems which you should be aware of. + which is found on the &os; website. + Check the errata before installing to make sure that there are + no late-breaking problems to be aware of. - Information about all the releases, including the errata for each + Information about all releases, including the errata for + each release, can be found on the release information section of the &os; web site. + url="&url.base;/index.html">&os; website. Obtain the &os; Installation Files - The &os; installation process can install &os; from files + The &os; installer can install &os; from files located in any of the following places: @@ -548,11 +564,7 @@ - A SCSI or QIC tape - - - - Floppy disks + Floppy disks (&os;/&arch.pc98; only) @@ -560,8 +572,8 @@ Network - An FTP site, going through a firewall, or using an HTTP proxy, - as necessary + An FTP site through a firewall or using an HTTP + proxy @@ -573,14 +585,14 @@ - If you have purchased &os; on CD or DVD then you already have - everything you need, and should proceed to the next section - (). + If installing from a purchased &os; CD/DVD, + skip ahead to + . - If you have not obtained the &os; installation files you should + To obtain the &os; installation files, skip ahead to which explains how - to prepare to install &os; from any of the above. After reading - that section, you should come back here, and read on to + to prepare the installation media. After reading + that section, come back here and read on to . @@ -588,18 +600,19 @@ Prepare the Boot Media The &os; installation process is started by booting the - computer into the &os; installer—it is not a program you run + computer into the &os; installer. It is not a program that + can be run within another operating system. The computer normally boots using the operating system installed on the hard disk, but it can also be configured to boot from a CDROM or from a USB disk. - If you have &os; on CDROM or DVD (either one you purchased - or you prepared yourself), and your computer allows you to boot from - the CDROM or DVD (typically a BIOS option called Boot - Order or similar), then you can skip this section. The - &os; CDROM and DVD images are bootable and can be used to install + If installing from a CD/DVD to a + computer whose BIOS supports booting from + the CD/DVD, skip this section. The + &os; CD/DVD images are bootable and can be used to + install &os; without any other special preparation. @@ -611,36 +624,38 @@ Acquire the Memory Stick Image Memory stick images for - &os; 8.X and earlier can be downloaded from + &os; 8.X can be downloaded + from the ISO-IMAGES/ directory at ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/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 - install, respectively. For example, the memory stick + architecture and the version number to + install. For example, the memory stick images for &os;/&arch.i386; &rel2.current;-RELEASE are available from . A different directory path is used for - &os; 9.0-RELEASE and later versions. Details of - download and installation of &os; 9.0-RELEASE and - later is covered in . + &os; 9.0-RELEASE and later versions. How to + download and install + &os; 9.X + is covered in . The memory stick image has a .img extension. The ISO-IMAGES/ directory - contains a number of different images, and the one you - will need to use will depend on the version of &os; you - are installing, and in some cases, the hardware you are - installing to. + contains a number of different images and the one to + use depends on the version of &os; and the + type of media supported by the hardware being installed + to. Before proceeding, back up the - data you currently have on your USB stick, as this + data on the USB stick, as this procedure will erase it. @@ -653,29 +668,32 @@ The example below - lists /dev/da0 as the - target device where the image will be written. Be very careful - that you have the correct device as the output target, or you - may destroy your existing data. + uses /dev/da0 + as the + target device where the image will be written. Be + very careful + to use the correct device as the output target, as + the data on that device will be destroyed. Writing the Image with &man.dd.1; The .img file - is not a regular file you copy to the + is not a regular file that can + just be copied to the memory stick. It is an image of the complete contents of the - disk. This means that you cannot simply - copy files from one disk to another. Instead, you must use - &man.dd.1; to write the image directly to the disk: + disk. This means that + &man.dd.1; must be used to write the image directly to + the disk: &prompt.root; dd if=&os;-&rel2.current;-RELEASE-&arch.i386;-memstick.img of=/dev/da0 bs=64k If an Operation not permitted error is displayed, make certain that the target device - is not in use, mounted, or being automounted by some - well-intentioned utility program. Then try + is not in use, mounted, or being automounted by + another program. Then try again. @@ -684,8 +702,10 @@ Using &windows; To Write the Image - Make sure you use the correct drive letter as the output - target, or you may overwrite and destroy existing data. + Make sure to use the correct drive letter as the + output + target, as this command will overwrite and destroy + any existing data on the specified device. @@ -740,29 +760,32 @@ kern*. - Your FTP program must use binary mode - to download these disk images. Some web browsers have been - known to use text (or - ASCII) mode, which will be apparent if you - cannot boot from the disks. + The FTP program must use binary + mode + to download these disk images. Some web browsers + use text or + ASCII mode, which will be apparent + if + the disks are not bootable. Prepare the Floppy Disks - Prepare one floppy disk per image file you had to - download. It is imperative that these disks are free from - defects. The easiest way to test this is to format the disks - for yourself. Do not trust pre-formatted floppies. The format + Prepare one floppy disk per downloaded image file. + It is imperative that these disks are free from + defects. The easiest way to test this is to reformat the + disks. + Do not trust pre-formatted floppies. The format utility in &windows; will not tell about the presence of bad blocks, it simply marks them as bad - and ignores them. It is advised that you use brand new - floppies if choosing this installation route. + and ignores them. It is advised to use brand new + floppies. - If you try to install &os; and the installation - program crashes, freezes, or otherwise misbehaves, one of + If the installer + crashes, freezes, or otherwise misbehaves, one of the first things to suspect is the floppies. Write the floppy image files to new disks and try again. @@ -773,47 +796,44 @@ Write the Image Files to the Floppy Disks The .flp files are - not regular files you copy to the disk. + not regular files that can be copied + to the disk. They are images of the complete contents of the - disk. This means that you cannot simply - copy files from one disk to another. - Instead, you must use specific tools to write the + disk. + Specific tools must be used to write the images directly to the disk. DOS - If you are creating the floppies on a computer running - &ms-dos; / &windows;, then we provide a tool to do - this called fdimage. - - If you are using the floppies from the CDROM, and your - CDROM is the E: drive, then you would - run this: + &os; provides a tool called + rawrite for creating the floppies on a + computer running + &windows;. This tool can be downloaded from + ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/pc98/ + version-RELEASE/tools/ + on the &os; FTP site. Download this tool, insert a + floppy, then specify the filename to write to the floppy + drive: - E:\> tools\fdimage floppies\boot.flp A: + C:\> rawrite boot.flp A: Repeat this command for each .flp file, replacing the floppy disk each time, being sure to label - the disks with the name of the file that you copied to them. - Adjust the command line as necessary, depending on where you have - placed the .flp files. If you do not have - the CDROM, then fdimage can be downloaded from - the tools - directory on the &os; FTP site. - - If you are writing the floppies on a &unix; system (such as - another &os; system) you can use the &man.dd.1; command to - write the image files directly to disk. On &os;, you would + the disks with the name of the file. + Adjust the command line as necessary, depending on where + the .flp files are located. + + When writing the floppies on a &unix;-like system, + such as + another &os; system, use &man.dd.1; to + write the image files directly to disk. On &os;, run: &prompt.root; dd if=boot.flp of=/dev/fd0 On &os;, /dev/fd0 refers to the - first floppy disk (the A: drive). - /dev/fd1 would be the - B: drive, and so on. Other &unix; + first floppy disk. Other &unix; variants might have different names for the floppy disk - devices, and you will need to check the documentation for the + device, so check the documentation for the system as necessary. @@ -826,8 +846,9 @@ Starting the Installation - By default, the installation will not make any changes to your - disk(s) until you see the following message: + By default, the installer will not make any changes to + the + disk(s) until after the following message: Last Chance: Are you SURE you want continue the installation? @@ -836,10 +857,12 @@ STRONGLY ENCOURAGE YOU TO MAKE PROPER BA We can take no responsibility for lost disk contents! - The install can be exited at any time prior to the final - 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 point, and no damage will be + The install can be exited at any time prior to this final + warning without changing the contents of the hard drive. If + there is a + concern that something is configured incorrectly, + turn the computer off before this point, and no damage + will be done. @@ -851,10 +874,6 @@ We can take no responsibility for lost d - Start with your computer turned off. - - - Turn on the computer. As it starts it should display an option to enter the system set up menu, or BIOS, commonly reached by keys like F2, F10, @@ -863,9 +882,10 @@ We can take no responsibility for lost d Alt S . Use whichever keystroke is indicated on screen. In - some cases your computer may display a graphic while it starts. + some cases the computer may display a graphic while it + starts. Typically, pressing Esc will dismiss the graphic - and allow you to see the necessary messages. + and display the boot messages. @@ -875,11 +895,10 @@ We can take no responsibility for lost d Floppy, CDROM, First Hard Disk, and so on. - If you are booting from the CDROM then make sure that - the CDROM is selected. If you are booting from a USB disk or - a floppy disk then - make sure that is selected instead. In case of doubt, you - should consult the manual that came with your computer, and/or its + If booting from the CD/DVD, make sure that + the CDROM drive is selected. If booting from a USB disk, + make sure that it is selected instead. When in doubt, + consult the manual that came with the computer or its motherboard. Make the change, then save and exit. The computer should now @@ -887,12 +906,13 @@ We can take no responsibility for lost d - If you prepared a bootable USB stick, as described in - , then plug in your USB + If using a prepared a bootable USB + stick, as described in + , 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 + If booting from CD/DVD, turn on + the computer, and insert the CD/DVD at the first opportunity. @@ -904,32 +924,33 @@ We can take no responsibility for lost d installer. - If your computer starts up as normal and loads your existing + If the computer starts up as normal and loads the + existing operating system, then either: The disks were not inserted early enough in the boot - process. Leave them in, and try restarting your + process. Leave them in, and try restarting the computer. - The BIOS changes earlier did not work correctly. You - should redo that step until you get the right option. + The BIOS changes did not work correctly. + Redo that step until the right option is + selected. - Your particular BIOS does not support booting from + That particular BIOS does not support booting from the desired media. *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***