Date: Sat, 12 Jun 2021 15:02:15 GMT From: Sergio Carlavilla Delgado <carlavilla@FreeBSD.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org Subject: git: b766aad819 - main - Use One Sentence Per Line in the FAQ Message-ID: <202106121502.15CF2Fm6005087@gitrepo.freebsd.org>
next in thread | raw e-mail | index | archive | help
The branch main has been updated by carlavilla: URL: https://cgit.FreeBSD.org/doc/commit/?id=b766aad81955ca8746248a67b3fa85148f0134ae commit b766aad81955ca8746248a67b3fa85148f0134ae Author: Sergio Carlavilla Delgado <carlavilla@FreeBSD.org> AuthorDate: 2021-06-12 15:01:13 +0000 Commit: Sergio Carlavilla Delgado <carlavilla@FreeBSD.org> CommitDate: 2021-06-12 15:01:13 +0000 Use One Sentence Per Line in the FAQ --- documentation/content/en/books/faq/_index.adoc | 1204 ++++++++++++++++++------ 1 file changed, 896 insertions(+), 308 deletions(-) diff --git a/documentation/content/en/books/faq/_index.adoc b/documentation/content/en/books/faq/_index.adoc index 5f5554c60f..852fbf7ce6 100644 --- a/documentation/content/en/books/faq/_index.adoc +++ b/documentation/content/en/books/faq/_index.adoc @@ -73,9 +73,11 @@ endif::[] [.abstract-title] Abstract -This is the Frequently Asked Questions (FAQ) for FreeBSD versions {rel-relx}, {rel2-relx}, and {rel3-relx}. Every effort has been made to make this FAQ as informative as possible; if you have any suggestions as to how it may be improved, send them to the {freebsd-doc}. +This is the Frequently Asked Questions (FAQ) for FreeBSD versions {rel-relx}, {rel2-relx}, and {rel3-relx}. +Every effort has been made to make this FAQ as informative as possible; if you have any suggestions as to how it may be improved, send them to the {freebsd-doc}. -The latest version of this document is always available from the link:{faq}[FreeBSD website]. It may also be downloaded as one large link:.[HTML] file with HTTP or as a variety of other formats from the https://download.freebsd.org/ftp/doc/[FreeBSD FTP server]. +The latest version of this document is always available from the link:{faq}[FreeBSD website]. +It may also be downloaded as one large link:.[HTML] file with HTTP or as a variety of other formats from the https://download.freebsd.org/ftp/doc/[FreeBSD FTP server]. ''' @@ -89,7 +91,9 @@ toc::[] FreeBSD is a modern operating system for desktops, laptops, servers, and embedded systems with support for a large number of https://www.FreeBSD.org/platforms/[platforms]. -It is based on U.C. Berkeley's "4.4BSD-Lite" release, with some "4.4BSD-Lite2" enhancements. It is also based indirectly on William Jolitz's port of U.C. Berkeley's "Net/2" to the i386(TM), known as "386BSD", though very little of the 386BSD code remains. +It is based on U.C. Berkeley's "4.4BSD-Lite" release, with some "4.4BSD-Lite2" enhancements. +It is also based indirectly on William Jolitz's port of U.C. Berkeley's "Net/2" to the i386(TM), known as "386BSD", +though very little of the 386BSD code remains. FreeBSD is used by companies, Internet Service Providers, researchers, computer professionals, students and home users all over the world in their work, education and recreation. @@ -103,26 +107,42 @@ The goal of the FreeBSD Project is to provide a stable and fast general purpose [[bsd-license-restrictions]] === Does the FreeBSD license have any restrictions? -Yes. Those restrictions do not control how the code is used, but how to treat the FreeBSD Project itself. The license itself is available at https://www.FreeBSD.org/copyright/freebsd-license/[license] and can be summarized like this: +Yes. Those restrictions do not control how the code is used, but how to treat the FreeBSD Project itself. +The license itself is available at https://www.FreeBSD.org/copyright/freebsd-license/[license] and can be summarized like this: * Do not claim that you wrote this. * Do not sue us if it breaks. * Do not remove or modify the license. -Many of us have a significant investment in the project and would certainly not mind a little financial compensation now and then, but we definitely do not insist on it. We believe that our first and foremost "mission" is to provide code to any and all comers, and for whatever purpose, so that the code gets the widest possible use and provides the widest possible benefit. This, we believe, is one of the most fundamental goals of Free Software and one that we enthusiastically support. +Many of us have a significant investment in the project and would certainly not mind a little financial compensation now and then, +but we definitely do not insist on it. +We believe that our first and foremost "mission" is to provide code to any and all comers, and for whatever purpose, so that the code gets the widest possible use and provides the widest possible benefit. +This, we believe, is one of the most fundamental goals of Free Software and one that we enthusiastically support. -Code in our source tree which falls under the https://www.FreeBSD.org/copyright/COPYING[GNU General Public License (GPL)] or https://www.FreeBSD.org/copyright/COPYING.LIB[GNU Library General Public License (LGPL)] comes with slightly more strings attached, though at least on the side of enforced access rather than the usual opposite. Due to the additional complexities that can evolve in the commercial use of GPL software, we do, however, endeavor to replace such software with submissions under the more relaxed https://www.FreeBSD.org/copyright/freebsd-license/[FreeBSD license] whenever possible. +Code in our source tree which falls under the https://www.FreeBSD.org/copyright/COPYING[GNU General Public License (GPL)] or https://www.FreeBSD.org/copyright/COPYING.LIB[GNU Library General Public License (LGPL)] comes with slightly more strings attached, though at least on the side of enforced access rather than the usual opposite. +Due to the additional complexities that can evolve in the commercial use of GPL software, we do, however, endeavor to replace such software with submissions under the more relaxed https://www.FreeBSD.org/copyright/freebsd-license/[FreeBSD license] whenever possible. [[replace-current-OS]] === Can FreeBSD replace my current operating system? For most people, yes. But this question is not quite that cut-and-dried. -Most people do not actually use an operating system. They use applications. The applications are what really use the operating system. FreeBSD is designed to provide a robust and full-featured environment for applications. It supports a wide variety of web browsers, office suites, email readers, graphics programs, programming environments, network servers, and much more. Most of these applications can be managed through the https://www.FreeBSD.org/ports/[Ports Collection]. +Most people do not actually use an operating system. +They use applications. +The applications are what really use the operating system. +FreeBSD is designed to provide a robust and full-featured environment for applications. +It supports a wide variety of web browsers, office suites, email readers, graphics programs, programming environments, network servers, and much more. +Most of these applications can be managed through the https://www.FreeBSD.org/ports/[Ports Collection]. -If an application is only available on one operating system, that operating system cannot just be replaced. Chances are, there is a very similar application on FreeBSD, however. As a solid office or Internet server or a reliable workstation, FreeBSD will almost certainly do everything you need. Many computer users across the world, including both novices and experienced UNIX(R) administrators, use FreeBSD as their only desktop operating system. +If an application is only available on one operating system, that operating system cannot just be replaced. +Chances are, there is a very similar application on FreeBSD, however. +As a solid office or Internet server or a reliable workstation, FreeBSD will almost certainly do everything you need. +Many computer users across the world, including both novices and experienced UNIX(R) administrators, use FreeBSD as their only desktop operating system. -Users migrating to FreeBSD from another UNIX(R)-like environment will find FreeBSD to be similar. Windows(R) and Mac OS(R) users may be interested in instead using https://www.ghostbsd.org/[GhostBSD], https://www.midnightbsd.org/[MidnightBSD] or https://www.nomadbsd.org/[NomadBSD] three FreeBSD-based desktop distributions. Non-UNIX(R) users should expect to invest some additional time learning the UNIX(R) way of doing things. This FAQ and the link:{handbook}[FreeBSD Handbook] are excellent places to start. +Users migrating to FreeBSD from another UNIX(R)-like environment will find FreeBSD to be similar. +Windows(R) and Mac OS(R) users may be interested in instead using https://www.ghostbsd.org/[GhostBSD], https://www.midnightbsd.org/[MidnightBSD] or https://www.nomadbsd.org/[NomadBSD] three FreeBSD-based desktop distributions. +Non-UNIX(R) users should expect to invest some additional time learning the UNIX(R) way of doing things. +This FAQ and the link:{handbook}[FreeBSD Handbook] are excellent places to start. [[why-called-FreeBSD]] === Why is it called FreeBSD? @@ -131,16 +151,21 @@ Users migrating to FreeBSD from another UNIX(R)-like environment will find FreeB * Full source for the operating system is freely available, and the minimum possible restrictions have been placed upon its use, distribution and incorporation into other work (commercial or non-commercial). * Anyone who has an improvement or bug fix is free to submit their code and have it added to the source tree (subject to one or two obvious provisions). -It is worth pointing out that the word "free" is being used in two ways here: one meaning "at no cost" and the other meaning "do whatever you like". Apart from one or two things you _cannot_ do with the FreeBSD code, for example pretending you wrote it, you can really do whatever you like with it. +It is worth pointing out that the word "free" is being used in two ways here: one meaning "at no cost" and the other meaning "do whatever you like". +Apart from one or two things you _cannot_ do with the FreeBSD code, for example pretending you wrote it, you can really do whatever you like with it. [[differences-to-other-bsds]] === What are the differences between FreeBSD and NetBSD, OpenBSD, and other open source BSD operating systems? -James Howard wrote a good explanation of the history and differences between the various projects, called https://jameshoward.us/archive/bsd-family-tree/[The BSD Family Tree] which goes a fair way to answering this question. Some of the information is out of date, but the history portion in particular remains accurate. +James Howard wrote a good explanation of the history and differences between the various projects, +called https://jameshoward.us/archive/bsd-family-tree/[The BSD Family Tree] which goes a fair way to answering this question. +Some of the information is out of date, but the history portion in particular remains accurate. -Most of the BSDs share patches and code, even today. All of the BSDs have common ancestry. +Most of the BSDs share patches and code, even today. +All of the BSDs have common ancestry. -The design goals of FreeBSD are described in <<FreeBSD-goals>>, above. The design goals of the other most popular BSDs may be summarized as follows: +The design goals of FreeBSD are described in <<FreeBSD-goals>>, above. +The design goals of the other most popular BSDs may be summarized as follows: * OpenBSD aims for operating system security above all else. The OpenBSD team wrote man:ssh[1] and man:pf[4], which have both been ported to FreeBSD. * NetBSD aims to be easily ported to other hardware platforms. @@ -149,34 +174,51 @@ The design goals of FreeBSD are described in <<FreeBSD-goals>>, above. The desig [[latest-version]] === What is the latest version of FreeBSD? -At any point in the development of FreeBSD, there can be multiple parallel branches. {rel-relx} releases are made from the {rel-stable} branch, and {rel2-relx} releases are made from the {rel2-stable} branch. +At any point in the development of FreeBSD, there can be multiple parallel branches. +{rel-relx} releases are made from the {rel-stable} branch, and {rel2-relx} releases are made from the {rel2-stable} branch. -Up until the release of 12.0, the {rel2-relx} series was the one known as _-STABLE_. However, as of {rel-head-relx}, the {rel2-relx} branch will be designated for an "extended support" status and receive only fixes for major problems, such as security-related fixes. +Up until the release of 12.0, the {rel2-relx} series was the one known as _-STABLE_. +However, as of {rel-head-relx}, the {rel2-relx} branch will be designated for an "extended support" status and receive only fixes for major problems, such as security-related fixes. -Releases are made <<release-freq,every few months>>. While many people stay more up-to-date with the FreeBSD sources (see the questions on <<current,FreeBSD-CURRENT>> and <<stable,FreeBSD-STABLE>>) than that, doing so is more of a commitment, as the sources are a moving target. +Releases are made <<release-freq,every few months>>. +While many people stay more up-to-date with the FreeBSD sources (see the questions on <<current,FreeBSD-CURRENT>> and <<stable,FreeBSD-STABLE>>) than that, doing so is more of a commitment, as the sources are a moving target. More information on FreeBSD releases can be found on the https://www.FreeBSD.org/releng/#release-build[Release Engineering page] and in man:release[7]. [[current]] === What is _FreeBSD-CURRENT_? -link:{handbook}#current[FreeBSD-CURRENT] is the development version of the operating system, which will in due course become the new FreeBSD-STABLE branch. As such, it is really only of interest to developers working on the system and die-hard hobbyists. See the link:{handbook}#current[relevant section] in the link:{handbook}[Handbook] for details on running _-CURRENT_. +link:{handbook}#current[FreeBSD-CURRENT] is the development version of the operating system, which will in due course become the new FreeBSD-STABLE branch. +As such, it is really only of interest to developers working on the system and die-hard hobbyists. +See the link:{handbook}#current[relevant section] in the link:{handbook}[Handbook] for details on running _-CURRENT_. -Users not familiar with FreeBSD should not use FreeBSD-CURRENT. This branch sometimes evolves quite quickly and due to mistake can be un-buildable at times. People that use FreeBSD-CURRENT are expected to be able to analyze, debug, and report problems. +Users not familiar with FreeBSD should not use FreeBSD-CURRENT. +This branch sometimes evolves quite quickly and due to mistake can be un-buildable at times. +People that use FreeBSD-CURRENT are expected to be able to analyze, debug, and report problems. [[stable]] === What is the FreeBSD-STABLE concept? -_FreeBSD-STABLE_ is the development branch from which major releases are made. Changes go into this branch at a slower pace and with the general assumption that they have first been tested in FreeBSD-CURRENT. However, at any given time, the sources for FreeBSD-STABLE may or may not be suitable for general use, as it may uncover bugs and corner cases that were not yet found in FreeBSD-CURRENT. Users who do not have the resources to perform testing should instead run the most recent release of FreeBSD. _FreeBSD-CURRENT_, on the other hand, has been one unbroken line since 2.0 was released. +_FreeBSD-STABLE_ is the development branch from which major releases are made. +Changes go into this branch at a slower pace and with the general assumption that they have first been tested in FreeBSD-CURRENT. +However, at any given time, the sources for FreeBSD-STABLE may or may not be suitable for general use, +as it may uncover bugs and corner cases that were not yet found in FreeBSD-CURRENT. +Users who do not have the resources to perform testing should instead run the most recent release of FreeBSD. +_FreeBSD-CURRENT_, on the other hand, has been one unbroken line since 2.0 was released. -For more detailed information on branches see "link:{releng}#rel-branch[FreeBSD Release Engineering: Creating the Release Branch]", the status of the branches and the upcoming release schedule can be found on the https://www.FreeBSD.org/releng[Release Engineering Information] page. +For more detailed information on branches see "link:{releng}#rel-branch[FreeBSD Release Engineering: Creating the Release Branch]", +the status of the branches and the upcoming release schedule can be found on the https://www.FreeBSD.org/releng[Release Engineering Information] page. -Version https://download.FreeBSD.org/ftp/releases/amd64/amd64/{rel121-current}-RELEASE/[{rel121-current}] is the latest release from the {rel-stable} branch; it was released in {rel121-current-date}. Version https://download.FreeBSD.org/ftp/releases/amd64/amd64/{rel113-current}-RELEASE/[{rel113-current}] is the latest release from the {rel2-stable} branch; it was released in {rel113-current-date}. +Version https://download.FreeBSD.org/ftp/releases/amd64/amd64/{rel121-current}-RELEASE/[{rel121-current}] is the latest release from the {rel-stable} branch; it was released in {rel121-current-date}. +Version https://download.FreeBSD.org/ftp/releases/amd64/amd64/{rel113-current}-RELEASE/[{rel113-current}] is the latest release from the {rel2-stable} branch; it was released in {rel113-current-date}. [[release-freq]] === When are FreeBSD releases made? -The {re} releases a new major version of FreeBSD about every 18 months and a new minor version about every 8 months, on average. Release dates are announced well in advance, so that the people working on the system know when their projects need to be finished and tested. A testing period precedes each release, to ensure that the addition of new features does not compromise the stability of the release. Many users regard this caution as one of the best things about FreeBSD, even though waiting for all the latest goodies to reach _-STABLE_ can be a little frustrating. +The {re} releases a new major version of FreeBSD about every 18 months and a new minor version about every 8 months, on average. +Release dates are announced well in advance, so that the people working on the system know when their projects need to be finished and tested. +A testing period precedes each release, to ensure that the addition of new features does not compromise the stability of the release. +Many users regard this caution as one of the best things about FreeBSD, even though waiting for all the latest goodies to reach _-STABLE_ can be a little frustrating. More information on the release engineering process (including a schedule of upcoming releases) can be found on the https://www.FreeBSD.org/releng/[release engineering] pages on the FreeBSD Web site. @@ -185,14 +227,16 @@ For people who need or want a little more excitement, binary snapshots are made [[snapshot-freq]] === When are FreeBSD snapshots made? -FreeBSD link:https://www.FreeBSD.org/snapshots/[snapshot] releases are made based on the current state of the _-CURRENT_ and _-STABLE_ branches. The goals behind each snapshot release are: +FreeBSD link:https://www.FreeBSD.org/snapshots/[snapshot] releases are made based on the current state of the _-CURRENT_ and _-STABLE_ branches. +The goals behind each snapshot release are: * To test the latest version of the installation software. * To give people who would like to run _-CURRENT_ or _-STABLE_ but who do not have the time or bandwidth to follow it on a day-to-day basis an easy way of bootstrapping it onto their systems. * To preserve a fixed reference point for the code in question, just in case we break something really badly later. (Although Subversion normally prevents anything horrible like this happening.) * To ensure that all new features and fixes in need of testing have the greatest possible number of potential testers. -No claims are made that any _-CURRENT_ snapshot can be considered "production quality" for any purpose. If a stable and fully tested system is needed, stick to full releases. +No claims are made that any _-CURRENT_ snapshot can be considered "production quality" for any purpose. +If a stable and fully tested system is needed, stick to full releases. Snapshot releases are directly available from link:https://www.FreeBSD.org/snapshots/[snapshot]. @@ -201,9 +245,12 @@ Official snapshots are generated on a regular basis for all actively developed b [[responsible]] === Who is responsible for FreeBSD? -The key decisions concerning the FreeBSD project, such as the overall direction of the project and who is allowed to add code to the source tree, are made by a link:https://www.FreeBSD.org/administration#t-core[core team] of 9 people. There is a much larger team of more than 350 link:{contributors}#staff-committers[committers] who are authorized to make changes directly to the FreeBSD source tree. +The key decisions concerning the FreeBSD project, such as the overall direction of the project and who is allowed to add code to the source tree, +are made by a link:https://www.FreeBSD.org/administration#t-core[core team] of 9 people. +There is a much larger team of more than 350 link:{contributors}#staff-committers[committers] who are authorized to make changes directly to the FreeBSD source tree. -However, most non-trivial changes are discussed in advance in the <<mailing,mailing lists>>, and there are no restrictions on who may take part in the discussion. +However, most non-trivial changes are discussed in advance in the <<mailing,mailing lists>>, +and there are no restrictions on who may take part in the discussion. [[where-get]] === Where can I get FreeBSD? @@ -236,9 +283,11 @@ The project produces a wide range of documentation, available online from this l [[doc-formats]] === Is the documentation available in other formats, such as plain text (ASCII), or PDF? -Yes. The documentation is available in a number of different formats and compression schemes on the FreeBSD FTP site, in the https://download.freebsd.org/ftp/doc/[/ftp/doc/] directory. +Yes. The documentation is available in a number of different formats and compression schemes on the FreeBSD FTP site, +in the https://download.freebsd.org/ftp/doc/[/ftp/doc/] directory. -The documentation is categorized in a number of different ways. These include: +The documentation is categorized in a number of different ways. +These include: * The document's name, such as `faq`, or `handbook`. * The document's language and encoding. These are based on the locale names found under [.filename]#/usr/share/locale# on a FreeBSD system. The current languages and encodings are as follows: @@ -336,13 +385,15 @@ Some documents may not be available in all languages. .. Where the format is `html-split`, the files are bundled up using man:tar[1]. The resulting [.filename]#.tar# is then compressed using the compression schemes detailed in the next point. .. All the other formats generate one file. For example, [.filename]#article.pdf#, [.filename]#book.html#, and so on. + -These files are then compressed using either the `zip` or `bz2` compression schemes. man:tar[1] can be used to uncompress these files. +These files are then compressed using either the `zip` or `bz2` compression schemes. +man:tar[1] can be used to uncompress these files. + So the PDF version of the Handbook, compressed using `bzip2` will be stored in a file called [.filename]#book.pdf.bz2# in the [.filename]#handbook/# directory. After choosing the format and compression mechanism, download the compressed files, uncompress them, and then copy the appropriate documents into place. -For example, the split HTML version of the FAQ, compressed using man:bzip2[1], can be found in [.filename]#doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2# To download and uncompress that file, type: +For example, the split HTML version of the FAQ, compressed using man:bzip2[1], +can be found in [.filename]#doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2# To download and uncompress that file, type: [source,shell] .... @@ -350,7 +401,9 @@ For example, the split HTML version of the FAQ, compressed using man:bzip2[1], c # tar xvf book.html-split.tar.bz2 .... -If the file is compressed, tar will automatically detect the appropriate format and decompress it correctly, resulting in a collection of [.filename]#.html# files. The main one is called [.filename]#index.html#, which will contain the table of contents, introductory material, and links to the other parts of the document. +If the file is compressed, tar will automatically detect the appropriate format and decompress it correctly, +resulting in a collection of [.filename]#.html# files. +The main one is called [.filename]#index.html#, which will contain the table of contents, introductory material, and links to the other parts of the document. [[mailing]] === Where do I find info on the FreeBSD mailing lists? What FreeBSD news groups are available? @@ -371,7 +424,8 @@ Yes, most major IRC networks host a FreeBSD chat channel: The FreeBSD wiki has a https://wiki.freebsd.org/IRC/Channels[good list] of IRC channels. -Each of these channels are distinct and are not connected to each other. Since their chat styles differ, try each to find one suited to your chat style. +Each of these channels are distinct and are not connected to each other. +Since their chat styles differ, try each to find one suited to your chat style. [[forums]] === Are there any web based forums to discuss FreeBSD? @@ -381,9 +435,12 @@ The official FreeBSD forums are located at https://forums.FreeBSD.org/[https://f [[training]] === Where can I get commercial FreeBSD training and support? -http://www.ixsystems.com[iXsystems, Inc.], parent company of the http://www.freebsdmall.com/[FreeBSD Mall], provides commercial FreeBSD and TrueOS software http://www.ixsystems.com/support[support], in addition to FreeBSD development and tuning solutions. +http://www.ixsystems.com[iXsystems, Inc.], parent company of the http://www.freebsdmall.com/[FreeBSD Mall], +provides commercial FreeBSD and TrueOS software http://www.ixsystems.com/support[support], +in addition to FreeBSD development and tuning solutions. -BSD Certification Group, Inc. provides system administration certifications for DragonFly BSD, FreeBSD, NetBSD, and OpenBSD. Refer to http://www.BSDCertification.org[their site] for more information. +BSD Certification Group, Inc. provides system administration certifications for DragonFly BSD, FreeBSD, NetBSD, and OpenBSD. +Refer to http://www.BSDCertification.org[their site] for more information. Any other organizations providing training and support should contact the Project to be listed here. @@ -393,7 +450,10 @@ Any other organizations providing training and support should contact the Projec [[which-architecture]] === Which platform should I download? I have a 64 bit capable Intel(R) CPU, but I only see amd64. -amd64 is the term FreeBSD uses for 64-bit compatible x86 architectures (also known as "x86-64" or "x64"). Most modern computers should use amd64. Older hardware should use i386. When installing on a non-x86-compatible architecture, select the platform which best matches the hardware. +amd64 is the term FreeBSD uses for 64-bit compatible x86 architectures (also known as "x86-64" or "x64"). +Most modern computers should use amd64. +Older hardware should use i386. +When installing on a non-x86-compatible architecture, select the platform which best matches the hardware. [[floppy-download]] === Which file do I download to get FreeBSD? @@ -428,7 +488,9 @@ Full instructions on this procedure and a little bit more about installation iss This can be caused by not downloading the image in _binary_ mode when using FTP. -Some FTP clients default their transfer mode to _ascii_ and attempt to change any end-of-line characters received to match the conventions used by the client's system. This will almost invariably corrupt the boot image. Check the SHA-256 checksum of the downloaded boot image: if it is not _exactly_ that on the server, then the download process is suspect. +Some FTP clients default their transfer mode to _ascii_ and attempt to change any end-of-line characters received to match the conventions used by the client's system. +This will almost invariably corrupt the boot image. +Check the SHA-256 checksum of the downloaded boot image: if it is not _exactly_ that on the server, then the download process is suspect. When using a command line FTP client, type _binary_ at the FTP command prompt after getting connected to the server and before starting the download of the image. @@ -440,17 +502,23 @@ Installation instructions can be found at link:{handbook}#bsdinstall/[Handbook e [[custom-boot-floppy]] === How can I make my own custom release or install disk? -Customized FreeBSD installation media can be created by building a custom release. Follow the instructions in the link:{releng}[Release Engineering] article. +Customized FreeBSD installation media can be created by building a custom release. +Follow the instructions in the link:{releng}[Release Engineering] article. [[windows-coexist]] === Can Windows(R) co-exist with FreeBSD? (x86-specific) -If Windows(R) is installed first, then yes. FreeBSD's boot manager will then manage to boot Windows(R) and FreeBSD. If Windows(R) is installed afterwards, it will overwrite the boot manager. If that happens, see the next section. +If Windows(R) is installed first, then yes. +FreeBSD's boot manager will then manage to boot Windows(R) and FreeBSD. +If Windows(R) is installed afterwards, it will overwrite the boot manager. +If that happens, see the next section. [[bootmanager-restore]] === Another operating system destroyed my Boot Manager. How do I get it back? (x86-specific) -This depends upon the boot manager. The FreeBSD boot selection menu can be reinstalled using man:boot0cfg[8]. For example, to restore the boot menu onto the disk _ada0_: +This depends upon the boot manager. +The FreeBSD boot selection menu can be reinstalled using man:boot0cfg[8]. +For example, to restore the boot menu onto the disk _ada0_: [source,shell] .... @@ -469,38 +537,59 @@ For more complex situations, including GPT disks, see man:gpart[8]. [[need-complete-sources]] === Do I need to install the source? -In general, no. There is nothing in the base system which requires the presence of the source to operate. Some ports, like package:sysutils/lsof[], will not build unless the source is installed. In particular, if the port builds a kernel module or directly operates on kernel structures, the source must be installed. +In general, no. +There is nothing in the base system which requires the presence of the source to operate. +Some ports, like package:sysutils/lsof[], will not build unless the source is installed. +In particular, if the port builds a kernel module or directly operates on kernel structures, the source must be installed. [[need-kernel]] === Do I need to build a kernel? -Usually not. The supplied `GENERIC` kernel contains the drivers an ordinary computer will need. man:freebsd-update[8], the FreeBSD binary upgrade tool, cannot upgrade custom kernels, another reason to stick with the `GENERIC` kernel when possible. For computers with very limited RAM, such as embedded systems, it may be worthwhile to build a smaller custom kernel containing just the required drivers. +Usually not. +The supplied `GENERIC` kernel contains the drivers an ordinary computer will need. +man:freebsd-update[8], the FreeBSD binary upgrade tool, cannot upgrade custom kernels, +another reason to stick with the `GENERIC` kernel when possible. +For computers with very limited RAM, such as embedded systems, +it may be worthwhile to build a smaller custom kernel containing just the required drivers. [[password-encryption]] === Should I use DES, Blowfish, or MD5 passwords and how do I specify which form my users receive? -FreeBSD uses _SHA512_ by default. DES passwords are still available for backwards compatibility with operating systems that still use the less secure password format. FreeBSD also supports the Blowfish and MD5 password formats. Which password format to use for new passwords is controlled by the `passwd_format` login capability in [.filename]#/etc/login.conf#, which takes values of `des`, `blf` (if these are available) or `md5`. See the man:login.conf[5] manual page for more information about login capabilities. +FreeBSD uses _SHA512_ by default. +DES passwords are still available for backwards compatibility with operating systems that still use the less secure password format. +FreeBSD also supports the Blowfish and MD5 password formats. +Which password format to use for new passwords is controlled by the `passwd_format` login capability in [.filename]#/etc/login.conf#, +which takes values of `des`, `blf` (if these are available) or `md5`. +See the man:login.conf[5] manual page for more information about login capabilities. [[ffs-limits]] === What are the limits for FFS file systems? -For FFS file systems, the largest file system is practically limited by the amount of memory required to man:fsck[8] the file system. man:fsck[8] requires one bit per fragment, which with the default fragment size of 4 KB equates to 32 MB of memory per TB of disk. This does mean that on architectures which limit userland processes to 2 GB (e.g., i386(TM)), the maximum man:fsck[8]'able filesystem is ~60 TB. +For FFS file systems, the largest file system is practically limited by the amount of memory required to man:fsck[8] the file system. +man:fsck[8] requires one bit per fragment, which with the default fragment size of 4 KB equates to 32 MB of memory per TB of disk. +This does mean that on architectures which limit userland processes to 2 GB (e.g., i386(TM)), the maximum man:fsck[8]'able filesystem is ~60 TB. If there was not a man:fsck[8] memory limit the maximum filesystem size would be 2 ^ 64 (blocks) * 32 KB => 16 Exa * 32 KB => 512 ZettaBytes. -The maximum size of a single FFS file is approximately 2 PB with the default block size of 32 KB. Each 32 KB block can point to 4096 blocks. With triple indirect blocks, the calculation is 32 KB * 12 + 32 KB * 4096 + 32 KB * 4096^2 + 32 KB * 4096^3. Increasing the block size to 64 KB will increase the max file size by a factor of 16. +The maximum size of a single FFS file is approximately 2 PB with the default block size of 32 KB. +Each 32 KB block can point to 4096 blocks. +With triple indirect blocks, the calculation is 32 KB * 12 + 32 KB * 4096 + 32 KB * 4096^2 + 32 KB * 4096^3. +Increasing the block size to 64 KB will increase the max file size by a factor of 16. [[archsw-readin-failed-error]] === Why do I get an error message, readin failed after compiling and booting a new kernel? -The world and kernel are out of sync. This is not supported. Be sure to use `make buildworld` and `make buildkernel` to update the kernel. +The world and kernel are out of sync. +This is not supported. +Be sure to use `make buildworld` and `make buildkernel` to update the kernel. Boot the system by specifying the kernel directly at the second stage, pressing any key when the `|` shows up before loader is started. [[general-configuration-tool]] === Is there a tool to perform post-installation configuration tasks? -Yes. bsdconfig provides a nice interface to configure FreeBSD post-installation. +Yes. +bsdconfig provides a nice interface to configure FreeBSD post-installation. [[hardware]] == Hardware Compatibility @@ -511,30 +600,51 @@ Yes. bsdconfig provides a nice interface to configure FreeBSD post-installation. [[which-hardware-to-get]] ==== I want to get a piece of hardware for my FreeBSD system. Which model/brand/type is best? -This is discussed continually on the FreeBSD mailing lists but is to be expected since hardware changes so quickly. Read through the Hardware Notes for FreeBSD link:{u-rel121-hardware}[{rel121-current}] or link:{u-rel113-hardware}[{rel113-current}] and search the mailing list https://www.FreeBSD.org/search/#mailinglists[archives] before asking about the latest and greatest hardware. Chances are a discussion about that type of hardware took place just last week. +This is discussed continually on the FreeBSD mailing lists but is to be expected since hardware changes so quickly. +Read through the Hardware Notes for FreeBSD link:{u-rel121-hardware}[{rel121-current}] or link:{u-rel113-hardware}[{rel113-current}] and search the mailing list https://www.FreeBSD.org/search/#mailinglists[archives] before asking about the latest and greatest hardware. +Chances are a discussion about that type of hardware took place just last week. -Before purchasing a laptop, check the archives for {freebsd-questions}, or possibly a specific mailing list for a particular hardware type. +Before purchasing a laptop, check the archives for {freebsd-questions}, +or possibly a specific mailing list for a particular hardware type. [[memory-upper-limitation]] ==== What are the limits for memory? -FreeBSD as an operating system generally supports as much physical memory (RAM) as the platform it is running on does. Keep in mind that different platforms have different limits for memory; for example i386(TM) without PAE supports at most 4 GB of memory (and usually less than that because of PCI address space) and i386(TM) with PAE supports at most 64 GB memory. As of FreeBSD 10, AMD64 platforms support up to 4 TB of physical memory. +FreeBSD as an operating system generally supports as much physical memory (RAM) as the platform it is running on does. +Keep in mind that different platforms have different limits for memory; +for example i386(TM) without PAE supports at most 4 GB of memory (and usually less than that because of PCI address space) and i386(TM) with PAE supports at most 64 GB memory. +As of FreeBSD 10, AMD64 platforms support up to 4 TB of physical memory. [[memory-i386-over-4gb]] ==== Why does FreeBSD report less than 4 GB memory when installed on an i386(TM) machine? -The total address space on i386(TM) machines is 32-bit, meaning that at most 4 GB of memory is addressable (can be accessed). Furthermore, some addresses in this range are reserved by hardware for different purposes, for example for using and controlling PCI devices, for accessing video memory, and so on. Therefore, the total amount of memory usable by the operating system for its kernel and applications is limited to significantly less than 4 GB. Usually, 3.2 GB to 3.7 GB is the maximum usable physical memory in this configuration. - -To access more than 3.2 GB to 3.7 GB of installed memory (meaning up to 4 GB but also more than 4 GB), a special tweak called PAE must be used. PAE stands for Physical Address Extension and is a way for 32-bit x86 CPUs to address more than 4 GB of memory. It remaps the memory that would otherwise be overlaid by address reservations for hardware devices above the 4 GB range and uses it as additional physical memory (see man:pae[4]). Using PAE has some drawbacks; this mode of memory access is a little bit slower than the normal (without PAE) mode and loadable modules (see man:kld[4]) are not supported. This means all drivers must be compiled into the kernel. - -The most common way to enable PAE is to build a new kernel with the special ready-provided kernel configuration file called [.filename]#PAE#, which is already configured to build a safe kernel. Note that some entries in this kernel configuration file are too conservative and some drivers marked as unready to be used with PAE are actually usable. A rule of thumb is that if the driver is usable on 64-bit architectures (like AMD64), it is also usable with PAE. When creating a custom kernel configuration file, PAE can be enabled by adding the following line: +The total address space on i386(TM) machines is 32-bit, meaning that at most 4 GB of memory is addressable (can be accessed). +Furthermore, some addresses in this range are reserved by hardware for different purposes, +for example for using and controlling PCI devices, for accessing video memory, and so on. +Therefore, the total amount of memory usable by the operating system for its kernel and applications is limited to significantly less than 4 GB. +Usually, 3.2 GB to 3.7 GB is the maximum usable physical memory in this configuration. + +To access more than 3.2 GB to 3.7 GB of installed memory (meaning up to 4 GB but also more than 4 GB), +a special tweak called PAE must be used. +PAE stands for Physical Address Extension and is a way for 32-bit x86 CPUs to address more than 4 GB of memory. +It remaps the memory that would otherwise be overlaid by address reservations for hardware devices above the 4 GB range and uses it as additional physical memory (see man:pae[4]). +Using PAE has some drawbacks; this mode of memory access is a little bit slower than the normal (without PAE) mode and loadable modules (see man:kld[4]) are not supported. +This means all drivers must be compiled into the kernel. + +The most common way to enable PAE is to build a new kernel with the special ready-provided kernel configuration file called [.filename]#PAE#, +which is already configured to build a safe kernel. +Note that some entries in this kernel configuration file are too conservative and some drivers marked as unready to be used with PAE are actually usable. +A rule of thumb is that if the driver is usable on 64-bit architectures (like AMD64), it is also usable with PAE. +When creating a custom kernel configuration file, PAE can be enabled by adding the following line: [.programlisting] .... options PAE .... -PAE is not much used nowadays because most new x86 hardware also supports running in 64-bit mode, known as AMD64 or Intel(R) 64. It has a much larger address space and does not need such tweaks. FreeBSD supports AMD64 and it is recommended that this version of FreeBSD be used instead of the i386(TM) version if 4 GB or more memory is required. +PAE is not much used nowadays because most new x86 hardware also supports running in 64-bit mode, known as AMD64 or Intel(R) 64. +It has a much larger address space and does not need such tweaks. +FreeBSD supports AMD64 and it is recommended that this version of FreeBSD be used instead of the i386(TM) version if 4 GB or more memory is required. [[compatibility-processors]] === Architectures and Processors @@ -542,21 +652,28 @@ PAE is not much used nowadays because most new x86 hardware also supports runnin [[architectures]] ==== Does FreeBSD support architectures other than the x86? -Yes. FreeBSD divides support into multiple tiers. Tier 1 architectures, such as i386 or amd64; are fully supported. Tiers 2 and 3 are supported on a best-effort basis. A full explanation of the tier system is available in the link:{committers-guide}#archs/[Committer's Guide.] +Yes. +FreeBSD divides support into multiple tiers. +Tier 1 architectures, such as i386 or amd64; are fully supported. +Tiers 2 and 3 are supported on a best-effort basis. +A full explanation of the tier system is available in the link:{committers-guide}#archs/[Committer's Guide.] A complete list of supported architectures can be found on the https://www.FreeBSD.org/platforms/[platforms page.] [[smp-support]] ==== Does FreeBSD support Symmetric Multiprocessing (SMP)? -FreeBSD supports symmetric multi-processor (SMP) on all non-embedded platforms (e.g, i386, amd64, etc.). SMP is also supported in arm and MIPS kernels, although some CPUs may not support this. FreeBSD's SMP implementation uses fine-grained locking, and performance scales nearly linearly with number of CPUs. +FreeBSD supports symmetric multi-processor (SMP) on all non-embedded platforms (e.g, i386, amd64, etc.). +SMP is also supported in arm and MIPS kernels, although some CPUs may not support this. +FreeBSD's SMP implementation uses fine-grained locking, and performance scales nearly linearly with number of CPUs. man:smp[4] has more details. [[microcode]] ==== What is microcode? How do I install Intel(R) CPU microcode updates? -Microcode is a method of programmatically implementing hardware level instructions. This allows for CPU bugs to be fixed without replacing the on board chip. +Microcode is a method of programmatically implementing hardware level instructions. +This allows for CPU bugs to be fixed without replacing the on board chip. Install package:sysutils/devcpu-data[], then add: @@ -581,7 +698,8 @@ See the complete list in the Hardware Notes for FreeBSD link:{u-rel121-hardware} [[moused]] ==== Is it possible to use a mouse outside the X Window system? -The default console driver, man:vt[4], provides the ability to use a mouse pointer in text consoles to cut & paste text. Run the mouse daemon, man:moused[8], and turn on the mouse pointer in the virtual console: +The default console driver, man:vt[4], provides the ability to use a mouse pointer in text consoles to cut & paste text. +Run the mouse daemon, man:moused[8], and turn on the mouse pointer in the virtual console: [source,shell] .... @@ -589,37 +707,53 @@ The default console driver, man:vt[4], provides the ability to use a mouse point # vidcontrol -m on .... -Where _xxxx_ is the mouse device name and _yyyy_ is a protocol type for the mouse. The mouse daemon can automatically determine the protocol type of most mice, except old serial mice. Specify the `auto` protocol to invoke automatic detection. If automatic detection does not work, see the man:moused[8] manual page for a list of supported protocol types. +Where _xxxx_ is the mouse device name and _yyyy_ is a protocol type for the mouse. +The mouse daemon can automatically determine the protocol type of most mice, except old serial mice. +Specify the `auto` protocol to invoke automatic detection. +If automatic detection does not work, see the man:moused[8] manual page for a list of supported protocol types. -For a PS/2 mouse, add `moused_enable="YES"` to [.filename]#/etc/rc.conf# to start the mouse daemon at boot time. Additionally, to use the mouse daemon on all virtual terminals instead of just the console, add `allscreens_flags="-m on"` to [.filename]#/etc/rc.conf#. +For a PS/2 mouse, add `moused_enable="YES"` to [.filename]#/etc/rc.conf# to start the mouse daemon at boot time. +Additionally, to use the mouse daemon on all virtual terminals instead of just the console, add `allscreens_flags="-m on"` to [.filename]#/etc/rc.conf#. -When the mouse daemon is running, access to the mouse must be coordinated between the mouse daemon and other programs such as X Windows. Refer to the FAQ<<x-and-moused,Why does my mouse not work with X?>> for more details on this issue. +When the mouse daemon is running, access to the mouse must be coordinated between the mouse daemon and other programs such as X Windows. +Refer to the FAQ <<x-and-moused,Why does my mouse not work with X?>> for more details on this issue. [[text-mode-cut-paste]] ==== How do I cut and paste text with a mouse in the text console? -It is not possible to remove data using the mouse. However, it is possible to copy and paste. Once the mouse daemon is running as described in the <<moused,previous question>>, hold down button 1 (left button) and move the mouse to select a region of text. Then, press button 2 (middle button) to paste it at the text cursor. Pressing button 3 (right button) will "extend" the selected region of text. +It is not possible to remove data using the mouse. +However, it is possible to copy and paste. +Once the mouse daemon is running as described in the <<moused,previous question>>, +hold down button 1 (left button) and move the mouse to select a region of text. +Then, press button 2 (middle button) to paste it at the text cursor. +Pressing button 3 (right button) will "extend" the selected region of text. -If the mouse does not have a middle button, it is possible to emulate one or remap buttons using mouse daemon options. See the man:moused[8] manual page for details. +If the mouse does not have a middle button, it is possible to emulate one or remap buttons using mouse daemon options. +See the man:moused[8] manual page for details. [[mouse-wheel-buttons]] ==== My mouse has a fancy wheel and buttons. Can I use them in FreeBSD? -The answer is, unfortunately, "It depends". These mice with additional features require specialized driver in most cases. Unless the mouse device driver or the user program has specific support for the mouse, it will act just like a standard two, or three button mouse. +The answer is, unfortunately, "It depends". +These mice with additional features require specialized driver in most cases. +Unless the mouse device driver or the user program has specific support for the mouse, +it will act just like a standard two, or three button mouse. For the possible usage of wheels in the X Window environment, refer to <<x-and-wheel,that section>>. [[keyboard-delete-key]] ==== How do I use my delete key in sh and csh? -For the Bourne Shell, add the following lines to [.filename]#~/.shrc#. See man:sh[1] and man:editrc[5]. +For the Bourne Shell, add the following lines to [.filename]#~/.shrc#. +See man:sh[1] and man:editrc[5]. [.programlisting] .... bind ^[[3~ ed-delete-next-char # for xterm .... -For the C Shell, add the following lines to [.filename]#~/.cshrc#. See man:csh[1]. +For the C Shell, add the following lines to [.filename]#~/.cshrc#. +See man:csh[1]. [.programlisting] .... @@ -632,7 +766,8 @@ bindkey ^[[3~ delete-char # for xterm [[es1370-silent-pcm]] ==== Workarounds for no sound from my man:pcm[4] sound card? -Some sound cards set their output volume to 0 at every boot. Run the following command every time the machine boots: +Some sound cards set their output volume to 0 at every boot. +Run the following command every time the machine boots: [source,shell] .... @@ -642,7 +777,8 @@ Some sound cards set their output volume to 0 at every boot. Run the following c [[power-management-support]] ==== Does FreeBSD support power management on my laptop? -FreeBSD supports the ACPI features found in modern hardware. Further information can be found in man:acpi[4]. +FreeBSD supports the ACPI features found in modern hardware. +Further information can be found in man:acpi[4]. [[troubleshoot]] == Troubleshooting @@ -652,20 +788,29 @@ FreeBSD supports the ACPI features found in modern hardware. Further information The most likely reason is the difference between physical memory addresses and virtual addresses. -The convention for most PC hardware is to use the memory area between 3.5 GB and 4 GB for a special purpose (usually for PCI). This address space is used to access PCI hardware. As a result real, physical memory cannot be accessed by that address space. +The convention for most PC hardware is to use the memory area between 3.5 GB and 4 GB for a special purpose (usually for PCI). +This address space is used to access PCI hardware. +As a result real, physical memory cannot be accessed by that address space. -What happens to the memory that should appear in that location is hardware dependent. Unfortunately, some hardware does nothing and the ability to use that last 500 MB of RAM is entirely lost. +What happens to the memory that should appear in that location is hardware dependent. +Unfortunately, some hardware does nothing and the ability to use that last 500 MB of RAM is entirely lost. -Luckily, most hardware remaps the memory to a higher location so that it can still be used. However, this can cause some confusion when watching the boot messages. +Luckily, most hardware remaps the memory to a higher location so that it can still be used. +However, this can cause some confusion when watching the boot messages. -On a 32-bit version of FreeBSD, the memory appears lost, since it will be remapped above 4 GB, which a 32-bit kernel is unable to access. In this case, the solution is to build a PAE enabled kernel. See the entry on memory limits for more information. +On a 32-bit version of FreeBSD, the memory appears lost, since it will be remapped above 4 GB, which a 32-bit kernel is unable to access. +In this case, the solution is to build a PAE enabled kernel. +See the entry on memory limits for more information. -On a 64-bit version of FreeBSD, or when running a PAE-enabled kernel, FreeBSD will correctly detect and remap the memory so it is usable. During boot, however, it may seem as if FreeBSD is detecting more memory than the system really has, due to the described remapping. This is normal and the available memory will be corrected as the boot process completes. +On a 64-bit version of FreeBSD, or when running a PAE-enabled kernel, FreeBSD will correctly detect and remap the memory so it is usable. +During boot, however, it may seem as if FreeBSD is detecting more memory than the system really has, due to the described remapping. +This is normal and the available memory will be corrected as the boot process completes. [[signal11]] === Why do my programs occasionally die with Signal 11 errors? -Signal 11 errors are caused when a process has attempted to access memory which the operating system has not granted it access to. If something like this is happening at seemingly random intervals, start investigating the cause. +Signal 11 errors are caused when a process has attempted to access memory which the operating system has not granted it access to. +If something like this is happening at seemingly random intervals, start investigating the cause. These problems can usually be attributed to either: @@ -674,7 +819,9 @@ These problems can usually be attributed to either: It is probably not a FreeBSD bug if the problem occurs compiling a program, but the activity that the compiler is carrying out changes each time. -For example, if `make buildworld` fails while trying to compile [.filename]#ls.c# into [.filename]#ls.o# and, when run again, it fails in the same place, this is a broken build. Try updating source and try again. If the compile fails elsewhere, it is almost certainly due to hardware. +For example, if `make buildworld` fails while trying to compile [.filename]#ls.c# into [.filename]#ls.o# and, when run again, it fails in the same place, this is a broken build. +Try updating source and try again. +If the compile fails elsewhere, it is almost certainly due to hardware. In the first case, use a debugger such as man:gdb[1] to find the point in the program which is attempting to access a bogus address and fix it. @@ -690,61 +837,93 @@ Regarding overclocking, it is far cheaper to have a slow system than a fried sys . Over-optimistic motherboard settings: the BIOS settings, and some motherboard jumpers, provide options to set various timings. The defaults are often sufficient, but sometimes setting the wait states on RAM too low, or setting the "RAM Speed: Turbo" option will cause strange behavior. A possible idea is to set to BIOS defaults, after noting the current settings first. . Unclean or insufficient power to the motherboard. Remove any unused I/O boards, hard disks, or CD-ROMs, or disconnect the power cable from them, to see if the power supply can manage a smaller load. Or try another power supply, preferably one with a little more power. For instance, if the current power supply is rated at 250 Watts, try one rated at 300 Watts. -Read the section on <<signal11,Signal 11>> for a further explanation and a discussion on how memory testing software or hardware can still pass faulty memory. There is an extensive FAQ on this at http://www.bitwizard.nl/sig11/[the SIG11 problem FAQ]. +Read the section on <<signal11,Signal 11>> for a further explanation and a discussion on how memory testing software or hardware can still pass faulty memory. +There is an extensive FAQ on this at http://www.bitwizard.nl/sig11/[the SIG11 problem FAQ]. -Finally, if none of this has helped, it is possibly a bug in FreeBSD. Follow <<access-pr,these instructions>> to send a problem report. +Finally, if none of this has helped, it is possibly a bug in FreeBSD. +Follow <<access-pr,these instructions>> to send a problem report. [[trap-12-panic]] === My system crashes with either Fatal trap 12: page fault in kernel mode, or panic:, and spits out a bunch of information. What should I do? -The FreeBSD developers are interested in these errors, but need more information than just the error message. Copy the full crash message. Then consult the FAQ section on <<kernel-panic-troubleshooting,kernel panics>>, build a debugging kernel, and get a backtrace. This might sound difficult, but does not require any programming skills. Just follow the instructions. +The FreeBSD developers are interested in these errors, but need more information than just the error message. +Copy the full crash message. +Then consult the FAQ section on <<kernel-panic-troubleshooting,kernel panics>>, build a debugging kernel, and get a backtrace. +This might sound difficult, but does not require any programming skills. +Just follow the instructions. [[proc-table-full]] === What is the meaning of the error maxproc limit exceeded by uid %i, please see tuning(7) and login.conf(5)? -The FreeBSD kernel will only allow a certain number of processes to exist at one time. The number is based on the `kern.maxusers` man:sysctl[8] variable. `kern.maxusers` also affects various other in-kernel limits, such as network buffers. If the machine is heavily loaded, increase `kern.maxusers`. This will increase these other system limits in addition to the maximum number of processes. +The FreeBSD kernel will only allow a certain number of processes to exist at one time. +The number is based on the `kern.maxusers` man:sysctl[8] variable. +`kern.maxusers` also affects various other in-kernel limits, such as network buffers. +If the machine is heavily loaded, increase `kern.maxusers`. +This will increase these other system limits in addition to the maximum number of processes. -To adjust the `kern.maxusers` value, see the link:{handbook}#kern-maxfiles[File/Process Limits] section of the Handbook. While that section refers to open files, the same limits apply to processes. +To adjust the `kern.maxusers` value, see the link:{handbook}#kern-maxfiles[File/Process Limits] section of the Handbook. +While that section refers to open files, the same limits apply to processes. -If the machine is lightly loaded but running a very large number of processes, adjust the `kern.maxproc` tunable by defining it in [.filename]#/boot/loader.conf#. The tunable will not get adjusted until the system is rebooted. For more information about tuning tunables, see man:loader.conf[5]. If these processes are being run by a single user, adjust `kern.maxprocperuid` to be one less than the new `kern.maxproc` value. It must be at least one less because one system program, man:init[8], must always be running. +If the machine is lightly loaded but running a very large number of processes, adjust the `kern.maxproc` tunable by defining it in [.filename]#/boot/loader.conf#. +The tunable will not get adjusted until the system is rebooted. +For more information about tuning tunables, see man:loader.conf[5]. +If these processes are being run by a single user, adjust `kern.maxprocperuid` to be one less than the new `kern.maxproc` value. +It must be at least one less because one system program, man:init[8], must always be running. [[remote-fullscreen]] === Why do full screen applications on remote machines misbehave? -The remote machine may be setting the terminal type to something other than `xterm` which is required by the FreeBSD console. Alternatively the kernel may have the wrong values for the width and height of the terminal. +The remote machine may be setting the terminal type to something other than `xterm` which is required by the FreeBSD console. +Alternatively the kernel may have the wrong values for the width and height of the terminal. -Check the value of the `TERM` environment variable is `xterm`. If the remote machine does not support that try `vt100`. +Check the value of the `TERM` environment variable is `xterm`. +If the remote machine does not support that try `vt100`. -Run `stty -a` to check what the kernel thinks the terminal dimensions are. If they are incorrect, they can be changed by running `stty rows _RR_ cols _CC_`. +Run `stty -a` to check what the kernel thinks the terminal dimensions are. +If they are incorrect, they can be changed by running `stty rows _RR_ cols _CC_`. -Alternatively, if the client machine has package:x11/xterm[] installed, then running `resize` will query the terminal for the correct dimensions and set them. +Alternatively, if the client machine has package:x11/xterm[] installed, +then running `resize` will query the terminal for the correct dimensions and set them. [[connection-delay]] === Why does it take so long to connect to my computer via ssh or telnet? The symptom: there is a long delay between the time the TCP connection is established and the time when the client software asks for a password (or, in man:telnet[1]'s case, when a login prompt appears). -The problem: more likely than not, the delay is caused by the server software trying to resolve the client's IP address into a hostname. Many servers, including the Telnet and SSH servers that come with FreeBSD, do this to store the hostname in a log file for future reference by the administrator. +The problem: more likely than not, the delay is caused by the server software trying to resolve the client's IP address into a hostname. +Many servers, including the Telnet and SSH servers that come with FreeBSD, +do this to store the hostname in a log file for future reference by the administrator. -The remedy: if the problem occurs whenever connecting the client computer to any server, the problem is with the client. If the problem only occurs when someone connects to the server computer, the problem is with the server. +The remedy: if the problem occurs whenever connecting the client computer to any server, the problem is with the client. +If the problem only occurs when someone connects to the server computer, the problem is with the server. -If the problem is with the client, the only remedy is to fix the DNS so the server can resolve it. If this is on a local network, consider it a server problem and keep reading. If this is on the Internet, contact your ISP. +If the problem is with the client, the only remedy is to fix the DNS so the server can resolve it. +If this is on a local network, consider it a server problem and keep reading. +If this is on the Internet, contact your ISP. -If the problem is with the server on a local network, configure the server to resolve address-to-hostname queries for the local address range. See man:hosts[5] and man:named[8] for more information. If this is on the Internet, the problem may be that the local server's resolver is not functioning correctly. To check, try to look up another host such as `www.yahoo.com`. If it does not work, that is the problem. +If the problem is with the server on a local network, configure the server to resolve address-to-hostname queries for the local address range. +See man:hosts[5] and man:named[8] for more information. +If this is on the Internet, the problem may be that the local server's resolver is not functioning correctly. +To check, try to look up another host such as `www.yahoo.com`. +If it does not work, that is the problem. -Following a fresh install of FreeBSD, it is also possible that domain and name server information is missing from [.filename]#/etc/resolv.conf#. This will often cause a delay in SSH, as the option `UseDNS` is set to `yes` by default in [.filename]#/etc/ssh/sshd_config#. If this is causing the problem, either fill in the missing information in [.filename]#/etc/resolv.conf# or set `UseDNS` to `no` in [.filename]#sshd_config# as a temporary workaround. +Following a fresh install of FreeBSD, it is also possible that domain and name server information is missing from [.filename]#/etc/resolv.conf#. +This will often cause a delay in SSH, as the option `UseDNS` is set to `yes` by default in [.filename]#/etc/ssh/sshd_config#. +If this is causing the problem, either fill in the missing information in [.filename]#/etc/resolv.conf# or set `UseDNS` to `no` in [.filename]#sshd_config# as a temporary workaround. [[file-table-full]] === Why does file: table is full show up repeatedly in man:dmesg[8]? -This error message indicates that the number of available file descriptors have been exhausted on the system. Refer to the link:{handbook}#kern-maxfiles[kern.maxfiles] section of the link:{handbook}#configtuning-kernel-limits/[Tuning Kernel Limits] section of the Handbook for a discussion and solution. +This error message indicates that the number of available file descriptors have been exhausted on the system. +Refer to the link:{handbook}#kern-maxfiles[kern.maxfiles] section of the link:{handbook}#configtuning-kernel-limits/[Tuning Kernel Limits] section of the Handbook for a discussion and solution. [[computer-clock-skew]] === Why does the clock on my computer keep incorrect time? The computer has two or more clocks, and FreeBSD has chosen to use the wrong one. -Run man:dmesg[8], and check for lines that contain `Timecounter`. The one with the highest quality value that FreeBSD chose. +Run man:dmesg[8], and check for lines that contain `Timecounter`. +The one with the highest quality value that FreeBSD chose. [source,shell] .... @@ -763,14 +942,16 @@ Confirm this by checking the `kern.timecounter.hardware` man:sysctl[3]. kern.timecounter.hardware: ACPI-fast .... -It may be a broken ACPI timer. The simplest solution is to disable the ACPI timer in [.filename]#/boot/loader.conf#: +It may be a broken ACPI timer. +The simplest solution is to disable the ACPI timer in [.filename]#/boot/loader.conf#: [.programlisting] .... debug.acpi.disabled="timer" .... -Or the BIOS may modify the TSC clock-perhaps to change the speed of the processor when running from batteries, or going into a power saving mode, but FreeBSD is unaware of these adjustments, and appears to gain or lose time. +Or the BIOS may modify the TSC clock-perhaps to change the speed of the processor when running from batteries, +or going into a power saving mode, but FreeBSD is unaware of these adjustments, and appears to gain or lose time. In this example, the `i8254` clock is also available, and can be selected by writing its name to the `kern.timecounter.hardware` man:sysctl[3]. @@ -792,16 +973,27 @@ kern.timecounter.hardware=i8254 [[indefinite-wait-buffer]] === What does the error swap_pager: indefinite wait buffer: mean? -This means that a process is trying to page memory from disk, and the page attempt has hung trying to access the disk for more than 20 seconds. It might be caused by bad blocks on the disk drive, disk wiring, cables, or any other disk I/O-related hardware. If the drive itself is bad, disk errors will appear in [.filename]#/var/log/messages# and in the output of `dmesg`. Otherwise, check the cables and connections. +This means that a process is trying to page memory from disk, and the page attempt has hung trying to access the disk for more than 20 seconds. +It might be caused by bad blocks on the disk drive, disk wiring, cables, or any other disk I/O-related hardware. +If the drive itself is bad, disk errors will appear in [.filename]#/var/log/messages# and in the output of `dmesg`. +Otherwise, check the cables and connections. [[lock-order-reversal]] === What is a lock order reversal? -The FreeBSD kernel uses a number of resource locks to arbitrate contention for certain resources. When multiple kernel threads try to obtain multiple resource locks, there's always the potential for a deadlock, where two threads have each obtained one of the locks and blocks forever waiting for the other thread to release one of the other locks. This sort of locking problem can be avoided if all threads obtain the locks in the same order. +The FreeBSD kernel uses a number of resource locks to arbitrate contention for certain resources. +When multiple kernel threads try to obtain multiple resource locks, there's always the potential for a deadlock, +where two threads have each obtained one of the locks and blocks forever waiting for the other thread to release one of the other locks. +This sort of locking problem can be avoided if all threads obtain the locks in the same order. -A run-time lock diagnostic system called man:witness[4], enabled in FreeBSD-CURRENT and disabled by default for stable branches and releases, detects the potential for deadlocks due to locking errors, including errors caused by obtaining multiple resource locks with a different order from different parts of the kernel. The man:witness[4] framework tries to detect this problem as it happens, and reports it by printing a message to the system console about a `lock order reversal` (often referred to also as LOR). +A run-time lock diagnostic system called man:witness[4], enabled in FreeBSD-CURRENT and disabled by default for stable branches and releases, +detects the potential for deadlocks due to locking errors, including errors caused by obtaining multiple resource locks with a different order from different parts of the kernel. +The man:witness[4] framework tries to detect this problem as it happens, +and reports it by printing a message to the system console about a `lock order reversal` (often referred to also as LOR). -It is possible to get false positives, as man:witness[4] is conservative. A true positive report _does not_ mean that a system is dead-locked; instead it should be understood as a warning that a deadlock could have happened here. +It is possible to get false positives, as man:witness[4] is conservative. +A true positive report _does not_ mean that a system is dead-locked; +instead it should be understood as a warning that a deadlock could have happened here. [NOTE] ==== @@ -813,18 +1005,25 @@ Problematic LORs tend to get fixed quickly, so check the {freebsd-current} befor This means that a function that may sleep was called while a mutex (or other unsleepable) lock was held. -The reason this is an error is because mutexes are not intended to be held for long periods of time; they are supposed to only be held to maintain short periods of synchronization. This programming contract allows device drivers to use mutexes to synchronize with the rest of the kernel during interrupts. Interrupts (under FreeBSD) may not sleep. Hence it is imperative that no subsystem in the kernel block for an extended period while holding a mutex. +The reason this is an error is because mutexes are not intended to be held for long periods of time; +they are supposed to only be held to maintain short periods of synchronization. +This programming contract allows device drivers to use mutexes to synchronize with the rest of the kernel during interrupts. +Interrupts (under FreeBSD) may not sleep. +Hence it is imperative that no subsystem in the kernel block for an extended period while holding a mutex. To catch such errors, assertions may be added to the kernel that interact with the man:witness[4] subsystem to emit a warning or fatal error (depending on the system configuration) when a potentially blocking call is made while holding a mutex. -In summary, such warnings are non-fatal, however with unfortunate timing they could cause undesirable effects ranging from a minor blip in the system's responsiveness to a complete system lockup. +In summary, such warnings are non-fatal, +however with unfortunate timing they could cause undesirable effects ranging from a minor blip in the system's responsiveness to a complete system lockup. For additional information about locking in FreeBSD see man:locking[9]. [[touch-not-found]] === Why does buildworld/installworld die with the message touch: not found? -This error does not mean that the man:touch[1] utility is missing. The error is instead probably due to the dates of the files being set sometime in the future. If the CMOS clock is set to local time, run `adjkerntz -i` to adjust the kernel clock when booting into single-user mode. +This error does not mean that the man:touch[1] utility is missing. +The error is instead probably due to the dates of the files being set sometime in the future. +If the CMOS clock is set to local time, run `adjkerntz -i` to adjust the kernel clock when booting into single-user mode. [[applications]] == User Applications @@ -834,9 +1033,12 @@ This error does not mean that the man:touch[1] utility is missing. The error is Refer to link:https://www.FreeBSD.org/ports/[the ports page] for info on software packages ported to FreeBSD. -Most ports should work on all supported versions of FreeBSD. Those that do not are specifically marked as such. Each time a FreeBSD release is made, a snapshot of the ports tree at the time of release is also included in the [.filename]#ports/# directory. +Most ports should work on all supported versions of FreeBSD. +Those that do not are specifically marked as such. +Each time a FreeBSD release is made, a snapshot of the ports tree at the time of release is also included in the [.filename]#ports/# directory. -FreeBSD supports compressed binary packages to easily install and uninstall ports. Use man:pkg[7] to control the installation of packages. +FreeBSD supports compressed binary packages to easily install and uninstall ports. +Use man:pkg[7] to control the installation of packages. [[how-do-download-ports-tree]] === How do I download the Ports tree? Should I be using Git? @@ -846,40 +1048,54 @@ See crossref:handbook[ports-using-installation-methods,Installing the Ports Coll [[ports-4x]] === Why can I not build this port on my {rel2-relx} -, or {rel-relx} -STABLE machine? -If the installed FreeBSD version lags significantly behind _-CURRENT_ or _-STABLE_, update the Ports Collection using the instructions in link:{handbook}#ports-using/[Using the Ports Collection]. If the system is up-to-date, someone might have committed a change to the port which works for _-CURRENT_ but which broke the port for _-STABLE_. https://bugs.FreeBSD.org/submit/[Submit] a bug report, since the Ports Collection is supposed to work for both the _-CURRENT_ and _-STABLE_ branches. +If the installed FreeBSD version lags significantly behind _-CURRENT_ or _-STABLE_, update the Ports Collection using the instructions in link:{handbook}#ports-using/[Using the Ports Collection]. +If the system is up-to-date, someone might have committed a change to the port which works for _-CURRENT_ but which broke the port for _-STABLE_. +https://bugs.FreeBSD.org/submit/[Submit] a bug report, since the Ports Collection is supposed to work for both the _-CURRENT_ and _-STABLE_ branches. [[make-index]] === I just tried to build INDEX using make index, and it failed. Why? -First, make sure that the Ports Collection is up-to-date. Errors that affect building [.filename]#INDEX# from an up-to-date copy of the Ports Collection are high-visibility and are thus almost always fixed immediately. +First, make sure that the Ports Collection is up-to-date. +Errors that affect building [.filename]#INDEX# from an up-to-date copy of the Ports Collection are high-visibility and are thus almost always fixed immediately. -There are rare cases where [.filename]#INDEX# will not build due to odd cases involving `OPTIONS_SET` being set in [.filename]#make.conf#. If you suspect that this is the case, try to make [.filename]#INDEX# with those variables turned off before reporting it to {freebsd-ports}. +There are rare cases where [.filename]#INDEX# will not build due to odd cases involving `OPTIONS_SET` being set in [.filename]#make.conf#. +If you suspect that this is the case, try to make [.filename]#INDEX# with those variables turned off before reporting it to {freebsd-ports}. [[ports-update]] === I updated the sources, now how do I update my installed ports? -FreeBSD does not include a port upgrading tool, but it does have some tools to make the upgrade process somewhat easier. Additional tools are available to simplify port handling and are described the link:{handbook}#ports-using/[Upgrading Ports] section in the FreeBSD Handbook. +FreeBSD does not include a port upgrading tool, but it does have some tools to make the upgrade process somewhat easier. +Additional tools are available to simplify port handling and are described the link:{handbook}#ports-using/[Upgrading Ports] section in the FreeBSD Handbook. [[ports-major-upgrade]] === Do I need to recompile every port each time I perform a major version update? -Yes! While a recent system will run with software compiled under an older release, things will randomly crash and fail to work once other ports are installed or updated. +Yes! While a recent system will run with software compiled under an older release, +things will randomly crash and fail to work once other ports are installed or updated. -When the system is upgraded, various shared libraries, loadable modules, and other parts of the system will be replaced with newer versions. Applications linked against the older versions may fail to start or, in other cases, fail to function properly. +When the system is upgraded, various shared libraries, loadable modules, and other parts of the system will be replaced with newer versions. +Applications linked against the older versions may fail to start or, in other cases, fail to function properly. For more information, see link:{handbook}#freebsdupdate-upgrade[the section on upgrades] in the FreeBSD Handbook. [[ports-minor-upgrade]] === Do I need to recompile every port each time I perform a minor version update? -In general, no. FreeBSD developers do their utmost to guarantee binary compatibility across all releases with the same major version number. Any exceptions will be documented in the Release Notes, and advice given there should be followed. +In general, no. FreeBSD developers do their utmost to guarantee binary compatibility across all releases with the same major version number. +Any exceptions will be documented in the Release Notes, and advice given there should be followed. [[minimal-sh]] === Why is /bin/sh so minimal? Why does FreeBSD not use bash or another shell? -Many people need to write shell scripts which will be portable across many systems. That is why POSIX(R) specifies the shell and utility commands in great detail. Most scripts are written in Bourne shell (man:sh[1]), and because several important programming interfaces (man:make[1], man:system[3], man:popen[3], and analogues in higher-level scripting languages like Perl and Tcl) are specified to use the Bourne shell to interpret commands. As the Bourne shell is so often and widely used, it is important for it to be quick to start, be deterministic in its behavior, and have a small memory footprint. +Many people need to write shell scripts which will be portable across many systems. +That is why POSIX(R) specifies the shell and utility commands in great detail. +Most scripts are written in Bourne shell (man:sh[1]), and because several important programming interfaces (man:make[1], man:system[3], man:popen[3], and analogues in higher-level scripting languages like Perl and Tcl) are specified to use the Bourne shell to interpret commands. +As the Bourne shell is so often and widely used, it is important for it to be quick to start, be deterministic in its behavior, and have a small memory footprint. -The existing implementation is our best effort at meeting as many of these requirements simultaneously as we can. To keep `/bin/sh` small, we have not provided many of the convenience features that other shells have. That is why other more featureful shells like `bash`, `scsh`, man:tcsh[1], and `zsh` are available. Compare the memory utilization of these shells by looking at the "VSZ" and "RSS" columns in a `ps -u` listing. +The existing implementation is our best effort at meeting as many of these requirements simultaneously as we can. +To keep `/bin/sh` small, we have not provided many of the convenience features that other shells have. +That is why other more featureful shells like `bash`, `scsh`, man:tcsh[1], and `zsh` are available. +Compare the memory utilization of these shells by looking at the "VSZ" and "RSS" columns in a `ps -u` listing. [[kernelconfig]] == Kernel Configuration @@ -891,13 +1107,19 @@ Not at all! Check out the link:{handbook}#kernelconfig/[kernel config section of [NOTE] ==== -The new [.filename]#kernel# will be installed to the [.filename]#/boot/kernel# directory along with its modules, while the old kernel and its modules will be moved to the [.filename]#/boot/kernel.old# directory. If a mistake is made in the configuration, simply boot the previous version of the kernel. +The new [.filename]#kernel# will be installed to the [.filename]#/boot/kernel# directory along with its modules, +while the old kernel and its modules will be moved to the [.filename]#/boot/kernel.old# directory. +If a mistake is made in the configuration, simply boot the previous version of the kernel. ==== [[why-kernel-big]] === Why is my kernel so big? -`GENERIC` kernels shipped with FreeBSD are compiled in _debug mode_. Kernels built in debug mode contain debug data in separate files that are used for debugging. FreeBSD releases prior to 11.0 store these debug files in the same directory as the kernel itself, [.filename]#/boot/kernel/#. In FreeBSD 11.0 and later the debug files are stored in [.filename]#/usr/lib/debug/boot/kernel/#. Note that there will be little or no performance loss from running a debug kernel, and it is useful to keep one around in case of a system panic. +`GENERIC` kernels shipped with FreeBSD are compiled in _debug mode_. +Kernels built in debug mode contain debug data in separate files that are used for debugging. +FreeBSD releases prior to 11.0 store these debug files in the same directory as the kernel itself, [.filename]#/boot/kernel/#. +In FreeBSD 11.0 and later the debug files are stored in [.filename]#/usr/lib/debug/boot/kernel/#. +Note that there will be little or no performance loss from running a debug kernel, and it is useful to keep one around in case of a system panic. When running low on disk space, there are different options to reduce the size of [.filename]#/boot/kernel/# and [.filename]#/usr/lib/debug/#. @@ -930,9 +1152,13 @@ To build and install only the specified modules, list them in [.filename]#/etc/m MODULES_OVERRIDE= accf_http ipfw .... -Replace _accf_httpd ipfw_ with a list of needed modules. Only the listed modules will be built. This reduces the size of the kernel directory and decreases the amount of time needed to build the kernel. For more information, read [.filename]#/usr/share/examples/etc/make.conf#. +Replace _accf_httpd ipfw_ with a list of needed modules. +Only the listed modules will be built. +This reduces the size of the kernel directory and decreases the amount of time needed to build the kernel. +For more information, read [.filename]#/usr/share/examples/etc/make.conf#. -Unneeded devices can be removed from the kernel to further reduce the size. See <<make-kernel>> for more information. +Unneeded devices can be removed from the kernel to further reduce the size. +See <<make-kernel>> for more information. To put any of these options into effect, follow the instructions to link:{handbook}#kernelconfig-building/[build and install] the new kernel. @@ -974,13 +1200,21 @@ See the link:{handbook}#disks-adding/[Adding Disks] section in the FreeBSD Handb [[new-huge-disk]] === How do I move my system over to my huge new disk? -The best way is to reinstall the operating system on the new disk, then move the user data over. This is highly recommended when tracking _-STABLE_ for more than one release or when updating a release instead of installing a new one. Install booteasy on both disks with man:boot0cfg[8] and dual boot until you are happy with the new configuration. Skip the next paragraph to find out how to move the data after doing this. +The best way is to reinstall the operating system on the new disk, then move the user data over. +This is highly recommended when tracking _-STABLE_ for more than one release or when updating a release instead of installing a new one. +Install booteasy on both disks with man:boot0cfg[8] and dual boot until you are happy with the new configuration. +Skip the next paragraph to find out how to move the data after doing this. -Alternatively, partition and label the new disk with either man:sade[8] or man:gpart[8]. If the disks are MBR-formatted, booteasy can be installed on both disks with man:boot0cfg[8] so that the computer can dual boot to the old or new system after the copying is done. +Alternatively, partition and label the new disk with either man:sade[8] or man:gpart[8]. +If the disks are MBR-formatted, booteasy can be installed on both disks with man:boot0cfg[8] so that the computer can dual boot to the old or new system after the copying is done. -Once the new disk set up, the data cannot just be copied. Instead, use tools that understand device files and system flags, such as man:dump[8]. Although it is recommended to move the data while in single-user mode, it is not required. +Once the new disk set up, the data cannot just be copied. +Instead, use tools that understand device files and system flags, such as man:dump[8]. +Although it is recommended to move the data while in single-user mode, it is not required. -When the disks are formatted with UFS, never use anything but man:dump[8] and man:restore[8] to move the root file system. These commands should also be used when moving a single partition to another empty partition. The sequence of steps to use `dump` to move the data from one UFS partitions to a new partition is: +When the disks are formatted with UFS, never use anything but man:dump[8] and man:restore[8] to move the root file system. +These commands should also be used when moving a single partition to another empty partition. +The sequence of steps to use `dump` to move the data from one UFS partitions to a new partition is: [.procedure] ==== @@ -1000,7 +1234,8 @@ For example, to move [.filename]#/dev/ada1s1a# with [.filename]#/mnt# as the tem # dump 0af - / | restore rf - .... -Rearranging partitions with `dump` takes a bit more work. To merge a partition like [.filename]#/var# into its parent, create the new partition large enough for both, move the parent partition as described above, then move the child partition into the empty directory that the first move created: +Rearranging partitions with `dump` takes a bit more work. +To merge a partition like [.filename]#/var# into its parent, create the new partition large enough for both, move the parent partition as described above, then move the child partition into the empty directory that the first move created: [source,shell] .... @@ -1025,24 +1260,41 @@ To split a directory from its parent, say putting [.filename]#/var# on its own p # dump 0af - / | restore rf - .... -The man:cpio[1] and man:pax[1] utilities are also available for moving user data. These are known to lose file flag information, so use them with caution. +The man:cpio[1] and man:pax[1] utilities are also available for moving user data. +These are known to lose file flag information, so use them with caution. [[safe-softupdates]] === Which partitions can safely use Soft Updates? I have heard that Soft Updates on / can cause problems. What about Journaled Soft Updates? Short answer: Soft Updates can usually be safely used on all partitions. *** 1508 LINES SKIPPED ***
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202106121502.15CF2Fm6005087>