Date: Fri, 2 Nov 2012 04:13:41 +0000 (UTC) From: Warren Block <wblock@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r39908 - head/en_US.ISO8859-1/books/handbook/disks Message-ID: <201211020413.qA24DfDZ040748@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: wblock Date: Fri Nov 2 04:13:41 2012 New Revision: 39908 URL: http://svn.freebsd.org/changeset/doc/39908 Log: Whitespace-only fixes. Translators, please ignore. Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Fri Nov 2 01:57:49 2012 (r39907) +++ head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Fri Nov 2 04:13:41 2012 (r39908) @@ -237,6 +237,7 @@ <sect2> <title>Using &man.sysinstall.8;</title> + <indexterm> <primary><application>sysinstall</application></primary> <secondary>adding disks</secondary> @@ -278,6 +279,7 @@ <step> <title>Disk Label Editor</title> + <indexterm><primary>BSD partitions</primary></indexterm> <para>Next, you need to exit @@ -358,6 +360,7 @@ <sect3> <title>Dedicated</title> + <indexterm><primary>OS/2</primary></indexterm> <para>If you will not be sharing the new drive with another @@ -572,7 +575,7 @@ bsdlabel -e ad3</programlisting> </calloutlist> <para>After running &man.ccdconfig.8; the &man.ccd.4; is - configured. A file system can be installed. Refer to + configured. A file system can be installed. Refer to &man.newfs.8; for options, or simply run: </para> <programlisting>newfs /dev/ccd0c</programlisting> @@ -770,6 +773,7 @@ ar0: ATA RAID1 subdisks: ad4 ad6 status: </sect1info> <title>USB Storage Devices</title> + <indexterm> <primary>USB</primary> <secondary>disks</secondary> @@ -961,6 +965,7 @@ umass0: detached</screen> </sect1info> <title>Creating and Using Optical Media (CDs)</title> + <indexterm> <primary>CDROMs</primary> <secondary>creating</secondary> @@ -1125,6 +1130,7 @@ umass0: detached</screen> <sect2 id="burncd"> <title><application>burncd</application></title> + <indexterm> <primary>CDROMs</primary> <secondary>burning</secondary> @@ -1506,6 +1512,7 @@ cd0: Attempt to query device size failed </sect1info> <title>Creating and Using Optical Media (DVDs)</title> + <indexterm> <primary>DVD</primary> <secondary>burning</secondary> @@ -1542,8 +1549,8 @@ cd0: Attempt to query device size failed removable hard drive. However, this media is not compatible with most DVD-ROM drives and DVD-Video players; only a few DVD writers support the DVD-RAM format. Read - the <xref linkend="creating-dvd-ram"/> for more information - on DVD-RAM use.</para> + the <xref linkend="creating-dvd-ram"/> for more + information on DVD-RAM use.</para> </listitem> <listitem> @@ -1589,8 +1596,8 @@ cd0: Attempt to query device size failed devices, therefore the <link linkend="atapicam">ATAPI/CAM support</link> must be added to your kernel. If your burner uses the USB interface this addition is useless, and you - should read the <xref linkend="usb-disks"/> for more details on - USB devices configuration.</para> + should read the <xref linkend="usb-disks"/> for more details + on USB devices configuration.</para> <para>You also have to enable DMA access for ATAPI devices, this can be done in adding the following line to the @@ -2046,7 +2053,7 @@ cd0: Attempt to query device size failed <sect2> <title>The File System</title> - <para>Now the floppy is ready to be high-level formatted. This + <para>Now the floppy is ready to be high-level formatted. This will place a new file system on it, which will let FreeBSD read and write to the disk. After creating the new file system, the disk label is destroyed, so if you want to @@ -2123,6 +2130,7 @@ cd0: Attempt to query device size failed <sect2 id="backups-tapebackups-8mm"> <title>8mm (Exabyte)</title> + <indexterm> <primary>tape media</primary> <secondary>Exabyte (8mm) tapes</secondary> @@ -2205,6 +2213,7 @@ cd0: Attempt to query device size failed <sect2 id="backups-tapebackups-dlt"> <title>DLT</title> + <indexterm> <primary>tape media</primary> <secondary>DLT</secondary> @@ -2242,6 +2251,7 @@ cd0: Attempt to query device size failed <sect2> <title id="backups-tapebackups-ait">AIT</title> + <indexterm> <primary>tape media</primary> <secondary>AIT</secondary> @@ -2310,6 +2320,7 @@ sa0(ncr1:4:0): Logical unit is in proce <sect2 id="floppies-using"> <title>Can I Use Floppies for Backing Up My Data?</title> + <indexterm><primary>backup floppies</primary></indexterm> <indexterm><primary>floppy disks</primary></indexterm> @@ -2369,6 +2380,7 @@ sa0(ncr1:4:0): Logical unit is in proce <sect2 id="floppies-compress"> <title>Can I Compress My Backups?</title> + <indexterm> <primary><command>tar</command></primary> </indexterm> @@ -2600,7 +2612,7 @@ sa0(ncr1:4:0): Logical unit is in proce <example> <title>Using <command>dump</command> over <application>ssh</application> with <envar>RSH</envar> - set</title> + Set</title> <screen>&prompt.root; <userinput>env RSH=/usr/bin/ssh /sbin/dump -0uan -f targetuser@targetmachine.example.com:/dev/sa0 /usr</userinput></screen> </example> @@ -2608,6 +2620,7 @@ sa0(ncr1:4:0): Logical unit is in proce <sect2> <title><command>tar</command></title> + <indexterm> <primary>backup software</primary> <secondary><command>tar</command></secondary> @@ -2635,6 +2648,7 @@ sa0(ncr1:4:0): Logical unit is in proce <sect2> <title><command>cpio</command></title> + <indexterm> <primary>backup software</primary> <secondary><command>cpio</command></secondary> @@ -2698,6 +2712,7 @@ sa0(ncr1:4:0): Logical unit is in proce <sect2 id="backups-programs-amanda"> <title><application>Amanda</application></title> + <indexterm> <primary>backup software</primary> <secondary><application>Amanda</application></secondary> @@ -2764,6 +2779,7 @@ sa0(ncr1:4:0): Logical unit is in proce <sect2> <title>Which Backup Program Is Best?</title> + <indexterm> <primary>LISA</primary> </indexterm> @@ -2925,6 +2941,7 @@ sa0(ncr1:4:0): Logical unit is in proce </authorgroup> </sect1info> <title>Network, Memory, and File-Backed File Systems</title> + <indexterm><primary>virtual disks</primary></indexterm> <indexterm> <primary>disks</primary> @@ -2957,6 +2974,7 @@ sa0(ncr1:4:0): Logical unit is in proce <sect2 id="disks-mdconfig"> <title>File-Backed File System</title> + <indexterm> <primary>disks</primary> <secondary>file-backed</secondary> @@ -3227,6 +3245,7 @@ Filesystem 1K-blocks Used Avail Capacity <sect1 id="quotas"> <title>File System Quotas</title> + <indexterm> <primary>accounting</primary> <secondary>disk space</secondary> @@ -3268,6 +3287,7 @@ Filesystem 1K-blocks Used Avail Capacity line instead:</para> <programlisting>quota_enable="YES"</programlisting> + <indexterm> <primary>disk quotas</primary> <secondary>checking</secondary> @@ -3331,6 +3351,7 @@ Filesystem 1K-blocks Used Avail Capacity <sect2> <title>Setting Quota Limits</title> + <indexterm> <primary>disk quotas</primary> <secondary>limits</secondary> @@ -3371,7 +3392,7 @@ Filesystem 1K-blocks Used Avail Capacity grace period, which is one week by default. If a user stays over his or her soft limit longer than the grace period, the soft limit will turn into a hard limit and no further - allocations will be allowed. When the user drops back below + allocations will be allowed. When the user drops back below the soft limit, the grace period will be reset.</para> <para>The following is an example of what you might see when you @@ -3424,6 +3445,7 @@ Filesystem 1K-blocks Used Avail Capacity <sect2> <title>Checking Quota Limits and Disk Usage</title> + <indexterm> <primary>disk quotas</primary> <secondary>checking</secondary> @@ -3586,9 +3608,9 @@ Password:</screen> <title>Add the New Hard Drive</title> <para>Install the new drive to the system as explained in - <xref linkend="disks-adding"/>. For the purposes of this - example, a new hard drive partition has been added as - <filename>/dev/ad4s1c</filename>. The + <xref linkend="disks-adding"/>. For the purposes of + this example, a new hard drive partition has been added + as <filename>/dev/ad4s1c</filename>. The <filename>/dev/ad0s1<replaceable>*</replaceable></filename> devices represent existing standard FreeBSD partitions on the example system.</para> @@ -3600,7 +3622,8 @@ Password:</screen> </step> <step> - <title>Create a Directory to Hold gbde Lock Files</title> + <title>Create a Directory to Hold <command>gbde</command> + Lock Files</title> <screen>&prompt.root; <userinput>mkdir /etc/gbde</userinput></screen> @@ -3616,10 +3639,11 @@ Password:</screen> </step> <step> - <title>Initialize the gbde Partition</title> + <title>Initialize the <command>gbde</command> + Partition</title> <para>A <application>gbde</application> partition must be - initialized before it can be used. This initialization + initialized before it can be used. This initialization needs to be performed only once:</para> <screen>&prompt.root; <userinput>gbde init /dev/ad4s1c -i -L /etc/gbde/ad4s1c.lock</userinput></screen> @@ -3753,12 +3777,13 @@ Filesystem Size Used Avail Cap <para>After each boot, any encrypted file systems must be re-attached to the kernel, checked for errors, and mounted, - before the file systems can be used. The required commands + before the file systems can be used. The required commands must be executed as user <username>root</username>.</para> <procedure> <step> - <title>Attach the gbde Partition to the Kernel</title> + <title>Attach the <command>gbde</command> Partition to the + Kernel</title> <screen>&prompt.root; <userinput>gbde attach /dev/ad4s1c -l /etc/gbde/ad4s1c.lock</userinput></screen> @@ -3816,7 +3841,8 @@ gbde_lockdir="/etc/gbde"</programlisting </sect3> <sect3> - <title>Cryptographic Protections Employed by gbde</title> + <title>Cryptographic Protections Employed by + <command>gbde</command></title> <para>&man.gbde.8; encrypts the sector payload using 128-bit AES in CBC mode. Each sector on the disk is encrypted with @@ -4223,6 +4249,7 @@ Device 1K-blocks Used Av </sect1info> <title>Highly Available Storage (HAST)</title> + <indexterm> <primary>HAST</primary> <secondary>high availability</secondary> @@ -4621,11 +4648,11 @@ Device 1K-blocks Used Av same network segment to share an IP address. Set up <acronym>CARP</acronym> on both nodes of the cluster according to the documentation available in - <xref linkend="carp"/>. After setup, each node will have its - own <devicename>carp0</devicename> interface with a shared - IP address <replaceable>172.16.0.254</replaceable>. The - primary <acronym>HAST</acronym> node of the cluster must be - the master <acronym>CARP</acronym> node.</para> + <xref linkend="carp"/>. After setup, each node will have + its own <devicename>carp0</devicename> interface with a + shared IP address <replaceable>172.16.0.254</replaceable>. + The primary <acronym>HAST</acronym> node of the cluster must + be the master <acronym>CARP</acronym> node.</para> <para>The <acronym>HAST</acronym> pool created in the previous section is now ready to be exported to the other hosts on
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201211020413.qA24DfDZ040748>