svn commit: r43449 - head/en_US.ISO8859-1/books/handbook/disks
Warren Block
wblock at FreeBSD.org
Wed Jan 8 18:58:17 UTC 2014
Author: wblock
Date: Wed Jan 8 18:58:16 2014
New Revision: 43449
URL: http://svnweb.freebsd.org/changeset/doc/43449
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 Wed Jan 8 17:57:01 2014 (r43448)
+++ head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Wed Jan 8 18:58:16 2014 (r43449)
@@ -4,16 +4,19 @@
$FreeBSD$
-->
-<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="disks">
+
+<chapter xmlns="http://docbook.org/ns/docbook"
+ xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
+ xml:id="disks">
+
<title>Storage</title>
<sect1 xml:id="disks-synopsis">
<title>Synopsis</title>
- <para>This chapter covers the use of disks in &os;. This
- includes memory-backed disks, network-attached disks,
- standard SCSI/IDE storage devices, and devices using the USB
- interface.</para>
+ <para>This chapter covers the use of disks in &os;. This includes
+ memory-backed disks, network-attached disks, standard SCSI/IDE
+ storage devices, and devices using the USB interface.</para>
<para>After reading this chapter, you will know:</para>
@@ -112,6 +115,7 @@
<entry><literal>acd</literal> or
<literal>cd</literal></entry>
</row>
+
<row>
<entry>SCSI hard drives and USB Mass storage
devices</entry>
@@ -165,15 +169,20 @@
</sect1>
<sect1 xml:id="disks-adding">
- <info><title>Adding Disks</title>
+ <info>
+ <title>Adding Disks</title>
+
<authorgroup>
- <author><personname><firstname>David</firstname><surname>O'Brien</surname></personname><contrib>Originally contributed by </contrib></author>
+ <author>
+ <personname>
+ <firstname>David</firstname>
+ <surname>O'Brien</surname>
+ </personname>
+ <contrib>Originally contributed by </contrib>
+ </author>
</authorgroup>
-
</info>
-
-
<indexterm>
<primary>disks</primary>
<secondary>adding</secondary>
@@ -183,8 +192,9 @@
<acronym>SATA</acronym> disk to a machine that currently only
has a single drive. First, turn off the computer and install
the drive in the computer following the instructions of the
- computer, controller, and drive manufacturers. Reboot
- the system and become <systemitem class="username">root</systemitem>.</para>
+ computer, controller, and drive manufacturers. Reboot the
+ system and become
+ <systemitem class="username">root</systemitem>.</para>
<para>Inspect <filename>/var/run/dmesg.boot</filename> to ensure
the new disk was found. In this example, the newly added
@@ -197,7 +207,8 @@
</indexterm>
<para>For this example, a single large partition will be created
- on the new disk. The <link xlink:href="http://en.wikipedia.org/wiki/GUID_Partition_Table">
+ on the new disk. The <link
+ xlink:href="http://en.wikipedia.org/wiki/GUID_Partition_Table">
<acronym>GPT</acronym></link> partitioning scheme will be
used in preference to the older and less versatile
<acronym>MBR</acronym> scheme.</para>
@@ -242,15 +253,20 @@
</sect1>
<sect1 xml:id="usb-disks">
- <info><title>USB Storage Devices</title>
+ <info>
+ <title>USB Storage Devices</title>
+
<authorgroup>
- <author><personname><firstname>Marc</firstname><surname>Fonvieille</surname></personname><contrib>Contributed by </contrib></author>
+ <author>
+ <personname>
+ <firstname>Marc</firstname>
+ <surname>Fonvieille</surname>
+ </personname>
+ <contrib>Contributed by </contrib>
+ </author>
</authorgroup>
-
</info>
-
-
<indexterm>
<primary>USB</primary>
<secondary>disks</secondary>
@@ -263,9 +279,9 @@
<sect2>
<title>Configuration</title>
- <para>The USB mass storage devices driver, &man.umass.4;,
- is built into the <filename>GENERIC</filename> kernel
- and provides support for USB storage devices. For a custom
+ <para>The USB mass storage devices driver, &man.umass.4;, is
+ built into the <filename>GENERIC</filename> kernel and
+ provides support for USB storage devices. For a custom
kernel, be sure that the following lines are present in the
kernel configuration file:</para>
@@ -337,8 +353,9 @@ da0: 126MB (258048 512 byte sectors: 64H
<para>To make the device mountable as a normal user, one
solution is to make all users of the device a member of the
- <systemitem class="groupname">operator</systemitem> group using &man.pw.8;.
- Next, ensure that the <systemitem class="groupname">operator</systemitem> group is
+ <systemitem class="groupname">operator</systemitem> group
+ using &man.pw.8;. Next, ensure that the
+ <systemitem class="groupname">operator</systemitem> group is
able to read and write the device by adding these lines to
<filename>/etc/devfs.rules</filename>:</para>
@@ -354,7 +371,8 @@ add path 'da*' mode 0660 group operator<
<para>This will exclude the first three SCSI disks
(<filename>da0</filename> to
<filename>da2</filename>)from belonging to the
- <systemitem class="groupname">operator</systemitem> group.</para>
+ <systemitem class="groupname">operator</systemitem>
+ group.</para>
</note>
<para>Next, enable the &man.devfs.rules.5; ruleset in
@@ -375,12 +393,12 @@ add path 'da*' mode 0660 group operator<
<para>The final step is to create a directory where the file
system is to be mounted. This directory needs to be owned by
the user that is to mount the file system. One way to do that
- is for <systemitem class="username">root</systemitem> to create a subdirectory
- owned by that user as <filename>/mnt/username</filename>.
- In the following example, replace
- <replaceable>username</replaceable> with the login name of the
- user and <replaceable>usergroup</replaceable> with the user's
- primary group:</para>
+ is for <systemitem class="username">root</systemitem> to
+ create a subdirectory owned by that user as
+ <filename>/mnt/username</filename>. In the following example,
+ replace <replaceable>username</replaceable> with the login
+ name of the user and <replaceable>usergroup</replaceable> with
+ the user's primary group:</para>
<screen>&prompt.root; <userinput>mkdir /mnt/username</userinput>
&prompt.root; <userinput>chown username:usergroup /mnt/username</userinput></screen>
@@ -417,15 +435,20 @@ umass0: detached</screen>
</sect1>
<sect1 xml:id="creating-cds">
- <info><title>Creating and Using CD Media</title>
+ <info>
+ <title>Creating and Using CD Media</title>
+
<authorgroup>
- <author><personname><firstname>Mike</firstname><surname>Meyer</surname></personname><contrib>Contributed by </contrib></author>
+ <author>
+ <personname>
+ <firstname>Mike</firstname>
+ <surname>Meyer</surname>
+ </personname>
+ <contrib>Contributed by </contrib>
+ </author>
</authorgroup>
-
</info>
-
-
<indexterm>
<primary>CD-ROMs</primary>
<secondary>creating</secondary>
@@ -476,18 +499,17 @@ umass0: detached</screen>
<para>Which tool to use to burn the CD depends on whether the
CD burner is ATAPI or something else. ATAPI CD burners use
- <command>burncd</command>
- which is part of the base system. SCSI and USB CD burners
- should use <command>cdrecord</command> from the
- <package>sysutils/cdrtools</package> port.
- It is also possible to use <command>cdrecord</command> and other tools
- for SCSI drives on ATAPI hardware with the <link linkend="atapicam">ATAPI/CAM module</link>.</para>
+ <command>burncd</command> which is part of the base system.
+ SCSI and USB CD burners should use <command>cdrecord</command>
+ from the <package>sysutils/cdrtools</package> port. It is
+ also possible to use <command>cdrecord</command> and other
+ tools for SCSI drives on ATAPI hardware with the
+ <link linkend="atapicam">ATAPI/CAM module</link>.</para>
<para>For CD burning software with a graphical user
interface, consider <application>X-CD-Roast</application> or
<application>K3b</application>. These tools are available as
- packages or from the
- <package>sysutils/xcdroast</package> and
+ packages or from the <package>sysutils/xcdroast</package> and
<package>sysutils/k3b</package> ports.
<application>X-CD-Roast</application> and
<application>K3b</application> require the
@@ -549,15 +571,16 @@ umass0: detached</screen>
in producing an <quote>El Torito</quote> bootable CD. This
option takes an argument which is the path to a boot image
from the top of the tree being written to the CD. By default,
- &man.mkisofs.8; creates an ISO image in <quote>floppy disk
- emulation</quote> mode, and thus expects the boot image to
- be exactly 1200, 1440 or 2880 KB in size. Some boot
- loaders, like the one used by the &os; distribution disks, do
- not use emulation mode. In this case,
+ &man.mkisofs.8; creates an ISO image in
+ <quote>floppy disk emulation</quote> mode, and thus expects
+ the boot image to be exactly 1200, 1440 or 2880 KB in
+ size. Some boot loaders, like the one used by the &os;
+ distribution disks, do not use emulation mode. In this case,
<option>-no-emul-boot</option> should be used. So, if
- <filename>/tmp/myboot</filename> holds a
- bootable &os; system with the boot image in <filename>/tmp/myboot/boot/cdboot</filename>, this
- command would produce the image of an ISO 9660 file system as
+ <filename>/tmp/myboot</filename> holds a bootable &os; system
+ with the boot image in
+ <filename>/tmp/myboot/boot/cdboot</filename>, this command
+ would produce the image of an ISO 9660 file system as
<filename>/tmp/bootable.iso</filename>:</para>
<screen>&prompt.root; <userinput>mkisofs -R -no-emul-boot -b boot/cdboot -o /tmp/bootable.iso /tmp/myboot</userinput></screen>
@@ -569,8 +592,8 @@ umass0: detached</screen>
<screen>&prompt.root; <userinput>mdconfig -a -t vnode -f /tmp/bootable.iso -u 0</userinput>
&prompt.root; <userinput>mount -t cd9660 /dev/md0 /mnt</userinput></screen>
- <para>One can then verify that <filename>/mnt</filename> and <filename>/tmp/myboot</filename> are
- identical.</para>
+ <para>One can then verify that <filename>/mnt</filename> and
+ <filename>/tmp/myboot</filename> are identical.</para>
<para>There are many other options available for
&man.mkisofs.8; to fine-tune its behavior. Refer to
@@ -606,11 +629,12 @@ umass0: detached</screen>
<para>For systems without an ATAPI CD burner,
<command>cdrecord</command> can be used to burn CDs.
<command>cdrecord</command> is not part of the base system and
- must be installed from either the <package>sysutils/cdrtools</package> package or port.
- Changes to the base system can cause binary versions of this
- program to fail, possibly resulting in a
- <quote>coaster</quote>. It is recommended to either upgrade
- the port when the system is upgraded, or for users
+ must be installed from either the
+ <package>sysutils/cdrtools</package> package or port. Changes
+ to the base system can cause binary versions of this program
+ to fail, possibly resulting in a <quote>coaster</quote>. It
+ is recommended to either upgrade the port when the system is
+ upgraded, or for users
<link linkend="stable">tracking -STABLE</link>, to upgrade the
port when a new version becomes available.</para>
@@ -686,7 +710,8 @@ scsibus1:
<screen>&prompt.user; <userinput>cdrecord -v dev=2,0 -dao -useinfo *.wav</userinput></screen>
<para>Make sure that <replaceable>2,0</replaceable> is set
- appropriately, as described in <xref linkend="cdrecord"/>.</para>
+ appropriately, as described in
+ <xref linkend="cdrecord"/>.</para>
</step>
</procedure>
@@ -786,11 +811,11 @@ scsibus1:
<screen>&prompt.root; <userinput>mount_cd9660 /dev/cd0 /mnt</userinput></screen>
- <para>While data CD-ROMs from any vendor can be mounted this way,
- disks with certain ISO 9660 extensions might behave oddly.
- For example, Joliet disks store all filenames in two-byte
- Unicode characters. The &os; kernel does not speak Unicode,
- but the &os; CD9660 driver is able to convert Unicode
+ <para>While data CD-ROMs from any vendor can be mounted this
+ way, disks with certain ISO 9660 extensions might behave
+ oddly. For example, Joliet disks store all filenames in
+ two-byte Unicode characters. The &os; kernel does not speak
+ Unicode, but the &os; CD9660 driver is able to convert Unicode
characters on the fly. If some non-English characters show up
as question marks, specify the local charset with
<option>-C</option>. For more information, refer to
@@ -817,8 +842,9 @@ scsibus1:
that a media is present, so be patient.</para>
<para>Sometimes, a SCSI CD-ROM may be missed because it did not
- have enough time to answer the bus reset. To resolve this,add
- the following option to the kernel configuration and <link linkend="kernelconfig-building">rebuild the
+ have enough time to answer the bus reset. To resolve this,
+ add the following option to the kernel configuration and
+ <link linkend="kernelconfig-building">rebuild the
kernel</link>.</para>
<programlisting>options SCSI_DELAY=15000</programlisting>
@@ -843,22 +869,28 @@ scsibus1:
<screen>&prompt.root; <userinput>tar xzvf /dev/acd1</userinput></screen>
- <para>This type of disk can not be mounted as a normal CD-ROM and
- the data cannot be read under any operating system except
+ <para>This type of disk can not be mounted as a normal CD-ROM
+ and the data cannot be read under any operating system except
&os;. In order to mount the CD, or to share the data with
another operating system, &man.mkisofs.8; must be used as
described above.</para>
</sect2>
<sect2 xml:id="atapicam">
- <info><title>Using the ATAPI/CAM Driver</title>
+ <info>
+ <title>Using the ATAPI/CAM Driver</title>
+
<authorgroup>
- <author><personname><firstname>Marc</firstname><surname>Fonvieille</surname></personname><contrib>Contributed by </contrib></author>
+ <author>
+ <personname>
+ <firstname>Marc</firstname>
+ <surname>Fonvieille</surname>
+ </personname>
+ <contrib>Contributed by </contrib>
+ </author>
</authorgroup>
</info>
-
-
<indexterm>
<primary>CD burner</primary>
<secondary>ATAPI/CAM driver</secondary>
@@ -911,8 +943,9 @@ cd0: Attempt to query device size failed
<screen>&prompt.root; <userinput>mount -t cd9660 /dev/cd0 /mnt</userinput></screen>
- <para>As <systemitem class="username">root</systemitem>, run the following command
- to get the SCSI address of the burner:</para>
+ <para>As <systemitem class="username">root</systemitem>, run the
+ following command to get the SCSI address of the
+ burner:</para>
<screen>&prompt.root; <userinput>camcontrol devlist</userinput>
<MATSHITA CDRW/DVD UJDA740 1.00> at scbus1 target 0 lun 0 (pass0,cd0)</screen>
@@ -927,18 +960,29 @@ cd0: Attempt to query device size failed
</sect1>
<sect1 xml:id="creating-dvds">
- <info><title>Creating and Using DVD Media</title>
+ <info>
+ <title>Creating and Using DVD Media</title>
+
<authorgroup>
- <author><personname><firstname>Marc</firstname><surname>Fonvieille</surname></personname><contrib>Contributed by </contrib></author>
+ <author>
+ <personname>
+ <firstname>Marc</firstname>
+ <surname>Fonvieille</surname>
+ </personname>
+ <contrib>Contributed by </contrib>
+ </author>
</authorgroup>
<authorgroup>
- <author><personname><firstname>Andy</firstname><surname>Polyakov</surname></personname><contrib>With inputs from </contrib></author>
+ <author>
+ <personname>
+ <firstname>Andy</firstname>
+ <surname>Polyakov</surname>
+ </personname>
+ <contrib>With inputs from </contrib>
+ </author>
</authorgroup>
-
</info>
-
-
<indexterm>
<primary>DVD</primary>
<secondary>burning</secondary>
@@ -1009,8 +1053,9 @@ cd0: Attempt to query device size failed
<title>Configuration</title>
<para>To perform DVD recording, use &man.growisofs.1;. This
- command is part of the <package>sysutils/dvd+rw-tools</package> utilities
- which support all DVD media types.</para>
+ command is part of the
+ <package>sysutils/dvd+rw-tools</package> utilities which
+ support all DVD media types.</para>
<para>These tools use the SCSI subsystem to access the devices,
therefore <link linkend="atapicam">ATAPI/CAM support</link>
@@ -1026,13 +1071,14 @@ cd0: Attempt to query device size failed
<programlisting>hw.ata.atapi_dma="1"</programlisting>
<para>Before attempting to use
- <application>dvd+rw-tools</application>, consult the
- <link xlink:href="http://fy.chalmers.se/~appro/linux/DVD+RW/hcn.html">Hardware
+ <application>dvd+rw-tools</application>, consult the <link
+ xlink:href="http://fy.chalmers.se/~appro/linux/DVD+RW/hcn.html">Hardware
Compatibility Notes</link>.</para>
<note>
- <para>For a graphical user interface, consider using <package>sysutils/k3b</package> which provides a
- user friendly interface to &man.growisofs.1; and many other
+ <para>For a graphical user interface, consider using
+ <package>sysutils/k3b</package> which provides a user
+ friendly interface to &man.growisofs.1; and many other
burning tools.</para>
</note>
</sect2>
@@ -1040,7 +1086,8 @@ cd0: Attempt to query device size failed
<sect2>
<title>Burning Data DVDs</title>
- <para>Since &man.growisofs.1; is a front-end to <link linkend="mkisofs">mkisofs</link>, it will invoke
+ <para>Since &man.growisofs.1; is a front-end to
+ <link linkend="mkisofs">mkisofs</link>, it will invoke
&man.mkisofs.8; to create the file system layout and perform
the write on the DVD. This means that an image of the data
does not need to be created before the burning process.</para>
@@ -1098,11 +1145,12 @@ cd0: Attempt to query device size failed
additional options are required for &man.growisofs.1; to
burn that image on a disk.</para>
- <para>Be sure to use an up-to-date version of <package>sysutils/cdrtools</package>, which
- contains &man.mkisofs.8;, as an older version may not
- contain large files support. If the latest version does
- not work, install <package>sysutils/cdrtools-devel</package> and read
- its &man.mkisofs.8;.</para>
+ <para>Be sure to use an up-to-date version of
+ <package>sysutils/cdrtools</package>, which contains
+ &man.mkisofs.8;, as an older version may not contain large
+ files support. If the latest version does not work, install
+ <package>sysutils/cdrtools-devel</package> and read its
+ &man.mkisofs.8;.</para>
</note>
</sect2>
@@ -1117,14 +1165,14 @@ cd0: Attempt to query device size failed
<para>A DVD-Video is a specific file layout based on the ISO
9660 and micro-UDF (M-UDF) specifications. Since DVD-Video
presents a specific data structure hierarchy, a particular
- program such as <package>multimedia/dvdauthor</package> is needed to
- author the DVD.</para>
+ program such as <package>multimedia/dvdauthor</package> is
+ needed to author the DVD.</para>
<para>If an image of the DVD-Video file system already exists,
it can be burned in the same way as any other image. If
<command>dvdauthor</command> was used to make the DVD and the
- result is in <filename>/path/to/video</filename>, the following
- command should be used to burn the DVD-Video:</para>
+ result is in <filename>/path/to/video</filename>, the
+ following command should be used to burn the DVD-Video:</para>
<screen>&prompt.root; <userinput>growisofs -Z /dev/cd0 -dvd-video /path/to/video</userinput></screen>
@@ -1296,9 +1344,11 @@ cd0: Attempt to query device size failed
<para>More information about
<application>dvd+rw-tools</application> can be found in
- &man.growisofs.1;, on the <link xlink:href="http://fy.chalmers.se/~appro/linux/DVD+RW/">dvd+rw-tools
- web site</link>, and in the <link xlink:href="http://lists.debian.org/cdwrite/">cdwrite mailing
- list</link> archives.</para>
+ &man.growisofs.1;, on the <link
+ xlink:href="http://fy.chalmers.se/~appro/linux/DVD+RW/">dvd+rw-tools
+ web site</link>, and in the <link
+ xlink:href="http://lists.debian.org/cdwrite/">cdwrite
+ mailing list</link> archives.</para>
<note>
<para>When creating a problem report related to the use of
@@ -1357,19 +1407,30 @@ cd0: Attempt to query device size failed
</sect1>
<sect1 xml:id="floppies">
- <info><title>Creating and Using Floppy Disks</title>
+ <info>
+ <title>Creating and Using Floppy Disks</title>
+
<authorgroup>
- <author><personname><firstname>Julio</firstname><surname>Merino</surname></personname><contrib>Original work by </contrib></author>
+ <author>
+ <personname>
+ <firstname>Julio</firstname>
+ <surname>Merino</surname>
+ </personname>
+ <contrib>Original work by </contrib>
+ </author>
</authorgroup>
-
+
<authorgroup>
- <author><personname><firstname>Martin</firstname><surname>Karlsson</surname></personname><contrib>Rewritten by </contrib></author>
+ <author>
+ <personname>
+ <firstname>Martin</firstname>
+ <surname>Karlsson</surname>
+ </personname>
+ <contrib>Rewritten by </contrib>
+ </author>
</authorgroup>
-
</info>
-
-
<para>Storing data on floppy disks is sometimes useful, for
example when one does not have any other removable storage media
or when one needs to transfer small amounts of data to another
@@ -1536,7 +1597,8 @@ cd0: Attempt to query device size failed
<title xml:id="tapes-dumprestore">Using &man.dump.8; and
&man.restore.8; to Create and Restore Backups</title>
- <para>A simple backup of <filename>/usr</filename> with &man.dump.8;:</para>
+ <para>A simple backup of <filename>/usr</filename> with
+ &man.dump.8;:</para>
<screen>&prompt.root; <userinput>dump -0aL -b64 -f /dev/nsa0 /usr</userinput></screen>
@@ -1560,15 +1622,20 @@ cd0: Attempt to query device size failed
</sect1>
<sect1 xml:id="backup-strategies">
- <info><title>Backup Strategies</title>
+ <info>
+ <title>Backup Strategies</title>
+
<authorgroup>
- <author><personname><firstname>Lowell</firstname><surname>Gilbert</surname></personname><contrib>Original work by </contrib></author>
+ <author>
+ <personname>
+ <firstname>Lowell</firstname>
+ <surname>Gilbert</surname>
+ </personname>
+ <contrib>Original work by </contrib>
+ </author>
</authorgroup>
-
</info>
-
-
<para>The first requirement in devising a backup plan is to make
sure that all of the following problems are covered:</para>
@@ -1617,12 +1684,13 @@ cd0: Attempt to query device size failed
<listitem>
<para>Copies of whole file systems or disks which can be
- created with a periodic <package>net/rsync</package> of the whole machine.
- This is generally most useful in networks with unique
- requirements. For general protection against disk failure,
- this is usually inferior to <acronym>RAID</acronym>. For
- restoring accidentally deleted files, it can be comparable
- to <acronym>UFS</acronym> snapshots.</para>
+ created with a periodic <package>net/rsync</package> of the
+ whole machine. This is generally most useful in networks
+ with unique requirements. For general protection against
+ disk failure, this is usually inferior to
+ <acronym>RAID</acronym>. For restoring accidentally deleted
+ files, it can be comparable to <acronym>UFS</acronym>
+ snapshots.</para>
</listitem>
<listitem>
@@ -1682,9 +1750,9 @@ cd0: Attempt to query device size failed
<command>dump</command> does not write files and directories,
but rather writes the raw data blocks that comprise files and
directories. When used to extract data,
- <command>restore</command> stores temporary
- files in <filename>/tmp/</filename> by
- default. When using a recovery disk with a small <filename>/tmp</filename>, set
+ <command>restore</command> stores temporary files in
+ <filename>/tmp/</filename> by default. When using a recovery
+ disk with a small <filename>/tmp</filename>, set
<envar>TMPDIR</envar> to a directory with more free space in
order for the restore to succeed.</para>
@@ -1768,7 +1836,8 @@ cd0: Attempt to query device size failed
<indexterm><primary><command>tar</command></primary></indexterm>
<para>To <command>tar</command> to an Exabyte tape drive
- connected to a host called <systemitem>komodo</systemitem>:</para>
+ connected to a host called
+ <systemitem>komodo</systemitem>:</para>
<screen>&prompt.root; <userinput>tar cf - . | rsh komodo dd of=tape-device obs=20b</userinput></screen>
@@ -1925,7 +1994,8 @@ cd0: Attempt to query device size failed
unwritable files, devices, files that change size during the
backup, files that are created/deleted during the backup and
more. She presented the results at LISA V in Oct. 1991. See
- <link xlink:href="http://www.coredumps.de/doc/dump/zwicky/testdump.doc.html">torture-testing
+ <link
+ xlink:href="http://www.coredumps.de/doc/dump/zwicky/testdump.doc.html">torture-testing
Backup and Archive Programs</link>.</para>
</sect2>
@@ -1954,7 +2024,8 @@ cd0: Attempt to query device size failed
&man.restore.8;, &man.fdisk.8;, &man.bsdlabel.8;,
&man.newfs.8;, &man.mount.8;, and more. The livefs CD image
for &os;/&arch.i386; &rel2.current;-RELEASE is
- available from <uri xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-livefs.iso">ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-livefs.iso</uri>.</para>
+ available from <uri
+ xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-livefs.iso">ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-livefs.iso</uri>.</para>
<note>
<para>Livefs CD images are not available for
@@ -1963,7 +2034,8 @@ cd0: Attempt to query device size failed
images may be used to recover a system. The
<quote>memstick</quote> image for
&os;/&arch.i386; &rel.current;-RELEASE is available
- from <uri xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/&arch.i386;/ISO-IMAGES/&rel.current;/&os;-&rel.current;-RELEASE-&arch.i386;-memstick.img">ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/&arch.i386;/ISO-IMAGES/&rel.current;/&os;-&rel.current;-RELEASE-&arch.i386;-memstick.img</uri>.</para>
+ from <uri
+ xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/&arch.i386;/ISO-IMAGES/&rel.current;/&os;-&rel.current;-RELEASE-&arch.i386;-memstick.img">ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/&arch.i386;/ISO-IMAGES/&rel.current;/&os;-&rel.current;-RELEASE-&arch.i386;-memstick.img</uri>.</para>
</note>
<para>Third, create backup tapes regularly. Any changes that
@@ -2040,12 +2112,19 @@ cd0: Attempt to query device size failed
</sect1>
<sect1 xml:id="disks-virtual">
- <info><title>Network, Memory, and File-Backed File Systems</title>
+ <info>
+ <title>Network, Memory, and File-Backed File Systems</title>
+
<authorgroup>
- <author><personname><firstname>Marc</firstname><surname>Fonvieille</surname></personname><contrib>Reorganized and enhanced by </contrib></author>
+ <author>
+ <personname>
+ <firstname>Marc</firstname>
+ <surname>Fonvieille</surname>
+ </personname>
+ <contrib>Reorganized and enhanced by </contrib>
+ </author>
</authorgroup>
</info>
-
<indexterm><primary>virtual disks</primary></indexterm>
<indexterm>
@@ -2054,8 +2133,8 @@ cd0: Attempt to query device size failed
</indexterm>
<para>In addition to physical disks such as floppies, CDs, and
- hard drives, &os; also supports <firstterm>virtual
- disks</firstterm>.</para>
+ hard drives, &os; also supports
+ <firstterm>virtual disks</firstterm>.</para>
<indexterm><primary>NFS</primary></indexterm>
<indexterm><primary>Coda</primary></indexterm>
@@ -2235,15 +2314,20 @@ Filesystem 1K-blocks Used Avail Capacity
</sect1>
<sect1 xml:id="snapshots">
- <info><title>File System Snapshots</title>
+ <info>
+ <title>File System Snapshots</title>
+
<authorgroup>
- <author><personname><firstname>Tom</firstname><surname>Rhodes</surname></personname><contrib>Contributed by </contrib></author>
+ <author>
+ <personname>
+ <firstname>Tom</firstname>
+ <surname>Rhodes</surname>
+ </personname>
+ <contrib>Contributed by </contrib>
+ </author>
</authorgroup>
-
</info>
-
-
<indexterm>
<primary>file systems</primary>
<secondary>snapshots</secondary>
@@ -2323,19 +2407,19 @@ Filesystem 1K-blocks Used Avail Capacity
</listitem>
</itemizedlist>
- <para>The frozen <filename>/var</filename> is
- now available through <filename>/mnt</filename>. Everything will initially
- be in the same state it was during the snapshot creation time.
- The only exception is that any earlier snapshots will appear as
- zero length files. To unmount the snapshot, use:</para>
+ <para>The frozen <filename>/var</filename> is now available
+ through <filename>/mnt</filename>. Everything will initially be
+ in the same state it was during the snapshot creation time. The
+ only exception is that any earlier snapshots will appear as zero
+ length files. To unmount the snapshot, use:</para>
<screen>&prompt.root; <userinput>umount /mnt</userinput>
&prompt.root; <userinput>mdconfig -d -u 4</userinput></screen>
<para>For more information about <option>softupdates</option> and
file system snapshots, including technical papers, visit
- Marshall Kirk McKusick's website at
- <uri xlink:href="http://www.mckusick.com/">http://www.mckusick.com/</uri>.</para>
+ Marshall Kirk McKusick's website at <uri
+ xlink:href="http://www.mckusick.com/">http://www.mckusick.com/</uri>.</para>
</sect1>
<sect1 xml:id="quotas">
@@ -2365,13 +2449,13 @@ Filesystem 1K-blocks Used Avail Capacity
<programlisting>options QUOTA</programlisting>
- <para>Before &os; 9.2,
- the <filename>GENERIC</filename> kernel usually did not include this
- option. <command>sysctl kern.features.ufs_quota</command>
- can be used to test whether the current kernel supports
- quotas. If the option is not present, a custom kernel must be
- compiled. Refer to <xref linkend="kernelconfig"/> for more information on
- kernel configuration.</para>
+ <para>Before &os; 9.2, the <filename>GENERIC</filename>
+ kernel usually did not include this option.
+ <command>sysctl kern.features.ufs_quota</command> can be used
+ to test whether the current kernel supports quotas. If the
+ option is not present, a custom kernel must be compiled.
+ Refer to <xref linkend="kernelconfig"/> for more information
+ on kernel configuration.</para>
<para>Next, enable disk quotas in
<filename>/etc/rc.conf</filename>:</para>
@@ -2510,11 +2594,11 @@ Filesystem 1K-blocks Used Avail Capacity
<para>Sometimes it is desirable to set quota limits on a range
of UIDs. This can be done by passing <option>-p</option> to
&man.edquota.8;. First, assign the desired quota limit to a
- user, then run <command>edquota -p protouser
- startuid-enduid</command>. For example, if
- <systemitem class="username">test</systemitem> has the desired quota limits, the
- following command will duplicate those quota limits for UIDs
- 10,000 through 19,999:</para>
+ user, then run
+ <command>edquota -p protouser startuid-enduid</command>. For
+ example, if <systemitem class="username">test</systemitem> has
+ the desired quota limits, the following command will duplicate
+ those quota limits for UIDs 10,000 through 19,999:</para>
<screen>&prompt.root; <userinput>edquota -p test 10000-19999</userinput></screen>
@@ -2548,10 +2632,12 @@ Filesystem 1K-blocks Used Avail Capacity
/usr/var 0 50 75 0 50 60</programlisting>
<indexterm><primary>grace period</primary></indexterm>
+
<para>In this example, the user is currently 15 kbytes over the
- soft limit of 50 kbytes on <filename>/usr</filename> and has 5 days of grace
- period left. The asterisk <literal>*</literal> indicates that
- the user is currently over the quota limit.</para>
+ soft limit of 50 kbytes on <filename>/usr</filename> and has 5
+ days of grace period left. The asterisk <literal>*</literal>
+ indicates that the user is currently over the quota
+ limit.</para>
<para>Normally, file systems that the user is not using any disk
space on will not show in the output of &man.quota.1;, even if
@@ -2584,24 +2670,33 @@ Filesystem 1K-blocks Used Avail Capacity
</sect1>
<sect1 xml:id="disks-encrypting">
- <info><title>Encrypting Disk Partitions</title>
+ <info>
+ <title>Encrypting Disk Partitions</title>
+
<authorgroup>
- <author><personname><firstname>Lucky</firstname><surname>Green</surname></personname><contrib>Contributed by </contrib><affiliation>
- <address><email>shamrock at cypherpunks.to</email></address>
- </affiliation></author>
+ <author>
+ <personname>
+ <firstname>Lucky</firstname>
+ <surname>Green</surname>
+ </personname>
+ <contrib>Contributed by </contrib>
+ <affiliation>
+ <address>
+ <email>shamrock at cypherpunks.to</email>
+ </address>
+ </affiliation>
+ </author>
</authorgroup>
-
</info>
-
-
<indexterm>
<primary>disks</primary>
<secondary>encrypting</secondary>
</indexterm>
<para>&os; offers excellent online protections against
- unauthorized data access. File permissions and <link linkend="mac">Mandatory Access Control</link> (MAC) help
+ unauthorized data access. File permissions and
+ <link linkend="mac">Mandatory Access Control</link> (MAC) help
prevent unauthorized users from accessing data while the
operating system is active and the computer is powered up.
However, the permissions enforced by the operating system are
@@ -2725,7 +2820,8 @@ sector_size = 2048
<application>gbde</application> to protect data depends
entirely on the quality of the passphrase. For tips on
how to select a secure passphrase that is easy to
- remember, see the <link xlink:href="http://world.std.com/~reinhold/diceware.html">Diceware
+ remember, see the <link
+ xlink:href="http://world.std.com/~reinhold/diceware.html">Diceware
Passphrase</link> website.</para>
<para><command>gbde init</command>creates a lock file for
@@ -2828,7 +2924,8 @@ 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
- must be executed as <systemitem class="username">root</systemitem>.</para>
+ must be executed as
+ <systemitem class="username">root</systemitem>.</para>
<procedure>
<step>
@@ -2919,15 +3016,20 @@ gbde_lockdir="/etc/gbde"</programlisting
</sect2>
<sect2>
- <info><title>Disk Encryption with <command>geli</command></title>
+ <info>
+ <title>Disk Encryption with <command>geli</command></title>
+
<authorgroup>
- <author><personname><firstname>Daniel</firstname><surname>Gerzo</surname></personname><contrib>Contributed by </contrib></author>
+ <author>
+ <personname>
+ <firstname>Daniel</firstname>
+ <surname>Gerzo</surname>
+ </personname>
+ <contrib>Contributed by </contrib>
+ </author>
</authorgroup>
-
</info>
-
-
<para>An alternative cryptographic GEOM class is available
through &man.geli.8;. <command>geli</command> differs from
<command>gbde</command>; offers different features, and uses
@@ -3131,14 +3233,20 @@ geli_da2_flags="-p -k /root/da2.key"</pr
</sect1>
<sect1 xml:id="swap-encrypting">
- <info><title>Encrypting Swap Space</title>
+ <info>
+ <title>Encrypting Swap Space</title>
+
<authorgroup>
- <author><personname><firstname>Christian</firstname><surname>Brüffer</surname></personname><contrib>Written by </contrib></author>
+ <author>
+ <personname>
+ <firstname>Christian</firstname>
+ <surname>Brüffer</surname>
+ </personname>
+ <contrib>Written by </contrib>
+ </author>
</authorgroup>
</info>
-
-
<indexterm>
<primary>swap</primary>
<secondary>encrypting</secondary>
@@ -3147,12 +3255,12 @@ geli_da2_flags="-p -k /root/da2.key"</pr
<para>Like the encryption of disk partitions, encryption of swap
space is used to protect sensitive information. Consider an
application that deals with passwords. As long as these
- passwords stay in physical memory, these passwords will not
- be written to disk and be cleared after a reboot. If &os;
- starts swapping out memory pages to free
- space for other applications, the passwords may be written to
- the disk platters unencrypted. Encrypting swap space can be a
- solution for this scenario.</para>
+ passwords stay in physical memory, these passwords will not be
+ written to disk and be cleared after a reboot. If &os; starts
+ swapping out memory pages to free space for other applications,
+ the passwords may be written to the disk platters unencrypted.
+ Encrypting swap space can be a solution for this
+ scenario.</para>
<para>The &man.gbde.8; or &man.geli.8; encryption systems may be
used for swap encryption. Both systems use the
@@ -3233,21 +3341,51 @@ Device 1K-blocks Used Av
</sect1>
<sect1 xml:id="disks-hast">
- <info><title>Highly Available Storage (HAST)</title>
+ <info>
+ <title>Highly Available Storage (HAST)</title>
+
<authorgroup>
- <author><personname><firstname>Daniel</firstname><surname>Gerzo</surname></personname><contrib>Contributed by </contrib></author>
+ <author>
+ <personname>
+ <firstname>Daniel</firstname>
+ <surname>Gerzo</surname>
+ </personname>
+ <contrib>Contributed by </contrib>
+ </author>
</authorgroup>
+
<authorgroup>
- <author><personname><firstname>Freddie</firstname><surname>Cash</surname></personname><contrib>With inputs from </contrib></author>
- <author><personname><firstname>Pawel Jakub</firstname><surname>Dawidek</surname></personname></author>
- <author><personname><firstname>Michael W.</firstname><surname>Lucas</surname></personname></author>
- <author><personname><firstname>Viktor</firstname><surname>Petersson</surname></personname></author>
+ <author>
+ <personname>
+ <firstname>Freddie</firstname>
+ <surname>Cash</surname>
+ </personname>
+ <contrib>With inputs from </contrib>
+ </author>
+
+ <author>
+ <personname>
+ <firstname>Pawel Jakub</firstname>
+ <surname>Dawidek</surname>
+ </personname>
+ </author>
+
+ <author>
+ <personname>
+ <firstname>Michael W.</firstname>
+ <surname>Lucas</surname>
+ </personname>
+ </author>
+
+ <author>
+ <personname>
+ <firstname>Viktor</firstname>
+ <surname>Petersson</surname>
+ </personname>
+ </author>
</authorgroup>
-
</info>
-
-
<indexterm>
<primary>HAST</primary>
<secondary>high availability</secondary>
@@ -3261,8 +3399,8 @@ Device 1K-blocks Used Av
a key component in such environments. Highly Available
STorage, or <acronym>HAST<remark role="acronym">Highly
Available STorage</remark></acronym>, was developed by
- &a.pjd.email; as a framework which allows transparent storage of the
- same data across several physically separated machines
+ &a.pjd.email; as a framework which allows transparent storage
+ of the same data across several physically separated machines
connected by a TCP/IP network. <acronym>HAST</acronym> can be
understood as a network-based RAID1 (mirror), and is similar
to the DRBD® storage system known from the GNU/&linux;
@@ -3295,23 +3433,28 @@ Device 1K-blocks Used Av
<itemizedlist>
<listitem>
- <para>Understand &unix; and <link linkend="basics">&os; basics</link>.</para>
+ <para>Understand &unix; and
+ <link linkend="basics">&os; basics</link>.</para>
</listitem>
<listitem>
- <para>Know how to <link linkend="config-tuning">configure</link> network
+ <para>Know how to
+ <link linkend="config-tuning">configure</link> network
interfaces and other core &os; subsystems.</para>
</listitem>
<listitem>
- <para>Have a good understanding of <link linkend="network-communication">&os;
+ <para>Have a good understanding of
+ <link linkend="network-communication">&os;
networking</link>.</para>
</listitem>
</itemizedlist>
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
More information about the svn-doc-all
mailing list