Release Notes for openSUSE/Leap_15.6 — Chinese (China) (zh_CN) @ openSUSE Weblate: Make sure to also review the following sections of this …

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: sect1/para

Chinese (China) (zh_CN)

Needs editing

This translation is currently locked.

Skip

	English	Chinese (China) (zh_CN)	Actions
	systemctl disable --now transactional-update.timer rebootmgr.service	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/"/>.	更多关于事务更新的信息，请参阅 openSUSE Kubic 博客文章 <link xlink:href="https://kubic.opensuse.org/blog/2018-04-04-transactionalupdates/"/> 和 <link xlink:href="https://kubic.opensuse.org/blog/2018-04-20-transactionalupdates2/"/>.
	Installing on Hard Disks With Less Than 12 GB of Capacity	安装到容量低于 12 GB 的硬盘
	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.	安装程序只在磁盘可用大小超过 12 GB 时会建议分区方案。如果你想安装，例如很小的虚拟机器映像，请使用指导分区程序来手动调整分区参数。
	UEFI—Unified Extensible Firmware Interface	UEFI——统一可扩展固件接口
	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（统一可扩展固件接口）引导的计算机上前，特别建议您检查一下硬件制造商推荐的固件更新，并且，如果有的话，请安装这样的更新。预装了 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 固件存在问题，会导致在向 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 引导加载器的位置。我们默认禁用了上游 Linux 内核使用 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.	伴随着 EFI/UEFI 规范到来的是一种新的分区风格：GPT（GUID 分区表）。这种新方法使用全局唯一标识符（128 位值显示成 32 个十六进制数字）来识别设备和分区类型。
	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.	另外，UEFI 规范也允许传统的 MBR（MS-DOS）分区。Linux 引导加载器（ELILO 或 GRUB2）会尝试为这些传统方式的分区自动生成一个 GUID，并将它们写入到固件中。这样的 GUID 可频繁变化，导致重写固件。重写由两个不同操作组成：移除旧项和创建替代前一个项的新项。
	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.	规避方法很简单：将传统的 MBR 分区转换成新的 GPT 分区来避免此问题。
	System Upgrade	系统升级
	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:	请务必查阅 <xref linkend="sec.driver"/>。
	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.	弃用的软件包依旧提供为发行版的一部分，但计划在下个 openSUSE Leap 版本中移除。这些软件包存在是为了方面迁移，但不鼓励使用它们且它们可能不会再收到更新。
	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:	如需确认安装的软件包是否不再维护，请先安装 <package>lifecycle-data-openSUSE</package> 软件包，再执行如下命令：
	zypper lifecycle	zypper lifecycle
	Removed Packages	移除的软件包
	Removed packages are not shipped as part of the distribution anymore.	移除的软件包不再随发行版一起发布。
	<package>gnome-todo</package>: gnome-todo was replaced by package Endeavour.	<package>gnome-system-log</package>：被替换为 <package>gnome-logs</package>。
	<package>msgpack</package>: msgpack was replaced by msgpack-c and msgpack-cxx.	<package>qgo</package>：被替换为 <package>q5go</package>。
	<package>nodejs-electron</package>: This old version of Electron is EOL, and we are unable to support this runtime throughout Leap's lifetime due to frequent ABI breaks. Current versions of Electron are still available from the devel:languages:nodejs repository on OBS.
	Drivers and Hardware	驱动与硬件
	Secure Boot: Third-Party Drivers Need to Be Properly Signed	安全引导：第三方驱动需要正确签名
	Starting with openSUSE Leap 15.2, kernel module signature check for third-party drivers (<literal>CONFIG_MODULE_SIG=y</literal>) is now enabled. This is an important security measure to avoid untrusted code running in the kernel.	从 openSUSE Leap 15.2 开始，会对第三方驱动启用内核模块签名检查（<literal>CONFIG_MODULE_SIG=y</literal>）。这是一个重要的安全措施，以避免在内核中运行未经信任的代码。
	This may prevent third-party kernel modules from being loaded if UEFI Secure Boot is enabled. Kernel Module Packages (KMPs) from the official openSUSE repositories are not affected, because the modules they contain are signed with the openSUSE key. The signature check has the following behavior:	如果启用了 UEFI 安全引导，这可能会阻止到第三方内核模块的加载。来自 openSUSE 官方仓库的内核模块软件包（KMP）则不受影响，因为仓库内的模块已用 openSUSE 密钥签名过。签名检查表现为以下行为：
	Kernel modules that are unsigned or signed with a key that is either known as untrusted or cannot be verified against the system's trusted key data base will be blocked.	未签名与不受信任或未被系统可信密钥数据库验证过的密钥所签名的内核模块，将被屏蔽。

Loading…

None

Source string changed

English 37 characters edited

9 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	Chinese (China) (zh_CN)
No related strings found in the glossary.

String information

Source string description

(itstool) path: sect1/para

Source string location

xml/release-notes.xml:311

String age

9 months ago

Last updated

2 weeks ago

Source string age

9 months ago

Translation file

po/zh_CN.po, string 58