diff options
Diffstat (limited to 'documentation/content/en/books/handbook')
6 files changed, 51 insertions, 25 deletions
diff --git a/documentation/content/en/books/handbook/bsdinstall/_index.adoc b/documentation/content/en/books/handbook/bsdinstall/_index.adoc index 5f24e4c43f..83acfe30e7 100644 --- a/documentation/content/en/books/handbook/bsdinstall/_index.adoc +++ b/documentation/content/en/books/handbook/bsdinstall/_index.adoc @@ -634,7 +634,8 @@ The `Size` may be entered with common abbreviations: _K_ for kilobytes, _M_ for ==== Proper sector alignment provides the best performance, and making partition sizes even multiples of 4K bytes helps to ensure alignment on drives with either 512-byte or 4K-byte sectors. Generally, using partition sizes that are even multiples of 1M or 1G is the easiest way to make sure every partition starts at an even multiple of 4K. -There is one exception: the _freebsd-boot_ partition should be no larger than 512K due to current boot code limitations. +There is one exception: a _freebsd-boot_ partition for BIOS booting should be no larger than 512K due to legacy boot code limitations. +This limitation does not apply to UEFI booting. ==== A `Mountpoint` is needed if the partition will contain a file system. diff --git a/documentation/content/en/books/handbook/desktop/_index.adoc b/documentation/content/en/books/handbook/desktop/_index.adoc index 225ed297b2..829a63d77c 100644 --- a/documentation/content/en/books/handbook/desktop/_index.adoc +++ b/documentation/content/en/books/handbook/desktop/_index.adoc @@ -151,12 +151,21 @@ Enable D-BUS service in `/etc/rc.conf` to start at system boot: # sysrc dbus_enable="YES" .... -To increase messages size execute: +KDE Plasma requires larger message sizes for optimal performance. + +Add the following lines to man:sysctl.conf[5]: + +[.programlisting] +.... +sysctl net.local.stream.recvspace=65536 +sysctl net.local.stream.sendspace=65536 +.... + +To apply the change, either run the following command as root or simply reboot the system: [source,shell] .... -# sysctl net.local.stream.recvspace=65536 -# sysctl net.local.stream.sendspace=65536 +# sysctl -f /etc/sysctl.conf .... [[kde-start]] @@ -281,15 +290,6 @@ To install the XFCE meta package, execute: [[xfce-configuration]] ==== Configure XFCE -XFCE requires `/proc` to be mounted. -Add this line to `/etc/fstab` to mount this file system automatically during system startup: - -[.programlisting] -.... -# Device Mountpoint FStype Options Dump Pass# -proc /proc procfs rw 0 0 -.... - XFCE uses man:dbus-daemon[1] for a message bus and hardware abstraction. This application is automatically installed as a dependency of XFCE. diff --git a/documentation/content/en/books/handbook/jails/_index.adoc b/documentation/content/en/books/handbook/jails/_index.adoc index a9b941a3a2..fd652694cc 100644 --- a/documentation/content/en/books/handbook/jails/_index.adoc +++ b/documentation/content/en/books/handbook/jails/_index.adoc @@ -1051,7 +1051,7 @@ Finally, it will be necessary to remove the jail entry in [.filename]#/etc/jail. The man:pkg[8] tool supports the `-j` argument in order to handle packages installed inside the jail. -For example, to install package:nginx-lite[] in the jail, the next command can be executed *from the host*: +For example, to install package:www/nginx-lite[] in the jail, the next command can be executed *from the host*: [source,shell] .... diff --git a/documentation/content/en/books/handbook/mirrors/_index.adoc b/documentation/content/en/books/handbook/mirrors/_index.adoc index e921ce156e..9c308e1dbf 100644 --- a/documentation/content/en/books/handbook/mirrors/_index.adoc +++ b/documentation/content/en/books/handbook/mirrors/_index.adoc @@ -96,6 +96,8 @@ http://ftp-archive.FreeBSD.org is not in the GeoDNS Infrastructure, hosted in on The project is looking for new locations; those willing to sponsor, please reach out to the Cluster Administrators team for more information. +There is an ongoing project to provide **download.FreeBSD.org** and **pkg.FreeBSD.org** through link:https://www.fastly.com[Fastly], using its CDN acceleration, caching, and bandwidth to bring FreeBSD images and packages to our globally distributed community. + Mirror list maintained by the community and other companies: [cols="1,1,3"] diff --git a/documentation/content/en/books/handbook/network/_index.adoc b/documentation/content/en/books/handbook/network/_index.adoc index 5d54ddd5e8..bb49981b31 100644 --- a/documentation/content/en/books/handbook/network/_index.adoc +++ b/documentation/content/en/books/handbook/network/_index.adoc @@ -577,11 +577,15 @@ The following sections discuss each step. Connecting FreeBSD to an existing wireless network is a very common situation. -This procedure shows the steps required: +This Quick Start procedure shows the steps required to connect to a network using basic authentication. +A more detailed procedure is given in the next section. -* The first step will be to obtain the SSID (Service Set Identifier) and PSK (Pre-Shared Key) for the wireless network from the network administrator. +The first step is to obtain the Service Set Identifier (SSID) and Pre-Shared Key (PSK) for the wireless network from the network administrator. -* The second step will be to add default configuration paramaters and an entry for this network to [.filename]#/etc/wpa_supplicant.conf#. If the file does not exist, create it: +The second step is to add an entry for this network to [.filename]#/etc/wpa_supplicant.conf#. + +If the file does not exist, create it. +Consult man:wpa_supplicant.conf[5] for details on formatting entries in this file. [.programlisting] .... @@ -596,10 +600,28 @@ network={ } .... -<.> Is the SSID of the wireless network. Replace it with the name of the wireless network. -<.> Is the PSK of the wireless network. Replace it with the password of the wireless network. +<.> Is the SSID of the wireless network. +Replace it with the name of the wireless network. +<.> Is the PSK of the wireless network. +Replace it with the password of the wireless network. + +The third step is to add the network interface entry to configure the network on startup. +Obtain the network device interface by using the sysctl `net.wlan.devices`. +In the listing below, the output of this sysctl shows the network device interface is "iwn0". + +[source,shell] +.... +# sysctl net.wlan.devices +.... + +The output should be similar to the following: + +[.programlisting] +.... +net.wlan.devices: iwm0 +.... -* The third step will be to add the network entry to configure the network on startup: +In the sysrc line that follows, replace "iwn0" with the output of the sysctl command if needed. [source,shell] .... @@ -607,7 +629,7 @@ network={ # sysrc ifconfig_wlan0="WPA DHCP" .... -* And the last step will be the restart `netif` service executing the following command: +* And the last step is to restart the `netif` service executing the following command: [source,shell] .... @@ -617,7 +639,7 @@ network={ [[basic-wireless-configuration]] === Basic Wireless Configuration -The first step will be to configure the wireless network card to an interface. +This section provides a more detailed example of configuring a wireless network card. To find out what wireless network cards are in the system check the section crossref:network[config-identify-network-adapter, Identify Network Adapters]. diff --git a/documentation/content/en/books/handbook/wayland/_index.adoc b/documentation/content/en/books/handbook/wayland/_index.adoc index 48d9e4a4e1..aa402971ff 100644 --- a/documentation/content/en/books/handbook/wayland/_index.adoc +++ b/documentation/content/en/books/handbook/wayland/_index.adoc @@ -73,9 +73,10 @@ After reading this chapter, you will know: [[wayland-overview]] == Wayland Overview -Wayland is a new display server, but it differs from Xorg in several important ways. -First, Wayland is only a protocol that acts as an intermediary between clients using a different mechanism which removes the dependency on an X server. -Xorg includes both the X11 protocol, used to run remote displays and the X server will accept connections and display windows. +Wayland is a communication protocol that can replace a display server such as Xorg. +It differs from Xorg in several important ways. +First, Wayland is only a protocol that acts as an intermediary between clients using a mechanism which removes the dependency on an X server. +Xorg includes both the X11 protocol, used to run remote displays, and the X server, used to accept connections and display windows. Under Wayland, the compositor or window manager provides the display server instead of a traditional X server. Since Wayland is not an X server, traditional X screen connections will need to utilize other methods such as VNC or RDP for remote desktop management. |