diff options
Diffstat (limited to 'zh_TW.Big5/books/handbook/disks/chapter.xml')
| -rw-r--r-- | zh_TW.Big5/books/handbook/disks/chapter.xml | 544 |
1 files changed, 227 insertions, 317 deletions
diff --git a/zh_TW.Big5/books/handbook/disks/chapter.xml b/zh_TW.Big5/books/handbook/disks/chapter.xml index 97816e5541..ca159a29bf 100644 --- a/zh_TW.Big5/books/handbook/disks/chapter.xml +++ b/zh_TW.Big5/books/handbook/disks/chapter.xml @@ -5,11 +5,10 @@ $FreeBSD$ Original revision: 1.246 --> - -<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>儲存設備篇</title> - <sect1 id="disks-synopsis"> + <sect1 xml:id="disks-synopsis"> <title>概述</title> @@ -67,12 +66,12 @@ </sect1> - <sect1 id="disks-naming"> + <sect1 xml:id="disks-naming"> <title>裝置名稱</title> <para>下面是 FreeBSD 支援的儲存媒體列表，及它們對應的裝置名稱。</para> - <table id="disk-naming-physical-table" frame="none"> + <table xml:id="disk-naming-physical-table" frame="none"> <title>命名規則</title> <tgroup cols="2"> @@ -134,19 +133,15 @@ </table> </sect1> - <sect1 id="disks-adding"> - <sect1info> + <sect1 xml:id="disks-adding"> + <info><title>新增磁碟</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>新增磁碟</title> + <indexterm> <primary>disk</primary> @@ -157,11 +152,11 @@ 首先將電腦關機，依製造商的指示將磁碟裝上去， 詳細的操作方式請參考製造商的說明文件。</para> - <para>安裝好磁碟後，用 <username>root</username> 登入系統， + <para>安裝好磁碟後，用 <systemitem class="username">root</systemitem> 登入系統， 看一下 <filename>/var/run/dmesg.boot</filename> 以確認系統是否抓到新磁碟。 - 繼續剛才的範例，新增的磁碟會是 <devicename>da1</devicename>， + 繼續剛才的範例，新增的磁碟會是 <filename>da1</filename>， 假設我們想將它掛載到 <filename>/1</filename> 這個位置 - (如果您新增的是 IDE 磁碟的話，請用 <devicename>ad1</devicename>)。</para> + (如果您新增的是 IDE 磁碟的話，請用 <filename>ad1</filename>)。</para> <indexterm><primary>partitions</primary></indexterm> <indexterm><primary>slices</primary></indexterm> @@ -348,31 +343,23 @@ </sect2> </sect1> - <sect1 id="raid"> + <sect1 xml:id="raid"> <title>RAID</title> - <sect2 id="raid-soft"> + <sect2 xml:id="raid-soft"> <title>軟體 RAID</title> - <sect3 id="ccd"> - <sect3info> + <sect3 xml:id="ccd"> + <info><title>連接式磁碟裝置驅動程式(CCD, Concatenated Disk Driver) 設定</title> <authorgroup> - <author> - <firstname>Christopher</firstname> - <surname>Shumway</surname> - <contrib>Original work by </contrib> - </author> + <author><personname><firstname>Christopher</firstname><surname>Shumway</surname></personname><contrib>Original work by </contrib></author> </authorgroup> <authorgroup> - <author> - <firstname>Jim</firstname> - <surname>Brown</surname> - <contrib>Revised by </contrib> - </author> + <author><personname><firstname>Jim</firstname><surname>Brown</surname></personname><contrib>Revised by </contrib></author> </authorgroup> - </sect3info> + </info> - <title>連接式磁碟裝置驅動程式(CCD, Concatenated Disk Driver) 設定</title> + <indexterm><primary>RAID</primary><secondary>software</secondary></indexterm> <indexterm> @@ -391,7 +378,7 @@ <para>選擇大容量儲存設備方案時，首先要定義您的需求。 如果您重視速度或可靠性甚於價格，接下來的介紹恐非您所需。</para> - <sect4 id="ccd-installhw"> + <sect4 xml:id="ccd-installhw"> <title>安裝硬體</title> <para>除了系統磁碟外，下面介紹的 CCD 磁碟陣列將使用到三顆 30GB、 @@ -420,7 +407,7 @@ ad3: 29333MB <WDC WD307AA> [59598/16/63] at ata1-slave UDMA33</programlist 在此我們選擇 &man.ccd.4;。</para> </sect4> - <sect4 id="ccd-setup"> + <sect4 xml:id="ccd-setup"> <title>設定 CCD</title> <para>&man.ccd.4; 可以將多個磁碟接起來成為一個大磁碟。要使用 @@ -437,8 +424,8 @@ ad3: 29333MB <WDC WD307AA> [59598/16/63] at ata1-slave UDMA33</programlist bsdlabel -r -w ad2 auto bsdlabel -r -w ad3 auto</programlisting> - <para>上述指令會建立 <devicename>ad1c</devicename>， - <devicename>ad2c</devicename> 和 <devicename>ad3c</devicename>， + <para>上述指令會建立 <filename>ad1c</filename>， + <filename>ad2c</filename> 和 <filename>ad3c</filename>， 這些 bsdlabel 都使用了整個磁碟。</para> <para>下一步是修改 label type，同樣用 &man.bsdlabel.8; 來處理：</para> @@ -470,13 +457,13 @@ bsdlabel -e ad3</programlisting> </sect4> - <sect4 id="ccd-buildingfs"> + <sect4 xml:id="ccd-buildingfs"> <title>建立檔案系統</title> <para>現在所有的磁碟都已經建好 bsdlabel 了，可以開始建立 &man.ccd.4;。 用 &man.ccdconfig.8; 來建立 &man.ccd.4;，參考下面的指令：</para> - <programlisting>ccdconfig ccd0<co id="co-ccd-dev"/> 32<co id="co-ccd-interleave"/> 0<co id="co-ccd-flags"/> /dev/ad1e<co id="co-ccd-devs"/> /dev/ad2e /dev/ad3e</programlisting> + <programlisting>ccdconfig ccd0<co xml:id="co-ccd-dev"/> 32<co xml:id="co-ccd-interleave"/> 0<co xml:id="co-ccd-flags"/> /dev/ad1e<co xml:id="co-ccd-devs"/> /dev/ad2e /dev/ad3e</programlisting> <para>每個參數的作用如下：</para> @@ -515,7 +502,7 @@ bsdlabel -e ad3</programlisting> </sect4> - <sect4 id="ccd-auto"> + <sect4 xml:id="ccd-auto"> <title>讓一切自動完成</title> <para>通常您會希望每次開機時都能自動掛上(mount) &man.ccd.4;。 @@ -544,7 +531,7 @@ bsdlabel -e ad3</programlisting> </sect4> </sect3> - <sect3 id="vinum"> + <sect3 xml:id="vinum"> <title>Vinum 容量管理系統</title> <indexterm><primary>RAID</primary><secondary>software</secondary></indexterm> @@ -566,7 +553,7 @@ bsdlabel -e ad3</programlisting> </sect3> </sect2> - <sect2 id="raid-hard"> + <sect2 xml:id="raid-hard"> <title>硬體 RAID</title> <indexterm> @@ -679,19 +666,15 @@ ar0: ATA RAID1 subdisks: ad4 ad6 status: REBUILDING 0% completed</screen> </sect2> </sect1> - <sect1 id="usb-disks"> - <sect1info> + <sect1 xml:id="usb-disks"> + <info><title>USB 儲存裝置</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 儲存裝置</title> + <indexterm> <primary>USB</primary> <secondary>disks</secondary> @@ -756,7 +739,7 @@ da0: 1.000MB/s transfers da0: 126MB (258048 512 byte sectors: 64H 32S/T 126C)</screen> <para>Of course, the brand, the device node - (<devicename>da0</devicename>) and other details can differ + (<filename>da0</filename>) and other details can differ according to your configuration.</para> <para>Since the USB device is seen as a SCSI one, the @@ -793,20 +776,15 @@ umass0: detached</screen> </sect2> </sect1> - <sect1 id="creating-cds"> - <sect1info> + <sect1 xml:id="creating-cds"> + <info><title>Creating and Using Optical Media (CDs)</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 Optical Media (CDs)</title> + <indexterm> <primary>CDROMs</primary> <secondary>creating</secondary> @@ -840,9 +818,9 @@ umass0: detached</screen> working with systems 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 you can use to produce a data file containing an ISO 9660 file system. It has options that support various extensions, and is @@ -853,16 +831,15 @@ umass0: detached</screen> <secondary>ATAPI</secondary> </indexterm> <para>Which tool to use to burn the CD depends on whether your CD burner - is ATAPI or something else. ATAPI CD burners use the <command><link - linkend="burncd">burncd</link></command> program that is part of + is ATAPI or something else. ATAPI CD burners use the <command>burncd</command> program that 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.</para> + <command>cdrecord</command> from + the <package>sysutils/cdrtools</package> port.</para> <para><command>burncd</command> has a limited number of supported drives. To find out if a drive is supported, see the - <ulink url="http://www.freebsd.dk/ata/">CD-R/RW supported - drives</ulink> list.</para> + <link xlink:href="http://www.freebsd.dk/ata/">CD-R/RW supported + drives</link> list.</para> <note> <indexterm> @@ -870,35 +847,30 @@ umass0: detached</screen> <secondary>ATAPI/CAM driver</secondary> </indexterm> <para>If you run &os; 5.X, &os; 4.8-RELEASE version or - higher, it will be possible to use <command><link - linkend="cdrecord">cdrecord</link></command> and other tools - for SCSI drives on an ATAPI hardware with the <link - linkend="atapicam">ATAPI/CAM module</link>.</para> + higher, it will be possible to use <command>cdrecord</command> and other tools + for SCSI drives on an ATAPI hardware with the <link linkend="atapicam">ATAPI/CAM module</link>.</para> </note> <para>If you want a CD burning software with a graphical user interface, you should have a look to <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. + 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 <link - linkend="atapicam">ATAPI/CAM module</link> with ATAPI + <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>mkisofs</title> <para>The &man.mkisofs.8; program, which is part of the - <filename role="package">sysutils/cdrtools</filename> port, + <package>sysutils/cdrtools</package> port, 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> @@ -955,7 +927,7 @@ umass0: detached</screen> <screen>&prompt.root; <userinput>mkisofs -R -no-emul-boot -b boot/cdboot -o /tmp/bootable.iso /tmp/myboot</userinput></screen> - <para>Having done that, if you have <devicename>md</devicename> + <para>Having done that, if you have <filename>md</filename> configured in your kernel, you can mount the file system with:</para> <screen>&prompt.root; <userinput>mdconfig -a -t vnode -f /tmp/bootable.iso -u 0</userinput> @@ -970,7 +942,7 @@ umass0: detached</screen> and HFS discs. See the &man.mkisofs.8; manual page for details.</para> </sect2> - <sect2 id="burncd"> + <sect2 xml:id="burncd"> <title>burncd</title> <indexterm> <primary>CDROMs</primary> @@ -982,7 +954,7 @@ umass0: detached</screen> 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>Will burn a copy of <replaceable>imagefile.iso</replaceable> on <replaceable>cddevice</replaceable>. The default device is @@ -991,26 +963,25 @@ umass0: detached</screen> data.</para> </sect2> - <sect2 id="cdrecord"> + <sect2 xml:id="cdrecord"> <title>cdrecord</title> <para>If you do not have an ATAPI CD burner, you will have to use <command>cdrecord</command> to burn your CDs. <command>cdrecord</command> is not part of the base system; - you must install it from either the port at <filename role="package">sysutils/cdrtools</filename> + you must install it from either the port at <package>sysutils/cdrtools</package> or the appropriate package. Changes to the base system can cause binary versions of this program to fail, possibly resulting in a <quote>coaster</quote>. You should therefore either upgrade the - port when you upgrade your system, or if you are <link - linkend="stable">tracking -STABLE</link>, upgrade the port when a + port when you upgrade your system, or if you are <link linkend="stable">tracking -STABLE</link>, upgrade the port when a new version becomes available.</para> <para>While <command>cdrecord</command> has many options, basic usage is even simpler than <command>burncd</command>. 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 setting, use @@ -1053,7 +1024,7 @@ scsibus1: audio tracks, controlling the speed, and other things.</para> </sect2> - <sect2 id="duplicating-audiocds"> + <sect2 xml:id="duplicating-audiocds"> <title>Duplicating Audio CDs</title> <para>You can duplicate an audio CD by extracting the audio data from @@ -1074,7 +1045,7 @@ 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> @@ -1086,7 +1057,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 needed. @@ -1119,19 +1090,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>You can copy a data CD to a image file that is functionally equivalent to the image file created with &man.mkisofs.8;, and you can use it to duplicate any data CD. The example given here assumes that your CDROM - device is <devicename>acd0</devicename>. Substitute your + device is <filename>acd0</filename>. Substitute your correct CDROM device.</para> <screen>&prompt.root; <userinput>dd if=/dev/acd0 of=file.iso bs=2048</userinput></screen> @@ -1140,7 +1111,7 @@ scsibus1: described above.</para> </sect2> - <sect2 id="mounting-cd"> + <sect2 xml:id="mounting-cd"> <title>Using Data CDs</title> <para>Now that you have created a standard data CDROM, you @@ -1181,7 +1152,7 @@ scsibus1: CD9660 driver includes hooks to load an appropriate Unicode conversion table on the fly. Modules for some of the common encodings are available via the - <filename role="package">sysutils/cd9660_unicode</filename> port.)</para> + <package>sysutils/cd9660_unicode</package> port.)</para> <para>Occasionally, you might get <errorname>Device not configured</errorname> when trying to mount a CDROM. This @@ -1202,7 +1173,7 @@ scsibus1: bus reset.</para> </sect2> - <sect2 id="rawdata-cd"> + <sect2 xml:id="rawdata-cd"> <title>Burning Raw Data CDs</title> <para>You can choose to burn a file directly to CD, without @@ -1224,18 +1195,14 @@ scsibus1: &man.mkisofs.8; as 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> @@ -1244,8 +1211,7 @@ scsibus1: <para>This driver allows ATAPI devices (CD-ROM, CD-RW, DVD drives etc...) to be accessed through the SCSI subsystem, and - so allows the use of applications like <filename - role="package">sysutils/cdrdao</filename> or + so allows the use of applications like <package>sysutils/cdrdao</package> or &man.cdrecord.1;.</para> <para>To use this driver, you will need to add the following @@ -1278,9 +1244,9 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c mount a CD-ROM on <filename>/mnt</filename>, just 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>, you can run the following + <para>As <systemitem class="username">root</systemitem>, you can run the following command to get the SCSI address of the burner:</para> <screen>&prompt.root; <userinput>camcontrol devlist</userinput> @@ -1295,26 +1261,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 Optical Media (DVDs)</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 Optical Media (DVDs)</title> + <indexterm> <primary>DVD</primary> <secondary>burning</secondary> @@ -1334,8 +1292,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <itemizedlist> <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>. + available. The DVD-R standard is defined by the <link xlink:href="http://www.dvdforum.com/forum.shtml">DVD Forum</link>. This format is write once.</para> </listitem> @@ -1355,8 +1312,8 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <listitem> <para>DVD+RW: This is a rewriteable 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> @@ -1385,8 +1342,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <para>The program &man.growisofs.1; will be used to perform DVD recording. This command is part of the - <application>dvd+rw-tools</application> utilities (<filename - role="package">sysutils/dvd+rw-tools</filename>). The + <application>dvd+rw-tools</application> utilities (<package>sysutils/dvd+rw-tools</package>). The <application>dvd+rw-tools</application> support all DVD media types.</para> @@ -1405,15 +1361,13 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <para>Before attempting to use the <application>dvd+rw-tools</application> you should consult the - <ulink - url="http://fy.chalmers.se/~appro/linux/DVD+RW/hcn.html">dvd+rw-tools' - hardware compatibility notes</ulink> for any information + <link xlink:href="http://fy.chalmers.se/~appro/linux/DVD+RW/hcn.html">dvd+rw-tools' + hardware compatibility notes</link> for any information related to your DVD burner.</para> <note> <para>If you want a graphical user interface, you should have - a look to <application>K3b</application> (<filename - role="package">sysutils/k3b</filename>) which provides a + a look to <application>K3b</application> (<package>sysutils/k3b</package>) which provides a user friendly interface to &man.growisofs.1; and many others burning tools.</para> </note> @@ -1422,17 +1376,15 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <sect2> <title>Burning Data DVDs</title> - <para>The &man.growisofs.1; command is a frontend to <link - linkend="mkisofs">mkisofs</link>, it will invoke + <para>The &man.growisofs.1; command is a frontend to <link linkend="mkisofs">mkisofs</link>, it will invoke &man.mkisofs.8; to create the file system layout and will perform the write on the DVD. This means you do not need to create an image of the data before the burning process.</para> - <para>To burn onto a DVD+R or a DVD-R the data from the <filename - class="directory">/path/to/data</filename> directory, use the + <para>To burn onto a DVD+R or a DVD-R the data from the <filename>/path/to/data</filename> directory, 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>The options <option>-J -R</option> are passed to &man.mkisofs.8; for the file system creation (in this case: an @@ -1452,7 +1404,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c example to burn the image <replaceable>imagefile.iso</replaceable>, we will run:</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. If you want @@ -1472,18 +1424,17 @@ 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 ISO 9660 and the micro-UDF (M-UDF) specifications. The DVD-Video also presents a specific data structure hierarchy, it is the reason - why you need a particular program such as <filename - role="package">multimedia/dvdauthor</filename> to author the + why you need a particular program such as <package>multimedia/dvdauthor</package> to author the DVD.</para> <para>If you already have an image of the DVD-Video file system, just burn it in the same way as for any image, see the previous section for an example. If you have made the DVD authoring and the result is in, for example, the directory - <filename class="directory">/path/to/video</filename>, the + <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>The <option>-dvd-video</option> option will be passed down to &man.mkisofs.8; and will instruct it to create a DVD-Video file system @@ -1507,7 +1458,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <command>dvd+rw-format</command> 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>You need to perform this operation just once, keep in mind that only virgin DVD+RW medias need to be formatted. Then you @@ -1519,7 +1470,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c blank it, you just have to write over the previous recording (in performing a new initial session), 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>DVD+RW format offers the possibility to easily append data to a previous recording. The operation consists in merging a @@ -1530,7 +1481,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <para>For example, if we want to append data to our previous DVD+RW, we have to 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 we used to burn the initial session should be used during next writes.</para> @@ -1545,7 +1496,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <para>If for any reason you really want to blank the media, do the following:</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> @@ -1567,7 +1518,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <para>To blank a DVD-RW in sequential mode, run:</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 (<option>-blank=full</option>) will take @@ -1576,7 +1527,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c DVD-RW will 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>The <option>-use-the-force-luke=dao</option> option should not be required since &man.growisofs.1; attempts to @@ -1591,7 +1542,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>If you want to append some data to your previous recording, you will have to use the &man.growisofs.1; @@ -1611,11 +1562,11 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <para>To put a DVD-RW in the 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 the 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> @@ -1632,7 +1583,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 line with a DVD+RW or a DVD-RW in restricted overwrite mode, will append data in merging the new session to @@ -1655,16 +1606,14 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <para>To obtain more information about a DVD, the <command>dvd+rw-mediainfo - <replaceable>/dev/cd0</replaceable></command> command can be + /dev/cd0</command> command can be ran with the disc in the drive.</para> <para>More information about the <application>dvd+rw-tools</application> can be found in - the &man.growisofs.1; manual page, 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> + the &man.growisofs.1; manual page, 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>The <command>dvd+rw-mediainfo</command> output of the @@ -1675,27 +1624,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 @@ -1716,7 +1657,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <para>Floppy disks are accessed through entries in <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> @@ -1740,7 +1681,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <title>Formatting Floppy Disks</title> <para>Use the - <filename>/dev/fd<replaceable>N</replaceable></filename> + <filename>/dev/fdN</filename> devices to format the floppy. Insert a new 3.5inch floppy disk in your drive and issue:</para> @@ -1801,19 +1742,19 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <title>Using the Floppy</title> <para>To use the floppy, mount it with &man.mount.msdos.8;. One can also use - <filename role="package">emulators/mtools</filename> from the ports + <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> <para>The major tape media are the 4mm, 8mm, QIC, mini-cartridge and DLT.</para> - <sect2 id="backups-tapebackups-4mm"> + <sect2 xml:id="backups-tapebackups-4mm"> <title>4mm (DDS: Digital Data Storage)</title> <indexterm> @@ -1850,7 +1791,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c backups.</para> </sect2> - <sect2 id="backups-tapebackups-8mm"> + <sect2 xml:id="backups-tapebackups-8mm"> <title>8mm (Exabyte)</title> <indexterm> <primary>tape media</primary> @@ -1883,7 +1824,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c tape from one edge to the other.</para> </sect2> - <sect2 id="backups-tapebackups-qic"> + <sect2 xml:id="backups-tapebackups-qic"> <title>QIC</title> <indexterm> <primary>tape media</primary> @@ -1920,7 +1861,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c <para>Tapes should be retired from use after 5,000 backups.</para> </sect2> - <sect2 id="backups-tapebackups-dlt"> + <sect2 xml:id="backups-tapebackups-dlt"> <title>DLT</title> <indexterm> <primary>tape media</primary> @@ -1956,7 +1897,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c </sect2> <sect2> - <title id="backups-tapebackups-ait">AIT</title> + <title xml:id="backups-tapebackups-ait">AIT</title> <indexterm> <primary>tape media</primary> <secondary>AIT</secondary> @@ -2016,10 +1957,10 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen> </sect2> </sect1> - <sect1 id="backups-floppybackups"> + <sect1 xml:id="backups-floppybackups"> <title>Backups to Floppies</title> - <sect2 id="floppies-using"> + <sect2 xml:id="floppies-using"> <title>Can I Use Floppies for Backing Up My Data?</title> <indexterm><primary>backup floppies</primary></indexterm> <indexterm><primary>floppy disks</primary></indexterm> @@ -2053,7 +1994,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen> reputable manufacturer.</para> </sect2> - <sect2 id="floppies-creating"> + <sect2 xml:id="floppies-creating"> <title>So How Do I Backup My Data to Floppies?</title> <para>The best way to backup to floppy disk is to use @@ -2062,7 +2003,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen> floppies.</para> <para>To backup all the files in the current directory and sub-directory - use this (as <username>root</username>):</para> + use this (as <systemitem class="username">root</systemitem>):</para> <screen>&prompt.root; <userinput>tar Mcvf /dev/fd0 *</userinput></screen> @@ -2076,7 +2017,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen> the specified files have been archived.</para> </sect2> - <sect2 id="floppies-compress"> + <sect2 xml:id="floppies-compress"> <title>Can I Compress My Backups?</title> <indexterm> <primary><command>tar</command></primary> @@ -2093,7 +2034,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen> &man.gunzip.1; the files again!</para> </sect2> - <sect2 id="floppies-restoring"> + <sect2 xml:id="floppies-restoring"> <title>How Do I Restore My Backups?</title> <para>To restore the entire archive use:</para> @@ -2104,7 +2045,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen> specific files. First, you can start with the first floppy and use:</para> - <screen>&prompt.root; <userinput>tar Mxvf /dev/fd0 <replaceable>filename</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>tar Mxvf /dev/fd0 filename</userinput></screen> <para>The utility &man.tar.1; will prompt you to insert subsequent floppies until it finds the required file.</para> @@ -2117,19 +2058,15 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen> </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> @@ -2208,7 +2145,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen> you want to protect against, and how you will handle each.</para> </sect1> - <sect1 id="backup-basics"> + <sect1 xml:id="backup-basics"> <title>Backup Basics</title> <para>The three major backup programs are @@ -2261,9 +2198,9 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen> to use on the remote computer. When <command>rdump</command>ing from a FreeBSD computer to an Exabyte tape drive connected to a Sun 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>Beware: there are security implications to allowing <filename>.rhosts</filename> authentication. Evaluate your @@ -2316,16 +2253,16 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen> supports remote devices using the same syntax as <command>rdump</command>. To <command>tar</command> to an Exabyte tape drive connected to a Sun called - <hostid>komodo</hostid>, use:</para> + <systemitem>komodo</systemitem>, use:</para> - <screen>&prompt.root; <userinput>/usr/bin/gtar cf komodo:/dev/nsa8 . 2>&1</userinput></screen> + <screen>&prompt.root; <userinput>/usr/bin/gtar cf komodo:/dev/nsa8 . 2>&1</userinput></screen> <para>The same could be accomplished with <command>bsdtar</command> by using a pipeline and <command>rsh</command> to send the data to a remote tape drive.</para> - <screen>&prompt.root; <userinput>tar cf - . | rsh <replaceable>hostname</replaceable> dd of=<replaceable>tape-device</replaceable> obs=20b</userinput></screen> + <screen>&prompt.root; <userinput>tar cf - . | rsh hostname dd of=tape-device obs=20b</userinput></screen> <para>If you are worried about the security of backing up over a network you should use the <command>ssh</command> command @@ -2353,10 +2290,10 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen> the network. You can use a pipeline and <command>rsh</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 you want to back up, @@ -2388,7 +2325,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen> <command>tar</command>.</para> </sect2> - <sect2 id="backups-programs-amanda"> + <sect2 xml:id="backups-programs-amanda"> <title><application>Amanda</application></title> <indexterm> <primary>backup software</primary> @@ -2460,9 +2397,8 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen> names, unreadable and 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://berdmann.dyndns.org/zwicky/testdump.doc.html">torture-testing - Backup and Archive Programs</ulink>.</para> + See <link xlink:href="http://berdmann.dyndns.org/zwicky/testdump.doc.html">torture-testing + Backup and Archive Programs</link>.</para> </sect2> <sect2> @@ -2574,7 +2510,7 @@ then The MINI kernel does not exist, please create one. Here is an example config file: # -# MINI -- A kernel to get FreeBSD onto a disk. +# MINI - A kernel to get FreeBSD onto a disk. # machine "i386" cpu "I486_CPU" @@ -2704,8 +2640,8 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting> floppy.</literal> option. Insert the <filename>fixit.flp</filename> when prompted. <command>restore</command> and the other programs that you need are - located in <filename class="directory">/mnt2/rescue</filename> - (<filename class="directory">/mnt2/stand</filename> for + located in <filename>/mnt2/rescue</filename> + (<filename>/mnt2/stand</filename> for &os; versions older than 5.2).</para> <para>Recover each file system separately.</para> @@ -2739,17 +2675,13 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting> </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> <primary>disks</primary> @@ -2767,8 +2699,7 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting> <primary>disks</primary> <secondary>memory</secondary> </indexterm> - <para>These include network file systems such as the <link - linkend="network-nfs">Network File System</link> and Coda, memory-based + <para>These include network file systems such as the <link linkend="network-nfs">Network File System</link> and Coda, memory-based file systems and file-backed file systems.</para> @@ -2781,7 +2712,7 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting> user.</para> </note> - <sect2 id="disks-mdconfig"> + <sect2 xml:id="disks-mdconfig"> <title>File-Backed File System</title> <indexterm> <primary>disks</primary> @@ -2807,8 +2738,8 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting> <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 &man.mdconfig.8;:</para> @@ -2816,18 +2747,18 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting> <example> <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> @@ -2836,7 +2767,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on <option>-u</option> option, &man.mdconfig.8; will use the &man.md.4; automatic allocation to select an unused device. The name of the allocated unit will be output on stdout like - <devicename>md4</devicename>. For more details about + <filename>md4</filename>. For more details about &man.mdconfig.8;, please refer to the manual page.</para> <para>The utility &man.mdconfig.8; is very useful, however it @@ -2850,11 +2781,11 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on <example> <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> @@ -2866,7 +2797,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on </sect2> - <sect2 id="disks-md-freebsd5"> + <sect2 xml:id="disks-md-freebsd5"> <title>Memory-Based File System</title> <indexterm> <primary>disks</primary> @@ -2888,15 +2819,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 malloc -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 malloc -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, 256 inodes. with soft updates super-block backups (for fsck -b #) at: 32, 2624, 5216, 7808 -&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 4846 2 4458 0% /mnt</screen> </example> @@ -2904,8 +2835,8 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on <example> <title>Creating a New Memory-Based Disk with <command>mdmfs</command></title> - <screen>&prompt.root; <userinput>mdmfs -M -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 -M -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> @@ -2935,7 +2866,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 in using the command <command>mdconfig @@ -2944,19 +2875,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> @@ -3048,10 +2975,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on <para>For more information about <option>softupdates</option> and file system snapshots, including technical papers, you can 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>磁碟空間配額(Quota)</title> <indexterm> <primary>accounting</primary> @@ -3191,7 +3118,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on 的 <option>-p</option> 參數功能來完成。 首先， 把某個帳號調為想要的相關配額，然後可以用 <command>edquota -p protouser startuid-enduid</command> 之類的方式來改。 - 舉例來說，假設 <username>test</username> 這帳號已經設定好相關配額， + 舉例來說，假設 <systemitem class="username">test</systemitem> 這帳號已經設定好相關配額， 然後要改的對象為 UID 從 10,000 到 19,999 的帳號， 那麼就可以下列指令來設定同樣的配額：</para> @@ -3255,22 +3182,17 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on </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> <secondary>encrypting</secondary></indexterm> @@ -3301,7 +3223,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on <procedure> <step> - <title>Become <username>root</username></title> + <title>Become <systemitem class="username">root</systemitem></title> <para>Configuring <application>gbde</application> requires super-user privileges.</para> @@ -3318,8 +3240,7 @@ Password:</screen> <para><literal>options GEOM_BDE</literal></para> - <para>Rebuild the kernel as described in <xref - linkend="kernelconfig"/>.</para> + <para>Rebuild the kernel as described in <xref linkend="kernelconfig"/>.</para> <para>Reboot into the new kernel.</para> </step> @@ -3340,11 +3261,10 @@ Password:</screen> <step> <title>Add the New Hard Drive</title> - <para>Install the new drive to the system as explained in <xref - linkend="disks-adding"/>. For the purposes of this example, + <para>Install the new drive to the system as explained in <xref linkend="disks-adding"/>. For the purposes of this example, a new hard drive partition has been added as <filename>/dev/ad4s1c</filename>. The - <filename>/dev/ad0s1<replaceable>*</replaceable></filename> + <filename>/dev/ad0s1*</filename> devices represent existing standard FreeBSD partitions on the example system.</para> @@ -3401,9 +3321,8 @@ sector_size = 2048 passphrase that you choose. <footnote> <para>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></footnote></para> + to remember, see the <link xlink:href="http://world.std.com/~reinhold/diceware.html">Diceware + Passphrase</link> website.</para></footnote></para> <para>The <command>gbde init</command> command creates a lock file for your <application>gbde</application> partition that in @@ -3456,7 +3375,7 @@ sector_size = 2048 <para>The &man.newfs.8; command 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> @@ -3497,7 +3416,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 user <username>root</username>.</para> + executed as user <systemitem class="username">root</systemitem>.</para> <procedure> <step> @@ -3570,7 +3489,7 @@ gbde_devices="ad4s1c"</screen> <para>&man.sysinstall.8; is incompatible with <application>gbde</application>-encrypted devices. All - <devicename><replaceable>*</replaceable>.bde</devicename> devices must be detached from the + <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 our example, use the following command:</para> @@ -3585,18 +3504,14 @@ gbde_devices="ad4s1c"</screen> </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>A new cryptographic GEOM class is available as of &os; 6.0 - <command>geli</command>. It is currently being developed by @@ -3665,8 +3580,7 @@ gbde_devices="ad4s1c"</screen> <screen>options GEOM_ELI device crypto</screen> - <para>Rebuild the kernel as described in <xref - linkend="kernelconfig"/>.</para> + <para>Rebuild the kernel as described in <xref linkend="kernelconfig"/>.</para> <para>Alternatively, the <command>geli</command> module can be loaded at boot time. Add the following line to the @@ -3683,7 +3597,7 @@ device crypto</screen> <para>The following example will describe 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 be protected by a passphrase as well. Provider's sector size will be 4kB big. @@ -3724,7 +3638,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> @@ -3755,7 +3669,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> partition + 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> @@ -3807,18 +3721,14 @@ geli_da2_flags="-p -k /root/da2.key"</screen> </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> <secondary>encrypting</secondary> @@ -3854,7 +3764,7 @@ geli_da2_flags="-p -k /root/da2.key"</screen> <title>Preparation</title> <note> - <para>For the remainder of this section, <devicename>ad0s1b</devicename> + <para>For the remainder of this section, <filename>ad0s1b</filename> will be the swap partition.</para> </note> |