diff options
Diffstat (limited to 'en_US.ISO8859-1/books/handbook/disks/chapter.xml')
| -rw-r--r-- | en_US.ISO8859-1/books/handbook/disks/chapter.xml | 691 |
1 files changed, 287 insertions, 404 deletions
diff --git a/en_US.ISO8859-1/books/handbook/disks/chapter.xml b/en_US.ISO8859-1/books/handbook/disks/chapter.xml index 59b56fbbaa..eda4426892 100644 --- a/en_US.ISO8859-1/books/handbook/disks/chapter.xml +++ b/en_US.ISO8859-1/books/handbook/disks/chapter.xml @@ -4,11 +4,10 @@ $FreeBSD$ --> - -<chapter 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 id="disks-synopsis"> + <sect1 xml:id="disks-synopsis"> <title>Synopsis</title> <para>This chapter covers the use of disks in &os;. This @@ -72,13 +71,13 @@ </itemizedlist> </sect1> - <sect1 id="disks-naming"> + <sect1 xml:id="disks-naming"> <title>Device Names</title> <para>The following is a list of physical storage devices supported in &os; and their associated device names.</para> - <table id="disk-naming-physical-table" frame="none"> + <table xml:id="disk-naming-physical-table" frame="none"> <title>Physical Disk Naming Conventions</title> <tgroup cols="2"> @@ -165,19 +164,15 @@ </table> </sect1> - <sect1 id="disks-adding"> - <sect1info> + <sect1 xml:id="disks-adding"> + <info><title>Adding Disks</title> <authorgroup> - <author> - <firstname>David</firstname> - <surname>O'Brien</surname> - <contrib>Originally contributed by </contrib> - </author> + <author><personname><firstname>David</firstname><surname>O'Brien</surname></personname><contrib>Originally contributed by </contrib></author> </authorgroup> - <!-- 26 Apr 1998 --> - </sect1info> + + </info> - <title>Adding Disks</title> + <indexterm> <primary>disks</primary> @@ -189,12 +184,12 @@ 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 <username>root</username>.</para> + 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 <acronym>SATA</acronym> drive will appear as - <devicename>ada1</devicename>.</para> + <filename>ada1</filename>.</para> <indexterm><primary>partitions</primary></indexterm> <indexterm> @@ -202,9 +197,8 @@ </indexterm> <para>For this example, a single large partition will be created - on the new disk. The <ulink - url="http://en.wikipedia.org/wiki/GUID_Partition_Table"> - <acronym>GPT</acronym></ulink> partitioning scheme will be + 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> @@ -247,19 +241,15 @@ <screen>&prompt.root; <userinput>mount /newdisk</userinput></screen> </sect1> - <sect1 id="usb-disks"> - <sect1info> + <sect1 xml:id="usb-disks"> + <info><title>USB Storage Devices</title> <authorgroup> - <author> - <firstname>Marc</firstname> - <surname>Fonvieille</surname> - <contrib>Contributed by </contrib> - </author> + <author><personname><firstname>Marc</firstname><surname>Fonvieille</surname></personname><contrib>Contributed by </contrib></author> </authorgroup> - <!-- Jul 2004 --> - </sect1info> + + </info> - <title>USB Storage Devices</title> + <indexterm> <primary>USB</primary> @@ -322,7 +312,7 @@ da0: <Generic Traveling Disk 1.11> Removable Direct Access SCSI-2 device da0: 1.000MB/s transfers da0: 126MB (258048 512 byte sectors: 64H 32S/T 126C)</screen> - <para>The brand, device node (<devicename>da0</devicename>), and + <para>The brand, device node (<filename>da0</filename>), and other details will differ according to the device.</para> <para>Since the USB device is seen as a SCSI one, @@ -347,8 +337,8 @@ da0: 126MB (258048 512 byte sectors: 64H 32S/T 126C)</screen> <para>To make the device mountable as a normal user, one solution is to make all users of the device a member of the - <groupname>operator</groupname> group using &man.pw.8;. - Next, ensure that the <groupname>operator</groupname> 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> @@ -362,9 +352,9 @@ add path 'da*' mode 0660 group operator</programlisting> <programlisting>add path 'da[3-9]*' mode 0660 group operator</programlisting> <para>This will exclude the first three SCSI disks - (<devicename>da0</devicename> to - <devicename>da2</devicename>)from belonging to the - <groupname>operator</groupname> group.</para> + (<filename>da0</filename> to + <filename>da2</filename>)from belonging to the + <systemitem class="groupname">operator</systemitem> group.</para> </note> <para>Next, enable the &man.devfs.rules.5; ruleset in @@ -385,23 +375,22 @@ add path 'da*' mode 0660 group operator</programlisting> <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 <username>root</username> to create a subdirectory - owned by that user as <filename - class="directory">/mnt/<replaceable>username</replaceable></filename>. + 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/<replaceable>username</replaceable></userinput> -&prompt.root; <userinput>chown <replaceable>username</replaceable>:<replaceable>usergroup</replaceable> /mnt/<replaceable>username</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>mkdir /mnt/username</userinput> +&prompt.root; <userinput>chown username:usergroup /mnt/username</userinput></screen> <para>Suppose a USB thumbdrive is plugged in, and a device <filename>/dev/da0s1</filename> appears. If the device is preformatted with a FAT file system, it can be mounted using:</para> - <screen>&prompt.user; <userinput>mount -t msdosfs -o -m=644,-M=755 /dev/da0s1 /mnt/<replaceable>username</replaceable></userinput></screen> + <screen>&prompt.user; <userinput>mount -t msdosfs -o -m=644,-M=755 /dev/da0s1 /mnt/username</userinput></screen> <para>Before the device can be unplugged, it <emphasis>must</emphasis> be unmounted first. After device @@ -427,20 +416,15 @@ umass0: detached</screen> </sect2> </sect1> - <sect1 id="creating-cds"> - <sect1info> + <sect1 xml:id="creating-cds"> + <info><title>Creating and Using CD Media</title> <authorgroup> - <author> - <firstname>Mike</firstname> - <surname>Meyer</surname> - <contrib>Contributed by </contrib> - <!-- mwm@mired.org --> - </author> + <author><personname><firstname>Mike</firstname><surname>Meyer</surname></personname><contrib>Contributed by </contrib></author> </authorgroup> - <!-- Apr 2001 --> - </sect1info> + + </info> - <title>Creating and Using CD Media</title> + <indexterm> <primary>CD-ROMs</primary> @@ -476,11 +460,10 @@ umass0: detached</screen> that do not support those extensions.</para> <indexterm> - <primary><filename - role="package">sysutils/cdrtools</filename></primary> + <primary><package>sysutils/cdrtools</package></primary> </indexterm> - <para>The <filename role="package">sysutils/cdrtools</filename> + <para>The <package>sysutils/cdrtools</package> port includes &man.mkisofs.8;, a program that can be used to produce a data file containing an ISO 9660 file system. It has options that support various extensions, and is described @@ -493,37 +476,34 @@ 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><link linkend="burncd">burncd</link></command> + <command>burncd</command> which is part of the base system. SCSI and USB CD burners - should use <command><link - linkend="cdrecord">cdrecord</link></command> from the - <filename role="package">sysutils/cdrtools</filename> port. - It is also possible to use <command><link - linkend="cdrecord">cdrecord</link></command> and other tools - for SCSI drives on ATAPI hardware with the <link - linkend="atapicam">ATAPI/CAM module</link>.</para> + 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 - <filename role="package">sysutils/xcdroast</filename> and - <filename role="package">sysutils/k3b</filename> ports. + <package>sysutils/xcdroast</package> and + <package>sysutils/k3b</package> ports. <application>X-CD-Roast</application> and <application>K3b</application> require the <link linkend="atapicam">ATAPI/CAM module</link> with ATAPI hardware.</para> </sect2> - <sect2 id="mkisofs"> + <sect2 xml:id="mkisofs"> <title><application>mkisofs</application></title> - <para>The <filename role="package">sysutils/cdrtools</filename> + <para>The <package>sysutils/cdrtools</package> port also installs &man.mkisofs.8;, which produces an ISO 9660 file system that is an image of a directory tree in the &unix; file system name space. The simplest usage is:</para> - <screen>&prompt.root; <userinput>mkisofs -o <replaceable>imagefile.iso</replaceable> <replaceable>/path/to/tree</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>mkisofs -o imagefile.iso /path/to/tree</userinput></screen> <indexterm> <primary>file systems</primary> @@ -575,24 +555,21 @@ umass0: detached</screen> 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 class="directory">/tmp/myboot</filename> holds a - bootable &os; system with the boot image in <filename - class="directory">/tmp/myboot/boot/cdboot</filename>, this + <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> - <para>If <devicename>md</devicename> is configured in the + <para>If <filename>md</filename> is configured in the kernel, the file system can be mounted as a memory disk with:</para> <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 - class="directory">/mnt</filename> and <filename - class="directory">/tmp/myboot</filename> are + <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 @@ -600,7 +577,7 @@ umass0: detached</screen> &man.mkisofs.8; for details.</para> </sect2> - <sect2 id="burncd"> + <sect2 xml:id="burncd"> <title><application>burncd</application></title> <indexterm> @@ -613,7 +590,7 @@ umass0: detached</screen> installed as <filename>/usr/sbin/burncd</filename>. Usage is very simple, as it has few options:</para> - <screen>&prompt.root; <userinput>burncd -f <replaceable>cddevice</replaceable> data <replaceable>imagefile.iso</replaceable> fixate</userinput></screen> + <screen>&prompt.root; <userinput>burncd -f cddevice data imagefile.iso fixate</userinput></screen> <para>This command will burn a copy of <replaceable>imagefile.iso</replaceable> on @@ -623,14 +600,13 @@ umass0: detached</screen> and write audio data.</para> </sect2> - <sect2 id="cdrecord"> + <sect2 xml:id="cdrecord"> <title><application>cdrecord</application></title> <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 <filename - role="package">sysutils/cdrtools</filename> package or port. + 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 @@ -642,7 +618,7 @@ umass0: detached</screen> usage is simple. Burning an ISO 9660 image is done with:</para> - <screen>&prompt.root; <userinput>cdrecord dev=<replaceable>device</replaceable> <replaceable>imagefile.iso</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>cdrecord dev=device imagefile.iso</userinput></screen> <para>The tricky part of using <command>cdrecord</command> is finding the <option>dev</option> to use. To find the proper @@ -685,7 +661,7 @@ scsibus1: controlling the write speed.</para> </sect2> - <sect2 id="duplicating-audiocds"> + <sect2 xml:id="duplicating-audiocds"> <title>Duplicating Audio CDs</title> <para>To duplicate an audio CD, extract the audio data from the @@ -707,11 +683,10 @@ scsibus1: <para>Use <command>cdrecord</command> to write the <filename>.wav</filename> files:</para> - <screen>&prompt.user; <userinput>cdrecord -v dev=<replaceable>2,0</replaceable> -dao -useinfo *.wav</userinput></screen> + <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> @@ -729,7 +704,7 @@ scsibus1: <step> <para>The ATAPI CD driver makes each track available as - <filename>/dev/acd<replaceable>d</replaceable>t<replaceable>nn</replaceable></filename>, + <filename>/dev/acddtnn</filename>, where <replaceable>d</replaceable> is the drive number, and <replaceable>nn</replaceable> is the track number written with two decimal digits, prefixed with zero as @@ -760,19 +735,19 @@ scsibus1: files, and that <command>burncd</command> should fixate the disk when finished:</para> - <screen>&prompt.root; <userinput>burncd -f <replaceable>/dev/acd0</replaceable> audio track1.cdr track2.cdr <replaceable>...</replaceable> fixate</userinput></screen> + <screen>&prompt.root; <userinput>burncd -f /dev/acd0 audio track1.cdr track2.cdr ... fixate</userinput></screen> </step> </procedure> </sect2> - <sect2 id="imaging-cd"> + <sect2 xml:id="imaging-cd"> <title>Duplicating Data CDs</title> <para>It is possible to copy a data CD to an image file that is functionally equivalent to the image file created with &man.mkisofs.8;, and then use it to duplicate any data CD. The example given here assumes that the CD-ROM device is - <devicename>acd0</devicename>. Substitute the correct CD-ROM + <filename>acd0</filename>. Substitute the correct CD-ROM device.</para> <screen>&prompt.root; <userinput>dd if=/dev/acd0 of=file.iso bs=2048</userinput></screen> @@ -781,7 +756,7 @@ scsibus1: described above.</para> </sect2> - <sect2 id="mounting-cd"> + <sect2 xml:id="mounting-cd"> <title>Using Data CDs</title> <para>It is possible to mount and read the data on a standard @@ -799,7 +774,7 @@ scsibus1: <literal>ISO9660</literal> by specifying <option>-t cd9660</option> to &man.mount.8;. For example, to mount the CD-ROM device, <filename>/dev/cd0</filename>, - under <filename class="directory">/mnt</filename>, + under <filename>/mnt</filename>, use:</para> <screen>&prompt.root; <userinput>mount -t cd9660 /dev/cd0 /mnt</userinput></screen> @@ -843,8 +818,7 @@ scsibus1: <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 + the following option to the kernel configuration and <link linkend="kernelconfig-building">rebuild the kernel</link>.</para> <programlisting>options SCSI_DELAY=15000</programlisting> @@ -854,7 +828,7 @@ scsibus1: bus reset.</para> </sect2> - <sect2 id="rawdata-cd"> + <sect2 xml:id="rawdata-cd"> <title>Burning Raw Data CDs</title> <para>It is possible to burn a file directly to CD, without @@ -876,18 +850,14 @@ scsibus1: described above.</para> </sect2> - <sect2 id="atapicam"> - <sect2info> + <sect2 xml:id="atapicam"> + <info><title>Using the ATAPI/CAM Driver</title> <authorgroup> - <author> - <firstname>Marc</firstname> - <surname>Fonvieille</surname> - <contrib>Contributed by </contrib> - </author> + <author><personname><firstname>Marc</firstname><surname>Fonvieille</surname></personname><contrib>Contributed by </contrib></author> </authorgroup> - </sect2info> + </info> - <title>Using the ATAPI/CAM Driver</title> + <indexterm> <primary>CD burner</primary> @@ -896,8 +866,7 @@ scsibus1: <para>This driver allows ATAPI devices, such as CD/DVD drives, to be accessed through the SCSI subsystem, and so allows the - use of applications like <filename - role="package">sysutils/cdrdao</filename> or + use of applications like <package>sysutils/cdrdao</package> or &man.cdrecord.1;.</para> <para>To use this driver, add the following line to @@ -937,12 +906,12 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <para>The drive can now be accessed via the <filename>/dev/cd0</filename> device name. For example, to - mount a CD-ROM on <filename class="directory">/mnt</filename>, + mount a CD-ROM on <filename>/mnt</filename>, type the following:</para> - <screen>&prompt.root; <userinput>mount -t cd9660 <replaceable>/dev/cd0</replaceable> /mnt</userinput></screen> + <screen>&prompt.root; <userinput>mount -t cd9660 /dev/cd0 /mnt</userinput></screen> - <para>As <username>root</username>, run the following command + <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> @@ -957,26 +926,18 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c </sect2> </sect1> - <sect1 id="creating-dvds"> - <sect1info> + <sect1 xml:id="creating-dvds"> + <info><title>Creating and Using DVD Media</title> <authorgroup> - <author> - <firstname>Marc</firstname> - <surname>Fonvieille</surname> - <contrib>Contributed by </contrib> - </author> + <author><personname><firstname>Marc</firstname><surname>Fonvieille</surname></personname><contrib>Contributed by </contrib></author> </authorgroup> <authorgroup> - <author> - <firstname>Andy</firstname> - <surname>Polyakov</surname> - <contrib>With inputs from </contrib> - </author> + <author><personname><firstname>Andy</firstname><surname>Polyakov</surname></personname><contrib>With inputs from </contrib></author> </authorgroup> - <!-- Feb 2004 --> - </sect1info> + + </info> - <title>Creating and Using DVD Media</title> + <indexterm> <primary>DVD</primary> @@ -997,8 +958,8 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <listitem> <para>DVD-R: This was the first DVD recordable format available. The DVD-R standard is defined by the - <ulink url="http://www.dvdforum.com/forum.shtml">DVD - Forum</ulink>. This format is write once.</para> + <link xlink:href="http://www.dvdforum.com/forum.shtml">DVD + Forum</link>. This format is write once.</para> </listitem> <listitem> @@ -1018,8 +979,8 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <listitem> <para>DVD+RW: This is a rewritable format defined by - the <ulink url="http://www.dvdrw.com/">DVD+RW - Alliance</ulink>. A DVD+RW can be rewritten about 1000 + the <link xlink:href="http://www.dvdrw.com/">DVD+RW + Alliance</link>. A DVD+RW can be rewritten about 1000 times.</para> </listitem> @@ -1048,8 +1009,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <title>Configuration</title> <para>To perform DVD recording, use &man.growisofs.1;. This - command is part of the <filename - role="package">sysutils/dvd+rw-tools</filename> utilities + 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, @@ -1067,13 +1027,11 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <para>Before attempting to use <application>dvd+rw-tools</application>, consult the - <ulink - url="http://fy.chalmers.se/~appro/linux/DVD+RW/hcn.html">Hardware - Compatibility Notes</ulink>.</para> + <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 <filename - role="package">sysutils/k3b</filename> which provides a + <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> @@ -1082,17 +1040,16 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <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> <para>To burn to a DVD+R or a DVD-R the data in - <filename class="directory">/path/to/data</filename>, + <filename>/path/to/data</filename>, use the following command:</para> - <screen>&prompt.root; <userinput>growisofs -dvd-compat -Z <replaceable>/dev/cd0</replaceable> -J -R <replaceable>/path/to/data</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>growisofs -dvd-compat -Z /dev/cd0 -J -R /path/to/data</userinput></screen> <para>In this example, <option>-J -R</option> is passed to &man.mkisofs.8; to create an ISO 9660 file system with Joliet @@ -1110,7 +1067,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <para>To burn a pre-mastered image, such as <replaceable>imagefile.iso</replaceable>, use:</para> - <screen>&prompt.root; <userinput>growisofs -dvd-compat -Z <replaceable>/dev/cd0</replaceable>=<replaceable>imagefile.iso</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>growisofs -dvd-compat -Z /dev/cd0=imagefile.iso</userinput></screen> <para>The write speed should be detected and automatically set according to the media and the drive being used. To force the @@ -1131,22 +1088,20 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <para>To create this type of ISO file:</para> - <screen>&prompt.user; <userinput>mkisofs -R -J -udf -iso-level 3 -o <replaceable>imagefile.iso</replaceable> <replaceable>/path/to/data</replaceable></userinput></screen> + <screen>&prompt.user; <userinput>mkisofs -R -J -udf -iso-level 3 -o imagefile.iso /path/to/data</userinput></screen> <para>To burn files directly to a disk:</para> - <screen>&prompt.root; <userinput>growisofs -dvd-compat -udf -iso-level 3 -Z <replaceable>/dev/cd0</replaceable> -J -R <replaceable>/path/to/data</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>growisofs -dvd-compat -udf -iso-level 3 -Z /dev/cd0 -J -R /path/to/data</userinput></screen> <para>When an ISO image already contains large files, no 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 <filename - role="package">sysutils/cdrtools</filename>, which + <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 <filename - role="package">sysutils/cdrtools-devel</filename> and read + not work, install <package>sysutils/cdrtools-devel</package> and read its &man.mkisofs.8;.</para> </note> </sect2> @@ -1162,18 +1117,16 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <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 <filename - role="package">multimedia/dvdauthor</filename> is needed to + 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 - class="directory">/path/to/video</filename>, the following + 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 <replaceable>/dev/cd0</replaceable> -dvd-video <replaceable>/path/to/video</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>growisofs -Z /dev/cd0 -dvd-video /path/to/video</userinput></screen> <para><option>-dvd-video</option> is passed to &man.mkisofs.8; to instruct it to create a DVD-Video file system layout. @@ -1195,7 +1148,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c appropriate. However, it is possible to use <command>dvd+rw-format</command> to format the DVD+RW:</para> - <screen>&prompt.root; <userinput>dvd+rw-format <replaceable>/dev/cd0</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>dvd+rw-format /dev/cd0</userinput></screen> <para>Only perform this operation once and keep in mind that only virgin DVD+RW medias need to be formatted. Once @@ -1206,7 +1159,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c first. Instead, write over the previous recording like this:</para> - <screen>&prompt.root; <userinput>growisofs -Z <replaceable>/dev/cd0</replaceable> -J -R <replaceable>/path/to/newdata</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>growisofs -Z /dev/cd0 -J -R /path/to/newdata</userinput></screen> <para>The DVD+RW format supports appending data to a previous recording. This operation consists of merging a new session @@ -1218,7 +1171,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <para>For example, to append data to a DVD+RW, use the following:</para> - <screen>&prompt.root; <userinput>growisofs -M <replaceable>/dev/cd0</replaceable> -J -R <replaceable>/path/to/nextdata</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>growisofs -M /dev/cd0 -J -R /path/to/nextdata</userinput></screen> <para>The same &man.mkisofs.8; options used to burn the initial session should be used during next writes.</para> @@ -1231,7 +1184,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <para>To blank the media, use:</para> - <screen>&prompt.root; <userinput>growisofs -Z <replaceable>/dev/cd0</replaceable>=<replaceable>/dev/zero</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>growisofs -Z /dev/cd0=/dev/zero</userinput></screen> </sect2> <sect2> @@ -1253,7 +1206,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <para>To blank a DVD-RW in sequential mode:</para> - <screen>&prompt.root; <userinput>dvd+rw-format -blank=full <replaceable>/dev/cd0</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>dvd+rw-format -blank=full /dev/cd0</userinput></screen> <note> <para>A full blanking using <option>-blank=full</option> will @@ -1262,7 +1215,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c be recorded in Disk-At-Once (DAO) mode. To burn the DVD-RW in DAO mode, use the command:</para> - <screen>&prompt.root; <userinput>growisofs -use-the-force-luke=dao -Z <replaceable>/dev/cd0</replaceable>=<replaceable>imagefile.iso</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>growisofs -use-the-force-luke=dao -Z /dev/cd0=imagefile.iso</userinput></screen> <para>Since &man.growisofs.1; automatically attempts to detect fast blanked media and engage DAO write, @@ -1277,7 +1230,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <para>To write data on a sequential DVD-RW, use the same instructions as for the other DVD formats:</para> - <screen>&prompt.root; <userinput>growisofs -Z <replaceable>/dev/cd0</replaceable> -J -R <replaceable>/path/to/data</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>growisofs -Z /dev/cd0 -J -R /path/to/data</userinput></screen> <para>To append some data to a previous recording, use <option>-M</option> with &man.growisofs.1;. However, if data @@ -1295,11 +1248,11 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <para>To put a DVD-RW in restricted overwrite format, the following command must be used:</para> - <screen>&prompt.root; <userinput>dvd+rw-format <replaceable>/dev/cd0</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>dvd+rw-format /dev/cd0</userinput></screen> <para>To change back to sequential format, use:</para> - <screen>&prompt.root; <userinput>dvd+rw-format -blank=full <replaceable>/dev/cd0</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>dvd+rw-format -blank=full /dev/cd0</userinput></screen> </sect2> <sect2> @@ -1315,7 +1268,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c session on a DVD+R, DVD-R, or DVD-RW in sequential format, will add a new session to the disc:</para> - <screen>&prompt.root; <userinput>growisofs -M <replaceable>/dev/cd0</replaceable> -J -R <replaceable>/path/to/nextdata</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>growisofs -M /dev/cd0 -J -R /path/to/nextdata</userinput></screen> <para>Using this command with a DVD+RW or a DVD-RW in restricted overwrite mode will append data while merging the new session @@ -1338,16 +1291,14 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <para>To obtain more information about a DVD, use <command>dvd+rw-mediainfo - <replaceable>/dev/cd0</replaceable></command> while the disc + /dev/cd0</command> while the disc in the specified drive.</para> <para>More information about <application>dvd+rw-tools</application> can be found in - &man.growisofs.1;, on the <ulink - url="http://fy.chalmers.se/~appro/linux/DVD+RW/">dvd+rw-tools - web site</ulink>, and in the <ulink - url="http://lists.debian.org/cdwrite/">cdwrite mailing - list</ulink> 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 @@ -1356,7 +1307,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c </note> </sect2> - <sect2 id="creating-dvd-ram"> + <sect2 xml:id="creating-dvd-ram"> <title>Using a DVD-RAM</title> <indexterm> @@ -1383,11 +1334,11 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c it can be used. In this example, the whole disk space will be formatted with a standard UFS2 file system:</para> - <screen>&prompt.root; <userinput>dd if=/dev/zero of=<replaceable>/dev/acd0</replaceable> bs=2k count=1</userinput> -&prompt.root; <userinput>bsdlabel -Bw <replaceable>acd0</replaceable></userinput> -&prompt.root; <userinput>newfs <replaceable>/dev/acd0</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/acd0 bs=2k count=1</userinput> +&prompt.root; <userinput>bsdlabel -Bw acd0</userinput> +&prompt.root; <userinput>newfs /dev/acd0</userinput></screen> - <para>The DVD device, <devicename>acd0</devicename>, must be + <para>The DVD device, <filename>acd0</filename>, must be changed according to the configuration.</para> </sect3> @@ -1397,7 +1348,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <para>Once the DVD-RAM has been formatted, it can be mounted as a normal hard drive:</para> - <screen>&prompt.root; <userinput>mount <replaceable>/dev/acd0</replaceable> <replaceable>/mnt</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>mount /dev/acd0 /mnt</userinput></screen> <para>Once mounted, the DVD-RAM will be both readable and writeable.</para> @@ -1405,27 +1356,19 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c </sect2> </sect1> - <sect1 id="floppies"> - <sect1info> + <sect1 xml:id="floppies"> + <info><title>Creating and Using Floppy Disks</title> <authorgroup> - <author> - <firstname>Julio</firstname> - <surname>Merino</surname> - <contrib>Original work by </contrib> - </author> + <author><personname><firstname>Julio</firstname><surname>Merino</surname></personname><contrib>Original work by </contrib></author> </authorgroup> - <!-- 24 Dec 2001 --> + <authorgroup> - <author> - <firstname>Martin</firstname> - <surname>Karlsson</surname> - <contrib>Rewritten by </contrib> - </author> + <author><personname><firstname>Martin</firstname><surname>Karlsson</surname></personname><contrib>Rewritten by </contrib></author> </authorgroup> - <!-- 27 Apr 2003 --> - </sect1info> + + </info> - <title>Creating and Using Floppy Disks</title> + <para>Storing data on floppy disks is sometimes useful, for example when one does not have any other removable storage media @@ -1443,9 +1386,9 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <title>The Device</title> <para>Floppy disks are accessed through entries in - <filename class="directory">/dev</filename>, just like other + <filename>/dev</filename>, just like other devices. To access the raw floppy disk, simply use - <filename>/dev/fd<replaceable>N</replaceable></filename>.</para> + <filename>/dev/fdN</filename>.</para> </sect3> <sect3> @@ -1517,12 +1460,12 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <para>To use the floppy, mount it with &man.mount.msdosfs.8;. One can also use - <filename role="package">emulators/mtools</filename> from the + <package>emulators/mtools</package> from the Ports Collection.</para> </sect2> </sect1> - <sect1 id="backups-tapebackups"> + <sect1 xml:id="backups-tapebackups"> <title>Creating and Using Data Tapes</title> <indexterm><primary>tape media</primary></indexterm> @@ -1534,7 +1477,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c uses SCSI, such as LTO and older devices such as DAT. There is limited support for SATA and USB tape drives.</para> - <sect2 id="tapes-sa0"> + <sect2 xml:id="tapes-sa0"> <title>Serial Access with &man.sa.4;</title> <indexterm> @@ -1542,20 +1485,20 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c </indexterm> <para>&os; uses the &man.sa.4; driver, providing - <devicename>/dev/sa0</devicename>, - <devicename>/dev/nsa0</devicename>, and - <devicename>/dev/esa0</devicename>. In normal use, only - <devicename>/dev/sa0</devicename> is needed. - <devicename>/dev/nsa0</devicename> is the same physical drive - as <devicename>/dev/sa0</devicename> but does not rewind the + <filename>/dev/sa0</filename>, + <filename>/dev/nsa0</filename>, and + <filename>/dev/esa0</filename>. In normal use, only + <filename>/dev/sa0</filename> is needed. + <filename>/dev/nsa0</filename> is the same physical drive + as <filename>/dev/sa0</filename> but does not rewind the tape after writing a file. This allows writing more than one - file to a tape. Using <devicename>/dev/esa0</devicename> + file to a tape. Using <filename>/dev/esa0</filename> ejects the tape after the device is closed, if applicable.</para> </sect2> <sect2> - <title id="tapes-mt">Controlling the Tape Drive with + <title xml:id="tapes-mt">Controlling the Tape Drive with &man.mt.1;</title> <indexterm> @@ -1575,13 +1518,13 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c </sect2> <sect2> - <title id="tapes-tar">Using &man.tar.1; to Read and + <title xml:id="tapes-tar">Using &man.tar.1; to Read and Write Tape Backups</title> <para>An example of writing a single file to tape using &man.tar.1;:</para> - <screen>&prompt.root; <userinput>tar cvf /dev/sa0 <replaceable>file</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>tar cvf /dev/sa0 file</userinput></screen> <para>Recovering files from a &man.tar.1; archive on tape into the current directory:</para> @@ -1590,11 +1533,10 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c </sect2> <sect2> - <title id="tapes-dumprestore">Using &man.dump.8; and + <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 - class="directory">/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> @@ -1605,7 +1547,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c </sect2> <sect2> - <title id="tapes-othersofware">Other Tape Software</title> + <title xml:id="tapes-othersofware">Other Tape Software</title> <para>Higher-level programs are available to simplify tape backup. The most popular are @@ -1617,19 +1559,15 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c </sect2> </sect1> - <sect1 id="backup-strategies"> - <sect1info> + <sect1 xml:id="backup-strategies"> + <info><title>Backup Strategies</title> <authorgroup> - <author> - <firstname>Lowell</firstname> - <surname>Gilbert</surname> - <contrib>Original work by </contrib> - </author> + <author><personname><firstname>Lowell</firstname><surname>Gilbert</surname></personname><contrib>Original work by </contrib></author> </authorgroup> - <!-- 3 Dec 2005 --> - </sect1info> + + </info> - <title>Backup Strategies</title> + <para>The first requirement in devising a backup plan is to make sure that all of the following problems are covered:</para> @@ -1679,8 +1617,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <listitem> <para>Copies of whole file systems or disks which can be - created with a periodic <filename - role="package">net/rsync</filename> of the whole machine. + 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 @@ -1713,7 +1650,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c against, and how each will be handled.</para> </sect1> - <sect1 id="backup-basics"> + <sect1 xml:id="backup-basics"> <title>Backup Basics</title> <para>The major backup programs built into &os; are @@ -1746,17 +1683,15 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c 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 class="directory">/tmp/</filename> by - default. When using a recovery disk with a small <filename - class="directory">/tmp</filename>, set + 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> <note> <para>If <command>dump</command> is used on the root - directory, it will not back up <filename - class="directory">/home</filename>, - <filename class="directory">/usr</filename> or many other + directory, it will not back up <filename>/home</filename>, + <filename>/usr</filename> or many other directories since these are typically mount points for other file systems or symbolic links into those file systems.</para> @@ -1783,9 +1718,9 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c be suitable to use on the remote computer. For example, to <command>rdump</command> from a &os; computer to an Exabyte tape drive connected to a host called - <hostid>komodo</hostid>, use:</para> + <systemitem>komodo</systemitem>, use:</para> - <screen>&prompt.root; <userinput>/sbin/rdump 0dsbfu 54000 13000 126 komodo:/dev/nsa8 /dev/da0a 2>&1</userinput></screen> + <screen>&prompt.root; <userinput>/sbin/rdump 0dsbfu 54000 13000 126 komodo:/dev/nsa8 /dev/da0a 2>&1</userinput></screen> <para>There are security implications to allowing <filename>.rhosts</filename> authentication, so use @@ -1833,9 +1768,9 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <indexterm><primary><command>tar</command></primary></indexterm> <para>To <command>tar</command> to an Exabyte tape drive - connected to a host called <hostid>komodo</hostid>:</para> + connected to a host called <systemitem>komodo</systemitem>:</para> - <screen>&prompt.root; <userinput>tar cf - . | rsh komodo dd of=<replaceable>tape-device</replaceable> obs=20b</userinput></screen> + <screen>&prompt.root; <userinput>tar cf - . | rsh komodo dd of=tape-device obs=20b</userinput></screen> <para>When backing up over an insecure network, instead use <command>ssh</command>.</para> @@ -1866,10 +1801,10 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c across the network, use a pipeline and <command>ssh</command> to send the data to a remote tape drive.</para> - <screen>&prompt.root; <userinput>for f in <replaceable>directory_list; do</replaceable></userinput> + <screen>&prompt.root; <userinput>for f in directory_list; do</userinput> <userinput>find $f >> backup.list</userinput> <userinput>done</userinput> -&prompt.root; <userinput>cpio -v -o --format=newc < backup.list | ssh <replaceable>user</replaceable>@<replaceable>host</replaceable> "cat > <replaceable>backup_device</replaceable>"</userinput></screen> +&prompt.root; <userinput>cpio -v -o --format=newc < backup.list | ssh user@host "cat > backup_device"</userinput></screen> <para>Where <replaceable>directory_list</replaceable> is the list of directories to back up, @@ -1903,7 +1838,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <command>cpio</command> than <command>tar</command>.</para> </sect2> - <sect2 id="backups-programs-amanda"> + <sect2 xml:id="backups-programs-amanda"> <title><application>Amanda</application></title> <indexterm> @@ -1961,7 +1896,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c files.</para> <para><quote>Do nothing</quote> is the correct backup method for - <filename class="directory">/usr/obj</filename> and other + <filename>/usr/obj</filename> and other directory trees that can be exactly recreated by the computer. An example is the files that comprise the HTML or &postscript; version of this Handbook. These document formats have been @@ -1990,9 +1925,8 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c 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 - <ulink - url="http://www.coredumps.de/doc/dump/zwicky/testdump.doc.html">torture-testing - Backup and Archive Programs</ulink>.</para> + <link xlink:href="http://www.coredumps.de/doc/dump/zwicky/testdump.doc.html">torture-testing + Backup and Archive Programs</link>.</para> </sect2> <sect2> @@ -2020,8 +1954,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c &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 <ulink - url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-livefs.iso"></ulink>.</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 @@ -2030,8 +1963,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c images may be used to recover a system. The <quote>memstick</quote> image for &os;/&arch.i386; &rel.current;-RELEASE is available - from <ulink - url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/&arch.i386;/ISO-IMAGES/&rel.current;/&os;-&rel.current;-RELEASE-&arch.i386;-memstick.img"></ulink>.</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 @@ -2072,8 +2004,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <guimenuitem>CD-ROM/DVD -- Use the live filesystem CD-ROM/DVD</guimenuitem>. <command>restore</command> and the other needed programs - are located in <filename - class="directory">/mnt2/rescue</filename>.</para> + are located in <filename>/mnt2/rescue</filename>.</para> <para>Recover each file system separately.</para> @@ -2108,17 +2039,13 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c </sect2> </sect1> - <sect1 id="disks-virtual"> - <sect1info> + <sect1 xml:id="disks-virtual"> + <info><title>Network, Memory, and File-Backed File Systems</title> <authorgroup> - <author> - <firstname>Marc</firstname> - <surname>Fonvieille</surname> - <contrib>Reorganized and enhanced by </contrib> - </author> + <author><personname><firstname>Marc</firstname><surname>Fonvieille</surname></personname><contrib>Reorganized and enhanced by </contrib></author> </authorgroup> - </sect1info> - <title>Network, Memory, and File-Backed File Systems</title> + </info> + <indexterm><primary>virtual disks</primary></indexterm> <indexterm> @@ -2149,7 +2076,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c for the user.</para> </note> - <sect2 id="disks-mdconfig"> + <sect2 xml:id="disks-mdconfig"> <title>File-Backed File System</title> <indexterm> @@ -2175,8 +2102,8 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <title>Using <command>mdconfig</command> to Mount an Existing File System Image</title> - <screen>&prompt.root; <userinput>mdconfig -a -t vnode -f <replaceable>diskimage</replaceable> -u <replaceable>0</replaceable></userinput> -&prompt.root; <userinput>mount /dev/md<replaceable>0</replaceable> <replaceable>/mnt</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>mdconfig -a -t vnode -f diskimage -u 0</userinput> +&prompt.root; <userinput>mount /dev/md0 /mnt</userinput></screen> </example> <para>To create a new file system image with @@ -2186,18 +2113,18 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <title>Creating a New File-Backed Disk with <command>mdconfig</command></title> - <screen>&prompt.root; <userinput>dd if=/dev/zero of=<replaceable>newimage</replaceable> bs=1k count=<replaceable>5</replaceable>k</userinput> + <screen>&prompt.root; <userinput>dd if=/dev/zero of=newimage bs=1k count=5k</userinput> 5120+0 records in 5120+0 records out -&prompt.root; <userinput>mdconfig -a -t vnode -f <replaceable>newimage</replaceable> -u <replaceable>0</replaceable></userinput> -&prompt.root; <userinput>bsdlabel -w md<replaceable>0</replaceable> auto</userinput> -&prompt.root; <userinput>newfs md<replaceable>0</replaceable>a</userinput> +&prompt.root; <userinput>mdconfig -a -t vnode -f newimage -u 0</userinput> +&prompt.root; <userinput>bsdlabel -w md0 auto</userinput> +&prompt.root; <userinput>newfs md0a</userinput> /dev/md0a: 5.0MB (10224 sectors) block size 16384, fragment size 2048 using 4 cylinder groups of 1.25MB, 80 blks, 192 inodes. super-block backups (for fsck -b #) at: 160, 2720, 5280, 7840 -&prompt.root; <userinput>mount /dev/md<replaceable>0</replaceable>a <replaceable>/mnt</replaceable></userinput> -&prompt.root; <userinput>df <replaceable>/mnt</replaceable></userinput> +&prompt.root; <userinput>mount /dev/md0a /mnt</userinput> +&prompt.root; <userinput>df /mnt</userinput> Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/md0a 4710 4 4330 0% /mnt</screen> </example> @@ -2206,7 +2133,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on <option>-u</option>, &man.mdconfig.8; uses the &man.md.4; automatic allocation to select an unused device. The name of the allocated unit will be output to stdout, such - as <devicename>md4</devicename>. Refer to &man.mdconfig.8; + as <filename>md4</filename>. Refer to &man.mdconfig.8; for more details about.</para> <para>While &man.mdconfig.8; is useful, it takes several @@ -2221,11 +2148,11 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on <title>Configure and Mount a File-Backed Disk with <command>mdmfs</command></title> - <screen>&prompt.root; <userinput>dd if=/dev/zero of=<replaceable>newimage</replaceable> bs=1k count=<replaceable>5</replaceable>k</userinput> + <screen>&prompt.root; <userinput>dd if=/dev/zero of=newimage bs=1k count=5k</userinput> 5120+0 records in 5120+0 records out -&prompt.root; <userinput>mdmfs -F <replaceable>newimage</replaceable> -s <replaceable>5</replaceable>m md<replaceable>0</replaceable> <replaceable>/mnt</replaceable></userinput> -&prompt.root; <userinput>df <replaceable>/mnt</replaceable></userinput> +&prompt.root; <userinput>mdmfs -F newimage -s 5m md0 /mnt</userinput> +&prompt.root; <userinput>df /mnt</userinput> Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/md0 4718 4 4338 0% /mnt</screen> </example> @@ -2236,7 +2163,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on about &man.mdmfs.8;, refer to its manual page.</para> </sect2> - <sect2 id="disks-md-freebsd5"> + <sect2 xml:id="disks-md-freebsd5"> <title>Memory-Based File System</title> <indexterm> @@ -2258,15 +2185,15 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on <title>Creating a New Memory-Based Disk with <command>mdconfig</command></title> - <screen>&prompt.root; <userinput>mdconfig -a -t swap -s <replaceable>5</replaceable>m -u <replaceable>1</replaceable></userinput> -&prompt.root; <userinput>newfs -U md<replaceable>1</replaceable></userinput> + <screen>&prompt.root; <userinput>mdconfig -a -t swap -s 5m -u 1</userinput> +&prompt.root; <userinput>newfs -U md1</userinput> /dev/md1: 5.0MB (10240 sectors) block size 16384, fragment size 2048 using 4 cylinder groups of 1.27MB, 81 blks, 192 inodes. with soft updates super-block backups (for fsck -b #) at: 160, 2752, 5344, 7936 -&prompt.root; <userinput>mount /dev/md<replaceable>1</replaceable> <replaceable>/mnt</replaceable></userinput> -&prompt.root; <userinput>df <replaceable>/mnt</replaceable></userinput> +&prompt.root; <userinput>mount /dev/md1 /mnt</userinput> +&prompt.root; <userinput>df /mnt</userinput> Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/md1 4718 4 4338 0% /mnt</screen> </example> @@ -2275,8 +2202,8 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on <title>Creating a New Memory-Based Disk with <command>mdmfs</command></title> - <screen>&prompt.root; <userinput>mdmfs -s <replaceable>5</replaceable>m md<replaceable>2</replaceable> <replaceable>/mnt</replaceable></userinput> -&prompt.root; <userinput>df <replaceable>/mnt</replaceable></userinput> + <screen>&prompt.root; <userinput>mdmfs -s 5m md2 /mnt</userinput> +&prompt.root; <userinput>df /mnt</userinput> Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/md2 4846 2 4458 0% /mnt</screen> </example> @@ -2299,7 +2226,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on <para>For example, to detach and free all resources used by <filename>/dev/md4</filename>:</para> - <screen>&prompt.root; <userinput>mdconfig -d -u <replaceable>4</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>mdconfig -d -u 4</userinput></screen> <para>It is possible to list information about configured &man.md.4; devices by running @@ -2307,19 +2234,15 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on </sect2> </sect1> - <sect1 id="snapshots"> - <sect1info> + <sect1 xml:id="snapshots"> + <info><title>File System Snapshots</title> <authorgroup> - <author> - <firstname>Tom</firstname> - <surname>Rhodes</surname> - <contrib>Contributed by </contrib> - </author> + <author><personname><firstname>Tom</firstname><surname>Rhodes</surname></personname><contrib>Contributed by </contrib></author> </authorgroup> - <!-- 15 JUL 2002 --> - </sect1info> + + </info> - <title>File System Snapshots</title> + <indexterm> <primary>file systems</primary> @@ -2348,7 +2271,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on allows them to be removed.</para> <para>Snapshots are created using &man.mount.8;. To place a - snapshot of <filename class="directory">/var</filename> in the + snapshot of <filename>/var</filename> in the file <filename>/var/snapshot/snap</filename>, use the following command:</para> @@ -2360,7 +2283,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on <screen>&prompt.root; <userinput>mksnap_ffs /var /var/snapshot/snap</userinput></screen> <para>One can find snapshot files on a file system, such as - <filename class="directory">/var</filename>, using + <filename>/var</filename>, using &man.find.1;:</para> <screen>&prompt.root; <userinput>find /var -flags snapshot</userinput></screen> @@ -2400,9 +2323,8 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on </listitem> </itemizedlist> - <para>The frozen <filename class="directory">/var</filename> is - now available through <filename - class="directory">/mnt</filename>. Everything will initially + <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> @@ -2413,10 +2335,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on <para>For more information about <option>softupdates</option> and file system snapshots, including technical papers, visit Marshall Kirk McKusick's website at - <ulink url="http://www.mckusick.com/"></ulink>.</para> + <uri xlink:href="http://www.mckusick.com/">http://www.mckusick.com/</uri>.</para> </sect1> - <sect1 id="quotas"> + <sect1 xml:id="quotas"> <title>File System Quotas</title> <indexterm> @@ -2445,8 +2367,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on <para>The <filename>GENERIC</filename> kernel does not have this enabled by default, so a custom kernel must be - compiled in order to use disk quotas. Refer to <xref - linkend="kernelconfig"/> for more information on + compiled in order to use disk quotas. Refer to <xref linkend="kernelconfig"/> for more information on kernel configuration.</para> <para>Next, enable disk quotas in @@ -2588,7 +2509,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on &man.edquota.8;. First, assign the desired quota limit to a user, then run <command>edquota -p protouser startuid-enduid</command>. For example, if - <username>test</username> has the desired quota limits, the + <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> @@ -2625,8 +2546,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on <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 - class="directory">/usr</filename> and has 5 days of grace + 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> @@ -2634,7 +2554,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on space on will not show in the output of &man.quota.1;, even if the user has a quota limit assigned for that file system. Use <option>-v</option> to display those file systems, such as - <filename class="directory">/usr/var</filename> in the above + <filename>/usr/var</filename> in the above example.</para> </sect2> @@ -2660,22 +2580,17 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on </sect2> </sect1> - <sect1 id="disks-encrypting"> - <sect1info> + <sect1 xml:id="disks-encrypting"> + <info><title>Encrypting Disk Partitions</title> <authorgroup> - <author> - <firstname>Lucky</firstname> - <surname>Green</surname> - <contrib>Contributed by </contrib> - <affiliation> + <author><personname><firstname>Lucky</firstname><surname>Green</surname></personname><contrib>Contributed by </contrib><affiliation> <address><email>shamrock@cypherpunks.to</email></address> - </affiliation> - </author> + </affiliation></author> </authorgroup> - <!-- 11 MARCH 2003 --> - </sect1info> + + </info> - <title>Encrypting Disk Partitions</title> + <indexterm> <primary>disks</primary> @@ -2683,8 +2598,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on </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 @@ -2736,10 +2650,10 @@ Password:</screen> <para>The following example demonstrates adding a new hard drive to a system that will hold a single encrypted partition. This partition will be mounted as - <filename class="directory">/private</filename>. + <filename>/private</filename>. <application>gbde</application> can also be used to encrypt - <filename class="directory">/home</filename> and - <filename class="directory">/var/mail</filename>, but this + <filename>/home</filename> and + <filename>/var/mail</filename>, but this requires more complex instructions which exceed the scope of this introduction.</para> @@ -2750,8 +2664,8 @@ Password:</screen> <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 <devicename>/dev/ad4s1c</devicename> and - <devicename>/dev/ad0s1<replaceable>*</replaceable></devicename> + added as <filename>/dev/ad4s1c</filename> and + <filename>/dev/ad0s1*</filename> represents the existing standard &os; partitions.</para> <screen>&prompt.root; <userinput>ls /dev/ad*</userinput> @@ -2808,9 +2722,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 <ulink - url="http://world.std.com/~reinhold/diceware.html">Diceware - Passphrase</ulink> website.</para> + 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 the <application>gbde</application> partition. In this @@ -2845,8 +2758,8 @@ sector_size = 2048 that was selected during the initialization of the encrypted partition. The new encrypted device will appear in - <filename class="directory">/dev</filename> as - <devicename>/dev/device_name.bde</devicename>:</para> + <filename>/dev</filename> as + <filename>/dev/device_name.bde</filename>:</para> <screen>&prompt.root; <userinput>ls /dev/ad*</userinput> /dev/ad0 /dev/ad0s1b /dev/ad0s1e /dev/ad4s1 @@ -2869,7 +2782,7 @@ sector_size = 2048 <para>&man.newfs.8; must be performed on an attached <application>gbde</application> partition which is identified by a - <filename><replaceable>*</replaceable>.bde</filename> + <filename>*.bde</filename> extension to the device name.</para> </note> </step> @@ -2912,7 +2825,7 @@ Filesystem Size Used Avail Capacity Mounted on <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 <username>root</username>.</para> + must be executed as <systemitem class="username">root</systemitem>.</para> <procedure> <step> @@ -2991,7 +2904,7 @@ gbde_lockdir="/etc/gbde"</programlisting> <para>&man.sysinstall.8; is incompatible with <application>gbde</application>-encrypted devices. All - <devicename><replaceable>*</replaceable>.bde</devicename> + <filename>*.bde</filename> devices must be detached from the kernel before starting &man.sysinstall.8; or it will crash during its initial probing for devices. To detach the encrypted device used in @@ -3003,18 +2916,14 @@ gbde_lockdir="/etc/gbde"</programlisting> </sect2> <sect2> - <sect2info> + <info><title>Disk Encryption with <command>geli</command></title> <authorgroup> - <author> - <firstname>Daniel</firstname> - <surname>Gerzo</surname> - <contrib>Contributed by </contrib> - </author> + <author><personname><firstname>Daniel</firstname><surname>Gerzo</surname></personname><contrib>Contributed by </contrib></author> </authorgroup> - <!-- Date of writing: 28 November 2005 --> - </sect2info> + + </info> - <title>Disk Encryption with <command>geli</command></title> + <para>An alternative cryptographic GEOM class is available through &man.geli.8;. <command>geli</command> differs from @@ -3103,7 +3012,7 @@ device crypto</programlisting> <para>The following example describes how to generate a key file which will be used as part of the master key for the encrypted provider mounted under - <filename class="directory">/private</filename>. The key + <filename>/private</filename>. The key file will provide some random data used to encrypt the master key. The master key will also be protected by a passphrase. The provider's sector size will be 4kB. @@ -3117,8 +3026,8 @@ device crypto</programlisting> <para>The master key will be protected with a passphrase and the data source for the key file will be - <devicename>/dev/random</devicename>. The sector size of - the provider <devicename>/dev/da2.eli</devicename> will be + <filename>/dev/random</filename>. The sector size of + the provider <filename>/dev/da2.eli</filename> will be 4kB.</para> <screen>&prompt.root; <userinput>dd if=/dev/random of=/root/da2.key bs=64 count=1</userinput> @@ -3144,7 +3053,7 @@ Reenter new passphrase:</screen> Enter passphrase:</screen> <para>The new plaintext device will be named - <filename>/dev/<replaceable>da2</replaceable>.eli</filename>.</para> + <filename>/dev/da2.eli</filename>.</para> <screen>&prompt.root; <userinput>ls /dev/da2*</userinput> /dev/da2 /dev/da2.eli</screen> @@ -3174,7 +3083,7 @@ Filesystem Size Used Avail Capacity Mounted on <title>Unmounting and Detaching the Provider</title> <para>Once the work on the encrypted partition is done, and - the <filename class="directory">/private</filename> + the <filename>/private</filename> partition is no longer needed, it is prudent to consider unmounting and detaching the <command>geli</command> encrypted partition from the kernel:</para> @@ -3200,7 +3109,7 @@ Filesystem Size Used Avail Capacity Mounted on <programlisting>geli_devices="da2" geli_da2_flags="-p -k /root/da2.key"</programlisting> - <para>This configures <devicename>/dev/da2</devicename> as a + <para>This configures <filename>/dev/da2</filename> as a <command>geli</command> provider of which the master key file is located in <filename>/root/da2.key</filename>. <command>geli</command> will not use a passphrase when @@ -3218,18 +3127,14 @@ geli_da2_flags="-p -k /root/da2.key"</programlisting> </sect2> </sect1> - <sect1 id="swap-encrypting"> - <sect1info> + <sect1 xml:id="swap-encrypting"> + <info><title>Encrypting Swap Space</title> <authorgroup> - <author> - <firstname>Christian</firstname> - <surname>Brüffer</surname> - <contrib>Written by </contrib> - </author> + <author><personname><firstname>Christian</firstname><surname>Brüffer</surname></personname><contrib>Written by </contrib></author> </authorgroup> - </sect1info> + </info> - <title>Encrypting Swap Space</title> + <indexterm> <primary>swap</primary> @@ -3253,7 +3158,7 @@ geli_da2_flags="-p -k /root/da2.key"</programlisting> <note> <para>For the remainder of this section, - <devicename>ad0s1b</devicename> will be the swap + <filename>ad0s1b</filename> will be the swap partition.</para> </note> @@ -3262,7 +3167,7 @@ geli_da2_flags="-p -k /root/da2.key"</programlisting> overwrite the current swap parition with random garbage, execute the following command:</para> - <screen>&prompt.root; <userinput>dd if=/dev/random of=/dev/<replaceable>ad0s1b</replaceable> bs=1m</userinput></screen> + <screen>&prompt.root; <userinput>dd if=/dev/random of=/dev/ad0s1b bs=1m</userinput></screen> <sect2> <title>Swap Encryption with &man.gbde.8;</title> @@ -3324,38 +3229,21 @@ Device 1K-blocks Used Avail Capacity </sect2> </sect1> - <sect1 id="disks-hast"> - <sect1info> + <sect1 xml:id="disks-hast"> + <info><title>Highly Available Storage (HAST)</title> <authorgroup> - <author> - <firstname>Daniel</firstname> - <surname>Gerzo</surname> - <contrib>Contributed by </contrib> - </author> + <author><personname><firstname>Daniel</firstname><surname>Gerzo</surname></personname><contrib>Contributed by </contrib></author> </authorgroup> <authorgroup> - <author> - <firstname>Freddie</firstname> - <surname>Cash</surname> - <contrib>With inputs from </contrib> - </author> - <author> - <firstname>Pawel Jakub</firstname> - <surname>Dawidek</surname> - </author> - <author> - <firstname>Michael W.</firstname> - <surname>Lucas</surname> - </author> - <author> - <firstname>Viktor</firstname> - <surname>Petersson</surname> - </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> - <!-- Date of writing: 26 February 2011 --> - </sect1info> + + </info> - <title>Highly Available Storage (HAST)</title> + <indexterm> <primary>HAST</primary> @@ -3404,28 +3292,24 @@ Device 1K-blocks Used Avail Capacity <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> <para>The <acronym>HAST</acronym> project was sponsored by The - &os; Foundation with support from <ulink - url="http://www.omc.net/">OMCnet Internet Service - GmbH</ulink> and <ulink url="http://www.transip.nl/">TransIP - BV</ulink>.</para> + &os; Foundation with support from <link xlink:href="http://www.omc.net/">OMCnet Internet Service + GmbH</link> and <link xlink:href="http://www.transip.nl/">TransIP + BV</link>.</para> </sect2> <sect2> @@ -3515,7 +3399,7 @@ Device 1K-blocks Used Avail Capacity <para><acronym>HAST</acronym> operates synchronously on a block level, making it transparent to file systems and applications. <acronym>HAST</acronym> provides regular GEOM providers in - <filename class="directory">/dev/hast/</filename> for use by + <filename>/dev/hast/</filename> for use by other tools or applications, thus there is no difference between using <acronym>HAST</acronym>-provided devices and raw disks or partitions.</para> @@ -3609,18 +3493,17 @@ Device 1K-blocks Used Avail Capacity <literal>primary</literal>-<literal>secondary</literal> operation using <acronym>HAST</acronym> to replicate the data between the two. The nodes will be called - <literal><replaceable>hasta</replaceable></literal> with an IP + <literal>hasta</literal> with an IP address of <replaceable>172.16.0.1</replaceable> and - <literal><replaceable>hastb</replaceable></literal> with an IP + <literal>hastb</literal> with an IP of address <replaceable>172.16.0.2</replaceable>. Both nodes will have a dedicated hard drive - <devicename>/dev/<replaceable>ad6</replaceable></devicename> + <filename>/dev/ad6</filename> of the same size for <acronym>HAST</acronym> operation. The <acronym>HAST</acronym> pool, sometimes also referred to as a - resource or the GEOM provider in <filename - class="directory">/dev/hast/</filename>, will be + resource or the GEOM provider in <filename>/dev/hast/</filename>, will be called - <filename><replaceable>test</replaceable></filename>.</para> + <filename>test</filename>.</para> <para>Configuration of <acronym>HAST</acronym> is done using <filename>/etc/hast.conf</filename>. This file should be the @@ -3671,13 +3554,13 @@ Device 1K-blocks Used Avail Capacity administrator, or software like <application>Heartbeat</application>, using &man.hastctl.8;. On the primary node, - <literal><replaceable>hasta</replaceable></literal>, issue + <literal>hasta</literal>, issue this command:</para> <screen>&prompt.root; <userinput>hastctl role primary test</userinput></screen> <para>Similarly, run this command on the secondary node, - <literal><replaceable>hastb</replaceable></literal>:</para> + <literal>hastb</literal>:</para> <screen>&prompt.root; <userinput>hastctl role secondary test</userinput></screen> @@ -3704,10 +3587,10 @@ Device 1K-blocks Used Avail Capacity <para>The next step is to create a filesystem on the - <devicename>/dev/hast/<replaceable>test</replaceable></devicename> + <filename>/dev/hast/test</filename> GEOM provider and mount it. This must be done on the <literal>primary</literal> node, as - <filename>/dev/hast/<replaceable>test</replaceable></filename> + <filename>/dev/hast/test</filename> appears only on the <literal>primary</literal> node. Creating the filesystem can take a few minutes, depending on the size of the hard drive:</para> @@ -3743,7 +3626,7 @@ Device 1K-blocks Used Avail Capacity <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 + have its own <filename>carp0</filename> interface with a shared IP address of <replaceable>172.16.0.254</replaceable>. The primary <acronym>HAST</acronym> node of the cluster must be the @@ -3791,7 +3674,7 @@ notify 30 { <screen>&prompt.root; <userinput>service devd restart</userinput></screen> - <para>When the <devicename>carp0</devicename> interface state + <para>When the <filename>carp0</filename> interface state changes by going up or down , the system generates a notification, allowing the &man.devd.8; subsystem to run an arbitrary script, in this case @@ -3828,7 +3711,7 @@ case "$1" in # Wait for any "hastd secondary" processes to stop for disk in ${resources}; do - while $( pgrep -lf "hastd: ${disk} \(secondary\)" > /dev/null 2>&1 ); do + while $( pgrep -lf "hastd: ${disk} \(secondary\)" > /dev/null 2>&1 ); do sleep 1 done @@ -3876,7 +3759,7 @@ case "$1" in umount -f /hast/${disk} fi sleep $delay - hastctl role secondary ${disk} 2>&1 + hastctl role secondary ${disk} 2>&1 if [ $? -ne 0 ]; then logger -p $log -t $name "Unable to switch role to secondary for resource ${disk}." exit 1 @@ -3935,7 +3818,7 @@ esac</programlisting> <para>More detailed information with additional examples can be found in the - <ulink url="http://wiki.FreeBSD.org/HAST">HAST Wiki</ulink> + <link xlink:href="http://wiki.FreeBSD.org/HAST">HAST Wiki</link> page.</para> </sect3> </sect2> @@ -3963,7 +3846,7 @@ esac</programlisting> foreground.</para> </sect3> - <sect3 id="disks-hast-sb"> + <sect3 xml:id="disks-hast-sb"> <title>Recovering from the Split-brain Condition</title> <para><literal>Split-brain</literal> is when the nodes of the |