Checkout from a Mirror

Architecture	`SHA512`	`SHA256`
amd64 (x86_64)	SHA512	SHA256
i386	SHA512	SHA256
powerpc	SHA512	SHA256
powerpc64	SHA512	SHA256
sparc64	SHA512	SHA256
aarch64	SHA512	SHA256

Architecture	`SHA512`	`SHA256`
amd64 (x86_64)	SHA512	SHA256
i386	SHA512	SHA256
aarch64	SHA512	SHA256

Board Name	`SHA512`	`SHA256`
BANANAPI	SHA512	SHA256
BEAGLEBONE	SHA512	SHA256
CUBIEBOARD	SHA512	SHA256
CUBIEBOARD2	SHA512	SHA256
CUBOX/HUMMINGBOARD	SHA512	SHA256
GUMSTIX	SHA512	SHA256
PANDABOARD	SHA512	SHA256
RPI-B	SHA512	SHA256
RPI2	SHA512	SHA256
WANDBOARD	SHA512	SHA256

Errata	Date	Topic
FreeBSD-EN-17:07.vnet	10�August�2017	VNET kernel panic with asynchronous + exceptions
FreeBSD-SA-18:07.lazyfpu	21�June�2018	Fix Lazy FPU information + disclosure

Errata	Date	Topic
FreeBSD-EN-17:07.vnet	10�August�2017	VNET kernel panic with asynchronous I/O
FreeBSD-EN-17:08.pf	10�August�2017	pf(4) housekeeping thread causes kernel panic
FreeBSD-EN-17:09.tzdata	2�November�2017	Timezone database information update
FreeBSD-EN-18:01.tzdata	07�March�2018	Timezone database information @@ -53,7 +54,7 @@ information
FreeBSD-EN-18:04.mem	04�April�2018	Multiple small kernel memory disclosures
FreeBSD-EN-18:05.mem	08�May�2018	Multiple small kernel memory disclosures
FreeBSD-EN-18:06.tzdata	08�May�2018	Update timezone database - information

Errata	Date	Topic
FreeBSD-EN-17:07.vnet	10�August�2017	VNET kernel panic with asynchronous + exceptions
FreeBSD-SA-18:07.lazyfpu	21�June�2018	Fix Lazy FPU information + disclosure

