The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not merge the repository.
Zen

Translation

English (itstool) path: sect2/title
UEFI—Unified Extensible Firmware Interface
42/420 · 42

This translation is currently locked.

English Danish Actions
<emphasis>Transactional Server</emphasis> Needs At Least 12 GB of Disk Space
 
The system role <emphasis>Transactional Server</emphasis> needs a disk size of at least 12 GB to accommodate Btrfs snapshots.
 
YaST Does Not Work Transactional Mode
 
Currently, YaST does not work with transactional updates. This is because YaST performs things immediately and because it cannot edit a read-only filesystem.
 
To work with transactional updates, always use the command <command>transactional-update</command> instead of YaST and Zypper for all software management:
 
Update the system: <command>transactional-update up</command>
 
Install a package: <command>transactional-update pkg in <replaceable>PACKAGE_NAME</replaceable></command>
 
Remove a package: <command>transactional-update pkg rm <replaceable>PACKAGE_NAME</replaceable></command>
 
To revert the last snapshot, that is the last set of changes to the root file system, make sure your system is booted into the next to last snapshot and run: <command>transactional-update rollback</command>
 
Optionally, add a snapshot ID to the end of the command to rollback to a specific ID.
 
When using this system role, by default, the system will perform a daily update and reboot between 03:30 am and 05:00 am. Both of these actions are systemd-based and if necessary can be disabled using <command>systemctl</command>:
 
systemctl disable --now transactional-update.timer rebootmgr.service
 
For more information about transactional updates, see the openSUSE Kubic blog posts <link xlink:href="https://kubic.opensuse.org/blog/2018-04-04-transactionalupdates/"/> and <link xlink:href="https://kubic.opensuse.org/blog/2018-04-20-transactionalupdates2/"/>.
For mere information om transaktionelle opdateringer, se openSUSE Kubic-blogindlæggene <link xlink:href="https://kubic.opensuse.org/blog/2018-04-04-transactionalupdates/"/> og <link xlink:href="https://kubic.opensuse.org/blog/2018-04-20-transactionalupdates2/"/>.
Installing on Hard Disks With Less Than 12 GB of Capacity
 
The installer will only propose a partitioning scheme if the available hard disk size is larger than 12 GB. If you want to set up, for example, very small virtual machines images, use the guided partitioner to tune partitioning parameters manually.
 
UEFI—Unified Extensible Firmware Interface
UEFI—Unified Extensible Firmware Interface
Prior to installing openSUSE on a system that boots using UEFI (Unified Extensible Firmware Interface), you are urgently advised to check for any firmware updates the hardware vendor recommends and, if available, to install such an update. A pre-installation of Windows 8 or later is a strong indication that your system boots using UEFI.
Før du installerer openSUSE på et system, som bruger UEFI (Unified Extensible Firmware Interface) til at boote er det vigtigt, at du tjekker om hardware-producenten anbefaler nogen opdatering af firmwaren og om muligt installerer en sådan opdatering. Hvis maskinen er købt med Windows 8 eller senere, så er det en stærk indikation af at systemet booter med UEFI.
<emphasis>Background:</emphasis> Some UEFI firmware has bugs that cause it to break if too much data gets written to the UEFI storage area. However, there is no clear data of how much is <quote>too much</quote>.
<emphasis>Baggrund:</emphasis> Noget UEFI-firmware har fejl, som får det til at bryde sammen, hvis der skrives for store mængder data til UEFI's lagerområde. Der findes dog ingen sikre oplysninger om, hvor meget <quote>for meget</quote> er.
openSUSE minimizes the risk by not writing more than the bare minimum required to boot the OS. The minimum means telling the UEFI firmware about the location of the openSUSE boot loader. Upstream Linux kernel features that use the UEFI storage area for storing boot and crash information (<literal>pstore</literal>) have been disabled by default. Nevertheless, it is recommended to install any firmware updates the hardware vendor recommends.
openSUSE minimerer risikoen ved ikke at skrive mere end det absolutte minimum der skal til for at boote OS'et. Dette minimum involverer at fortælle UEFI hvor openSUSE's boot loader findes. Funktioner i Linux-kernen, som anvender UEFI's lager til at gemme information om opstart og nedbrud (<literal>pstore</literal>) bliver deaktiveret som standard. Ikke desto mindre anbefales det at installere enhver opdatering af firmwaren som anbefales af hardware-producenten.
UEFI, GPT, and MS-DOS Partitions
UEFI-, GPT- og MS-DOS-partitioner
Together with the EFI/UEFI specification, a new style of partitioning arrived: GPT (GUID Partition Table). This new schema uses globally unique identifiers (128-bit values displayed in 32 hexadecimal digits) to identify devices and partition types.
Sammen med specifikationerne for EFI/UEFI kom en ny form for partitionering: GPT (GUID Partition Table). Denne nye form bruger globalt entydige identifikatorer (128-bit-værdier vist som 32 hexadecimale cifre) til identifikation af enheder og partitionstyper.
Additionally, the UEFI specification also allows legacy MBR (MS-DOS) partitions. The Linux boot loaders (ELILO or GRUB 2) try to automatically generate a GUID for those legacy partitions, and write them to the firmware. Such a GUID can change frequently, causing a rewrite in the firmware. A rewrite consists of two different operations: Removing the old entry and creating a new entry that replaces the first one.
Derudover tillader UEFI-specifikationen gammeldags MBR- (MS_DOS-)partitioner. Linux' boot loadere (ELILO or GRUB 2) prøver automatisk at danne et GUID for disse gammeldags partitioner og at skrive dem til firmwaren. Sådan et GUID kan blive ændret ret ofte, hvilket forårsager endnu en skrivning til firmwaren. En sådan skrivning indbefatter to forskellige operationer: Fjernelse af den gamle indgang og oprettelse af en ny, som erstatter den gemle.
Modern firmware has a garbage collector that collects deleted entries and frees the memory reserved for old entries. A problem arises when faulty firmware does not collect and free those entries. This can result in a non-bootable system.
Moderne firmware har en garbage collector, som indsamler slettede indførsler og frigiver den hukommelse, der var reserveret til dem. Der opstår et problem, når fejlbehæfter firmware ikke indsamler og frigiver disse indførsler. Dette kan resultere i at systmet ikke længere kan startes op.
To work around this problem, convert the legacy MBR partition to GPT.
Konvertér gamle MBR-partitioner til GPT for at omgå dette problem.
System Upgrade
Systemopgradering
This section lists notes related to upgrading the system. For supported scenarios and detailed upgrade instructions, see the documentation at:
Dette afsnit oplister noter relateret til opgradering af systemet. For understøttede scenarier og detaljerede instruktioner, se sokumentationen på:
Make sure to also review the following sections of this documentation:
 
Packaging Changes
 
Deprecated Packages
 
Deprecated packages are still shipped as part of the distribution but are scheduled to be removed the next version of openSUSE Leap. These packages exist to aid migration, but their use is discouraged and they may not receive updates.
 
To check whether installed packages are no longer maintained, make sure that the <package>lifecycle-data-openSUSE</package> package is installed, then use the command:
 

Loading…

No matching activity found.
Browse all string changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English Danish
No related strings found in the glossary.

String information

Source string description
(itstool) path: sect2/title
Source string location
xml/release-notes.xml:238
String age
9 months ago
Last updated
2 weeks ago
Source string age
9 months ago
Translation file
po/da.po, string 47