Date: Thu, 24 Apr 2014 22:11:46 +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: r44654 - head/en_US.ISO8859-1/books/handbook/bsdinstall Message-ID: <201404242211.s3OMBkOD066761@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: dru Date: Thu Apr 24 22:11:46 2014 New Revision: 44654 URL: http://svnweb.freebsd.org/changeset/doc/44654 Log: Fix most missing acronym tags. Fix other tags spotted along the way. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml Thu Apr 24 21:46:37 2014 (r44653) +++ head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml Thu Apr 24 22:11:46 2014 (r44654) @@ -137,7 +137,7 @@ <para>A summary of this information is given in the following sections. Depending upon the method chosen to install &os;, - a supported CDROM drive and, in some cases, a + a supported <acronym>CD</acronym> drive and, in some cases, a network adapter may be needed. This will be covered by <xref linkend="bsdinstall-installation-media"/>.</para> @@ -145,12 +145,12 @@ <title>&os;/&arch.i386;</title> <para>&os;/&arch.i386; requires a 486 or better processor and - at least 64 MB of RAM. At least 1.1 GB of free + at least 64 MB of <acronym>RAM</acronym>. At least 1.1 GB of free hard drive space is needed for the most minimal installation.</para> <note> - <para>On old computers, increasing RAM and hard drive space + <para>On old computers, increasing <acronym>RAM</acronym> and hard drive space is usually more effective at improving performance than installing a faster processor.</para> </note> @@ -175,19 +175,19 @@ &intel; &core; i3, i5 and i7 processors.</para> <para>If the system is based on an nVidia nForce3 - Pro-150, the IO APIC <emphasis>must</emphasis> be disabled - in the BIOS setup. If this BIOS option does not exist, - disable ACPI instead.</para> + Pro-150, the <acronym>IO</acronym> <acronym>APIC</acronym> <emphasis>must</emphasis> be disabled + in the <acronym>BIOS</acronym> setup. If this <acronym>BIOS</acronym> option does not exist, + disable <acronym>ACPI</acronym> instead.</para> </sect3> <sect3> <title>&os;/&arch.powerpc; &apple; &macintosh;</title> <para>All New World &apple; &macintosh; systems with built-in - USB are supported. SMP is supported on machines with - multiple CPUs.</para> + <acronym>USB</acronym> are supported. <acronym>SMP</acronym> is supported on machines with + multiple <acronym>CPU</acronym>s.</para> - <para>A 32-bit kernel can only use the first 2 GB of RAM. + <para>A 32-bit kernel can only use the first 2 GB of <acronym>RAM</acronym>. &firewire; is not supported on the Blue & White PowerMac G3.</para> </sect3> @@ -246,26 +246,26 @@ <para>Hard disks can be divided into multiple sections. These sections are called - <emphasis>partitions</emphasis>.</para> + <firstterm>partitions</firstterm>.</para> <para>There are two ways of dividing a disk into partitions. - A traditional <emphasis>Master Boot Record</emphasis> + A traditional <firstterm>Master Boot Record</firstterm> (<acronym>MBR</acronym>) holds a - partition table defining up to four <emphasis>primary - partitions</emphasis>. (For historical reasons, &os; - calls primary partitions <emphasis>slices</emphasis>.) A + partition table defining up to four <firstterm>primary + partitions</firstterm>. For historical reasons, &os; + calls primary partitions <firstterm>slices</firstterm>. A limit of only four partitions is restrictive for large disks, so one of these primary partitions can be made into - an <emphasis>extended partition</emphasis>. Multiple - <emphasis>logical partitions</emphasis> may then be + an <firstterm>extended partition</firstterm>. Multiple + <firstterm>logical partitions</firstterm> may then be created inside the extended partition. This may sound a little unwieldy, and it is.</para> - <para>The <emphasis>GUID Partition Table</emphasis> + <para>The <firstterm>GUID Partition Table</firstterm> (<acronym>GPT</acronym>) is a newer and simpler method of partitioning a disk. <acronym>GPT</acronym> is far - more versatile than the traditional MBR partition table. + more versatile than the traditional <acronym>MBR </acronym>partition table. Common <acronym>GPT</acronym> implementations allow up to 128 partitions per disk, eliminating the need for inconvenient workarounds like logical partitions.</para> @@ -311,7 +311,7 @@ </warning> <para>Resizing µsoft; Vista partitions can be - difficult. A Vista installation CDROM can be useful when + difficult. A Vista installation <acronym>CD</acronym> can be useful when attempting such an operation.</para> <example> @@ -372,10 +372,10 @@ <para>Some &os; installation methods need a network connection to download files. To connect to an Ethernet network (or - cable or DSL modem with an Ethernet interface), the installer + cable or <acronym>DSL</acronym> modem with an Ethernet interface), the installer will request some information about the network.</para> - <para><emphasis><acronym>DHCP</acronym></emphasis> is commonly + <para><acronym>DHCP</acronym> is commonly used to provide automatic network configuration. If <acronym>DHCP</acronym> is not available, this network information must be obtained from the local network @@ -430,7 +430,7 @@ <title>Prepare the Installation Media</title> <para>A &os; installation is started by booting the computer - with a &os; installation CD, DVD, or USB memory stick. The + with a &os; installation <acronym>CD</acronym>, <acronym>DVD</acronym>, or <acronym>USB</acronym> memory stick. The installer is not a program that can be run from within another operating system.</para> @@ -439,7 +439,7 @@ <emphasis>bootonly</emphasis> variant. Bootonly install media does not have copies of the installation files, but downloads them from the network during an install. The bootonly install - CD is consequently much smaller, and reduces bandwidth usage + <acronym>CD</acronym> is consequently much smaller, and reduces bandwidth usage during the install by only downloading required files.</para> <para>Copies of &os; installation media are available at @@ -456,16 +456,16 @@ corrupt and should be discarded.</para> <tip> - <para>If a copy of &os; already exists on CDROM, DVD, or USB + <para>If a copy of &os; already exists on <acronym>CD</acronym>, <acronym>DVD</acronym>, or <acronym>USB</acronym> memory stick, this section can be skipped.</para> </tip> - <para>&os; CD and DVD images are bootable ISO files. Only one - CD or DVD is needed for an install. Burn the ISO image to a - bootable CD or DVD using the CD recording applications + <para>&os; <acronym>CD</acronym> and <acronym>DVD</acronym> images are bootable <acronym>ISO</acronym> files. Only one + <acronym>CD</acronym> or <acronym>DVD</acronym> is needed for an install. Burn the <acronym>ISO</acronym> image to a + bootable <acronym>CD</acronym> or <acronym>DVD</acronym> using the burning applications available with the current operating system. On &os;, - recording is provided by &man.cdrecord.1; from - <filename>sysutils/cdrtools</filename>, installed + recording is provided by <command>cdrecord</command> from + <package>sysutils/cdrtools</package>, installed from the Ports Collection.</para> <para>To create a bootable memory stick, follow these @@ -619,17 +619,17 @@ commit your changes?</literallayout> <para>When using a prepared <quote>bootable</quote> USB stick, as described in <xref linkend="bsdinstall-installation-media"/>, - plug in the USB stick before turning on the + plug in the <acronym>USB</acronym> stick before turning on the computer.</para> - <para>When booting from CDROM, - turn on the computer and insert the CDROM at the first + <para>When booting from <acronym>CD</acronym>, + turn on the computer and insert the <acronym>CD</acronym> at the first opportunity.</para> </step> <step> - <para>Configure the system to boot from either the CDROM - or from USB, depending on the media being used for the + <para>Configure the system to boot from either the <acronym>CD</acronym> + or from <acronym>USB</acronym>, depending on the media being used for the installation. <acronym>BIOS</acronym> configurations allow the selection of a specific boot device. Most systems also provide for selecting a boot device during @@ -661,14 +661,14 @@ commit your changes?</literallayout> <application>Plop Boot Manager</application> (<link xlink:href="http://www.plop.at/en/bootmanager.html">http://www.plop.at/en/bootmanager.html</link>) can be used to boot older - computers from CD or USB media.</para> + computers from <acronym>CD</acronym> or <acronym>USB</acronym> media.</para> </listitem> </orderedlist> </step> <step> <para>&os; will start to boot. When booting from - CDROM, messages similar to this will be displayed (version + <acronym>CD</acronym>, messages similar to this will be displayed (version information omitted):</para> <screen>Booting from CD-ROM... @@ -718,7 +718,7 @@ Loading /boot/defaults/loader.conf <title>Booting for &macintosh; &powerpc;</title> <para>On most machines, holding <keycap>C</keycap> on the - keyboard during boot will boot from the CD. Otherwise, hold + keyboard during boot will boot from the <acronym>CD</acronym>. Otherwise, hold <keycombo action="simul"> <keycap>Command</keycap> <keycap>Option</keycap> @@ -748,7 +748,7 @@ Loading /boot/defaults/loader.conf <para>Most &sparc64; systems are set up to boot automatically from disk. To install &os;, booting over the - network or from a CDROM requires a break into + network or from a <acronym>CD</acronym> requires a break into the <acronym>PROM</acronym> (OpenFirmware).</para> @@ -785,12 +785,12 @@ Ethernet address 0:3:ba:b:92:d4, Host ID </callout> <callout arearefs="bsdinstall-prompt-smp"> - <para>This is the prompt used on SMP systems, the digit - indicates the number of the active CPU.</para> + <para>This is the prompt used on <acronym>SMP</acronym> systems, the digit + indicates the number of the active <acronym>CPU</acronym>.</para> </callout> </calloutlist> - <para>At this point, place the CDROM into the drive, and from + <para>At this point, place the <acronym>CD</acronym> into the drive, and from the <acronym>PROM</acronym> prompt, type <command>boot cdrom</command>.</para> </sect3> @@ -977,7 +977,7 @@ Trying to mount root from cd9660:/dev/is <para>After the procedure of device probing, the menu shown in <xref linkend="bsdinstall-choose-mode"/> will be displayed. The install media - can be used in three ways: to install &os;, as a live CD as described in + can be used in three ways: to install &os;, as a live <acronym>CD</acronym> as described in <xref linkend="using-live-cd"/>, or to access a &os; shell. Use the arrow keys to choose an option, and <keycap>Enter</keycap> to select.</para> @@ -1124,8 +1124,8 @@ Trying to mount root from cd9660:/dev/is <para>Deciding which components to install will depend largely on the intended use of the system and the amount of disk space - available. The &os; Kernel and userland (collectively the - <quote>base system</quote>) are always installed.</para> + available. The &os; kernel and userland, collectively known as the + <quote>base system</quote>, are always installed.</para> <para>Depending on the type of installation, some of these components may not appear.</para> @@ -1141,7 +1141,7 @@ Trying to mount root from cd9660:/dev/is </listitem> <listitem> - <para><literal>games</literal> - Several traditional BSD + <para><literal>games</literal> - Several traditional <acronym>BSD</acronym> games, including <application>fortune</application>, <application>rot13</application>, and others.</para> </listitem> @@ -1360,8 +1360,8 @@ Trying to mount root from cd9660:/dev/is introduced in the smaller write heavy partitions will not bleed over into the mostly read partitions. Keeping the write loaded partitions closer to the disk's edge will - increase I/O performance in the partitions where it occurs - the most. While I/O performance in the larger partitions + increase<acronym> I/O</acronym> performance in the partitions where it occurs + the most. While <acronym>I/O</acronym> performance in the larger partitions may be needed, shifting them more toward the edge of the disk will not lead to a significant performance improvement over moving <filename>/var</filename> to the edge.</para> @@ -1620,7 +1620,7 @@ Trying to mount root from cd9660:/dev/is <filename>/</filename>, <filename>/var</filename>, <filename>/tmp</filename>, and <filename>/usr</filename> directories are separate file systems on their own - partitions, create a GPT partitioning scheme, then create + partitions, create a <acronym>GPT</acronym> partitioning scheme, then create the partitions as shown. Partition sizes shown are typical for a 20G target disk. If more space is available on the target disk, larger swap or <filename>/var</filename> @@ -1810,7 +1810,7 @@ Trying to mount root from cd9660:/dev/is <para>The menu also allows the user to enter a name for the pool, disable forcing 4k sectors, enable or disable - encryption, switch between GPT (recommended) and MBR partition + encryption, switch between <acronym>GPT</acronym> (recommended) and <acronym>MBR</acronym> partition table types, and select the desired amount of swap space. Once all options have been set to the desired values, select the <guibutton>>>> Install</guibutton> @@ -2092,7 +2092,7 @@ Trying to mount root from cd9660:/dev/is <sect3 xml:id="bsdinstall-ipv4"> <title>Configuring IPv4 Networking</title> - <para>Choose whether IPv4 networking is to be used. This is + <para>Choose whether <acronym>IPv4</acronym> networking is to be used. This is the most common type of network connection.</para> <figure xml:id="bsdinstall-configure-net-ipv4"> @@ -2106,7 +2106,7 @@ Trying to mount root from cd9660:/dev/is </mediaobject> </figure> - <para>There are two methods of IPv4 configuration. + <para>There are two methods of <acronym>IPv4</acronym> configuration. <emphasis><acronym>DHCP</acronym></emphasis> will automatically configure the network interface correctly, and is the preferred method. <emphasis>Static</emphasis> @@ -2121,14 +2121,14 @@ Trying to mount root from cd9660:/dev/is </note> <sect4 xml:id="bsdinstall-net-ipv4-dhcp-config"> - <title>IPv4 DHCP Network Configuration</title> + <title><acronym>IPv4</acronym> <acronym>DHCP</acronym> Network Configuration</title> - <para>If a DHCP server is available, select + <para>If a <acronym>DHCP</acronym> server is available, select <guibutton>[ Yes ]</guibutton> to automatically configure the network interface.</para> <figure xml:id="bsdinstall-net-ipv4-dhcp"> - <title>Choose IPv4 DHCP Configuration</title> + <title>Choose <acronym>IPv4</acronym> <acronym>DHCP</acronym> Configuration</title> <mediaobject> <imageobject> @@ -2140,13 +2140,13 @@ Trying to mount root from cd9660:/dev/is </sect4> <sect4 xml:id="bsdinstall-net-ipv4-static-config"> - <title>IPv4 Static Network Configuration</title> + <title><acronym>IPv4</acronym> Static Network Configuration</title> <para>Static configuration of the network interface requires - entry of some IPv4 information.</para> + entry of some <acronym>IPv4</acronym> information.</para> <figure xml:id="bsdinstall-net-ipv4-static"> - <title>IPv4 Static Configuration</title> + <title><acronym>IPv4</acronym> Static Configuration</title> <mediaobject> <imageobject> @@ -2159,7 +2159,7 @@ Trying to mount root from cd9660:/dev/is <itemizedlist> <listitem> <para><literal>IP Address</literal> - The - manually-assigned IPv4 address to be assigned to this + manually-assigned <acronym>IPv4</acronym> address to be assigned to this computer. This address must be unique and not already in use by another piece of equipment on the local network.</para> @@ -2186,8 +2186,8 @@ Trying to mount root from cd9660:/dev/is <sect3 xml:id="bsdinstall-ipv6"> <title>Configuring IPv6 Networking</title> - <para>IPv6 is a newer method of network configuration. If - IPv6 is available and desired, choose + <para><acronym>IPv6</acronym> is a newer method of network configuration. If + <acronym>IPv6</acronym> is available and desired, choose <guibutton>[ Yes ]</guibutton> to select it.</para> @@ -2210,9 +2210,9 @@ Trying to mount root from cd9660:/dev/is requires manual entry of network information.</para> <sect4 xml:id="bsdinstall-net-ipv6-slaac-config"> - <title>IPv6 Stateless Address Autoconfiguration</title> + <title><acronym>IPv6</acronym> Stateless Address Autoconfiguration</title> - <para><acronym>SLAAC</acronym> allows an IPv6 network + <para><acronym>SLAAC</acronym> allows an <acronym>IPv6</acronym> network component to request autoconfiguration information from a local router. See <link xlink:href="http://tools.ietf.org/html/rfc4862">http://tools.ietf.org/html/rfc4862</link>; @@ -2231,10 +2231,10 @@ Trying to mount root from cd9660:/dev/is </sect4> <sect4 xml:id="bsdinstall-net-ipv6-static-config"> - <title>IPv6 Static Network Configuration</title> + <title><acronym>IPv6</acronym> Static Network Configuration</title> <para>Static configuration of the network interface requires - entry of the IPv6 configuration information.</para> + entry of the <acronym>IPv6 </acronym>configuration information.</para> <figure xml:id="bsdinstall-net-ipv6-static"> <title>IPv6 Static Configuration</title> @@ -2271,8 +2271,8 @@ Trying to mount root from cd9660:/dev/is <sect3 xml:id="bsdinstall-net-dns"> <title>Configuring <acronym>DNS</acronym></title> - <para>The <emphasis>Domain Name System</emphasis> (or - <emphasis><acronym>DNS</acronym></emphasis>) Resolver + <para>The Domain Name System + (<acronym>DNS</acronym>) resolver converts hostnames to and from network addresses. If <acronym>DHCP</acronym> or <acronym>SLAAC</acronym> was used to autoconfigure the network interface, the @@ -2501,7 +2501,7 @@ Trying to mount root from cd9660:/dev/is </listitem> <listitem> - <para><literal>Uid</literal> - User ID. Typically, this + <para><literal>Uid</literal> - User <acronym>ID</acronym>. Typically, this is left blank so the system will assign a value.</para> </listitem> @@ -2689,12 +2689,12 @@ Trying to mount root from cd9660:/dev/is <para>If further configuration or special setup is needed, selecting <guibutton>[ Live CD ]</guibutton> - will boot the install media into Live CD mode.</para> + will boot the install media into Live <acronym>CD</acronym> mode.</para> <para>When the installation is complete, select <guibutton>[ Reboot ]</guibutton> to reboot the computer and start the new &os; system. Do not forget to - remove the &os; install CD, DVD, or USB memory stick, or the + remove the &os; install <acronym>CD</acronym>, <acronym>DVD</acronym>, or <acronym>USB</acronym> memory stick, or the computer may boot from it again.</para> </sect2> @@ -2893,7 +2893,7 @@ FreeBSD/amd64 (machine3.example.com) (tt login:</screen> - <para>Generating the RSA and DSA keys may take some time on + <para>Generating the <acronym>RSA</acronym> and <acronym>DSA</acronym> keys may take some time on slower machines. This happens only on the initial boot-up of a new installation, and only if <application>sshd</application> is set to start @@ -2961,8 +2961,8 @@ login:</screen> add support for devices which are not present in the <filename>GENERIC</filename> kernel. The kernel on the boot disks is configured assuming that most hardware devices - are in their factory default configuration in terms of IRQs, - IO addresses, and DMA channels. If the hardware has been + are in their factory default configuration in terms of <acronym>IRQ</acronym>s, + <acronym>I/O</acronym> addresses, and <acronym>DMA</acronym> channels. If the hardware has been reconfigured, a custom kernel configuration file can tell &os; where to find things.</para> @@ -3001,12 +3001,12 @@ login:</screen> <answer> <para>&os; makes extensive use of the system - ACPI service on the i386, amd64, and ia64 platforms to + <acronym>ACPI</acronym> service on the i386, amd64, and ia64 platforms to aid in system configuration if it is detected during boot. Unfortunately, some bugs still exist in both the - ACPI driver and within system motherboards and + <acronym>ACPI</acronym> driver and within system motherboards and <acronym>BIOS</acronym> - firmware. ACPI can be disabled by setting + firmware. <acronym>ACPI</acronym> can be disabled by setting the <literal>hint.acpi.0.disabled</literal> hint in the third stage boot loader:</para> @@ -3026,16 +3026,16 @@ login:</screen> </sect1> <sect1 xml:id="using-live-cd"> - <title>Using the Live CD</title> + <title>Using the Live <acronym>CD</acronym></title> - <para>A live CD of &os; is available on the same CD as the main + <para>A live <acronym>CD</acronym> of &os; is available on the same <acronym>CD</acronym> as the main installation program. This is useful for those who are still wondering whether &os; is the right operating system for them and want to test some of the features before installing.</para> <note> <para>The following points should be noted while using the live - CD:</para> + <acronym>CD</acronym>:</para> <itemizedlist> <listitem> <para>To gain access to the system, authentication is @@ -3045,13 +3045,13 @@ login:</screen> </listitem> <listitem> - <para>As the system runs directly from the CD, performance + <para>As the system runs directly from the <acronym>CD</acronym>, performance will be significantly slower than that of a system installed on a hard disk.</para> </listitem> <listitem> - <para>The live CD provides a command prompt and not a + <para>The live <acronym>CD</acronym> provides a command prompt and not a graphical interface.</para> </listitem> </itemizedlist>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201404242211.s3OMBkOD066761>