Path: blob/main/documentation/content/en/articles/explaining-bsd/_index.po
18096 views
# SOME DESCRIPTIVE TITLE # Copyright (C) YEAR The FreeBSD Project # This file is distributed under the same license as the FreeBSD Documentation package. # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: FreeBSD Documentation VERSION\n" "POT-Creation-Date: 2026-05-09 23:29+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <[email protected]>\n" "Language: \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. type: YAML Front Matter: description #: documentation/content/en/articles/explaining-bsd/_index.adoc:1 #, no-wrap msgid "Brief explanation about BSD" msgstr "" #. type: Title = #: documentation/content/en/articles/explaining-bsd/_index.adoc:1 #: documentation/content/en/articles/explaining-bsd/_index.adoc:11 #, no-wrap msgid "Explaining BSD" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:44 msgid "Abstract" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:46 msgid "" "In the open source world, the word \"Linux\" is almost synonymous with " "\"Operating System\", but it is not the only open source UNIX(R) operating " "system." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:48 msgid "" "So what is the secret? Why is BSD not better known? This white paper " "addresses these and other questions." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:50 msgid "" "Throughout this paper, differences between BSD and Linux will be noted " "__like this__." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:52 msgid "'''" msgstr "" #. type: Title == #: documentation/content/en/articles/explaining-bsd/_index.adoc:56 #, no-wrap msgid "What is BSD?" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:63 msgid "" "BSD stands for \"Berkeley Software Distribution\". It is the name of " "distributions of source code from the University of California, Berkeley, " "which were originally extensions to AT&T's Research UNIX(R) operating " "system. Several open source operating system projects are based on a " "release of this source code known as 4.4BSD-Lite. In addition, they " "comprise a number of packages from other Open Source projects, including " "notably the GNU project. The overall operating system comprises:" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:65 msgid "" "The BSD kernel, which handles process scheduling, memory management, " "symmetric multi-processing (SMP), device drivers, etc." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:66 msgid "The C library, the base API for the system." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:68 msgid "" "__The BSD C library is based on code from Berkeley, not the GNU project.__" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:69 msgid "Utilities such as shells, file utilities, compilers and linkers." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:71 msgid "" "__Some of the utilities are derived from the GNU project, others are not.__" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:72 msgid "The X Window system, which handles graphical display." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:75 msgid "" "The X Window system used in most versions of BSD is maintained by the http://" "www.X.org/[X.Org project]. FreeBSD allows the user to choose from a variety " "of desktop environments, such as Gnome, KDE, or Xfce; and lightweight window " "managers like Openbox, Fluxbox, or Awesome." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:76 msgid "Many other programs and utilities." msgstr "" #. type: Title == #: documentation/content/en/articles/explaining-bsd/_index.adoc:78 #, no-wrap msgid "What, a real UNIX(R)?" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:83 msgid "" "The BSD operating systems are not clones, but open source derivatives of " "AT&T's Research UNIX(R) operating system, which is also the ancestor of the " "modern UNIX(R) System V. This may surprise you. How could that happen when " "AT&T has never released its code as open source?" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:85 msgid "" "It is true that AT&T UNIX(R) is not open source, and in a copyright sense " "BSD is very definitely _not_ UNIX(R), but on the other hand, AT&T has " "imported sources from other projects, noticeably the Computer Sciences " "Research Group (CSRG) of the University of California in Berkeley, CA. " "Starting in 1976, the CSRG started releasing tapes of their software, " "calling them _Berkeley Software Distribution_ or __BSD__." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:89 msgid "" "Initial BSD releases consisted mainly of user programs, but that changed " "dramatically when the CSRG landed a contract with the Defense Advanced " "Research Projects Agency (DARPA) to upgrade the communications protocols on " "their network, ARPANET. The new protocols were known as the __Internet " "Protocols__, later _TCP/IP_ after the most important protocols. The first " "widely distributed implementation was part of 4.2BSD, in 1982." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:96 msgid "" "In the course of the 1980s, a number of new workstation companies sprang " "up. Many preferred to license UNIX(R) rather than developing operating " "systems for themselves. In particular, Sun Microsystems licensed UNIX(R) " "and implemented a version of 4.2BSD, which they called SunOS(TM). When AT&T " "themselves were allowed to sell UNIX(R) commercially, they started with a " "somewhat bare-bones implementation called System III, to be quickly followed " "by System V. The System V code base did not include networking, so all " "implementations included additional software from the BSD, including the TCP/" "IP software, but also utilities such as the _csh_ shell and the _vi_ " "editor. Collectively, these enhancements were known as the __Berkeley " "Extensions__." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:105 msgid "" "The BSD tapes contained AT&T source code and thus required a UNIX(R) source " "license. By 1990, the CSRG's funding was running out, and it faced " "closure. Some members of the group decided to release the BSD code, which " "was Open Source, without the AT&T proprietary code. This finally happened " "with the __Networking Tape 2__, usually known as __Net/2__. Net/2 was not a " "complete operating system: about 20% of the kernel code was missing. One of " "the CSRG members, William F. Jolitz, wrote the remaining code and released " "it in early 1992 as __386BSD__. At the same time, another group of ex-CSRG " "members formed a commercial company called http://www.bsdi.com/[Berkeley " "Software Design Inc.] and released a beta version of an operating system " "called http://www.bsdi.com/[BSD/386], which was based on the same sources. " "The name of the operating system was later changed to BSD/OS." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:111 msgid "" "386BSD never became a stable operating system. Instead, two other projects " "split off from it in 1993: http://www.NetBSD.org/[NetBSD] and link:https://" "www.FreeBSD.org/[FreeBSD]. The two projects originally diverged due to " "differences in patience waiting for improvements to 386BSD: the NetBSD " "people started early in the year, and the first version of FreeBSD was not " "ready until the end of the year. In the meantime, the code base had " "diverged sufficiently to make it difficult to merge. In addition, the " "projects had different aims, as we will see below. In 1996, http://" "www.OpenBSD.org/[OpenBSD] split off from NetBSD, and in 2003, http://" "www.dragonflybsd.org/[DragonFlyBSD] split off from FreeBSD." msgstr "" #. type: Title == #: documentation/content/en/articles/explaining-bsd/_index.adoc:113 #, no-wrap msgid "Why is BSD not better known?" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:116 msgid "For a number of reasons, BSD is relatively unknown:" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:118 msgid "" "The BSD developers are often more interested in polishing their code than " "marketing it." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:119 msgid "" "Much of Linux's popularity is due to factors external to the Linux projects, " "such as the press, and to companies formed to provide Linux services. Until " "recently, the open source BSDs had no such proponents." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:120 msgid "" "In 1992, AT&T sued http://www.bsdi.com/[BSDI], the vendor of BSD/386, " "alleging that the product contained AT&T-copyrighted code. The case was " "settled out of court in 1994, but the spectre of the litigation continues to " "haunt people. In March 2000 an article published on the web claimed that the " "court case had been \"recently settled\"." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:124 msgid "" "One detail that the lawsuit did clarify is the naming: in the 1980s, BSD was " "known as \"BSD UNIX(R)\". With the elimination of the last vestige of AT&T " "code from BSD, it also lost the right to the name UNIX(R). Thus you will " "see references in book titles to \"the 4.3BSD UNIX(R) operating system\" and " "\"the 4.4BSD operating system\"." msgstr "" #. type: Title == #: documentation/content/en/articles/explaining-bsd/_index.adoc:126 #, no-wrap msgid "Comparing BSD and Linux" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:132 msgid "" "So what is really the difference between, say, Debian Linux and FreeBSD? For " "the average user, the difference is surprisingly small: Both are UNIX(R) " "like operating systems. Both are developed by non-commercial projects (this " "does not apply to many other Linux distributions, of course). In the " "following section, we will look at BSD and compare it to Linux. The " "description applies most closely to FreeBSD, which accounts for an estimated " "80% of the BSD installations, but the differences from NetBSD, OpenBSD and " "DragonFlyBSD are small." msgstr "" #. type: Title === #: documentation/content/en/articles/explaining-bsd/_index.adoc:133 #, no-wrap msgid "Who owns BSD?" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:138 msgid "" "No one person or corporation owns BSD. It is created and distributed by a " "community of highly technical and committed contributors all over the " "world. Some of the components of BSD are Open Source projects in their own " "right and managed by different project maintainers." msgstr "" #. type: Title === #: documentation/content/en/articles/explaining-bsd/_index.adoc:139 #, no-wrap msgid "How is BSD developed and updated?" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:144 msgid "" "The BSD kernels are developed and updated following the Open Source " "development model. Each project maintains a publicly accessible _source " "tree_ which contains all source files for the project, including " "documentation and other incidental files. Users can obtain a complete copy " "of any version." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:147 msgid "" "A large number of developers worldwide contribute to improvements to BSD. " "They are divided into three kinds:" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:149 msgid "" "_Contributors_ write code or documentation. They are not permitted to commit " "(add code) directly to the source tree. For their code to be included in the " "system, it must be reviewed and checked in by a registered developer, known " "as a __committer__." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:150 msgid "" "_Committers_ are developers with write access to the source tree. To become " "a committer, an individual must show ability in the area in which they are " "active." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:157 msgid "" "It is at the individual committer's discretion whether they should obtain " "authority before committing changes to the source tree. In general, an " "experienced committer may make changes which are obviously correct without " "obtaining consensus. For example, a documentation project committer may " "correct typographical or grammatical errors without review. On the other " "hand, developers making far-reaching or complicated changes are expected to " "submit their changes for review before committing them. In extreme cases, a " "core team member with a function such as Principal Architect may order that " "changes be removed from the tree, a process known as _backing out_. All " "committers receive mail describing each individual commit, so it is not " "possible to commit secretly." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:158 msgid "" "The _Core team_. FreeBSD and NetBSD each have a core team which manages the " "project. The core teams developed in the course of the projects, and their " "role is not always well-defined. It is not necessary to be a developer to be " "a core team member, though it is normal. The rules for the core team vary " "from one project to the other, but in general they have more say in the " "direction of the project than non-core team members have." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:160 msgid "This arrangement differs from Linux in a number of ways:" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:162 msgid "" "No one person controls the content of the system. In practice, this " "difference is overrated, since the Principal Architect can require that code " "be backed out, and even in the Linux project several people are permitted to " "make changes." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:163 msgid "" "On the other hand, there _is_ a central repository, a single place where you " "can find the entire operating system sources, including all older versions." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:164 msgid "" "BSD projects maintain the entire \"Operating System\", not only the kernel. " "This distinction is only marginally useful: neither BSD nor Linux is useful " "without applications. The applications used under BSD are frequently the " "same as the applications used under Linux." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:165 msgid "" "As a result of the formalized maintenance of a single Git source tree, BSD " "development is clear, and it is possible to access any version of the system " "by release number or by date. Git also allows incremental updates to the " "system: for example, the FreeBSD repository is updated about 100 times a " "day. Most of these changes are small." msgstr "" #. type: Title === #: documentation/content/en/articles/explaining-bsd/_index.adoc:166 #, no-wrap msgid "BSD releases" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:171 msgid "" "FreeBSD, NetBSD and OpenBSD provide the system in three different " "\"releases\". As with Linux, releases are assigned a number such as 1.4.1 " "or 3.5. In addition, the version number has a suffix indicating its purpose:" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:173 msgid "" "The development version of the system is called _CURRENT_. FreeBSD assigns a " "number to CURRENT, for example FreeBSD 5.0-CURRENT. NetBSD uses a slightly " "different naming scheme and appends a single-letter suffix which indicates " "changes in the internal interfaces, for example NetBSD 1.4.3G. OpenBSD does " "not assign a number (\"OpenBSD-current\"). All new development on the system " "goes into this branch." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:174 msgid "" "At regular intervals, between two and four times a year, the projects bring " "out a _RELEASE_ version of the system, which is available on CD-ROM and for " "free download from FTP sites, for example OpenBSD 2.6-RELEASE or NetBSD 1.4-" "RELEASE. The RELEASE version is intended for end users and is the normal " "version of the system. NetBSD also provides _patch releases_ with a third " "digit, for example NetBSD 1.4.2." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:175 msgid "" "As bugs are found in a RELEASE version, they are fixed, and the fixes are " "added to the Git tree. In FreeBSD, the resultant version is called the " "_STABLE_ version, while in NetBSD and OpenBSD it continues to be called the " "RELEASE version. Smaller new features can also be added to this branch after " "a period of test in the CURRENT branch. Security and other important bug " "fixes are also applied to all supported RELEASE versions." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:182 msgid "" "_By contrast, Linux maintains two separate code trees: the stable version " "and the development version. Stable versions have an even minor version " "number, such as 2.0, 2.2 or 2.4. Development versions have an odd minor " "version number, such as 2.1, 2.3 or 2.5. In each case, the number is " "followed by a further number designating the exact release. In addition, " "each vendor adds their own userland programs and utilities, so the name of " "the distribution is also important. Each distribution vendor also assigns " "version numbers to the distribution, so a complete description might be " "something like \"TurboLinux 6.0 with kernel 2.2.14\"_" msgstr "" #. type: Title === #: documentation/content/en/articles/explaining-bsd/_index.adoc:183 #, no-wrap msgid "What versions of BSD are available?" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:186 msgid "" "In contrast to the numerous Linux distributions, there are only four major " "open source BSDs. Each BSD project maintains its own source tree and its own " "kernel. In practice, though, there appear to be fewer divergences between " "the userland code of the projects than there is in Linux." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:188 msgid "" "It is difficult to categorize the goals of each project: the differences are " "very subjective. Basically," msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:190 msgid "" "FreeBSD aims for high performance and ease of use by end users, and is a " "favourite of web content providers. It runs on a link:https://" "www.FreeBSD.org/platforms/[number of platforms] and has significantly more " "users than the other projects." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:191 msgid "" "NetBSD aims for maximum portability: \"of course it runs NetBSD\". It runs " "on machines from palmtops to large servers, and has even been used on NASA " "space missions. It is a particularly good choice for running on old non-" "Intel(R) hardware." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:192 msgid "" "OpenBSD aims for security and code purity: it uses a combination of the open " "source concept and rigorous code reviews to create a system which is " "demonstrably correct, making it the choice of security-conscious " "organizations such as banks, stock exchanges and US Government departments. " "Like NetBSD, it runs on a number of platforms." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:193 msgid "" "DragonFlyBSD aims for high performance and scalability under everything from " "a single-node UP system to a massively clustered system. DragonFlyBSD has " "several long-range technical goals, but focus lies on providing a SMP-" "capable infrastructure that is easy to understand, maintain and develop for." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:195 msgid "" "There are also two additional BSD UNIX(R) operating systems which are not " "open source, BSD/OS and Apple's Mac OS(R) X:" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:197 msgid "" "BSD/OS was the oldest of the 4.4BSD derivatives. It was not open source, " "though source code licenses were available at relatively low cost. It " "resembled FreeBSD in many ways. Two years after the acquisition of BSDi by " "Wind River Systems, BSD/OS failed to survive as an independent product. " "Support and source code may still be available from Wind River, but all new " "development is focused on the VxWorks embedded operating system." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:198 msgid "" "http://www.apple.com/macosx/server/[Mac OS(R) X] is the latest version of " "the operating system for Apple(R)'s Mac(R) line. The BSD core of this " "operating system, http://developer.apple.com/darwin/[Darwin], is available " "as a fully functional open source operating system for x86 and PPC " "computers. The Aqua/Quartz graphics system and many other proprietary " "aspects of Mac OS(R) X remain closed-source, however. Several Darwin " "developers are also FreeBSD committers, and vice-versa." msgstr "" #. type: Title === #: documentation/content/en/articles/explaining-bsd/_index.adoc:199 #, no-wrap msgid "How does the BSD license differ from the GNU Public license?" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:205 msgid "" "Linux is available under the http://www.fsf.org/copyleft/gpl.html[GNU " "General Public License] (GPL), which is designed to eliminate closed source " "software. In particular, any derivative work of a product released under " "the GPL must also be supplied with source code if requested. By contrast, " "the http://www.opensource.org/licenses/bsd-license.html[BSD license] is less " "restrictive: binary-only distributions are allowed. This is particularly " "attractive for embedded applications." msgstr "" #. type: Title === #: documentation/content/en/articles/explaining-bsd/_index.adoc:206 #, no-wrap msgid "What else should I know?" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:211 msgid "" "Since fewer applications are available for BSD than Linux, the BSD " "developers created a Linux compatibility package, which allows Linux " "programs to run under BSD. The package includes both kernel modifications, " "to correctly perform Linux system calls, and Linux compatibility files such " "as the C library. There is no noticeable difference in execution speed " "between a Linux application running on a Linux machine and a Linux " "application running on a BSD machine of the same speed." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:214 msgid "" "The \"all from one supplier\" nature of BSD means that upgrades are much " "easier to handle than is frequently the case with Linux. BSD handles " "library version upgrades by providing compatibility modules for earlier " "library versions, so it is possible to run binaries which are several years " "old with no problems." msgstr "" #. type: Title === #: documentation/content/en/articles/explaining-bsd/_index.adoc:215 #, no-wrap msgid "Which should I use, BSD or Linux?" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:218 msgid "" "What does this all mean in practice? Who should use BSD, who should use " "Linux?" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:221 msgid "This is a very difficult question to answer. Here are some guidelines:" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:223 msgid "" "\"If it ain't broke, don't fix it\": If you already use an open source " "operating system, and you are happy with it, there is probably no good " "reason to change." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:224 msgid "" "BSD systems, in particular FreeBSD, can have notably higher performance than " "Linux. But this is not across the board. In many cases, there is little or " "no difference in performance. In some cases, Linux may perform better than " "FreeBSD." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:225 msgid "" "In general, BSD systems have a better reputation for reliability, mainly as " "a result of the more mature code base." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:226 msgid "" "BSD projects have a better reputation for the quality and completeness of " "their documentation. The various documentation projects aim to provide " "actively updated documentation, in many languages, and covering all aspects " "of the system." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:227 msgid "The BSD license may be more attractive than the GPL." msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:228 msgid "" "BSD can execute most Linux binaries, while Linux can not execute BSD " "binaries. Many BSD implementations can also execute binaries from other " "UNIX(R) like systems. As a result, BSD may present an easier migration route " "from other systems than Linux would." msgstr "" #. type: Title === #: documentation/content/en/articles/explaining-bsd/_index.adoc:229 #, no-wrap msgid "Who provides support, service, and training for BSD?" msgstr "" #. type: Plain text #: documentation/content/en/articles/explaining-bsd/_index.adoc:231 msgid "" "Each of the projects has a list of consultants for hire: link:https://" "www.FreeBSD.org/commercial/consult_bycat/[FreeBSD], http://www.netbsd.org/" "gallery/consultants.html[NetBSD], and http://www.openbsd.org/" "support.html[OpenBSD]." msgstr ""