Download the freebsd-update-server software by installing - devel/subversion and security/ca_root_nss, and execute: + devel/subversion and + security/ca_root_nss, and execute: &prompt.user; svn co https://svn.freebsd.org/base/user/cperciva/freebsd-update-build freebsd-update-server From owner-svn-doc-head@freebsd.org Sun Jun 17 16:54:57 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 56CBB1001A43; Sun, 17 Jun 2018 16:54:57 +0000 (UTC) (envelope-from trasz@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 05A1A757B5; Sun, 17 Jun 2018 16:54:57 +0000 (UTC) (envelope-from trasz@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id D5BF9180BD; Sun, 17 Jun 2018 16:54:56 +0000 (UTC) (envelope-from trasz@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w5HGsu7E006721; Sun, 17 Jun 2018 16:54:56 GMT (envelope-from trasz@FreeBSD.org) Received: (from trasz@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w5HGsuus006720; Sun, 17 Jun 2018 16:54:56 GMT (envelope-from trasz@FreeBSD.org) Message-Id: <201806171654.w5HGsuus006720@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: trasz set sender to trasz@FreeBSD.org using -f From: Edward Tomasz Napierala Date: Sun, 17 Jun 2018 16:54:56 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r51863 - head/en_US.ISO8859-1/books/handbook/introduction X-SVN-Group: doc-head X-SVN-Commit-Author: trasz X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/handbook/introduction X-SVN-Commit-Revision: 51863 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2018 16:54:57 -0000 Author: trasz (src,ports committer) Date: Sun Jun 17 16:54:56 2018 New Revision: 51863 URL: https://svnweb.freebsd.org/changeset/doc/51863 Log: Fix claims on binary compatibility - it's just Linux nowadays; nobody cares about SCO or BSD/OS anyway. Reviewed by: eadler@ Approved by: eadler@ Differential Revision: https://reviews.freebsd.org/D15863 Modified: head/en_US.ISO8859-1/books/handbook/introduction/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/introduction/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/introduction/chapter.xml Sun Jun 17 16:40:13 2018 (r51862) +++ head/en_US.ISO8859-1/books/handbook/introduction/chapter.xml Sun Jun 17 16:54:56 2018 (r51863) @@ -140,25 +140,8 @@ binary compatibility Linux - - binary compatibility - SCO - - - binary compatibility - SVR4 - - - binary compatibility - BSD/OS - - - binary compatibility - NetBSD - Binary compatibility with many - programs built for Linux, SCO, SVR4, BSDI and - NetBSD. + programs built for Linux. From owner-svn-doc-head@freebsd.org Sun Jun 17 16:57:59 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8F34A1001AF3; Sun, 17 Jun 2018 16:57:58 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 404857584B; Sun, 17 Jun 2018 16:57:58 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 1CEDF180C1; Sun, 17 Jun 2018 16:57:58 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w5HGvvAJ006915; Sun, 17 Jun 2018 16:57:57 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w5HGvvkV006914; Sun, 17 Jun 2018 16:57:57 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201806171657.w5HGvvkV006914@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Sun, 17 Jun 2018 16:57:57 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r51864 - head/en_US.ISO8859-1/articles/explaining-bsd X-SVN-Group: doc-head X-SVN-Commit-Author: bcr X-SVN-Commit-Paths: head/en_US.ISO8859-1/articles/explaining-bsd X-SVN-Commit-Revision: 51864 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2018 16:57:59 -0000 Author: bcr Date: Sun Jun 17 16:57:57 2018 New Revision: 51864 URL: https://svnweb.freebsd.org/changeset/doc/51864 Log: Style cleanup: - wrap long lines - put two spaces after a sentence stop - put and on lines on their own - in one instance, put the text right next to the <para> tag and not below it I did not change the capitalizations in this file, so the file should not have any visible changes. Modified: head/en_US.ISO8859-1/articles/explaining-bsd/article.xml Modified: head/en_US.ISO8859-1/articles/explaining-bsd/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/explaining-bsd/article.xml Sun Jun 17 16:54:56 2018 (r51863) +++ head/en_US.ISO8859-1/articles/explaining-bsd/article.xml Sun Jun 17 16:57:57 2018 (r51864) @@ -3,9 +3,11 @@ "http://www.FreeBSD.org/XML/share/xml/freebsd50.dtd">   -<article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en"> - <info><title>Explaining BSD - +

+ + Explaining BSD GregLehey

grog@FreeBSD.org

