Date: Mon, 14 Apr 2014 15:52:42 +0000 (UTC) From: Dru Lavigne <dru@FreeBSD.org> 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 Message-ID: <201404141552.s3EFqgvE008097@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
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$ --> <chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="install"> - <info><title>Installing &os; 8.<replaceable>X</replaceable></title> + <info> + <title>Installing &os; 8.<replaceable>X</replaceable></title> + <authorgroup> - <author><personname><firstname>Jim</firstname><surname>Mock</surname></personname><contrib>Restructured, reorganized, and parts - rewritten by </contrib></author> + <author><personname><firstname>Jim</firstname><surname>Mock</surname></personname><contrib>Restructured, + reorganized, and parts rewritten by </contrib></author> </authorgroup> <authorgroup> - <author><personname><firstname>Randy</firstname><surname>Pratt</surname></personname><contrib>The sysinstall walkthrough, screenshots, and general - copy by </contrib></author> + <author><personname><firstname>Randy</firstname><surname>Pratt</surname></personname><contrib>The + sysinstall walkthrough, screenshots, and general copy by + </contrib></author> </authorgroup> - </info> - - <sect1 xml:id="install-synopsis"> <title>Synopsis</title> <indexterm><primary>installation</primary></indexterm> <para>&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.<replaceable>X</replaceable> uses - &man.sysinstall.8;. This chapter describes - how to use &man.sysinstall.8;. - The use of &man.bsdinstall.8; - is covered in <xref linkend="bsdinstall"/>.</para> + program. &os; 9.0-RELEASE and later use the installation + program known as &man.bsdinstall.8; while + &os; 8.<replaceable>X</replaceable> uses + &man.sysinstall.8;. This chapter describes how to use + &man.sysinstall.8;. The use of &man.bsdinstall.8; is covered in + <xref linkend="bsdinstall"/>.</para> <para>After reading this chapter, you will know:</para> @@ -50,8 +49,8 @@ </listitem> <listitem> - <para>The questions &man.sysinstall.8; asks, - what they mean, and how to answer them.</para> + <para>The questions &man.sysinstall.8; asks, what they mean, + and how to answer them.</para> </listitem> </itemizedlist> @@ -59,20 +58,20 @@ <itemizedlist> <listitem> - <para>Read the supported hardware list that shipped with the version - of &os; to install, and verify that the system's hardware is - supported.</para> + <para>Read the supported hardware list that shipped with the + version of &os; to install, and verify that the system's + hardware is supported.</para> </listitem> </itemizedlist> <note> <para>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.</para> + 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.</para> </note> </sect1> @@ -86,25 +85,24 @@ <para>The minimal configuration to install &os; varies with the &os; version and the hardware architecture.</para> - <para>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 - <xref linkend="install-boot-media"/>.</para> + <para>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 <xref linkend="install-boot-media"/>.</para> <sect3> <title>&os;/&arch.i386; and &os;/&arch.pc98;</title> - <para>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.</para> + <para>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.</para> <note> <para>In the case of older hardware, installing more RAM and - more hard drive space is often more important than - a faster processor.</para> + more hard drive space is often more important than a + faster processor.</para> </note> </sect3> @@ -113,32 +111,29 @@ <para>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.</para> - - <para>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.</para> - - <para>If the machine is based on an nVidia nForce3 - Pro-150, the BIOS setup <emphasis>must</emphasis> 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.</para> + including the &amd.athlon;64, &amd.athlon;64-FX, and + &amd.opteron; or better processors.</para> + + <para>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.</para> + + <para>If the machine is based on an nVidia nForce3 Pro-150, + the BIOS setup <emphasis>must</emphasis> 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.</para> </sect3> <sect3> <title>&os;/&arch.sparc64;</title> - <para>To install &os;/&arch.sparc64;, use a supported - platform (see <xref linkend="install-hardware-supported"/>).</para> + <para>To install &os;/&arch.sparc64;, use a supported platform + (see <xref linkend="install-hardware-supported"/>).</para> - <para>A dedicated disk is needed for &os;/&arch.sparc64; as - it is not possible to share a disk with another operating + <para>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.</para> </sect3> </sect2> @@ -150,12 +145,13 @@ release in the &os; Hardware Notes. This document can usually be found in a file named <filename>HARDWARE.TXT</filename>, 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 <link xlink:href="http://www.FreeBSD.org/releases/index.html">Release - Information</link> page of the &os; website.</para> + &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 <link + xlink:href="http://www.FreeBSD.org/releases/index.html">Release + Information</link> page of the &os; website.</para> </sect2> </sect1> @@ -167,31 +163,25 @@ <para>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.</para> - - <para>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 <literal>0x330</literal>.</para> + 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.</para> + + <para>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 + <literal>0x330</literal>.</para> <para>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:</para> + before installing &os;. It may help to use a table, as seen + in this example:</para> <table pgwide="1" frame="none"> <title>Sample Device Inventory</title> @@ -221,7 +211,8 @@ <entry>N/A</entry> - <entry>40 GB, made by Seagate, first IDE master</entry> + <entry>40 GB, made by Seagate, first IDE + master</entry> </row> <row> @@ -241,7 +232,8 @@ <entry>N/A</entry> - <entry>20 GB, made by IBM, second IDE master</entry> + <entry>20 GB, made by IBM, second IDE + master</entry> </row> <row> @@ -282,174 +274,157 @@ </table> <para>Once the inventory of the components in the computer is - complete, check if it matches the hardware - requirements of the &os; release to install.</para> + complete, check if it matches the hardware requirements of the + &os; release to install.</para> </sect2> <sect2> <title>Make a Backup</title> - <para>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.</para> + <para>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.</para> </sect2> <sect2 xml:id="install-where"> <title>Decide Where to Install &os;</title> - <para>If &os; is to be installed on the entire hard disk, - skip this - section.</para> + <para>If &os; is to be installed on the entire hard disk, skip + this section.</para> <para>However, if &os; will co-exist with other operating - systems, a rough understanding of how data is - laid out on the disk is useful.</para> + systems, a rough understanding of how data is laid out on the + disk is useful.</para> <sect3 xml:id="install-where-i386"> <title>Disk Layouts for &os;/&arch.i386;</title> - <para>A PC disk can be divided into discrete chunks known as - <firstterm>partitions</firstterm>. 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 - <firstterm>primary partitions</firstterm>. To work around this - limitation and allow more than four partitions, a new partition type - was created, the <firstterm>extended partition</firstterm>. A disk - may contain only one extended partition. Special partitions, called - <firstterm>logical partitions</firstterm>, can be created inside this - extended partition.</para> - - <para>Each partition has a <firstterm>partition ID</firstterm>, which is - a number used to identify the type of data on the partition. &os; - partitions have the partition ID of <literal>165</literal>.</para> - - <para>In general, each operating system will identify - partitions in a particular way. For example, - &windows;, assigns each primary and logical partition a - <firstterm>drive letter</firstterm>, starting with - <filename>C:</filename>.</para> - - <para>&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.</para> - - <para>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; - <command>fdisk</command>.</para> - - <para>If there is a spare partition, use that. If it is too - small, - shrink one or more existing partitions to create more - available space.</para> - - <para>A minimal installation of &os; takes as little as 100 MB - of disk - space. However, that is a <emphasis>very</emphasis> 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.</para> - - <para>You can use a tool such as <application>GParted</application> - to resize your partitions and make space for - &os;. <application>GParted</application> is known to work on - <acronym>NTFS</acronym> and - is available on a number of Live CD Linux distributions, such as - <link xlink:href="http://www.sysresccd.org/">SystemRescueCD</link>.</para>; + <para>A PC disk can be divided into discrete chunks known as + <firstterm>partitions</firstterm>. 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 + <firstterm>primary partitions</firstterm>. To work around + this limitation and allow more than four partitions, a new + partition type was created, the <firstterm>extended + partition</firstterm>. A disk may contain only one + extended partition. Special partitions, called + <firstterm>logical partitions</firstterm>, can be created + inside this extended partition.</para> + + <para>Each partition has a <firstterm>partition + ID</firstterm>, which is a number used to identify the + type of data on the partition. &os; partitions have the + partition ID of <literal>165</literal>.</para> + + <para>In general, each operating system will identify + partitions in a particular way. For example, &windows;, + assigns each primary and logical partition a + <firstterm>drive letter</firstterm>, starting with + <filename>C:</filename>.</para> + + <para>&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.</para> + + <para>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; + <command>fdisk</command>.</para> + + <para>If there is a spare partition, use that. If it is too + small, shrink one or more existing partitions to create more + available space.</para> + + <para>A minimal installation of &os; takes as little as + 100 MB of disk space. However, that is a + <emphasis>very</emphasis> 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.</para> + + <para>You can use a tool such as + <application>GParted</application> to resize your partitions + and make space for &os;. <application>GParted</application> + is known to work on <acronym>NTFS</acronym> and is available + on a number of Live CD Linux distributions, such as <link + xlink:href="http://www.sysresccd.org/">SystemRescueCD</link>.</para>; + + <warning> + <para>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.</para> + </warning> + + <example> + <title>Using an Existing Partition Unchanged</title> + + <para>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, + <filename>C:</filename> and <filename>D:</filename>, each + of which is 2 GB in size. There is 1 GB of data + on <filename>C:</filename>, and 0.5 GB of data on + <filename>D:</filename>.</para> + + <para>This disk has two partitions, one per drive letter. + Copy all existing data from <filename>D:</filename> to + <filename>C:</filename>, which will free up the second + partition, ready for &os;.</para> + </example> + + <example> + <title>Shrinking an Existing Partition</title> + + <para>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 <filename>C:</filename> drive that is 4 GB in size. + Currently, 1.5 GB of space is used, and &os; should + have 2 GB of space.</para> - <warning> - <para>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.</para> - </warning> - - <example> - <title>Using an Existing Partition Unchanged</title> - - <para>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, - <filename>C:</filename> and - <filename>D:</filename>, each of which is 2 GB in size. - There is 1 GB of data on <filename>C:</filename>, - and - 0.5 GB of data on - <filename>D:</filename>.</para> - - <para>This disk has two partitions, one per - drive letter. Copy all existing data from - <filename>D:</filename> to <filename>C:</filename>, which - will free up the second partition, ready for &os;.</para> - </example> - - <example> - <title>Shrinking an Existing Partition</title> - - <para>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 - <filename>C:</filename> drive that is 4 GB in size. - Currently, 1.5 GB of space is used, and &os; should - have 2 GB - of space.</para> - - <para>In order to install &os;, either:</para> - - <orderedlist> - <listitem> - <para>Backup the &windows; data and then reinstall - &windows;, - asking for a 2 GB partition at install time.</para> - </listitem> + <para>In order to install &os;, either:</para> - <listitem> - <para>Use one of the tools described above to shrink your &windows; - partition.</para> - </listitem> - </orderedlist> - </example> + <orderedlist> + <listitem> + <para>Backup the &windows; data and then reinstall + &windows;, asking for a 2 GB partition at install + time.</para> + </listitem> + <listitem> + <para>Use one of the tools described above to shrink + your &windows; partition.</para> + </listitem> + </orderedlist> + </example> </sect3> </sect2> <sect2> <title>Collect the Network Configuration Details</title> - <para>Before - installing from an FTP - site or an + <para>Before installing from an FTP site or an <acronym>NFS</acronym> 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.</para> <sect3> - <title>Connecting to an Ethernet Network or Cable/DSL Modem</title> + <title>Connecting to an Ethernet Network or Cable/DSL + Modem</title> - <para>If using an Ethernet network or an Internet - connection using an Ethernet adapter via cable or DSL, the - following information is needed:</para> + <para>If using an Ethernet network or an Internet connection + using an Ethernet adapter via cable or DSL, the following + information is needed:</para> <orderedlist> <listitem> @@ -482,10 +457,9 @@ <sect3> <title>Connecting Using a Modem</title> - <para>If using a dialup modem, - &os; can still be installed over the Internet, it will just - take a very - long time.</para> + <para>If using a dialup modem, &os; can still be installed + over the Internet, it will just take a very long + time.</para> <para>You will need to know:</para> @@ -510,28 +484,28 @@ <title>Check for &os; Errata</title> <para>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 <link xlink:href="http://www.FreeBSD.org/releases/&rel.current;R/errata.html">&os; Errata</link>, - 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.</para> + 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 <link + xlink:href="http://www.FreeBSD.org/releases/&rel.current;R/errata.html">&os; + Errata</link>, 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.</para> <para>Information about all releases, including the errata for - each - release, can be found on the - <link xlink:href="&url.base;/releases/index.html">release - information</link> section of the - <link xlink:href="&url.base;/index.html">&os; website</link>.</para> + each release, can be found on the <link + xlink:href="&url.base;/releases/index.html">release + information</link> section of the <link + xlink:href="&url.base;/index.html">&os; + website</link>.</para> </sect2> <sect2> <title>Obtain the &os; Installation Files</title> - <para>The &os; installer can install &os; from files - located in any of the following places:</para> + <para>The &os; installer can install &os; from files located in + any of the following places:</para> <itemizedlist> <title>Local Media</title> @@ -570,15 +544,14 @@ </listitem> </itemizedlist> - <para>If installing from a purchased &os; CD/DVD, - skip ahead to + <para>If installing from a purchased &os; CD/DVD, skip ahead to <xref linkend="install-boot-media"/>.</para> - <para>To obtain the &os; installation files, - skip ahead to <xref linkend="install-diff-media"/> which explains how - to prepare the installation media. After reading - that section, come back here and read on to - <xref linkend="install-boot-media"/>.</para> + <para>To obtain the &os; installation files, skip ahead to <xref + linkend="install-diff-media"/> which explains how to prepare + the installation media. After reading that section, come back + here and read on to <xref + linkend="install-boot-media"/>.</para> </sect2> <sect2 xml:id="install-boot-media"> @@ -586,18 +559,15 @@ <para>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.</para> + 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.</para> <tip> - <para>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 + <para>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.</para> </tip> @@ -610,16 +580,16 @@ <para>Memory stick images for &os; 8.<replaceable>X</replaceable> can be downloaded - from - the <filename class="directory">ISO-IMAGES/</filename> - directory at + from the <filename + class="directory">ISO-IMAGES/</filename> directory at <literal>ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<replaceable>arch</replaceable>/ISO-IMAGES/<replaceable>version</replaceable>/&os;-<replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-memstick.img</literal>. Replace <replaceable>arch</replaceable> and - <replaceable>version</replaceable> 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 <uri xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-memstick.img">ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-memstick.img</uri>.</para>; + <replaceable>version</replaceable> 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 <uri + xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-memstick.img">ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-memstick.img</uri>.</para>; <tip> <para>A different directory path is used for @@ -632,14 +602,13 @@ <para>The memory stick image has a <filename>.img</filename> extension. The <filename>ISO-IMAGES/</filename> 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.</para> + use depends on the version of &os; and the type of media + supported by the hardware being installed to.</para> <important> <para>Before proceeding, <emphasis>back up</emphasis> the - data on the USB stick, as this - procedure will <emphasis>erase</emphasis> it.</para> + data on the USB stick, as this procedure will + <emphasis>erase</emphasis> it.</para> </important> </step> @@ -650,31 +619,29 @@ <title>Using &os; to Write the Image</title> <warning> - <para>The example below - lists <filename>/dev/da0</filename> 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.</para> + <para>The example below lists + <filename>/dev/da0</filename> 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.</para> </warning> <step> <title>Writing the Image with &man.dd.1;</title> - <para>The <filename>.img</filename> file - is <emphasis>not</emphasis> 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 + <para>The <filename>.img</filename> file is + <emphasis>not</emphasis> 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:</para> <screen>&prompt.root; <userinput>dd if=&os;-&rel2.current;-RELEASE-&arch.i386;-memstick.img of=/dev/<replaceable>da0</replaceable> bs=64k</userinput></screen> - <para>If an - <computeroutput>Operation not permitted</computeroutput> - error is displayed, make certain that the target device - is not in use, mounted, or being automounted by - another program. Then try + <para>If an <computeroutput>Operation not + permitted</computeroutput> error is displayed, make + certain that the target device is not in use, mounted, + or being automounted by another program. Then try again.</para> </step> </procedure> @@ -684,35 +651,38 @@ <warning> <para>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.</para> + output target, as this command will overwrite and + destroy any existing data on the specified + device.</para> </warning> <step> - <title>Obtaining <application>Image Writer for Windows</application></title> + <title>Obtaining <application>Image Writer for + Windows</application></title> - <para><application>Image Writer for Windows</application> is a - free application that can correctly write an image file to a - memory stick. Download it from - <uri xlink:href="https://launchpad.net/win32-image-writer/">https://launchpad.net/win32-image-writer/</uri>; + <para><application>Image Writer for + Windows</application> is a free application that can + correctly write an image file to a memory stick. + Download it from <uri + xlink:href="https://launchpad.net/win32-image-writer/">https://launchpad.net/win32-image-writer/</uri>; and extract it into a folder.</para> </step> <step> <title>Writing the Image with Image Writer</title> - <para>Double-click - the <application>Win32DiskImager</application> icon to start - the program. Verify that the drive letter shown - under <computeroutput>Device</computeroutput> is the drive - with the memory stick. Click the folder icon and select the - image to be written to the memory stick. - Click <guibutton>Save</guibutton> 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 <guibutton>Write</guibutton> to write the image file to - the drive.</para> + <para>Double-click the + <application>Win32DiskImager</application> icon to + start the program. Verify that the drive letter shown + under <computeroutput>Device</computeroutput> is the + drive with the memory stick. Click the folder icon + and select the image to be written to the memory + stick. Click <guibutton>Save</guibutton> 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 + <guibutton>Write</guibutton> to write the image file + to the drive.</para> </step> </procedure> </step> @@ -725,14 +695,15 @@ <step> <title>Acquire the Boot Floppy Images</title> - <para>The &os;/&arch.pc98; boot disks - can be downloaded from the floppies directory, + <para>The &os;/&arch.pc98; boot disks can be downloaded from + the floppies directory, <literal>ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/pc98/<replaceable>version</replaceable>-RELEASE/floppies/</literal>. Replace <replaceable>version</replaceable> with the version number to install.</para> <para>The floppy images have a <filename>.flp</filename> - extension. <filename class="directory">floppies/</filename> contains a number + extension. <filename + class="directory">floppies/</filename> contains a number of different images. Download <filename>boot.flp</filename> as well as the number of files associated with the type of installation, such as @@ -741,34 +712,29 @@ <important> <para>The FTP program must use <emphasis>binary - mode</emphasis> - to download these disk images. Some web browsers - use <emphasis>text</emphasis> or + mode</emphasis> to download these disk images. Some + web browsers use <emphasis>text</emphasis> or <emphasis>ASCII</emphasis> mode, which will be apparent - if - the disks are not bootable.</para> + if the disks are not bootable.</para> </important> </step> <step> <title>Prepare the Floppy Disks</title> - <para>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 <quote>bad</quote> - and ignores them. It is advised to use brand new - floppies.</para> + <para>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 <quote>bad</quote> and ignores + them. It is advised to use brand new floppies.</para> <important> - <para>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.</para> + <para>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.</para> </important> </step> @@ -777,44 +743,37 @@ <para>The <filename>.flp</filename> files are <emphasis>not</emphasis> 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.</para> <indexterm><primary>DOS</primary></indexterm> - <para>&os; provides a tool called - <command>rawrite</command> for creating the floppies on a - computer running - &windows;. This tool can be downloaded from + <para>&os; provides a tool called <command>rawrite</command> + for creating the floppies on a computer running &windows;. + This tool can be downloaded from <literal>ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/pc98/<replaceable>; - version</replaceable>-RELEASE/tools/</literal> - on the &os; FTP site. Download this tool, insert a - floppy, then specify the filename to write to the floppy - drive:</para> + version</replaceable>-RELEASE/tools/</literal> on the + &os; FTP site. Download this tool, insert a floppy, then + specify the filename to write to the floppy drive:</para> <screen><prompt>C:\></prompt> <userinput>rawrite boot.flp A:</userinput></screen> <para>Repeat this command for each <filename>.flp</filename> - 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 <filename>.flp</filename> files are located.</para> + 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 + <filename>.flp</filename> files are located.</para> <para>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:</para> + such as another &os; system, use &man.dd.1; to write the + image files directly to disk. On &os;, run:</para> <screen>&prompt.root; <userinput>dd if=boot.flp of=/dev/fd0</userinput></screen> <para>On &os;, <filename>/dev/fd0</filename> 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.</para> + first floppy disk. Other &unix; variants might have + different names for the floppy disk device, so check the + documentation for the system as necessary.</para> </step> </procedure> @@ -827,8 +786,7 @@ <important> <para>By default, the installer will not make any changes to - the - disk(s) until after the following message:</para> + the disk(s) until after the following message:</para> <literallayout class="monospaced">Last Chance: Are you SURE you want continue the installation? @@ -839,10 +797,8 @@ We can take no responsibility for lost d <para>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.</para> </important> @@ -852,86 +808,85 @@ We can take no responsibility for lost d <sect3 xml:id="install-starting-i386"> <title>Booting for the &i386;</title> - <procedure> - <step> - <para>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 <keycap>F2</keycap>, <keycap>F10</keycap>, - <keycap>Del</keycap>, or - <keycombo action="simul"> - <keycap>Alt</keycap> - <keycap>S</keycap> - </keycombo>. Use whichever keystroke is indicated on screen. In - some cases the computer may display a graphic while it - starts. - Typically, pressing <keycap>Esc</keycap> will dismiss the graphic - and display the boot messages.</para> - </step> - - <step> - <para>Find the setting that controls which devices the system boots - from. This is usually labeled as the <quote>Boot Order</quote> - and commonly shown as a list of devices, such as - <literal>Floppy</literal>, <literal>CDROM</literal>, - <literal>First Hard Disk</literal>, and so on.</para> - - <para>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 ***
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201404141552.s3EFqgvE008097>