Release Notes for openSUSE/Leap 15.4 — Romanian @ openSUSE Weblate: To work with transactional updates, always use the command <command>transactional-update</command> …

Translation

English (itstool) path: sect2/para

Romanian

Needs editing

Skip

	English	Romanian	Actions
	Using Atomic Updates With the System Role <emphasis>Transactional Server</emphasis>	Utilizarea actualizărilor atomice cu rolul de sistem <emphasis>Server tranzacțional</emphasis>
	The installer supports the system role <emphasis>Transactional Server</emphasis>. This system role features an update system that applies updates atomically (as a single operation) and makes them easy to revert should that become necessary. These features are based on the package management tools that all other SUSE and openSUSE distributions also rely on. This means that the vast majority of RPM packages that work with other system roles of openSUSE Leap 15.4 also work with the system role <emphasis>Transactional Server</emphasis>.
	Incompatible Packages	Pachete incompatibile
	Some packages modify the contents of <filename>/var</filename> or <filename>/srv</filename> in their RPM <literal>%post</literal> scripts. These packages are incompatible. If you find such a package, file a bug report.	Unele pachete modifică conținutul <filename>/var</filename> sau <filename>/srv</filename> în scripturile lor RPM <literal>%post</literal>. Aceste pachete sunt incompatibile. Dacă găsiți un astfel de pachet, trimiteți un raport de eroare.
	To provide these features, this update system relies on:	Pentru a oferi aceste caracteristici, acest sistem de actualizare se bazează pe:
	Btrfs snapshots	Instantanee Btrfs
	Before a system update is started, a new Btrfs snapshot of the root file system is created. Then, all the changes from the update are installed into that Btrfs snapshot. To complete the update, you can then restart the system into the new snapshot.	Înainte de a începe o actualizare a sistemului, se creează un nou instantaneu Btrfs al sistemului de fișiere rădăcină. Apoi, toate modificările aduse de actualizare sunt instalate în acel instantaneu Btrfs. Pentru a finaliza actualizarea, puteți reporni apoi sistemul în noul instantaneu.
	To revert the update, simply boot from the previous snapshot instead.	Pentru a inversa actualizarea, pur și simplu porniți calculatorul folosind instantaneul anterior.
	A read-only root file system	Un sistem de fișiere rădăcină numai pentru citire
	To avoid issues with and data loss because of updates, the root file system must not be written to otherwise. Therefore, the root file system is mounted read-only during normal operation.	Pentru a evita problemele și pierderile de date din cauza actualizărilor, nu trebuie să se scrie în sistemul de fișiere rădăcină. Prin urmare, sistemul de fișiere rădăcină este montat numai pentru citire în timpul funcționării normale.
	To make this setup work, two additional changes to the file system needed to be made: To allow writing user configuration in <filename>/etc</filename>, this directory is automatically configured to use OverlayFS. <filename>/var</filename> is now a separate subvolume which can be written to by processes.	Pentru ca această configurație să funcționeze, a fost nevoie să se facă două modificări suplimentare la sistemul de fișiere: Pentru a permite scrierea configurației utilizatorului în <filename>/etc</filename>, acest director este configurat automat pentru a utiliza OverlayFS. <filename>/var</filename> este acum un subvolum separat în care procesele pot scrie.
	<emphasis>Transactional Server</emphasis> Needs At Least 12 GB of Disk Space	<emphasis>Server tranzacțional</emphasis> are nevoie de cel puțin 12 GB de spațiu pe disc
	The system role <emphasis>Transactional Server</emphasis> needs a disk size of at least 12 GB to accommodate Btrfs snapshots.	Rolul de sistem <emphasis>Server tranzacțional</emphasis> are nevoie de o dimensiune a discului de cel puțin 12 GB pentru a găzdui instantanee Btrfs.
	YaST Does Not Work Transactional Mode	YaST nu funcționează în modul tranzacțional
	Currently, YaST does not work with transactional updates. This is because YaST performs things immediately and because it cannot edit a read-only filesystem.	În prezent, YaST nu funcționează cu actualizări tranzacționale. Acest lucru se datorează faptului că YaST efectuează lucrurile imediat și pentru că nu poate edita un sistem de fișiere numai pentru citire.
	To work with transactional updates, always use the command <command>transactional-update</command> instead of YaST and Zypper for all software management:	Pentru a lucra cu actualizări tranzacționale, utilizați întotdeauna comanda <comand>transactional-update</comand> în loc de YaST și Zypper pentru toată gestiunea programelor:
	Update the system: <command>transactional-update up</command>	Actualizați sistemul: <command>transactional-update up</command>
	Install a package: <command>transactional-update pkg in <replaceable>PACKAGE_NAME</replaceable></command>	Instalați un pachet: <command>transactional-update pkg in <replaceable>PACKAGE_NAME</replaceable></command>
	Remove a package: <command>transactional-update pkg rm <replaceable>PACKAGE_NAME</replaceable></command>	Îndepărtați un pachet: <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>	Pentru a reveni la ultimul instantaneu, adică la ultimul set de modificări aduse sistemului de fișiere rădăcină, asigurați-vă că sistemul este pornit în penultimul instantaneu și rulați: <command>transactional-update rollback</command>
	Optionally, add a snapshot ID to the end of the command to rollback to a specific ID.	Opțional, adăugați un ID de instantaneu la sfârșitul comenzii pentru a reveni la un anumit 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/"/>.
	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.
	<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>.
	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.
	UEFI, GPT, and MS-DOS Partitions	UEFI, GPT și partiții MS-DOS

Loading…

Translation changed

English

Romanian 2 characters edited Current translation

4 months ago

Translation added

English

Romanian 176 characters edited

4 months ago

Browse all string changes

Things to check

XML markup

XML tags in translation do not match source

Reset

Glossary

English	Romanian
No related strings found in the glossary.

String information

Source string description

(itstool) path: sect2/para

Source string location

xml/release-notes.xml:174

String age

2 years ago

Last updated

2 weeks ago

Source string age

2 years ago

Translation file

po/ro.po, string 36