Translation

Back when FreeBSD 2.0.5 was released, FreeBSD development branched in two. One branch was named <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/current-stable.html#stable">-STABLE</link>, one <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/current-stable.html#current">-CURRENT</link>. <emphasis>FreeBSD-STABLE</emphasis> is the development branch from which major releases are made. Changes go into this branch at a slower pace and with the general assumption that they have first been tested in FreeBSD-CURRENT. However, at any given time, the sources for FreeBSD-STABLE may or may not be suitable for general use, as it may uncover bugs and corner cases that were not yet found in FreeBSD-CURRENT. Users who do not have the resources to perform testing should instead run the most recent release of FreeBSD. <emphasis>FreeBSD-CURRENT</emphasis>, on the other hand, has been one unbroken line since 2.0 was released, leading towards 12.0-RELEASE and beyond. For more detailed information on branches see <quote><link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/releng/release-proc.html#rel-branch">FreeBSD Release Engineering: Creating the Release Branch</link></quote>, the status of the branches and the upcoming release schedule can be found on the <link xlink:href="https://www.FreeBSD.org/releng">Release Engineering Information</link> page.
(itstool) path: answer/para
<emphasis>FreeBSD-STABLE</emphasis> is the development branch from which major releases are made. Changes go into this branch at a slower pace and with the general assumption that they have first been tested in FreeBSD-CURRENT. However, at any given time, the sources for FreeBSD-STABLE may or may not be suitable for general use, as it may uncover bugs and corner cases that were not yet found in FreeBSD-CURRENT. Users who do not have the resources to perform testing should instead run the most recent release of FreeBSD. <emphasis>FreeBSD-CURRENT</emphasis>, on the other hand, has been one unbroken line since 2.0 was released.
1408/6320
Context English Norwegian Bokmål State
James Howard wrote a good explanation of the history and differences between the various projects, called <link xlink:href="https://jameshoward.us/archive/the-bsd-family-tree/">The BSD Family Tree</link> which goes a fair way to answering this question. Some of the information is out of date, but the history portion in particular remains accurate.
James Howard skrev en god forklaring rundt historien til de forskjellige prosjektene, dette ble kalt for <link xlink:href="https://jameshoward.us/archive/the-bsd-family-tree/">The BSD Family Tree</link> (BSD Familietreet) som tar for seg å svare på dette.
Noe av informasjonen har gått litt ut på dato men historien rundt de forskjellige utgivelsene virker til å fortsatt være korrekt.
Most of the BSDs share patches and code, even today. All of the BSDs have common ancestry.
De fleste av BSD'ene deler oppdateringer og kode selv i disse dager. Alle BSD-utgivelsene har samme historikk bak seg.
The design goals of FreeBSD are described in <xref linkend="FreeBSD-goals"/>, above. The design goals of the other most popular BSDs may be summarized as follows:
Målet med FreeBSD er nevnt i <xref linkend="FreeBSD-goals"/>, ovenfor. Målet med de forskjellige BSD-utgivelsene kan oppsummeres som følgende:
OpenBSD aims for operating system security above all else. The OpenBSD team wrote <citerefentry><refentrytitle>ssh</refentrytitle><manvolnum>1</manvolnum></citerefentry> and <citerefentry><refentrytitle>pf</refentrytitle><manvolnum>4</manvolnum></citerefentry>, which have both been ported to FreeBSD.
OpenBSD satser først og fremst på sikkerhet. Dette er prioritet nr. 1. OpenBSD teamet skrev <citerefentry><refentrytitle>ssh</refentrytitle><manvolnum>1</manvolnum></citerefentry> og <citerefentry><refentrytitle>pf</refentrytitle><manvolnum>4</manvolnum></citerefentry> som begge har blitt portet over til FreeBSD.
NetBSD aims to be easily ported to other hardware platforms.
NetBSD har som mål å bli enkelt portet over til andre plattformer.
DragonFly BSD is a fork of FreeBSD 4.8 that has since developed many interesting features of its own, including the HAMMER file system and support for user-mode <quote>vkernels</quote>.
DragonFLY BSD er en utvidelse av FreeBSD 4.8 som siden har blitt utviklet med mange interessante egne funksjoner, inkludert deres eget filsystem HAMMER og støtte for bruker-modus <quote>vkernels</quote>.
What is the latest version of FreeBSD?
Hva er siste versjon av FreeBSD?
At any point in the development of FreeBSD, there can be multiple parallel branches. 12.<replaceable>X</replaceable> releases are made from the <emphasis>12-STABLE</emphasis> branch, and 11.<replaceable>X</replaceable> releases are made from the <emphasis>11-STABLE</emphasis> branch.
Når som helst i utviklingen av FreeBSD så kan det være flere forskjellige "greiner". 12.<replaceable>X</replaceable> utgivelser er utgitt fra <emphasis>12-STABLE</emphasis> grenen og 11.<replaceable>X</replaceable> utgivelsene fra <emphasis>11-STABLE</emphasis> grenen.
Up until the release of 12.0, the 11.<replaceable>X</replaceable> series was the one known as <emphasis>-STABLE</emphasis>. However, as of 13.<replaceable>X</replaceable>, the 11.<replaceable>X</replaceable> branch will be designated for an <quote>extended support</quote> status and receive only fixes for major problems, such as security-related fixes.
Inntil utgivelsen av 9.0 så var 11.<replaceable>X</replaceable> serien navngitt som <emphasis>-STABLE</emphasis>. Uansett, fra 13.<replaceable>X</replaceable> så vil 11.<replaceable>X</replaceable> grenen bli utgitt for <quote>utvidet support</quote> status og vil kun få oppdateringer for store problemer som sikkerhets relaterte problemer
Releases are made <link linkend="release-freq">every few months</link>. While many people stay more up-to-date with the FreeBSD sources (see the questions on <link linkend="current">FreeBSD-CURRENT</link> and <link linkend="stable">FreeBSD-STABLE</link>) than that, doing so is more of a commitment, as the sources are a moving target.
Utgivelser kommer med <link linkend="release-freq">noen få måneders</link> mellomrom. Selvom mange liker å være "up-to-date" med FreeBSD kilder (see spørsmål på <link linkend="current">FreeBSD-CURRENT</link> og <link linkend="stable">FreeBSD-STABLE</link>) så det å gjøre dette er mer en slags plikt ettersom kilder stadig beveger seg videre.
More information on FreeBSD releases can be found on the <link xlink:href="https://www.FreeBSD.org/releng/index.html#release-build">Release Engineering page</link> and in <citerefentry><refentrytitle>release</refentrytitle><manvolnum>7</manvolnum></citerefentry>.
Mer informasjon om FreeBSD utgivelser kan sjekkes ut på <link xlink:href="https://www.FreeBSD.org/releng/index.html#release-build">Release Engineering page</link> og i <citerefentry><refentrytitle>release</refentrytitle><manvolnum>7</manvolnum></citerefentry>.
What is <emphasis>FreeBSD-CURRENT</emphasis>?
Hva er <emphasis>FreeBSD-CURRENT</emphasis>?
<link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/current-stable.html#current">FreeBSD-CURRENT</link> is the development version of the operating system, which will in due course become the new FreeBSD-STABLE branch. As such, it is really only of interest to developers working on the system and die-hard hobbyists. See the <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/current-stable.html#current">relevant section</link> in the <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/index.html">Handbook</link> for details on running <emphasis>-CURRENT</emphasis>.
<link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/current-stable.html#current">FreeBSD-CURRENT</link> er den grenen som er kontinuerlig under utvikling innenfor operativ systemet. -CURRENT vil etterhvert som tiden går bli gitt ut som ny FreeBSD-stable gren. FreeBSD-CURRENT er mest for de som liker å utvikle og die-hard hobbyists. Sjekk ut <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/current-stable.html#current">relevant section</link> i <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/index.html">Handbook</link> for detaljer om å kjøre <emphasis>-CURRENT</emphasis>.
Users not familiar with FreeBSD should not use FreeBSD-CURRENT. This branch sometimes evolves quite quickly and due to mistake can be un-buildable at times. People that use FreeBSD-CURRENT are expected to be able to analyze, debug, and report problems.
Brukere som ikke er kjent med FreeBSD bør ikke bruke FreeBSD-CURRENT. Denne grenen av FreeBSD er stadig under utvikling og kan plutselig kræsje ved anledninger. Folk som bruker FreeBSD-CURRENT bør være kjent med analysering, debugging og vite hvordan man rapporter problemer.
What is the <emphasis>FreeBSD-STABLE</emphasis> concept?
Hva er <emphasis>FreeBSD-STABLE</emphasis> konseptet?
<emphasis>FreeBSD-STABLE</emphasis> is the development branch from which major releases are made. Changes go into this branch at a slower pace and with the general assumption that they have first been tested in FreeBSD-CURRENT. However, at any given time, the sources for FreeBSD-STABLE may or may not be suitable for general use, as it may uncover bugs and corner cases that were not yet found in FreeBSD-CURRENT. Users who do not have the resources to perform testing should instead run the most recent release of FreeBSD. <emphasis>FreeBSD-CURRENT</emphasis>, on the other hand, has been one unbroken line since 2.0 was released.
Tilbake i sin tid når FreeBSD 2.0.5 ble utgitt, ble FreeBSD utviklings grenene delt i to.
En gren ble navngitt <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/current-stable.html#stable">-STABLE</link> og en annen <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/current-stable.html#current">-CURRENT</link>. <emphasis>FreeBSD-STABLE</emphasis> er utviklings grenen som de større utgivelsene grener utifra.
Endringer inn i denne grenen går over et lenger tidsperspektiv i et saktere tempo. Det blir også tatt høyde for at disse endringene først er testet i FreeBSD-CURRENT. Uansett tid eller dato så kan FreeBSD-STABLE både være anvendelig eller ikke for generelt bruk ettersom det kan være feil/bugs og enkelte tilfeller som ikke ennå har blitt oppdaget i FreeBSD-CURRENT.
Brukere som ikke har ressursene til å teste dette burde heller benytte seg av nyeste utgivelse av FeeeBSD. <emphasis>FreeBSD-CURRENT</emphasis> har vært komplett siden 2.0 var utgitt til 12.0-RELEASE og videre.
For mer detaljert informasjon om grener sjekk ut: <quote><link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/releng/release-proc.html#rel-branch">FreeBSD Release Engineering: Creating the Release Branch</link></quote> , stats av grener og kommende utgivelser finnes på: <link xlink:href="https://www.FreeBSD.org/releng">Release Engineering Information</link> siden.
For more detailed information on branches see <quote><link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/releng/release-proc.html#rel-branch">FreeBSD Release Engineering: Creating the Release Branch</link></quote>, the status of the branches and the upcoming release schedule can be found on the <link xlink:href="https://www.FreeBSD.org/releng">Release Engineering Information</link> page.
For mer detaljert informasjon om utgreininger se <quote><link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/releng/release-proc.html#rel-branch">FreeBSD Release Engineering: Creating the Release Branch</link></quote>, status av greiner og kommende utgivelsesplan kan finnes her <link xlink:href="https://www.FreeBSD.org/releng">Release Engineering Information</link> .
Version <link xlink:href="https://download.FreeBSD.org/ftp/releases/amd64/amd64/12.1-RELEASE/">12.1</link> is the latest release from the <emphasis>12-STABLE</emphasis> branch; it was released in November 2019. Version <link xlink:href="https://download.FreeBSD.org/ftp/releases/amd64/amd64/11.3-RELEASE/">11.3</link> is the latest release from the <emphasis>11-STABLE</emphasis> branch; it was released in July 2019.
Versjon <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/i386/12.0-RELEASE/">12.0</link> er den siste utgivelsen fra <emphasis>12-STABLE</emphasis> grenen; 12.0 ble utgitt Desember 2018. Versjon <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/10.4-RELEASE/">10.4</link> er den siste utgivelsen fra <emphasis>11-STABLE</emphasis>; 10.4 var utgitt Oktober 2017.
When are FreeBSD releases made?
Når blir FreeBSD utgivelser laget?
The Release Engineering Team <email>re@FreeBSD.org</email> releases a new major version of FreeBSD about every 18 months and a new minor version about every 8 months, on average. Release dates are announced well in advance, so that the people working on the system know when their projects need to be finished and tested. A testing period precedes each release, to ensure that the addition of new features does not compromise the stability of the release. Many users regard this caution as one of the best things about FreeBSD, even though waiting for all the latest goodies to reach <emphasis>-STABLE</emphasis> can be a little frustrating.
The Release Engineering Team <email>re@FreeBSD.org</email> gir ut en ny stor versjon av FreeBSD ca hver 18 måned og en ny mindre versjon ca hver 8 måned i gjennomsnitt.
Utgivelses datoer er annonsert på forhånd i god tid slik at de som jobber med systemet vet når prosjektene deres trenger å være ferdige for testing.
En testperiode foregår før hver utgivelse for å sørge for at nye funksjonaliteter ikke kommer i veien for stabiliteten i utgivelsen.
Mange brukere synes dette er noe av det beste med FreeBSD selvom ventetiden for å få dette i <emphasis>-STABLE</emphasis> kan være litt frustrerende.
More information on the release engineering process (including a schedule of upcoming releases) can be found on the <link xlink:href="https://www.FreeBSD.org/releng/index.html">release engineering</link> pages on the FreeBSD Web site.
Mer informasjon om utgivelses prosessen (inkludert en plan om kommende utgivelse) kan sjekkes ut på <link xlink:href="https://www.FreeBSD.org/releng/index.html">release engineering</link> siden på FreeBSD Web.
For people who need or want a little more excitement, binary snapshots are made weekly as discussed above.
For folk som vil ha litt mer spenning i hverdagen så får man binære snapshots som gis ut ukentlig som nevnt ovenfor.
When are FreeBSD snapshots made?
Når blir FreeBSD utgivelser laget?
FreeBSD <link xlink:href="@@URL_RELPREFIX@@/snapshots/">snapshot</link> releases are made based on the current state of the <emphasis>-CURRENT</emphasis> and <emphasis>-STABLE</emphasis> branches. The goals behind each snapshot release are:
FreeBSD <link xlink:href="@@URL_RELPREFIX@@/snapshots/">snapshot</link> utgivelser er laget utifra status fra <emphasis>-CURRENT</emphasis> og <emphasis>-STABLE</emphasis> grenene. Målet bak hver snapshot utgivelse er:
To test the latest version of the installation software.
Teste siste versjon av installerings programvare.
To give people who would like to run <emphasis>-CURRENT</emphasis> or <emphasis>-STABLE</emphasis> 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.
Gi folk mulighet til å kjøre <emphasis>-CURRENT</emphasis> eller <emphasis>-STABLE</emphasis> uten å ha tid el båndbredden til å følge med dag-til-dag hva som skjer. Som en enkel mulighet å prøve ut systemet.
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.)
Preservere et satt referanse poeng for koden som gjennomgås i tilfelle noe kræsjer/ryker senere. (Selvom Subversion normalt vanligvis skal sørge for at dette ikke skjer).
To ensure that all new features and fixes in need of testing have the greatest possible number of potential testers.
Sørge for at alle nye funksjoner og oppdateringer har så mange som mulige testere av systemet.
No claims are made that any <emphasis>-CURRENT</emphasis> snapshot can be considered <quote>production quality</quote> for any purpose. If a stable and fully tested system is needed, stick to full releases.
Vi kan ikke garantere at <emphasis>-CURRENT</emphasis> snapshots kan ses på som <quote>produksjons klar</quote> for noe som helst bruk. Hvis ønsket er et stabilt og fullt testet system er ønskelig, hold deg til fulle utgivelser.
Snapshot releases are directly available from <link xlink:href="@@URL_RELPREFIX@@/snapshots/">snapshot</link>.
Snapshots utgivelser er direkte tilgjengelige fra: <link xlink:href="@@URL_RELPREFIX@@/snapshots/">snapshot</link>.
Official snapshots are generated on a regular basis for all actively developed branches.
Offisielle snapshots er generert på regular basis for alle aktive grener under utvikling.

Loading…

No matching activity found.

Browse all component changes

Things to check

XML syntax

The translation is not valid XML

Reset

Mismatching line breaks

Number of new lines in translation does not match source

Reset

Glossary

English Norwegian Bokmål
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: answer/para
Labels
No labels currently set.
Source string location
book.translate.xml:450
Source string age
9 months ago
Translation file
books/nb_NO/faq.po, string 66