If man:ls[1] is used to view the contents of this directory, it will show two subdirectories, `A1` and `A2`.
The directory tree looks like this:
-image::example-dir1.png[Directory tree with the root directory and two subdirectories, A1 and A2]
+image::example-dir1.png["Directory tree with the root directory and two subdirectories, A1 and A2"]
A file system must be mounted on to a directory in another file system.
When mounting file system `B` on to the directory `A1`, the root directory of `B` replaces `A1`, and the directories in `B` appear accordingly:
-image::example-dir2.png[Directory tree with the root directory and two subdirectories, A1 and A2. And more subdirectories, B1 and B2 hanging from A1]
+image::example-dir2.png["Directory tree with the root directory and two subdirectories, A1 and A2. And more subdirectories, B1 and B2 hanging from A1"]
Any files that are in the `B1` or `B2` directories can be reached with the path `/A1/B1` or `/A1/B2` as necessary.
Any files that were in `/A1` have been temporarily hidden.
@@ -1234,7 +1234,7 @@
If `B` had been mounted on `A2` then the diagram would look like this:
-image::example-dir3.png[Directory tree with the root directory and two subdirectories, A1 and A2. And more subdirectories, B1 and B2 hanging from A2]
+image::example-dir3.png["Directory tree with the root directory and two subdirectories, A1 and A2. And more subdirectories, B1 and B2 hanging from A2"]
and the paths would be `/A2/B1` and `/A2/B2` respectively.
@@ -1245,7 +1245,7 @@
Or `C` could be mounted directly on to the `A` file system, under the `A1` directory:
-image::example-dir5.png[A complex directory tree. With different subdirectories hanging from root.]
+image::example-dir5.png["A complex directory tree. With different subdirectories hanging from root."]
It is entirely possible to have one large root file system, and not need to create any others.
There are some drawbacks to this approach, and one advantage.
-image::bsdinstall-config-components.png[Different components that can be installed. Example: base-dbg, lib32, ports, etc.]
+image::bsdinstall-config-components.png["Different components that can be installed. Example: base-dbg, lib32, ports, etc."]
Deciding which components to install will depend largely on the intended use of the system and the amount of disk space available.
The FreeBSD kernel and userland, collectively known as the _base system_, are always installed.
@@ -478,7 +478,7 @@
[[bsdinstall-zfs-partmenu]]
.Partitioning Choices
-image::bsdinstall-zfs-partmenu.png[Shows the different partition options. Example: Manual, Shell, etc.]
+image::bsdinstall-zfs-partmenu.png["Shows the different partition options. Example: Manual, Shell, etc."]
bsdinstall gives the user four methods for allocating disk space:
@@ -628,7 +628,7 @@
[[bsdinstall-part-manual-addpart]]
.Manually Create Partitions
-image::bsdinstall-part-manual-addpart.png[Menu requesting type, size, mountpoint and label for the new partition.]
+image::bsdinstall-part-manual-addpart.png["Menu requesting type, size, mountpoint and label for the new partition."]
A standard FreeBSD GPT installation uses at least three partitions, including either UFS or ZFS:
@@ -762,7 +762,7 @@
[[bsdinstall-zfs-vdev_type]]
.ZFS Pool Type
-image::bsdinstall-zfs-vdev_type.png[Menu requesting the Virtual Device type. Ex: stripe, mirror, raidz1]
+image::bsdinstall-zfs-vdev_type.png["Menu requesting the Virtual Device type. Ex: stripe, mirror, raidz1"]
Here is a summary of the `Pool Type` that can be selected in this menu:
@@ -1153,7 +1153,7 @@
[[bsdinstall-final-config]]
.Final Configuration
-image::bsdinstall-finalconfiguration.png[Menu showing different options to perform before finishing the installation. Ex: Add user, Time Zone, etc.]
+image::bsdinstall-finalconfiguration.png["Menu showing different options to perform before finishing the installation. Ex: Add user, Time Zone, etc."]
Use this menu to make any changes or to do any additional configuration before completing the installation.
Architecture-independent images can be downloaded and directly imported into your own registry from the https://download.freebsd.org/releases[Official FreeBSD Releases] site, or alternatively, pulled from the FreeBSD project's https://hub.docker.com/u/freebsd[Docker Hub], or https://github.com/orgs/freebsd/packages[GitHub Container Registry].
-Both https://hub.docker.com/_/alpine/[Alpine Linux] and the https://hub.docker.com/_/debian/[Debian] project publish tagged and mutable images, using similar approaches.
+// Escape only the first _ in a Docker Hub URL (/_/) so Asciidoctor does not treat it as an italic marker.
+Both https://hub.docker.com/\_/alpine/[Alpine Linux] and the https://hub.docker.com/_/debian/[Debian] project publish tagged and mutable images, using similar approaches.
* Keith Bostic <mailto:bostic@toe.CS.Berkeley.EDU[bostic@toe.CS.Berkeley.EDU]>
* Ken Hughes
* Kent Talarico <mailto:kent@shipwreck.tsoft.net[kent@shipwreck.tsoft.net]>
-* Kevin Lahey <mailto:kml%rokkaku.UUCP@mathcs.emory.edu[kml%rokkaku.UUCP@mathcs.emory.edu]mailto:kml@mosquito.cis.ufl.edu[kml@mosquito.cis.ufl.edu]>
+* Kevin Lahey <mailto:kml%25rokkaku.UUCP@mathcs.emory.edu[kml%rokkaku.UUCP@mathcs.emory.edu]mailto:kml@mosquito.cis.ufl.edu[kml@mosquito.cis.ufl.edu]>
* Marc Frajola <mailto:marc@dev.com[marc@dev.com]>
* Mark Tinguely <mailto:tinguely@plains.nodak.edu[tinguely@plains.nodak.edu]mailto:tinguely@hookie.cs.ndsu.NoDak.edu[tinguely@hookie.cs.ndsu.NoDak.edu]>