diff options
Diffstat (limited to 'documentation')
19 files changed, 161 insertions, 162 deletions
diff --git a/documentation/content/en/books/fdp-primer/overview/_index.adoc b/documentation/content/en/books/fdp-primer/overview/_index.adoc index 2b72b0c23e..c316176b05 100644 --- a/documentation/content/en/books/fdp-primer/overview/_index.adoc +++ b/documentation/content/en/books/fdp-primer/overview/_index.adoc @@ -290,7 +290,7 @@ Repeat until all of the errors are resolved. + [source,shell] .... -$ bmake run USE_RUBYGEMS=YES RUBY_CMD=$(brew --prefix ruby)/bin/ruby +$ bmake run USE_RUBYGEMS=YES RUBY_CMD="$(brew --prefix ruby)/bin/ruby" HUGO_CMD="$(brew --prefix hugo)/bin/hugo" .... . Add all the files with `git add .`, then review the diff with `git diff`. For example: + diff --git a/documentation/content/en/books/handbook/advanced-networking/_index.adoc b/documentation/content/en/books/handbook/advanced-networking/_index.adoc index 57ddfe3d75..6bade200be 100644 --- a/documentation/content/en/books/handbook/advanced-networking/_index.adoc +++ b/documentation/content/en/books/handbook/advanced-networking/_index.adoc @@ -54,7 +54,7 @@ endif::[] This chapter covers a number of advanced networking topics. -After reading this chapter, you will know: +Read this chapter to learn: * The basics of gateways and routes. * How to set up USB tethering. @@ -63,9 +63,9 @@ After reading this chapter, you will know: * How to set up network PXE booting. * How to enable and utilize the features of the Common Address Redundancy Protocol (CARP) in FreeBSD. * How to configure multiple VLANs on FreeBSD. -* Configure bluetooth headset. +* How to configure a bluetooth headset. -Before reading this chapter, you should: +Before reading this chapter: * Understand the basics of the [.filename]#/etc/rc# scripts. * Be familiar with basic network terminology. @@ -1325,7 +1325,7 @@ cu -l $PTS By default, when FreeBSD is accepting a new connection, it tries to perform a role switch and become master. Some older Bluetooth devices which do not support role switching will not be able to connect. -Since role switching is performed when a new connection is being established, it is not possible to ask the remote device if it supports role switching. +Since role switching is performed when a new connection is being established, it is not possible to ask the remote device if it supports role switching. However, there is a HCI option to disable role switching on the local side: [source,shell] @@ -1454,7 +1454,7 @@ The STP protocol detects loops and puts redundant links into a blocked state. Should one of the active links fail, STP calculates a different tree and enables one of the blocked paths to restore connectivity to all points in the network. The Rapid Spanning Tree Protocol (RSTP or 802.1w) provides backwards compatibility with legacy STP. -RSTP provides faster convergence and exchanges information with neighboring switches to quickly transition to forwarding mode without creating loops. +RSTP provides faster convergence and exchanges information with neighboring switches to quickly transition to forwarding mode without creating loops. FreeBSD supports RSTP and STP as operating modes, with RSTP being the default mode. STP can be enabled on member interfaces using man:ifconfig[8]. @@ -1527,7 +1527,7 @@ Sticky entries are never aged out of the cache or replaced, even if the address This gives the benefit of static address entries without the need to pre-populate the forwarding table. Clients learned on a particular segment of the bridge cannot roam to another segment. + -An example of using sticky addresses is to combine the bridge with VLANs in order to isolate customer networks without wasting IP address space. +An example of using sticky addresses is to combine the bridge with VLANs in order to isolate customer networks without wasting IP address space. Consider that `CustomerA` is on `vlan100`, `CustomerB` is on `vlan101`, and the bridge has the address `192.168.0.1`: + [source,shell] @@ -1558,7 +1558,7 @@ The following example sets the maximum number of Ethernet devices for `CustomerA # ifconfig bridge0 ifmaxaddr vlan100 10 .... -Bridge interfaces also support monitor mode, where the packets are discarded after man:bpf[4] processing and are not processed or forwarded further. +Bridge interfaces also support monitor mode, where the packets are discarded after man:bpf[4] processing and are not processed or forwarded further. This can be used to multiplex the input of two or more interfaces into a single man:bpf[4] stream. This is useful for reconstructing the traffic for network taps that transmit the RX/TX signals out through two separate interfaces. For example, to read the input from four network interfaces as one stream: @@ -1688,7 +1688,7 @@ Each LAG is composed of ports of the same speed, set to full-duplex operation, a Typically, there is only one LAG which contains all the ports. In the event of changes in physical connectivity, LACP will quickly converge to a new configuration. + -LACP balances outgoing traffic across the active ports based on hashed protocol header information and accepts incoming traffic from any active port. +LACP balances outgoing traffic across the active ports based on hashed protocol header information and accepts incoming traffic from any active port. The hash includes the Ethernet source and destination address and, if available, the VLAN tag, and the IPv4 or IPv6 source and destination address. roundrobin:: @@ -1844,7 +1844,7 @@ ifconfig_lagg0="laggproto failover laggport fxp0 laggport fxp1 10.0.0.15/24" [example] ==== -For laptop users, it is usually desirable to configure the wireless device as a secondary which is only used when the Ethernet connection is not available. +For laptop users, it is usually desirable to configure the wireless device as a secondary which is only used when the Ethernet connection is not available. With man:lagg[4], it is possible to configure a failover which prefers the Ethernet connection for both performance and security reasons, while maintaining the ability to transfer data over the wireless connection. This is achieved by overriding the Ethernet interface's MAC address with that of the wireless interface. @@ -1859,13 +1859,13 @@ We therefore recommend overriding the Ethernet MAC address for this purpose. [NOTE] **** If the driver for the wireless interface is not loaded in the `GENERIC` or custom kernel, and the computer is running FreeBSD {rel121-current}, load the corresponding [.filename]#.ko# in [.filename]#/boot/loader.conf# by adding `*driver_load="YES"*` to that file and rebooting. -Another, better way is to load the driver in [.filename]#/etc/rc.conf# by adding it to `kld_list` (see man:rc.conf[5] for details) in that file and rebooting. +Another, better way is to load the driver in [.filename]#/etc/rc.conf# by adding it to `kld_list` (see man:rc.conf[5] for details) in that file and rebooting. This is needed because otherwise the driver is not loaded yet at the time the man:lagg[4] interface is set up. **** In this example, the Ethernet interface, _re0_, is the master and the wireless interface, _wlan0_, is the failover. The _wlan0_ interface was created from the _ath0_ physical wireless interface, and the Ethernet interface will be configured with the MAC address of the wireless interface. -First, bring the wireless interface up (replacing _FR_ with your own 2-letter country code), but do not set an IP address. +First, bring the wireless interface up (replacing _FR_ with the local 2-letter country code), but do not set an IP address. Replace _wlan0_ to match the system's wireless interface name: [source,shell] @@ -1873,7 +1873,7 @@ Replace _wlan0_ to match the system's wireless interface name: # ifconfig wlan0 create wlandev ath0 country FR ssid my_router up .... -Now you can determine the MAC address of the wireless interface: +Determine the MAC address of the wireless interface like this: [source,shell] .... @@ -2095,7 +2095,7 @@ In this case, [.filename]#/etc# and [.filename]#/var# need to be memory backed f When the system boots, memory file systems for [.filename]#/etc# and [.filename]#/var# will be created and mounted and the contents of the [.filename]#cpio.gz# files will be copied into them. By default, these file systems have a maximum capacity of 5 megabytes. -If your archives do not fit, which is usually the case for [.filename]#/var# when binary packages have been installed, request a larger size by putting the number of 512 byte sectors needed (e.g., 5 megabytes is 10240 sectors) in [.filename]#${NFSROOTDIR}/conf/base/etc/md_size# and [.filename]#${NFSROOTDIR}/conf/base/var/md_size# files for [.filename]#/etc# and [.filename]#/var# file systems respectively. +If the archives do not fit, which is usually the case for [.filename]#/var# when binary packages have been installed, request a larger size by putting the number of 512 byte sectors needed (e.g., 5 megabytes is 10240 sectors) in [.filename]#${NFSROOTDIR}/conf/base/etc/md_size# and [.filename]#${NFSROOTDIR}/conf/base/var/md_size# files for [.filename]#/etc# and [.filename]#/var# file systems respectively. [[network-pxe-setting-up-dhcp]] === Configuring the DHCP Server diff --git a/documentation/content/en/books/handbook/basics/_index.adoc b/documentation/content/en/books/handbook/basics/_index.adoc index 0abb750dab..ad0cdb7a9c 100644 --- a/documentation/content/en/books/handbook/basics/_index.adoc +++ b/documentation/content/en/books/handbook/basics/_index.adoc @@ -56,7 +56,7 @@ This chapter covers the basic commands and functionality of the FreeBSD operatin Much of this material is relevant for any UNIX(R)-like operating system. New FreeBSD users are encouraged to read through this chapter carefully. -After reading this chapter, you will know: +Read this chapter to learn: * How to use and configure virtual consoles. * How to create and manage users and groups on FreeBSD. @@ -559,7 +559,7 @@ How to configure NIS is covered in crossref:network-servers[network-servers,Netw Any user can easily change their password using man:passwd[1]. To prevent accidental or unauthorized changes, this command will prompt for the user's original password before a new password can be set: -.Changing Your Password +.Changing The Password [example] ==== [source,shell] @@ -1076,7 +1076,7 @@ The root directory also contains mount points for other file systems that are mo A mount point is a directory where additional file systems can be grafted onto a parent file system (usually the root file system). This is further described in crossref:basics[disk-organization, Disk Organization]. -Standard mount points include `/usr/`, `/var/`, `/tmp/`, `/mnt/`, and `/cdrom/`. +Standard mount points include `/usr/`, `/var/`, `/tmp/`, `/mnt/`, and `/media/`. These directories are usually referenced to entries in `/etc/fstab`. This file is a table of various file systems and mount points and is read by the system. Most of the file systems in `/etc/fstab` are mounted automatically at boot time from the script man:rc[8] unless their entry includes `noauto`. @@ -1257,7 +1257,7 @@ There are some drawbacks to this approach, and one advantage. * FreeBSD's file systems are robust if power is lost. However, a power loss at a critical point could still damage the structure of the file system. By splitting data over multiple file systems it is more likely that the system will still come up, making it easier to restore from backup as necessary. .Benefit of a Single File System -* File systems are a fixed size. If you create a file system when you install FreeBSD and give it a specific size, you may later discover that you need to make the partition bigger. This is not easily accomplished without backing up, recreating the file system with the new size, and then restoring the backed up data. +* File systems are a fixed size. When creating a file system during the FreeBSD installation and giving it a specific size, it may be that one wants to make the partition bigger. This is not easily accomplished without backing up, recreating the file system with the new size, and then restoring the backed up data. + [IMPORTANT] ==== @@ -1291,7 +1291,7 @@ These devices are used by file systems that expect to occupy a slice. Each GPT or BSD partition can contain only one file system, which means that file systems are often described by either their typical mount point in the file system hierarchy, or the name of the partition they are contained in. FreeBSD also uses disk space for _swap space_ to provide _virtual memory_. -This allows your computer to behave as though it has much more memory than it actually does. +This allows the computer to behave as though it has much more memory than it actually does. When FreeBSD runs out of memory, it moves some of the data that is not currently being used to the swap space, and moves it back in (moving something else out) when it needs it. This is called _paging_. @@ -1772,7 +1772,7 @@ For example, to change the shell to `bash`: % chsh -s /usr/local/bin/bash .... -Enter your password at the prompt and press kbd:[Return] to change your shell. +Enter the password at the prompt and press kbd:[Return] to change the shell. Log off and log in again to start using the new shell. [NOTE] diff --git a/documentation/content/en/books/handbook/bsdinstall/_index.adoc b/documentation/content/en/books/handbook/bsdinstall/_index.adoc index 83acfe30e7..79234d2dc6 100644 --- a/documentation/content/en/books/handbook/bsdinstall/_index.adoc +++ b/documentation/content/en/books/handbook/bsdinstall/_index.adoc @@ -64,7 +64,7 @@ The image types are: The rest of this chapter describes the third case, explaining how to install FreeBSD using the text-based installation program named bsdinstall. There may be minor differences between the installer and what is shown here, so use this chapter as a general guide rather than as a set of literal instructions. -After reading this chapter, you will know: +Read this chapter to learn: * How to obtain FreeBSD images and create FreeBSD installation media. * How to start bsdinstall. @@ -86,7 +86,7 @@ Once it has been determined that the system meets the minimum hardware requireme [TIP] ==== -Consider using crossref:virtualization[virtualization,virtualization] if you want to use FreeBSD on a system that already has another operating system installed. +Consider using crossref:virtualization[virtualization,virtualization] when wanting to use FreeBSD on a system that already has another operating system installed. ==== Before moving on to the installation, check that the system is ready by verifying the items in this checklist: @@ -185,7 +185,7 @@ There are two _checksum_ files available, named after the release number and the For example: `CHECKSUM.SHA256-FreeBSD-13.1-RELEASE-amd64` and `CHECKSUM.SHA512-FreeBSD-13.1-RELEASE-amd64`. After downloading one of the files (or both), calculate the _checksum_ for the image file and compare it with the one shown in the _checksum_ file. -Note that you need to compare the calculated _checksum_ against the correct file, as they correspond to two different algorithms: SHA256 and SHA512. +Note that comparing the calculated _checksum_ against the correct file is needed, as they correspond to two different algorithms: SHA256 and SHA512. FreeBSD provides man:sha256[1] and man:sha512[1] that can be used for calculating the _checksum_. Other operating systems have similar programs. @@ -468,7 +468,7 @@ It then demonstrates how to use the different partitioning methods. === Designing the Partition Layout The default partition layout for file systems includes one file system for the entire system. -When using `UFS` it may be worth considering the use of multiple file systems if you have sufficient disk space or multiple disks. +When using `UFS` it may be worth considering the use of multiple file systems with sufficient disk space or multiple disks available. When laying out file systems, remember that hard drives transfer data faster from the outer tracks to the inner. Thus, smaller and heavier-accessed file systems should be closer to the outside of the drive, while larger partitions like `/usr` should be placed toward the inner parts of the disk. It is a good idea to create partitions in an order similar to: `/`, swap, `/var`, and `/usr`. @@ -1045,7 +1045,7 @@ Here is a summary of the services that can be enabled in this menu: * `sshd` - The Secure Shell (SSH) daemon is used to remotely access a system over an encrypted connection. Only enable this service if the system should be available for remote logins. * `moused` - Enable this service if the mouse will be used from the command-line system console. * `ntpdate` - Enable automatic clock synchronization at boot time. Note that the functionality of this program is now available in the man:ntpd[8] daemon and the man:ntpdate[8] utility will soon be retired. -* `ntpd` - The Network Time Protocol (NTP) daemon for automatic clock synchronization. Enable this service if you wish to synchronise your system clock with a remote time server or pool. +* `ntpd` - The Network Time Protocol (NTP) daemon for automatic clock synchronization. Enable this service when wanting to synchronise the system clock with a remote time server or pool. * `powerd` - System power control utility for power control and energy saving. * `dumpdev` - Crash dumps are useful when debugging issues with the system, so users are encouraged to enable them. @@ -1151,7 +1151,7 @@ Once configuration is complete, select btn:[Exit]. [[bsdinstall-final-modification-shell]] .Manual Configuration -image::bsdinstall-final-modification-shell.png[Menu showing that the installation has finished. And asking if you want to open a shell to make manual changes.] +image::bsdinstall-final-modification-shell.png[Menu showing that the installation has finished. And asking if a shell to make manual changes should open.] bsdinstall will prompt for any additional configuration that needs to be done before rebooting into the new system. Select btn:[Yes] to exit to a shell within the new system or btn:[No] to proceed to the last step of the installation. diff --git a/documentation/content/en/books/handbook/cutting-edge/_index.adoc b/documentation/content/en/books/handbook/cutting-edge/_index.adoc index e1390faa52..59e38e2bc9 100644 --- a/documentation/content/en/books/handbook/cutting-edge/_index.adoc +++ b/documentation/content/en/books/handbook/cutting-edge/_index.adoc @@ -415,8 +415,8 @@ If physical access to the system is available, a copy of the `GENERIC` kernel ca [source,shell] .... -# mount /cdrom -# cd /cdrom/usr/freebsd-dist +# mount /media +# cd /media/usr/freebsd-dist # tar -C/ -xvf kernel.txz boot/kernel/kernel .... diff --git a/documentation/content/en/books/handbook/disks/_index.adoc b/documentation/content/en/books/handbook/disks/_index.adoc index 599952fecd..b86395f9e4 100644 --- a/documentation/content/en/books/handbook/disks/_index.adoc +++ b/documentation/content/en/books/handbook/disks/_index.adoc @@ -55,7 +55,7 @@ endif::[] This chapter covers the use of disks and storage media in FreeBSD. This includes SCSI and IDE disks, CD and DVD media, memory-backed disks, and USB storage devices. -After reading this chapter, you will know: +Read this chapter to learn: * How to add additional hard disks to a FreeBSD system. * How to grow the size of a disk's partition on FreeBSD. @@ -68,7 +68,7 @@ After reading this chapter, you will know: * How to encrypt disks and swap to secure them against attackers. * How to configure a highly available storage network. -Before reading this chapter, you should: +Before reading this chapter: * Know how to crossref:kernelconfig[kernelconfig,configure and install a new FreeBSD kernel]. @@ -1487,7 +1487,8 @@ 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. 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. +When using the crossref:zfs[,Z file system (ZFS)], refer to crossref:zfs[zfs-zfs-snapshot,"Managing Snapshots"] 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. @@ -2148,13 +2149,13 @@ The following are the main features of HAST: * Can be used in an already deployed environment to add additional redundancy. * Together with CARP, Heartbeat, or other tools, it can be used to build a robust and durable storage system. -After reading this section, you will know: +Read this chapter to learn: * What HAST is, how it works, and which features it provides. * How to set up and use HAST on FreeBSD. * How to integrate CARP and man:devd[8] to build a robust storage system. -Before reading this section, you should: +Before reading this section: * 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]). diff --git a/documentation/content/en/books/handbook/introduction/_index.adoc b/documentation/content/en/books/handbook/introduction/_index.adoc index 6b59ec791f..4e84e37165 100644 --- a/documentation/content/en/books/handbook/introduction/_index.adoc +++ b/documentation/content/en/books/handbook/introduction/_index.adoc @@ -54,13 +54,13 @@ endif::[] Thank you for your interest in FreeBSD! The following chapter covers various aspects of the FreeBSD Project, such as its history, goals, development model, and so on. -After reading this chapter you will know: +Read this chapter to learn: * How FreeBSD relates to other computer operating systems. * The history of the FreeBSD Project. * The goals of the FreeBSD Project. * The basics of the FreeBSD open-source development model. -* And of course: where the name "FreeBSD" comes from. +* Where the name "FreeBSD" comes from. [[nutshell]] == Welcome to FreeBSD! @@ -69,13 +69,13 @@ FreeBSD is an Open Source, standards-compliant Unix-like operating system for x8 It provides all the features that are nowadays taken for granted, such as preemptive multitasking, memory protection, virtual memory, multi-user facilities, SMP support, all the Open Source development tools for different languages and frameworks, and desktop features centered around X Window System, KDE, or GNOME. Its particular strengths are: -* _Liberal Open Source license_, which grants you rights to freely modify and extend its source code and incorporate it in both Open Source projects and closed products without imposing restrictions typical to copyleft licenses, as well as avoiding potential license incompatibility problems. +* _Liberal Open Source license_, which grants the rights to freely modify and extend its source code and incorporate it in both Open Source projects and closed products without imposing restrictions typical to copyleft licenses, as well as avoiding potential license incompatibility problems. * _Strong TCP/IP networking_ - FreeBSD implements industry standard protocols with ever increasing performance and scalability. This makes it a good match in both server, and routing/firewalling roles - and indeed many companies and vendors use it precisely for that purpose. * _Fully integrated OpenZFS support_, including root-on-ZFS, ZFS Boot Environments, fault management, administrative delegation, support for jails, FreeBSD specific documentation, and system installer support. * _Extensive security features_, from the Mandatory Access Control framework to Capsicum capability and sandbox mechanisms. -* _Over 30 thousand prebuilt packages_ for all supported architectures, and the Ports Collection which makes it easy to build your own, customized ones. +* _Over 30 thousand prebuilt packages_ for all supported architectures, and the Ports Collection which makes it easy to build customized ones. * _Documentation_ - in addition to the Handbook and books from different authors that cover topics ranging from system administration to kernel internals, there are also the man:man[1] pages, not only for userspace daemons, utilities, and configuration files, but also for kernel driver APIs (section 9) and individual drivers (section 4). -* _Simple and consistent repository structure and build system_ - FreeBSD uses a single repository for all of its components, both kernel and userspace. This, along with a unified and easy to customize build system and a well thought-out development process makes it easy to integrate FreeBSD with build infrastructure for your own product. +* _Simple and consistent repository structure and build system_ - FreeBSD uses a single repository for all of its components, both kernel and userspace. This, along with a unified and easy to customize build system and a well thought-out development process makes it easy to integrate FreeBSD with build infrastructure for own product. * _Staying true to Unix philosophy_, preferring composability instead of monolithic "all in one" daemons with hardcoded behavior. * _Binary compatibility_ with Linux, which makes it possible to run many Linux binaries without the need for virtualisation. @@ -86,8 +86,8 @@ FreeBSD offers performance and reliability on par with other Open Source and com [[os-overview]] === What Can FreeBSD Do? -The applications to which FreeBSD can be put are truly limited only by your own imagination. -From software development to factory automation, inventory control to azimuth correction of remote satellite antenna; if it can be done with a commercial UNIX(R) product then it is more than likely that you can do it with FreeBSD too! FreeBSD also benefits significantly from literally thousands of high quality applications developed by research centers and universities around the world, often available at little to no cost. +The applications to which FreeBSD can be put are truly limited only by ones own imagination. +From software development to factory automation, inventory control to azimuth correction of remote satellite antenna; if it can be done with a commercial UNIX(R) product then it is more than likely that FreeBSD can do it, too! FreeBSD also benefits significantly from literally thousands of high quality applications developed by research centers and universities around the world, often available at little to no cost. Because the source code for FreeBSD itself is freely available, the system can also be customized to an almost unheard-of degree for special applications or projects, and in ways not generally possible with operating systems from most major commercial vendors. Here is just a sampling of some of the applications in which people are currently using FreeBSD: @@ -103,9 +103,9 @@ Here is just a sampling of some of the applications in which people are currentl ** Virtualization servers ** And more... -* _Education:_ Are you a student of computer science or a related engineering field? There is no better way of learning about operating systems, computer architecture and networking than the hands-on, under-the-hood experience that FreeBSD can provide. A number of freely available CAD, mathematical and graphic design packages also make it highly useful to those whose primary interest in a computer is to get _other_ work done! +* _Education:_ Computer science students, as well as those in related engineering fields, will benefit from FreeBSD. There is no better way of learning about operating systems, computer architecture and networking than the hands-on, under-the-hood experience that FreeBSD can provide. A number of freely available CAD, mathematical and graphic design packages also make it highly useful to those whose primary interest in a computer is to get _other_ work done! * _Research:_ With source code for the entire system available, FreeBSD is an excellent platform for research in operating systems as well as other branches of computer science. FreeBSD's freely available nature also makes it possible for remote groups to collaborate on ideas or shared development without having to worry about special licensing agreements or limitations on what may be discussed in open forums. -* _Networking:_ Need a new router? A name server (DNS)? A firewall to keep people out of your internal network? FreeBSD can easily turn that unused PC sitting in the corner into an advanced router with sophisticated packet-filtering capabilities. +* _Networking:_ Need a new router? A name server (DNS)? A firewall to keep people out of the internal network? FreeBSD can easily turn that unused PC sitting in the corner into an advanced router with sophisticated packet-filtering capabilities. * _Embedded:_ FreeBSD makes an excellent platform to build embedded systems upon. With support for the ARM, AArch64 and PowerPC platforms, coupled with a robust network stack, cutting edge features, and the permissive extref:{faq}[BSD license, bsd-license-restrictions], FreeBSD makes an excellent foundation for building embedded routers, firewalls, and other devices. * _Desktop:_ FreeBSD makes a fine choice for an inexpensive desktop solution using the freely available X11 server and Wayland display server. FreeBSD offers a choice from many open-source desktop environments, including the standard GNOME and KDE graphical user interfaces. FreeBSD can even boot "diskless" from a central server, making individual workstations even cheaper and easier to administer. * _Software Development:_ The basic FreeBSD system comes with a full suite of development tools including a full C/C++ compiler and debugger suite. Support for many other languages are also available through the ports and packages collection. @@ -237,8 +237,8 @@ All we ask of those who would join us as FreeBSD developers is some of the same In addition to the base distributions, FreeBSD offers a ported software collection with thousands of commonly sought-after programs. The list of ports ranges from HTTP servers to games, languages, editors, and almost everything in between. There are about {numports} ports; the entire Ports Collection requires approximately {ports-size}. -To compile a port, you simply change to the directory of the program you wish to install, type `make install`, and let the system do the rest. -The full original distribution for each port you build is retrieved dynamically so you need only enough disk space to build the ports you want. +To compile a port, simply change to the directory of the program needed to install, type `make install`, and let the system do the rest. +The full original distribution for each port that is build is retrieved dynamically so only enough disk space to build the ports is needed. Almost every port is also provided as a pre-compiled "package", which can be installed with a simple command (`pkg install`) by those who do not wish to compile their own ports from source. More information on packages and ports can be found in crossref:ports[ports,Installing Applications: Packages and Ports]. @@ -255,7 +255,7 @@ Documentation may also be installed later using packages: For localized versions replace the "en" with the language prefix of choice. Be aware that some of the localised versions might be out of date and might contain information that is no longer correct or relevant. -You may view the locally installed manuals with a web browser using the following URLs: +Read the locally installed manuals with a web browser using the following URLs: The FreeBSD Handbook:: `/usr/local/share/doc/freebsd/en/books/handbook/handbook_en.pdf` @@ -263,6 +263,6 @@ The FreeBSD Handbook:: The FreeBSD FAQ:: `/usr/local/share/doc/freebsd/en/books/faq/faq_en.pdf` -You can always find up to date documentation at link:https://docs.FreeBSD.org/[The Documentation Portal]. +Find up to date documentation at link:https://docs.FreeBSD.org/[The Documentation Portal]. All trademarks are the property of their respective owners. diff --git a/documentation/content/en/books/handbook/linuxemu/_index.adoc b/documentation/content/en/books/handbook/linuxemu/_index.adoc index df1034c1e7..1f0c07c540 100644 --- a/documentation/content/en/books/handbook/linuxemu/_index.adoc +++ b/documentation/content/en/books/handbook/linuxemu/_index.adoc @@ -119,7 +119,7 @@ In order to run Linux software a Linux userland must be installed first. If all that is wanted is to run some software already included in the Ports tree, it can be installed via package manager and man:pkg[8] will automatically setup the required Linux userland. For example, to install Sublime Text 4, along with all the Linux libraries it depends on, run this command: - + [source,shell] .... # pkg install linux-sublime-text4 @@ -231,7 +231,7 @@ Once enabled, execute the following command to install Ubuntu or Debian in [.fil [source,shell] .... -# debootstrap focal /compat/ubuntu +# debootstrap jammy /compat/ubuntu .... [NOTE] @@ -244,11 +244,11 @@ The output should be similar to the following: [.programlisting] .... -I: Retrieving InRelease +I: Retrieving InRelease I: Checking Release signature I: Valid Release signature (key id F6ECB3762474EDA9D21B7022871920D1991BC93C) -I: Retrieving Packages -I: Validating Packages +I: Retrieving Packages +I: Validating Packages I: Resolving dependencies of required packages... I: Resolving dependencies of base packages... I: Checking component main on http://archive.ubuntu.com/ubuntu... @@ -307,7 +307,7 @@ The output should be similar to the following: [.programlisting] .... -Linux 3.17.0 x86_64 +Linux 5.15.0 x86_64 .... Once inside the chroot, the system behaves as in a normal Ubuntu installation. @@ -321,10 +321,10 @@ For amd64 the following example can be used: [.programlisting] .... -deb http://archive.ubuntu.com/ubuntu focal main universe restricted multiverse -deb http://security.ubuntu.com/ubuntu/ focal-security universe multiverse restricted main -deb http://archive.ubuntu.com/ubuntu focal-backports universe multiverse restricted main -deb http://archive.ubuntu.com/ubuntu focal-updates universe multiverse restricted main +deb http://archive.ubuntu.com/ubuntu jammy main universe restricted multiverse +deb http://security.ubuntu.com/ubuntu/ jammy-security universe multiverse restricted main +deb http://archive.ubuntu.com/ubuntu jammy-backports universe multiverse restricted main +deb http://archive.ubuntu.com/ubuntu jammy-updates universe multiverse restricted main .... For arm64 this other example can be used: diff --git a/documentation/content/en/books/handbook/mail/_index.adoc b/documentation/content/en/books/handbook/mail/_index.adoc index c8c3cb076a..003b5a429c 100644 --- a/documentation/content/en/books/handbook/mail/_index.adoc +++ b/documentation/content/en/books/handbook/mail/_index.adoc @@ -141,10 +141,8 @@ username@gmail.com|smtp.gmail.com:password [NOTE] ==== -If you have 2-factor authentication enabled, you will need to generate an -application-specific password as your normal login password will be -rejected. See Google documentation for more information on -https://myaccount.google.com/apppasswords[app-specific passwords]. +With enabled 2-factor authentication a generated application-specific password as the normal login password will be rejected. +See Google documentation for more information on https://myaccount.google.com/apppasswords[app-specific passwords]. ==== Execute the following command to test the configuration: @@ -384,7 +382,7 @@ daily_submit_queuerun="NO" The next step is to install another MTA, man:dma[8] will be used in this example. As pointed above, man:dma[8] is the default MTA in FreeBSD starting with version 14.0. -Therefore, it is only necessary to install it from the ports if you are using a previous version. +Therefore, it is only necessary to install it from the ports when using a previous version. To install it execute the following command: @@ -767,7 +765,7 @@ example.FreeBSD.org has address 204.216.27.XX example.FreeBSD.org mail is handled (pri=10) by nevdull.FreeBSD.org .... -All mail sent to `example.FreeBSD.org` will be collected on `nevdull` under the same username instead of being sent directly to your host. +All mail sent to `example.FreeBSD.org` will be collected on `nevdull` under the same username instead of being sent directly to the local host. The above information is handled by the DNS server. The DNS record that carries mail routing information is the link:https://en.wikipedia.org/wiki/MX_record[mail exchanger record (MX record)]. @@ -788,7 +786,7 @@ The lowest MX number is the host that receives mail directly, if available. If it is not accessible for some reason, the next lower-numbered host will accept messages temporarily, and pass it along when a lower-numbered host becomes available. Alternate MX sites should have separate Internet connections in order to be most useful. -Your ISP can provide this service. +The ISP can provide this service. [[mail-domain]] === Mail for a Domain diff --git a/documentation/content/en/books/handbook/multimedia/_index.adoc b/documentation/content/en/books/handbook/multimedia/_index.adoc index 17cb077290..0950c9d5c1 100644 --- a/documentation/content/en/books/handbook/multimedia/_index.adoc +++ b/documentation/content/en/books/handbook/multimedia/_index.adoc @@ -57,7 +57,7 @@ Multimedia applications and technologies have become an integral part of modern This chapter covers various multimedia components such as audio, video, and image processing. It also discusses various media formats and codecs, as well as tools and applications for multimedia creation and playback. Additionally, the chapter covers multimedia system configuration, troubleshooting, and optimization. -Whether you are a multimedia enthusiast or a professional content creator, FreeBSD offers a robust platform for multimedia work. +FreeBSD provides a robust platform for multimedia work, suitable for both multimedia enthusiasts and professional content creators. This chapter aims to help get the most out of FreeBSD's multimedia capabilities, providing useful information and practical examples to help get started. [[sound-setup]] @@ -343,7 +343,7 @@ To install GNOME Music, execute: === Audacious Audacious is an open source audio player. -A descendant of XMMS, it plays your music how you want it, without stealing away your computer's resources from other tasks. +As a descendant of XMMS, it provides music playback while maintaining efficient use of system resources. To install Audacious, execute: diff --git a/documentation/content/en/books/handbook/network-servers/_index.adoc b/documentation/content/en/books/handbook/network-servers/_index.adoc index dba07a8e2c..d7ac579d4f 100644 --- a/documentation/content/en/books/handbook/network-servers/_index.adoc +++ b/documentation/content/en/books/handbook/network-servers/_index.adoc @@ -96,14 +96,14 @@ Each line of this configuration file represents an application which can be star By default, every line starts with a comment (`+#+`), meaning that inetd is not listening for any applications. To configure inetd to listen for an application's connections, remove the `+#+` at the beginning of the line for that application. -After saving your edits, configure inetd to start at system boot by editing [.filename]#/etc/rc.conf#: +After saving the edits, configure inetd to start at system boot by editing [.filename]#/etc/rc.conf#: [.programlisting] .... inetd_enable="YES" .... -To start inetd now, so that it listens for the service you configured, type: +To start inetd now, so that it listens for the configured service, type: [source,shell] .... @@ -319,11 +319,11 @@ The examples can be modified to match the file systems and client names on the r There are many options that can be used in this file, but only a few will be mentioned here. See man:exports[5] for the full list of options. -This example shows how to export [.filename]#/cdrom# to three hosts named _alpha_, _bravo_, and _charlie_: +This example shows how to export [.filename]#/media# to three hosts named _alpha_, _bravo_, and _charlie_: [.programlisting] .... -/cdrom -ro alpha bravo charlie +/media -ro alpha bravo charlie .... The `-ro` flag makes the file system read-only, preventing clients from making any changes to the exported file system. @@ -1249,7 +1249,7 @@ default:\ In this example, the system is using the DES format for password hashing. Other possible values include `blf` for Blowfish, `md5` for MD5, `sha256` and `sha512` for SHA-256 and SHA-512 respectively. -For more information and the up to date list of what is available on your system, consult the man:crypt[3] manpage. +For more information and the up to date list of what is available on the system, consult the man:crypt[3] manpage. If the format on a host needs to be edited to match the one being used in the NIS domain, the login capability database must be rebuilt after saving the change: @@ -2618,7 +2618,7 @@ On FreeBSD, the built-in ntpd can be used to synchronize a system's clock. ntpd is configured using man:rc.conf[5] variables and [.filename]#/etc/ntp.conf#, as detailed in the following sections. ntpd communicates with its network peers using UDP packets. -Any firewalls between your machine and its NTP peers must be configured to allow UDP packets in and out on port 123. +Any firewalls between the machine and its NTP peers must be configured to allow UDP packets in and out on port 123. ==== The [.filename]#/etc/ntp.conf# file @@ -2732,7 +2732,7 @@ The presence of any of the following keywords in [.filename]#ntp.conf# requires * logdir * statsdir -To manually configure ntpd to run as user `ntpd` you must: +To manually configure ntpd to run as user `ntpd`: * Ensure that the `ntpd` user has access to all the files and directories specified in the configuration. * Arrange for the `mac_ntpd` module to be loaded or compiled into the kernel. See man:mac_ntpd[4] for details. diff --git a/documentation/content/en/books/handbook/ports/_index.adoc b/documentation/content/en/books/handbook/ports/_index.adoc index fe7001ab82..725e00331c 100644 --- a/documentation/content/en/books/handbook/ports/_index.adoc +++ b/documentation/content/en/books/handbook/ports/_index.adoc @@ -57,7 +57,7 @@ In addition, FreeBSD provides two complementary technologies for installing thir for installing from source, and packages, for installing from pre-built binaries. Either method may be used to install software from local media or from the network. -After reading this chapter, you will know: +Read this chapter to learn: * The difference between binary packages and ports. * How to find third-party software that has been ported to FreeBSD. @@ -86,7 +86,7 @@ A FreeBSD package contains pre-compiled copies of all the commands for an applic A package can be manipulated with the man:pkg[8] commands, such as `pkg install`. While the two technologies are similar, packages and ports each have their own strengths. -Select the technology that meets your requirements for installing a particular application. +Select the technology that meets the needs for installing a particular application. .Package Benefits * A compressed package tarball is typically smaller than the compressed tarball containing the source code for the application. @@ -99,7 +99,7 @@ Select the technology that meets your requirements for installing a particular a + In some cases, multiple packages will exist for the same application with different settings. For example, NGINX(R) is available as a `nginx` package and a `nginx-lite` package, the former has many more options enabled, but this in turn requires many things to be installed as dependencies for it to work, thus increasing space consumption and attack surface. + -The transitive dependencies can grow quite large, for example the full `nginx` package will pull in several X libraries which can be quite surprising, so building from ports allow you to choose only the options you need without a "kitchen sink" approach. In some cases, multiple packages will exist for the same application to specify certain settings. +The transitive dependencies can grow quite large, for example the full `nginx` package will pull in several X libraries which can be quite surprising, so building from ports allows to choose only the options needed without a "kitchen sink" approach. In some cases, multiple packages will exist for the same application to specify certain settings. * The licensing conditions of some software forbid binary distribution. Such software must be distributed as source code which must be compiled by the end-user. * Some people do not trust binary distributions or prefer to read through source code in order to look for potential problems. * Source code is needed in order to apply custom patches. @@ -165,7 +165,7 @@ The package management tool is not yet installed on your system. Do you want to fetch and install it now? [y/N] .... -man:pkg[7] will intercept the command, and if you confirm that is your intention, download the man:pkg[8] tarball, install man:pkg[8] from it, bootstrap the local package database and then proceed to run the command you originally requested. +man:pkg[7] will intercept the command, and when confirmed, downloads the man:pkg[8] tarball, installs man:pkg[8] from it, bootstraps the local package database and then proceeds to run the command originally requested. More recent versions of man:pkg[7] understand `pkg -N` as a test to see if man:pkg[8] is installed without triggering the installation, and conversely, pkg bootstrap[-f] to install man:pkg[8] (or force it to be reinstalled) without performing any other actions. @@ -695,7 +695,7 @@ By default, the Ports Collection itself is stored as a subdirectory of `/usr/por Before installing and using the Ports Collection, please be aware that it is generally ill-advised to use the Ports Collection in conjunction with the binary packages provided via pkg to install software. pkg, by default, tracks quarterly branch-releases of the ports tree and not HEAD. Dependencies could be different for a port in HEAD compared to its counterpart in a quarterly branch release and this could result in conflicts between dependencies installed by pkg and those from the Ports Collection. -If the Ports Collection and pkg must be used in conjunction, then be sure that your Ports Collection and pkg are on the same branch release of the ports tree. +If the Ports Collection and pkg must be used in conjunction, then be sure that the Ports Collection and pkg are on the same branch release of the ports tree. ==== The Ports Collection contains directories for software categories. @@ -730,8 +730,8 @@ If more control over the ports tree is needed or if local changes need to be mai Git can be used to obtain the Ports Collection. Refer to extref:{committers-guide}[the Git Primer, git-primer] for a detailed description of Git. -We add --depth 1 to the git command line to clone the tree without obtaining the commit history, which saves time and is acceptable for most users. -If you have your own changes to the ports tree, or need the history for any reason, omit the --depth 1 argument below. +We add --depth 1 to the git command line to clone the tree without obtaining the commit history, which saves time and is acceptable for most users. +When maintaining custom changes to the ports tree, or need the history for any reason, omit the --depth 1 argument below. . Git must be installed before it can be used to check out the ports tree. If a copy of the ports tree is already present, install Git like this: + @@ -875,7 +875,7 @@ and ports options screens no longer appear, to be certain that all dependency op There are several ways to revisit a port's build options menu in order to add, remove, or change these options after a port has been built. One method is to `cd` into the directory containing the port and type `make config`. Another option is to use `make showconfig`. -Another option is to execute `make rmconfig` which will remove all selected options and allow you to start over. +Another option is to execute `make rmconfig` which will remove all selected options and allows to start over. All of these options, and others, are explained in great detail in man:ports[7]. The ports system uses man:fetch[1] to download the source files, which supports various environment variables. @@ -921,7 +921,7 @@ will compile the port in `/usr/ports` and install it in `/usr/home/example/local will combine the two. These can also be set as environmental variables. -Refer to the manual page for your shell for instructions on how to set an environmental variable. +Refer to the manual page for the shell for instructions on how to set an environmental variable. [[ports-removing]] === Removing Installed Ports @@ -983,7 +983,7 @@ Synth is a newer alternative. [NOTE] ==== The choice of which tool is best for a particular system is up to the system administrator. -It is recommended practice to back up your data before using any of these tools. +It is recommended practice to back up data before using any of these tools. ==== [[portmaster]] @@ -1361,5 +1361,5 @@ Instead, any fixes and support come from the general community who subscribe to ==== + If there is no response to the email, use Bugzilla to submit a bug report using the instructions in extref:{problem-reports}[Writing FreeBSD Problem Reports]. -. Fix it! The extref:{porters-handbook}[Porter's Handbook] includes detailed information on the ports infrastructure so that you can fix the occasional broken port or even submit your own! -. Install the package instead of the port using the instructions in crossref:ports[pkgng-intro, Using pkg for Binary Package Management]. + +. Fix it! The extref:{porters-handbook}[Porter's Handbook] includes detailed information on the ports infrastructure, enabling the fixing of occasional broken ports or the submission of new ones. Install the package instead of the port using the instructions in crossref:ports[pkgng-intro, Using pkg for Binary Package Management]. diff --git a/documentation/content/en/books/handbook/ppp-and-slip/_index.adoc b/documentation/content/en/books/handbook/ppp-and-slip/_index.adoc index a267fdc7ea..3d7ec970d3 100644 --- a/documentation/content/en/books/handbook/ppp-and-slip/_index.adoc +++ b/documentation/content/en/books/handbook/ppp-and-slip/_index.adoc @@ -55,13 +55,13 @@ endif::[] FreeBSD supports the Point-to-Point (PPP) protocol which can be used to establish a network or Internet connection using a dial-up modem. This chapter describes how to configure modem-based communication services in FreeBSD. -After reading this chapter, you will know: +Read this chapter to learn: * How to configure, use, and troubleshoot a PPP connection. * How to set up PPP over Ethernet (PPPoE). * How to set up PPP over ATM (PPPoA). -Before reading this chapter, you should: +Before reading this chapter: * Be familiar with basic network terminology. * Understand the basics and purpose of a dial-up connection and PPP. @@ -289,7 +289,7 @@ This line specifies the PAP/CHAP user name.Insert the correct value for _MyUserN Line 14::: This line specifies the PAP/CHAP password. Insert the correct value for _MyPassword_. -You may want to add an additional line, such as: +An additional line may be added, such as: + [.programlisting] .... @@ -384,8 +384,8 @@ router_enable="NO" It is important that the `routed` daemon is not started, as `routed` tends to delete the default routing table entries created by `ppp`. -It is probably a good idea to ensure that the `sendmail_flags` line does not include the `-q` option, otherwise `sendmail` will attempt to do a network lookup every now and then, possibly causing your machine to dial out. -You may try: +It is probably a good idea to ensure that the `sendmail_flags` line does not include the `-q` option, otherwise `sendmail` will attempt to do a network lookup every now and then, possibly causing the machine to dial out. +Try this: [.programlisting] .... @@ -709,13 +709,13 @@ Here is an example of a working [.filename]#ppp.conf#: [.programlisting] .... default: - set log Phase tun command # you can add more detailed logging if you wish + set log Phase tun command # add more detailed logging when needed set ifaddr 10.0.0.1/0 10.0.0.2/0 name_of_service_provider: - set device PPPoE:xl1 # replace xl1 with your Ethernet device - set authname YOURLOGINNAME - set authkey YOURPASSWORD + set device PPPoE:xl1 # replace xl1 with the Ethernet device + set authname THELOGINNAME + set authkey THEPASSWORD set dial set login add default HISADDR @@ -734,7 +734,7 @@ Add the following to [.filename]#/etc/rc.conf#: .... ppp_enable="YES" ppp_mode="ddial" -ppp_nat="YES" # if you want to enable nat for your local network, otherwise NO +ppp_nat="YES" # when needing to enable nat for the local network, otherwise NO ppp_profile="name_of_service_provider" .... @@ -746,7 +746,7 @@ Service tags are used to distinguish between different PPPoE servers attached to Any required service tag information should be in the documentation provided by the ISP. As a last resort, one could try installing the package:net/rr-pppoe[] package or port. -Bear in mind however, this may de-program your modem and render it useless, so think twice before doing it. +Bear in mind however, this may de-program the modem and render it useless, so think twice before doing it. Simply install the program shipped with the modem. Then, access the menu:System[] menu from the program. The name of the profile should be listed there. @@ -838,8 +838,8 @@ adsl: open .... -<.> The username used to authenticate with your ISP. -<.> The password used to authenticate with your ISP. +<.> The username used to authenticate with the ISP. +<.> The password used to authenticate with the ISP. Information about the link, or links, to establish is found in [.filename]#mpd.links#. An example [.filename]#mpd.links# to accompany the above example is given beneath: @@ -896,7 +896,7 @@ adsl: .... <.> The username for the DSL provider. -<.> The password for your account. +<.> The password for the account. [WARNING] ==== diff --git a/documentation/content/en/books/handbook/preface/_index.adoc b/documentation/content/en/books/handbook/preface/_index.adoc index b25f3960d8..dfed27ebd1 100644 --- a/documentation/content/en/books/handbook/preface/_index.adoc +++ b/documentation/content/en/books/handbook/preface/_index.adoc @@ -51,8 +51,8 @@ endif::[] The FreeBSD newcomer will find that the first section of this book guides the user through the FreeBSD installation process and gently introduces the concepts and conventions that underpin UNIX(R). Working through this section requires little more than the desire to explore, and the ability to take on board new concepts as they are introduced. -Once you have traveled this far, the second, far larger, section of the Handbook is a comprehensive reference to all manner of topics of interest to FreeBSD system administrators. -Some of these chapters may recommend that you do some prior reading, and this is noted in the synopsis at the beginning of each chapter. +Once reaching this far, the second, far larger, section of the Handbook is a comprehensive reference to all manner of topics of interest to FreeBSD system administrators. +Some of these chapters may recommend to do some prior reading, and this is noted in the synopsis at the beginning of each chapter. For a list of additional sources of information, please see crossref:bibliography[bibliography,Bibliography]. @@ -157,7 +157,7 @@ _crossref:bsdinstall[bsdinstall,Installing FreeBSD]_:: Walks a user through the entire installation process of FreeBSD 9._x_ and later using bsdinstall. _crossref:basics[basics,FreeBSD Basics]_:: -Covers the basic commands and functionality of the FreeBSD operating system. If you are familiar with Linux(R) or another flavor of UNIX(R) then you can probably skip this chapter. +Covers the basic commands and functionality of the FreeBSD operating system. When familiar with Linux(R) or another flavor of UNIX(R) then this chapter can probably be skipped. _crossref:ports[ports,Installing Applications: Packages and Ports]_:: Covers the installation of third-party software with both FreeBSD's innovative "Ports Collection" and standard binary packages. @@ -172,10 +172,10 @@ _crossref:desktop[desktop,Desktop Applications]_:: Lists some common desktop applications, such as web browsers and productivity suites, and describes how to install them on FreeBSD. _crossref:multimedia[multimedia,Multimedia]_:: -Shows how to set up sound and video playback support for your system. Also describes some sample audio and video applications. +Shows how to set up sound and video playback support for the system. Also describes some sample audio and video applications. _crossref:kernelconfig[kernelconfig,Configuring the FreeBSD Kernel]_:: -Explains why you might need to configure a new kernel and provides detailed instructions for configuring, building, and installing a custom kernel. +Explains the need to configure a new kernel and provides detailed instructions for configuring, building, and installing a custom kernel. _crossref:printing[printing,Printing]_:: Describes managing printers on FreeBSD, including information about banner pages, printer accounting, and initial setup. @@ -193,7 +193,7 @@ _crossref:boot[boot,The FreeBSD Booting Process]_:: Describes the FreeBSD boot process and explains how to control this process with configuration options. _crossref:security[security,Security]_:: -Describes many different tools available to help keep your FreeBSD system secure, including Kerberos, IPsec and OpenSSH. +Describes many different tools available to help keep the FreeBSD system secure, including Kerberos, IPsec and OpenSSH. _crossref:jails[jails,Jails]_:: Describes the jails framework, and the improvements of jails over the traditional chroot support of FreeBSD. @@ -238,19 +238,19 @@ _crossref:mail[mail,Electronic Mail]_:: Explains the different components of an email server and dives into simple configuration topics for the most popular mail server software: sendmail. _crossref:network-servers[network-servers,Network Servers]_:: -Provides detailed instructions and example configuration files to set up your FreeBSD machine as a network filesystem server, domain name server, network information system server, or time synchronization server. +Provides detailed instructions and example configuration files to set up the FreeBSD machine as a network filesystem server, domain name server, network information system server, or time synchronization server. _crossref:firewalls[firewalls,Firewalls]_:: Explains the philosophy behind software-based firewalls and provides detailed information about the configuration of the different firewalls available for FreeBSD. _crossref:advanced-networking[advanced-networking,Advanced Networking]_:: -Describes many networking topics, including sharing an Internet connection with other computers on your LAN, advanced routing topics, wireless networking, Bluetooth(R), ATM, IPv6, and much more. +Describes many networking topics, including sharing an Internet connection with other computers on the LAN, advanced routing topics, wireless networking, Bluetooth(R), ATM, IPv6, and much more. _crossref:mirrors[mirrors,Obtaining FreeBSD]_:: -Lists different sources for obtaining FreeBSD media on CDROM or DVD as well as different sites on the Internet that allow you to download and install FreeBSD. +Lists different sources for obtaining FreeBSD media on CDROM or DVD as well as different sites on the Internet that allows to download and install FreeBSD. _crossref:bibliography[bibliography,Bibliography]_:: -This book touches on many different subjects that may leave you hungry for a more detailed explanation. The bibliography lists many excellent books that are referenced in the text. +This book touches on many different subjects that may leave readers hungry for a more detailed explanation. The bibliography lists many excellent books that are referenced in the text. _crossref:eresources[eresources,Resources on the Internet]_:: Describes the many forums available for FreeBSD users to post questions and engage in technical conversations about FreeBSD. @@ -303,7 +303,7 @@ C:\> tools\fdimage floppies\kern.flp A: .... Examples starting with # indicate a command that must be invoked as the superuser in FreeBSD. -You can login as `root` to type the command, or login as your normal account and use man:su[1] to gain superuser privileges. +Login as `root` to type the command, or login as the normal account and use man:su[1] to gain superuser privileges. [source,shell] .... @@ -321,7 +321,7 @@ Unless otherwise noted, C-shell syntax is used for setting environment variables [[preface-acknowledgements]] == Acknowledgments -The book you are holding represents the efforts of many hundreds of people around the world. +This book represents the efforts of many hundreds of people around the world. Whether they sent in fixes for typos, or submitted complete chapters, all the contributions have been useful. Several companies have supported the development of this document by paying authors to work on it full-time, paying for publication, etc. diff --git a/documentation/content/en/books/handbook/security/_index.adoc b/documentation/content/en/books/handbook/security/_index.adoc index 53be6040d1..f2dc051b6a 100644 --- a/documentation/content/en/books/handbook/security/_index.adoc +++ b/documentation/content/en/books/handbook/security/_index.adoc @@ -256,7 +256,7 @@ Enter new password: If a password that does not match the policy is entered, it will be rejected with a warning and the user will have an opportunity to try again, up to the configured number of retries. -If your organization's policy requires passwords to expire, FreeBSD supports the `passwordtime` in the user's login class in [.filename]#/etc/login.conf# +If the organization's policy requires passwords to expire, FreeBSD supports the `passwordtime` in the user's login class in [.filename]#/etc/login.conf# The `default` login class contains an example: @@ -580,7 +580,7 @@ All devices may be read or written subject to their permissions. 1:: *Secure mode* - the system immutable and system append-only flags may not be turned off; disks for mounted file systems, [.filename]#/dev/mem# and [.filename]#/dev/kmem# may not be opened for writing; -[.filename]#/dev/io# (if your platform has it) may not be opened at all; kernel modules (see man:kld[4]) may not be loaded or unloaded. +[.filename]#/dev/io# (if the platform has it) may not be opened at all; kernel modules (see man:kld[4]) may not be loaded or unloaded. The kernel debugger may not be entered using the debug.kdb.enter sysctl. A panic or trap cannot be forced using the debug.kdb.panic, debug.kdb.panic_str and other sysctl's. @@ -1888,7 +1888,7 @@ Additionally, always exercise caution when editing system configuration files, e === Enabling and Configuring Resource Limits The man:rctl[8] system provides a more fine-grained way to set and manage resource limits for individual processes and users. -It allows you to dynamically assign resource limits to specific processes or users, regardless of their user class. +It allows dynamically assigning resource limits to specific processes or users, regardless of their user class. The first step to use man:rctl[8] will be to enable it adding the following line to [.filename]#/boot/loader.conf# and reboot the system: diff --git a/documentation/content/en/books/handbook/serialcomms/_index.adoc b/documentation/content/en/books/handbook/serialcomms/_index.adoc index 18637f7d1c..e275e26ae6 100644 --- a/documentation/content/en/books/handbook/serialcomms/_index.adoc +++ b/documentation/content/en/books/handbook/serialcomms/_index.adoc @@ -56,14 +56,14 @@ UNIX(R) has always had support for serial communications as the very first UNIX( Things have changed a lot from the days when the average terminal consisted of a 10-character-per-second serial printer and a keyboard. This chapter covers some of the ways serial communications can be used on FreeBSD. -After reading this chapter, you will know: +Read this chapter to learn: * How to connect terminals to a FreeBSD system. * How to use a modem to dial out to remote hosts. * How to allow remote users to login to a FreeBSD system with a modem. * How to boot a FreeBSD system from a serial console. -Before reading this chapter, you should: +Before reading this chapter: * Know how to crossref:kernelconfig[kernelconfig, configure and install a custom kernel]. * Understand crossref:basics[basics, FreeBSD permissions and processes]. @@ -880,7 +880,7 @@ Put in an entry for `tip1200` or `cu1200`, but go ahead and use whatever bps rat === Accessing a Number of Hosts Through a Terminal Server Rather than waiting until connected and typing `CONNECT _host_` each time, use ``tip``'s `cm` capability. -For example, these entries in [.filename]#/etc/remote# will let you type `tip pain` or `tip muffin` to connect to the hosts `pain` or `muffin`, and `tip deep13` to connect to the terminal server. +For example, these entries in [.filename]#/etc/remote# allow typing `tip pain` or `tip muffin` to connect to the hosts `pain` or `muffin`, and `tip deep13` to connect to the terminal server. [.programlisting] .... diff --git a/documentation/content/en/books/handbook/usb-device-mode/_index.adoc b/documentation/content/en/books/handbook/usb-device-mode/_index.adoc index 224412d35f..1ca78d5dfd 100644 --- a/documentation/content/en/books/handbook/usb-device-mode/_index.adoc +++ b/documentation/content/en/books/handbook/usb-device-mode/_index.adoc @@ -75,7 +75,7 @@ Note that in some cases, depending on the hardware and the hosts operating syste When FreeBSD is running on the host, man:usbconfig[8] `reset` can be used. This also must be done after loading [.filename]#usb_template.ko# if the USB host was already connected to the USBOTG socket. -After reading this chapter, you will know: +Read this chapter to learn: * How to set up USB Device Mode functionality on FreeBSD. * How to configure the virtual serial port on FreeBSD. @@ -141,7 +141,7 @@ To load the module and set the template without rebooting use: To connect to a board configured to provide USB device mode serial ports, connect the USB host, such as a laptop, to the boards USB OTG or USB client port. Use `pstat -t` on the host to list the terminal lines. -Near the end of the list you should see a USB serial port, e.g. "ttyU0". +Near the end of the list a USB serial port is shown, e.g. "ttyU0". To open the connection, use: [source,shell] @@ -149,7 +149,7 @@ To open the connection, use: # cu -l /dev/ttyU0 .... -After pressing the kbd:[Enter] key a few times you will see a login prompt. +After pressing the kbd:[Enter] key a few times a login prompt appears. === Connecting to USB Device Mode Serial Ports from macOS @@ -174,10 +174,10 @@ To open the connection, use: === Connecting to USB Device Mode Serial Ports from Microsoft Windows 10 To connect to a board configured to provide USB device mode serial ports, connect the USB host, such as a laptop, to the boards USB OTG or USB client port. -To open a connection you will need a serial terminal program, such as PuTTY. +To open a connection a serial terminal program is needed, such as PuTTY. To check the COM port name used by Windows, run Device Manager, expand "Ports (COM & LPT)". -You will see a name similar to "USB Serial Device (COM4)". -Run serial terminal program of your choice, for example PuTTY. +A name similar to "USB Serial Device (COM4)" appears. +Run the serial terminal program of choice, for example PuTTY. In the PuTTY dialog set "Connection type" to "Serial", type the COMx obtained from Device Manager in the "Serial line" dialog box and click Open. [[usb-device-mode-network]] diff --git a/documentation/content/en/books/handbook/virtualization/_index.adoc b/documentation/content/en/books/handbook/virtualization/_index.adoc index aa264bc80d..bd9dc39007 100644 --- a/documentation/content/en/books/handbook/virtualization/_index.adoc +++ b/documentation/content/en/books/handbook/virtualization/_index.adoc @@ -55,7 +55,7 @@ endif::[] Virtualization software allows multiple operating systems to run simultaneously on the same computer. Such software systems for PCs often involve a host operating system which runs the virtualization software and supports any number of guest operating systems. -After reading this chapter, you will know: +Read this chapter to learn: * The difference between a host operating system and a guest operating system. * How to install FreeBSD on the following virtualization platforms: @@ -66,7 +66,7 @@ After reading this chapter, you will know: ** bhyve(FreeBSD) * How to tune a FreeBSD system for best performance under virtualization. -Before reading this chapter, you should: +Before reading this chapter: * Understand the crossref:basics[basics,basics of UNIX(R) and FreeBSD]. * Know how to crossref:bsdinstall[bsdinstall,install FreeBSD]. @@ -424,7 +424,7 @@ All users that need access to VirtualBox(TM) will have to be added as members of [source,shell] .... -# pw groupmod vboxusers -m yourusername +# pw groupmod vboxusers -m username .... The default permissions for [.filename]#/dev/vboxnetctl# are restrictive and need to be changed for bridged networking: @@ -463,7 +463,7 @@ For VirtualBox(TM) to be aware of USB devices attached to the machine, the user [source,shell] .... -# pw groupmod operator -m yourusername +# pw groupmod operator -m username .... Then, add the following to [.filename]#/etc/devfs.rules#, or create this file if it does not exist yet: @@ -747,7 +747,7 @@ After a successful installation, QEMU will boot the operating system installed o [NOTE] ==== QEMU supports a ```-runas``` option. -For added security, include the option "-runas your_user_name" in the script listing above. +For added security, include the option "-runas user_name" in the script listing above. See man:qemu[1] for details. ==== @@ -1170,7 +1170,7 @@ image::qemu-freebsd16.png[] Reboot the system, and before FreeBSD starts up, switch to the monitor and enter `stop`. The VM will stop. -Enter `loadvm` with the tag you used above (here `original_install`). +Enter `loadvm` with the tag used above (here `original_install`). [source, shell] .... @@ -1413,7 +1413,7 @@ Now the guest can be started from the virtual disk: [[virtualization-bhyve-linux]] === Creating a Linux(R) Guest -Linux guests can be booted either like any other regular crossref:virtualization[virtualization-bhyve-uefi,"UEFI-based guest"] virtual machine, or alternatively, you can make use of the package:sysutils/grub2-bhyve[] port. +Linux guests can be booted either like any other regular crossref:virtualization[virtualization-bhyve-uefi,"UEFI-based guest"] virtual machine, or alternatively, use the package:sysutils/grub2-bhyve[] port. To do this, first ensure that the port is installed, then create a file to use as the virtual disk for the guest machine: @@ -1503,9 +1503,9 @@ Boot the virtual machine: -s 3:0,virtio-blk,./linux.img -l com1,stdio -c 4 -m 1024M linuxguest .... -Linux(R) will now boot in the virtual machine and eventually present you with the login prompt. +Linux(R) will now boot in the virtual machine and eventually presents the login prompt. Login and use the virtual machine. -When you are finished, reboot the virtual machine to exit bhyve. +When finished, reboot the virtual machine to exit bhyve. Destroy the virtual machine instance: [source,shell] @@ -1522,7 +1522,7 @@ This option may support guest operating systems that are not supported by the ot To make use of the UEFI support in bhyve, first obtain the UEFI firmware images. This can be done by installing package:sysutils/bhyve-firmware[] port or package. -With the firmware in place, add the flags `-l bootrom,_/path/to/firmware_` to your bhyve command line. +With the firmware in place, add the flags `-l bootrom,_/path/to/firmware_` to the bhyve command line. The actual bhyve command may look like this: [source,shell] @@ -1534,7 +1534,7 @@ The actual bhyve command may look like this: guest .... -To allow a guest to store UEFI variables, you can use a variables file appended to the `-l` flag. +To allow a guest to store UEFI variables, use a variables file appended to the `-l` flag. Note that bhyve will write guest modifications to the given variables file. Therefore, be sure to first create a per-guest-copy of the variables template file: @@ -1543,7 +1543,7 @@ Therefore, be sure to first create a per-guest-copy of the variables template fi # cp /usr/local/share/uefi-firmware/BHYVE_UEFI_VARS.fd /path/to/vm-image/BHYVE_UEFI_VARS.fd .... -Then, add that variables file into your bhyve arguments: +Then, add that variables file to the bhyve arguments: [source,shell] .... @@ -1641,7 +1641,7 @@ A detailed description for this process can be found on the link:https://wiki.fr [WARNING] ==== Modifying Windows installation media and running Windows guests without a TPM module are unsupported by the manufacturer. -Consider your application and use case before implementing such approaches. +Consider the application and use case before implementing such approaches. ==== [[virtualization-bhyve-zfs]] @@ -1664,7 +1664,7 @@ When starting the VM, specify the ZFS volume as the disk drive: -l com1,stdio -c 4 -m 1024M linuxguest .... -If you are using ZFS for the host as well as inside a guest, keep in mind the competing memory pressure of both systems caching the virtual machine's contents. +When using ZFS for the host as well as inside a guest, keep in mind the competing memory pressure of both systems caching the virtual machine's contents. To alleviate this, consider setting the host's ZFS filesystems to use metadata-only cache. To do this, apply the following settings to ZFS filesystems on the host, replacing `<name>` with the name of the specific zvol dataset name of the virtual machine. @@ -1762,7 +1762,7 @@ To verify successful activation of the snapshot feature, enter and check if the output lists a `--suspend` flag. If the flag is missing, the feature did not activate correctly. -Then, you can snapshot and suspend a running virtual machine of your choice: +Then, snapshot and suspend a running virtual machine of choice: [source,shell] .... @@ -1877,7 +1877,7 @@ add path 'tap10*' unhide [NOTE] ==== -If there's another devfs rule with the numeric ID 100 in your [.filename]#/etc/devfs.rules# file, replace the one in the listing with another yet unused ID number. +If there's another devfs rule with the numeric ID 100 in the [.filename]#/etc/devfs.rules# file, replace the one in the listing with another yet unused ID number. ==== [NOTE] @@ -1907,8 +1907,8 @@ Those rules can be expanded and varied with different guest and interface names [NOTE] ==== -If you intend to use bhyve on the host as well as in a one or more jails, remember that [.filename]#tap# and [.filename]#nmdm# interface names will operate in a shared environment. -For example, you can use [.filename]#/dev/nmdmbhyve0# only either for bhyve on the host or in a jail. +When intending to use bhyve on the host as well as in a one or more jails, remember that [.filename]#tap# and [.filename]#nmdm# interface names will operate in a shared environment. +For example, use [.filename]#/dev/nmdmbhyve0# only either for bhyve on the host or in a jail. ==== Restart devfs for the changes to be loaded: @@ -1918,8 +1918,8 @@ Restart devfs for the changes to be loaded: # service devfs restart .... -Then add a definition for your new jail into [.filename]#/etc/jail.conf# or [.filename]#/etc/jail.conf.d#. -Replace the interface number [.filename]#$if# and IP address with your personal variations. +Then add a definition for the new jail into [.filename]#/etc/jail.conf# or [.filename]#/etc/jail.conf.d#. +Replace the interface number [.filename]#$if# and IP address with personal variations. .Using NAT or routed traffic with a firewall [example] @@ -1937,7 +1937,7 @@ bhyve { exec.clean; - host.hostname = "your-hostname-here"; + host.hostname = "the-hostname-here"; vnet; vnet.interface = "jail${if}"; path = "/jails/${name}"; @@ -1955,7 +1955,7 @@ bhyve { } .... -This example assumes use of a firewall like `pf` or `ipfw` to NAT your jail traffic. +This example assumes use of a firewall like `pf` or `ipfw` to NAT the jail traffic. See the crossref:firewalls[,Firewalls] chapter for more details on the available options to implement this. ==== .Using a bridged network connection @@ -1974,7 +1974,7 @@ bhyve { exec.clean; - host.hostname = "your-hostname-here"; + host.hostname = "the-hostname-here"; vnet; vnet.interface = "jail${if}"; path = "/jails/${name}"; @@ -1995,7 +1995,7 @@ bhyve { [NOTE] ==== -If you previously replaced the devfs ruleset ID 100 in [.filename]#/etc/devfs.rules# with your own unique number, remember to replace the numeric ID also in your [.filename]#jails.conf# too. +Having previously replaced the devfs ruleset ID 100 in [.filename]#/etc/devfs.rules# with a custom unique number, remember to replace the numeric ID also in the [.filename]#jails.conf# too. ==== [[virtualization-bhyve-jailed-config]] @@ -2023,7 +2023,7 @@ Restart and enable the jail: # service jail restart bhyve .... -Afterwards, you can create a virtual machine within the jail. +Afterwards, create a virtual machine within the jail. For a FreeBSD guest, download an installation ISO first: [source,shell] @@ -2052,7 +2052,7 @@ Skipping this step may cause the following error message when starting `bhyve`: `vm_open: vm-name could not be opened. No such file or directory` ==== -Finally, use your preferred way of starting the guest. +Finally, use the preferred way of starting the guest. .Starting with `vmrun.sh` and ZFS [example] @@ -2083,7 +2083,7 @@ Using `vmrun.sh` on a UFS filesystem: .Starting bhyve for an UEFI guest with ZFS [example] ==== -If instead you want to use an UEFI guest, remember to first install the required firmware package package:sysutils/bhyve-firmware[] in the jail: +When wanting to use an UEFI guest, remember to first install the required firmware package package:sysutils/bhyve-firmware[] in the jail: [source,shell] .... @@ -2106,7 +2106,7 @@ Then use `bhyve` directly: bhyvevm0 .... -This will allow you to connect to your virtual machine `bhyvevm0` through VNC as well as a serial console at [.filename]#/dev/nmdbbhyve0B#. +This allows connecting to the virtual machine `bhyvevm0` through VNC as well as a serial console at [.filename]#/dev/nmdbbhyve0B#. ==== [[virtualization-bhyve-nmdm]] @@ -2139,7 +2139,7 @@ For security reasons, it's therefore recommended to logout before disconnecting. The number in the [.filename]#nmdm# device path must be unique for each virtual machine and must not be used by any other processes before bhyve starts. The number can be chosen arbitrarily and does not need to be taken from a consecutive sequence of numbers. The device node pair (i.e. [.filename]#/dev/nmdm0a# and [.filename]#/dev/nmdm0b#) are created dynamically when bhyve connects its console and destroyed when it shuts down. -Keep this in mind when creating scripts to start your virtual machines: you need to make sure that all virtual machines are assigned unique [.filename]#nmdm# devices. +Keep this in mind when creating scripts to start the virtual machines: make sure that all virtual machines are assigned unique [.filename]#nmdm# devices. [[virtualization-bhyve-managing]] === Managing Virtual Machines @@ -2225,7 +2225,7 @@ In order to configure the system to start bhyve guests at boot time, some config [.procedure] . [.filename]#/etc/sysctl.conf# + -When using [.filename]#tap# interfaces as network backend, you either need to manually set each used [.filename]#tap# interface to UP or simply set the following sysctl: +When using [.filename]#tap# interfaces as network backend, either manually set each used [.filename]#tap# interface to UP or simply set the following sysctl: + [.programlisting] .... @@ -2234,9 +2234,9 @@ net.link.tap.up_on_open=1 . [.filename]#/etc/rc.conf# + -To connect your virtual machine's [.filename]#tap# device to the network via a [.filename]#bridge#, you need to persist the device settings in [.filename]#/etc/rc.conf#. -Additionally, you can load the necessary kernel modules `vmm` for bhyve and `nmdm` for [.filename]#nmdm# devices through the `kld_list` configuration variable. -When configuring `ifconfig_bridge0`, make sure to replace `<ipaddr>/<netmask>` with the actual IP address of your physical interface ([.filename]#igb0# in this example) and remove IP settings from your physical device. +To connect the virtual machine's [.filename]#tap# device to the network via a [.filename]#bridge#, persisting the device settings in [.filename]#/etc/rc.conf# is needed. +Additionally, load the necessary kernel modules `vmm` for bhyve and `nmdm` for [.filename]#nmdm# devices through the `kld_list` configuration variable. +When configuring `ifconfig_bridge0`, make sure to replace `<ipaddr>/<netmask>` with the actual IP address of the physical interface ([.filename]#igb0# in this example) and remove IP settings from the physical device. + [source,shell] .... @@ -2250,7 +2250,7 @@ When configuring `ifconfig_bridge0`, make sure to replace `<ipaddr>/<netmask>` w .Setting the IP for a bridge device [example] ==== -For a host with an _igb0_ interface connected to the network with IP `10.10.10.1` and netmask `255.255.255.0`, you would use the following commands: +For a host with an _igb0_ interface connected to the network with IP `10.10.10.1` and netmask `255.255.255.0`, use the following commands: [source,shell] .... @@ -2263,7 +2263,7 @@ For a host with an _igb0_ interface connected to the network with IP `10.10.10.1 [WARNING] ==== -Modifying the IP address configuration of a system may lock you out if you are executing these commands while you are connected remotely (i.e. via SSH)! +Modifying the IP address configuration of a system may terminate the current remote connection (e.g., via SSH), causing a lock out. Take precautions to maintain system access or make those modifications while logged in on a local terminal session. ==== @@ -2509,9 +2509,9 @@ This section contains basic information in order to help troubleshoot issues fou ==== Host Boot Troubleshooting Please note that the following troubleshooting tips are intended for Xen(TM) 4.11 or newer. -If you are still using Xen(TM) 4.7 and having issues, consider migrating to a newer version of Xen(TM). +When still using Xen(TM) 4.7 and having issues, consider migrating to a newer version of Xen(TM). -In order to troubleshoot host boot issues, you will likely need a serial cable, or a debug USB cable. +In order to troubleshoot host boot issues, a serial cable or a debug USB cable is needed. Verbose Xen(TM) boot output can be obtained by adding options to the `xen_cmdline` option found in [.filename]#loader.conf#. A couple of relevant debug options are: @@ -2555,6 +2555,6 @@ libxl: debug: libxl_dom.c:988:libxl__load_hvm_firmware_module: Loading BIOS: /us .... If the verbose output does not help diagnose the issue, there are also QEMU and Xen(TM) toolstack logs in [.filename]#/var/log/xen#. -Note that the name of the domain is appended to the log name, so if the domain is named `freebsd` you should find a [.filename]#/var/log/xen/xl-freebsd.log# and likely a [.filename]#/var/log/xen/qemu-dm-freebsd.log#. +Note that the name of the domain is appended to the log name, so if the domain is named `freebsd` find a [.filename]#/var/log/xen/xl-freebsd.log# and likely a [.filename]#/var/log/xen/qemu-dm-freebsd.log#. Both log files can contain useful information for debugging. -If none of this helps solve the issue, please send the description of the issue you are facing and as much information as possible to mailto:freebsd-xen@FreeBSD.org[freebsd-xen@FreeBSD.org] and mailto:xen-devel@lists.xenproject.org[xen-devel@lists.xenproject.org] in order to get help. +If none of this helps solve the issue, please send the description of the issue and as much information as possible to mailto:freebsd-xen@FreeBSD.org[freebsd-xen@FreeBSD.org] and mailto:xen-devel@lists.xenproject.org[xen-devel@lists.xenproject.org] to get help. diff --git a/documentation/content/pt-br/books/fdp-primer/overview/_index.adoc b/documentation/content/pt-br/books/fdp-primer/overview/_index.adoc index 3cfbb5b603..605491e080 100644 --- a/documentation/content/pt-br/books/fdp-primer/overview/_index.adoc +++ b/documentation/content/pt-br/books/fdp-primer/overview/_index.adoc @@ -276,7 +276,7 @@ Revise a saída e edite os arquivos para corrigir os problemas informados e, em + [source, shell] .... -$ bmake run USE_RUBYGEMS=YES RUBY_CMD=$(brew --prefix ruby)/bin/ruby +$ bmake run USE_RUBYGEMS=YES RUBY_CMD="$(brew --prefix ruby)/bin/ruby" HUGO_CMD="$(brew --prefix hugo)/bin/hugo" .... . Adicione todos os arquivos com `git add .`, então revise o diff com `git diff`. Por exemplo: + |