Release Notes for openSUSE/Leap 15.3 — Bulgarian @ openSUSE Weblate: This section lists notes related to upgrading the system. For …

Translation

Source change

English (itstool) path: sect1/para

Bulgarian

Needs editing

Skip

	English	Bulgarian	Actions
	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.	Преди да инсталирате openSUSE на система, зареждаща се с помощта на UEFI (Unified Extensible Firmware Interface), настоятелно Ви препоръчваме да проверите наличието на обновена firmware, от всички производители, и в случай че существуват инсталирайте ги. Предварително инсталирана Windows 8 се явява верен признак на това, че вашата система исползва 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>Внимание:</emphasis> Някои UEFI фърмуери имат бъгове които могат да доведат до счупването им ако твърде много информация бъде записана в паметта им. Обаче, не е ясно колко много информация е <quote>твърде много</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.	openSUSE намалява риска чрез записването на минималното нужно за да зареди Операционната Система.Минималното означава да каже на UEFI фърмуера къде се намира openSUSE boot loader-а. Допълнителните функционалности от по-новите версии на ядрото , като използването на UEFI паметта за съхранение на зареждаща и краш информация <literal>pstore</literal>, са изключени по подразбиране. Въпреки това, препоръчваме да инсталирате обновленията на фърмуера ,които вашия производител препоръчва.
	UEFI, GPT, and MS-DOS partitions	Дялове от тип UEFI, GPT и MS-DOS
	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.
	<literal>tlp</literal> package service
	During installation on a laptop, the <literal>tlp</literal> package is installed (together with its sub-package <literal>tlp-rdw</literal>, if the installation of recommended packages is enabled). This package provides additional tools to save battery power on laptops, especially Lenovo laptops.
	The service is not enabled by default because it might interfere with other specialized laptop tools, for example, <literal>laptop-mode-tools</literal>, <literal>rfkill</literal>, <literal>gnome-power-manager</literal>, or <literal>kde-power-manager</literal>. To enable and start the service explicitly, use YaST Services Manager or use the command <literal> systemctl enable --now tlp.service </literal>. If you encounter any unexpected behavior afterward, for example, WiFi problems or non-functional USB ports, disable the service again.
	System upgrade	Система
	This section lists notes related to upgrading the system. For supported scenarios and detailed upgrade instructions, see the documentation at:	Тази секция съдържа бележки свързани със инсталацията. За детайлни инструкции как да надстроите, моля консултирайте се с документацията на <link href="https://doc.opensuse.org/documentation/leap/startup/html/book.opensuse.startup/part.basics.html"/>.
	Additionally, check <xref linkend="removed-deprecated"/>.
	Seamless upgrade from openSUSE Leap 15.2	openSUSE Leap
	openSUSE Leap 15.3 is newly built on top of binary rpms from SUSE Linux Enterprise Server. This change was introduced as part of the Closing The Leap Gap (CtLG) effort to bring openSUSE Leap and SUSE Linux Enterprise Server closer together.
	Unlike 15.2, the default installation of openSUSE Leap 15.3 contains the majority of rpms from SUSE Linux Enterprise Server. These rpms are signed by SUSE LLC instead of using the openSUSE key. The <package>libzypp</package> package version 12.25.8 introduced whitelist for the SUSE LLC and openSUSE vendor exchange to allow seamless migration. This whitelist removes the need to specify <literal>--allow-vendor-change</literal> for openSUSE and SUSE LLC vendor exchange only. You might still need to specify <literal>--allow-vendor-change</literal> during migration if you are using OBS repositories signed with other keys.
	openSUSE Leap releases older than 15.2 do not contain this feature because they are not supported anymore. All users are advised to upgrade to openSUSE Leap 15.2 with the latest updates before upgrading to 15.3. The following parameters can be used as a workaround for <package>libzypp</package> versions older than 12.25.8 (replace 15.0 below with your current openSUSE version):
	zypper addrepo --check --refresh --name 'openSUSE-Leap-15.0-Update' http://download.opensuse.org/update/leap/15.0/oss/ repo-update zypper dup --allow-vendor-change --force-resolution
	openSUSE Leap 15.3 provides all the required RPM verification keys, including the SUSE Linux Enterprise Server ones, as part of the <package>openSUSE-build-key</package> package. All the keys are also newly available inside the OSS repository.
	The <package>libzypp</package> package version 17.25.11 should automatically import the required keys that are identified as trusted. If it has, you will be notified about the import and no other action will be needed.
	If the system has not imported the key that was used to sign the <literal>repodata</literal>, you will need to import it manually. You can check by running the following command:
	rpm -qa gpg-pubkey
	The output should include a line starting with the following text: <literal>gpg-pubkey-39db7c82-*</literal> If it does not, the do the following to import the key manually:
	Download the SUSE Linux Enterprise 15 key from <link xlink:href="https://download.opensuse.org/distribution/leap/15.3/repo/oss/gpg-pubkey-39db7c82-5847eb1f.asc"/>.
	Save the key to the <literal>/var/cache/zypp/pubkeys</literal> directory. Rename it so that it ends with <literal>.key</literal>.
	Run the <literal>zypper dup</literal> command. You will be asked to import the missing key. This will happen even if the key is in the directory mentioned above. If the file contains multiple keys, zypper will import only the required key.
	For more information, see <link xlink:href="https://bugzilla.opensuse.org/show_bug.cgi?id=1184326"/>.	Свалянето на EPUB файловете от <ulink url="http://en.opensuse.org/Documentation"/>.

Loading…

No matching activity found.

Browse all string changes

Things to check

Mismatched colon

Source and translation do not both end with a colon

Reset

Mismatched full stop

Source and translation do not both end with a full stop

Reset

Glossary

English	Bulgarian
No related strings found in the glossary.

String information

Source string description

(itstool) path: sect1/para

Source string location

xml/release-notes.xml:349

String age

3 years ago

Last updated

a month ago

Source string age

3 years ago

Translation file

po/bg.po, string 65