Attachment 233342 Details for Bug 263332 – spurious "because" removed from Features and Terminology section

[patch] spurious "because" removed from Features and Terminology section

because-removed-zfs.txt (text/plain), 5.79 KB, created by John Darrah on 2022-04-19 17:51:57 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: John Darrah

Created: 2022-04-19 17:51:57 UTC

Size: 5.79 KB

patch

obsolete

>diff --git a/documentation/content/en/books/handbook/bsdinstall/_index.adoc b/documentation/content/en/books/handbook/bsdinstall/_index.adoc
>index 625462331d..f06cb706ca 100644
>--- a/documentation/content/en/books/handbook/bsdinstall/_index.adoc
>+++ b/documentation/content/en/books/handbook/bsdinstall/_index.adoc
>@@ -132,6 +132,7 @@ A 32-bit kernel can only use the first 2 GB of RAM.
> == Pre-Installation Tasks
> 
> Once it has been determined that the system meets the minimum hardware requirements for installing FreeBSD, the installation file should be downloaded and the installation media prepared.
>+An alternative is to use virtualization (crossref:virtualization[virtualization,Virtualization]) which allows multiple operating systems to run at the same time without modifying any disk partitions.
> Before doing this, check that the system is ready for an installation by verifying the items in this checklist:
> 
> [.procedure]
>@@ -169,7 +170,7 @@ Since the possibility of selecting the wrong partition exists, always backup any
> ====
> +
> Disk partitions containing different operating systems make it possible to install multiple operating systems on one computer.
>-An alternative is to use virtualization (crossref:virtualization[virtualization,Virtualization]) which allows multiple operating systems to run at the same time without modifying any disk partitions.
>+Virtualization (crossref:virtualization[virtualization,Virtualization]) allows multiple operating systems to run at the same time without modifying any disk partitions.
> . *Collect Network Information*
> +
> Some FreeBSD installation methods require a network connection in order to download the installation files.
>diff --git a/documentation/content/en/books/handbook/linuxemu/_index.adoc b/documentation/content/en/books/handbook/linuxemu/_index.adoc
>index 8b46e6444f..540a3127d5 100644
>--- a/documentation/content/en/books/handbook/linuxemu/_index.adoc
>+++ b/documentation/content/en/books/handbook/linuxemu/_index.adoc
>@@ -324,7 +324,7 @@ The Linux system call vector contains, among other things, a list of `sysent[]`
> When a system call is called by the Linux binary, the trap code dereferences the system call function pointer off the `proc` structure, and gets the Linux, not the FreeBSD, system call entry points.
> 
> Linux mode dynamically _reroots_ lookups.
>-This is, in effect, equivalent to `union` to file system mounts.
>+This is, in effect, equivalent to `union` file system mounts.
> First, an attempt is made to look up the file in [.filename]#/compat/linux/original-path#.
> If that fails, the lookup is done in [.filename]#/original-path#.
> This makes sure that binaries that require other binaries can run.
>diff --git a/documentation/content/en/books/handbook/zfs/_index.adoc b/documentation/content/en/books/handbook/zfs/_index.adoc
>index 3f9a2a457d..aa7537e5dc 100644
>--- a/documentation/content/en/books/handbook/zfs/_index.adoc
>+++ b/documentation/content/en/books/handbook/zfs/_index.adoc
>@@ -50,7 +50,7 @@ endif::[]
> 
> ZFS is an advanced file system designed to solve major problems found in previous storage subsystem software.
> 
>-Originally developed at Sun(TM), ongoing open source ZFS development has moved to the http://open-zfs.org[OpenZFS Project].
>+Originally developed at Sun(TM), ongoing open source ZFS development has moved to the http://openzfs.org[OpenZFS Project].
> 
> ZFS has three major design goals:
> 
>@@ -488,7 +488,7 @@ The <<zfs-zfs,`zfs`>> utility allows creating, destroying, and managing datasets
> [[zfs-zpool-create]]
> === Creating and Destroying Storage Pools
> 
>-Creating a ZFS storage pool (_zpool_) requires permanent decisions, as the pool structure cannot change after creation.
>+Creating a ZFS storage pool requires permanent decisions, as the pool structure cannot change after creation.
> The most important decision is which types of vdevs to group the physical disks into. 
> See the list of <<zfs-term-vdev,vdev types>> for details about the possible options.
> After creating the pool, most vdev types do not allow adding disks to the vdev.
>@@ -580,7 +580,7 @@ This can cause undefined behavior in applications which had open files on those
> [[zfs-zpool-attach]]
> === Adding and Removing Devices
> 
>-Two ways exist for adding disks to a zpool: attaching a disk to an existing vdev with `zpool attach`, or adding vdevs to the pool with `zpool add`.
>+Two ways exist for adding disks to a pool: attaching a disk to an existing vdev with `zpool attach`, or adding vdevs to the pool with `zpool add`.
> Some <<zfs-term-vdev,vdev types>> allow adding disks to the vdev after creation.
> 
> A pool created with a single disk lacks redundancy.
>@@ -2692,9 +2692,8 @@ For a more detailed list of recommendations for ZFS-related tuning, see https://
> [[zfs-links]]
> == Further Resources
> 
>-* http://open-zfs.org[OpenZFS]
>+* http://openzfs.org[OpenZFS]
> * https://wiki.freebsd.org/ZFSTuningGuide[FreeBSD Wiki - ZFS Tuning]
>-* http://docs.oracle.com/cd/E19253-01/819-5461/index.html[Oracle Solaris ZFS Administration Guide]
> * https://calomel.org/zfs_raid_speed_capacity.html[Calomel Blog - ZFS Raidz Performance, Capacity and Integrity]
> 
> [[zfs-term]]
>@@ -2725,7 +2724,7 @@ a|A pool consists of one or more vdevs, which themselves are a single disk or a
> ====
> Using an entire disk as part of a bootable pool is strongly discouraged, as this may render the pool unbootable.
> Likewise, you should not use an entire disk as part of a mirror or RAID-Z vdev.
>-Reliably determining the size of an unpartitioned disk at boot time is impossible and because there's no place to put in boot code.
>+Reliably determining the size of an unpartitioned disk at boot time is impossible and there's no place to put in boot code.
> ====
> 
> * [[zfs-term-vdev-file]] _File_ - Regular files may make up ZFS pools, which is useful for testing and experimentation. Use the full path to the file as the device path in `zpool create`.

Actions: View | Diff

Attachments on bug 263332: 233342 | 233461 | 233462