Release Notes for openSUSE/Leap_15.6 — 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
	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.	Преди да инсталирате 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.
	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"/>.
	Make sure to also review the following sections of this documentation:
	Packaging Changes
	Important changes in updated packages
	Package python-podman is now based on the project <link xlink:href="https://github.com/containers/podman-py">podman-py</link> was <link xlink:href="https://github.com/containers/python-podman">python-podman</link>.
	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:
	zypper lifecycle
	Removed Packages
	Removed packages are not shipped as part of the distribution anymore.
	The following packages were all superseded by <link xlink:href="https://en.opensuse.org/SDB:NVIDIA_SUSE_Prime">NVIDIA SUSE Prime</link>. Also see <xref linkend="drivers-hardware-bumblebee"/>	Свалянето на EPUB файловете от <ulink url="http://en.opensuse.org/Documentation"/>.
	<package>bbswitch</package>
	<package>bumblebee</package>
	<package>bumblebee-status</package>
	<package>primus</package>

Loading…

None

Source string changed

English 150 characters edited

10 months ago

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:245

String age

10 months ago

Last updated

2 weeks ago

Source string age

10 months ago

Translation file

po/bg.po, string 57