@@ -29,42 +31,43 @@ $FreeBSD$ - In the open source world, the word Linux is almost - synonymous with Operating System, but it is not the only - open source &unix; operating system. + In the open source world, the word Linux is + almost synonymous with Operating System, but it + is not the only open source &unix; operating system. - So what is the secret? Why is BSD not better known? This white - paper addresses these and other questions. + So what is the secret? Why is BSD not better known? This + white paper addresses these and other questions. - Throughout this paper, differences between BSD and Linux will be - noted like this. + Throughout this paper, differences between BSD and Linux + will be noted like this. What is BSD? - 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; 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 + 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; + 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: The BSD kernel, which handles process scheduling, memory - management, symmetric multi-processing (SMP), device drivers, - etc. + management, symmetric multi-processing (SMP), device + drivers, etc. The C library, the base API for the system. - The BSD C library is based on code from Berkeley, not - the GNU project. + The BSD C library is based on code from + Berkeley, not the GNU project. @@ -76,16 +79,17 @@ - The X Window system, which handles graphical display. + The X Window system, which handles graphical + display. - The X Window system used in most versions of BSD is maintained - by the - X.Org project. - &os; allows the user to choose from a variety of desktop - environments, such as Gnome, - KDE, or Xfce; - and lightweight window managers like - Openbox, + The X Window system used in most versions of BSD is + maintained by the X.Org + project. &os; 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. @@ -100,71 +104,77 @@ What, a real &unix;? The BSD operating systems are not clones, but open source - derivatives of AT&T's Research &unix; operating system, which is also - the ancestor of the modern &unix; System V. This may surprise you. How - could that happen when AT&T has never released its code as open - source? + derivatives of AT&T's Research &unix; operating system, + which is also the ancestor of the modern &unix; System V. This + may surprise you. How could that happen when AT&T has never + released its code as open source? - It is true that AT&T &unix; is not open source, and in a copyright - sense BSD is very definitely not &unix;, 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. + It is true that AT&T &unix; is not open source, and in a + copyright sense BSD is very definitely not + &unix;, 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. - 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. + 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. - In the course of the 1980s, a number of new workstation companies - sprang up. Many preferred to license &unix; rather than developing - operating systems for themselves. In particular, Sun Microsystems - licensed &unix; and implemented a version of 4.2BSD, which they called - &sunos;. When AT&T themselves were allowed to sell &unix; 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. + In the course of the 1980s, a number of new workstation + companies sprang up. Many preferred to license &unix; rather + than developing operating systems for themselves. In + particular, Sun Microsystems licensed &unix; and implemented a + version of 4.2BSD, which they called &sunos;. When AT&T + themselves were allowed to sell &unix; 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. - The BSD tapes contained AT&T source code and thus required a - &unix; 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 - Berkeley Software Design Inc. - and released a beta version of an operating system called - BSD/386, which was based on - the same sources. The name of the operating system was later changed - to BSD/OS. + The BSD tapes contained AT&T source code and thus + required a &unix; 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 Berkeley Software Design + Inc. and released a beta version of an operating system + called BSD/386, + which was based on the same sources. The name of the operating + system was later changed to BSD/OS. - 386BSD never became a stable operating system. Instead, two other - projects split off from it in 1993: - NetBSD and - 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, - OpenBSD split off from - NetBSD, and in 2003, - DragonFlyBSD split - off from FreeBSD. + 386BSD never became a stable operating system. Instead, two + other projects split off from it in 1993: NetBSD and 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, OpenBSD split off + from NetBSD, and in 2003, DragonFlyBSD + split off from FreeBSD. @@ -174,39 +184,41 @@ - The BSD developers are often more interested in polishing their - code than marketing it. + The BSD developers are often more interested in + polishing their code than marketing it. - 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. + 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. BSD developers tend to be more experienced than Linux - developers, and have less interest in making the system easy to use. - Newcomers tend to feel more comfortable with Linux. + developers, and have less interest in making the system easy + to use. Newcomers tend to feel more comfortable with + Linux. - In 1992, AT&T sued - 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. + In 1992, AT&T sued 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. - One detail that the lawsuit did clarify is the naming: in the - 1980s, BSD was known as BSD &unix;. With the - elimination of the last vestige of AT&T code from BSD, it - also lost the right to the name &unix;. Thus you will see - references in book titles to the 4.3BSD &unix; operating - system and the 4.4BSD operating - system. + One detail that the lawsuit did clarify is the naming: + in the 1980s, BSD was known as BSD &unix;. + With the elimination of the last vestige of AT&T code + from BSD, it also lost the right to the name &unix;. Thus + you will see references in book titles to the 4.3BSD + &unix; operating system and the 4.4BSD + operating system. @@ -214,113 +226,123 @@ Comparing BSD and Linux - So what is really the difference between, say, Debian Linux and - FreeBSD? For the average user, the difference is surprisingly small: - Both are &unix; 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. - + So what is really the difference between, say, Debian Linux + and FreeBSD? For the average user, the difference is + surprisingly small: Both are &unix; 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. Who owns BSD? 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. + 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. How is BSD developed and updated? - 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. + 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. - A large number of developers worldwide contribute to improvements - to BSD. They are divided into three kinds: + A large number of developers worldwide contribute to + improvements to BSD. They are divided into three + kinds: - Contributors write code or documentation. - They are not permitted to commit (add code) directly to the source - tree. In order for their code to be included in the system, it - must be reviewed and checked in by a registered developer, known - as a committer. + Contributors write code or + documentation. They are not permitted to commit (add + code) directly to the source tree. In order for their + code to be included in the system, it must be reviewed and + checked in by a registered developer, known as a + committer. - Committers are developers with write - access to the source tree. In order to become a committer, an - individual must show ability in the area in which they are - active. + Committers are developers with + write access to the source tree. In order to become a + committer, an individual must show ability in the area in + which they are active. - - 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. + 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. 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 - in order 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 + 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 in order 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. - This arrangement differs from Linux in a number of ways: + This arrangement differs from Linux in a number of + ways: 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. + 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. - 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. + 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. 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. + 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. - As a result of the formalized maintenance of a single SVN - source tree, BSD development is clear, and it is possible to - access any version of the system by release number or by date. - SVN 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. + As a result of the formalized maintenance of a single + SVN source tree, BSD development is clear, and it is + possible to access any version of the system by release + number or by date. SVN 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. @@ -328,105 +350,115 @@ BSD releases - 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: + 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: 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. + 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. - 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. + 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. - As bugs are found in a RELEASE version, they are fixed, and - the fixes are added to the SVN 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. + As bugs are found in a RELEASE version, they are + fixed, and the fixes are added to the SVN 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. - 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 + 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 What versions of BSD are available? - 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. + 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. - It is difficult to categorize the goals of each project: the - differences are very subjective. Basically, + It is difficult to categorize the goals of each project: + the differences are very subjective. Basically, - &os; aims for high performance and ease of use by - end users, and is a favourite of web content providers. It runs - on a number of platforms - and has significantly more users than the other projects. + &os; aims for high performance and ease of use by end + users, and is a favourite of web content providers. It + runs on a number + of platforms and has significantly more users + than the other projects. - 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; - hardware. + 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; hardware. 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. + 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. - 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, + 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. - There are also two additional BSD &unix; operating systems which are not - open source, BSD/OS and Apple's &macos; X: + There are also two additional BSD &unix; operating systems + which are not open source, BSD/OS and Apple's &macos; + X: @@ -435,23 +467,24 @@ 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 + 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. - &macos; - X is the latest version of the operating system for - &apple;'s - &mac; line. The BSD core of this operating - system, 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 - &macos; X remain closed-source, however. Several Darwin - developers are also FreeBSD committers, and - vice-versa. + &macos; + X is the latest version of the operating system + for &apple;'s &mac; line. The BSD core of this operating + system, 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 + &macos; X remain closed-source, however. Several Darwin + developers are also FreeBSD committers, and + vice-versa. @@ -460,58 +493,63 @@ How does the BSD license differ from the GNU Public license? - Linux is available under the - 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 - BSD - license is less restrictive: binary-only distributions are - allowed. This is particularly attractive for embedded - applications. + Linux is available under the 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 + BSD + license is less restrictive: binary-only + distributions are allowed. This is particularly attractive + for embedded applications. What else should I know? - 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, in order 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. + 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, in order 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. - 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. + 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. Which should I use, BSD or Linux? - What does this all mean in practice? Who should use BSD, who - should use Linux? + What does this all mean in practice? Who should use BSD, + who should use Linux? - This is a very difficult question to answer. Here are some - guidelines: + This is a very difficult question to answer. Here are + some guidelines: - 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. + 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. - 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. + 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. @@ -521,38 +559,43 @@ - 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. + 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. - The BSD license may be more attractive than the GPL. - + The BSD license may be more attractive than the + GPL. - BSD can execute most Linux binaries, while Linux can not execute BSD - binaries. Many BSD implementations can also execute binaries - from other &unix; like systems. As a result, BSD may present an - easier migration route from other systems than - Linux would. + BSD can execute most Linux binaries, while Linux can + not execute BSD binaries. Many BSD implementations can + also execute binaries from other &unix; like systems. As + a result, BSD may present an easier migration route from + other systems than Linux would. - Who provides support, service, and training for BSD? + Who provides support, service, and training for + BSD? - BSDi / FreeBSD - Mall, Inc. have been providing support contracts for + BSDi / FreeBSD Mall, + Inc. have been providing support contracts for FreeBSD for nearly a decade. - In addition, each of the projects has a list of consultants for - hire: - FreeBSD, - NetBSD, - and OpenBSD. + In addition, each of the projects has a list of + consultants for hire: FreeBSD, + NetBSD, + and OpenBSD.

