diff --git a/documentation/content/en/books/handbook/disks/_index.adoc b/documentation/content/en/books/handbook/disks/_index.adoc --- a/documentation/content/en/books/handbook/disks/_index.adoc +++ b/documentation/content/en/books/handbook/disks/_index.adoc @@ -69,7 +69,7 @@ Before reading this chapter, you should: -* Know how to crossref:kernelconfig[kernelconfig,configure and install a new FreeBSD kernel]. +* Know how to <>. [[disks-adding]] == Adding Disks @@ -354,7 +354,7 @@ .... If the device has not been formatted, refer to <> for instructions on how to format and create partitions on the USB drive. -If the drive comes with a file system, it can be mounted by `root` using the instructions in crossref:basics[mount-unmount,“Mounting and Unmounting File Systems”]. +If the drive comes with a file system, it can be mounted by `root` using the instructions in <>. [WARNING] ==== @@ -742,7 +742,7 @@ Sometimes, a SCSICD drive may be missed because it did not have enough time to answer the bus reset. To resolve this, a custom kernel can be created which increases the default SCSI delay. -Add the following option to the custom kernel configuration file and rebuild the kernel using the instructions in crossref:kernelconfig[kernelconfig-building,“Building and Installing a Custom Kernel”]: +Add the following option to the custom kernel configuration file and rebuild the kernel using the instructions in <>: [.programlisting] .... @@ -1164,7 +1164,7 @@ # sysrc kld_list+=fusefs .... -. Install the actual NTFS file system from packages as in the example (see crossref:ports[pkgng-intro,Using pkg for Binary Package Management]) or from ports (see crossref:ports[ports-using,Using the Ports Collection]): +. Install the NTFS file system driver as described in <>: + [source,shell] .... @@ -1284,7 +1284,7 @@ [TIP] ==== -Systems using the crossref:zfs[,Z file system (ZFS)] can make use of man:zfs[8] for creating snapshots, as well as crossref:zfs[zfs-zfs-send,sending and receiving] them to/from remote systems. +Systems using the <> can make use of man:zfs[8] for creating snapshots, as well as <> them to/from remote systems. ==== === Directory Backups @@ -1561,9 +1561,9 @@ [[snapshots]] == File System Snapshots -FreeBSD offers a feature in conjunction with crossref:config[soft-updates,Soft Updates]: file system snapshots. +FreeBSD offers a feature in conjunction with <>: file system snapshots. -UFS snapshots allow a user to create images of specified file systems, and treat them as a file. If you are using the crossref:zfs[,Z file system (ZFS)], refer to crossref:zfs[zfs-zfs-snapshot,"Managing Snapshots"] on how to use snapshots. +UFS snapshots allow a user to create images of specified file systems, and treat them as a file. If you are using the <>, refer to <> on how to use snapshots. Snapshot files must be created in the file system that the action is performed on, and a user may create no more than 20 snapshots per file system. Active snapshots are recorded in the superblock so they are persistent across unmount and remount operations along with system reboots. @@ -1628,7 +1628,8 @@ This prevents one user or group of users from consuming all of the available disk space. This section describes how to configure disk quotas for the UFS file system. -To configure quotas on the ZFS file system, refer to crossref:zfs[zfs-zfs-quota,"Dataset, User, and Group Quotas"] + +To configure quotas on the ZFS file system, refer to <>. === Enabling Disk Quotas @@ -1641,7 +1642,7 @@ .... In this example, the `1` indicates quota support. -If the value is instead `0`, add the following line to a custom kernel configuration file and rebuild the kernel using the instructions in crossref:kernelconfig[kernelconfig,Configuring the FreeBSD Kernel]: +If the value is instead `0`, add the following line to a custom kernel configuration file and rebuild the kernel using the instructions in <>: [.programlisting] .... @@ -1800,7 +1801,7 @@ == Encrypting Disk Partitions FreeBSD offers excellent online protections against unauthorized data access. -File permissions and crossref:mac[mac,Mandatory Access Control] (MAC) help prevent unauthorized users from accessing data while the operating system is active and the computer is powered up. +File permissions and <> (MAC) help prevent unauthorized users from accessing data while the operating system is active and the computer is powered up. However, the permissions enforced by the operating system are irrelevant if an attacker has physical access to a computer and can move the computer's hard drive to another system to copy and analyze the data. Regardless of how an attacker may have come into possession of a hard drive or powered-down computer, the GEOM-based cryptographic subsystems built into FreeBSD are able to protect the data on the computer's file systems against even highly-motivated attackers with significant resources. @@ -2117,7 +2118,7 @@ If the boot process seems to stall, look carefully for the password prompt among the other messages. Once the correct passphrase is entered, the provider is attached. The file system is then mounted, typically by an entry in [.filename]#/etc/fstab#. -Refer to crossref:basics[mount-unmount,“Mounting and Unmounting File Systems”] for instructions on how to configure a file system to mount at boot time. +Refer to <> for instructions on how to configure a file system to mount at boot time. [[swap-encrypting]] == Encrypting Swap @@ -2232,9 +2233,9 @@ Before reading this section, you should: -* Understand UNIX(R) and FreeBSD basics (crossref:basics[basics,FreeBSD Basics]). -* Know how to configure network interfaces and other core FreeBSD subsystems (crossref:config[config-tuning,Configuration and Tuning]). -* Have a good understanding of FreeBSD networking (crossref:partiv[network-communication,"Network Communication"]). +* Understand UNIX(R) and <>. +* Know how to configure <> interfaces and <>. +* Have a good understanding of FreeBSD networking <>. The HAST project was sponsored by The FreeBSD Foundation with support from http://www.omc.net/[http://www.omc.net/] and http://www.transip.nl/[http://www.transip.nl/]. @@ -2276,7 +2277,7 @@ * The userland management utility, man:hastctl[8]. * The man:hast.conf[5] configuration file. This file must exist before starting hastd. -Users who prefer to statically build `GEOM_GATE` support into the kernel should add this line to the custom kernel configuration file, then rebuild the kernel using the instructions in crossref:kernelconfig[kernelconfig,Configuring the FreeBSD Kernel]: +Users who prefer to statically build `GEOM_GATE` support into the kernel should add this line to the custom kernel configuration file, then rebuild the kernel using the instructions in <>: [.programlisting] .... @@ -2382,7 +2383,7 @@ To accomplish this task, the Common Address Redundancy Protocol (CARP) is used to provide for automatic failover at the IP layer. CARP allows multiple hosts on the same network segment to share an IP address. -Set up CARP on both nodes of the cluster according to the documentation available in crossref:advanced-networking[carp,“Common Address Redundancy Protocol (CARP)”]. +Set up CARP on both nodes of the cluster according to the documentation available in <>. In this example, each node will have its own management IP address and a shared IP address of _172.16.0.254_. The primary HAST node of the cluster must be the primary CARP node. @@ -2534,7 +2535,7 @@ To reduce the time needed for recovery, a journal-enabled UFS or ZFS file system can be used instead. ==== -Instead of using the highly available storage locally, it can also be shared to other computers on a network via crossref:network-servers[network-nfs,NFS], crossref:network-servers[network-iscsi,iSCSI], man:sshfs[1], or programs in ports (i.e. package:net/samba419[]). +Instead of using the highly available storage locally, it can also be shared to other computers on a network via <>, <>, man:sshfs[1], or programs in ports (i.e. package:net/samba419[]). More detailed information with additional examples can be found at http://wiki.FreeBSD.org/HAST[http://wiki.FreeBSD.org/HAST].