Release Notes for openSUSE/Leap 15.2 — Chinese (China) (zh_CN) @ openSUSE Weblate: systemctl disable --now transactional-update.timer rebootmgr.service

Translation

English (itstool) path: sect2/screen

Chinese (China) (zh_CN)

Needs editing

Skip

	English	Chinese (China) (zh_CN)	Actions
	To revert the update, simply boot from the previous snapshot instead.	要撤销更新，只要从前一个快照重新启动系统即可。
	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.	要让此安装设置工作，需要对文件系统做两个额外的更改：要允许写入 <filename>/etc</filename> 里的用户配置，此目录自动配置为使用 OverlayFS。<filename>/var</filename> 现在是独立的子卷，可以被进程写入。
	<emphasis>Transactional Server</emphasis> Needs At Least 12 GB of Disk Space	<emphasis>事务服务器</emphasis>需要至少 12 GB 的磁盘空间
	The system role <emphasis>Transactional Server</emphasis> needs a disk size of at least 12 GB to accommodate Btrfs snapshots.	系统角色<emphasis>事务服务器</emphasis>需要至少 12 GB 的磁盘大小来容纳 Btrfs 快照。
	YaST Does Not Work Transactional Mode	YaST 不能在事务模式下使用
	Currently, YaST does not work with transactional updates. This is because YaST performs things immediately and because it cannot edit a read-only filesystem.	当前，YaST 不适用于事务更新。这是因为 YaST 是即时执行操作的，并且它也无法编辑只读文件系统。
	To work with transactional updates, always use the command <command>transactional-update</command> instead of YaST and Zypper for all software management:	要使用事务更新，软件的全部管理要始终使用命令 <command>transactional-update</command> 来代替 YaST 和 Zypper：
	Update the system: <command>transactional-update up</command>	更新系统：<command>transactional-update up</command>
	Install a package: <command>transactional-update pkg in <replaceable>PACKAGE_NAME</replaceable></command>	安装软件包：<command>transactional-update pkg in <replaceable>软件包名称</replaceable></command>
	Remove a package: <command>transactional-update pkg rm <replaceable>PACKAGE_NAME</replaceable></command>	移除软件包：<command>transactional-update pkg rm <replaceable>软件包名称</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>	要还原最近的快照，即最近一次对根文件系统所做的更改，请确保你的系统已启动到最近快照的下一个，然后运行：<command>transactional-update rollback</command>
	Optionally, add a snapshot ID to the end of the command to rollback to a specific ID.	或者，在命令的末尾添加一个快照的 ID 以回滚到指定的 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>:	使用此系统角色时，按默认，系统会执行日常更新并在上午 3:00 和 5:00 之间重启。这两个操作都是基于 systemd 而且如有必要可用 <command>systemctl</command> 禁用：
	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 时会建议分区方案。如果你想安装，例如很小的虚拟机器映像，请使用指导分区程序来手动调整分区参数。
	Btrfs Filesystem RAM and Storage Requirements	Btrfs 文件系统 RAM 和存储需求
	The Btrfs filesystem is best used on systems with sufficient RAM and storage. SSD is also recommended. There have been user reports of performance degradation on systems with low amounts of RAM (4 GiB or less) and regular hard disk drives.	Btrfs 文件系统最好在有足够内存和存储空间的系统上使用。同时推荐使用 SSD。有用户报告称，在低内存容量（4 GiB 或更少）和常规硬盘驱动器的系统上使用出现性能下降的问题。
	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	系统升级

Loading…

No matching activity found.

Browse all string changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English	Chinese (China) (zh_CN)
No related strings found in the glossary.

String information

Source string description

(itstool) path: sect2/screen

Flags

no-wrap

Source string location

xml/release-notes.xml:217

String age

4 years ago

Last updated

2 weeks ago

Source string age

4 years ago

Translation file

po/zh_CN.po, string 43