From owner-svn-doc-head@freebsd.org Mon Jun 18 00:40:21 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CBC9710102AF; Mon, 18 Jun 2018 00:40:21 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7D9A386E0F; Mon, 18 Jun 2018 00:40:21 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 5EB9B1CC73; Mon, 18 Jun 2018 00:40:21 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w5I0eLc0047347; Mon, 18 Jun 2018 00:40:21 GMT (envelope-from linimon@FreeBSD.org) Received: (from linimon@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w5I0eLNC047346; Mon, 18 Jun 2018 00:40:21 GMT (envelope-from linimon@FreeBSD.org) Message-Id: <201806180040.w5I0eLNC047346@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: linimon set sender to linimon@FreeBSD.org using -f From: Mark Linimon Date: Mon, 18 Jun 2018 00:40:21 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r51865 - head/en_US.ISO8859-1/books/porters-handbook/versions X-SVN-Group: doc-head X-SVN-Commit-Author: linimon X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/porters-handbook/versions X-SVN-Commit-Revision: 51865 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2018 00:40:22 -0000 Author: linimon Date: Mon Jun 18 00:40:20 2018 New Revision: 51865 URL: https://svnweb.freebsd.org/changeset/doc/51865 Log: Document OSVERSION 1200068. Modified: head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Sun Jun 17 16:57:57 2018 (r51864) +++ head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Mon Jun 18 00:40:20 2018 (r51865) @@ -665,6 +665,14 @@ is spelled &, < is < and > is >. + 1200068 + r334930 + June 12, 2018 + 12.0-CURRENT after changing the interface between + the NFS modules. + + + 1200069 r335237 June 15, 2018 From owner-svn-doc-head@freebsd.org Mon Jun 18 06:41:37 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E36481019460; Mon, 18 Jun 2018 06:41:36 +0000 (UTC) (envelope-from ygy@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 92EE271207; Mon, 18 Jun 2018 06:41:36 +0000 (UTC) (envelope-from ygy@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 758EF20977; Mon, 18 Jun 2018 06:41:36 +0000 (UTC) (envelope-from ygy@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w5I6fasq035204; Mon, 18 Jun 2018 06:41:36 GMT (envelope-from ygy@FreeBSD.org) Received: (from ygy@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w5I6fa7I035203; Mon, 18 Jun 2018 06:41:36 GMT (envelope-from ygy@FreeBSD.org) Message-Id: <201806180641.w5I6fa7I035203@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: ygy set sender to ygy@FreeBSD.org using -f From: Guangyuan Yang Date: Mon, 18 Jun 2018 06:41:36 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r51866 - head/zh_CN.UTF-8/share/xml X-SVN-Group: doc-head X-SVN-Commit-Author: ygy X-SVN-Commit-Paths: head/zh_CN.UTF-8/share/xml X-SVN-Commit-Revision: 51866 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2018 06:41:37 -0000 Author: ygy Date: Mon Jun 18 06:41:36 2018 New Revision: 51866 URL: https://svnweb.freebsd.org/changeset/doc/51866 Log: Start syncing news from the English version from 2018. MFen: 1.110 -> r51846 Reviewed by: loader (mentor) Approved by: loader (mentor) Differential Revision: https://reviews.freebsd.org/D15845 Modified: head/zh_CN.UTF-8/share/xml/news.xml Modified: head/zh_CN.UTF-8/share/xml/news.xml ============================================================================== --- head/zh_CN.UTF-8/share/xml/news.xml Mon Jun 18 00:40:20 2018 (r51865) +++ head/zh_CN.UTF-8/share/xml/news.xml Mon Jun 18 06:41:36 2018 (r51866) @@ -20,7 +20,7 @@ the contents of will be preferred over <p>. The FreeBSD Simplified Chinese Documentation Project - Original Revision: 1.110 + Original Revision: r51846 From: www/share/xml/news.xml --> @@ -29,6 +29,310 @@ $FreeBSD$ </cvs:keyword> + <year> + <name>2018</name> + + <month> + <name>6</name> + + <day> + <name>16</name> + + <event> + <title>&os; 11.2-RC3 发布了 + +

&os; 11.2 的第三个候选发布版本现已发布。 + 用于 amd64、armv6、arm64、i386、powerpc、powerpc64 和 sparc64 + 架构的 ISO 映像文件已经发布， + 可以通过众多的 &os; + 镜像站点获得。

+ + + + + 9 + + + &os; 11.2-RC2 发布了 + +

&os; 11.2 的第二个候选发布版本现已发布。 + 用于 amd64、armv6、arm64、i386、powerpc、powerpc64 和 sparc64 + 架构的 ISO 映像文件已经发布， + 可以通过众多的 &os; + 镜像站点获得。

+ + + + + 8 + + + 服务中断 + +

部分 &os; 集群将于六月九日星期六因电力工程维护而离线。 + 服务将会受到影响，尤其是邮件列表和我们的部分网站服务。

+ +

维护窗口开始于六月九日星期六 11:00 UTC (04:00 太平洋时间)， + 结束于 20:00 UTC (13:00 太平洋时间)

。 + + + + + 2 + + + &os; 11.2-RC1 发布了 + +

&os; 11.2 的第一个候选发布版本现已发布。 + 用于 amd64、armv6、arm64、i386、powerpc、powerpc64 和 sparc64 + 架构的 ISO 映像文件已经发布， + 可以通过众多的 &os; + 镜像站点获得。

+ + + + + + 5 + + + 26 + + + &os; 11.2-BETA3 发布了 + +

&os; 11.2 的第三个 BETA 版本现已发布。 + 用于 amd64、armv6、arm64、i386、powerpc、powerpc64 和 sparc64 + 架构的 ISO 映像文件已经发布， + 可以通过众多的 &os; + 镜像站点获得。

+ + + + + 22 + +

新增 committer: + Breno Leitao + (src)

+ + + + + 21 + + +

新增 committer: + Leandro Lupori + (src)

+ + + + + 19 + + + &os; 11.2-BETA2 发布了 + +

&os; 11.2 的第二个 BETA 版本现已发布。 + 用于 amd64、armv6、arm64、i386、powerpc、powerpc64 和 sparc64 + 架构的 ISO 映像文件已经发布， + 可以通过众多的 &os; + 镜像站点获得。

+ + + + + 15 + + +

新增 committer: + Gleb Popov + (ports)

+ + + + + 12 + + + &os; 11.2-BETA1 发布了 + +

&os; 11.2 的第一个 BETA 版本现已发布。 + 用于 amd64、armv6、arm64、i386、powerpc、powerpc64 和 sparc64 + 架构的 ISO 映像文件已经发布， + 可以通过众多的 &os; + 镜像站点获得。

+ + + + + + 4 + + + 17 + + +

新增 commiter: + Sean Eric Fagan + (src)

+ + + + + 7 + + +

新增 committer: + Tom Jones + (src)

+ + + + + 4 + + +

新增 committer: + Ram Kishore Vegesna + (src)

+ + + + + + 3 + + + 23 + + +

新增 committer: + Matthias Fechner + (ports)

+ + + + + 17 + + +

新增 committer: + Eric Turgeon + (ports)

+ + + + + 16 + + +

新增 committer: + Vincenzo Maffione + (src)

+ + + + + 14 + + +

新增 committer: + Koichiro Iwao + (ports)

+ + + + + 3 + + +

新增 committer: + Fernando Apesteguia + (ports)

+ + + + + 1 + + +

新增 committer: + Devin Teske + (ports)

+ + + + + + 2 + + + 14 + + + FreeBSD 项目计划参加 Google Summer of Code 2018 + +

FreeBSD 项目很高兴地宣布参加 Google 的 2018 年 Summer of Code 项目， + 此项目资助暑期学生参与开源项目。这将是 FreeBSD 参与该项目的第 14 年。 + 2005 至 2017 年，通过暑期的编程项目，我们已经指导了超过 210 名成功的学生。

+ +

过去的成功项目包含了 Linux ABI 模拟的改进， NFSv4 ACLs， TCP 回归测试， + FUSE 文件系统支持，以及其他非常多的项目，数不胜数。 + 许多学生在参与项目后依然持做出贡献，继而成为 FreeBSD 开发者，也通过 FreeBSD + 基金会的持续支持，参加了在世界各地举办的 FreeBSD 开发者活动。

+ +

我们邀请有意向的参与者申请；更多信息，包括提案和截止日期等，请参阅 FreeBSD + 暑期项目页面。

+ + + + + 8 + + +

新增 committer: + Slava Shwartsman + (src)

+ + + + + + 1 + + + 4 + + + + 关于 Meltdown 和 Spectre 攻击 + +

关于 Meltdown + 和 Spectre 攻击： + &os; 在 2017 年十二月下旬已经注意到这个问题。 + 我们正在与 CPU 制造商一起努力，参考已发布的论文，努力减轻这类攻击对 + &os; 的影响。鉴于这类攻击的原理，补丁的发布日期暂时无法确定。

+ + + + + + 2007 @@ -65,7 +369,8 @@

我们非常高兴 22 位学生完成了他们的 FreeBSD Summer of Code 项目。在此祝贺参与项目的导师和学生，并感谢 Google 运营此项活动，并为其提供资金赞助。

+ href="http://www.google.com/">Google 运营此项活动， + 并为其提供资金赞助。

From owner-svn-doc-head@freebsd.org Mon Jun 18 07:33:38 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7EA3F101A828; Mon, 18 Jun 2018 07:33:38 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2426C72B38; Mon, 18 Jun 2018 07:33:38 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 002A9211DA; Mon, 18 Jun 2018 07:33:37 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w5I7XbJd063324; Mon, 18 Jun 2018 07:33:37 GMT (envelope-from eadler@FreeBSD.org) Received: (from eadler@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w5I7XbwH063320; Mon, 18 Jun 2018 07:33:37 GMT (envelope-from eadler@FreeBSD.org) Message-Id: <201806180733.w5I7XbwH063320@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: eadler set sender to eadler@FreeBSD.org using -f From: Eitan Adler Date: Mon, 18 Jun 2018 07:33:37 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r51867 - in head/en_US.ISO8859-1: books/faq htdocs/ipv6 htdocs/search X-SVN-Group: doc-head X-SVN-Commit-Author: eadler X-SVN-Commit-Paths: in head/en_US.ISO8859-1: books/faq htdocs/ipv6 htdocs/search X-SVN-Commit-Revision: 51867 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2018 07:33:38 -0000 Author: eadler Date: Mon Jun 18 07:33:36 2018 New Revision: 51867 URL: https://svnweb.freebsd.org/changeset/doc/51867 Log: faq+www: replace IPv6 only page with an FAQ The references wiki pages no longer exist. In addition having a standalone web page for IPv6 isn't useful anymore. Analytics shows less than one hit per month. Deleted: head/en_US.ISO8859-1/htdocs/ipv6/ipv6only.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml head/en_US.ISO8859-1/htdocs/ipv6/Makefile head/en_US.ISO8859-1/htdocs/ipv6/ipv6.ent head/en_US.ISO8859-1/htdocs/search/sitemap.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Mon Jun 18 06:41:36 2018 (r51866) +++ head/en_US.ISO8859-1/books/faq/book.xml Mon Jun 18 07:33:36 2018 (r51867) @@ -46,6 +46,7 @@ 2015 2016 2017 + 2018 The &os; Documentation Project @@ -5260,6 +5261,25 @@ Key F15 A A Menu Workplace Nop

net.link.ether.inet.log_arp_wrong_iface to 0. + + + + + + How do I compile an IPv6 only kernel? + + + + + Configure your kernel with these settings: + +include GENERIC +ident GENERIC-IPV6ONLY +makeoptions MKMODULESENV+="WITHOUT_INET_SUPPORT=" +nooptions INET +nodevice gre + + Modified: head/en_US.ISO8859-1/htdocs/ipv6/Makefile ============================================================================== --- head/en_US.ISO8859-1/htdocs/ipv6/Makefile Mon Jun 18 06:41:36 2018 (r51866) +++ head/en_US.ISO8859-1/htdocs/ipv6/Makefile Mon Jun 18 07:33:36 2018 (r51867) @@ -8,7 +8,6 @@ .endif DOCS+= index.xml -DOCS+= ipv6only.xml DOCS+= w6d.xml DOCS+= w6l.xml DOCS+= w6d-www-stats.xml Modified: head/en_US.ISO8859-1/htdocs/ipv6/ipv6.ent ============================================================================== --- head/en_US.ISO8859-1/htdocs/ipv6/ipv6.ent Mon Jun 18 06:41:36 2018 (r51866) +++ head/en_US.ISO8859-1/htdocs/ipv6/ipv6.ent Mon Jun 18 07:33:36 2018 (r51867) @@ -36,7 +36,6 @@

Category Navigation

IPv6 in FreeBSD
No-IPv4 support (IPv6-only)
World IPv6 Launch
World IPv6 Day

Signed Checksum Signatures

Installation Image Checksums

Virtual Machine Image Checksums

SD Card Image Checksums

FreeBSD 11.1-RELEASE Errata

The FreeBSD Project

FreeBSD 11.1-RELEASE Errata

The FreeBSD Project

3.�Errata Notices

3.�Errata Notices

4.�Open Issues

4.�Open Issues

FreeBSD 11.1-RELEASE Errata

The FreeBSD Project

FreeBSD 11.1-RELEASE Errata

The FreeBSD Project

1.�Installing FreeBSD

2.2.�Upgrading Using “FreeBSD Update”

< a id="intro">1.�Introduction

1.�Introduction

3.2.�Errata Notices

3.2.�Errata Notices

4.4.�`/etc/rc.d` - Scripts

5.�Kernel

5.�Kernel

5.1.�General Kernel Changes

FreeBSD 11.2-RELEASE Errata

The FreeBSD Project

1.�Introduction

2.�Security Advisories

3.�Errata Notices

4.�Open Issues

5.�Late-Breaking News

Category Navigation

The X Window System

Hardware

Related Operating System Projects

X Window System

�ϡ��ɥ��

��Ϣ��륪�ڥ졼�ƥ��󥰥��ƥ�Υץ��

Category Navigation

The X Window System

Hardware

Related Operating System Projects

X Window System

�ϡ��ɥ�����

��Ϣ���륪�ڥ졼�ƥ��󥰥����ƥ�Υץ���������

Signed Checksum Signatures

Installation Image Checksums

Virtual Machine Image Checksums

SD Card Image Checksums

FreeBSD 11.1-RELEASE Errata

The FreeBSD Project

FreeBSD 11.1-RELEASE Errata

The FreeBSD Project

3.�Errata Notices

3.�Errata Notices

4.�Open Issues

4.�Open Issues

FreeBSD 11.1-RELEASE Errata

The FreeBSD Project

FreeBSD 11.1-RELEASE Errata

The FreeBSD Project

1.�Installing FreeBSD

2.2.�Upgrading Using “FreeBSD Update”

< a id="intro">1.�Introduction

1.�Introduction

3.2.�Errata Notices

3.2.�Errata Notices

4.4.�/etc/rc.d - Scripts

5.�Kernel

5.�Kernel

5.1.�General Kernel Changes

FreeBSD 11.2-RELEASE Errata

The FreeBSD Project

1.�Introduction

2.�Security Advisories

3.�Errata Notices

4.�Open Issues

5.�Late-Breaking News

�ϡ��ɥ��

��Ϣ��륪�ڥ졼�ƥ��󥰥��ƥ�Υץ��

4.4.�`/etc/rc.d` - Scripts