The translation is temporarily closed for contributions due to maintenance, please come back later.

Translation

(itstool) path: answer/para
English
The key decisions concerning the FreeBSD project, such as the overall direction of the project and who is allowed to add code to the source tree, are made by a <link xlink:href="@@URL_RELPREFIX@@/administration.html#t-core">core team</link> of 9 people. There is a much larger team of more than 350 <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/contributors/article.html#staff-committers">committers</link> who are authorized to make changes directly to the FreeBSD source tree.
Context English Norwegian Bokmål State
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.
Who is responsible for FreeBSD? Hvem har ansvaret for FreeBSD?
The key decisions concerning the FreeBSD project, such as the overall direction of the project and who is allowed to add code to the source tree, are made by a <link xlink:href="@@URL_RELPREFIX@@/administration.html#t-core">core team</link> of 9 people. There is a much larger team of more than 350 <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/contributors/article.html#staff-committers">committers</link> who are authorized to make changes directly to the FreeBSD source tree. De store avgjørelsene innenfor FreeBSD prosjektet som hovedretning og hvor det ønskes at prosjektet tar veiene + hvem som kan legge til kode i source coden bestemmes
av et <link xlink:href="@@URL_RELPREFIX@@/administration.html#t-core">core team</link> på 9 personer.
Det er et mye større team på mer enn 350 <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/contributors/article.html#staff-committers">committers</link> som er autorisert til å gjøre endringer direkte i FreeBSD Source Tree.
However, most non-trivial changes are discussed in advance in the <link linkend="mailing">mailing lists</link>, and there are no restrictions on who may take part in the discussion. Uansett så er de fleste mindre-viktige endringer diskutert på forhånd via <link linkend="mailing">mailing listsen</link> og det er ingen restriksjoner om hvem som kan delta i den diskusjonen.
Where can I get FreeBSD? Hvor kan jeg få tak i FreeBSD?
Every significant release of FreeBSD is available via anonymous FTP from the <link xlink:href="https://download.FreeBSD.org/ftp/releases/">FreeBSD FTP site</link>: Alle betydelige utgivelser av FreeBSD er tilgjengelig anonymt via <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/">FreeBSD FTP siden</link>:
The latest <emphasis>12-STABLE</emphasis> release, 12.1-RELEASE can be found in the <link xlink:href="https://download.FreeBSD.org/ftp/releases/amd64/amd64/12.1-RELEASE/">12.1-RELEASE directory</link>. Den nyeste <emphasis>12-STABLE</emphasis> utgivelsen, 12.0-RELEASE kan finnes frem i <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/i386/12.0-RELEASE/">12.0-RELEASE directory</link>.
<link xlink:href="@@URL_RELPREFIX@@/snapshots/">Snapshot</link> releases are made monthly for the <link linkend="current">-CURRENT</link> and <link linkend="stable">-STABLE</link> branch, these being of service purely to bleeding-edge testers and developers. <link xlink:href="@@URL_RELPREFIX@@/snapshots/">Snapshot</link> utgivelser er gitt ut månedlig for <link linkend="current">-CURRENT</link> og <link linkend="stable">-STABLE</link> grenen, disse er mest for bleeding-edge testere og utviklere.
The latest <emphasis>11-STABLE</emphasis> release, 11.3-RELEASE can be found in the <link xlink:href="https://download.FreeBSD.org/ftp/releases/amd64/amd64/11.3-RELEASE/">11.3-RELEASE directory</link>. Den nyeste <emphasis>11-STABLE</emphasis> utgivelsen, 10.4-RELEASE kan finnes frem i <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/10.4-RELEASE/">10.4-RELEASE directory</link>.
Information about obtaining FreeBSD on CD, DVD, and other media can be found in <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/mirrors.html">the Handbook</link>. Informasjon om hvordan skaffe seg FreeBSD via CD,DVD eller andre media kan sjekkes ut i <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/mirrors.html">Handbook</link>.
How do I access the Problem Report database? Hvordan får jeg tilgang til Problem Rapporterings databasen?
The Problem Report database of all user change requests may be queried by using our web-based PR <link xlink:href="https://bugs.FreeBSD.org/search/">query</link> interface. Forespørsler i Problem Rapporterings databasen av alle bruker endringer kan henvendes til den web-baserte PR <link xlink:href="https://bugs.FreeBSD.org/search/">query</link> grensesnittet.
The <link xlink:href="@@URL_RELPREFIX@@/support/bugreports.html">web-based problem report submission interface</link> can be used to submit problem reports through a web browser. Den <link xlink:href="@@URL_RELPREFIX@@/support/bugreports.html">web-baserte problem rapporterings grensesnittet</link> kan brukes til å sende inn problemer via en web-browser.
Before submitting a problem report, read <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/problem-reports/article.html">Writing FreeBSD Problem Reports</link>, an article on how to write good problem reports. Før man sender inn problem rapport, les <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/problem-reports/article.html">Writing FreeBSD Problem Reports</link>, en artikkel om hvordan man bør skrive gode rapporter vedrørende problemer.
Documentation and Support Dokumentasjon og Support
What good books are there about FreeBSD? Hvilke gode bøker anbefales rundt FreeBSD?
The project produces a wide range of documentation, available online from this link: <uri xlink:href="https://www.FreeBSD.org/docs.html">https://www.FreeBSD.org/docs.html</uri>. FreeBSD prosjektet har stor variasjon av dokumentasjon tilgjengelig på nett via denne lenken: <uri xlink:href="https://www.FreeBSD.org/docs.html">https://www.FreeBSD.org/docs.html</uri> I tillegg finner man <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/bibliography.html">referanser i Handbook</link> som henviser til andre anbefalte bøker.
Is the documentation available in other formats, such as plain text (ASCII), or PDF? Er dokumentasjonen tilgjengelig i andre format som klar tekst (ASCII) eller <trademark class="registered">PostScript</trademark>?

Loading…

No matching activity found.

Browse all component changes

Things to check

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
Source string location
book.translate.xml:569
String age
a year ago
Source string age
a year ago
Translation file
books/nb_NO/faq.po, string 83