Lines 14-22
Link Here
|
14 |
<sect1 xml:id="disks-synopsis"> |
14 |
<sect1 xml:id="disks-synopsis"> |
15 |
<title>Synopsis</title> |
15 |
<title>Synopsis</title> |
16 |
|
16 |
|
17 |
<para>This chapter covers the use of disks in &os;. This includes |
17 |
<para>This chapter covers the configuration and use of disks in &os;. This includes |
18 |
memory-backed disks, network-attached disks, standard SCSI/IDE |
18 |
memory-backed disks, network-attached disks, standard <acronym>SCSI</acronym>/<acronym>IDE</acronym> and <acronym>SATA</acronym> |
19 |
storage devices, and devices using the USB interface.</para> |
19 |
storage devices, and removable devices using the <acronym>USB</acronym> interface.</para> |
20 |
|
20 |
|
21 |
<para>After reading this chapter, you will know:</para> |
21 |
<para>After reading this chapter, you will know:</para> |
22 |
|
22 |
|
Lines 23-29
Link Here
|
23 |
<itemizedlist> |
23 |
<itemizedlist> |
24 |
<listitem> |
24 |
<listitem> |
25 |
<para>The terminology &os; uses to describe the organization |
25 |
<para>The terminology &os; uses to describe the organization |
26 |
of data on a physical disk.</para> |
26 |
of data on a physical or logical disk.</para> |
27 |
</listitem> |
27 |
</listitem> |
28 |
|
28 |
|
29 |
<listitem> |
29 |
<listitem> |
Lines 32-38
Link Here
|
32 |
</listitem> |
32 |
</listitem> |
33 |
|
33 |
|
34 |
<listitem> |
34 |
<listitem> |
35 |
<para>How to configure &os; to use USB storage devices.</para> |
35 |
<para>How to configure &os; to use <acronym>USB</acronym> storage devices.</para> |
36 |
</listitem> |
36 |
</listitem> |
37 |
|
37 |
|
38 |
<listitem> |
38 |
<listitem> |
Lines 93-167
Link Here
|
93 |
|
93 |
|
94 |
<tbody> |
94 |
<tbody> |
95 |
<row> |
95 |
<row> |
96 |
<entry>IDE hard drives</entry> |
96 |
<entry><acronym>IDE</acronym> hard drives</entry> |
97 |
<entry><literal>ad</literal> or |
97 |
<entry><filename>ad</filename> or |
98 |
<literal>ada</literal></entry> |
98 |
<filename>ada</filename></entry> |
99 |
</row> |
99 |
</row> |
100 |
|
100 |
|
101 |
<row> |
101 |
<row> |
102 |
<entry>IDE CD-ROM drives</entry> |
102 |
<entry><acronym>IDE</acronym> CD-ROM drives</entry> |
103 |
<entry><literal>acd</literal> or |
103 |
<entry><filename>acd</filename> or |
104 |
<literal>cd</literal></entry> |
104 |
<filename>cd</filename></entry> |
105 |
</row> |
105 |
</row> |
106 |
|
106 |
|
107 |
<row> |
107 |
<row> |
108 |
<entry>SATA hard drives</entry> |
108 |
<entry><acronym>SATA</acronym> hard drives</entry> |
109 |
<entry><literal>ad</literal> or |
109 |
<entry><filename>ad</filename> or |
110 |
<literal>ada</literal></entry> |
110 |
<filename>ada</filename></entry> |
111 |
</row> |
111 |
</row> |
112 |
|
112 |
|
113 |
<row> |
113 |
<row> |
114 |
<entry>SATA CD-ROM drives</entry> |
114 |
<entry><acronym>SATA</acronym> CD-ROM drives</entry> |
115 |
<entry><literal>acd</literal> or |
115 |
<entry><filename>acd</filename> or |
116 |
<literal>cd</literal></entry> |
116 |
<filename>cd</filename></entry> |
117 |
</row> |
117 |
</row> |
118 |
|
118 |
|
119 |
<row> |
119 |
<row> |
120 |
<entry>SCSI hard drives and USB Mass storage |
120 |
<entry><acronym>SCSI</acronym> hard drives and <acronym>USB</acronym> Mass storage |
121 |
devices</entry> |
121 |
devices</entry> |
122 |
<entry><literal>da</literal></entry> |
122 |
<entry><filename>da</filename></entry> |
123 |
</row> |
123 |
</row> |
124 |
|
124 |
|
125 |
<row> |
125 |
<row> |
126 |
<entry>SCSI CD-ROM drives</entry> |
126 |
<entry><acronym>SCSI</acronym> CD-ROM drives</entry> |
127 |
<entry><literal>cd</literal></entry> |
127 |
<entry><filename>cd</filename></entry> |
128 |
</row> |
128 |
</row> |
129 |
|
129 |
|
130 |
<row> |
130 |
<row> |
131 |
<entry>Assorted non-standard CD-ROM drives</entry> |
131 |
<entry>Assorted non-standard CD-ROM drives</entry> |
132 |
<entry><literal>mcd</literal> for Mitsumi CD-ROM and |
132 |
<entry><filename>mcd</filename> for Mitsumi CD-ROM and |
133 |
<literal>scd</literal> for Sony CD-ROM devices</entry> |
133 |
<filename>scd</filename> for Sony CD-ROM devices</entry> |
134 |
</row> |
134 |
</row> |
135 |
|
135 |
|
136 |
<row> |
136 |
<row> |
137 |
<entry>Floppy drives</entry> |
137 |
<entry>Floppy drives</entry> |
138 |
<entry><literal>fd</literal></entry> |
138 |
<entry><filename>fd</filename></entry> |
139 |
</row> |
139 |
</row> |
140 |
|
140 |
|
141 |
<row> |
141 |
<row> |
142 |
<entry>SCSI tape drives</entry> |
142 |
<entry><acronym>SCSI</acronym> tape drives</entry> |
143 |
<entry><literal>sa</literal></entry> |
143 |
<entry><filename>sa</filename></entry> |
144 |
</row> |
144 |
</row> |
145 |
|
145 |
|
146 |
<row> |
146 |
<row> |
147 |
<entry>IDE tape drives</entry> |
147 |
<entry><acronym>IDE</acronym> tape drives</entry> |
148 |
<entry><literal>ast</literal></entry> |
148 |
<entry><filename>ast</filename></entry> |
149 |
</row> |
149 |
</row> |
150 |
|
150 |
|
151 |
<row> |
151 |
<row> |
152 |
<entry>Flash drives</entry> |
152 |
<entry>Flash drives</entry> |
153 |
<entry><literal>fla</literal> for &diskonchip; Flash |
153 |
<entry><filename>fla</filename> for &diskonchip; Flash |
154 |
device</entry> |
154 |
device</entry> |
155 |
</row> |
155 |
</row> |
156 |
|
156 |
|
157 |
<row> |
157 |
<row> |
158 |
<entry>RAID drives</entry> |
158 |
<entry>RAID drives</entry> |
159 |
<entry><literal>aacd</literal> for &adaptec; AdvancedRAID, |
159 |
<entry><filename>aacd</filename> for &adaptec; AdvancedRAID, |
160 |
<literal>mlxd</literal> and <literal>mlyd</literal> |
160 |
<filename>mlxd</filename> and <filename>mlyd</filename> |
161 |
for &mylex;, |
161 |
for &mylex;, |
162 |
<literal>amrd</literal> for AMI &megaraid;, |
162 |
<filename>amrd</filename> for AMI &megaraid;, |
163 |
<literal>idad</literal> for Compaq Smart RAID, |
163 |
<filename>idad</filename> for Compaq Smart RAID, |
164 |
<literal>twed</literal> for &tm.3ware; RAID.</entry> |
164 |
<filename>twed</filename> for &tm.3ware; RAID, |
|
|
165 |
<filename>mfid</filename> for &lsilogic; &megaraid;.</entry> |
165 |
</row> |
166 |
</row> |
166 |
</tbody> |
167 |
</tbody> |
167 |
</tgroup> |
168 |
</tgroup> |
Lines 402-408
Link Here
|
402 |
|
403 |
|
403 |
<sect1 xml:id="usb-disks"> |
404 |
<sect1 xml:id="usb-disks"> |
404 |
<info> |
405 |
<info> |
405 |
<title>USB Storage Devices</title> |
406 |
<title><acronym>USB</acronym> Storage Devices</title> |
406 |
|
407 |
|
407 |
<authorgroup> |
408 |
<authorgroup> |
408 |
<author> |
409 |
<author> |
Lines 420-471
Link Here
|
420 |
<secondary>disks</secondary> |
421 |
<secondary>disks</secondary> |
421 |
</indexterm> |
422 |
</indexterm> |
422 |
|
423 |
|
423 |
<para>Many external storage solutions, such as hard drives, USB |
424 |
<para>Many external storage solutions, such as hard drives, <acronym>USB</acronym> |
424 |
thumbdrives, and CD/DVD burners, use the Universal Serial Bus |
425 |
thumbdrives, and CD/DVD burners, use the Universal Serial Bus |
425 |
(USB). &os; provides support for these devices.</para> |
426 |
(<acronym>USB</acronym>). &os; provides support for these devices.</para> |
426 |
|
427 |
|
427 |
<sect2> |
428 |
<sect2> |
428 |
<title>Configuration</title> |
429 |
<title>Configuration</title> |
429 |
|
430 |
|
430 |
<para>The USB mass storage devices driver, &man.umass.4;, is |
431 |
<para>The <acronym>USB</acronym> mass storage devices driver, &man.umass.4;, is |
431 |
built into the <filename>GENERIC</filename> kernel and |
432 |
built into the <filename>GENERIC</filename> kernel and |
432 |
provides support for USB storage devices. For a custom |
433 |
provides support for <acronym>USB</acronym> storage devices. For a custom |
433 |
kernel, be sure that the following lines are present in the |
434 |
kernel, be sure that the following lines are present in the |
434 |
kernel configuration file:</para> |
435 |
kernel configuration file:</para> |
435 |
|
436 |
|
436 |
<programlisting>device scbus |
437 |
<programlisting>device scbus # SCSI bus (required for ATA/SCSI) |
437 |
device da |
438 |
device da # Direct Access (disks) |
438 |
device pass |
439 |
device cd # CD |
439 |
device uhci |
440 |
device pass # Passthrough device (direct ATA/SCSI access) |
440 |
device ohci |
441 |
device uhci # UHCI PCI->USB interface |
441 |
device ehci |
442 |
device ohci # OHCI PCI->USB interface |
442 |
device usb |
443 |
device ehci # EHCI PCI->USB interface (USB 2.0) |
443 |
device umass</programlisting> |
444 |
device xhci # XHCI PCI->USB interface (USB 3.0) |
|
|
445 |
device usb # USB Bus (required) |
446 |
device umass # Disks/Mass storage - Requires scbus and da</programlisting> |
444 |
|
447 |
|
445 |
<para>Since the &man.umass.4; driver uses the SCSI subsystem to |
448 |
<para>Since the &man.umass.4; driver uses the <acronym>SCSI</acronym> subsystem to |
446 |
access the USB storage devices, any USB device will be seen as |
449 |
access the <acronym>USB</acronym> storage devices, any <acronym>USB</acronym> device will be seen as |
447 |
a SCSI device by the system. Depending on the USB chipset on |
450 |
a <acronym>SCSI</acronym> device by the system. Depending on the <acronym>USB</acronym> chipset on |
448 |
the motherboard, <literal>device uhci</literal> or |
451 |
the motherboard, <literal>device uhci</literal> or |
449 |
<literal>device ohci</literal> is used to provide USB 1.X |
452 |
<literal>device ohci</literal> is used to provide <acronym>USB</acronym> 1.X |
450 |
support. Support for USB 2.0 controllers is provided by |
453 |
support. Support for <acronym>USB</acronym> 2.0 controllers is provided by |
451 |
<literal>device ehci</literal>.</para> |
454 |
<literal>device ehci</literal> and <acronym>USB</acronym> 3.0 |
452 |
|
455 |
by <filename>xhci</filename>.</para> |
453 |
<note> |
|
|
454 |
<para>If the USB device is a CD or DVD burner, &man.cd.4;, |
455 |
must be added to the kernel via the line:</para> |
456 |
|
457 |
<programlisting>device cd</programlisting> |
458 |
|
459 |
<para>Since the burner is seen as a SCSI drive, the driver |
460 |
&man.atapicam.4; should not be used in the kernel |
461 |
configuration.</para> |
462 |
</note> |
463 |
</sect2> |
456 |
</sect2> |
464 |
|
457 |
|
465 |
<sect2> |
458 |
<sect2> |
466 |
<title>Testing the Configuration</title> |
459 |
<title>Testing the Configuration</title> |
467 |
|
460 |
|
468 |
<para>To test the USB configuration, plug in the USB device. In |
461 |
<para>To test the <acronym>USB</acronym> configuration, plug in the <acronym>USB</acronym> device. In |
469 |
the system message buffer, &man.dmesg.8;, the drive should |
462 |
the system message buffer, &man.dmesg.8;, the drive should |
470 |
appear as something like:</para> |
463 |
appear as something like:</para> |
471 |
|
464 |
|
Lines 479-486
Link Here
|
479 |
<para>The brand, device node (<filename>da0</filename>), and |
472 |
<para>The brand, device node (<filename>da0</filename>), and |
480 |
other details will differ according to the device.</para> |
473 |
other details will differ according to the device.</para> |
481 |
|
474 |
|
482 |
<para>Since the USB device is seen as a SCSI one, |
475 |
<para>Since the <acronym>USB</acronym> device is seen as a <acronym>SCSI</acronym> device, |
483 |
<command>camcontrol</command> can be used to list the USB |
476 |
<command>camcontrol</command> can be used to list the <acronym>USB</acronym> |
484 |
storage devices attached to the system:</para> |
477 |
storage devices attached to the system:</para> |
485 |
|
478 |
|
486 |
<screen>&prompt.root; <userinput>camcontrol devlist</userinput> |
479 |
<screen>&prompt.root; <userinput>camcontrol devlist</userinput> |
Lines 488-494
Link Here
|
488 |
|
481 |
|
489 |
<para>If the drive comes with a file system, it can be mounted. |
482 |
<para>If the drive comes with a file system, it can be mounted. |
490 |
Refer to <xref linkend="disks-adding"/> for |
483 |
Refer to <xref linkend="disks-adding"/> for |
491 |
instructions on how to format and create partitions on the USB |
484 |
instructions on how to format and create partitions on the <acronym>USB</acronym> |
492 |
drive.</para> |
485 |
drive.</para> |
493 |
|
486 |
|
494 |
<warning> |
487 |
<warning> |
Lines 511-534
Link Here
|
511 |
add path 'da*' mode 0660 group operator</programlisting> |
504 |
add path 'da*' mode 0660 group operator</programlisting> |
512 |
|
505 |
|
513 |
<note> |
506 |
<note> |
514 |
<para>If SCSI disks are installed in the system, change |
507 |
<para>If <acronym>SCSI</acronym> disks are installed in the system, change |
515 |
the second line as follows:</para> |
508 |
the second line as follows:</para> |
516 |
|
509 |
|
517 |
<programlisting>add path 'da[3-9]*' mode 0660 group operator</programlisting> |
510 |
<programlisting>add path 'da[3-9]*' mode 0660 group operator</programlisting> |
518 |
|
511 |
|
519 |
<para>This will exclude the first three SCSI disks |
512 |
<para>This will exclude the first three <acronym>SCSI</acronym> disks |
520 |
(<filename>da0</filename> to |
513 |
(<filename>da0</filename> through |
521 |
<filename>da2</filename>)from belonging to the |
514 |
<filename>da2</filename>) from belonging to the |
522 |
<systemitem class="groupname">operator</systemitem> |
515 |
<systemitem class="groupname">operator</systemitem> |
523 |
group.</para> |
516 |
group.</para> |
524 |
</note> |
517 |
</note> |
525 |
|
518 |
|
526 |
<para>Next, enable the &man.devfs.rules.5; ruleset in |
519 |
<para>Enable the &man.devfs.rules.5; ruleset in |
527 |
<filename>/etc/rc.conf</filename>:</para> |
520 |
<filename>/etc/rc.conf</filename>:</para> |
528 |
|
521 |
|
529 |
<programlisting>devfs_system_ruleset="localrules"</programlisting> |
522 |
<programlisting>devfs_system_ruleset="localrules"</programlisting> |
530 |
|
523 |
|
531 |
<para>Next, instruct the running kernel to allow regular users |
524 |
<para>Instruct the running kernel to allow regular users |
532 |
to mount file systems. The easiest way is to add the |
525 |
to mount file systems. The easiest way is to add the |
533 |
following line to |
526 |
following line to |
534 |
<filename>/etc/sysctl.conf</filename>:</para> |
527 |
<filename>/etc/sysctl.conf</filename>:</para> |
Lines 551-557
Link Here
|
551 |
<screen>&prompt.root; <userinput>mkdir /mnt/username</userinput> |
544 |
<screen>&prompt.root; <userinput>mkdir /mnt/username</userinput> |
552 |
&prompt.root; <userinput>chown username:usergroup /mnt/username</userinput></screen> |
545 |
&prompt.root; <userinput>chown username:usergroup /mnt/username</userinput></screen> |
553 |
|
546 |
|
554 |
<para>Suppose a USB thumbdrive is plugged in, and a device |
547 |
<para>Suppose a <acronym>USB</acronym> thumbdrive is plugged in, and a device |
555 |
<filename>/dev/da0s1</filename> appears. If the device is |
548 |
<filename>/dev/da0s1</filename> appears. If the device is |
556 |
preformatted with a FAT file system, it can be mounted |
549 |
preformatted with a FAT file system, it can be mounted |
557 |
using:</para> |
550 |
using:</para> |
Lines 646-658
Link Here
|
646 |
</indexterm> |
639 |
</indexterm> |
647 |
|
640 |
|
648 |
<para>Which tool to use to burn the CD depends on whether the |
641 |
<para>Which tool to use to burn the CD depends on whether the |
649 |
CD burner is ATAPI or something else. ATAPI CD burners use |
642 |
CD burner is <acronym>ATAPI</acronym> or something else. <acronym>ATAPI</acronym> CD burners use |
650 |
<command>burncd</command> which is part of the base system. |
643 |
<command>burncd</command> which is part of the base system. |
651 |
SCSI and USB CD burners should use <command>cdrecord</command> |
644 |
<acronym>SCSI</acronym> and <acronym>USB</acronym> CD burners should use <command>cdrecord</command> |
652 |
from the <package>sysutils/cdrtools</package> port. It is |
645 |
from the <package>sysutils/cdrtools</package> port. It is |
653 |
also possible to use <command>cdrecord</command> and other |
646 |
also possible to use <command>cdrecord</command> and other |
654 |
tools for SCSI drives on ATAPI hardware with the |
647 |
tools for <acronym>SCSI</acronym> drives on <acronym>ATAPI</acronym> hardware with the |
655 |
<link linkend="atapicam">ATAPI/CAM module</link>.</para> |
648 |
<link linkend="atapicam"><acronym>ATAPI</acronym>/<acronym>CAM</acronym> module</link>.</para> |
656 |
|
649 |
|
657 |
<para>For CD burning software with a graphical user |
650 |
<para>For CD burning software with a graphical user |
658 |
interface, consider <application>X-CD-Roast</application> or |
651 |
interface, consider <application>X-CD-Roast</application> or |
Lines 661-667
Link Here
|
661 |
<package>sysutils/k3b</package> ports. |
654 |
<package>sysutils/k3b</package> ports. |
662 |
<application>X-CD-Roast</application> and |
655 |
<application>X-CD-Roast</application> and |
663 |
<application>K3b</application> require the |
656 |
<application>K3b</application> require the |
664 |
<link linkend="atapicam">ATAPI/CAM module</link> with ATAPI |
657 |
<link linkend="atapicam"><acronym>ATAPI</acronym>/<acronym>CAM</acronym> module</link> with <acronym>ATAPI</acronym> |
665 |
hardware.</para> |
658 |
hardware.</para> |
666 |
</sect2> |
659 |
</sect2> |
667 |
|
660 |
|
Lines 755-761
Link Here
|
755 |
<primary>CD-ROMs</primary> |
748 |
<primary>CD-ROMs</primary> |
756 |
<secondary>burning</secondary> |
749 |
<secondary>burning</secondary> |
757 |
</indexterm> |
750 |
</indexterm> |
758 |
<para>For an ATAPI CD burner, <command>burncd</command> can be |
751 |
<para>For an <acronym>ATAPI</acronym> CD burner, <command>burncd</command> can be |
759 |
used to burn an ISO image onto a CD. |
752 |
used to burn an ISO image onto a CD. |
760 |
<command>burncd</command> is part of the base system, |
753 |
<command>burncd</command> is part of the base system, |
761 |
installed as <filename>/usr/sbin/burncd</filename>. Usage is |
754 |
installed as <filename>/usr/sbin/burncd</filename>. Usage is |
Lines 774-780
Link Here
|
774 |
<sect2 xml:id="cdrecord"> |
767 |
<sect2 xml:id="cdrecord"> |
775 |
<title><application>cdrecord</application></title> |
768 |
<title><application>cdrecord</application></title> |
776 |
|
769 |
|
777 |
<para>For systems without an ATAPI CD burner, |
770 |
<para>For systems without an <acronym>ATAPI</acronym> CD burner, |
778 |
<command>cdrecord</command> can be used to burn CDs. |
771 |
<command>cdrecord</command> can be used to burn CDs. |
779 |
<command>cdrecord</command> is not part of the base system and |
772 |
<command>cdrecord</command> is not part of the base system and |
780 |
must be installed from either the |
773 |
must be installed from either the |
Lines 838-848
Link Here
|
838 |
|
831 |
|
839 |
<para>To duplicate an audio CD, extract the audio data from the |
832 |
<para>To duplicate an audio CD, extract the audio data from the |
840 |
CD to a series of files, then write these files to a blank CD. |
833 |
CD to a series of files, then write these files to a blank CD. |
841 |
The process is slightly different for ATAPI and SCSI |
834 |
The process is slightly different for <acronym>ATAPI</acronym> and <acronym>SCSI</acronym> |
842 |
drives.</para> |
835 |
drives.</para> |
843 |
|
836 |
|
844 |
<procedure> |
837 |
<procedure> |
845 |
<title>SCSI Drives</title> |
838 |
<title><acronym>SCSI</acronym> Drives</title> |
846 |
|
839 |
|
847 |
<step> |
840 |
<step> |
848 |
<para>Use <command>cdda2wav</command> to extract the |
841 |
<para>Use <command>cdda2wav</command> to extract the |
Lines 864-875
Link Here
|
864 |
</procedure> |
857 |
</procedure> |
865 |
|
858 |
|
866 |
<procedure> |
859 |
<procedure> |
867 |
<title>ATAPI Drives</title> |
860 |
<title><acronym>ATAPI</acronym> Drives</title> |
868 |
|
861 |
|
869 |
<note> |
862 |
<note> |
870 |
<para>With the help of the |
863 |
<para>With the help of the |
871 |
<link linkend="atapicam">ATAPI/CAM module</link>, |
864 |
<link linkend="atapicam"><acronym>ATAPI</acronym>/<acronym>CAM</acronym> module</link>, |
872 |
<command>cdda2wav</command> can also be used on ATAPI |
865 |
<command>cdda2wav</command> can also be used on <acronym>ATAPI</acronym> |
873 |
drives. This tool is usually a better choice for most of |
866 |
drives. This tool is usually a better choice for most of |
874 |
users, as it supports jitter correction and endianness, |
867 |
users, as it supports jitter correction and endianness, |
875 |
than the method proposed below.</para> |
868 |
than the method proposed below.</para> |
Lines 876-882
Link Here
|
876 |
</note> |
869 |
</note> |
877 |
|
870 |
|
878 |
<step> |
871 |
<step> |
879 |
<para>The ATAPI CD driver makes each track available as |
872 |
<para>The <acronym>ATAPI</acronym> CD driver makes each track available as |
880 |
<filename>/dev/acddtnn</filename>, |
873 |
<filename>/dev/acddtnn</filename>, |
881 |
where <replaceable>d</replaceable> is the drive number, |
874 |
where <replaceable>d</replaceable> is the drive number, |
882 |
and <replaceable>nn</replaceable> is the track number |
875 |
and <replaceable>nn</replaceable> is the track number |
Lines 941-947
Link Here
|
941 |
|
934 |
|
942 |
<para>will generate an error about <errorname>Incorrect super |
935 |
<para>will generate an error about <errorname>Incorrect super |
943 |
block</errorname>, and will fail to mount the CD. The CD |
936 |
block</errorname>, and will fail to mount the CD. The CD |
944 |
does not use the <literal>UFS</literal> file system, so |
937 |
does not use the <acronym>UFS</acronym> file system, so |
945 |
attempts to mount it as such will fail. Instead, tell |
938 |
attempts to mount it as such will fail. Instead, tell |
946 |
&man.mount.8; that the file system is of type |
939 |
&man.mount.8; that the file system is of type |
947 |
<literal>ISO9660</literal> by specifying |
940 |
<literal>ISO9660</literal> by specifying |
Lines 950-956
Link Here
|
950 |
under <filename>/mnt</filename>, |
943 |
under <filename>/mnt</filename>, |
951 |
use:</para> |
944 |
use:</para> |
952 |
|
945 |
|
953 |
<screen>&prompt.root; <userinput>mount -t cd9660 /dev/cd0 /mnt</userinput></screen> |
946 |
<screen>&prompt.root; <userinput>mount -t cd9660 <replaceable>/dev/cd0</replaceable> /mnt</userinput></screen> |
954 |
|
947 |
|
955 |
<para>Replace <filename>/dev/cd0</filename> with the device |
948 |
<para>Replace <filename>/dev/cd0</filename> with the device |
956 |
name for the CD device. Also, <option>-t cd9660</option> |
949 |
name for the CD device. Also, <option>-t cd9660</option> |
Lines 989-995
Link Here
|
989 |
It can take a couple of seconds for a CD-ROM drive to realize |
982 |
It can take a couple of seconds for a CD-ROM drive to realize |
990 |
that a media is present, so be patient.</para> |
983 |
that a media is present, so be patient.</para> |
991 |
|
984 |
|
992 |
<para>Sometimes, a SCSI CD-ROM may be missed because it did not |
985 |
<para>Sometimes, a <acronym>SCSI</acronym> CD-ROM may be missed because it did not |
993 |
have enough time to answer the bus reset. To resolve this, |
986 |
have enough time to answer the bus reset. To resolve this, |
994 |
add the following option to the kernel configuration and |
987 |
add the following option to the kernel configuration and |
995 |
<link linkend="kernelconfig-building">rebuild the |
988 |
<link linkend="kernelconfig-building">rebuild the |
Lines 997-1003
Link Here
|
997 |
|
990 |
|
998 |
<programlisting>options SCSI_DELAY=15000</programlisting> |
991 |
<programlisting>options SCSI_DELAY=15000</programlisting> |
999 |
|
992 |
|
1000 |
<para>This tells the SCSI bus to pause 15 seconds during boot, |
993 |
<para>This tells the <acronym>SCSI</acronym> bus to pause 15 seconds during boot, |
1001 |
to give the CD-ROM drive every possible chance to answer the |
994 |
to give the CD-ROM drive every possible chance to answer the |
1002 |
bus reset.</para> |
995 |
bus reset.</para> |
1003 |
</sect2> |
996 |
</sect2> |
Lines 1026-1032
Link Here
|
1026 |
|
1019 |
|
1027 |
<sect2 xml:id="atapicam"> |
1020 |
<sect2 xml:id="atapicam"> |
1028 |
<info> |
1021 |
<info> |
1029 |
<title>Using the ATAPI/CAM Driver</title> |
1022 |
<title>Using the <acronym>ATAPI</acronym>/<acronym>CAM</acronym> Driver</title> |
1030 |
|
1023 |
|
1031 |
<authorgroup> |
1024 |
<authorgroup> |
1032 |
<author> |
1025 |
<author> |
Lines 1041-1051
Link Here
|
1041 |
|
1034 |
|
1042 |
<indexterm> |
1035 |
<indexterm> |
1043 |
<primary>CD burner</primary> |
1036 |
<primary>CD burner</primary> |
1044 |
<secondary>ATAPI/CAM driver</secondary> |
1037 |
<secondary><acronym>ATAPI</acronym>/<acronym>CAM</acronym> driver</secondary> |
1045 |
</indexterm> |
1038 |
</indexterm> |
1046 |
|
1039 |
|
1047 |
<para>This driver allows ATAPI devices, such as CD/DVD drives, |
1040 |
<para>This driver allows <acronym>ATAPI</acronym> devices, such as CD/DVD drives, |
1048 |
to be accessed through the SCSI subsystem, and so allows the |
1041 |
to be accessed through the <acronym>SCSI</acronym> subsystem, and so allows the |
1049 |
use of applications like <package>sysutils/cdrdao</package> or |
1042 |
use of applications like <package>sysutils/cdrdao</package> or |
1050 |
&man.cdrecord.1;.</para> |
1043 |
&man.cdrecord.1;.</para> |
1051 |
|
1044 |
|
Lines 1092-1108
Link Here
|
1092 |
<screen>&prompt.root; <userinput>mount -t cd9660 /dev/cd0 /mnt</userinput></screen> |
1085 |
<screen>&prompt.root; <userinput>mount -t cd9660 /dev/cd0 /mnt</userinput></screen> |
1093 |
|
1086 |
|
1094 |
<para>As <systemitem class="username">root</systemitem>, run the |
1087 |
<para>As <systemitem class="username">root</systemitem>, run the |
1095 |
following command to get the SCSI address of the |
1088 |
following command to get the <acronym>SCSI</acronym> address of the |
1096 |
burner:</para> |
1089 |
burner:</para> |
1097 |
|
1090 |
|
1098 |
<screen>&prompt.root; <userinput>camcontrol devlist</userinput> |
1091 |
<screen>&prompt.root; <userinput>camcontrol devlist</userinput> |
1099 |
<MATSHITA CDRW/DVD UJDA740 1.00> at scbus1 target 0 lun 0 (pass0,cd0)</screen> |
1092 |
<MATSHITA CDRW/DVD UJDA740 1.00> at scbus1 target 0 lun 0 (pass0,cd0)</screen> |
1100 |
|
1093 |
|
1101 |
<para>In this example, <literal>1,0,0</literal> is the SCSI |
1094 |
<para>In this example, <literal>1,0,0</literal> is the <acronym>SCSI</acronym> |
1102 |
address to use with &man.cdrecord.1; and other SCSI |
1095 |
address to use with &man.cdrecord.1; and other <acronym>SCSI</acronym> |
1103 |
applications.</para> |
1096 |
applications.</para> |
1104 |
|
1097 |
|
1105 |
<para>For more information about ATAPI/CAM and SCSI system, |
1098 |
<para>For more information about <acronym>ATAPI</acronym>/<acronym>CAM</acronym> and <acronym>SCSI</acronym> system, |
1106 |
refer to &man.atapicam.4; and &man.cam.4;.</para> |
1099 |
refer to &man.atapicam.4; and &man.cam.4;.</para> |
1107 |
</sect2> |
1100 |
</sect2> |
1108 |
</sect1> |
1101 |
</sect1> |
Lines 1205-1218
Link Here
|
1205 |
<package>sysutils/dvd+rw-tools</package> utilities which |
1198 |
<package>sysutils/dvd+rw-tools</package> utilities which |
1206 |
support all DVD media types.</para> |
1199 |
support all DVD media types.</para> |
1207 |
|
1200 |
|
1208 |
<para>These tools use the SCSI subsystem to access the devices, |
1201 |
<para>These tools use the <acronym>SCSI</acronym> subsystem to access the devices, |
1209 |
therefore <link linkend="atapicam">ATAPI/CAM support</link> |
1202 |
therefore <link linkend="atapicam"><acronym>ATAPI</acronym>/<acronym>CAM</acronym> support</link> |
1210 |
must be loaded or statically compiled into the kernel. This |
1203 |
must be loaded or statically compiled into the kernel. This |
1211 |
support is not needed if the burner uses the USB interface. |
1204 |
support is not needed if the burner uses the <acronym>USB</acronym> interface. |
1212 |
Refer to <xref linkend="usb-disks"/> for more details |
1205 |
Refer to <xref linkend="usb-disks"/> for more details |
1213 |
on USB device configuration.</para> |
1206 |
on <acronym>USB</acronym> device configuration.</para> |
1214 |
|
1207 |
|
1215 |
<para>DMA access must also be enabled for ATAPI devices, by |
1208 |
<para>DMA access must also be enabled for <acronym>ATAPI</acronym> devices, by |
1216 |
adding the following line to |
1209 |
adding the following line to |
1217 |
<filename>/boot/loader.conf</filename>:</para> |
1210 |
<filename>/boot/loader.conf</filename>:</para> |
1218 |
|
1211 |
|
Lines 1516-1523
Link Here
|
1516 |
<sect3> |
1509 |
<sect3> |
1517 |
<title>Configuration</title> |
1510 |
<title>Configuration</title> |
1518 |
|
1511 |
|
1519 |
<para>DVD-RAM writers can use either a SCSI or ATAPI |
1512 |
<para>DVD-RAM writers can use either a <acronym>SCSI</acronym> or <acronym>ATAPI</acronym> |
1520 |
interface. For ATAPI devices, DMA access has to be |
1513 |
interface. For <acronym>ATAPI</acronym> devices, DMA access has to be |
1521 |
enabled by adding the following line to |
1514 |
enabled by adding the following line to |
1522 |
<filename>/boot/loader.conf</filename>:</para> |
1515 |
<filename>/boot/loader.conf</filename>:</para> |
1523 |
|
1516 |
|
Lines 1613-1619
Link Here
|
1613 |
|
1606 |
|
1614 |
<step> |
1607 |
<step> |
1615 |
<para>The floppy is now ready to be high-level formatted with |
1608 |
<para>The floppy is now ready to be high-level formatted with |
1616 |
a file system. The floppy's file system can be either UFS |
1609 |
a file system. The floppy's file system can be either <acronym>UFS</acronym> |
1617 |
or FAT, where FAT is generally a better choice for |
1610 |
or FAT, where FAT is generally a better choice for |
1618 |
floppies.</para> |
1611 |
floppies.</para> |
1619 |
|
1612 |
|
Lines 1638-1645
Link Here
|
1638 |
to be used in a modern system. Modern backup systems tend to |
1631 |
to be used in a modern system. Modern backup systems tend to |
1639 |
use off site combined with local removable disk drive |
1632 |
use off site combined with local removable disk drive |
1640 |
technologies. Still, &os; will support any tape drive that |
1633 |
technologies. Still, &os; will support any tape drive that |
1641 |
uses SCSI, such as LTO and older devices such as DAT. There is |
1634 |
uses <acronym>SCSI</acronym>, such as LTO and older devices such as DAT. There is |
1642 |
limited support for SATA and USB tape drives.</para> |
1635 |
limited support for <acronym>SATA</acronym> and <acronym>USB</acronym> tape drives.</para> |
1643 |
|
1636 |
|
1644 |
<sect2 xml:id="tapes-sa0"> |
1637 |
<sect2 xml:id="tapes-sa0"> |
1645 |
<title>Serial Access with &man.sa.4;</title> |
1638 |
<title>Serial Access with &man.sa.4;</title> |
Lines 1777-1783
Link Here
|
1777 |
<para>Typically, a mix of backup techniques is used. For |
1770 |
<para>Typically, a mix of backup techniques is used. For |
1778 |
example, one could create a schedule to automate a weekly, full |
1771 |
example, one could create a schedule to automate a weekly, full |
1779 |
system backup that is stored off-site and to supplement this |
1772 |
system backup that is stored off-site and to supplement this |
1780 |
backup with hourly ZFS snapshots. In addition, one could make a |
1773 |
backup with hourly <acronym>ZFS</acronym> snapshots. In addition, one could make a |
1781 |
manual backup of individual directories or files before making |
1774 |
manual backup of individual directories or files before making |
1782 |
file edits or deletions.</para> |
1775 |
file edits or deletions.</para> |
1783 |
|
1776 |
|
Lines 1857-1863
Link Here
|
1857 |
</example> |
1850 |
</example> |
1858 |
|
1851 |
|
1859 |
<para>This example sets <envar>RSH</envar> in order to write the |
1852 |
<para>This example sets <envar>RSH</envar> in order to write the |
1860 |
the backup to a tape drive on a remote system over a |
1853 |
backup to a tape drive on a remote system over a |
1861 |
<acronym>SSH</acronym> connection:</para> |
1854 |
<acronym>SSH</acronym> connection:</para> |
1862 |
|
1855 |
|
1863 |
<example> |
1856 |
<example> |
Lines 1896-1902
Link Here
|
1896 |
same directory that is being backed up.</para> |
1889 |
same directory that is being backed up.</para> |
1897 |
|
1890 |
|
1898 |
<example> |
1891 |
<example> |
1899 |
<title>Backing Up the Current Directory With |
1892 |
<title>Backing Up the Current Directory with |
1900 |
<command>tar</command></title> |
1893 |
<command>tar</command></title> |
1901 |
|
1894 |
|
1902 |
<screen>&prompt.root; <userinput>tar czvf /tmp/mybackup.tgz . </userinput></screen> |
1895 |
<screen>&prompt.root; <userinput>tar czvf /tmp/mybackup.tgz . </userinput></screen> |
Lines 1910-1916
Link Here
|
1910 |
backup to restore.</para> |
1903 |
backup to restore.</para> |
1911 |
|
1904 |
|
1912 |
<example> |
1905 |
<example> |
1913 |
<title>Restoring Up the Current Directory With |
1906 |
<title>Restoring Up the Current Directory with |
1914 |
<command>tar</command></title> |
1907 |
<command>tar</command></title> |
1915 |
|
1908 |
|
1916 |
<screen>&prompt.root; <userinput>tar xzvf /tmp/mybackup.tgz</userinput></screen> |
1909 |
<screen>&prompt.root; <userinput>tar xzvf /tmp/mybackup.tgz</userinput></screen> |
Lines 1968-1974
Link Here
|
1968 |
examples would be:</para> |
1961 |
examples would be:</para> |
1969 |
|
1962 |
|
1970 |
<example> |
1963 |
<example> |
1971 |
<title>Backing Up the Current Directory With |
1964 |
<title>Backing Up the Current Directory with |
1972 |
<command>pax</command></title> |
1965 |
<command>pax</command></title> |
1973 |
|
1966 |
|
1974 |
<screen>&prompt.root; <userinput>pax -wf /tmp/mybackup.pax .</userinput></screen> |
1967 |
<screen>&prompt.root; <userinput>pax -wf /tmp/mybackup.pax .</userinput></screen> |
Lines 2158-2164
Link Here
|
2158 |
<para>While &man.mdconfig.8; is useful, it takes several |
2151 |
<para>While &man.mdconfig.8; is useful, it takes several |
2159 |
command lines to create a file-backed file system. &os; also |
2152 |
command lines to create a file-backed file system. &os; also |
2160 |
comes with &man.mdmfs.8; which automatically configures a |
2153 |
comes with &man.mdmfs.8; which automatically configures a |
2161 |
&man.md.4; disk using &man.mdconfig.8;, puts a UFS file system |
2154 |
&man.md.4; disk using &man.mdconfig.8;, puts a <acronym>UFS</acronym> file system |
2162 |
on it using &man.newfs.8;, and mounts it using &man.mount.8;. |
2155 |
on it using &man.newfs.8;, and mounts it using &man.mount.8;. |
2163 |
For example, to create and mount the same file system image as |
2156 |
For example, to create and mount the same file system image as |
2164 |
above, type the following:</para> |
2157 |
above, type the following:</para> |
Lines 2273-2283
Link Here
|
2273 |
<secondary>snapshots</secondary> |
2266 |
<secondary>snapshots</secondary> |
2274 |
</indexterm> |
2267 |
</indexterm> |
2275 |
|
2268 |
|
2276 |
<para>&os; offers a feature in conjunction with |
2269 |
<para>&os; offers a feature in conjunction with <acronym>UFS</acronym> |
2277 |
<link linkend="soft-updates">Soft Updates</link>: file system |
2270 |
<link linkend="soft-updates">Soft Updates</link>: file system |
2278 |
snapshots.</para> |
2271 |
snapshots.</para> |
2279 |
|
2272 |
|
2280 |
<para>UFS snapshots allow a user to create images of specified |
2273 |
<para><acronym>UFS</acronym> snapshots allow a user to create images of specified |
2281 |
file systems, and treat them as a file. Snapshot files must be |
2274 |
file systems, and treat them as a file. Snapshot files must be |
2282 |
created in the file system that the action is performed on, and |
2275 |
created in the file system that the action is performed on, and |
2283 |
a user may create no more than 20 snapshots per file system. |
2276 |
a user may create no more than 20 snapshots per file system. |
Lines 2285-2292
Link Here
|
2285 |
persistent across unmount and remount operations along with |
2278 |
persistent across unmount and remount operations along with |
2286 |
system reboots. When a snapshot is no longer required, it can |
2279 |
system reboots. When a snapshot is no longer required, it can |
2287 |
be removed using &man.rm.1;. While snapshots may be removed in |
2280 |
be removed using &man.rm.1;. While snapshots may be removed in |
2288 |
any order, all the used space may not be acquired because |
2281 |
any order, all the used space may not be reclaimed because |
2289 |
another snapshot will possibly claim some of the released |
2282 |
another snapshot will possibly still be using some of the |
2290 |
blocks.</para> |
2283 |
blocks.</para> |
2291 |
|
2284 |
|
2292 |
<para>The un-alterable <option>snapshot</option> file flag is set |
2285 |
<para>The un-alterable <option>snapshot</option> file flag is set |
Lines 2656-2662
Link Here
|
2656 |
systems. No cleartext ever touches the hard drive's |
2649 |
systems. No cleartext ever touches the hard drive's |
2657 |
platter.</para> |
2650 |
platter.</para> |
2658 |
|
2651 |
|
2659 |
<sect2> |
2652 |
<sect2 xml:id="disks-encrypting-gbde"> |
2660 |
<title>Disk Encryption with |
2653 |
<title>Disk Encryption with |
2661 |
<application>gbde</application></title> |
2654 |
<application>gbde</application></title> |
2662 |
|
2655 |
|
Lines 2702-2715
Link Here
|
2702 |
<para>Install the new drive to the system as explained in |
2695 |
<para>Install the new drive to the system as explained in |
2703 |
<xref linkend="disks-adding"/>. For the purposes |
2696 |
<xref linkend="disks-adding"/>. For the purposes |
2704 |
of this example, a new hard drive partition has been |
2697 |
of this example, a new hard drive partition has been |
2705 |
added as <filename>/dev/ad4s1c</filename> and |
2698 |
added as <filename>/dev/ada1p1</filename> and |
2706 |
<filename>/dev/ad0s1*</filename> |
2699 |
<filename>/dev/ada0*</filename> |
2707 |
represents the existing standard &os; partitions.</para> |
2700 |
represents the existing standard &os; partitions.</para> |
2708 |
|
2701 |
|
2709 |
<screen>&prompt.root; <userinput>ls /dev/ad*</userinput> |
2702 |
<screen>&prompt.root; <userinput>ls /dev/ada*</userinput> |
2710 |
/dev/ad0 /dev/ad0s1b /dev/ad0s1e /dev/ad4s1 |
2703 |
/dev/ada0 /dev/ada0p2 /dev/ada1 |
2711 |
/dev/ad0s1 /dev/ad0s1c /dev/ad0s1f /dev/ad4s1c |
2704 |
/dev/ada0p1 /dev/ada0p3 /dev/ada1p1</screen> |
2712 |
/dev/ad0s1a /dev/ad0s1d /dev/ad4</screen> |
|
|
2713 |
</step> |
2705 |
</step> |
2714 |
|
2706 |
|
2715 |
<step> |
2707 |
<step> |
Lines 2737-2743
Link Here
|
2737 |
initialized before it can be used. This initialization |
2729 |
initialized before it can be used. This initialization |
2738 |
needs to be performed only once:</para> |
2730 |
needs to be performed only once:</para> |
2739 |
|
2731 |
|
2740 |
<screen>&prompt.root; <userinput>gbde init /dev/ad4s1c -i -L /etc/gbde/ad4s1c.lock</userinput></screen> |
2732 |
<screen>&prompt.root; <userinput>gbde init /dev/ada1p1 -i -L /etc/gbde/ada1p1.lock</userinput></screen> |
2741 |
|
2733 |
|
2742 |
<para>&man.gbde.8; will open the default editor, in order |
2734 |
<para>&man.gbde.8; will open the default editor, in order |
2743 |
to set various configuration options in a template. For |
2735 |
to set various configuration options in a template. For |
Lines 2767-2773
Link Here
|
2767 |
<para><command>gbde init</command>creates a lock file for |
2759 |
<para><command>gbde init</command>creates a lock file for |
2768 |
the <application>gbde</application> partition. In this |
2760 |
the <application>gbde</application> partition. In this |
2769 |
example, it is stored as |
2761 |
example, it is stored as |
2770 |
<filename>/etc/gbde/ad4s1c.lock</filename>. |
2762 |
<filename>/etc/gbde/ada1p1.lock</filename>. |
2771 |
<application>gbde</application> lock files must end in |
2763 |
<application>gbde</application> lock files must end in |
2772 |
<quote>.lock</quote> in order to be correctly detected |
2764 |
<quote>.lock</quote> in order to be correctly detected |
2773 |
by the <filename>/etc/rc.d/gbde</filename> start up |
2765 |
by the <filename>/etc/rc.d/gbde</filename> start up |
Lines 2791-2797
Link Here
|
2791 |
<title>Attach the Encrypted Partition to the |
2783 |
<title>Attach the Encrypted Partition to the |
2792 |
Kernel</title> |
2784 |
Kernel</title> |
2793 |
|
2785 |
|
2794 |
<screen>&prompt.root; <userinput>gbde attach /dev/ad4s1c -l /etc/gbde/ad4s1c.lock</userinput></screen> |
2786 |
<screen>&prompt.root; <userinput>gbde attach /dev/ada1p1 -l /etc/gbde/ada1p1.lock</userinput></screen> |
2795 |
|
2787 |
|
2796 |
<para>This command will prompt to input the passphrase |
2788 |
<para>This command will prompt to input the passphrase |
2797 |
that was selected during the initialization of the |
2789 |
that was selected during the initialization of the |
Lines 2800-2809
Link Here
|
2800 |
<filename>/dev</filename> as |
2792 |
<filename>/dev</filename> as |
2801 |
<filename>/dev/device_name.bde</filename>:</para> |
2793 |
<filename>/dev/device_name.bde</filename>:</para> |
2802 |
|
2794 |
|
2803 |
<screen>&prompt.root; <userinput>ls /dev/ad*</userinput> |
2795 |
<screen>&prompt.root; <userinput>ls /dev/ada*</userinput> |
2804 |
/dev/ad0 /dev/ad0s1b /dev/ad0s1e /dev/ad4s1 |
2796 |
/dev/ada0 /dev/ada0p2 /dev/ada1 /dev/ada1p1.bde |
2805 |
/dev/ad0s1 /dev/ad0s1c /dev/ad0s1f /dev/ad4s1c |
2797 |
/dev/ada0p1 /dev/ada0p3 /dev/ada1p1</screen> |
2806 |
/dev/ad0s1a /dev/ad0s1d /dev/ad4 /dev/ad4s1c.bde</screen> |
|
|
2807 |
</step> |
2798 |
</step> |
2808 |
|
2799 |
|
2809 |
<step> |
2800 |
<step> |
Lines 2815-2821
Link Here
|
2815 |
&man.newfs.8;. This example creates a UFS2 file |
2806 |
&man.newfs.8;. This example creates a UFS2 file |
2816 |
system with soft updates enabled.</para> |
2807 |
system with soft updates enabled.</para> |
2817 |
|
2808 |
|
2818 |
<screen>&prompt.root; <userinput>newfs -U /dev/ad4s1c.bde</userinput></screen> |
2809 |
<screen>&prompt.root; <userinput>newfs -U /dev/ada1p1.bde</userinput></screen> |
2819 |
|
2810 |
|
2820 |
<note> |
2811 |
<note> |
2821 |
<para>&man.newfs.8; must be performed on an attached |
2812 |
<para>&man.newfs.8; must be performed on an attached |
Lines 2836-2842
Link Here
|
2836 |
|
2827 |
|
2837 |
<para>Mount the encrypted file system:</para> |
2828 |
<para>Mount the encrypted file system:</para> |
2838 |
|
2829 |
|
2839 |
<screen>&prompt.root; <userinput>mount /dev/ad4s1c.bde /private</userinput></screen> |
2830 |
<screen>&prompt.root; <userinput>mount /dev/ada1p1.bde /private</userinput></screen> |
2840 |
</step> |
2831 |
</step> |
2841 |
|
2832 |
|
2842 |
<step> |
2833 |
<step> |
Lines 2848-2859
Link Here
|
2848 |
|
2839 |
|
2849 |
<screen>&prompt.user; <userinput>df -H</userinput> |
2840 |
<screen>&prompt.user; <userinput>df -H</userinput> |
2850 |
Filesystem Size Used Avail Capacity Mounted on |
2841 |
Filesystem Size Used Avail Capacity Mounted on |
2851 |
/dev/ad0s1a 1037M 72M 883M 8% / |
2842 |
/dev/ada0p2 1037M 72M 883M 8% / |
2852 |
/devfs 1.0K 1.0K 0B 100% /dev |
2843 |
/devfs 1.0K 1.0K 0B 100% /dev |
2853 |
/dev/ad0s1f 8.1G 55K 7.5G 0% /home |
2844 |
/dev/ada1p1.bde 150G 4.1K 138G 0% /private</screen> |
2854 |
/dev/ad0s1e 1037M 1.1M 953M 0% /tmp |
|
|
2855 |
/dev/ad0s1d 6.1G 1.9G 3.7G 35% /usr |
2856 |
/dev/ad4s1c.bde 150G 4.1K 138G 0% /private</screen> |
2857 |
</step> |
2845 |
</step> |
2858 |
</procedure> |
2846 |
</procedure> |
2859 |
</sect3> |
2847 |
</sect3> |
Lines 2872-2878
Link Here
|
2872 |
<title>Attach the <command>gbde</command> Partition to the |
2860 |
<title>Attach the <command>gbde</command> Partition to the |
2873 |
Kernel</title> |
2861 |
Kernel</title> |
2874 |
|
2862 |
|
2875 |
<screen>&prompt.root; <userinput>gbde attach /dev/ad4s1c -l /etc/gbde/ad4s1c.lock</userinput></screen> |
2863 |
<screen>&prompt.root; <userinput>gbde attach /dev/ada1p1 -l /etc/gbde/ada1p1.lock</userinput></screen> |
2876 |
|
2864 |
|
2877 |
<para>This command will prompt for the passphrase that was |
2865 |
<para>This command will prompt for the passphrase that was |
2878 |
selected during initialization of the encrypted |
2866 |
selected during initialization of the encrypted |
Lines 2887-2899
Link Here
|
2887 |
the file systems must be checked for errors by running |
2875 |
the file systems must be checked for errors by running |
2888 |
&man.fsck.8; manually before mounting:</para> |
2876 |
&man.fsck.8; manually before mounting:</para> |
2889 |
|
2877 |
|
2890 |
<screen>&prompt.root; <userinput>fsck -p -t ffs /dev/ad4s1c.bde</userinput></screen> |
2878 |
<screen>&prompt.root; <userinput>fsck -p -t ffs /dev/ada1p1.bde</userinput></screen> |
2891 |
</step> |
2879 |
</step> |
2892 |
|
2880 |
|
2893 |
<step> |
2881 |
<step> |
2894 |
<title>Mount the Encrypted File System</title> |
2882 |
<title>Mount the Encrypted File System</title> |
2895 |
|
2883 |
|
2896 |
<screen>&prompt.root; <userinput>mount /dev/ad4s1c.bde /private</userinput></screen> |
2884 |
<screen>&prompt.root; <userinput>mount /dev/ada1p1.bde /private</userinput></screen> |
2897 |
|
2885 |
|
2898 |
<para>The encrypted file system is now available for |
2886 |
<para>The encrypted file system is now available for |
2899 |
use.</para> |
2887 |
use.</para> |
Lines 2915-2921
Link Here
|
2915 |
&man.rc.conf.5;:</para> |
2903 |
&man.rc.conf.5;:</para> |
2916 |
|
2904 |
|
2917 |
<programlisting>gbde_autoattach_all="YES" |
2905 |
<programlisting>gbde_autoattach_all="YES" |
2918 |
gbde_devices="ad4s1c" |
2906 |
gbde_devices="ada1p1" |
2919 |
gbde_lockdir="/etc/gbde"</programlisting> |
2907 |
gbde_lockdir="/etc/gbde"</programlisting> |
2920 |
|
2908 |
|
2921 |
<para>This requires that the |
2909 |
<para>This requires that the |
Lines 2950-2961
Link Here
|
2950 |
probing for devices. To detach the encrypted device used in |
2938 |
probing for devices. To detach the encrypted device used in |
2951 |
the example, use the following command:</para> |
2939 |
the example, use the following command:</para> |
2952 |
|
2940 |
|
2953 |
<screen>&prompt.root; <userinput>gbde detach /dev/ad4s1c</userinput></screen> |
2941 |
<screen>&prompt.root; <userinput>gbde detach /dev/ada1p1</userinput></screen> |
2954 |
|
2942 |
|
2955 |
</sect3> |
2943 |
</sect3> |
2956 |
</sect2> |
2944 |
</sect2> |
2957 |
|
2945 |
|
2958 |
<sect2> |
2946 |
<sect2 xml:id="disks-encrypting-geli"> |
2959 |
<info> |
2947 |
<info> |
2960 |
<title>Disk Encryption with <command>geli</command></title> |
2948 |
<title>Disk Encryption with <command>geli</command></title> |
2961 |
|
2949 |
|
Lines 3116-3126
Link Here
|
3116 |
|
3104 |
|
3117 |
<screen>&prompt.root; <userinput>df -H</userinput> |
3105 |
<screen>&prompt.root; <userinput>df -H</userinput> |
3118 |
Filesystem Size Used Avail Capacity Mounted on |
3106 |
Filesystem Size Used Avail Capacity Mounted on |
3119 |
/dev/ad0s1a 248M 89M 139M 38% / |
3107 |
/dev/ada0p2 248M 89M 139M 38% / |
3120 |
/devfs 1.0K 1.0K 0B 100% /dev |
3108 |
/devfs 1.0K 1.0K 0B 100% /dev |
3121 |
/dev/ad0s1f 7.7G 2.3G 4.9G 32% /usr |
|
|
3122 |
/dev/ad0s1d 989M 1.5M 909M 0% /tmp |
3123 |
/dev/ad0s1e 3.9G 1.3G 2.3G 35% /var |
3124 |
/dev/da2.eli 150G 4.1K 138G 0% /private</screen> |
3109 |
/dev/da2.eli 150G 4.1K 138G 0% /private</screen> |
3125 |
</step> |
3110 |
</step> |
3126 |
|
3111 |
|
Lines 3198-3204
Link Here
|
3198 |
passwords stay in physical memory, these passwords will not be |
3183 |
passwords stay in physical memory, these passwords will not be |
3199 |
written to disk and be cleared after a reboot. If &os; starts |
3184 |
written to disk and be cleared after a reboot. If &os; starts |
3200 |
swapping out memory pages to free space for other applications, |
3185 |
swapping out memory pages to free space for other applications, |
3201 |
the passwords may be written to the disk platters unencrypted. |
3186 |
the passwords may be written to disk unencrypted. |
3202 |
Encrypting swap space can be a solution for this |
3187 |
Encrypting swap space can be a solution for this |
3203 |
scenario.</para> |
3188 |
scenario.</para> |
3204 |
|
3189 |
|
Lines 3209-3215
Link Here
|
3209 |
|
3194 |
|
3210 |
<note> |
3195 |
<note> |
3211 |
<para>For the remainder of this section, |
3196 |
<para>For the remainder of this section, |
3212 |
<filename>ad0s1b</filename> will be the swap |
3197 |
<filename>ada0p3</filename> will be the swap |
3213 |
partition.</para> |
3198 |
partition.</para> |
3214 |
</note> |
3199 |
</note> |
3215 |
|
3200 |
|
Lines 3218-3224
Link Here
|
3218 |
overwrite the current swap partition with random garbage, |
3203 |
overwrite the current swap partition with random garbage, |
3219 |
execute the following command:</para> |
3204 |
execute the following command:</para> |
3220 |
|
3205 |
|
3221 |
<screen>&prompt.root; <userinput>dd if=/dev/random of=/dev/ad0s1b bs=1m</userinput></screen> |
3206 |
<screen>&prompt.root; <userinput>dd if=/dev/random of=/dev/ada0p3 bs=1m</userinput></screen> |
3222 |
|
3207 |
|
3223 |
<sect2> |
3208 |
<sect2> |
3224 |
<title>Swap Encryption with &man.gbde.8;</title> |
3209 |
<title>Swap Encryption with &man.gbde.8;</title> |
Lines 3228-3234
Link Here
|
3228 |
line:</para> |
3213 |
line:</para> |
3229 |
|
3214 |
|
3230 |
<programlisting># Device Mountpoint FStype Options Dump Pass# |
3215 |
<programlisting># Device Mountpoint FStype Options Dump Pass# |
3231 |
/dev/ad0s1b.bde none swap sw 0 0</programlisting> |
3216 |
/dev/ada0p3.bde none swap sw 0 0</programlisting> |
3232 |
</sect2> |
3217 |
</sect2> |
3233 |
|
3218 |
|
3234 |
<sect2> |
3219 |
<sect2> |
Lines 3241-3251
Link Here
|
3241 |
line:</para> |
3226 |
line:</para> |
3242 |
|
3227 |
|
3243 |
<programlisting># Device Mountpoint FStype Options Dump Pass# |
3228 |
<programlisting># Device Mountpoint FStype Options Dump Pass# |
3244 |
/dev/ad0s1b.eli none swap sw 0 0</programlisting> |
3229 |
/dev/ada0p3.eli none swap sw 0 0</programlisting> |
3245 |
|
3230 |
|
3246 |
<para>&man.geli.8; uses the <acronym>AES</acronym> algorithm |
3231 |
<para>&man.geli.8; uses the <acronym>AES</acronym> algorithm |
3247 |
with a key length of 128 bit by default. These defaults can |
3232 |
with a key length of 128 bit by default. These defaults can |
3248 |
be altered by using <literal>geli_swap_flags</literal> in |
3233 |
be altered by using <varname>geli_swap_flags</varname> in |
3249 |
<filename>/etc/rc.conf</filename>. The following line tells |
3234 |
<filename>/etc/rc.conf</filename>. The following line tells |
3250 |
the <filename>encswap</filename> rc.d script to create |
3235 |
the <filename>encswap</filename> rc.d script to create |
3251 |
&man.geli.8; swap partitions using the Blowfish algorithm with |
3236 |
&man.geli.8; swap partitions using the Blowfish algorithm with |
Lines 3270-3282
Link Here
|
3270 |
|
3255 |
|
3271 |
<screen>&prompt.user; <userinput>swapinfo</userinput> |
3256 |
<screen>&prompt.user; <userinput>swapinfo</userinput> |
3272 |
Device 1K-blocks Used Avail Capacity |
3257 |
Device 1K-blocks Used Avail Capacity |
3273 |
/dev/ad0s1b.bde 542720 0 542720 0%</screen> |
3258 |
/dev/ada0p3.bde 542720 0 542720 0%</screen> |
3274 |
|
3259 |
|
3275 |
<para>If &man.geli.8; is being used:</para> |
3260 |
<para>If &man.geli.8; is being used:</para> |
3276 |
|
3261 |
|
3277 |
<screen>&prompt.user; <userinput>swapinfo</userinput> |
3262 |
<screen>&prompt.user; <userinput>swapinfo</userinput> |
3278 |
Device 1K-blocks Used Avail Capacity |
3263 |
Device 1K-blocks Used Avail Capacity |
3279 |
/dev/ad0s1b.eli 542720 0 542720 0%</screen> |
3264 |
/dev/ada0p3.eli 542720 0 542720 0%</screen> |
3280 |
</sect2> |
3265 |
</sect2> |
3281 |
</sect1> |
3266 |
</sect1> |
3282 |
|
3267 |
|
Lines 3897-3905
Link Here
|
3897 |
</caution> |
3882 |
</caution> |
3898 |
|
3883 |
|
3899 |
<tip> |
3884 |
<tip> |
3900 |
<para>For this example, a standard UFS file system was used. |
3885 |
<para>For this example, a standard <acronym>UFS</acronym> file system was used. |
3901 |
To reduce the time needed for recovery, a journal-enabled |
3886 |
To reduce the time needed for recovery, a journal-enabled |
3902 |
UFS or ZFS file system can be used instead.</para> |
3887 |
<acronym>UFS</acronym> or <acronym>ZFS</acronym> file system can be used instead.</para> |
3903 |
</tip> |
3888 |
</tip> |
3904 |
|
3889 |
|
3905 |
<para>More detailed information with additional examples can |
3890 |
<para>More detailed information with additional examples can |