git: 1bf5347232 - main - Remove extra whitespace characters from the end of a few lines.
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 29 Jan 2022 13:22:29 UTC
The branch main has been updated by bcr:
URL: https://cgit.FreeBSD.org/doc/commit/?id=1bf534723265e5deebe949208a965486c57a59fc
commit 1bf534723265e5deebe949208a965486c57a59fc
Author: Benedict Reuschling <bcr@FreeBSD.org>
AuthorDate: 2022-01-29 13:19:47 +0000
Commit: Benedict Reuschling <bcr@FreeBSD.org>
CommitDate: 2022-01-29 13:19:47 +0000
Remove extra whitespace characters from the end of a few lines.
---
.../content/en/books/handbook/disks/_index.adoc | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/documentation/content/en/books/handbook/disks/_index.adoc b/documentation/content/en/books/handbook/disks/_index.adoc
index 81dde47a57..20272d58bb 100644
--- a/documentation/content/en/books/handbook/disks/_index.adoc
+++ b/documentation/content/en/books/handbook/disks/_index.adoc
@@ -670,7 +670,7 @@ When used with `-R`, it produces a file system image that is identical to the sp
The last option of general use is `-b`.
This is used to specify the location of a boot image for use in producing an "El Torito" bootable CD.
This option takes an argument which is the path to a boot image from the top of the tree being written to the CD.
-By default, `mkisofs` creates an ISO image in "floppy disk emulation" mode, and thus expects the boot image to be exactly 1200, 1440 or 2880 KB in size.
+By default, `mkisofs` creates an ISO image in "floppy disk emulation" mode, and thus expects the boot image to be exactly 1200, 1440 or 2880 KB in size.
Some boot loaders, like the one used by the FreeBSD distribution media, do not use emulation mode.
In this case, `-no-emul-boot` should be used.
So, if [.filename]#/tmp/myboot# holds a bootable FreeBSD system with the boot image in [.filename]#/tmp/myboot/boot/cdboot#, this command would produce [.filename]#/tmp/bootable.iso#:
@@ -877,7 +877,7 @@ To force the write speed, use `-speed=`. Refer to man:growisofs[1] for example u
====
In order to support working files larger than 4.38GB, an UDF/ISO-9660 hybrid file system must be created by passing `-udf -iso-level 3` to man:mkisofs[8] and all related programs, such as man:growisofs[1].
This is required only when creating an ISO image file or when writing files directly to a disk.
-Since a disk created this way must be mounted as an UDF file system with man:mount_udf[8], it will be usable only on an UDF aware operating system.
+Since a disk created this way must be mounted as an UDF file system with man:mount_udf[8], it will be usable only on an UDF aware operating system.
Otherwise it will look as if it contains corrupted files.
To create this type of ISO file:
@@ -1303,7 +1303,7 @@ When creating a backup file, make sure that the backup is not saved to the same
====
To restore the entire backup, `cd` into the directory to restore into and specify the name of the backup.
-Note that this will overwrite any newer versions of files in the restore directory.
+Note that this will overwrite any newer versions of files in the restore directory.
When in doubt, restore to a temporary directory or specify the name of the file within the backup to restore.
.Restoring Up the Current Directory with `tar`
@@ -1355,7 +1355,7 @@ While tape technology has continued to evolve, modern backup systems tend to com
FreeBSD supports any tape drive that uses SCSI, such as LTO or DAT.
There is limited support for SATA and USB tape drives.
-For SCSI tape devices, FreeBSD uses the man:sa[4] driver and the [.filename]#/dev/sa0#, [.filename]#/dev/nsa0#, and [.filename]#/dev/esa0# devices.
+For SCSI tape devices, FreeBSD uses the man:sa[4] driver and the [.filename]#/dev/sa0#, [.filename]#/dev/nsa0#, and [.filename]#/dev/esa0# devices.
The physical device name is [.filename]#/dev/sa0#. When [.filename]#/dev/nsa0# is used, the backup application will not rewind the tape after writing a file, which allows writing more than one file to a tape.
Using [.filename]#/dev/esa0# ejects the tape after the device is closed.
@@ -1557,7 +1557,7 @@ For more details about `mdmfs`, refer to man:mdmfs[8].
FreeBSD offers a feature in conjunction with crossref:config[soft-updates,Soft Updates]: file system snapshots.
UFS snapshots allow a user to create images of specified file systems, and treat them as a file.
-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.
+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.
When a snapshot is no longer required, it can be removed using man:rm[1].
While snapshots may be removed in any order, all the used space may not be acquired because another snapshot will possibly claim some of the released blocks.
@@ -1616,7 +1616,7 @@ For more information about `softupdates` and file system snapshots, including te
[[quotas]]
== Disk Quotas
-Disk quotas can be used to limit the amount of disk space or the number of files a user or members of a group may allocate on a per-file system basis.
+Disk quotas can be used to limit the amount of disk space or the number of files a user or members of a group may allocate on a per-file system basis.
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.
@@ -1804,7 +1804,7 @@ It first demonstrates the process using `gbde` and then demonstrates the same ex
=== Disk Encryption with gbde
-The objective of the man:gbde[4] facility is to provide a formidable challenge for an attacker to gain access to the contents of a _cold_ storage device.
+The objective of the man:gbde[4] facility is to provide a formidable challenge for an attacker to gain access to the contents of a _cold_ storage device.
However, if the computer is compromised while up and running and the storage device is actively attached, or the attacker has access to a valid passphrase, it offers no protection to the contents of the storage device.
Thus, it is important to provide physical security while the system is running and to protect the passphrase used by the encryption mechanism.
@@ -2204,7 +2204,7 @@ Device 1K-blocks Used Avail Capacity
[[disks-hast]]
== Highly Available Storage (HAST)
-High availability is one of the main requirements in serious business applications and highly-available storage is a key component in such environments.
+High availability is one of the main requirements in serious business applications and highly-available storage is a key component in such environments.
In FreeBSD, the Highly Available STorage (HAST) framework allows transparent storage of the same data across several physically separated machines connected by a TCP/IP network.
HAST can be understood as a network-based RAID1 (mirror), and is similar to the DRBD(R) storage system used in the GNU/Linux(R) platform.
In combination with other high-availability features of FreeBSD like CARP, HAST makes it possible to build a highly-available storage cluster that is resistant to hardware failures.
@@ -2281,7 +2281,7 @@ The nodes will be called `hasta`, with an IP address of `172.16.0.1`, and `hastb
Both nodes will have a dedicated hard drive [.filename]#/dev/ad6# of the same size for HAST operation.
The HAST pool, sometimes referred to as a resource or the GEOM provider in [.filename]#/dev/hast/#, will be called `test`.
-Configuration of HAST is done using [.filename]#/etc/hast.conf#.
+Configuration of HAST is done using [.filename]#/etc/hast.conf#.
This file should be identical on both nodes.
The simplest configuration is: