Release Notes for openSUSE/Leap_15.6 — Hungarian @ openSUSE Weblate: For more information about transactional updates, see the openSUSE Kubic …

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

Source change

English (itstool) path: sect2/para

Hungarian

Needs editing

This translation is currently locked.

Skip

	English	Hungarian	Actions
	A read-only root file system
	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.
	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.
	<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	systemctl disable NetworkManager.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/"/>.	Ez a hiba már be van jelentve a Gnome projekt fejlesztőinek <ulink url="https://bugzilla.gnome.org/show_bug.cgi?id=689839"/>.
	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.	Az openSUSE olyan gépre történő telepítése előtt, amely a rendszerbetöltéshez UEFI-t (Unified Extensible Firmware Interface) használ, mindenképpen ellenőrizni kell, hogy létezik-e olyan firmware frissítés, amelynek telepítését a hardver gyártója javasolja és amennyiben létezik ilyen, azt telepíteni kell. Amennyiben a számítógépen Windows 8 operációs rendszer van előtelepítve, az egy jel, hogy a számítógépen UEFI található.
	<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.	<emphasis>Háttér:</emphasis> Néhány UEFI firmware-ben egy olyan hiba található, amely tönkreteszi, amennyiben túl sok adat kerül kiírásra az UEFI tárterületre. Azonban senki sem tudja biztosan, hogy pontosan mennyi az a "túl sok". Az openSUSE igyekszik minimalizálni a kockázatot azzal, hogy csak a rendszer indításához feltétlenül szükséges információt írja ki az UEFI tárolóterületre. Ez azt jelenti, hogy ez arra szorítkozik, hogy az UEFI firmware tudja, mogy merre található az openSUSE rendszertöltő. Az olyan Linux Kernel funkciók, amelyek arra használják az UEFI tárolóterületet, hogy betöltéssel és az összeomlásokkal kapcsolatos információkat (<literal>pstore</literal>) tároljanak, alapértelmezésként ki vannak kapcsolva. Azonban mindenképpen javasolt a hardvergyártó által kiadott firmware telepítése.
	UEFI, GPT, and MS-DOS Partitions
	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.
	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.
	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.
	To work around this problem, convert the legacy MBR partition to GPT.
	System Upgrade	Rendszerfrissítés
	This section lists notes related to upgrading the system. For supported scenarios and detailed upgrade instructions, see the documentation at:
	Make sure to also review the following sections of this documentation:
	Packaging Changes