From owner-svn-doc-head@FreeBSD.ORG Mon Apr 14 15:52:42 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 CCFD328D; Mon, 14 Apr 2014 15:52:42 +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 B6B6C1818; Mon, 14 Apr 2014 15:52:42 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s3EFqgA5008098; Mon, 14 Apr 2014 15:52:42 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s3EFqgvE008097; Mon, 14 Apr 2014 15:52:42 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201404141552.s3EFqgvE008097@svn.freebsd.org> From: Dru Lavigne Date: Mon, 14 Apr 2014 15:52:42 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44550 - head/en_US.ISO8859-1/books/handbook/install 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: Mon, 14 Apr 2014 15:52:42 -0000 Author: dru Date: Mon Apr 14 15:52:42 2014 New Revision: 44550 URL: http://svnweb.freebsd.org/changeset/doc/44550 Log: White space fix only. Translators can ignore. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/install/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/install/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/install/chapter.xml Mon Apr 14 14:20:38 2014 (r44549) +++ head/en_US.ISO8859-1/books/handbook/install/chapter.xml Mon Apr 14 15:52:42 2014 (r44550) @@ -5,34 +5,33 @@ $FreeBSD$ --> - Installing &os; 8.<replaceable>X</replaceable> + + Installing &os; 8.<replaceable>X</replaceable> + - JimMockRestructured, reorganized, and parts - rewritten by + JimMockRestructured, + reorganized, and parts rewritten by - RandyPrattThe sysinstall walkthrough, screenshots, and general - copy by + RandyPrattThe + sysinstall walkthrough, screenshots, and general copy by + - - - Synopsis installation &os; provides a text-based, easy to use installation - program. &os; 9.0-RELEASE and later use the installation program - 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 . + program. &os; 9.0-RELEASE and later use the installation + program 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: @@ -50,8 +49,8 @@ - The questions &man.sysinstall.8; asks, - what they mean, and how to answer them. + The questions &man.sysinstall.8; asks, what they mean, + and how to answer them. @@ -59,20 +58,20 @@ - Read the supported hardware list that shipped with the version - of &os; to install, and verify that the system's hardware is - supported. + Read the supported hardware list that shipped with the + version of &os; to install, and verify that the system's + hardware is supported. In general, these installation instructions are written - 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. + 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. @@ -86,25 +85,24 @@ The minimal configuration to install &os; varies with the &os; version and the hardware architecture. - A summary of this information is given in the following sections. - 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 - . + A summary of this information is given in the following + sections. 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, at least 24 MB of RAM, and at - least 150 MB of free hard drive space for the - most minimal installation. + Both &os;/&arch.i386; and &os;/&arch.pc98; require a 486 + or better processor, at least 24 MB of RAM, and at + least 150 MB of free hard drive space for the most + minimal installation. In the case of older hardware, installing more RAM and - more hard drive space is often more important than - a faster processor. + more hard drive space is often more important than a + faster processor. @@ -113,32 +111,29 @@ 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, and &amd.opteron; or better - processors. - - 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 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. + including the &amd.athlon;64, &amd.athlon;64-FX, and + &amd.opteron; or better processors. + + 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 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;, use a supported - platform (see ). + To install &os;/&arch.sparc64;, use a supported platform + (see ). - A dedicated disk is needed for &os;/&arch.sparc64; as - 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. @@ -150,12 +145,13 @@ 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 - &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; website. + &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; website. @@ -167,31 +163,25 @@ 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, - 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. - - 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. + 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, 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. + + 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: + before installing &os;. It may help to use a table, as seen + in this example: Sample Device Inventory @@ -221,7 +211,8 @@ N/A - 40 GB, made by Seagate, first IDE master + 40 GB, made by Seagate, first IDE + master @@ -241,7 +232,8 @@ N/A - 20 GB, made by IBM, second IDE master + 20 GB, made by IBM, second IDE + master @@ -282,174 +274,157 @@
Once the inventory of the components in the computer is - complete, check if it matches the hardware - requirements of the &os; release to install. + complete, check if it matches the hardware requirements of the + &os; release to install. Make a Backup - 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. + 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 &os; is to be installed on the entire hard disk, - skip this - section. + If &os; is to be installed on the entire hard disk, skip + this section. However, if &os; will co-exist with other operating - systems, a rough understanding of how data is - laid out on the disk is useful. + 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 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 - limitation and allow more than four partitions, a new partition type - was created, the extended partition. A disk - may contain only one extended partition. Special partitions, called - logical partitions, can be created inside this - extended partition. - - Each partition has a partition ID, which is - 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 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. 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 files. A more realistic minimum - is 250 MB without a graphical environment, and 350 MB or - more for - a graphical user interface. If other - third-party software will be installed, - even more space is needed. - - You can use a tool such as GParted - to resize your partitions and make space for - &os;. GParted is known to work on - NTFS and - is available on a number of Live CD Linux distributions, such as - SystemRescueCD. + 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 limitation and allow more than four partitions, a new + partition type was created, the extended + partition. A disk may contain only one + extended partition. Special partitions, called + logical partitions, can be created + inside this extended partition. + + Each partition has a partition + ID, which is 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 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. 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 files. A more realistic minimum is 250 MB + without a graphical environment, and 350 MB or more for + a graphical user interface. If other third-party software + will be installed, even more space is needed. + + You can use a tool such as + GParted to resize your partitions + and make space for &os;. GParted + is known to work on NTFS and is available + on a number of Live CD Linux distributions, such as SystemRescueCD. + + + 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 + + Consider a computer with a single 4 GB disk that + 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. There is 1 GB of data + on C:, and 0.5 GB of data on + D:. + + 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;. + + + + Shrinking an Existing Partition + + 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. - - 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 - - Consider a computer with a single 4 GB disk - that - 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. - There is 1 GB of data on C:, - and - 0.5 GB of data on - D:. - - 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;. - - - - Shrinking an Existing Partition - - 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;, either: - - - - Backup the &windows; data and then reinstall - &windows;, - asking for a 2 GB partition at install time. - + In order to install &os;, either: - - Use one of the tools described above to shrink your &windows; - partition. - - - + + + Backup the &windows; data and then reinstall + &windows;, asking for a 2 GB partition at install + time. + + + Use one of the tools described above to shrink + your &windows; partition. + + + Collect the Network Configuration Details - Before - installing from an FTP - site or an + Before installing from an FTP site or an 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 + 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 + Connecting to an Ethernet Network or Cable/DSL + Modem - If using an Ethernet network or an Internet - connection using an Ethernet adapter via cable or DSL, the - following information is needed: + If using an Ethernet network or an Internet connection + using an Ethernet adapter via cable or DSL, the following + information is needed: @@ -482,10 +457,9 @@ Connecting Using a Modem - If using a dialup modem, - &os; can still be installed over the Internet, it will just - take a very - long time. + 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: @@ -510,28 +484,28 @@ Check for &os; Errata 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 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; website. - Check the errata before installing to make sure that there are - no late-breaking problems to be aware of. + release of &os; is as stable as possible, bugs do occasionally + creep into 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; website. Check + the errata before installing to make sure that there are no + late-breaking problems to be aware of. Information about all releases, including the errata for - each - release, can be found on the - release - information section of the - &os; website. + each release, can be found on the release + information section of the &os; + website. Obtain the &os; Installation Files - The &os; installer can install &os; from files - located in any of the following places: + The &os; installer can install &os; from files located in + any of the following places: Local Media @@ -570,15 +544,14 @@ - If installing from a purchased &os; CD/DVD, - skip ahead to + If installing from a purchased &os; CD/DVD, skip ahead to . - To obtain the &os; installation files, - skip ahead to which explains how - to prepare the installation media. After reading - that section, come back here and read on to - . + To obtain the &os; installation files, skip ahead to which explains how to prepare + the installation media. After reading that section, come back + here and read on to . @@ -586,18 +559,15 @@ The &os; installation process is started by booting the 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. + 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 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 + 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. @@ -610,16 +580,16 @@ Memory stick images for &os; 8.X can be downloaded - from - the ISO-IMAGES/ - directory at + 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 to - install. For example, the memory stick - images for &os;/&arch.i386; &rel2.current;-RELEASE are - available from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-memstick.img. + version with the architecture + and the version number to install. For example, the + memory stick images for + &os;/&arch.i386; &rel2.current;-RELEASE are + available from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-memstick.img. A different directory path is used for @@ -632,14 +602,13 @@ The memory stick image has a .img extension. The ISO-IMAGES/ directory 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. + 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 on the USB stick, as this - procedure will erase it. + data on the USB stick, as this procedure will + erase it. @@ -650,31 +619,29 @@ Using &os; to Write the Image - 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. + 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. Writing the Image with &man.dd.1; - The .img file - 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 + The .img file 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 &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 - another program. Then try + If an Operation not + permitted error is displayed, make + certain that the target device is not in use, mounted, + or being automounted by another program. Then try again. @@ -684,35 +651,38 @@ 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. + output target, as this command will overwrite and + destroy any existing data on the specified + device. - Obtaining <application>Image Writer for Windows</application> + Obtaining <application>Image Writer for + Windows</application> - Image Writer for Windows is a - free application that can correctly write an image file to a - memory stick. Download it from - https://launchpad.net/win32-image-writer/ + Image Writer for + Windows is a free application that can + correctly write an image file to a memory stick. + Download it from https://launchpad.net/win32-image-writer/ and extract it into a folder. Writing the Image with Image Writer - Double-click - the Win32DiskImager icon to start - the program. Verify that the drive letter shown - under Device is the drive - with the memory stick. Click the folder icon and select the - image to be written to the memory stick. - Click Save to accept the image file - name. Verify that everything is correct, and that no folders - on the memory stick are open in other windows. Finally, - click Write to write the image file to - the drive. + Double-click the + Win32DiskImager icon to + start the program. Verify that the drive letter shown + under Device is the + drive with the memory stick. Click the folder icon + and select the image to be written to the memory + stick. Click Save to accept + the image file name. Verify that everything is + correct, and that no folders on the memory stick are + open in other windows. Finally, click + Write to write the image file + to the drive. @@ -725,14 +695,15 @@ Acquire the Boot Floppy Images - The &os;/&arch.pc98; boot disks - can be downloaded from the floppies directory, + The &os;/&arch.pc98; boot disks can be downloaded from + the floppies directory, ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/pc98/version-RELEASE/floppies/. Replace version with the version number to install. The floppy images have a .flp - extension. floppies/ contains a number + extension. floppies/ contains a number of different images. Download boot.flp as well as the number of files associated with the type of installation, such as @@ -741,34 +712,29 @@ The FTP program must use binary - mode - to download these disk images. Some web browsers - use text or + mode to download these disk images. Some + web browsers use text or ASCII mode, which will be apparent - if - the disks are not bootable. + if the disks are not bootable. Prepare the Floppy Disks - 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 to use brand new - floppies. + 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 to use brand new floppies. - 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. + 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. @@ -777,44 +743,37 @@ The .flp files are not regular files that can be copied - to the disk. - They are images of the complete contents of the - disk. - Specific tools must be used to write the + to the disk. They are images of the complete contents of + the disk. Specific tools must be used to write the images directly to the disk. DOS - &os; provides a tool called - rawrite for creating the floppies on a - computer running - &windows;. This tool can be downloaded from + &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: + version-RELEASE/tools/ on the + &os; FTP site. Download this tool, insert a floppy, then + specify the filename to write to the floppy drive: 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. - Adjust the command line as necessary, depending on where - the .flp files are located. + file, replacing the floppy disk each time, being sure to + label 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: + 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. Other &unix; - variants might have different names for the floppy disk - device, so check the documentation for the - system as necessary. + first floppy disk. Other &unix; variants might have + different names for the floppy disk device, so check the + documentation for the system as necessary. @@ -827,8 +786,7 @@ By default, the installer will not make any changes to - the - disk(s) until after the following message: + the disk(s) until after the following message: Last Chance: Are you SURE you want continue the installation? @@ -839,10 +797,8 @@ We can take no responsibility for lost d 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 + there is a concern that something is configured incorrectly, + turn the computer off before this point, and no damage will be done. @@ -852,86 +808,85 @@ We can take no responsibility for lost d Booting for the &i386; - - - 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, - Del, or - - Alt - S - . Use whichever keystroke is indicated on screen. In - some cases the computer may display a graphic while it - starts. - Typically, pressing Esc will dismiss the graphic - and display the boot messages. - - - - Find the setting that controls which devices the system boots - from. This is usually labeled as the Boot Order - and commonly shown as a list of devices, such as - Floppy, CDROM, - First Hard Disk, and so on. - - 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, *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***