Release Notes for openSUSE/Leap_15.5 — Chinese (Taiwan) (zh_TW) @ openSUSE Weblate: systemctl disable --now transactional-update.timer rebootmgr.service

Translation

English (itstool) path: sect2/screen

Chinese (Taiwan) (zh_TW)

Needs editing

Skip

	English	Chinese (Taiwan) (zh_TW)	Actions
	To revert the update, simply boot from the previous snapshot instead.	要取消這項更新，只需從前一個快照開機即可。
	A read-only root file system	唯讀 root 檔案系統
	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.	為了避免因為更新造成的問題與資料遺失，root 檔案系統必須禁止寫入。是故 root 檔案系統在正常操作下是以唯讀方式掛載。
	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>PACKAGE_NAME</replaceable></command>
	Remove a package: <command>transactional-update pkg rm <replaceable>PACKAGE_NAME</replaceable></command>	移除套件：<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>	要取消最後一個快照對 root 檔案系統所做的變更，請先確認您的系統是使用最後一個快照之前的快照開機，然後執行：<command>transactional-update rollback</command>
	Optionally, add a snapshot ID to the end of the command to rollback to a specific 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>:	當使用該系統角色時，系統預設會執行每日更新並且在早上 03:30 與下午 05: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 時，安裝程式才會建議磁碟分割規劃。若您想要設定空間非常小的虛擬機器映象檔，請使用引導式磁碟分割程式來自行調整分割參數。
	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 Partition Table）。這個新的方式使用 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.	現代的韌體都有一個垃圾收集器（garbage collector），可以收集被刪除的進入點（entries），並且釋放原來保留給舊進入點（entries）的記憶體。當故障的韌體不能收集或是釋放這些進入點（entries）時，系統將會出現問題，最終將造成系統無法開機。
	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"/>。

Loading…

No matching activity found.

Browse all string changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English	Chinese (Taiwan) (zh_TW)
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

a year ago

Last updated

2 weeks ago

Source string age

a year ago

Translation file

po/zh_TW.po, string 43