diff --git a/documentation/content/en/books/arch-handbook/_index.adoc b/documentation/content/en/books/arch-handbook/_index.adoc index 777ef437e2..bb01f09331 100644 --- a/documentation/content/en/books/arch-handbook/_index.adoc +++ b/documentation/content/en/books/arch-handbook/_index.adoc @@ -1,55 +1,55 @@ --- title: FreeBSD Architecture Handbook authors: - author: The FreeBSD Documentation Project copyright: Copyright © 2000-2006, 2012-2021 The FreeBSD Documentation Project description: For FreeBSD system developers. This book covers the architectural details of many important FreeBSD kernel subsystems trademarks: ["freebsd", "apple", "microsoft", "unix", "general"] tags: ["Arch Handbook", "FreeBSD"] next: books/arch-handbook/parti add_single_page_link: true showBookMenu: true weight: 0 path: "/books/arch-handbook/" bookOrder: 50 --- = FreeBSD Architecture Handbook :doctype: book :toc: macro :toclevels: 1 :icons: font :sectnums: :sectnumlevels: 6 :partnums: :source-highlighter: rouge :experimental: :images-path: books/arch-handbook/ ifdef::env-beastie[] ifdef::backend-html5[] include::shared/authors.adoc[] include::shared/mirrors.adoc[] include::shared/releases.adoc[] include::shared/attributes/attributes-{{% lang %}}.adoc[] include::shared/{{% lang %}}/teams.adoc[] include::shared/{{% lang %}}/mailing-lists.adoc[] include::shared/{{% lang %}}/urls.adoc[] endif::[] ifdef::backend-pdf,backend-epub3[] include::../../../../../shared/asciidoctor.adoc[] endif::[] endif::[] ifndef::env-beastie[] include::../../../../../shared/asciidoctor.adoc[] endif::[] [.abstract-title] Abstract Welcome to the FreeBSD Architecture Handbook. This manual is a _work in progress_ and is the work of many individuals. Many sections do not yet exist and some of those that do exist need to be updated. If you are interested in helping with this project, send email to the {freebsd-doc}. -The latest version of this document is always available from the link:https://www.FreeBSD.org/[FreeBSD World Wide Web server]. It may also be downloaded in a variety of formats and compression options from the https://download.freebsd.org/doc/[FreeBSD FTP server] or one of the numerous extref:{handbook}[mirror sites, mirrors-ftp]. +The latest version of this document is always available from the link:https://www.FreeBSD.org/[FreeBSD World Wide Web server]. It may also be downloaded in a variety of formats and compression options from the https://download.freebsd.org/doc/[FreeBSD download server] or one of the numerous extref:{handbook}[mirror sites, mirrors]. ''' diff --git a/documentation/content/en/books/arch-handbook/book.adoc b/documentation/content/en/books/arch-handbook/book.adoc index d8993bdf12..15b9bdede4 100644 --- a/documentation/content/en/books/arch-handbook/book.adoc +++ b/documentation/content/en/books/arch-handbook/book.adoc @@ -1,82 +1,82 @@ --- title: FreeBSD Architecture Handbook authors: - author: The FreeBSD Documentation Project copyright: Copyright © 2000-2006, 2012-2021 The FreeBSD Documentation Project description: For FreeBSD system developers. This book covers the architectural details of many important FreeBSD kernel subsystems trademarks: ["freebsd", "apple", "microsoft", "unix", "general"] tags: ["Arch Handbook", "FreeBSD"] add_split_page_link: true --- = FreeBSD Architecture Handbook :doctype: book :toc: macro :toclevels: 2 :icons: font :sectnums: :sectnumlevels: 6 :partnums: :source-highlighter: rouge :experimental: :book: true :pdf: false ifdef::env-beastie[] ifdef::backend-html5[] include::shared/authors.adoc[] include::shared/mirrors.adoc[] include::shared/releases.adoc[] include::shared/attributes/attributes-{{% lang %}}.adoc[] include::shared/{{% lang %}}/teams.adoc[] include::shared/{{% lang %}}/mailing-lists.adoc[] include::shared/{{% lang %}}/urls.adoc[] :chapters-path: content/{{% lang %}}/books/arch-handbook/ endif::[] ifdef::backend-pdf,backend-epub3[] :chapters-path: include::../../../../../shared/asciidoctor.adoc[] endif::[] endif::[] ifndef::env-beastie[] :chapters-path: include::../../../../../shared/asciidoctor.adoc[] endif::[] [.abstract-title] Abstract Welcome to the FreeBSD Architecture Handbook. This manual is a _work in progress_ and is the work of many individuals. Many sections do not yet exist and some of those that do exist need to be updated. If you are interested in helping with this project, send email to the {freebsd-doc}. -The latest version of this document is always available from the link:https://www.FreeBSD.org/[FreeBSD World Wide Web server]. It may also be downloaded in a variety of formats and compression options from the https://download.freebsd.org/doc/[FreeBSD FTP server] or one of the numerous extref:{handbook}[mirror sites, mirrors-ftp]. +The latest version of this document is always available from the link:https://www.FreeBSD.org/[FreeBSD World Wide Web server]. It may also be downloaded in a variety of formats and compression options from the https://download.freebsd.org/doc/[FreeBSD download server] or one of the numerous extref:{handbook}[mirror sites, mirrors]. ''' toc::[] // Section one include::{chapters-path}parti.adoc[] include::{chapters-path}boot/_index.adoc[leveloffset=+1] include::{chapters-path}locking/_index.adoc[leveloffset=+1] include::{chapters-path}kobj/_index.adoc[leveloffset=+1] include::{chapters-path}jail/_index.adoc[leveloffset=+1] include::{chapters-path}sysinit/_index.adoc[leveloffset=+1]] include::{chapters-path}mac/_index.adoc[leveloffset=+1] include::{chapters-path}vm/_index.adoc[leveloffset=+1] include::{chapters-path}smp/_index.adoc[leveloffset=+1] // Section two include::{chapters-path}partii.adoc[] include::{chapters-path}driverbasics/_index.adoc[leveloffset=+1] include::{chapters-path}isa/_index.adoc[leveloffset=+1] include::{chapters-path}pci/_index.adoc[leveloffset=+1] include::{chapters-path}scsi/_index.adoc[leveloffset=+1] include::{chapters-path}usb/_index.adoc[leveloffset=+1] include::{chapters-path}newbus/_index.adoc[leveloffset=+1] include::{chapters-path}sound/_index.adoc[leveloffset=+1] include::{chapters-path}pccard/_index.adoc[leveloffset=+1] // Section three include::{chapters-path}partiii.adoc[] include::{chapters-path}bibliography/_index.adoc[leveloffset=+1] diff --git a/documentation/content/en/books/developers-handbook/_index.adoc b/documentation/content/en/books/developers-handbook/_index.adoc index add9336ec8..503fd905f8 100644 --- a/documentation/content/en/books/developers-handbook/_index.adoc +++ b/documentation/content/en/books/developers-handbook/_index.adoc @@ -1,59 +1,59 @@ --- title: FreeBSD Developers' Handbook authors: - author: The FreeBSD Documentation Project copyright: 1995-2021 The FreeBSD Documentation Project description: For people who want to develop software for FreeBSD (and not just people who are developing FreeBSD itself) trademarks: ["freebsd", "apple", "ibm", "ieee", "intel", "linux", "microsoft", "opengroup", "sun", "general"] next: books/developers-handbook/parti bookOrder: 25 tags: ["FreeBSD Developers' Handbook"] add_single_page_link: true showBookMenu: true weight: 0 path: "/books/developers-handbook/" --- = FreeBSD Developers' Handbook :doctype: book :toc: macro :toclevels: 1 :icons: font :sectnums: :sectnumlevels: 6 :partnums: :source-highlighter: rouge :experimental: :images-path: books/developers-handbook/ ifdef::env-beastie[] ifdef::backend-html5[] include::shared/authors.adoc[] include::shared/mirrors.adoc[] include::shared/releases.adoc[] include::shared/attributes/attributes-{{% lang %}}.adoc[] include::shared/{{% lang %}}/teams.adoc[] include::shared/{{% lang %}}/mailing-lists.adoc[] include::shared/{{% lang %}}/urls.adoc[] endif::[] ifdef::backend-pdf,backend-epub3[] include::../../../../../shared/asciidoctor.adoc[] endif::[] endif::[] ifndef::env-beastie[] include::../../../../../shared/asciidoctor.adoc[] endif::[] [.abstract-title] Abstract Welcome to the Developers' Handbook. This manual is a _work in progress_ and is the work of many individuals. Many sections do not yet exist and some of those that do exist need to be updated. If you are interested in helping with this project, send email to the {freebsd-doc}. The latest version of this document is always available from the link:https://www.FreeBSD.org[FreeBSD World Wide Web server]. -It may also be downloaded in a variety of formats and compression options from the link:https://download.freebsd.org/doc/[FreeBSD FTP server] or one of the numerous extref:{handbook}[mirror sites, mirrors-ftp]. +It may also be downloaded in a variety of formats and compression options from the link:https://download.freebsd.org/doc/[FreeBSD download server] or one of the numerous extref:{handbook}[mirror sites, mirrors]. ''' diff --git a/documentation/content/en/books/developers-handbook/book.adoc b/documentation/content/en/books/developers-handbook/book.adoc index 06061218ff..3cb4f7ccca 100644 --- a/documentation/content/en/books/developers-handbook/book.adoc +++ b/documentation/content/en/books/developers-handbook/book.adoc @@ -1,87 +1,87 @@ --- title: FreeBSD Developers' Handbook authors: - author: The FreeBSD Documentation Project copyright: 1995-2021 The FreeBSD Documentation Project description: For people who want to develop software for FreeBSD (and not just people who are developing FreeBSD itself) trademarks: ["freebsd", "apple", "ibm", "ieee", "intel", "linux", "microsoft", "opengroup", "sun", "general"] tags: ["FreeBSD Developers' Handbook"] add_split_page_link: true --- = FreeBSD Developers' Handbook :doctype: book :toc: macro :toclevels: 2 :icons: font :sectnums: :sectnumlevels: 6 :partnums: :source-highlighter: rouge :experimental: :book: true :pdf: false ifdef::env-beastie[] ifdef::backend-html5[] include::shared/authors.adoc[] include::shared/mirrors.adoc[] include::shared/releases.adoc[] include::shared/attributes/attributes-{{% lang %}}.adoc[] include::shared/{{% lang %}}/teams.adoc[] include::shared/{{% lang %}}/mailing-lists.adoc[] include::shared/{{% lang %}}/urls.adoc[] :chapters-path: content/{{% lang %}}/books/developers-handbook/ endif::[] ifdef::backend-pdf,backend-epub3[] :chapters-path: include::../../../../../shared/asciidoctor.adoc[] endif::[] endif::[] ifndef::env-beastie[] :chapters-path: include::../../../../../shared/asciidoctor.adoc[] endif::[] [.abstract-title] Abstract Welcome to the Developers' Handbook. This manual is a _work in progress_ and is the work of many individuals. Many sections do not yet exist and some of those that do exist need to be updated. If you are interested in helping with this project, send email to the {freebsd-doc}. The latest version of this document is always available from the link:https://www.FreeBSD.org[FreeBSD World Wide Web server]. -It may also be downloaded in a variety of formats and compression options from the link:https://download.freebsd.org/doc/[FreeBSD FTP server] or one of the numerous extref:{handbook}[mirror sites, mirrors-ftp]. +It may also be downloaded in a variety of formats and compression options from the link:https://download.freebsd.org/doc/[FreeBSD download server] or one of the numerous extref:{handbook}[mirror sites, mirrors]. ''' toc::[] // Section one include::{chapters-path}parti.adoc[] include::{chapters-path}introduction/_index.adoc[leveloffset=+1] include::{chapters-path}tools/_index.adoc[leveloffset=+1] include::{chapters-path}secure/_index.adoc[leveloffset=+1] include::{chapters-path}l10n/_index.adoc[leveloffset=+1] include::{chapters-path}policies/_index.adoc[leveloffset=+1] include::{chapters-path}testing/_index.adoc[leveloffset=+1] // Section two include::{chapters-path}partii.adoc[] include::{chapters-path}sockets/_index.adoc[leveloffset=+1] include::{chapters-path}ipv6/_index.adoc[leveloffset=+1] // Section three include::{chapters-path}partiii.adoc[] include::{chapters-path}kernelbuild/_index.adoc[leveloffset=+1] include::{chapters-path}kerneldebug/_index.adoc[leveloffset=+1] // Section four include::{chapters-path}partiv.adoc[] include::{chapters-path}x86/_index.adoc[leveloffset=+1] // Appendices include::{chapters-path}partv.adoc[] include::{chapters-path}bibliography/_index.adoc[leveloffset=+1] diff --git a/documentation/content/en/books/handbook/_index.adoc b/documentation/content/en/books/handbook/_index.adoc index fd7eb8115d..9fac327273 100644 --- a/documentation/content/en/books/handbook/_index.adoc +++ b/documentation/content/en/books/handbook/_index.adoc @@ -1,62 +1,62 @@ --- title: FreeBSD Handbook authors: - author: The FreeBSD Documentation Project copyright: 1995-2022 The FreeBSD Documentation Project description: A constantly evolving, comprehensive resource for FreeBSD users trademarks: ["freebsd", "ibm", "ieee", "redhat", "3com", "adobe", "apple", "intel", "linux", "microsoft", "opengroup", "sun", "realnetworks", "oracle", "3ware", "arm", "adaptec", "google", "heidelberger", "intuit", "lsilogic", "themathworks", "thomson", "vmware", "wolframresearch", "xiph", "xfree86", "general"] tags: ["FreeBSD Handbook", "Handbook"] next: books/handbook/preface add_single_page_link: true showBookMenu: true weight: 0 path: "/books/handbook/" bookOrder: 1 --- = FreeBSD Handbook :doctype: book :toc: macro :toclevels: 1 :icons: font :sectnums: :sectnumlevels: 6 :partnums: :source-highlighter: rouge :experimental: :images-path: books/handbook/ ifdef::env-beastie[] ifdef::backend-html5[] include::shared/authors.adoc[] include::shared/mirrors.adoc[] include::shared/releases.adoc[] include::shared/attributes/attributes-{{% lang %}}.adoc[] include::shared/{{% lang %}}/teams.adoc[] include::shared/{{% lang %}}/mailing-lists.adoc[] include::shared/{{% lang %}}/urls.adoc[] endif::[] ifdef::backend-pdf,backend-epub3[] include::../../../../../shared/asciidoctor.adoc[] endif::[] endif::[] ifndef::env-beastie[] include::../../../../../shared/asciidoctor.adoc[] endif::[] [.abstract-title] Abstract Welcome to FreeBSD! This handbook covers the installation and day to day use of _FreeBSD {rel130-current}-RELEASE_ and _FreeBSD {rel122-current}-RELEASE_. This book is the result of ongoing work by many individuals. Some sections might be outdated. Those interested in helping to update and expand this document should send email to the {freebsd-doc}. The latest version of this book is available from the https://www.FreeBSD.org/[FreeBSD web site]. Previous versions can be obtained from https://docs.FreeBSD.org/doc/[https://docs.FreeBSD.org/doc/]. -The book can be downloaded in a variety of formats and compression options from the https://download.freebsd.org/doc/[FreeBSD server] or one of the numerous link:./mirrors#mirrors-http[mirror sites]. +The book can be downloaded in a variety of formats and compression options from the https://download.freebsd.org/doc/[FreeBSD download server] or one of the numerous link:./mirrors#mirrors[mirror sites]. Printed copies can be purchased at the https://www.freebsdmall.com/[FreeBSD Mall]. Searches can be performed on the handbook and other documents on the link:https://www.FreeBSD.org/search/[search page]. ''' diff --git a/documentation/content/en/books/handbook/book.adoc b/documentation/content/en/books/handbook/book.adoc index bdb1c7f27b..1dcba8c6bf 100644 --- a/documentation/content/en/books/handbook/book.adoc +++ b/documentation/content/en/books/handbook/book.adoc @@ -1,161 +1,161 @@ --- title: FreeBSD Handbook authors: - author: The FreeBSD Documentation Project copyright: 1995-2022 The FreeBSD Documentation Project description: A constantly evolving, comprehensive resource for FreeBSD users trademarks: ["freebsd", "ibm", "ieee", "redhat", "3com", "adobe", "apple", "intel", "linux", "microsoft", "opengroup", "sun", "realnetworks", "oracle", "3ware", "arm", "adaptec", "google", "heidelberger", "intuit", "lsilogic", "themathworks", "thomson", "vmware", "wolframresearch", "xiph", "xfree86", "general"] tags: ["FreeBSD Handbook", "Handbook"] add_split_page_link: true --- = FreeBSD Handbook :doctype: book :toc: macro :toclevels: 2 :icons: font :sectnums: :sectnumlevels: 6 :partnums: :source-highlighter: rouge :experimental: :book: true :pdf: false :images-path: books/handbook/ ifdef::env-beastie[] ifdef::backend-html5[] include::shared/authors.adoc[] include::shared/mirrors.adoc[] include::shared/releases.adoc[] include::shared/attributes/attributes-{{% lang %}}.adoc[] include::shared/{{% lang %}}/teams.adoc[] include::shared/{{% lang %}}/mailing-lists.adoc[] include::shared/{{% lang %}}/urls.adoc[] :chapters-path: content/{{% lang %}}/books/handbook/ endif::[] ifdef::backend-pdf,backend-epub3[] :chapters-path: include::../../../../../shared/asciidoctor.adoc[] endif::[] endif::[] ifndef::env-beastie[] :chapters-path: include::../../../../../shared/asciidoctor.adoc[] endif::[] [.abstract-title] Abstract Welcome to FreeBSD! This handbook covers the installation and day to day use of _FreeBSD {rel130-current}-RELEASE_ and _FreeBSD {rel123-current}-RELEASE_. This book is the result of ongoing work by many individuals. Some sections might be outdated. Those interested in helping to update and expand this document should send email to the {freebsd-doc}. The latest version of this book is available from the https://www.FreeBSD.org/[FreeBSD web site]. Previous versions can be obtained from https://docs.FreeBSD.org/doc/[https://docs.FreeBSD.org/doc/]. -The book can be downloaded in a variety of formats and compression options from the https://download.freebsd.org/doc/[FreeBSD server] or one of the numerous crossref:mirrors[mirrors-http,mirror sites]. +The book can be downloaded in a variety of formats and compression options from the https://download.freebsd.org/doc/[FreeBSD download server] or one of the numerous crossref:mirrors[mirrors,mirror sites]. Printed copies can be purchased at the https://www.freebsdmall.com/[FreeBSD Mall]. Searches can be performed on the handbook and other documents on the link:https://www.FreeBSD.org/search/[search page]. ''' toc::[] :sectnums!: include::{chapters-path}preface/_index.adoc[leveloffset=+1] :sectnums: // Section one include::{chapters-path}parti.adoc[] include::{chapters-path}introduction/_index.adoc[leveloffset=+1] include::{chapters-path}bsdinstall/_index.adoc[leveloffset=+1] include::{chapters-path}basics/_index.adoc[leveloffset=+1] include::{chapters-path}ports/_index.adoc[leveloffset=+1] include::{chapters-path}x11/_index.adoc[leveloffset=+1] // Section two include::{chapters-path}partii.adoc[] include::{chapters-path}desktop/_index.adoc[leveloffset=+1] include::{chapters-path}multimedia/_index.adoc[leveloffset=+1] include::{chapters-path}kernelconfig/_index.adoc[leveloffset=+1] include::{chapters-path}printing/_index.adoc[leveloffset=+1] include::{chapters-path}linuxemu/_index.adoc[leveloffset=+1] include::{chapters-path}wine/_index.adoc[leveloffset=+1] // Section three include::{chapters-path}partiii.adoc[] include::{chapters-path}config/_index.adoc[leveloffset=+1] include::{chapters-path}boot/_index.adoc[leveloffset=+1] include::{chapters-path}security/_index.adoc[leveloffset=+1] include::{chapters-path}jails/_index.adoc[leveloffset=+1] include::{chapters-path}mac/_index.adoc[leveloffset=+1] include::{chapters-path}audit/_index.adoc[leveloffset=+1] include::{chapters-path}disks/_index.adoc[leveloffset=+1] include::{chapters-path}geom/_index.adoc[leveloffset=+1] include::{chapters-path}zfs/_index.adoc[leveloffset=+1] include::{chapters-path}filesystems/_index.adoc[leveloffset=+1] include::{chapters-path}virtualization/_index.adoc[leveloffset=+1] include::{chapters-path}l10n/_index.adoc[leveloffset=+1] include::{chapters-path}cutting-edge/_index.adoc[leveloffset=+1] include::{chapters-path}dtrace/_index.adoc[leveloffset=+1] include::{chapters-path}usb-device-mode/_index.adoc[leveloffset=+1] // Section four include::{chapters-path}partiv.adoc[] include::{chapters-path}serialcomms/_index.adoc[leveloffset=+1] include::{chapters-path}ppp-and-slip/_index.adoc[leveloffset=+1] include::{chapters-path}mail/_index.adoc[leveloffset=+1] include::{chapters-path}network-servers/_index.adoc[leveloffset=+1] include::{chapters-path}firewalls/_index.adoc[leveloffset=+1] include::{chapters-path}advanced-networking/_index.adoc[leveloffset=+1] // Section five include::{chapters-path}partv.adoc[] :sectnums!: include::{chapters-path}mirrors/_index.adoc[leveloffset=+1] include::{chapters-path}bibliography/_index.adoc[leveloffset=+1] include::{chapters-path}eresources/_index.adoc[leveloffset=+1] include::{chapters-path}pgpkeys/_index.adoc[leveloffset=+1] :sectnums: diff --git a/documentation/content/en/books/handbook/eresources/_index.adoc b/documentation/content/en/books/handbook/eresources/_index.adoc index e437769451..8aee215974 100644 --- a/documentation/content/en/books/handbook/eresources/_index.adoc +++ b/documentation/content/en/books/handbook/eresources/_index.adoc @@ -1,1320 +1,1177 @@ --- title: Appendix C. Resources on the Internet part: Part V. Appendices prev: books/handbook/bibliography next: books/handbook/pgpkeys description: FreeBSD additional resources on internet like websites, mailing lists, mirrors, etc tags: ["eresources", "Websites", "Mailing Lists", "Usenet", "Newsgroups"] showBookMenu: true weight: 41 path: "/books/handbook/" --- [appendix] [[eresources]] = Resources on the Internet :doctype: book :toc: macro :toclevels: 1 :icons: font :sectnums: :sectnumlevels: 6 :sectnumoffset: C :partnums: :source-highlighter: rouge :experimental: :images-path: books/handbook/eresources/ ifdef::env-beastie[] ifdef::backend-html5[] :imagesdir: ../../../../images/{images-path} endif::[] ifndef::book[] include::shared/authors.adoc[] include::shared/mirrors.adoc[] include::shared/releases.adoc[] include::shared/attributes/attributes-{{% lang %}}.adoc[] include::shared/{{% lang %}}/teams.adoc[] include::shared/{{% lang %}}/mailing-lists.adoc[] include::shared/{{% lang %}}/urls.adoc[] toc::[] endif::[] ifdef::backend-pdf,backend-epub3[] include::../../../../../shared/asciidoctor.adoc[] endif::[] endif::[] ifndef::env-beastie[] toc::[] include::../../../../../shared/asciidoctor.adoc[] endif::[] The rapid pace of FreeBSD progress makes print media impractical as a means of following the latest developments. Electronic resources are the best, if not often the only, way to stay informed of the latest advances. Since FreeBSD is a volunteer effort, the user community itself also generally serves as a "technical support department" of sorts, with electronic mail, web forums, and USENET news being the most effective way of reaching that community. The most important points of contact with the FreeBSD user community are outlined below. There is a possibly more up to date list on the link:https://wiki.freebsd.org/Community[community portal on the FreeBSD Wiki]. Please send other resources not mentioned here to the {freebsd-doc} so that they may also be included. [[eresources-www]] == Websites * The link:https://forums.FreeBSD.org/[FreeBSD Forums] provide a web based discussion forum for FreeBSD questions and technical discussion. * The link:https://wiki.FreeBSD.org/[FreeBSD Wiki] provides various bits of information that hadn't yet made it into the Handbook. * The link:https://docs.FreeBSD.org/[FreeBSD Documentation website] doesn't provide just the Users's Handbook; there are other handbooks and articles that are worth a read. * The link:https://freebsdfoundation.org/our-work/journal/browser-based-edition/[FreeBSD Journal] is a free, professionally-edited, bi-monthly technical magazine released by link:https://freebsdfoundation.org[FreeBSD Foundation]. * The link:http://www.youtube.com/bsdconferences[BSDConferences YouTube Channel] provides a collection of high quality videos from BSD conferences around the world. This is a great way to watch key developers give presentations about new work in FreeBSD. * link:https://www.freebsd.org/status/[FreeBSD Status Reports] are released every three months and track progress of FreeBSD development. * There's a link:https://www.reddit.com/r/freebsd/[FreeBSD-focused Reddit group] at r/freebsd. * link:https://superuser.com/questions/tagged/freebsd[Super User] and link:https://serverfault.com/questions/tagged/freebsd[Server Fault], the Stack Exchange services for system administrators. * link:https://wiki.freebsd.org/Discord[FreeBSD Discord server], a communications and community-building service, where FreeBSD community members can socialise, obtain support or support others, learn, contribute, collaborate, and stay up to date with all things FreeBSD-related. * link:https://wiki.freebsd.org/IRC/Channels[IRC channels], a widely implemented, technically mature, open standard text chat. * A link:https://bsd.network/[BSD-oriented social network], the bsd.network Mastodon instance. [[eresources-mail]] == Mailing Lists The mailing lists are the most direct way of addressing questions or opening a technical discussion to a concentrated FreeBSD audience. There are a wide variety of lists on a number of different FreeBSD topics. Sending questions to the most appropriate mailing list will invariably assure a faster and more accurate response. The charters for the various lists are given at the bottom of this document. _Please read the charter before joining or sending mail to any list_. Most list subscribers receive many hundreds of FreeBSD related messages every day, and the charters and rules for use are meant to keep the signal-to-noise ratio of the lists high. To do less would see the mailing lists ultimately fail as an effective communications medium for the Project. [NOTE] ==== _To test the ability to send email to FreeBSD lists, send a test message to {freebsd-test}._ Please do not send test messages to any other list. ==== When in doubt about what list to post a question to, see extref:{freebsd-questions-article}[How to get best results from the FreeBSD-questions mailing list]. Before posting to any list, please learn about how to best use the mailing lists, such as how to help avoid frequently-repeated discussions, by reading the extref:{mailing-list-faq}[Mailing List Frequently Asked Questions] (FAQ) document. Archives are kept for all of the mailing lists and can be searched using the link:https://www.FreeBSD.org/search/[FreeBSD World Wide Web server]. The keyword searchable archive offers an excellent way of finding answers to frequently asked questions and should be consulted before posting a question. Note that this also means that messages sent to FreeBSD mailing lists are archived in perpetuity. When protecting privacy is a concern, consider using a disposable secondary email address and posting only public information. [[eresources-summary]] === List Summary _General lists:_ The following are general lists which anyone is free (and encouraged) to join: [.informaltable] [cols="20%,80%", frame="none", options="header"] |=== | List | Purpose |link:{freebsd-advocacy-url}[freebsd-advocacy] |FreeBSD Evangelism |link:{freebsd-announce-url}[freebsd-announce] |Important events and Project milestones (moderated) |link:{freebsd-arch-url}[freebsd-arch] |Architecture and design discussions |link:{freebsd-bugbusters-url}[freebsd-bugbusters] |Discussions pertaining to the maintenance of the FreeBSD problem report database and related tools |link:{freebsd-bugs-url}[freebsd-bugs] |Bug reports |link:{freebsd-chat-url}[freebsd-chat] |Non-technical items related to the FreeBSD community |link:{freebsd-chromium-url}[freebsd-chromium] |FreeBSD-specific Chromium issues |link:{freebsd-current-url}[freebsd-current] |Discussion concerning the use of FreeBSD-CURRENT |link:{freebsd-isp-url}[freebsd-isp] |Issues for Internet Service Providers using FreeBSD |link:{freebsd-jobs-url}[freebsd-jobs] |FreeBSD employment and consulting opportunities |link:{freebsd-quarterly-calls-url}[freebsd-quarterly-calls] |Calls for quarterly status reports (moderated) |link:{freebsd-questions-url}[freebsd-questions] |User questions and technical support |link:{freebsd-security-notifications-url}[freebsd-security-notifications] |Security notifications (moderated) |link:{freebsd-stable-url}[freebsd-stable] |Discussion concerning the use of FreeBSD-STABLE |link:{freebsd-test-url}[freebsd-test] |Where to send test messages instead of to one of the actual lists |link:{freebsd-women-url}[freebsd-women] |FreeBSD advocacy for women |=== _Technical lists:_ The following lists are for technical discussion. Read the charter for each list carefully before joining or sending mail to one as there are firm guidelines for their use and content. [.informaltable] [cols="20%,80%", frame="none", options="header"] |=== | List | Purpose |link:{freebsd-acpi-url}[freebsd-acpi] |ACPI and power management development |link:{freebsd-amd64-url}[freebsd-amd64] |Porting FreeBSD to AMD64 systems (moderated) |link:{freebsd-apache-url}[freebsd-apache] |Discussion about Apache related ports |link:{freebsd-arm-url}[freebsd-arm] |Porting FreeBSD to ARM(R) processors |link:{freebsd-atm-url}[freebsd-atm] |Using ATM networking with FreeBSD |link:{freebsd-bluetooth-url}[freebsd-bluetooth] |Using Bluetooth(R) technology in FreeBSD |link:{freebsd-cloud-url}[freebsd-cloud] |FreeBSD on cloud platforms (EC2, GCE, Azure, etc.) |link:{freebsd-cluster-url}[freebsd-cluster] |Using FreeBSD in a clustered environment |link:{freebsd-database-url}[freebsd-database] |Discussing database use and development under FreeBSD |link:{freebsd-desktop-url}[freebsd-desktop] |Using and improving FreeBSD on the desktop |link:{dev-ci-url}[dev-ci] |Build and test reports from the Continuous Integration servers |link:{dev-reviews-url}[dev-reviews] |Notifications of the FreeBSD review system |link:{freebsd-doc-url}[freebsd-doc] |Creating FreeBSD related documents |link:{freebsd-drivers-url}[freebsd-drivers] |Writing device drivers for FreeBSD |link:{freebsd-dtrace-url}[freebsd-dtrace] |Using and working on DTrace in FreeBSD |link:{freebsd-eclipse-url}[freebsd-eclipse] |FreeBSD users of Eclipse IDE, tools, rich client applications and ports. |link:{freebsd-elastic-url}[freebsd-elastic] |FreeBSD-specific ElasticSearch discussions |link:{freebsd-embedded-url}[freebsd-embedded] |Using FreeBSD in embedded applications |link:{freebsd-emulation-url}[freebsd-emulation] |Emulation of other systems such as Linux/MS-DOS(R)/Windows(R) |link:{freebsd-enlightenment-url}[freebsd-enlightenment] |Porting Enlightenment and Enlightenment applications |link:{freebsd-erlang-url}[freebsd-erlang] |FreeBSD-specific Erlang discussions |link:{freebsd-firewire-url}[freebsd-firewire] |FreeBSD FireWire(R) (iLink, IEEE 1394) technical discussion |link:{freebsd-fortran-url}[freebsd-fortran] |Fortran on FreeBSD |link:{freebsd-fs-url}[freebsd-fs] |File systems |link:{freebsd-games-url}[freebsd-games] |Support for Games on FreeBSD |link:{freebsd-gecko-url}[freebsd-gecko] |Gecko Rendering Engine issues |link:{freebsd-geom-url}[freebsd-geom] |GEOM-specific discussions and implementations |link:{freebsd-git-url}[freebsd-git] |Discussion of git use in the FreeBSD project |link:{freebsd-gnome-url}[freebsd-gnome] |Porting GNOME and GNOME applications |link:{freebsd-hackers-url}[freebsd-hackers] |General technical discussion |link:{freebsd-haskell-url}[freebsd-haskell] |FreeBSD-specific Haskell issues and discussions |link:{freebsd-hardware-url}[freebsd-hardware] |General discussion of hardware for running FreeBSD |link:{freebsd-i18n-url}[freebsd-i18n] |FreeBSD Internationalization |link:{freebsd-infiniband-url}[freebsd-infiniband] |Infiniband on FreeBSD |link:{freebsd-ipfw-url}[freebsd-ipfw] |Technical discussion concerning the redesign of the IP firewall code |link:{freebsd-isdn-url}[freebsd-isdn] |ISDN developers |link:{freebsd-jail-url}[freebsd-jail] |Discussion about the man:jail[8] facility |link:{freebsd-java-url}[freebsd-java] |Java(TM) developers and people porting JDK(TM)s to FreeBSD |link:{freebsd-kde-url}[freebsd-kde] |Porting KDE and KDE applications |link:{freebsd-mips-url}[freebsd-mips] |Porting FreeBSD to MIPS(R) |link:{freebsd-mono-url}[freebsd-mono] |Mono and C# applications on FreeBSD |link:{freebsd-multimedia-url}[freebsd-multimedia] |Multimedia applications |link:{freebsd-new-bus-url}[freebsd-new-bus] |Technical discussions about bus architecture |link:{freebsd-net-url}[freebsd-net] |Networking discussion and TCP/IP source code |link:{freebsd-numerics-url}[freebsd-numerics] |Discussions of high quality implementation of libm functions |link:{freebsd-ocaml-url}[freebsd-ocaml] |FreeBSD-specific OCaml discussions |link:{freebsd-office-url}[freebsd-office] |Office applications on FreeBSD |link:{freebsd-performance-url}[freebsd-performance] |Performance tuning questions for high performance/load installations |link:{freebsd-perl-url}[freebsd-perl] |Maintenance of a number of Perl-related ports |link:{freebsd-pf-url}[freebsd-pf] |Discussion and questions about the packet filter firewall system |link:{freebsd-pkg-url}[freebsd-pkg] |Binary package management and package tools discussion |link:{freebsd-pkg-fallout-url}[freebsd-pkg-fallout] |Fallout logs from package building |link:{freebsd-pkgbase-url}[freebsd-pkgbase] |Packaging the FreeBSD base system |link:{freebsd-platforms-url}[freebsd-platforms] |Concerning ports to non Intel(R) architecture platforms |link:{freebsd-ports-url}[freebsd-ports] |Discussion of the Ports Collection |link:{freebsd-ports-announce-url}[freebsd-ports-announce] |Important news and instructions about the Ports Collection (moderated) |link:{freebsd-ports-bugs-url}[freebsd-ports-bugs] |Discussion of the ports bugs/PRs |link:{freebsd-ppc-url}[freebsd-ppc] |Porting FreeBSD to the PowerPC(R) |link:{freebsd-proliant-url}[freebsd-proliant] |Technical discussion of FreeBSD on HP ProLiant server platforms |link:{freebsd-python-url}[freebsd-python] |FreeBSD-specific Python issues |link:{freebsd-rc-url}[freebsd-rc] |Discussion related to the [.filename]#rc.d# system and its development |link:{freebsd-realtime-url}[freebsd-realtime] |Development of realtime extensions to FreeBSD |link:{freebsd-risc-url}[freebsd-risc] |Porting FreeBSD to RISC-V(R) systems |link:{freebsd-ruby-url}[freebsd-ruby] |FreeBSD-specific Ruby discussions |link:{freebsd-scsi-url}[freebsd-scsi] |The SCSI subsystem |link:{freebsd-security-url}[freebsd-security] |Security issues affecting FreeBSD |link:{freebsd-snapshots-url}[freebsd-snapshots] |FreeBSD Development Snapshot Announcements |link:{freebsd-sparc64-url}[freebsd-sparc64] |Porting FreeBSD to SPARC(R) based systems |link:{freebsd-standards-url}[freebsd-standards] |FreeBSD's conformance to the C99 and the POSIX(R) standards |link:{freebsd-sysinstall-url}[freebsd-sysinstall] |man:sysinstall[8] development |link:{freebsd-tcltk-url}[freebsd-tcltk] |FreeBSD-specific Tcl/Tk discussions |link:{freebsd-testing-url}[freebsd-testing] |Testing on FreeBSD |link:{freebsd-tex-url}[freebsd-tex] |Porting TeX and its applications to FreeBSD |link:{freebsd-threads-url}[freebsd-threads] |Threading in FreeBSD |link:{freebsd-tokenring-url}[freebsd-tokenring] |Support Token Ring in FreeBSD |link:{freebsd-toolchain-url}[freebsd-toolchain] |Maintenance of FreeBSD's integrated toolchain |link:{freebsd-translators-url}[freebsd-translators] |Translating FreeBSD documents and programs |link:{freebsd-transport-url}[freebsd-transport] |Discussions of transport level network protocols in FreeBSD |link:{freebsd-usb-url}[freebsd-usb] |Discussing FreeBSD support for USB |link:{freebsd-virtualization-url}[freebsd-virtualization] |Discussion of various virtualization techniques supported by FreeBSD |link:{freebsd-vuxml-url}[freebsd-vuxml] |Discussion on VuXML infrastructure |link:{freebsd-x11-url}[freebsd-x11] |Maintenance and support of X11 on FreeBSD |link:{freebsd-xen-url}[freebsd-xen] |Discussion of the FreeBSD port to Xen(TM) - implementation and usage |link:{freebsd-xfce-url}[freebsd-xfce] |XFCE for FreeBSD - porting and maintaining |link:{freebsd-zope-url}[freebsd-zope] |Zope for FreeBSD - porting and maintaining |=== _Limited lists:_ The following lists are for more specialized (and demanding) audiences and are probably not of interest to the general public. It is also a good idea to establish a presence in the technical lists before joining one of these limited lists in order to understand the communications etiquette involved. [.informaltable] [cols="20%,80%", frame="none", options="header"] |=== | List | Purpose |link:{freebsd-hubs-url}[freebsd-hubs] |People running mirror sites (infrastructural support) |link:{freebsd-user-groups-url}[freebsd-user-groups] |User group coordination |link:{freebsd-wip-status-url}[freebsd-wip-status] |FreeBSD Work-In-Progress Status |link:{freebsd-wireless-url}[freebsd-wireless] |Discussions of 802.11 stack, tools, device driver development |=== _Digest lists:_ All of the above lists are available in a digest format. Once subscribed to a list, the digest options can be changed in the account options section. _Commit message lists:_ The following lists are for people interested in seeing the log messages for changes to various areas of the source tree. [.informaltable] [cols="1,1,1", frame="none", options="header"] |=== | List | Source area | Area Description (source for) |{dev-commits-doc-all-url}[dev-commits-doc-all] |[.filename]#/usr/doc# |All changes to the doc repository |{dev-commits-ports-all-url}[dev-commits-ports-all] |[.filename]#/usr/ports# |All changes to the ports repository |{dev-commits-ports-main-url}[dev-commits-ports-main] |[.filename]#/usr/ports# |All changes to the "main" branch of the ports repository |{dev-commits-ports-branches-url}[dev-commits-ports-branches] |[.filename]#/usr/ports# |All changes to the quarterly branches of the ports repository |{dev-commits-src-all-url}[dev-commits-src-all] |[.filename]#/usr/src# |All changes to the src repository |{dev-commits-src-main-url}[dev-commits-src-main] |[.filename]#/usr/src# |All changes to the "main" branch of the src repository (the FreeBSD-CURRENT branch) |{dev-commits-src-branches-url}[dev-commits-src-branches] |[.filename]#/usr/src# |All changes to all stable branches of the src repository |=== _SVN lists:_ The following lists are for people interested in seeing the SVN log messages for changes to various areas of the source tree. [NOTE] ==== Only SVN log messages are sent to SVN lists. After the SVN to Git Migration, the following lists no longer receive new commit messages and are unavailable for subscribing. The lists' addresses are pointing to their respective archives. ==== [.informaltable] [cols="20%,20%,60%", frame="none", options="header"] |=== | List | Source area | Area Description (source for) |link:{svn-doc-all-url}[svn-doc-all] |[.filename]#/usr/doc# |All changes to the doc Subversion repository (except for [.filename]#user#, [.filename]#projects# and [.filename]#translations#) |link:{svn-doc-head-url}[svn-doc-head] |[.filename]#/usr/doc# |All changes to the "head" branch of the doc Subversion repository |link:{svn-doc-projects-url}[svn-doc-projects] |[.filename]#/usr/doc/projects# |All changes to the [.filename]#projects# area of the doc Subversion repository |link:{svn-doc-svnadmin-url}[svn-doc-svnadmin] |[.filename]#/usr/doc# |All changes to the administrative scripts, hooks, and other configuration data of the doc Subversion repository |link:{svn-ports-all-url}[svn-ports-all] |[.filename]#/usr/ports# |All changes to the ports Subversion repository |link:{svn-ports-head-url}[svn-ports-head] |[.filename]#/usr/ports# |All changes to the "head" branch of the ports Subversion repository |link:{svn-ports-svnadmin-url}[svn-ports-svnadmin] |[.filename]#/usr/ports# |All changes to the administrative scripts, hooks, and other configuration data of the ports Subversion repository |link:{svn-src-all-url}[svn-src-all] |[.filename]#/usr/src# |All changes to the src Subversion repository (except for [.filename]#user# and [.filename]#projects#) |link:{svn-src-head-url}[svn-src-head] |[.filename]#/usr/src# |All changes to the "head" branch of the src Subversion repository (the FreeBSD-CURRENT branch) |link:{svn-src-projects-url}[svn-src-projects] |[.filename]#/usr/projects# |All changes to the [.filename]#projects# area of the src Subversion repository |link:{svn-src-release-url}[svn-src-release] |[.filename]#/usr/src# |All changes to the [.filename]#releases# area of the src Subversion repository |link:{svn-src-releng-url}[svn-src-releng] |[.filename]#/usr/src# |All changes to the [.filename]#releng# branches of the src Subversion repository (the security / release engineering branches) |link:{svn-src-stable-url}[svn-src-stable] |[.filename]#/usr/src# |All changes to the all stable branches of the src Subversion repository |link:{svn-src-stable-6-url}[svn-src-stable-6] |[.filename]#/usr/src# |All changes to the [.filename]#stable/6# branch of the src Subversion repository |link:{svn-src-stable-7-url}[svn-src-stable-7] |[.filename]#/usr/src# |All changes to the [.filename]#stable/7# branch of the src Subversion repository |link:{svn-src-stable-8-url}[svn-src-stable-8] |[.filename]#/usr/src# |All changes to the [.filename]#stable/8# branch of the src Subversion repository |link:{svn-src-stable-9-url}[svn-src-stable-9] |[.filename]#/usr/src# |All changes to the [.filename]#stable/9# branch of the src Subversion repository |link:{svn-src-stable-10-url}[svn-src-stable-10] |[.filename]#/usr/src# |All changes to the [.filename]#stable/10# branch of the src Subversion repository |link:{svn-src-stable-11-url}[svn-src-stable-11] |[.filename]#/usr/src# |All changes to the [.filename]#stable/11# branch of the src Subversion repository |link:{svn-src-stable-12-url}[svn-src-stable-12] |[.filename]#/usr/src# |All changes to the [.filename]#stable/12# branch of the src Subversion repository |link:{svn-src-stable-other-url}[svn-src-stable-other] |[.filename]#/usr/src# |All changes to the older [.filename]#stable# branches of the src Subversion repository |link:{svn-src-svnadmin-url}[svn-src-svnadmin] |[.filename]#/usr/src# |All changes to the administrative scripts, hooks, and other configuration data of the src Subversion repository |link:{svn-src-user-url}[svn-src-user] |[.filename]#/usr/src# |All changes to the experimental [.filename]#user# area of the src Subversion repository |link:{svn-src-vendor-url}[svn-src-vendor] |[.filename]#/usr/src# |All changes to the vendor work area of the src Subversion repository |=== [[eresources-subscribe]] === How to Subscribe To subscribe to a list, click the list name at {mailing-lists-url}. The page that is displayed should contain all of the necessary subscription instructions for that list. To actually post to a given list, send mail to mailto:listname@FreeBSD.org[listname@FreeBSD.org]. It will then be redistributed to mailing list members world-wide. To unsubscribe from a list, click on the URL found at the bottom of every email received from the list. It is also possible to send an email to mailto:listname+unsubscribe@FreeBSD.org[listname+unsubscribe@FreeBSD.org] to unsubscribe. It is important to keep discussion in the technical mailing lists on a technical track. To only receive important announcements, instead join the {freebsd-announce}, which is intended for infrequent traffic. [[eresources-charters]] === List Charters _All_ FreeBSD mailing lists have certain basic rules which must be adhered to by anyone using them. Failure to comply with these guidelines will result in two (2) written warnings from the FreeBSD Postmaster mailto:postmaster@FreeBSD.org[postmaster@FreeBSD.org], after which, on a third offense, the poster will removed from all FreeBSD mailing lists and filtered from further posting to them. We regret that such rules and measures are necessary at all, but today's Internet is a pretty harsh environment, it would seem, and many fail to appreciate just how fragile some of its mechanisms are. Rules of the road: * The topic of any posting should adhere to the basic charter of the list it is posted to. If the list is about technical issues, the posting should contain technical discussion. Ongoing irrelevant chatter or flaming only detracts from the value of the mailing list for everyone on it and will not be tolerated. For free-form discussion on no particular topic, the {freebsd-chat} is freely available and should be used instead. * No posting should be made to more than 2 mailing lists, and only to 2 when a clear and obvious need to post to both lists exists. For most lists, there is already a great deal of subscriber overlap and except for the most esoteric mixes (say "-stable & -scsi"), there really is no reason to post to more than one list at a time. If a message is received with multiple mailing lists on the `Cc` line, trim the `Cc` line before replying. _The person who replies is still responsible for cross-posting, no matter who the originator might have been._ * Personal attacks and profanity (in the context of an argument) are not allowed, and that includes users and developers alike. Gross breaches of netiquette, like excerpting or reposting private mail when permission to do so was not and would not be forthcoming, are frowned upon but not specifically enforced. _However_, there are also very few cases where such content would fit within the charter of a list and it would therefore probably rate a warning (or ban) on that basis alone. * Advertising of non-FreeBSD related products or services is strictly prohibited and will result in an immediate ban if it is clear that the offender is advertising by spam. _Individual list charters:_ link:{freebsd-acpi-url}[freebsd-acpi]:: _ACPI and power management development_ link:{freebsd-announce-url}[freebsd-announce]:: _Important events / milestones_ + This is the mailing list for people interested only in occasional announcements of significant FreeBSD events. This includes announcements about snapshots and other releases. It contains announcements of new FreeBSD capabilities. It may contain calls for volunteers etc. This is a low volume, strictly moderated mailing list. link:{freebsd-arch-url}[freebsd-arch]:: _Architecture and design discussions_ + This list is for discussion of the FreeBSD architecture. Messages will mostly be kept strictly technical in nature. Examples of suitable topics are: ** How to re-vamp the build system to have several customized builds running at the same time. ** What needs to be fixed with VFS to make Heidemann layers work. ** How do we change the device driver interface to be able to use the same drivers cleanly on many buses and architectures. ** How to write a network driver. link:{freebsd-bluetooth-url}[freebsd-bluetooth]:: _Bluetooth(R) in FreeBSD_ + This is the forum where FreeBSD's Bluetooth(R) users congregate. Design issues, implementation details, patches, bug reports, status reports, feature requests, and all matters related to Bluetooth(R) are fair game. link:{freebsd-bugbusters-url}[freebsd-bugbusters]:: _Coordination of the Problem Report handling effort_ + The purpose of this list is to serve as a coordination and discussion forum for the Bugmeister, his Bugbusters, and any other parties who have a genuine interest in the PR database. This list is not for discussions about specific bugs, patches or PRs. link:{freebsd-bugs-url}[freebsd-bugs]:: _Bug reports_ + This is the mailing list for reporting bugs in FreeBSD. Whenever possible, bugs should be submitted using the link:https://bugs.freebsd.org/bugzilla/enter_bug.cgi[web interface]. link:{freebsd-chat-url}[freebsd-chat]:: _Non technical items related to the FreeBSD community_ + This list contains the overflow from the other lists about non-technical, social information. It includes discussion about whether Jordan looks like a toon ferret or not, whether or not to type in capitals, who is drinking too much coffee, where the best beer is brewed, who is brewing beer in their basement, and so on. Occasional announcements of important events (such as upcoming parties, weddings, births, new jobs, etc) can be made to the technical lists, but the follow ups should be directed to this -chat list. link:{freebsd-chromium-url}[freebsd-chromium]:: _FreeBSD-specific Chromium issues_ + This is a list for the discussion of Chromium support for FreeBSD. This is a technical list to discuss development and installation of Chromium. link:{freebsd-cloud-url}[freebsd-cloud]:: _Running FreeBSD on various cloud platforms_ + This list discusses running FreeBSD on Amazon EC2, Google Compute Engine, Microsoft Azure, and other cloud computing platforms. _FreeBSD core team_:: This is an internal mailing list for use by the core members. Messages can be sent to it when a serious FreeBSD-related matter requires arbitration or high-level scrutiny. link:{freebsd-current-url}[freebsd-current]:: _Discussions about the use of FreeBSD-CURRENT_ + This is the mailing list for users of FreeBSD-CURRENT. It includes warnings about new features coming out in -CURRENT that will affect the users, and instructions on steps that must be taken to remain -CURRENT. Anyone running "CURRENT" must subscribe to this list. This is a technical mailing list for which strictly technical content is expected. link:{freebsd-desktop-url}[freebsd-desktop]:: _Using and improving FreeBSD on the desktop_ + This is a forum for discussion of FreeBSD on the desktop. It is primarily a place for desktop porters and users to discuss issues and improve FreeBSD's desktop support. link:{dev-ci-url}[dev-ci]:: _Continuous Integration reports of build and test results_ + All Continuous Integration reports of build and test results link:{dev-reviews-url}[dev-reviews]:: _Notifications of work in progress in FreeBSD's review tool_ + Automated notifications of work in progress for review in FreeBSD's review tools, including patches. link:{freebsd-doc-url}[freebsd-doc]:: _Documentation Project_ + This mailing list is for the discussion of issues and projects related to the creation of documentation for FreeBSD. The members of this mailing list are collectively referred to as "The FreeBSD Documentation Project". It is an open list; feel free to join and contribute! link:{freebsd-drivers-url}[freebsd-drivers]:: _Writing device drivers for FreeBSD_ + This is a forum for technical discussions related to device drivers on FreeBSD. It is primarily a place for device driver writers to ask questions about how to write device drivers using the APIs in the FreeBSD kernel. link:{freebsd-dtrace-url}[freebsd-dtrace]:: _Using and working on DTrace in FreeBSD_ + DTrace is an integrated component of FreeBSD that provides a framework for understanding the kernel as well as user space programs at run time. The mailing list is an archived discussion for developers of the code as well as those using it. link:{freebsd-eclipse-url}[freebsd-eclipse]:: _FreeBSD users of Eclipse IDE, tools, rich client applications and ports._ + The intention of this list is to provide mutual support for everything to do with choosing, installing, using, developing and maintaining the Eclipse IDE, tools, rich client applications on the FreeBSD platform and assisting with the porting of Eclipse IDE and plugins to the FreeBSD environment. + The intention is also to facilitate exchange of information between the Eclipse community and the FreeBSD community to the mutual benefit of both. + Although this list is focused primarily on the needs of Eclipse users it will also provide a forum for those who would like to develop FreeBSD specific applications using the Eclipse framework. link:{freebsd-embedded-url}[freebsd-embedded]:: _Using FreeBSD in embedded applications_ + This list discusses topics related to using FreeBSD in embedded systems. This is a technical mailing list for which strictly technical content is expected. For the purpose of this list, embedded systems are those computing devices which are not desktops and which usually serve a single purpose as opposed to being general computing environments. Examples include, but are not limited to, all kinds of phone handsets, network equipment such as routers, switches and PBXs, remote measuring equipment, PDAs, Point Of Sale systems, and so on. link:{freebsd-emulation-url}[freebsd-emulation]:: _Emulation of other systems such as Linux/MS-DOS(R)/Windows(R)_ + This is a forum for technical discussions related to running programs written for other operating systems on FreeBSD. link:{freebsd-enlightenment-url}[freebsd-enlightenment]:: _Enlightenment_ + Discussions concerning the Enlightenment Desktop Environment for FreeBSD systems. This is a technical mailing list for which strictly technical content is expected. link:{freebsd-firewire-url}[freebsd-firewire]:: _FireWire(R) (iLink, IEEE 1394)_ + This is a mailing list for discussion of the design and implementation of a FireWire(R) (aka IEEE 1394 aka iLink) subsystem for FreeBSD. Relevant topics specifically include the standards, bus devices and their protocols, adapter boards/cards/chips sets, and the architecture and implementation of code for their proper support. link:{freebsd-fortran-url}[freebsd-fortran]:: _Fortran on FreeBSD_ + This is the mailing list for discussion of Fortran related ports on FreeBSD: compilers, libraries, scientific and engineering applications from laptops to HPC clusters. link:{freebsd-fs-url}[freebsd-fs]:: _File systems_ + Discussions concerning FreeBSD filesystems. This is a technical mailing list for which strictly technical content is expected. link:{freebsd-games-url}[freebsd-games]:: _Games on FreeBSD_ + This is a technical list for discussions related to bringing games to FreeBSD. It is for individuals actively working on porting games to FreeBSD, to bring up problems or discuss alternative solutions. Individuals interested in following the technical discussion are also welcome. link:{freebsd-gecko-url}[freebsd-gecko]:: _Gecko Rendering Engine_ + This is a forum about Gecko applications using FreeBSD. + Discussion centers around Gecko Ports applications, their installation, their development and their support within FreeBSD. link:{freebsd-geom-url}[freebsd-geom]:: _GEOM_ + Discussions specific to GEOM and related implementations. This is a technical mailing list for which strictly technical content is expected. link:{freebsd-git-url}[freebsd-git]:: _Use of git in the FreeBSD project_ + Discussions of how to use git in FreeBSD infrastructure including the github mirror and other uses of git for project collaboration. Discussion area for people using git against the FreeBSD github mirror. People wanting to get started with the mirror or git in general on FreeBSD can ask here. link:{freebsd-gnome-url}[freebsd-gnome]:: _GNOME_ + Discussions concerning The GNOME Desktop Environment for FreeBSD systems. This is a technical mailing list for which strictly technical content is expected. link:{freebsd-infiniband-url}[freebsd-infiniband]:: _Infiniband on FreeBSD_ + Technical mailing list discussing Infiniband, OFED, and OpenSM on FreeBSD. link:{freebsd-ipfw-url}[freebsd-ipfw]:: _IP Firewall_ + This is the forum for technical discussions concerning the redesign of the IP firewall code in FreeBSD. This is a technical mailing list for which strictly technical content is expected. link:{freebsd-isdn-url}[freebsd-isdn]:: _ISDN Communications_ + This is the mailing list for people discussing the development of ISDN support for FreeBSD. link:{freebsd-java-url}[freebsd-java]:: _Java(TM) Development_ + This is the mailing list for people discussing the development of significant Java(TM) applications for FreeBSD and the porting and maintenance of JDK(TM)s. [[eresources-charters-jobs]] link:{freebsd-jobs-url}[freebsd-jobs]:: _Jobs offered and sought_ + This is a forum for posting employment notices specifically related to FreeBSD and resumes from those seeking FreeBSD-related employment. This is _not_ a mailing list for general employment issues since adequate forums for that already exist elsewhere. + Note that this list, like other `FreeBSD.org` mailing lists, is distributed worldwide. Be clear about the geographic location and the extent to which telecommuting or assistance with relocation is available. + Email should use open formats only - preferably plain text, but basic Portable Document Format (PDF), HTML, and a few others are acceptable to many readers. Closed formats such as Microsoft(R) Word ([.filename]#.doc#) will be rejected by the mailing list server. link:{freebsd-kde-url}[freebsd-kde]:: _KDE_ + Discussions concerning KDE on FreeBSD systems. This is a technical mailing list for which strictly technical content is expected. link:{freebsd-hackers-url}[freebsd-hackers]:: _Technical discussions_ + This is a forum for technical discussions related to FreeBSD. This is the primary technical mailing list. It is for individuals actively working on FreeBSD, to bring up problems or discuss alternative solutions. Individuals interested in following the technical discussion are also welcome. This is a technical mailing list for which strictly technical content is expected. link:{freebsd-hardware-url}[freebsd-hardware]:: _General discussion of FreeBSD hardware_ + General discussion about the types of hardware that FreeBSD runs on, various problems and suggestions concerning what to buy or avoid. link:{freebsd-hubs-url}[freebsd-hubs]:: _Mirror sites_ + Announcements and discussion for people who run FreeBSD mirror sites. link:{freebsd-isp-url}[freebsd-isp]:: _Issues for Internet Service Providers_ + This mailing list is for discussing topics relevant to Internet Service Providers (ISPs) using FreeBSD. This is a technical mailing list for which strictly technical content is expected. link:{freebsd-mono-url}[freebsd-mono]:: _Mono and C# applications on FreeBSD_ + This is a list for discussions related to the Mono development framework on FreeBSD. This is a technical mailing list. It is for individuals actively working on porting Mono or C# applications to FreeBSD, to bring up problems or discuss alternative solutions. Individuals interested in following the technical discussion are also welcome. link:{freebsd-ocaml-url}[freebsd-ocaml]:: _FreeBSD-specific OCaml discussions_ + This is a list for discussions related to the OCaml support on FreeBSD. This is a technical mailing list. It is for individuals working on OCaml ports, 3rd party libraries and frameworks. Individuals interested in the technical discussion are also welcome. link:{freebsd-office-url}[freebsd-office]:: _Office applications on FreeBSD_ + Discussion centers around office applications, their installation, their development and their support within FreeBSD. link:{freebsd-ops-announce-url}[freebsd-ops-announce]:: _Project Infrastructure Announcements_ + This is the mailing list for people interested in changes and issues related to the FreeBSD.org Project infrastructure. + This moderated list is strictly for announcements: no replies, requests, discussions, or opinions. link:{freebsd-performance-url}[freebsd-performance]:: _Discussions about tuning or speeding up FreeBSD_ + This mailing list exists to provide a place for hackers, administrators, and/or concerned parties to discuss performance related topics pertaining to FreeBSD. Acceptable topics includes talking about FreeBSD installations that are either under high load, are experiencing performance problems, or are pushing the limits of FreeBSD. Concerned parties that are willing to work toward improving the performance of FreeBSD are highly encouraged to subscribe to this list. This is a highly technical list ideally suited for experienced FreeBSD users, hackers, or administrators interested in keeping FreeBSD fast, robust, and scalable. This list is not a question-and-answer list that replaces reading through documentation, but it is a place to make contributions or inquire about unanswered performance related topics. link:{freebsd-pf-url}[freebsd-pf]:: _Discussion and questions about the packet filter firewall system_ + Discussion concerning the packet filter (pf) firewall system in terms of FreeBSD. Technical discussion and user questions are both welcome. This list is also a place to discuss the ALTQ QoS framework. link:{freebsd-pkg-url}[freebsd-pkg]:: _Binary package management and package tools discussion_ + Discussion of all aspects of managing FreeBSD systems by using binary packages to install software, including binary package toolkits and formats, their development and support within FreeBSD, package repository management, and third party packages. + Note that discussion of ports which fail to generate packages correctly should generally be considered as ports problems, and so inappropriate for this list. link:{freebsd-pkg-fallout-url}[freebsd-pkg-fallout]:: _Fallout logs from package building_ + All packages building failures logs from the package building clusters link:{freebsd-pkgbase-url}[freebsd-pkgbase]:: _Packaging the FreeBSD base system._ + Discussions surrounding implementation and issues regarding packaging the FreeBSD base system. link:{freebsd-platforms-url}[freebsd-platforms]:: _Porting to Non Intel(R) platforms_ + Cross-platform FreeBSD issues, general discussion and proposals for non Intel(R) FreeBSD ports. This is a technical mailing list for which strictly technical content is expected. link:{freebsd-ports-url}[freebsd-ports]:: _Discussion of "ports"_ + Discussions concerning FreeBSD's "ports collection" ([.filename]#/usr/ports#), ports infrastructure, and general ports coordination efforts. This is a technical mailing list for which strictly technical content is expected. link:{freebsd-ports-announce-url}[freebsd-ports-announce]:: _Important news and instructions about the FreeBSD "Ports Collection"_ + Important news for developers, porters, and users of the "Ports Collection" ([.filename]#/usr/ports#), including architecture/infrastructure changes, new capabilities, critical upgrade instructions, and release engineering information. This is a low-volume mailing list, intended for announcements. link:{freebsd-ports-bugs-url}[freebsd-ports-bugs]:: _Discussion of "ports" bugs_ + Discussions concerning problem reports for FreeBSD's "ports collection" ([.filename]#/usr/ports#), proposed ports, or modifications to ports. This is a technical mailing list for which strictly technical content is expected. link:{freebsd-proliant-url}[freebsd-proliant]:: _Technical discussion of FreeBSD on HP ProLiant server platforms_ + This mailing list is to be used for the technical discussion of the usage of FreeBSD on HP ProLiant servers, including the discussion of ProLiant-specific drivers, management software, configuration tools, and BIOS updates. As such, this is the primary place to discuss the hpasmd, hpasmcli, and hpacucli modules. link:{freebsd-python-url}[freebsd-python]:: _Python on FreeBSD_ + This is a list for discussions related to improving Python-support on FreeBSD. This is a technical mailing list. It is for individuals working on porting Python, its third party modules and Zope stuff to FreeBSD. Individuals interested in following the technical discussion are also welcome. link:{freebsd-questions-url}[freebsd-questions]:: _User questions_ + This is the mailing list for questions about FreeBSD. Do not send "how to" questions to the technical lists unless the question is quite technical. link:{freebsd-ruby-url}[freebsd-ruby]:: _FreeBSD-specific Ruby discussions_ + This is a list for discussions related to the Ruby support on FreeBSD. This is a technical mailing list. It is for individuals working on Ruby ports, third party libraries and frameworks. + Individuals interested in the technical discussion are also welcome. link:{freebsd-scsi-url}[freebsd-scsi]:: _SCSI subsystem_ + This is the mailing list for people working on the SCSI subsystem for FreeBSD. This is a technical mailing list for which strictly technical content is expected. link:{freebsd-security-url}[freebsd-security]:: _Security issues_ + FreeBSD computer security issues (DES, Kerberos, known security holes and fixes, etc). This is a technical mailing list for which strictly technical discussion is expected. Note that this is not a question-and-answer list, but that contributions (BOTH question AND answer) to the FAQ are welcome. link:{freebsd-security-notifications-url}[freebsd-security-notifications]:: _Security Notifications_ + Notifications of FreeBSD security problems and fixes. This is not a discussion list. The discussion list is FreeBSD-security. link:{freebsd-snapshots-url}[freebsd-snapshots]:: _FreeBSD Development Snapshot Announcements_ + This list provides notifications about the availability of new FreeBSD development snapshots for the head/ and stable/ branches. link:{freebsd-stable-url}[freebsd-stable]:: _Discussions about the use of FreeBSD-STABLE_ + This is the mailing list for users of FreeBSD-STABLE. "STABLE" is the branch where development continues after a RELEASE, including bug fixes and new features. The ABI is kept stable for binary compatibility. It includes warnings about new features coming out in -STABLE that will affect the users, and instructions on steps that must be taken to remain -STABLE. Anyone running "STABLE" should subscribe to this list. This is a technical mailing list for which strictly technical content is expected. link:{freebsd-standards-url}[freebsd-standards]:: _C99 POSIX Conformance_ + This is a forum for technical discussions related to FreeBSD Conformance to the C99 and the POSIX standards. link:{freebsd-teaching-url}[freebsd-teaching]:: _Teaching with FreeBSD_ + Non technical mailing list discussing teaching with FreeBSD. link:{freebsd-testing-url}[freebsd-testing]:: _Testing on FreeBSD_ + Technical mailing list discussing testing on FreeBSD, including ATF/Kyua, test build infrastructure, port tests to FreeBSD from other operating systems (NetBSD, ...), etc. link:{freebsd-tex-url}[freebsd-tex]:: _Porting TeX and its applications to FreeBSD_ + This is a technical mailing list for discussions related to TeX and its applications on FreeBSD. It is for individuals actively working on porting TeX to FreeBSD, to bring up problems or discuss alternative solutions. Individuals interested in following the technical discussion are also welcome. link:{freebsd-toolchain-url}[freebsd-toolchain]:: _Maintenance of FreeBSD's integrated toolchain_ + This is the mailing list for discussions related to the maintenance of the toolchain shipped with FreeBSD. This could include the state of Clang and GCC, but also pieces of software such as assemblers, linkers and debuggers. link:{freebsd-transport-url}[freebsd-transport]:: _Discussions of transport level network protocols in FreeBSD_ + The transport mailing list exists for the discussion of issues and designs around the transport level protocols in the FreeBSD network stack, including TCP, SCTP and UDP. Other networking topics, including driver specific and network protocol issues should be discussed on the {freebsd-net}. link:{freebsd-translators-url}[freebsd-translators]:: _Translating FreeBSD documents and programs_ + A discussion list where translators of FreeBSD documents from English into other languages can talk about translation methods and tools. New members are asked to introduce themselves and mention the languages they are interested in translating. link:{freebsd-usb-url}[freebsd-usb]:: _Discussing FreeBSD support for USB_ + This is a mailing list for technical discussions related to FreeBSD support for USB. link:{freebsd-user-groups-url}[freebsd-user-groups]:: _User Group Coordination List_ + This is the mailing list for the coordinators from each of the local area Users Groups to discuss matters with each other and a designated individual from the Core Team. This mail list should be limited to meeting synopsis and coordination of projects that span User Groups. link:{freebsd-virtualization-url}[freebsd-virtualization]:: _Discussion of various virtualization techniques supported by FreeBSD_ + A list to discuss the various virtualization techniques supported by FreeBSD. On one hand the focus will be on the implementation of the basic functionality as well as adding new features. On the other hand users will have a forum to ask for help in case of problems or to discuss their use cases. link:{freebsd-wip-status-url}[freebsd-wip-status]:: _FreeBSD Work-In-Progress Status_ + This mailing list can be used by developers to announce the creation and progress of FreeBSD related work. Messages will be moderated. It is suggested to send the message "To:" a more topical FreeBSD list and only "BCC:" this list. This way the WIP can also be discussed on the topical list, as no discussion is allowed on this list. link:{freebsd-wireless-url}[freebsd-wireless]:: _Discussions of 802.11 stack, tools device driver development_ + The FreeBSD-wireless list focuses on 802.11 stack (sys/net80211), device driver and tools development. This includes bugs, new features and maintenance. link:{freebsd-xen-url}[freebsd-xen]:: _Discussion of the FreeBSD port to Xen(TM) - implementation and usage_ + A list that focuses on the FreeBSD Xen(TM) port. The anticipated traffic level is small enough that it is intended as a forum for both technical discussions of the implementation and design details as well as administrative deployment issues. link:{freebsd-xfce-url}[freebsd-xfce]:: _XFCE_ + This is a forum for discussions related to bring the XFCE environment to FreeBSD. This is a technical mailing list. It is for individuals actively working on porting XFCE to FreeBSD, to bring up problems or discuss alternative solutions. Individuals interested in following the technical discussion are also welcome. link:{freebsd-zope-url}[freebsd-zope]:: _Zope_ + This is a forum for discussions related to bring the Zope environment to FreeBSD. This is a technical mailing list. It is for individuals actively working on porting Zope to FreeBSD, to bring up problems or discuss alternative solutions. Individuals interested in following the technical discussion are also welcome. [[eresources-mailfiltering]] === Filtering on the Mailing Lists The FreeBSD mailing lists are filtered in multiple ways to avoid the distribution of spam, viruses, and other unwanted emails. The filtering actions described in this section do not include all those used to protect the mailing lists. Only certain types of attachments are allowed on the mailing lists. All attachments with a MIME content type not found in the list below will be stripped before an email is distributed on the mailing lists. * application/octet-stream * application/pdf * application/pgp-signature * application/x-pkcs7-signature * message/rfc822 * multipart/alternative * multipart/related * multipart/signed * text/html * text/plain * text/x-diff * text/x-patch [NOTE] ==== Some of the mailing lists might allow attachments of other MIME content types, but the above list should be applicable for most of the mailing lists. ==== If an email contains both an HTML and a plain text version, the HTML version will be removed. If an email contains only an HTML version, it will be converted to plain text. [[eresources-news]] == Usenet Newsgroups In addition to two FreeBSD specific newsgroups, there are many others in which FreeBSD is discussed or are otherwise relevant to FreeBSD users. === BSD Specific Newsgroups * link:news:comp.unix.bsd.freebsd.announce[comp.unix.bsd.freebsd.announce] * link:news:comp.unix.bsd.freebsd.misc[comp.unix.bsd.freebsd.misc] * link:news:de.comp.os.unix.bsd[de.comp.os.unix.bsd] (German) * link:news:fr.comp.os.bsd[fr.comp.os.bsd] (French) === Other UNIX(R) Newsgroups of Interest * link:news:comp.unix[comp.unix] * link:news:comp.unix.questions[comp.unix.questions] * link:news:comp.unix.admin[comp.unix.admin] * link:news:comp.unix.programmer[comp.unix.programmer] * link:news:comp.unix.shell[comp.unix.shell] * link:news:comp.unix.misc[comp.unix.misc] * link:news:comp.unix.bsd[comp.unix.bsd] === X Window System * link:news:comp.windows.x[comp.windows.x] - -[[eresources-web]] -== Website Mirrors - -Below is the list of official mirrors of the main FreeBSD website. -For the list of mirrors of FreeBSD releases, binaries, and other files shipped by the project, see link:./mirrors#mirrors-ftp[Mirrors]. - -<>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>. - -[[central-mirrors]] -*{central}* - -* {central-www} - -[[armenia-mirrors]] -*{mirrors-armenia}* - -* {mirrors-armenia-www-httpv6} (IPv6) - -[[australia-mirrors]] -*{mirrors-australia}* - -* {mirrors-australia-www-http} -* {mirrors-australia-www2-http} - -[[austria-mirrors]] -*{mirrors-austria}* - -* {mirrors-armenia-www-httpv6} (IPv6) - -[[czech-republic-mirrors]] -*{mirrors-czech}* - -* {mirrors-czech-www-httpv6} (IPv6) - -[[denmark-mirrors]] -*{mirrors-denmark}* - -* {mirrors-denmark-www-httpv6} (IPv6) - -[[finland-mirrors]] -*{mirrors-finland}* - -* {mirrors-finland-www-http} - -[[france-mirrors]] -*{mirrors-france}* - -* {mirrors-france-www-http} - -[[germany-mirrors]] -*{mirrors-germany}* - -* {mirrors-germany-www-http} - -[[hong-kong-mirrors]] -*{mirrors-hongkong}* - -* {mirrors-hongkong-www} - -[[ireland-mirrors]] -*{mirrors-ireland}* - -* {mirrors-ireland-www} - -[[japan-mirrors]] -*{mirrors-japan}* - -* {mirrors-japan-www-httpv6} (IPv6) - -[[latvia-mirrors]] -*{mirrors-latvia}* - -* {mirrors-latvia-www} - -[[lithuania-mirrors]] -*{mirrors-lithuania}* - -* {mirrors-lithuania-www} - -[[netherlands-mirrors]] -*{mirrors-netherlands}* - -* {mirrors-netherlands-www} - -[[norway-mirrors]] -*{mirrors-norway}* - -* {mirrors-norway-www} - -[[russia-mirrors]] -*{mirrors-russia}* - -* {mirrors-russia-www-httpv6} (IPv6) - -[[slovenia-mirrors]] -*{mirrors-slovenia}* - -* {mirrors-slovenia-www} - -[[south-africa-mirrors]] -*{mirrors-south-africa}* - -* {mirrors-south-africa-www} - -[[spain-mirrors]] -*{mirrors-spain}* - -* {mirrors-spain-www} -* {mirrors-spain-www2} - -[[sweden-mirrors]] -*{mirrors-sweden}* - -* {mirrors-sweden-www} - -[[switzerland-mirrors]] -*{mirrors-switzerland}* - -* {mirrors-switzerland-www-httpv6} (IPv6) -* {mirrors-switzerland-www2-httpv6} (IPv6) - -[[taiwan-mirrors]] -*{mirrors-taiwan}* - -* {mirrors-taiwan-www} -* {mirrors-taiwan-www2} -* {mirrors-taiwan-www4} -* {mirrors-taiwan-www5-httpv6} (IPv6) - -[[uk-mirrors]] -*{mirrors-uk}* - -* {mirrors-uk-www} -* {mirrors-uk-www3} - -[[usa-mirrors]] -*{mirrors-us}* - -* {mirrors-us-www5-httpv6} (IPv6) - -:sectnums: -:sectnumlevels: 6 diff --git a/documentation/content/en/books/handbook/jails/_index.adoc b/documentation/content/en/books/handbook/jails/_index.adoc index 4bdb15bf53..36c177926a 100644 --- a/documentation/content/en/books/handbook/jails/_index.adoc +++ b/documentation/content/en/books/handbook/jails/_index.adoc @@ -1,1231 +1,1231 @@ --- title: Chapter 15. Jails part: Part III. System Administration prev: books/handbook/security next: books/handbook/mac description: Jails improve on the concept of the traditional chroot environment in several ways tags: ["jails", "creating", "managing", "updating", "ezjail"] showBookMenu: true weight: 19 path: "/books/handbook/" --- [[jails]] = Jails :doctype: book :toc: macro :toclevels: 1 :icons: font :sectnums: :sectnumlevels: 6 :sectnumoffset: 15 :partnums: :source-highlighter: rouge :experimental: :images-path: books/handbook/jails/ ifdef::env-beastie[] ifdef::backend-html5[] :imagesdir: ../../../../images/{images-path} endif::[] ifndef::book[] include::shared/authors.adoc[] include::shared/mirrors.adoc[] include::shared/releases.adoc[] include::shared/attributes/attributes-{{% lang %}}.adoc[] include::shared/{{% lang %}}/teams.adoc[] include::shared/{{% lang %}}/mailing-lists.adoc[] include::shared/{{% lang %}}/urls.adoc[] toc::[] endif::[] ifdef::backend-pdf,backend-epub3[] include::../../../../../shared/asciidoctor.adoc[] endif::[] endif::[] ifndef::env-beastie[] toc::[] include::../../../../../shared/asciidoctor.adoc[] endif::[] [[jails-synopsis]] == Synopsis Since system administration is a difficult task, many tools have been developed to make life easier for the administrator. These tools often enhance the way systems are installed, configured, and maintained. One of the tools which can be used to enhance the security of a FreeBSD system is _jails_. Jails have been available since FreeBSD 4.X and continue to be enhanced in their usefulness, performance, reliability, and security. Jails build upon the man:chroot[2] concept, which is used to change the root directory of a set of processes. This creates a safe environment, separate from the rest of the system. Processes created in the chrooted environment can not access files or resources outside of it. For that reason, compromising a service running in a chrooted environment should not allow the attacker to compromise the entire system. However, a chroot has several limitations. It is suited to easy tasks which do not require much flexibility or complex, advanced features. Over time, many ways have been found to escape from a chrooted environment, making it a less than ideal solution for securing services. Jails improve on the concept of the traditional chroot environment in several ways. In a traditional chroot environment, processes are only limited in the part of the file system they can access. The rest of the system resources, system users, running processes, and the networking subsystem are shared by the chrooted processes and the processes of the host system. Jails expand this model by virtualizing access to the file system, the set of users, and the networking subsystem. More fine-grained controls are available for tuning the access of a jailed environment. Jails can be considered as a type of operating system-level virtualization. A jail is characterized by four elements: * A directory subtree: the starting point from which a jail is entered. Once inside the jail, a process is not permitted to escape outside of this subtree. * A hostname: which will be used by the jail. * An IP address: which is assigned to the jail. The IP address of a jail is often an alias address for an existing network interface. * A command: the path name of an executable to run inside the jail. The path is relative to the root directory of the jail environment. Jails have their own set of users and their own `root` account which are limited to the jail environment. The `root` account of a jail is not allowed to perform operations to the system outside of the associated jail environment. This chapter provides an overview of the terminology and commands for managing FreeBSD jails. Jails are a powerful tool for both system administrators, and advanced users. After reading this chapter, you will know: * What a jail is and what purpose it may serve in FreeBSD installations. * How to build, start, and stop a jail. * The basics of jail administration, both from inside and outside the jail. [IMPORTANT] ==== Jails are a powerful tool, but they are not a security panacea. While it is not possible for a jailed process to break out on its own, there are several ways in which an unprivileged user outside the jail can cooperate with a privileged user inside the jail to obtain elevated privileges in the host environment. Most of these attacks can be mitigated by ensuring that the jail root is not accessible to unprivileged users in the host environment. As a general rule, untrusted users with privileged access to a jail should not be given access to the host environment. ==== [[jails-terms]] == Terms Related to Jails To facilitate better understanding of parts of the FreeBSD system related to jails, their internals and the way they interact with the rest of FreeBSD, the following terms are used further in this chapter: man:chroot[8] (command):: Utility, which uses man:chroot[2] FreeBSD system call to change the root directory of a process and all its descendants. man:chroot[2] (environment):: The environment of processes running in a "chroot". This includes resources such as the part of the file system which is visible, user and group IDs which are available, network interfaces and other IPC mechanisms, etc. man:jail[8] (command):: The system administration utility which allows launching of processes within a jail environment. host (system, process, user, etc.):: The controlling system of a jail environment. The host system has access to all the hardware resources available, and can control processes both outside of and inside a jail environment. One of the important differences of the host system from a jail is that the limitations which apply to superuser processes inside a jail are not enforced for processes of the host system. hosted (system, process, user, etc.):: A process, user or other entity, whose access to resources is restricted by a FreeBSD jail. [[jails-build]] == Creating and Controlling Jails Some administrators divide jails into the following two types: "complete" jails, which resemble a real FreeBSD system, and "service" jails, dedicated to one application or service, possibly running with privileges. This is only a conceptual division and the process of building a jail is not affected by it. When creating a "complete" jail there are two options for the source of the userland: use prebuilt binaries (such as those supplied on an install media) or build from source. === Installing a Jail [[jails-install-internet]] ==== To install a Jail from the Internet The man:bsdinstall[8] tool can be used to fetch and install the binaries needed for a jail. This will walk through the picking of a mirror, which distributions will be installed into the destination directory, and some basic configuration of the jail: [source,shell] .... # bsdinstall jail /here/is/the/jail .... Once the command is complete, the next step is configuring the host to run the jail. [[jails-install-iso]] ==== To install a Jail from an ISO To install the userland from installation media, first create the root directory for the jail. This can be done by setting the `DESTDIR` variable to the proper location. Start a shell and define `DESTDIR`: [source,shell] .... # sh # export DESTDIR=/here/is/the/jail .... Mount the install media as covered in man:mdconfig[8] when using the install ISO: [source,shell] .... # mount -t cd9660 /dev/`mdconfig -f cdimage.iso` /mnt # cd /mnt/usr/freebsd-dist/ .... Extract the binaries from the tarballs on the install media into the declared destination. Minimally, only the base set needs to be extracted, but a complete install can be performed when preferred. To install just the base system: [source,shell] .... # tar -xf base.txz -C $DESTDIR .... To install everything except the kernel: [source,shell] .... # for set in base ports; do tar -xf $set.txz -C $DESTDIR ; done .... [[jails-install-source]] ==== To build and install a Jail from source The man:jail[8] manual page explains the procedure for building a jail: [source,shell] .... # setenv D /here/is/the/jail # mkdir -p $D <.> # cd /usr/src # make buildworld <.> # make installworld DESTDIR=$D <.> # make distribution DESTDIR=$D <.> # mount -t devfs devfs $D/dev <.> .... <.> Selecting a location for a jail is the best starting point. This is where the jail will physically reside within the file system of the jail's host. A good choice can be [.filename]#/usr/jail/jailname#, where _jailname_ is the hostname identifying the jail. Usually, [.filename]#/usr/# has enough space for the jail file system, which for "complete" jails is, essentially, a replication of every file present in a default installation of the FreeBSD base system. <.> If you have already rebuilt your userland using `make world` or `make buildworld`, you can skip this step and install your existing userland into the new jail. <.> This command will populate the directory subtree chosen as jail's physical location on the file system with the necessary binaries, libraries, manual pages and so on. <.> The `distribution` target for make installs every needed configuration file. In simple words, it installs every installable file of [.filename]#/usr/src/etc/# to the [.filename]#/etc# directory of the jail environment: [.filename]#$D/etc/#. <.> Mounting the man:devfs[8] file system inside a jail is not required. On the other hand, any, or almost any application requires access to at least one device, depending on the purpose of the given application. It is very important to control access to devices from inside a jail, as improper settings could permit an attacker to do nasty things in the jail. Control over man:devfs[8] is managed through rulesets which are described in the man:devfs[8] and man:devfs.conf[5] manual pages. === Configuring the Host Once a jail is installed, it can be started by using the man:jail[8] utility. The man:jail[8] utility takes four mandatory arguments which are described in the <>. Other arguments may be specified too, e.g., to run the jailed process with the credentials of a specific user. The `_command_` argument depends on the type of the jail; for a _virtual system_, [.filename]#/etc/rc# is a good choice, since it will replicate the startup sequence of a real FreeBSD system. For a _service_ jail, it depends on the service or application that will run within the jail. Jails are often started at boot time and the FreeBSD [.filename]#rc# mechanism provides an easy way to do this. [.procedure] * Configure jail parameters in [.filename]#jail.conf#: + [.programlisting] .... www { host.hostname = www.example.org; # Hostname ip4.addr = 192.168.0.10; # IP address of the jail path = "/usr/jail/www"; # Path to the jail devfs_ruleset = "www_ruleset"; # devfs ruleset mount.devfs; # Mount devfs inside the jail exec.start = "/bin/sh /etc/rc"; # Start command exec.stop = "/bin/sh /etc/rc.shutdown"; # Stop command } .... + Configure jails to start at boot time in [.filename]#rc.conf#: + [.programlisting] .... jail_enable="YES" # Set to NO to disable starting of any jails .... + The default startup of jails configured in man:jail.conf[5], will run the [.filename]#/etc/rc# script of the jail, which assumes the jail is a complete virtual system. For service jails, the default startup command of the jail should be changed, by setting the `exec.start` option appropriately. + [NOTE] ==== For a full list of available options, please see the man:jail.conf[5] manual page. ==== man:service[8] can be used to start or stop a jail by hand, if an entry for it exists in [.filename]#jail.conf#: [source,shell] .... # service jail start www # service jail stop www .... Jails can be shut down with man:jexec[8]. Use man:jls[8] to identify the jail's `JID`, then use man:jexec[8] to run the shutdown script in that jail. [source,shell] .... # jls JID IP Address Hostname Path 3 192.168.0.10 www /usr/jail/www # jexec 3 /etc/rc.shutdown .... More information about this can be found in the man:jail[8] manual page. [[jails-tuning]] == Fine Tuning and Administration There are several options which can be set for any jail, and various ways of combining a host FreeBSD system with jails, to produce higher level applications. This section presents: * Some of the options available for tuning the behavior and security restrictions implemented by a jail installation. * Some of the high-level applications for jail management, which are available through the FreeBSD Ports Collection, and can be used to implement overall jail-based solutions. [[jails-tuning-utilities]] === System Tools for Jail Tuning in FreeBSD Fine tuning of a jail's configuration is mostly done by setting man:sysctl[8] variables. A special subtree of sysctl exists as a basis for organizing all the relevant options: the `security.jail.*` hierarchy of FreeBSD kernel options. Here is a list of the main jail-related sysctls, complete with their default value. Names should be self-explanatory, but for more information about them, please refer to the man:jail[8] and man:sysctl[8] manual pages. * `security.jail.set_hostname_allowed: 1` * `security.jail.socket_unixiproute_only: 1` * `security.jail.sysvipc_allowed: 0` * `security.jail.enforce_statfs: 2` * `security.jail.allow_raw_sockets: 0` * `security.jail.chflags_allowed: 0` * `security.jail.jailed: 0` These variables can be used by the system administrator of the _host system_ to add or remove some of the limitations imposed by default on the `root` user. Note that there are some limitations which cannot be removed. The `root` user is not allowed to mount or unmount file systems from within a man:jail[8]. The `root` inside a jail may not load or unload man:devfs[8] rulesets, set firewall rules, or do many other administrative tasks which require modifications of in-kernel data, such as setting the `securelevel` of the kernel. The base system of FreeBSD contains a basic set of tools for viewing information about the active jails, and attaching to a jail to run administrative commands. The man:jls[8] and man:jexec[8] commands are part of the base FreeBSD system, and can be used to perform the following simple tasks: * Print a list of active jails and their corresponding jail identifier (JID), IP address, hostname and path. * Attach to a running jail, from its host system, and run a command inside the jail or perform administrative tasks inside the jail itself. This is especially useful when the `root` user wants to cleanly shut down a jail. The man:jexec[8] utility can also be used to start a shell in a jail to do administration in it; for example: + [source,shell] .... # jexec 1 tcsh .... [[jails-tuning-admintools]] === High-Level Administrative Tools in the FreeBSD Ports Collection Among the many third-party utilities for jail administration, one of the most complete and useful is package:sysutils/ezjail[]. It is a set of scripts that contribute to man:jail[8] management. Please refer to <> for more information. [[jails-updating]] === Keeping Jails Patched and up to Date Jails should be kept up to date from the host operating system as attempting to patch userland from within the jail may likely fail as the default behavior in FreeBSD is to disallow the use of man:chflags[1] in a jail which prevents the replacement of some files. It is possible to change this behavior but it is recommended to use man:freebsd-update[8] to maintain jails instead. Use `-b` to specify the path of the jail to be updated. To update the jail to the latest patch release of the version of FreeBSD it is already running, then execute the following commands on the host: [source,shell] .... # freebsd-update -b /here/is/the/jail fetch # freebsd-update -b /here/is/the/jail install .... To upgrade the jail to a new major or minor version, first upgrade the host system as described in crossref:cutting-edge[freebsdupdate-upgrade,“Performing Major and Minor Version Upgrades”]. Once the host has been upgraded and rebooted, the jail can then be upgraded. For example to upgrade from 12.0-RELEASE to 12.1-RELEASE, on the host run: [source,shell] .... # freebsd-update -b /here/is/the/jail --currently-running 12.0-RELEASE -r 12.1-RELEASE upgrade # freebsd-update -b /here/is/the/jail install # service jail restart myjail # freebsd-update -b /here/is/the/jail install .... Then, if it was a major version upgrade, reinstall all installed packages and restart the jail again. This is required because the ABI version changes when upgrading between major versions of FreeBSD. From the host: [source,shell] .... # pkg -j myjail upgrade -f # service jail restart myjail .... [[jails-application]] == Updating Multiple Jails The management of multiple jails can become problematic because every jail has to be rebuilt from scratch whenever it is upgraded. This can be time consuming and tedious if a lot of jails are created and manually updated. This section demonstrates one method to resolve this issue by safely sharing as much as is possible between jails using read-only man:mount_nullfs[8] mounts, so that updating is simpler. This makes it more attractive to put single services, such as HTTP, DNS, and SMTP, into individual jails. Additionally, it provides a simple way to add, remove, and upgrade jails. [NOTE] ==== Simpler solutions exist, such as ezjail, which provides an easier method of administering FreeBSD jails but is less versatile than this setup. ezjail is covered in more detail in <>. ==== The goals of the setup described in this section are: * Create a simple and easy to understand jail structure that does not require running a full installworld on each and every jail. * Make it easy to add new jails or remove existing ones. * Make it easy to update or upgrade existing jails. * Make it possible to run a customized FreeBSD branch. * Be paranoid about security, reducing as much as possible the possibility of compromise. * Save space and inodes, as much as possible. This design relies on a single, read-only master template which is mounted into each jail and one read-write device per jail. A device can be a separate physical disc, a partition, or a vnode backed memory device. This example uses read-write nullfs mounts. The file system layout is as follows: * The jails are based under the [.filename]#/home# partition. * Each jail will be mounted under the [.filename]#/home/j# directory. * The template for each jail and the read-only partition for all of the jails is [.filename]#/home/j/mroot#. * A blank directory will be created for each jail under the [.filename]#/home/j# directory. * Each jail will have a [.filename]#/s# directory that will be linked to the read-write portion of the system. * Each jail will have its own read-write system that is based upon [.filename]#/home/j/skel#. * The read-write portion of each jail will be created in [.filename]#/home/js#. [[jails-service-jails-template]] === Creating the Template This section describes the steps needed to create the master template. It is recommended to first update the host FreeBSD system to the latest -RELEASE branch using the instructions in crossref:cutting-edge[makeworld,“Updating FreeBSD from Source”]. Additionally, this template uses the package:sysutils/cpdup[] package or port and portsnap will be used to download the FreeBSD Ports Collection. [.procedure] . First, create a directory structure for the read-only file system which will contain the FreeBSD binaries for the jails. Then, change directory to the FreeBSD source tree and install the read-only file system to the jail template: + [source,shell] .... # mkdir /home/j /home/j/mroot # cd /usr/src # make installworld DESTDIR=/home/j/mroot .... . Next, prepare a FreeBSD Ports Collection for the jails as well as a FreeBSD source tree, which is required for mergemaster: + [source,shell] .... # cd /home/j/mroot # mkdir usr/ports # portsnap -p /home/j/mroot/usr/ports fetch extract # cpdup /usr/src /home/j/mroot/usr/src .... . Create a skeleton for the read-write portion of the system: + [source,shell] .... # mkdir /home/j/skel /home/j/skel/home /home/j/skel/usr-X11R6 /home/j/skel/distfiles # mv etc /home/j/skel # mv usr/local /home/j/skel/usr-local # mv tmp /home/j/skel # mv var /home/j/skel # mv root /home/j/skel .... . Use mergemaster to install missing configuration files. Then, remove the extra directories that mergemaster creates: + [source,shell] .... # mergemaster -t /home/j/skel/var/tmp/temproot -D /home/j/skel -i # cd /home/j/skel # rm -R bin boot lib libexec mnt proc rescue sbin sys usr dev .... . Now, symlink the read-write file system to the read-only file system. Ensure that the symlinks are created in the correct [.filename]#s/# locations as the creation of directories in the wrong locations will cause the installation to fail. + [source,shell] .... # cd /home/j/mroot # mkdir s # ln -s s/etc etc # ln -s s/home home # ln -s s/root root # ln -s ../s/usr-local usr/local # ln -s ../s/usr-X11R6 usr/X11R6 # ln -s ../../s/distfiles usr/ports/distfiles # ln -s s/tmp tmp # ln -s s/var var .... . As a last step, create a generic [.filename]#/home/j/skel/etc/make.conf# containing this line: + [.programlisting] .... WRKDIRPREFIX?= /s/portbuild .... + This makes it possible to compile FreeBSD ports inside each jail. Remember that the ports directory is part of the read-only system. The custom path for `WRKDIRPREFIX` allows builds to be done in the read-write portion of every jail. [[jails-service-jails-creating]] === Creating Jails The jail template can now be used to setup and configure the jails in [.filename]#/etc/rc.conf#. This example demonstrates the creation of 3 jails: `NS`, `MAIL` and `WWW`. [.procedure] . Add the following lines to [.filename]#/etc/fstab#, so that the read-only template for the jails and the read-write space will be available in the respective jails: + [.programlisting] .... /home/j/mroot /home/j/ns nullfs ro 0 0 /home/j/mroot /home/j/mail nullfs ro 0 0 /home/j/mroot /home/j/www nullfs ro 0 0 /home/js/ns /home/j/ns/s nullfs rw 0 0 /home/js/mail /home/j/mail/s nullfs rw 0 0 /home/js/www /home/j/www/s nullfs rw 0 0 .... + To prevent fsck from checking nullfs mounts during boot and dump from backing up the read-only nullfs mounts of the jails, the last two columns are both set to `0`. . Configure the jails in [.filename]#/etc/rc.conf#: + [.programlisting] .... jail_enable="YES" jail_set_hostname_allow="NO" jail_list="ns mail www" jail_ns_hostname="ns.example.org" jail_ns_ip="192.168.3.17" jail_ns_rootdir="/usr/home/j/ns" jail_ns_devfs_enable="YES" jail_mail_hostname="mail.example.org" jail_mail_ip="192.168.3.18" jail_mail_rootdir="/usr/home/j/mail" jail_mail_devfs_enable="YES" jail_www_hostname="www.example.org" jail_www_ip="62.123.43.14" jail_www_rootdir="/usr/home/j/www" jail_www_devfs_enable="YES" .... + The `jail__name__rootdir` variable is set to [.filename]#/usr/home# instead of [.filename]#/home# because the physical path of [.filename]#/home# on a default FreeBSD installation is [.filename]#/usr/home#. The `jail__name__rootdir` variable must _not_ be set to a path which includes a symbolic link, otherwise the jails will refuse to start. . Create the required mount points for the read-only file system of each jail: + [source,shell] .... # mkdir /home/j/ns /home/j/mail /home/j/www .... . Install the read-write template into each jail using package:sysutils/cpdup[]: + [source,shell] .... # mkdir /home/js # cpdup /home/j/skel /home/js/ns # cpdup /home/j/skel /home/js/mail # cpdup /home/j/skel /home/js/www .... . In this phase, the jails are built and prepared to run. First, mount the required file systems for each jail, and then start them: + [source,shell] .... # mount -a # service jail start .... The jails should be running now. To check if they have started correctly, use `jls`. Its output should be similar to the following: [source,shell] .... # jls JID IP Address Hostname Path 3 192.168.3.17 ns.example.org /home/j/ns 2 192.168.3.18 mail.example.org /home/j/mail 1 62.123.43.14 www.example.org /home/j/www .... At this point, it should be possible to log onto each jail, add new users, or configure daemons. The `JID` column indicates the jail identification number of each running jail. Use the following command to perform administrative tasks in the jail whose JID is `3`: [source,shell] .... # jexec 3 tcsh .... [[jails-service-jails-upgrading]] === Upgrading The design of this setup provides an easy way to upgrade existing jails while minimizing their downtime. Also, it provides a way to roll back to the older version should a problem occur. [.procedure] . The first step is to upgrade the host system. Then, create a new temporary read-only template in [.filename]#/home/j/mroot2#. + [source,shell] .... # mkdir /home/j/mroot2 # cd /usr/src # make installworld DESTDIR=/home/j/mroot2 # cd /home/j/mroot2 # cpdup /usr/src usr/src # mkdir s .... + The `installworld` creates a few unnecessary directories, which should be removed: + [source,shell] .... # chflags -R 0 var # rm -R etc var root usr/local tmp .... . Recreate the read-write symlinks for the master file system: + [source,shell] .... # ln -s s/etc etc # ln -s s/root root # ln -s s/home home # ln -s ../s/usr-local usr/local # ln -s ../s/usr-X11R6 usr/X11R6 # ln -s s/tmp tmp # ln -s s/var var .... . Next, stop the jails: + [source,shell] .... # service jail stop .... . Unmount the original file systems as the read-write systems are attached to the read-only system ([.filename]#/s#): + [source,shell] .... # umount /home/j/ns/s # umount /home/j/ns # umount /home/j/mail/s # umount /home/j/mail # umount /home/j/www/s # umount /home/j/www .... . Move the old read-only file system and replace it with the new one. This will serve as a backup and archive of the old read-only file system should something go wrong. The naming convention used here corresponds to when a new read-only file system has been created. Move the original FreeBSD Ports Collection over to the new file system to save some space and inodes: + [source,shell] .... # cd /home/j # mv mroot mroot.20060601 # mv mroot2 mroot # mv mroot.20060601/usr/ports mroot/usr .... . At this point the new read-only template is ready, so the only remaining task is to remount the file systems and start the jails: + [source,shell] .... # mount -a # service jail start .... Use `jls` to check if the jails started correctly. Run `mergemaster` in each jail to update the configuration files. [[jails-ezjail]] == Managing Jails with ezjail Creating and managing multiple jails can quickly become tedious and error-prone. Dirk Engling's ezjail automates and greatly simplifies many jail tasks. A _basejail_ is created as a template. Additional jails use man:mount_nullfs[8] to share many of the basejail directories without using additional disk space. Each additional jail takes only a few megabytes of disk space before applications are installed. Upgrading the copy of the userland in the basejail automatically upgrades all of the other jails. Additional benefits and features are described in detail on the ezjail web site, https://erdgeist.org/arts/software/ezjail/[]. [[jails-ezjail-install]] === Installing ezjail Installing ezjail consists of adding a loopback interface for use in jails, installing the port or package, and enabling the service. [[jails-ezjail-install-procedure]] [.procedure] . To keep jail loopback traffic off the host's loopback network interface `lo0`, a second loopback interface is created by adding an entry to [.filename]#/etc/rc.conf#: + [.programlisting] .... cloned_interfaces="lo1" .... + The second loopback interface `lo1` will be created when the system starts. It can also be created manually without a restart: + [source,shell] .... # service netif cloneup Created clone interfaces: lo1. .... + Jails can be allowed to use aliases of this secondary loopback interface without interfering with the host. + Inside a jail, access to the loopback address `127.0.0.1` is redirected to the first IP address assigned to the jail. To make the jail loopback correspond with the new `lo1` interface, that interface must be specified first in the list of interfaces and IP addresses given when creating a new jail. + Give each jail a unique loopback address in the `127.0.0.0/8` netblock. . Install package:sysutils/ezjail[]: + [source,shell] .... # cd /usr/ports/sysutils/ezjail # make install clean .... . Enable ezjail by adding this line to [.filename]#/etc/rc.conf#: + [.programlisting] .... ezjail_enable="YES" .... . The service will automatically start on system boot. It can be started immediately for the current session: + [source,shell] .... # service ezjail start .... [[jails-ezjail-initialsetup]] === Initial Setup With ezjail installed, the basejail directory structure can be created and populated. This step is only needed once on the jail host computer. In both of these examples, `-p` causes the ports tree to be retrieved with man:portsnap[8] into the basejail. That single copy of the ports directory will be shared by all the jails. Using a separate copy of the ports directory for jails isolates them from the host. The ezjailFAQ explains in more detail: http://erdgeist.org/arts/software/ezjail/#FAQ[]. [[jails-ezjail-initialsetup-procedure]] [.procedure] . To Populate the Jail with FreeBSD-RELEASE + For a basejail based on the FreeBSD RELEASE matching that of the host computer, use `install`. For example, on a host computer running FreeBSD 10-STABLE, the latest RELEASE version of FreeBSD -10 will be installed in the jail): + [source,shell] .... # ezjail-admin install -p .... . To Populate the Jail with `installworld` + The basejail can be installed from binaries created by `buildworld` on the host with `ezjail-admin update`. + In this example, FreeBSD 10-STABLE has been built from source. The jail directories are created. Then `installworld` is executed, installing the host's [.filename]#/usr/obj# into the basejail. + [source,shell] .... # ezjail-admin update -i -p .... + The host's [.filename]#/usr/src# is used by default. A different source directory on the host can be specified with `-s` and a path, or set with `ezjail_sourcetree` in [.filename]#/usr/local/etc/ezjail.conf#. [TIP] ==== The basejail's ports tree is shared by other jails. However, downloaded distfiles are stored in the jail that downloaded them. By default, these files are stored in [.filename]#/var/ports/distfiles# within each jail. [.filename]#/var/ports# inside each jail is also used as a work directory when building ports. ==== [TIP] ==== The FTP protocol is used by default to download packages for the installation of the basejail. Firewall or proxy configurations can prevent or interfere with FTP transfers. The HTTP protocol works differently and avoids these problems. It can be chosen by specifying a full URL for a particular download mirror in [.filename]#/usr/local/etc/ezjail.conf#: [.programlisting] .... ezjail_ftphost=http://ftp.FreeBSD.org .... -See crossref:mirrors[mirrors-ftp,“FTP Sites”] for a list of sites. +See the crossref:mirrors[mirrors,mirrors] section for a list of sites. ==== [[jails-ezjail-create]] === Creating and Starting a New Jail New jails are created with `ezjail-admin create`. In these examples, the `lo1` loopback interface is used as described above. [[jails-ezjail-create-steps]] [.procedure] .Procedure: Create and Start a New Jail . Create the jail, specifying a name and the loopback and network interfaces to use, along with their IP addresses. In this example, the jail is named `dnsjail`. + [source,shell] .... # ezjail-admin create dnsjail 'lo1|127.0.1.1,em0|192.168.1.50' .... + [TIP] ==== Most network services run in jails without problems. A few network services, most notably man:ping[8], use _raw network sockets_. In jails, raw network sockets are disabled by default for security. Services that require them will not work. Occasionally, a jail genuinely needs raw sockets. For example, network monitoring applications often use man:ping[8] to check the availability of other computers. When raw network sockets are actually needed in a jail, they can be enabled by editing the ezjail configuration file for the individual jail, [.filename]#/usr/local/etc/ezjail/jailname#. Modify the `parameters` entry: [.programlisting] .... export jail_jailname_parameters="allow.raw_sockets=1" .... Do not enable raw network sockets unless services in the jail actually require them. ==== . Start the jail: + [source,shell] .... # ezjail-admin start dnsjail .... . Use a console on the jail: + [source,shell] .... # ezjail-admin console dnsjail .... The jail is operating and additional configuration can be completed. Typical settings added at this point include: [.procedure] . Set the `root` Password + Connect to the jail and set the `root` user's password: + [source,shell] .... # ezjail-admin console dnsjail # passwd Changing local password for root New Password: Retype New Password: .... . Time Zone Configuration + The jail's time zone can be set with man:tzsetup[8]. To avoid spurious error messages, the man:adjkerntz[8] entry in [.filename]#/etc/crontab# can be commented or removed. This job attempts to update the computer's hardware clock with time zone changes, but jails are not allowed to access that hardware. . DNS Servers + Enter domain name server lines in [.filename]#/etc/resolv.conf# so DNS works in the jail. . Edit [.filename]#/etc/hosts# + Change the address and add the jail name to the `localhost` entries in [.filename]#/etc/hosts#. . Configure [.filename]#/etc/rc.conf# + Enter configuration settings in [.filename]#/etc/rc.conf#. This is much like configuring a full computer. The host name and IP address are not set here. Those values are already provided by the jail configuration. With the jail configured, the applications for which the jail was created can be installed. [TIP] ==== Some ports must be built with special options to be used in a jail. For example, both of the network monitoring plugin packages package:net-mgmt/nagios-plugins[] and package:net-mgmt/monitoring-plugins[] have a `JAIL` option which must be enabled for them to work correctly inside a jail. ==== [[jails-ezjail-update]] === Updating Jails [[jails-ezjail-update-os]] ==== Updating the Operating System Because the basejail's copy of the userland is shared by the other jails, updating the basejail automatically updates all of the other jails. Either source or binary updates can be used. To build the world from source on the host, then install it in the basejail, use: [source,shell] .... # ezjail-admin update -b .... If the world has already been compiled on the host, install it in the basejail with: [source,shell] .... # ezjail-admin update -i .... Binary updates use man:freebsd-update[8]. These updates have the same limitations as if man:freebsd-update[8] were being run directly. The most important one is that only -RELEASE versions of FreeBSD are available with this method. Update the basejail to the latest patched release of the version of FreeBSD on the host. For example, updating from RELEASE-p1 to RELEASE-p2. [source,shell] .... # ezjail-admin update -u .... To upgrade the basejail to a new version, first upgrade the host system as described in crossref:cutting-edge[freebsdupdate-upgrade,“Performing Major and Minor Version Upgrades”]. Once the host has been upgraded and rebooted, the basejail can then be upgraded. man:freebsd-update[8] has no way of determining which version is currently installed in the basejail, so the original version must be specified. Use man:file[1] to determine the original version in the basejail: [source,shell] .... # file /usr/jails/basejail/bin/sh /usr/jails/basejail/bin/sh: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically linked (uses shared libs), for FreeBSD 9.3, stripped .... Now use this information to perform the upgrade from `9.3-RELEASE` to the current version of the host system: [source,shell] .... # ezjail-admin update -U -s 9.3-RELEASE .... After updating the basejail, man:mergemaster[8] must be run to update each jail's configuration files. How to use man:mergemaster[8] depends on the purpose and trustworthiness of a jail. If a jail's services or users are not trusted, then man:mergemaster[8] should only be run from within that jail: [[jails-ezjail-update-mergemaster-untrusted]] .man:mergemaster[8] on Untrusted Jail [example] ==== Delete the link from the jail's [.filename]#/usr/src# into the basejail and create a new [.filename]#/usr/src# in the jail as a mountpoint. Mount the host computer's [.filename]#/usr/src# read-only on the jail's new [.filename]#/usr/src# mountpoint: [source,shell] .... # rm /usr/jails/jailname/usr/src # mkdir /usr/jails/jailname/usr/src # mount -t nullfs -o ro /usr/src /usr/jails/jailname/usr/src .... Get a console in the jail: [source,shell] .... # ezjail-admin console jailname .... Inside the jail, run `mergemaster`. Then exit the jail console: [source,shell] .... # cd /usr/src # mergemaster -U # exit .... Finally, unmount the jail's [.filename]#/usr/src#: [source,shell] .... # umount /usr/jails/jailname/usr/src .... ==== [[jails-ezjail-update-mergemaster-trusted]] .man:mergemaster[8] on Trusted Jail [example] ==== If the users and services in a jail are trusted, man:mergemaster[8] can be run from the host: [source,shell] .... # mergemaster -U -D /usr/jails/jailname .... ==== [TIP] ==== After a major version update it is recommended by package:sysutils/ezjail[] to make sure your `pkg` is of the correct version. Therefore enter: [source,shell] .... # pkg-static upgrade -f pkg .... to upgrade or downgrade to the appropriate version. ==== [[jails-ezjail-update-ports]] ==== Updating Ports The ports tree in the basejail is shared by the other jails. Updating that copy of the ports tree gives the other jails the updated version also. The basejail ports tree is updated with man:portsnap[8]: [source,shell] .... # ezjail-admin update -P .... [[jails-ezjail-control]] === Controlling Jails [[jails-ezjail-control-stop-start]] ==== Stopping and Starting Jails ezjail automatically starts jails when the computer is started. Jails can be manually stopped and restarted with `stop` and `start`: [source,shell] .... # ezjail-admin stop sambajail Stopping jails: sambajail. .... By default, jails are started automatically when the host computer starts. Autostarting can be disabled with `config`: [source,shell] .... # ezjail-admin config -r norun seldomjail .... This takes effect the next time the host computer is started. A jail that is already running will not be stopped. Enabling autostart is very similar: [source,shell] .... # ezjail-admin config -r run oftenjail .... [[jails-ezjail-control-backup]] ==== Archiving and Restoring Jails Use `archive` to create a [.filename]#.tar.gz# archive of a jail. The file name is composed from the name of the jail and the current date. Archive files are written to the archive directory, [.filename]#/usr/jails/ezjail_archives#. A different archive directory can be chosen by setting `ezjail_archivedir` in the configuration file. The archive file can be copied elsewhere as a backup, or an existing jail can be restored from it with `restore`. A new jail can be created from the archive, providing a convenient way to clone existing jails. Stop and archive a jail named `wwwserver`: [source,shell] .... # ezjail-admin stop wwwserver Stopping jails: wwwserver. # ezjail-admin archive wwwserver # ls /usr/jails/ezjail-archives/ wwwserver-201407271153.13.tar.gz .... Create a new jail named `wwwserver-clone` from the archive created in the previous step. Use the [.filename]#em1# interface and assign a new IP address to avoid conflict with the original: [source,shell] .... # ezjail-admin create -a /usr/jails/ezjail_archives/wwwserver-201407271153.13.tar.gz wwwserver-clone 'lo1|127.0.3.1,em1|192.168.1.51' .... [[jails-ezjail-example-bind]] === Full Example: BIND in a Jail Putting the BINDDNS server in a jail improves security by isolating it. This example creates a simple caching-only name server. * The jail will be called `dns1`. * The jail will use IP address `192.168.1.240` on the host's `re0` interface. * The upstream ISP's DNS servers are at `10.0.0.62` and `10.0.0.61`. * The basejail has already been created and a ports tree installed as shown in <>. [[jails-ezjail-example-bind-steps]] .Running BIND in a Jail [example] ==== Create a cloned loopback interface by adding a line to [.filename]#/etc/rc.conf#: [.programlisting] .... cloned_interfaces="lo1" .... Immediately create the new loopback interface: [source,shell] .... # service netif cloneup Created clone interfaces: lo1. .... Create the jail: [source,shell] .... # ezjail-admin create dns1 'lo1|127.0.2.1,re0|192.168.1.240' .... Start the jail, connect to a console running on it, and perform some basic configuration: [source,shell] .... # ezjail-admin start dns1 # ezjail-admin console dns1 # passwd Changing local password for root New Password: Retype New Password: # tzsetup # sed -i .bak -e '/adjkerntz/ s/^/#/' /etc/crontab # sed -i .bak -e 's/127.0.0.1/127.0.2.1/g; s/localhost.my.domain/dns1.my.domain dns1/' /etc/hosts .... Temporarily set the upstream DNS servers in [.filename]#/etc/resolv.conf# so ports can be downloaded: [.programlisting] .... nameserver 10.0.0.62 nameserver 10.0.0.61 .... Still using the jail console, install package:dns/bind99[]. [source,shell] .... # make -C /usr/ports/dns/bind99 install clean .... Configure the name server by editing [.filename]#/usr/local/etc/namedb/named.conf#. Create an Access Control List (ACL) of addresses and networks that are permitted to send DNS queries to this name server. This section is added just before the `options` section already in the file: [.programlisting] .... ... // or cause huge amounts of useless Internet traffic. acl "trusted" { 192.168.1.0/24; localhost; localnets; }; options { ... .... Use the jail IP address in the `listen-on` setting to accept DNS queries from other computers on the network: [.programlisting] .... listen-on { 192.168.1.240; }; .... A simple caching-only DNS name server is created by changing the `forwarders` section. The original file contains: [.programlisting] .... /* forwarders { 127.0.0.1; }; */ .... Uncomment the section by removing the `/\*` and `*/` lines. Enter the IP addresses of the upstream DNS servers. Immediately after the `forwarders` section, add references to the `trusted` ACL defined earlier: [.programlisting] .... forwarders { 10.0.0.62; 10.0.0.61; }; allow-query { any; }; allow-recursion { trusted; }; allow-query-cache { trusted; }; .... Enable the service in [.filename]#/etc/rc.conf#: [.programlisting] .... named_enable="YES" .... Start and test the name server: [source,shell] .... # service named start wrote key file "/usr/local/etc/namedb/rndc.key" Starting named. # /usr/local/bin/dig @192.168.1.240 freebsd.org .... A response that includes [source,shell] .... ;; Got answer; .... shows that the new DNS server is working. A long delay followed by a response including [source,shell] .... ;; connection timed out; no servers could be reached .... shows a problem. Check the configuration settings and make sure any local firewalls allow the new DNS access to the upstream DNS servers. The new DNS server can use itself for local name resolution, just like other local computers. Set the address of the DNS server in the client computer's [.filename]#/etc/resolv.conf#: [.programlisting] .... nameserver 192.168.1.240 .... A local DHCP server can be configured to provide this address for a local DNS server, providing automatic configuration on DHCP clients. ==== diff --git a/documentation/content/en/books/handbook/mirrors/_index.adoc b/documentation/content/en/books/handbook/mirrors/_index.adoc index 3723d5f948..b701d71f98 100644 --- a/documentation/content/en/books/handbook/mirrors/_index.adoc +++ b/documentation/content/en/books/handbook/mirrors/_index.adoc @@ -1,928 +1,568 @@ --- title: Appendix A. Obtaining FreeBSD part: Part V. Appendices prev: books/handbook/partv next: books/handbook/bibliography description: "How to get FreeBSD: CD and DVD sets, FTP sites and how to install and use Git" tags: ["Obtaining", "CD", "DVD", "FTP", "Git"] showBookMenu: true weight: 39 path: "/books/handbook/" --- [appendix] -[[mirrors]] = Obtaining FreeBSD :doctype: book :toc: macro :toclevels: 1 :icons: font :sectnums: :sectnumlevels: 6 :sectnumoffset: A :partnums: :source-highlighter: rouge :experimental: :images-path: books/handbook/mirrors/ ifdef::env-beastie[] ifdef::backend-html5[] :imagesdir: ../../../../images/{images-path} endif::[] ifndef::book[] include::shared/authors.adoc[] include::shared/mirrors.adoc[] include::shared/releases.adoc[] include::shared/attributes/attributes-{{% lang %}}.adoc[] include::shared/{{% lang %}}/teams.adoc[] include::shared/{{% lang %}}/mailing-lists.adoc[] include::shared/{{% lang %}}/urls.adoc[] toc::[] endif::[] ifdef::backend-pdf,backend-epub3[] include::../../../../../shared/asciidoctor.adoc[] endif::[] endif::[] ifndef::env-beastie[] toc::[] include::../../../../../shared/asciidoctor.adoc[] endif::[] -[[mirrors-http]] -== HTTP Mirrors - -The official sources for FreeBSD are available via HTTP from a worldwide set of mirror sites. -The site {central-http} is available via HTTP and anonymous FTP. -It is made up of many machines operated by the project cluster administrators and behind GeoDNS to direct users to the closest available mirror. - -[[primary]] -*{mirrors-primary}* - -In case of problems, please contact the hostmaster `<{mirrors-primary-email}>` for this domain. - -* {mirrors-primary-ftp4-http} -* {mirrors-primary-ftp10-http} -* {mirrors-primary-ftp14-http} - -[[armenia]] -*{mirrors-armenia}* - -In case of problems, please contact the hostmaster `<{mirrors-armenia-email}>` for this domain. - -* {mirrors-armenia-ftp-http} - -[[austria]] -*{mirrors-austria}* - -In case of problems, please contact the hostmaster `<{mirrors-austria-email}>` for this domain. - -* {mirrors-austria-ftp-http} - -[[brazil]] -*{mirrors-brazil}* - -In case of problems, please contact the hostmaster `<{mirrors-brazil-email}>` for this domain. - -* {mirrors-brazil-ftp2-http} - -[[bulgaria]] -*{mirrors-bulgaria}* - -In case of problems, please contact the hostmaster `<{mirrors-bulgaria-email}>` for this domain. - -* {mirrors-bulgaria-ftp-http} / {mirrors-bulgaria-ftp-httpv6} - -[[czech-republic]] -*{mirrors-czech}* - -In case of problems, please contact the hostmaster `<{mirrors-czech-email}>` for this domain. - -* {mirrors-czech-ftp-http} -* {mirrors-czech-ftp2-http} - -[[denmark]] -*{mirrors-denmark}* - -In case of problems, please contact the hostmaster `<{mirrors-denmark-email}>` for this domain. - -* {mirrors-denmark-ftp-http} - -[[france]] -*{mirrors-france}* - -In case of problems, please contact the hostmaster `<{mirrors-france-email}>` for this domain. - -* {mirrors-france-ftp1-http} - -[[germany]] -*{mirrors-germany}* - -In case of problems, please contact the hostmaster `<{mirrors-germany-email}>` for this domain. - -* http://www1.de.FreeBSD.org/freebsd/ -* http://ftp2.de.FreeBSD.org/pub/FreeBSD/ -* http://ftp4.de.FreeBSD.org/pub/FreeBSD/ -* http://ftp7.de.FreeBSD.org/pub/FreeBSD/ - -[[korea]] -*{mirrors-korea}* - -In case of problems, please contact the hostmaster `<{mirrors-korea-email}>` for this domain. - -* {mirrors-korea-ftp2-http} - -[[latvia]] -*{mirrors-latvia}* - -In case of problems, please contact the hostmaster `<{mirrors-latvia-email}>` for this domain. - -* {mirrors-latvia-ftp-http} - -[[lithuania]] -*{mirrors-lithuania}* - -In case of problems, please contact the hostmaster `<{mirrors-lithuania-email}>` for this domain. - -* {mirrors-lithuania-ftp-http} - -[[netherlands]] -*{mirrors-netherlands}* - -In case of problems, please contact the hostmaster `<{mirrors-netherlands-email}>` for this domain. - -* {mirrors-netherlands-ftp-http} - -[[new-zealand]] -*{mirrors-new-zealand}* - -* {mirrors-new-zealand-ftp-http} - -[[russia]] -*{mirrors-russia}* - -In case of problems, please contact the hostmaster `<{mirrors-russia-email}>` for this domain. - -* {mirrors-russia-ftp-http} -* {mirrors-russia-ftp2-http} -* {mirrors-russia-ftp5-http} - -[[spain]] -*{mirrors-spain}* - -In case of problems, please contact the hostmaster `<{mirrors-spain-email}>` for this domain. - -* {mirrors-spain-ftp-http} - -[[sweden]] -*{mirrors-sweden}* - -In case of problems, please contact the hostmaster `<{mirrors-sweden-email}>` for this domain. - -* {mirrors-sweden-ftp4-http} -* {mirrors-sweden-ftp6-http} - -[[switzerland]] -*{mirrors-switzerland}* - -In case of problems, please contact the hostmaster `<{mirrors-switzerland-email}>` for this domain. - -* {mirrors-switzerland-ftp-http} - -[[taiwan]] -*{mirrors-taiwan}* - -In case of problems, please contact the hostmaster `<{mirrors-taiwan-email}>` for this domain. - -* {mirrors-taiwan-ftp2-http} -* {mirrors-taiwan-ftp11-http} - -[[ukraine]] -*{mirrors-ukraine}* - -* {mirrors-ukraine-ftp-http} -* {mirrors-ukraine-ftp6-http} - -[[usa]] -*{mirrors-us}* - -In case of problems, please contact the hostmaster `<{mirrors-us-email}>` for this domain. - -* {mirrors-us-ftp4-http} -* {mirrors-us-ftp13-http} -* {mirrors-us-ftp14-http} - -[[mirrors-ftp]] -== FTP Sites - -In addition to HTTP mirrors, FreeBSD is available via anonymous FTP from the following sites. -When obtaining FreeBSD via anonymous FTP, please try to use a nearby site. -The mirror sites listed as "Primary Mirror Sites" typically have the entire FreeBSD archive (all the currently available versions for each of the architectures) but faster download speeds are probably available from a site that is in your country or region. -The regional sites carry the most recent versions for the most popular architecture(s) but might not carry the entire FreeBSD archive. -All sites provide access via anonymous FTP but some sites also provide access via other methods. -The access methods available for each site are provided in parentheses after the hostname. - -<>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>. - -[[central]] -*{central}* - -* {central-ftp} (ftp / ftpv6) - -[[primary]] -*{mirrors-primary}* - -In case of problems, please contact the hostmaster `<{mirrors-primary-email}>` for this domain. - -* {mirrors-primary-ftp1} -* {mirrors-primary-ftp2} -* {mirrors-primary-ftp3} -* {mirrors-primary-ftp4} (ftp / ftpv6) -* {mirrors-primary-ftp5} -* {mirrors-primary-ftp6} -* {mirrors-primary-ftp7} -* {mirrors-primary-ftp10} (ftp / ftpv6) -* {mirrors-primary-ftp11} -* {mirrors-primary-ftp13} -* {mirrors-primary-ftp14} - -[[armenia]] -*{mirrors-armenia}* - -In case of problems, please contact the hostmaster `<{mirrors-armenia-email}>` for this domain. - -* {mirrors-armenia-ftp} (ftp / rsync) - -[[australia]] -*{mirrors-australia}* - -In case of problems, please contact the hostmaster `<{mirrors-australia-email}>` for this domain. - -* {mirrors-australia-ftp} -* {mirrors-australia-ftp2} -* {mirrors-australia-ftp3} - -[[austria]] -*{mirrors-austria}* - -In case of problems, please contact the hostmaster `<{mirrors-austria-email}>` for this domain. - -* {mirrors-austria-ftp} (ftp / ftpv6) - -[[brazil]] -*{mirrors-brazil}* - -In case of problems, please contact the hostmaster `<{mirrors-brazil-email}>` for this domain. - -* {mirrors-brazil-ftp2} -* {mirrors-brazil-ftp3} (ftp / rsync) -* {mirrors-brazil-ftp4} - -[[bulgaria]] -*{mirrors-bulgaria}* - -In case of problems, please contact the hostmaster `<{mirrors-bulgaria-email}>` for this domain. - -* {mirrors-bulgaria-ftp} (ftp / {mirrors-bulgaria-ftpv6} / rsync / rsyncv6) - -[[czech-republic]] -*{mirrors-czech}* - -In case of problems, please contact the hostmaster `<{mirrors-czech-email}>` for this domain. - -* {mirrors-czech-ftp} (ftp / ftpv6 / rsync / rsyncv6) -* {mirrors-czech-ftp2} - -[[denmark]] -*{mirrors-denmark}* - -In case of problems, please contact the hostmaster `<{mirrors-denmark-email}>` for this domain. - -* {mirrors-denmark-ftp} (ftp / ftpv6) - -[[estonia]] -*{mirrors-estonia}* - -In case of problems, please contact the hostmaster `<{mirrors-estonia-email}>` for this domain. - -* {mirrors-estonia-ftp} - -[[finland]] -*{mirrors-finland}* - -In case of problems, please contact the hostmaster `<{mirrors-finland-email}>` for this domain. - -* {mirrors-finland-ftp} - -[[france]] -*{mirrors-france}* - -In case of problems, please contact the hostmaster `<{mirrors-france-email}>` for this domain. - -* {mirrors-france-ftp} -* {mirrors-france-ftp1} (ftp / rsync) -* {mirrors-france-ftp3} -* {mirrors-france-ftp5} -* {mirrors-france-ftp6} (ftp / rsync) -* {mirrors-france-ftp7} -* {mirrors-france-ftp8} - -[[germany]] -*{mirrors-germany}* - -In case of problems, please contact the hostmaster `<{mirrors-germany-email}>` for this domain. - -* ftp://ftp.de.FreeBSD.org/pub/FreeBSD/ -* ftp://ftp1.de.FreeBSD.org/freebsd/ -* ftp://ftp2.de.FreeBSD.org/pub/FreeBSD/ (ftp / rsync) -* ftp://ftp4.de.FreeBSD.org/FreeBSD/ -* ftp://ftp5.de.FreeBSD.org/pub/FreeBSD/ -* ftp://ftp7.de.FreeBSD.org/pub/FreeBSD/ - -[[greece]] -*{mirrors-greece}* - -In case of problems, please contact the hostmaster `<{mirrors-greece-email}>` for this domain. - -* {mirrors-greece-ftp} -* {mirrors-greece-ftp2} - -[[hong-kong]] -*{mirrors-hongkong}* +[[mirrors]] +== Mirrors -* {mirrors-hongkong-ftp} +The official mirrors of the FreeBSD project are made up of many machines operated by the project cluster administrators and behind GeoDNS to direct users to the closest available mirror. +Current locations are Brazil, Japan (two sites), Malaysia, Netherlands, South Africa, Taiwan, United Kingdom, United States of America (California, New Jersey, and Washington). -[[ireland]] -*{mirrors-ireland}* +Official mirrors service: -In case of problems, please contact the hostmaster `<{mirrors-ireland-email}>` for this domain. +[cols="1,1,3"] +|=== +| Service Name | Protocols | More information -* {mirrors-ireland-ftp} (ftp / rsync) +| **download.FreeBSD.org** +| link:https://download.FreeBSD.org/[https] link:ftp://download.FreeBSD.org/pub/FreeBSD/[ftp] +| Same content as `ftp.FreeBSD.org`, `ftp` is a legacy name; `download.FreeBSD.org` is recommended. -[[japan]] -*{mirrors-japan}* +| **git.FreeBSD.org** +| git over `https` and `ssh` +| More details on link:https://docs.freebsd.org/en/books/handbook/mirrors/#git[using git] section. -In case of problems, please contact the hostmaster `<{mirrors-japan-email}>` for this domain. +| **pkg.FreeBSD.org** +| man:pkg[8] over `http` and `https` +| Official FreeBSD package repositories used by the man:pkg[8] program. +|=== -* {mirrors-japan-ftp} -* {mirrors-japan-ftp2} -* {mirrors-japan-ftp3} -* {mirrors-japan-ftp4} -* {mirrors-japan-ftp5} -* {mirrors-japan-ftp6} -* {mirrors-japan-ftp7} -* {mirrors-japan-ftp8} -* {mirrors-japan-ftp9} +All official mirrors support IPv4 and IPv6. -[[korea]] -*{mirrors-korea}* +The FreeBSD website (https://www.FreeBSD.org and https://docs.FreeBSD.org) are not hosted in the GeoDNS Infrastructure; there are ongoing studies of its implementation. -In case of problems, please contact the hostmaster `<{mirrors-korea-email}>` for this domain. +http://ftp-archive.FreeBSD.org is not in the GeoDNS Infrastructure, hosted in only one location (US). -* {mirrors-korea-ftp} (ftp / rsync) -* {mirrors-korea-ftp2} +The project is looking for new locations; those willing to sponsor, please reach out to the Cluster Administrators team for more information. -[[latvia]] -*{mirrors-latvia}* +Mirror list maintained by the community and other companies: -In case of problems, please contact the hostmaster `<{mirrors-latvia-email}>` for this domain. +[cols="1,1,3"] +|=== +|Country | Hostname | Protocols -* {mirrors-latvia-ftp} +| Australia icon:envelope[link=mailto:{mirrors-australia-email}, title="mirror contact"] +| ftp.au.FreeBSD.org +| link:http://ftp.au.FreeBSD.org/pub/FreeBSD[http] link:http://ftp.au.FreeBSD.org/pub/FreeBSD[http_v6] link:rsync://ftp.au.FreeBSD.org[rsync] link:rsync://ftp.au.FreeBSD.org[rsync_v6] -[[lithuania]] -*{mirrors-lithuania}* +| +| ftp3.au.FreeBSD.org +| link:http://ftp3.au.FreeBSD.org/pub/FreeBSD[http] link:ftp://ftp3.au.FreeBSD.org/pub/FreeBSD[ftp] link:rsync://ftp3.au.FreeBSD.org[rsync] -In case of problems, please contact the hostmaster `<{mirrors-lithuania-email}>` for this domain. +| Austria icon:envelope[link=mailto:{mirrors-austria-email}, title="mirror contact"] +| ftp.at.FreeBSD.org +| link:http://ftp.at.FreeBSD.org/pub/FreeBSD[http] link:ftp://ftp.at.FreeBSD.org/pub/FreeBSD[ftp] link:rsync://ftp.at.FreeBSD.org[rsync] -* {mirrors-lithuania-ftp} +| Brazil icon:envelope[link=mailto:{mirrors-brazil-email}, title="mirror contact"] +| ftp2.br.FreeBSD.org +| link:http://ftp2.br.FreeBSD.org/FreeBSD[http] link:rsync://ftp2.br.FreeBSD.org[rsync] link:rsync://ftp2.br.FreeBSD.org[rsync_v6] -[[netherlands]] -*{mirrors-netherlands}* +| +| ftp3.br.FreeBSD.org +| link:http://ftp3.br.FreeBSD.org/pub/FreeBSD[http] link:ftp://ftp3.br.FreeBSD.org/pub/FreeBSD[ftp] link:rsync://ftp3.br.FreeBSD.org[rsync] -In case of problems, please contact the hostmaster `<{mirrors-netherlands-email}>` for this domain. +| Bulgaria icon:envelope[link=mailto:{mirrors-bulgaria-email}, title="mirror contact"] +| ftp.bg.FreeBSD.org +| link:ftp://ftp.bg.FreeBSD.org/pub/FreeBSD[ftp] link:ftp://ftp.bg.FreeBSD.org/pub/FreeBSD[ftp_v6] link:rsync://ftp.bg.FreeBSD.org[rsync] link:rsync://ftp.bg.FreeBSD.org[rsync_v6] -* {mirrors-netherlands-ftp} (ftp / rsync) -* {mirrors-netherlands-ftp2} +| Czech Republic icon:envelope[link=mailto:{mirrors-czech-email}, title="mirror contact"] +| ftp.cz.FreeBSD.org +| link:http://ftp.cz.FreeBSD.org/pub/FreeBSD[http] link:http://ftp.cz.FreeBSD.org/pub/FreeBSD[http_v6] link:rsync://ftp.cz.FreeBSD.org[rsync] link:rsync://ftp.cz.FreeBSD.org[rsync_v6] -[[new-zealand]] -*{mirrors-new-zealand}* +| Finland icon:envelope[link=mailto:{mirrors-finland-email}, title="mirror contact"] +| ftp.fi.FreeBSD.org +| link:ftp://ftp.fi.FreeBSD.org/pub/FreeBSD[ftp] -* {mirrors-new-zealand-ftp} +| France icon:envelope[link=mailto:{mirrors-france-email}, title="mirror contact"] +| ftp.fr.FreeBSD.org +| link:http://ftp.fr.FreeBSD.org/pub/FreeBSD[http] link:http://ftp.fr.FreeBSD.org/pub/FreeBSD[http_v6] link:ftp://ftp.fr.FreeBSD.org/pub/FreeBSD[ftp] link:ftp://ftp.fr.FreeBSD.org/pub/FreeBSD[ftp_v6] link:rsync://ftp.fr.FreeBSD.org[rsync] link:rsync://ftp.fr.FreeBSD.org[rsync_v6] -[[norway]] -*{mirrors-norway}* +| +| ftp3.fr.FreeBSD.org +| link:ftp://ftp3.fr.FreeBSD.org/pub/FreeBSD[ftp] -In case of problems, please contact the hostmaster `<{mirrors-norway-email}>` for this domain. +| +| ftp6.fr.FreeBSD.org +| link:http://ftp6.fr.FreeBSD.org/pub/FreeBSD[http] link:ftp://ftp6.fr.FreeBSD.org/pub/FreeBSD[ftp] link:rsync://ftp6.fr.FreeBSD.org[rsync] -* {mirrors-norway-ftp} (ftp / rsync) +| Germany icon:envelope[link=mailto:{mirrors-germany-email}, title="mirror contact"] +| ftp.de.FreeBSD.org +| link:ftp://ftp.de.FreeBSD.org/pub/FreeBSD[ftp] link:ftp://ftp.de.FreeBSD.org/pub/FreeBSD[ftp_v6] link:rsync://ftp.de.FreeBSD.org[rsync] link:rsync://ftp.de.FreeBSD.org[rsync_v6] -[[poland]] -*{mirrors-poland}* +| +| ftp1.de.FreeBSD.org +| link:http://ftp1.de.FreeBSD.org/pub/FreeBSD[http] link:http://ftp1.de.FreeBSD.org/pub/FreeBSD[http_v6] link:ftp://ftp1.de.FreeBSD.org/pub/FreeBSD[ftp] link:ftp://ftp1.de.FreeBSD.org/pub/FreeBSD[ftp_v6] link:rsync://ftp1.de.FreeBSD.org[rsync] link:rsync://ftp1.de.FreeBSD.org[rsync_v6] -In case of problems, please contact the hostmaster `<{mirrors-poland-email}>` for this domain. +| +| ftp2.de.FreeBSD.org +| link:http://ftp2.de.FreeBSD.org/pub/FreeBSD[http] link:http://ftp2.de.FreeBSD.org/pub/FreeBSD[http_v6] link:ftp://ftp2.de.FreeBSD.org/pub/FreeBSD[ftp] link:ftp://ftp2.de.FreeBSD.org/pub/FreeBSD[ftp_v6] link:rsync://ftp2.de.FreeBSD.org[rsync] link:rsync://ftp2.de.FreeBSD.org[rsync_v6] -* {mirrors-poland-ftp} -* ftp2.pl.FreeBSD.org +| +| ftp5.de.FreeBSD.org +| link:ftp://ftp5.de.FreeBSD.org/pub/FreeBSD[ftp] link:ftp://ftp5.de.FreeBSD.org/pub/FreeBSD[ftp_v6] -[[russia]] -*{mirrors-russia}* +| +| ftp7.de.FreeBSD.org +| link:http://ftp7.de.FreeBSD.org/pub/FreeBSD[http] link:http://ftp7.de.FreeBSD.org/pub/FreeBSD[http_v6] link:ftp://ftp7.de.FreeBSD.org/pub/FreeBSD[ftp] link:ftp://ftp7.de.FreeBSD.org/pub/FreeBSD[ftp_v6] -In case of problems, please contact the hostmaster `<{mirrors-russia-email}>` for this domain. +| Greece icon:envelope[link=mailto:{mirrors-greece-email}, title="mirror contact"] +| ftp.gr.FreeBSD.org +| link:http://ftp.gr.FreeBSD.org/pub/FreeBSD[http] link:http://ftp.gr.FreeBSD.org/pub/FreeBSD[http_v6] link:ftp://ftp.gr.FreeBSD.org/pub/FreeBSD[ftp] link:ftp://ftp.gr.FreeBSD.org/pub/FreeBSD[ftp_v6] -* {mirrors-russia-ftp} (ftp / rsync) -* {mirrors-russia-ftp2} (ftp / rsync) -* {mirrors-russia-ftp5} (ftp / rsync) -* {mirrors-russia-ftp6} +| +| ftp2.gr.FreeBSD.org +| link:http://ftp2.gr.FreeBSD.org/pub/FreeBSD[http] link:http://ftp2.gr.FreeBSD.org/pub/FreeBSD[http_v6] link:ftp://ftp2.gr.FreeBSD.org/pub/FreeBSD[ftp] link:ftp://ftp2.gr.FreeBSD.org/pub/FreeBSD[ftp_v6] link:rsync://ftp2.gr.FreeBSD.org[rsync] -[[saudi-arabia]] -*{mirrors-saudi-arabia}* +| Japan icon:envelope[link=mailto:{mirrors-japan-email}, title="mirror contact"] +| ftp.jp.FreeBSD.org +| link:http://ftp.jp.FreeBSD.org/pub/FreeBSD[http] link:http://ftp.jp.FreeBSD.org/pub/FreeBSD[http_v6] link:ftp://ftp.jp.FreeBSD.org/pub/FreeBSD[ftp] link:ftp://ftp.jp.FreeBSD.org/pub/FreeBSD[ftp_v6] link:rsync://ftp.jp.FreeBSD.org[rsync] link:rsync://ftp.jp.FreeBSD.org[rsync_v6] -In case of problems, please contact the hostmaster `<{mirrors-saudi-arabia-email}>` for this domain. +| +| ftp2.jp.FreeBSD.org +| link:ftp://ftp2.jp.FreeBSD.org/pub/FreeBSD[ftp] link:rsync://ftp2.jp.FreeBSD.org[rsync] link:rsync://ftp2.jp.FreeBSD.org[rsync_v6] -* {mirrors-saudi-arabia-ftp} +| +| ftp3.jp.FreeBSD.org +| link:http://ftp3.jp.FreeBSD.org/pub/FreeBSD[http] link:rsync://ftp3.jp.FreeBSD.org[rsync] -[[slovenia]] -*{mirrors-slovenia}* +| +| ftp4.jp.FreeBSD.org +| link:ftp://ftp4.jp.FreeBSD.org/pub/FreeBSD[ftp] -In case of problems, please contact the hostmaster `<{mirrors-slovenia-email}>` for this domain. +| +| ftp6.jp.FreeBSD.org +| link:http://ftp6.jp.FreeBSD.org/pub/FreeBSD[http] link:http://ftp6.jp.FreeBSD.org/pub/FreeBSD[http_v6] link:ftp://ftp6.jp.FreeBSD.org/pub/FreeBSD[ftp] link:ftp://ftp6.jp.FreeBSD.org/pub/FreeBSD[ftp_v6] link:rsync://ftp6.jp.FreeBSD.org[rsync] link:rsync://ftp6.jp.FreeBSD.org[rsync_v6] -* {mirrors-slovenia-ftp} +| Korea icon:envelope[link=mailto:{mirrors-korea-email}, title="mirror contact"] +| ftp.kr.FreeBSD.org +| link:http://ftp.kr.FreeBSD.org/pub/FreeBSD[http] link:https://ftp.kr.FreeBSD.org/pub/FreeBSD[https] link:ftp://ftp.kr.FreeBSD.org/pub/FreeBSD[ftp] link:rsync://ftp.kr.FreeBSD.org[rsync] -[[south-africa]] -*{mirrors-south-africa}* +| +| ftp2.kr.FreeBSD.org +| link:rsync://ftp2.kr.FreeBSD.org[rsync] -In case of problems, please contact the hostmaster `<{mirrors-south-africa-email}>` for this domain. +| Latvia icon:envelope[link=mailto:{mirrors-latvia-email}, title="mirror contact"] +| ftp.lv.FreeBSD.org +| link:http://ftp.lv.FreeBSD.org/pub/FreeBSD[http] link:ftp://ftp.lv.FreeBSD.org/pub/FreeBSD[ftp] -* {mirrors-south-africa-ftp} -* {mirrors-south-africa-ftp2} -* {mirrors-south-africa-ftp4} +| Netherlands icon:envelope[link=mailto:{mirrors-netherlands-email}, title="mirror contact"] +| ftp.nl.FreeBSD.org +| link:http://ftp.nl.FreeBSD.org/pub/FreeBSD[http] link:http://ftp.nl.FreeBSD.org/pub/FreeBSD[http_v6] link:ftp://ftp.nl.FreeBSD.org/pub/FreeBSD[ftp] link:ftp://ftp.nl.FreeBSD.org/pub/FreeBSD[ftp_v6] link:rsync://ftp.nl.FreeBSD.org[rsync] link:rsync://ftp.nl.FreeBSD.org[rsync_v6] -[[spain]] -*{mirrors-spain}* +| +| ftp2.nl.FreeBSD.org +| link:http://ftp2.nl.FreeBSD.org/pub/FreeBSD[http] link:ftp://ftp2.nl.FreeBSD.org/pub/FreeBSD[ftp] link:rsync://ftp2.nl.FreeBSD.org[rsync] -In case of problems, please contact the hostmaster `<{mirrors-spain-email}>` for this domain. +| New Zealand icon:envelope[link=mailto:{mirrors-new-zealand-email}, title="mirror contact"] +| ftp.nz.FreeBSD.org +| link:http://ftp.nz.FreeBSD.org/pub/FreeBSD[http] link:ftp://ftp.nz.FreeBSD.org/pub/FreeBSD[ftp] -* {mirrors-spain-ftp} -* {mirrors-spain-ftp3} +| Norway icon:envelope[link=mailto:{mirrors-norway-email}, title="mirror contact"] +| ftp.no.FreeBSD.org +| link:ftp://ftp.no.FreeBSD.org/pub/FreeBSD[ftp] link:ftp://ftp.no.FreeBSD.org/pub/FreeBSD[ftp_v6] link:rsync://ftp.no.FreeBSD.org[rsync] link:rsync://ftp.no.FreeBSD.org[rsync_v6] -[[sweden]] -*{mirrors-sweden}* +| Poland icon:envelope[link=mailto:{mirrors-poland-email}, title="mirror contact"] +| ftp.pl.FreeBSD.org +| link:http://ftp.pl.FreeBSD.org/pub/FreeBSD[http] link:http://ftp.pl.FreeBSD.org/pub/FreeBSD[http_v6] link:ftp://ftp.pl.FreeBSD.org/pub/FreeBSD[ftp] link:rsync://ftp.pl.FreeBSD.org[rsync] link:rsync://ftp.pl.FreeBSD.org[rsync_v6] -In case of problems, please contact the hostmaster `<{mirrors-sweden-email}>` for this domain. +| Russia icon:envelope[link=mailto:{mirrors-russia-email}, title="mirror contact"] +| ftp.ru.FreeBSD.org +| link:http://ftp.ru.FreeBSD.org/pub/FreeBSD[http] link:http://ftp.ru.FreeBSD.org/pub/FreeBSD[http_v6] link:ftp://ftp.ru.FreeBSD.org/pub/FreeBSD[ftp] link:ftp://ftp.ru.FreeBSD.org/pub/FreeBSD[ftp_v6] link:rsync://ftp.ru.FreeBSD.org[rsync] link:rsync://ftp.ru.FreeBSD.org[rsync_v6] -* {mirrors-sweden-ftp} -* {mirrors-sweden-ftp2} -* {mirrors-sweden-ftp3} -* {mirrors-sweden-ftp4} (ftp / ftpv6) -* {mirrors-sweden-ftp6} +| +| ftp2.ru.FreeBSD.org +| link:https://ftp2.ru.FreeBSD.org/pub/FreeBSD[https] link:ftp://ftp2.ru.FreeBSD.org/pub/FreeBSD[ftp] link:rsync://ftp2.ru.FreeBSD.org[rsync] -[[switzerland]] -*{mirrors-switzerland}* +| Slovenia icon:envelope[link=mailto:{mirrors-slovenia-email}, title="mirror contact"] +| ftp.si.FreeBSD.org +| link:http://ftp.si.FreeBSD.org/pub/FreeBSD[http] link:http://ftp.si.FreeBSD.org/pub/FreeBSD[http_v6] link:ftp://ftp.si.FreeBSD.org/pub/FreeBSD[ftp] link:ftp://ftp.si.FreeBSD.org/pub/FreeBSD[ftp_v6] -In case of problems, please contact the hostmaster `<{mirrors-switzerland-email}>` for this domain. +| South Africa icon:envelope[link=mailto:{mirrors-south-africa-email}, title="mirror contact"] +| ftp.za.FreeBSD.org +| link:https://ftp.za.FreeBSD.org/pub/FreeBSD[https] link:https://ftp.za.FreeBSD.org/pub/FreeBSD[https_v6] link:rsync://ftp.za.FreeBSD.org[rsync] link:rsync://ftp.za.FreeBSD.org[rsync_v6] -* {mirrors-switzerland-ftp} +| +| ftp2.za.FreeBSD.org +| link:http://ftp2.za.FreeBSD.org/pub/FreeBSD[http] link:http://ftp2.za.FreeBSD.org/pub/FreeBSD[http_v6] link:ftp://ftp2.za.FreeBSD.org/pub/FreeBSD[ftp_v6] -[[taiwan]] -*{mirrors-taiwan}* +| +| ftp4.za.FreeBSD.org +| link:http://ftp4.za.FreeBSD.org/pub/FreeBSD[http] link:ftp://ftp4.za.FreeBSD.org/pub/FreeBSD[ftp] link:rsync://ftp4.za.FreeBSD.org[rsync] -In case of problems, please contact the hostmaster `<{mirrors-taiwan-email}>` for this domain. +| Sweden icon:envelope[link=mailto:{mirrors-sweden-email}, title="mirror contact"] +| ftp.se.FreeBSD.org +| link:http://ftp.se.FreeBSD.org/pub/FreeBSD[http] link:http://ftp.se.FreeBSD.org/pub/FreeBSD[http_v6] link:ftp://ftp.se.FreeBSD.org/pub/FreeBSD[ftp] link:ftp://ftp.se.FreeBSD.org/pub/FreeBSD[ftp_v6] link:rsync://ftp.se.FreeBSD.org[rsync] link:rsync://ftp.se.FreeBSD.org[rsync_v6] -* {mirrors-taiwan-ftp} (ftp / ftpv6 / rsync / rsyncv6) -* {mirrors-taiwan-ftp2} (ftp / ftpv6 / rsync / rsyncv6) -* {mirrors-taiwan-ftp4} -* {mirrors-taiwan-ftp5} -* {mirrors-taiwan-ftp6} (ftp / ftpv6 / rsync) -* {mirrors-taiwan-ftp7} -* {mirrors-taiwan-ftp8} -* {mirrors-taiwan-ftp11} -* {mirrors-taiwan-ftp12} -* {mirrors-taiwan-ftp13} -* {mirrors-taiwan-ftp14} -* {mirrors-taiwan-ftp15} +| Taiwan icon:envelope[link=mailto:{mirrors-taiwan-email}, title="mirror contact"] +| ftp4.tw.FreeBSD.org +| link:https://ftp4.tw.FreeBSD.org/pub/FreeBSD[https] link:ftp://ftp4.tw.FreeBSD.org/pub/FreeBSD[ftp] link:rsync://ftp4.tw.FreeBSD.org[rsync] -[[ukraine]] -*{mirrors-ukraine}* +| +| ftp5.tw.FreeBSD.org +| link:http://ftp5.tw.FreeBSD.org/pub/FreeBSD[http] link:ftp://ftp5.tw.FreeBSD.org/pub/FreeBSD[ftp] -* {mirrors-ukraine-ftp} -* {mirrors-ukraine-ftp6} -* {mirrors-ukraine-ftp7} +| Ukraine icon:envelope[link=mailto:{mirrors-ukraine-email}, title="mirror contact"] +| ftp.ua.FreeBSD.org +| link:http://ftp.ua.FreeBSD.org/pub/FreeBSD[http] link:ftp://ftp.ua.FreeBSD.org/pub/FreeBSD[ftp] link:ftp://ftp.ua.FreeBSD.org/pub/FreeBSD[ftp_v6] link:rsync://ftp.ua.FreeBSD.org[rsync] link:rsync://ftp.ua.FreeBSD.org[rsync_v6] -[[uk]] -*{mirrors-uk}* +| United Kingdom icon:envelope[link=mailto:{mirrors-uk-email}, title="mirror contact"] +| ftp.uk.FreeBSD.org +| link:http://ftp.uk.FreeBSD.org/pub/FreeBSD[http] link:http://ftp.uk.FreeBSD.org/pub/FreeBSD[http_v6] link:ftp://ftp.uk.FreeBSD.org/pub/FreeBSD[ftp] link:ftp://ftp.uk.FreeBSD.org/pub/FreeBSD[ftp_v6] link:rsync://ftp.uk.FreeBSD.org[rsync] link:rsync://ftp.uk.FreeBSD.org[rsync_v6] -In case of problems, please contact the hostmaster `<{mirrors-uk-email}>` for this domain. +| +| ftp2.uk.FreeBSD.org +| link:http://ftp2.uk.FreeBSD.org/pub/FreeBSD[http] link:http://ftp2.uk.FreeBSD.org/pub/FreeBSD[http_v6] link:https://ftp2.uk.FreeBSD.org/pub/FreeBSD[https] link:https://ftp2.uk.FreeBSD.org/pub/FreeBSD[https_v6] link:ftp://ftp2.uk.FreeBSD.org/pub/FreeBSD[ftp] link:ftp://ftp2.uk.FreeBSD.org/pub/FreeBSD[ftp_v6] -* {mirrors-uk-ftp} -* {mirrors-uk-ftp2} -* {mirrors-uk-ftp3} -* {mirrors-uk-ftp4} -* {mirrors-uk-ftp5} +| United States of America icon:envelope[link=mailto:{mirrors-us-email}, title="mirror contact"] +| ftp11.FreeBSD.org +| link:http://ftp11.FreeBSD.org/pub/FreeBSD[http] link:http://ftp11.FreeBSD.org/pub/FreeBSD[http_v6] link:ftp://ftp11.FreeBSD.org/pub/FreeBSD[ftp] link:ftp://ftp11.FreeBSD.org/pub/FreeBSD[ftp_v6] link:rsync://ftp11.FreeBSD.org[rsync] link:rsync://ftp11.FreeBSD.org[rsync_v6] -[[usa]] -*{mirrors-us}* +| +| ftp14.FreeBSD.org +| link:ftp://ftp14.FreeBSD.org/pub/FreeBSD[ftp] link:rsync://ftp14.FreeBSD.org[rsync] (Former official tier 1) -In case of problems, please contact the hostmaster `<{mirrors-us-email}>` for this domain. +| +| ftp5.FreeBSD.org +| link:http://ftp5.FreeBSD.org/pub/FreeBSD[http] link:http://ftp5.FreeBSD.org/pub/FreeBSD[http_v6] link:ftp://ftp5.FreeBSD.org/pub/FreeBSD[ftp] link:ftp://ftp5.FreeBSD.org/pub/FreeBSD[ftp_v6] +|=== -* {mirrors-us-ftp} -* {mirrors-us-ftp2} -* {mirrors-us-ftp3} -* {mirrors-us-ftp4} (ftp / ftpv6) -* {mirrors-us-ftp5} -* {mirrors-us-ftp6} -* {mirrors-us-ftp8} -* {mirrors-us-ftp10} -* {mirrors-us-ftp11} -* {mirrors-us-ftp13} (ftp / rsync) -* {mirrors-us-ftp14} -* {mirrors-us-ftp15} +The current list of protocols supported by the community mirrors was last updated on 2022-01-31, and it's not guaranteed. [[git]] == Using Git [[git-intro]] === Introduction As of December 2020, FreeBSD uses git as the primary version control system for storing all of FreeBSD's base source code and documentation. As of April 2021, FreeBSD uses git as the only version control system for storing all of FreeBSD's Ports Collection. [NOTE] ==== Git is generally a developer tool. Users may prefer to use `freebsd-update` (crossref:cutting-edge[updating-upgrading-freebsdupdate,“FreeBSD Update”]) to update the FreeBSD base system, and `portsnap` (crossref:ports[ports-using,“Using the Ports Collection”]) to update the FreeBSD Ports Collection. ==== This section demonstrates how to install Git on a FreeBSD system and use it to create a local copy of a FreeBSD source code repository. [[git-install]] === Installation Git can be installed from the Ports Collection, or as a package: [source,shell] .... # pkg install git .... [[git-usage]] === Running Git To fetch a clean copy of the sources into a local directory, use `git clone`. This directory of files is called the _working tree_. Git uses URLs to designate a repository. There are three different repositories, `src` for the FreeBSD system source code, `doc` for documentation, and `ports` for the FreeBSD Ports Collection. All three are reachable over two different protocols: HTTPS and SSH. For example, the URL `https://git.FreeBSD.org/src.git` specifies the main branch of the `src` repository, using the `https` protocol. [[git-url-table]] .FreeBSD Git Repository URL Table [options="header,footer"] |======================================================= |Item | Git URL | Read-only src repo via HTTPS | `https://git.FreeBSD.org/src.git` | Read-only src repo via anon-ssh | `ssh://anongit@git.FreeBSD.org/src.git` | Read-only doc repo via HTTPS | `https://git.FreeBSD.org/doc.git` | Read-only doc repo via anon-ssh | `ssh://anongit@git.FreeBSD.org/doc.git` | Read-only ports repo via HTTPS | `https://git.FreeBSD.org/ports.git` | Read-only ports repo via anon-ssh | `ssh://anongit@git.FreeBSD.org/ports.git` |======================================================= External mirrors maintained by project members are also available; please refer to the <> section. To clone a copy of the FreeBSD system source code repository: [source,shell] .... # git clone -o freebsd https://git.FreeBSD.org/src.git /usr/src .... The `-o freebsd` option specifies the origin; by convention in the FreeBSD documentation, the origin is assumed to be `freebsd`. Because the initial checkout must download the full branch of the remote repository, it can take a while. Please be patient. Initially, the working tree contains source code for the `main` branch, which corresponds to CURRENT. To switch to 13-STABLE instead: [source,shell] .... # cd /usr/src # git checkout stable/13 .... The working tree can be updated with `git pull`. To update [.filename]#/usr/src# created in the example above, use: [source,shell] .... # cd /usr/src # git pull --rebase .... The update is much quicker than a checkout, only transferring files that have changed. === Web-based repository browser The FreeBSD project uses cgit as the web-based repository browser: link:https://cgit.FreeBSD.org/[https://cgit.FreeBSD.org/]. === For Developers For information about write access to repositories see the extref:{committers-guide}[Committer's Guide, git-mini-primer]. [[external-mirrors]] === External mirrors Those mirrors are not hosted in FreeBSD.org but still maintained by the project members. Users and developers are welcome to pull or browse repositories on those mirrors. Pull requests for the `doc` GitHub repository are being accepted; otherwise, the project workflow with those mirrors is still under discussion. Codeberg:: - doc: https://codeberg.org/FreeBSD/freebsd-doc - ports: https://codeberg.org/FreeBSD/freebsd-ports - src: https://codeberg.org/FreeBSD/freebsd-src GitHub:: - doc: https://github.com/freebsd/freebsd-doc - ports: https://github.com/freebsd/freebsd-ports - src: https://github.com/freebsd/freebsd-src GitLab:: - doc: https://gitlab.com/FreeBSD/freebsd-doc - ports: https://gitlab.com/FreeBSD/freebsd-ports - src: https://gitlab.com/FreeBSD/freebsd-src === Mailing lists The main mailing list for general usage and questions about git in the FreeBSD project is https://lists.freebsd.org/subscription/freebsd-git[freebsd-git]. For more details, including commit messages lists, see the crossref:handbook/eresources[eresources-mail, Mailing Lists] chapter. === SSH host keys * gitrepo.FreeBSD.org host key fingerprints: ** ECDSA key fingerprint is `SHA256:seWO5D27ySURcx4bknTNKlC1mgai0whP443PAKEvvZA` ** ED25519 key fingerprint is `SHA256:lNR6i4BEOaaUhmDHBA1WJsO7H3KtvjE2r5q4sOxtIWo` ** RSA key fingerprint is `SHA256:f453CUEFXEJAXlKeEHV+ajJfeEfx9MdKQUD7lIscnQI` * git.FreeBSD.org host key fingerprints: ** ECDSA key fingerprint is `SHA256:/UlirUAsGiitupxmtsn7f9b7zCWd0vCs4Yo/tpVWP9w` ** ED25519 key fingerprint is `SHA256:y1ljKrKMD3lDObRUG3xJ9gXwEIuqnh306tSyFd1tuZE` ** RSA key fingerprint is `SHA256:jBe6FQGoH4HjvrIVM23dcnLZk9kmpdezR/CvQzm7rJM` These are also published as SSHFP records in DNS. [[svn]] == Using Subversion [[svn-intro]] === Introduction As of December 2020, FreeBSD uses git as the primary version control system for storing all of FreeBSD's source code and documentation. Changes from the git repo on the `stable/11`, `stable/12` and related releng branches are exported to the subversion repository. This export will continue through the life of these branches. From July 2012 to March 2021, FreeBSD used Subversion as the only version control system for storing all of FreeBSD's Ports Collection. As of April 2021, FreeBSD uses git as the only version control system for storing all of FreeBSD's Ports Collection. [NOTE] ==== Subversion is generally a developer tool. Users may prefer to use `freebsd-update` (crossref:cutting-edge[updating-upgrading-freebsdupdate,“FreeBSD Update”]) to update the FreeBSD base system, and `portsnap` (crossref:ports[ports-using,“Using the Ports Collection”]) to update the FreeBSD Ports Collection. After March 2021, subversion use is only for legacy branches (`stable/11` and `stable/12`). ==== This section demonstrates how to install Subversion on a FreeBSD system and use it to create a local copy of a FreeBSD repository. Additional information on the use of Subversion is included. [[svn-svnlite]] === Svnlite A lightweight version of Subversion is already installed on FreeBSD as `svnlite`. The port or package version of Subversion is only needed if the Python or Perl API is needed, or if a later version of Subversion is desired. The only difference from normal Subversion use is that the command name is `svnlite`. [[svn-install]] === Installation If `svnlite` is unavailable or the full version of Subversion is needed, then it must be installed. Subversion can be installed from the Ports Collection: [source,shell] .... # cd /usr/ports/devel/subversion # make install clean .... Subversion can also be installed as a package: [source,shell] .... # pkg install subversion .... [[svn-usage]] === Running Subversion To fetch a clean copy of the sources into a local directory, use `svn`. The files in this directory are called a _local working copy_. [WARNING] ==== Move or delete an existing destination directory before using `checkout` for the first time. Checkout over an existing non-`svn` directory can cause conflicts between the existing files and those brought in from the repository. ==== Subversion uses URLs to designate a repository, taking the form of _protocol://hostname/path_. The first component of the path is the FreeBSD repository to access. There are three different repositories, `base` for the FreeBSD base system source code, `ports` for the Ports Collection, and `doc` for documentation. For example, the URL `https://svn.FreeBSD.org/base/head/` specifies the main branch of the src repository, using the `https` protocol. A checkout from a given repository is performed with a command like this: [source,shell] .... # svn checkout https://svn.FreeBSD.org/repository/branch lwcdir .... where: * _repository_ is one of the Project repositories: `base`, `ports`, or `doc`. * _branch_ depends on the repository used. `ports` and `doc` are mostly updated in the `head` branch, while `base` maintains the latest version of -CURRENT under `head` and the respective latest versions of the -STABLE branches under `stable/11` (11._x_) and `stable/12` (12._x_). * _lwcdir_ is the target directory where the contents of the specified branch should be placed. This is usually [.filename]#/usr/ports# for `ports`, [.filename]#/usr/src# for `base`, and [.filename]#/usr/doc# for `doc`. This example checks out the Source Tree from the FreeBSD repository using the HTTPS protocol, placing the local working copy in [.filename]#/usr/src#. If [.filename]#/usr/src# is already present but was not created by `svn`, remember to rename or delete it before the checkout. [source,shell] .... # svn checkout https://svn.FreeBSD.org/base/head /usr/src .... Because the initial checkout must download the full branch of the remote repository, it can take a while. Please be patient. After the initial checkout, the local working copy can be updated by running: [source,shell] .... # svn update lwcdir .... To update [.filename]#/usr/src# created in the example above, use: [source,shell] .... # svn update /usr/src .... The update is much quicker than a checkout, only transferring files that have changed. An alternate way of updating the local working copy after checkout is provided by the [.filename]#Makefile# in the [.filename]#/usr/ports#, [.filename]#/usr/src#, and [.filename]#/usr/doc# directories. Set `SVN_UPDATE` and use the `update` target. For example, to update [.filename]#/usr/src#: [source,shell] .... # cd /usr/src # make update SVN_UPDATE=yes .... [[svn-mirrors]] === Subversion Mirror Sites The FreeBSD Subversion repository is: [.programlisting] .... svn.FreeBSD.org .... This is a publicly accessible mirror network that uses GeoDNS to select an appropriate back end server. To view the FreeBSD Subversion repositories through a browser, use https://svnweb.FreeBSD.org/[https://svnweb.FreeBSD.org/]. HTTPS is the preferred protocol, but the [.filename]#security/ca_root_nss# package will need to be installed in order to automatically validate certificates. === For More Information For other information about using Subversion, please see the "Subversion Book", titled http://svnbook.red-bean.com/[Version Control with Subversion], or the http://subversion.apache.org/docs/[Subversion Documentation]. -[[mirrors-rsync]] -== Using rsync - -These sites make FreeBSD available through the rsync protocol. -The rsync utility transfers only the differences between two sets of files. -This is useful for mirror sites of the FreeBSD FTP server. -The rsync suite is available for many operating systems, on FreeBSD, see the package:net/rsync[] port or use the package. - -Czech Republic:: -rsync://ftp.cz.FreeBSD.org/ -+ -Available collections: - -** ftp: A partial mirror of the FreeBSD FTP server. -** FreeBSD: A full mirror of the FreeBSD FTP server. - -Germany:: -rsync://rsync3.de.FreeBSD.org/freebsd/ - -Netherlands:: -rsync://ftp.nl.FreeBSD.org/ -+ -Available collections: - -** FreeBSD: A full mirror of the FreeBSD FTP server. - -Russia:: -rsync://ftp.mtu.ru/ -+ -Available collections: - -** FreeBSD: A full mirror of the FreeBSD FTP server. -** FreeBSD-Archive: The mirror of FreeBSD Archive FTP server. - -Sweden:: -rsync://ftp4.se.freebsd.org/ -+ --- -Available collections: - -** FreeBSD: A full mirror of the FreeBSD FTP server. --- -+ -{mirrors-sweden-ftp2-rsync} -+ -{mirrors-sweden-ftp4-rsync} -+ -{mirrors-sweden-ftp4-rsyncv6} - -Taiwan:: -rsync://ftp.tw.FreeBSD.org/ -+ -rsync://ftp2.tw.FreeBSD.org/ -+ -rsync://ftp6.tw.FreeBSD.org/ -+ -Available collections: - -** FreeBSD: A full mirror of the FreeBSD FTP server. - -Ukraine:: -{mirrors-ukraine-ftp6-rsync} - -United Kingdom:: -rsync://rsync.mirrorservice.org/ -+ --- -Available collections: - -** ftp.freebsd.org: A full mirror of the FreeBSD FTP server. --- -+ -{mirrors-uk-ftp2-rsync} - -United States of America:: -rsync://ftp-master.FreeBSD.org/ -+ -This server may only be used by FreeBSD primary mirror sites. -+ -Available collections: -+ --- -** FreeBSD: The master archive of the FreeBSD FTP server. -** acl: The FreeBSD master ACL list. --- -+ -rsync://ftp13.FreeBSD.org/ -+ -Available collections: - -** FreeBSD: A full mirror of the FreeBSD FTP server. - [[mirrors-cdrom]] == CD and DVD Sets FreeBSD CD and DVD sets are available from several online retailers: * FreeBSD Mall, Inc. + -2420 Sand Creek Rd C-1 #347 + +1164 Claremont Dr + Brentwood, CA + 94513 + USA + Phone: +1 925 240-6652 + Fax: +1 925 674-0821 + -Email: + +Email: info@freebsdmall.com + WWW: https://www.freebsdmall.com * Getlinux + -78 Rue de la Croix Rochopt + -Épinay-sous-Sénart + -91860 + -France + -Email: + -WWW: http://www.getlinux.fr/ +WWW: https://www.getlinux.fr/ * Dr. Hinner EDV + -Kochelseestr. 11 + +Schäftlarnstr. 10 // 4. Stock + D-81371 München + Germany + -Phone: (0177) 428 419 0 + -Email: + +Phone: +49 171 417 544 6 + +Email: infow@hinner.de + WWW: http://www.hinner.de/linux/freebsd.html diff --git a/shared/mirrors.adoc b/shared/mirrors.adoc index 96e75fe1f0..8f617d2c63 100644 --- a/shared/mirrors.adoc +++ b/shared/mirrors.adoc @@ -1,349 +1,351 @@ // $FreeBSD$ // Central servers :central-www: https://www.FreeBSD.org/ :central-ftp: ftp://ftp.FreeBSD.org/pub/FreeBSD/ :central-http: http://ftp.FreeBSD.org/pub/FreeBSD/ :central-httpv6: http://ftp.FreeBSD.org/pub/FreeBSD/ :central-cvsup: cvsup.FreeBSD.org :central: Central Servers // Primary Mirror Sites :mirrors-primary-ftp1: ftp://ftp1.FreeBSD.org/pub/FreeBSD/ :mirrors-primary-ftp2: ftp://ftp2.FreeBSD.org/pub/FreeBSD/ :mirrors-primary-ftp3: ftp://ftp3.FreeBSD.org/pub/FreeBSD/ :mirrors-primary-ftp4: ftp://ftp4.FreeBSD.org/pub/FreeBSD/ :mirrors-primary-ftp4-http: http://ftp4.FreeBSD.org/pub/FreeBSD/ :mirrors-primary-ftp4-httpv6: http://ftp4.FreeBSD.org/pub/FreeBSD/ :mirrors-primary-ftp5: ftp://ftp5.FreeBSD.org/pub/FreeBSD/ :mirrors-primary-ftp6: ftp://ftp6.FreeBSD.org/pub/FreeBSD/ :mirrors-primary-ftp7: ftp://ftp7.FreeBSD.org/pub/FreeBSD/ :mirrors-primary-ftp10: ftp://ftp10.FreeBSD.org/pub/FreeBSD/ :mirrors-primary-ftp10-http: http://ftp10.FreeBSD.org/pub/FreeBSD/ :mirrors-primary-ftp10-httpv6: http://ftp10.FreeBSD.org/pub/FreeBSD/ :mirrors-primary-ftp11: ftp://ftp11.FreeBSD.org/pub/FreeBSD/ :mirrors-primary-ftp13: ftp://ftp13.FreeBSD.org/pub/FreeBSD/ :mirrors-primary-ftp14: ftp://ftp14.FreeBSD.org/pub/FreeBSD/ :mirrors-primary-ftp14-http: http://ftp14.FreeBSD.org/pub/FreeBSD/ :mirrors-primary-email: mirror-admin@FreeBSD.org :mirrors-primary: Primary Mirror Sites // Armenia mirrors :mirrors-armenia-www-http: http://www1.am.FreeBSD.org/ :mirrors-armenia-www-httpv6: http://www1.am.FreeBSD.org/ :mirrors-armenia-ftp: ftp://ftp1.am.FreeBSD.org/pub/FreeBSD/ :mirrors-armenia-ftp-http: http://ftp1.am.FreeBSD.org/pub/FreeBSD/ :mirrors-armenia-email: hostmaster@am.FreeBSD.org :mirrors-armenia: Armenia // Australia mirrors :mirrors-australia-www-http: http://www.au.FreeBSD.org/ :mirrors-australia-www2-http: http://www2.au.FreeBSD.org/ :mirrors-australia-ftp: ftp://ftp.au.FreeBSD.org/pub/FreeBSD/ :mirrors-australia-ftp2: ftp://ftp2.au.FreeBSD.org/pub/FreeBSD/ :mirrors-australia-ftp3: ftp://ftp3.au.FreeBSD.org/pub/FreeBSD/ :mirrors-australia-email: hostmaster@au.FreeBSD.org :mirrors-australia: Australia // Austria mirrors :mirrors-armenia-www-http: http://www.at.FreeBSD.org/ :mirrors-armenia-www-httpv6: http://www.at.FreeBSD.org/ :mirrors-austria-ftp: ftp://ftp.at.FreeBSD.org/pub/FreeBSD/ :mirrors-austria-ftp-http: http://ftp.at.FreeBSD.org/pub/FreeBSD/ :mirrors-austria-ftp-httpv6: http://ftp.at.FreeBSD.org/pub/FreeBSD/ :mirrors-austria-email: hostmaster@at.FreeBSD.org :mirrors-austria: Austria // Brazil mirrors :mirrors-brazil-ftp2: ftp://ftp2.br.FreeBSD.org/FreeBSD/ :mirrors-brazil-ftp2-http: http://ftp2.br.FreeBSD.org/ :mirrors-brazil-ftp3: ftp://ftp3.br.FreeBSD.org/pub/FreeBSD/ :mirrors-brazil-ftp4: ftp://ftp4.br.FreeBSD.org/pub/FreeBSD/ :mirrors-brazil-email: hostmaster@br.FreeBSD.org :mirrors-brazil: Brazil :mirrors-bulgaria-ftp: ftp://ftp.bg.FreeBSD.org/pub/FreeBSD/ :mirrors-bulgaria-email: mirror@telepoint.bg :mirrors-bulgaria-rsync: rsync.bg.FreeBSD.org :mirrors-bulgaria: Bulgaria // Czech Republic mirrors :mirrors-czech-www-http: http://www.cz.FreeBSD.org/ :mirrors-czech-www-httpv6: http://www.cz.FreeBSD.org/ :mirrors-czech-ftp: ftp://ftp.cz.FreeBSD.org/pub/FreeBSD/ :mirrors-czech-ftpv6: ftp://ftp.cz.FreeBSD.org/pub/FreeBSD/ :mirrors-czech-ftp-http: http://ftp.cz.FreeBSD.org/pub/FreeBSD/ :mirrors-czech-ftp-httpv6: http://ftp.cz.FreeBSD.org/pub/FreeBSD/ :mirrors-czech-ftp2: ftp://ftp2.cz.FreeBSD.org/pub/FreeBSD/ :mirrors-czech-ftp2-http: http://ftp2.cz.FreeBSD.org/pub/FreeBSD/ :mirrors-czech-email: hostmaster@cz.FreeBSD.org :mirrors-czech: Czech Republic // Denmark mirrors :mirrors-denmark-www-http: http://www.dk.FreeBSD.org/ :mirrors-denmark-www-httpv6: http://www.dk.FreeBSD.org/ :mirrors-denmark-ftp: ftp://ftp.dk.FreeBSD.org/pub/FreeBSD/ :mirrors-denmark-ftp-http: http://ftp.dk.FreeBSD.org/pub/FreeBSD/ :mirrors-denmark-ftp-httpv6: http://ftp.dk.FreeBSD.org/pub/FreeBSD/ :mirrors-denmark-email: hostmaster@dk.FreeBSD.org :mirrors-denmark: Denmark // Estonia mirrors :mirrors-estonia-ftp: ftp://ftp.ee.FreeBSD.org/pub/FreeBSD/ :mirrors-estonia-email: hostmaster@ee.FreeBSD.org :mirrors-estonia: Estonia // Finland mirrors :mirrors-finland-www-http: http://www.fi.FreeBSD.org/ :mirrors-finland-ftp: ftp://ftp.fi.FreeBSD.org/pub/FreeBSD/ :mirrors-finland-email: hostmaster@fi.FreeBSD.org :mirrors-finland: Finland // France mirrors :mirrors-france-www-http: http://www1.fr.FreeBSD.org/ :mirrors-france-ftp: ftp://ftp.fr.FreeBSD.org/pub/FreeBSD/ :mirrors-france-ftp1: ftp://ftp1.fr.FreeBSD.org/pub/FreeBSD/ :mirrors-france-ftp1-http: http://ftp1.fr.FreeBSD.org/pub/FreeBSD/ :mirrors-france-ftp3: ftp://ftp3.fr.FreeBSD.org/pub/FreeBSD/ :mirrors-france-ftp5: ftp://ftp6.fr.FreeBSD.org/pub/FreeBSD/ :mirrors-france-ftp6: ftp://ftp6.fr.FreeBSD.org/pub/FreeBSD/ :mirrors-france-ftp7: ftp://ftp7.fr.FreeBSD.org/pub/FreeBSD/ :mirrors-france-ftp8: ftp://ftp8.fr.FreeBSD.org/pub/FreeBSD/ :mirrors-france-rsync: rsync1.fr.FreeBSD.org :mirrors-france-email: hostmaster@fr.FreeBSD.org :mirrors-france: France // Germany mirrors :mirrors-germany-www-http: http://www.de.FreeBSD.org/ :mirrors-germany-ftp: ftp://ftp.de.FreeBSD.org/pub/FreeBSD/ :mirrors-germany-ftp1: ftp://ftp1.de.FreeBSD.org/freebsd/ :mirrors-germany-ftp1-http: http://www1.de.FreeBSD.org/freebsd/ :mirrors-germany-ftp1-rsync: rsync://rsync3.de.FreeBSD.org/freebsd/ :mirrors-germany-ftp2: ftp://ftp2.de.FreeBSD.org/pub/FreeBSD/ :mirrors-germany-ftp2-http: http://ftp2.de.FreeBSD.org/pub/FreeBSD/ :mirrors-germany-ftp4: ftp://ftp4.de.FreeBSD.org/FreeBSD/ :mirrors-germany-ftp4-http: http://ftp4.de.FreeBSD.org/pub/FreeBSD/ :mirrors-germany-ftp5: ftp://ftp5.de.FreeBSD.org/pub/FreeBSD/ :mirrors-germany-ftp7: ftp://ftp7.de.FreeBSD.org/pub/FreeBSD/ :mirrors-germany-ftp7-http: http://ftp7.de.FreeBSD.org/pub/FreeBSD/ :mirrors-germany-email: de-bsd-hubs@de.FreeBSD.org :mirrors-germany: Germany // Greece mirrors :mirrors-greece-ftp: ftp://ftp.gr.FreeBSD.org/pub/FreeBSD/ :mirrors-greece-ftp2: ftp://ftp2.gr.FreeBSD.org/pub/FreeBSD/ :mirrors-greece-email: hostmaster@gr.FreeBSD.org :mirrors-greece: Greece // Hong Kong mirrors :mirrors-hongkong-www: http://www.hk.FreeBSD.org/ :mirrors-hongkong-ftp: ftp://ftp.hk.FreeBSD.org/pub/FreeBSD/ :mirrors-hongkong: Hong Kong // Ireland mirrors :mirrors-ireland-www: http://www.ie.FreeBSD.org/ :mirrors-ireland-ftp: ftp://ftp3.ie.FreeBSD.org/pub/FreeBSD/ :mirrors-ireland-email: hostmaster@ie.FreeBSD.org :mirrors-ireland: Ireland // Japan mirrors :mirrors-japan-www-http: http://www.jp.FreeBSD.org/www.FreeBSD.org/ :mirrors-japan-www-httpv6: http://www.jp.FreeBSD.org/www.FreeBSD.org/ :mirrors-japan-ftp: ftp://ftp.jp.FreeBSD.org/pub/FreeBSD/ :mirrors-japan-ftp2: ftp://ftp2.jp.FreeBSD.org/pub/FreeBSD/ :mirrors-japan-ftp3: ftp://ftp3.jp.FreeBSD.org/pub/FreeBSD/ :mirrors-japan-ftp4: ftp://ftp4.jp.FreeBSD.org/pub/FreeBSD/ :mirrors-japan-ftp5: ftp://ftp5.jp.FreeBSD.org/pub/FreeBSD/ :mirrors-japan-ftp6: ftp://ftp6.jp.FreeBSD.org/pub/FreeBSD/ :mirrors-japan-ftp7: ftp://ftp7.jp.FreeBSD.org/pub/FreeBSD/ :mirrors-japan-ftp8: ftp://ftp8.jp.FreeBSD.org/pub/FreeBSD/ :mirrors-japan-ftp9: ftp://ftp9.jp.FreeBSD.org/pub/FreeBSD/ -:mirrors-japan-email: hostmaster@ie.FreeBSD.org +:mirrors-japan-email: hostmaster@jp.FreeBSD.org :mirrors-japan: Japan // Korea mirrors :mirrors-korea-ftp: ftp://ftp.kr.FreeBSD.org/pub/FreeBSD/ :mirrors-korea-ftp2: ftp://ftp2.kr.FreeBSD.org/pub/FreeBSD/ :mirrors-korea-ftp2-http: http://ftp2.kr.FreeBSD.org/pub/FreeBSD/ :mirrors-korea-email: hostmaster@kr.FreeBSD.org :mirrors-korea: Korea // Latvia mirrors :mirrors-latvia-www: http://www.lv.FreeBSD.org/ :mirrors-latvia-ftp: ftp://ftp.lv.FreeBSD.org/pub/FreeBSD/ :mirrors-latvia-ftp-http: http://ftp.lv.FreeBSD.org/pub/FreeBSD/ :mirrors-latvia-email: hostmaster@lv.FreeBSD.org :mirrors-latvia: Latvia // Lithuania mirrors :mirrors-lithuania-www: http://www.lt.FreeBSD.org/ :mirrors-lithuania-ftp: ftp://ftp.lt.FreeBSD.org/pub/FreeBSD/ :mirrors-lithuania-ftp-http: http://ftp.lt.FreeBSD.org/pub/FreeBSD/ :mirrors-lithuania-email: hostmaster@lt.FreeBSD.org :mirrors-lithuania: Lithuania // Netherlands mirrors :mirrors-netherlands-www: http://www.nl.FreeBSD.org/ :mirrors-netherlands-ftp: ftp://ftp.nl.FreeBSD.org/pub/FreeBSD/ :mirrors-netherlands-ftp-http: http://ftp.nl.FreeBSD.org/os/FreeBSD/ :mirrors-netherlands-ftp2: ftp://ftp2.nl.FreeBSD.org/pub/FreeBSD/ :mirrors-netherlands-email: hostmaster@nl.FreeBSD.org :mirrors-netherlands: Netherlands // New Zealand mirrors :mirrors-new-zealand-ftp: ftp://ftp.nz.FreeBSD.org/pub/FreeBSD/ :mirrors-new-zealand-ftp-http: http://ftp.nz.FreeBSD.org/pub/FreeBSD/ +:mirrors-new-zealand-email: hostmaster@nz.FreeBSD.org :mirrors-new-zealand: New Zealand // Norway mirrors :mirrors-norway-www: http://www.no.FreeBSD.org/ :mirrors-norway-ftp: ftp://ftp.no.FreeBSD.org/pub/FreeBSD/ :mirrors-norway-email: hostmaster@no.FreeBSD.org :mirrors-norway: Norway // Poland mirrors :mirrors-poland-ftp: ftp://ftp.pl.FreeBSD.org/pub/FreeBSD/ //:mirrors-poland-ftp2: http://ftp2.pl.FreeBSD.org/pub/FreeBSD/ //:mirrors-poland-ftp2-http: http://ftp2.pl.FreeBSD.org/pub/FreeBSD/ :mirrors-poland-email: hostmaster@pl.FreeBSD.org :mirrors-poland: Poland // Russia mirrors :mirrors-russia-www: http://www.ru.FreeBSD.org/ :mirrors-russia-www-httpv6: http://www.ru.FreeBSD.org/ :mirrors-russia-ftp: ftp://ftp.ru.FreeBSD.org/pub/FreeBSD/ :mirrors-russia-ftp-http: http://ftp.ru.FreeBSD.org/FreeBSD/ :mirrors-russia-ftp2: ftp://ftp2.ru.FreeBSD.org/pub/FreeBSD/ :mirrors-russia-ftp2-http: http://ftp2.ru.FreeBSD.org/pub/FreeBSD/ :mirrors-russia-ftp5: ftp://ftp5.ru.FreeBSD.org/pub/FreeBSD/ :mirrors-russia-ftp5-http: http://ftp5.ru.FreeBSD.org/pub/FreeBSD/ :mirrors-russia-ftp6: ftp://ftp6.ru.FreeBSD.org/pub/FreeBSD/ :mirrors-russia-email: hostmaster@ru.FreeBSD.org :mirrors-russia: Russia // Saudi Arabia mirrors :mirrors-saudi-arabia-ftp: ftp://ftp.isu.net.sa/pub/ftp.freebsd.org :mirrors-saudi-arabia-email: ftpadmin@isu.net.sa :mirrors-saudi-arabia: Saudi Arabia // Slovenia mirrors :mirrors-slovenia-www: http://www.si.FreeBSD.org/ :mirrors-slovenia-ftp: ftp://ftp.si.FreeBSD.org/pub/FreeBSD/ :mirrors-slovenia-email: hostmaster@si.FreeBSD.org :mirrors-slovenia: Slovenia // South Africa mirrors :mirrors-south-africa-www: http://www.za.FreeBSD.org/ :mirrors-south-africa-ftp: ftp://ftp.za.FreeBSD.org/pub/FreeBSD/ :mirrors-south-africa-ftp2: ftp://ftp2.za.FreeBSD.org/pub/FreeBSD/ :mirrors-south-africa-ftp4: ftp://ftp4.za.FreeBSD.org/pub/FreeBSD/ :mirrors-south-africa-email: hostmaster@za.FreeBSD.org :mirrors-south-africa: South Africa // Spain mirrors :mirrors-spain-www: http://www.es.FreeBSD.org/ :mirrors-spain-www2: http://www2.es.FreeBSD.org/ :mirrors-spain-ftp: ftp://ftp.es.FreeBSD.org/pub/FreeBSD/ :mirrors-spain-ftp-http: http://ftp.es.FreeBSD.org/pub/FreeBSD/ :mirrors-spain-ftp3: ftp://ftp3.es.FreeBSD.org/pub/FreeBSD/ :mirrors-spain-email: hostmaster@es.FreeBSD.org :mirrors-spain: Spain // Sweden mirrors :mirrors-sweden-www: http://www.se.FreeBSD.org/ :mirrors-sweden-ftp: ftp://ftp.se.FreeBSD.org/pub/FreeBSD/ :mirrors-sweden-ftp2: ftp://ftp2.se.FreeBSD.org/pub/FreeBSD/ :mirrors-sweden-ftp2-rsync: rsync://ftp2.se.FreeBSD.org/ :mirrors-sweden-ftp3: ftp://ftp3.se.FreeBSD.org/pub/FreeBSD/ :mirrors-sweden-ftp4: ftp://ftp4.se.FreeBSD.org/pub/FreeBSD/ :mirrors-sweden-ftp4v6: ftp://ftp4.se.FreeBSD.org/pub/FreeBSD/ :mirrors-sweden-ftp4-http: http://ftp4.se.FreeBSD.org/pub/FreeBSD/ :mirrors-sweden-ftp4-httpv6: http://ftp4.se.FreeBSD.org/pub/FreeBSD/ :mirrors-sweden-ftp4-rsync: rsync://ftp4.se.FreeBSD.org/pub/FreeBSD/ :mirrors-sweden-ftp4-rsyncv6: rsync://ftp4.se.FreeBSD.org/pub/FreeBSD/ :mirrors-sweden-ftp6: ftp://ftp6.se.FreeBSD.org/pub/FreeBSD/ :mirrors-sweden-ftp6-http: http://ftp6.se.FreeBSD.org/pub/FreeBSD/ :mirrors-sweden-email: hostmaster@se.FreeBSD.org :mirrors-sweden: Sweden // Switzerland mirrors :mirrors-switzerland-www: http://www.ch.FreeBSD.org/ :mirrors-switzerland-www-httpv6: http://www.ch.FreeBSD.org/ :mirrors-switzerland-www2: http://www2.ch.FreeBSD.org/ :mirrors-switzerland-www2-httpv6: http://www2.ch.FreeBSD.org/ :mirrors-switzerland-ftp: ftp://ftp.ch.FreeBSD.org/pub/FreeBSD/ :mirrors-switzerland-ftp-http: http://ftp.ch.FreeBSD.org/pub/FreeBSD/ :mirrors-switzerland-email: hostmaster@ch.FreeBSD.org :mirrors-switzerland: Switzerland // Taiwan mirrors :mirrors-taiwan-www: http://www.tw.FreeBSD.org/ :mirrors-taiwan-www2: http://www2.tw.FreeBSD.org/ :mirrors-taiwan-www4: http://www4.tw.FreeBSD.org/ :mirrors-taiwan-www5: http://www5.tw.FreeBSD.org/ :mirrors-taiwan-www5-httpv6: http://www5.tw.FreeBSD.org/ :mirrors-taiwan-ftp: ftp://ftp.tw.FreeBSD.org/pub/FreeBSD/ :mirrors-taiwan-ftpv6: ftp://ftp.tw.FreeBSD.org/pub/FreeBSD/ :mirrors-taiwan-ftp2: ftp://ftp2.tw.FreeBSD.org/pub/FreeBSD/ :mirrors-taiwan-ftp2v6: ftp://ftp2.tw.FreeBSD.org/pub/FreeBSD/ :mirrors-taiwan-ftp2-http: http://ftp2.tw.FreeBSD.org/pub/FreeBSD/ :mirrors-taiwan-ftp2-httpv6: http://ftp2.tw.FreeBSD.org/pub/FreeBSD/ :mirrors-taiwan-ftp4: ftp://ftp4.tw.FreeBSD.org/pub/FreeBSD/ :mirrors-taiwan-ftp5: ftp://ftp5.tw.FreeBSD.org/pub/FreeBSD/ :mirrors-taiwan-ftp6: ftp://ftp6.tw.FreeBSD.org/pub/FreeBSD/ :mirrors-taiwan-ftp6v6: http://ftp6.tw.FreeBSD.org/ :mirrors-taiwan-ftp7: ftp://ftp7.tw.FreeBSD.org/pub/FreeBSD/ :mirrors-taiwan-ftp8: ftp://ftp8.tw.FreeBSD.org/pub/FreeBSD/ :mirrors-taiwan-ftp11: ftp://ftp11.tw.FreeBSD.org/pub/FreeBSD/ :mirrors-taiwan-ftp11-http: http://ftp11.tw.FreeBSD.org/FreeBSD/ :mirrors-taiwan-ftp12: ftp://ftp12.tw.FreeBSD.org/pub/FreeBSD/ :mirrors-taiwan-ftp13: ftp://ftp13.tw.FreeBSD.org/pub/FreeBSD/ :mirrors-taiwan-ftp14: ftp://ftp14.tw.FreeBSD.org/pub/FreeBSD/ :mirrors-taiwan-ftp15: ftp://ftp15.tw.FreeBSD.org/pub/FreeBSD/ :mirrors-taiwan-ftp: ftp://ftp.ch.FreeBSD.org/pub/FreeBSD/ :mirrors-taiwan-ftp-http: http://ftp.ch.FreeBSD.org/pub/FreeBSD/ :mirrors-taiwan-email: hostmaster@tw.FreeBSD.org :mirrors-taiwan: Taiwan // Ukraine mirrors :mirrors-ukraine-ftp: ftp://ftp.ua.FreeBSD.org/pub/FreeBSD/ :mirrors-ukraine-ftp-http: http://ftp.ua.FreeBSD.org/pub/FreeBSD/ :mirrors-ukraine-ftp6: ftp://ftp6.ua.FreeBSD.org/pub/FreeBSD/ :mirrors-ukraine-ftp6-http: http://ftp6.ua.FreeBSD.org/pub/FreeBSD :mirrors-ukraine-ftp6-rsync: rsync://ftp6.ua.FreeBSD.org/FreeBSD/ :mirrors-ukraine-ftp7: ftp://ftp7.ua.FreeBSD.org/pub/FreeBSD/ +:mirrors-ukraine-email: hostmaster@ua.FreeBSD.org :mirrors-ukraine: Ukraine // United Kingdom mirrors :mirrors-uk-www: http://www1.uk.FreeBSD.org :mirrors-uk-www3: http://www3.uk.FreeBSD.org/ :mirrors-uk-ftp: ftp://ftp.uk.FreeBSD.org/pub/FreeBSD/ :mirrors-uk-ftp2: ftp://ftp2.uk.FreeBSD.org/pub/FreeBSD/ :mirrors-uk-ftp2-rsync: rsync://ftp2.uk.FreeBSD.org/ftp.freebsd.org/pub/FreeBSD/ :mirrors-uk-ftp3: ftp://ftp3.uk.FreeBSD.org/pub/FreeBSD/ :mirrors-uk-ftp4: ftp://ftp4.uk.FreeBSD.org/pub/FreeBSD/ :mirrors-uk-ftp5: ftp://ftp5.uk.FreeBSD.org/pub/FreeBSD/ :mirrors-uk-email: hostmaster@uk.FreeBSD.org :mirrors-uk: United Kingdom // USA mirrors :mirrors-us-www5: http://www5.us.FreeBSD.org/ :mirrors-us-www5-httpv6: http://www5.us.FreeBSD.org/ :mirrors-us-ftp: ftp://ftp1.us.FreeBSD.org/pub/FreeBSD/ :mirrors-us-ftp2: ftp://ftp2.us.FreeBSD.org/pub/FreeBSD/ :mirrors-us-ftp3: ftp://ftp3.us.FreeBSD.org/pub/FreeBSD/ :mirrors-us-ftp4: ftp://ftp4.us.FreeBSD.org/pub/FreeBSD/ :mirrors-us-ftp4-http: http://ftp4.us.FreeBSD.org/pub/FreeBSD/ :mirrors-us-ftp4-httpv6: http://ftp4.us.FreeBSD.org/pub/FreeBSD/ :mirrors-us-ftp5: ftp://ftp5.us.FreeBSD.org/pub/FreeBSD/ :mirrors-us-ftp6: ftp://ftp6.us.FreeBSD.org/pub/FreeBSD/ :mirrors-us-ftp8: ftp://ftp8.us.FreeBSD.org/pub/FreeBSD/ :mirrors-us-ftp10: ftp://ftp10.us.FreeBSD.org/pub/FreeBSD/ :mirrors-us-ftp11: ftp://ftp11.us.FreeBSD.org/pub/FreeBSD/ :mirrors-us-ftp13: ftp://ftp13.us.FreeBSD.org/pub/FreeBSD/ :mirrors-us-ftp13-http: http://ftp13.us.FreeBSD.org/pub/FreeBSD/ :mirrors-us-ftp14: ftp://ftp14.us.FreeBSD.org/pub/FreeBSD/ :mirrors-us-ftp14-http: http://ftp14.us.FreeBSD.org/pub/FreeBSD/ :mirrors-us-ftp15: ftp://ftp15.us.FreeBSD.org/pub/FreeBSD/ :mirrors-us-email: hostmaster@us.FreeBSD.org :mirrors-us: United States of America