Changeset View
Changeset View
Standalone View
Standalone View
documentation/content/en/books/faq/_index.adoc
| Show All 15 Lines | |||||
| :toclevels: 1 | :toclevels: 1 | ||||
| :icons: font | :icons: font | ||||
| :sectnums: | :sectnums: | ||||
| :sectnumlevels: 6 | :sectnumlevels: 6 | ||||
| :partnums: | :partnums: | ||||
| :source-highlighter: rouge | :source-highlighter: rouge | ||||
| :experimental: | :experimental: | ||||
| :images-path: books/faq/ | :images-path: books/faq/ | ||||
| :rel-numbranch: 4 | :rel-numbranch: 3 | ||||
| :rel-head: 14-CURRENT | :rel-head: 14-CURRENT | ||||
| :rel-head-relx: 14.X | :rel-head-relx: 14.X | ||||
| :rel-head-releng: head/ | :rel-head-releng: main | ||||
| :rel-relx: 13.X | :rel-relx: 13.X | ||||
| :rel-stable: 13-STABLE | :rel-stable: 13-STABLE | ||||
| :rel-releng: stable/13/ | :rel-releng: stable/13 | ||||
| :rel-relengdate: December 2018 | :rel-relengdate: January 2021 | ||||
| :rel2-relx: 12.X | :rel2-relx: 12.X | ||||
| :rel2-stable: 12-STABLE | :rel2-stable: 12-STABLE | ||||
| :rel2-releng: stable/12/ | :rel2-releng: stable/12 | ||||
| :rel2-relengdate: December 2018 | :rel2-relengdate: December 2018 | ||||
| ifdef::env-beastie[] | ifdef::env-beastie[] | ||||
| ifdef::backend-html5[] | ifdef::backend-html5[] | ||||
| include::shared/authors.adoc[] | include::shared/authors.adoc[] | ||||
| include::shared/mirrors.adoc[] | include::shared/mirrors.adoc[] | ||||
| include::shared/releases.adoc[] | include::shared/releases.adoc[] | ||||
| include::shared/attributes/attributes-{{% lang %}}.adoc[] | include::shared/attributes/attributes-{{% lang %}}.adoc[] | ||||
| ▲ Show 20 Lines • Show All 165 Lines • ▼ Show 20 Lines | |||||
| [[snapshot-freq]] | [[snapshot-freq]] | ||||
| === When are FreeBSD snapshots made? | === When are FreeBSD snapshots made? | ||||
| FreeBSD link:https://www.FreeBSD.org/snapshots/[snapshot] releases are made based on the current state of the _-CURRENT_ and _-STABLE_ branches. | FreeBSD link:https://www.FreeBSD.org/snapshots/[snapshot] releases are made based on the current state of the _-CURRENT_ and _-STABLE_ branches. | ||||
| The goals behind each snapshot release are: | The goals behind each snapshot release are: | ||||
| * To test the latest version of the installation software. | * To test the latest version of the installation software. | ||||
| * To give people who would like to run _-CURRENT_ or _-STABLE_ but who do not have the time or bandwidth to follow it on a day-to-day basis an easy way of bootstrapping it onto their systems. | * To give people who would like to run _-CURRENT_ or _-STABLE_ but who do not have the time or bandwidth to follow it on a day-to-day basis an easy way of bootstrapping it onto their systems. | ||||
| * To preserve a fixed reference point for the code in question, just in case we break something really badly later. | * To preserve a fixed reference point for the code in question, just in case we break something really badly later. | ||||
| (Although Subversion normally prevents anything horrible like this happening.) | (Although Git normally prevents anything horrible like this happening.) | ||||
emaste: Probably this entire bullet point should just be removed. | |||||
| * To ensure that all new features and fixes in need of testing have the greatest possible number of potential testers. | * To ensure that all new features and fixes in need of testing have the greatest possible number of potential testers. | ||||
| No claims are made that any _-CURRENT_ snapshot can be considered "production quality" for any purpose. | No claims are made that any _-CURRENT_ snapshot can be considered "production quality" for any purpose. | ||||
| If a stable and fully tested system is needed, stick to full releases. | If a stable and fully tested system is needed, stick to full releases. | ||||
| Snapshot releases are directly available from link:https://www.FreeBSD.org/snapshots/[snapshot]. | Snapshot releases are directly available from link:https://www.FreeBSD.org/snapshots/[snapshot]. | ||||
| Official snapshots are generated on a regular basis for all actively developed branches. | Official snapshots are generated on a regular basis for all actively developed branches. | ||||
| ▲ Show 20 Lines • Show All 1,609 Lines • ▼ Show 20 Lines | |||||
| Part of this process is a code freeze. | Part of this process is a code freeze. | ||||
| When a code freeze is initiated, the name of the branch is changed to reflect that it is about to become a release. | When a code freeze is initiated, the name of the branch is changed to reflect that it is about to become a release. | ||||
| For example, if the branch used to be called 6.2-STABLE, its name will be changed to 6.3-PRERELEASE to signify the code freeze and signify that extra pre-release testing should be happening. | For example, if the branch used to be called 6.2-STABLE, its name will be changed to 6.3-PRERELEASE to signify the code freeze and signify that extra pre-release testing should be happening. | ||||
| Bug fixes can still be committed to be part of the release. | Bug fixes can still be committed to be part of the release. | ||||
| When the source code is in shape for the release the name will be changed to 6.3-RC to signify that a release is about to be made from it. | When the source code is in shape for the release the name will be changed to 6.3-RC to signify that a release is about to be made from it. | ||||
| Once in the RC stage, only the most critical bugs found can be fixed. | Once in the RC stage, only the most critical bugs found can be fixed. | ||||
| Once the release (6.3-RELEASE in this example) and release branch have been made, the branch will be renamed to 6.3-STABLE. | Once the release (6.3-RELEASE in this example) and release branch have been made, the branch will be renamed to 6.3-STABLE. | ||||
| For more information on version numbers and the various Subversion branches, refer to the extref:{releng}[Release Engineering] article. | For more information on version numbers and the various Git branches, refer to the extref:{releng}[Release Engineering] article. | ||||
Done Inline ActionsOf course the releng article also needs an update. emaste: Of course the releng article also needs an update. | |||||
| [[kernel-chflag-failure]] | [[kernel-chflag-failure]] | ||||
| === I tried to install a new kernel, and the man:chflags[1] failed. How do I get around this? | === I tried to install a new kernel, and the man:chflags[1] failed. How do I get around this? | ||||
| Short answer: the security level is greater than 0. | Short answer: the security level is greater than 0. | ||||
| Reboot directly to single-user mode to install the kernel. | Reboot directly to single-user mode to install the kernel. | ||||
| Long answer: FreeBSD disallows changing system flags at security levels greater than 0. | Long answer: FreeBSD disallows changing system flags at security levels greater than 0. | ||||
| ▲ Show 20 Lines • Show All 1,146 Lines • ▼ Show 20 Lines | |||||
| We accept all types of contributions: documentation, code, and even art. | We accept all types of contributions: documentation, code, and even art. | ||||
| See the article on extref:{contributing}[Contributing to FreeBSD] for specific advice on how to do this. | See the article on extref:{contributing}[Contributing to FreeBSD] for specific advice on how to do this. | ||||
| And thanks for the thought! | And thanks for the thought! | ||||
| [[define-snap-release]] | [[define-snap-release]] | ||||
| === What are snapshots and releases? | === What are snapshots and releases? | ||||
| There are currently {rel-numbranch} active/semi-active branches in the FreeBSD http://svnweb.FreeBSD.org/base/[Subversion Repository]. | There are currently {rel-numbranch} active/semi-active branches in the FreeBSD http://cgit.FreeBSD.org/src/[Git Repository]. | ||||
| (Earlier branches are only changed very rarely, which is why there are only {rel-numbranch} active branches of development): | (Earlier branches are only changed very rarely, which is why there are only {rel-numbranch} active branches of development): | ||||
| * {rel2-releng} AKA {rel2-stable} | * {rel2-releng} AKA {rel2-stable} | ||||
| * {rel-releng} AKA {rel-stable} | * {rel-releng} AKA {rel-stable} | ||||
| * {rel-head-releng} AKA _-CURRENT_ AKA {rel-head} | * {rel-head-releng} AKA _-CURRENT_ AKA {rel-head} | ||||
| `HEAD` is not an actual branch tag. | |||||
| It is a symbolic constant for the current, non-branched development stream known as _-CURRENT_. | |||||
| Right now, _-CURRENT_ is the {rel-head-relx} development stream; the {rel-stable} branch, {rel-releng}, forked off from _-CURRENT_ in {rel-relengdate} and the {rel2-stable} branch, {rel2-releng}, forked off from _-CURRENT_ in {rel2-relengdate}. | Right now, _-CURRENT_ is the {rel-head-relx} development stream; the {rel-stable} branch, {rel-releng}, forked off from _-CURRENT_ in {rel-relengdate} and the {rel2-stable} branch, {rel2-releng}, forked off from _-CURRENT_ in {rel2-relengdate}. | ||||
| [[kernel-panic-troubleshooting]] | [[kernel-panic-troubleshooting]] | ||||
| === How can I make the most of the data I see when my kernel panics? | === How can I make the most of the data I see when my kernel panics? | ||||
| Here is typical kernel panic: | Here is typical kernel panic: | ||||
| ▲ Show 20 Lines • Show All 167 Lines • Show Last 20 Lines | |||||
Probably this entire bullet point should just be removed.