openSUSE Leap 42.1

發行紀事

openSUSE Leap 是一個自由的基於 Linux 的作業系統,可運作在您的桌上型電腦、筆記型電腦或是伺服器。您可以用它來瀏覽網頁、管理您的電子郵件與相片、進行生產力工作、播放影片或音樂。使用它讓您充滿樂趣。

出版日期:2015-10-28, 42.1.20151028

如果您從較舊的發行版本升級至 openSUSE Leap,請由此查看之前的發行紀事: http://en.opensuse.org/openSUSE:Release_Notes

1 安裝

1.1 基礎系統安裝

SuSEfirewall2 and yast2 have been removed from the minimal base system to save space. If you need it, select SuSEfirewall2 or patterns-openSUSE-yast2_basis.

1.2 UEFI—統一可延伸韌體介面

在安裝 openSUSE 到使用 UEFI (統一可延伸韌體介面) 開機的系統之前,強烈建議您先詢問是否有硬體製造商所建議的韌體更新並加以安裝。若您的系統有預裝 Windows 8,通常就代表您的系統使用 UEFI 開機。

背景知識: 有些 UEFI 韌體有缺陷,導致當有太多資料被寫入 UEFI 儲存區域時,韌體會發生問題。但是沒人知道究竟寫入多少資料才算「太多」,故 openSUSE 藉由只寫入能夠啟動系統的最少需要的資料量,來降低這個風險。寫入的資料至少要能告訴 UEFI 韌體 openSUSE 啟動程式的位置。官方 Linux 核心提供使用 UEFI 儲存區來寫入開機及當機資訊的功能 (pstore),在此預設被停用。無論如何,建議安裝任何硬體製造商建議的韌體更新。

1.3 UEFI,GPT 與 MS-DOS 磁碟分割區

在 EFI/UEFI 的規格書中提到一個新的分割磁碟的劃分方式:GPT(GUID Partition Table)。這個新的方式使用 GUID(128位元的值顯示在32個十六進制數字上)來識別裝置及分割區類型。

此外,UEFI 規範是允許傳統的 MBR(MS-DOS)分割區。 Linux 引導加載器(ELILO 或 GRUB2)嘗試針對那些傳統的分割區自動產生一個 GUID ,並把它們寫進韌體。像這樣的一個 GUID 可以頻繁變更,導致韌體的重寫入。一次的重寫入包括兩種不同的操作:刪除舊的項目,以及創建一個新的項目以取代第一個項目。

現代的韌體都有一個垃圾收集器(garbage collector),可以收集被刪除的進入點(entries),並且釋放原來保留給舊進入點(entries)的記憶體。當故障的韌體不能收集或是釋放這些進入點(entries)時,系統將會出現問題,最終將造成系統無法開機。

簡單的替代解決方案是:轉換傳統的 MBR 分割區成為新的 GPT 分割區以完整的避免此問題。

2 系統升級

3 一般說明

3.1 從 Live CD 進行安裝後,防火牆預設將不會啟動

當使用 Live CD 進行安裝,安裝完成後防火牆預設將不會啟用。

請使用 YaST 或執行以下指令啟用防火牆:

systemctl enable SuSEfirewall2
systemctl start SuSEfirewall2

4 技術議題

4.1 列印系統:改進以及不相容的變動

CUPS 版本昇級至 1.7

CUPS >= 1.6 有一主要變動和 1.5.4 版以前的版本不相容,特別是在網路列印這部分:

IPP 通訊協定預設版本自 1.1 昇級到 2.0。舊的 IPP 伺服器 (例如 SLE11 使用的 CUPS 1.3.x),會拒絕 IPP 2.0 的連線要求,並回傳 "Bad Request" (請見 http://www.cups.org/str.php?L4231 (http://www.cups.org/str.php?L4231))。對於舊伺服器使用舊 IPP 通訊協定必須明確指定,例如在 client.conf 中的 ServerName 加入 '/version=1.1' (ServerName older.server.example.com/version=1.1),或加到 CUPS_SERVER 環境變數,或是加到 '-h' 選項指定的伺服器名稱 (lpstat -h older.server.example.com/version=1.1 -p)。

CUPS Browsing is dropped in CUPS but the new package cups-filters provides the cups-browsed that provides basic CUPS Browsing and Polling functionality. The native protocol in CUPS for automatic client discovery of printers is now DNS-SD. Start cups-browsed on the local host to receive traditional CUPS Browsing information from traditional remote CUPS servers. To broadcast traditional CUPS Browsing information into the network so that traditional remote CUPS clients can receive it, set "BrowseLocalProtocols CUPS" in /etc/cups/cups-browsed.conf and start cups-browsed.

Some printing filters and back-ends are dropped in CUPS but the new package cups-filters provides them. So cups-filters is usually needed (recommended by RPM) but cups-filters is not strictly required.

The cupsd configuration directives are split into two files: cupsd.conf (can also be modified via HTTP PUT e.g. via cupsctl) and cups-files.conf (can only be modified manually by root) to have better default protection against misuse of privileges by normal users who have been specifically allowed by root to do cupsd configuration changes (see http://www.cups.org/str.php?L4223 (http://www.cups.org/str.php?L4223), CVE-2012-5519, and https://bugzilla.opensuse.org/show_bug.cgi?id=789566 (https://bugzilla.opensuse.org/show_bug.cgi?id=789566)).

CUPS banners and the CUPS test page are no longer supported since CUPS >= 1.6. The banners and the test page from cups-filters must be used. The CUPS banner files in /usr/share/cups/banners/ and the CUPS testpage /usr/share/cups/data/testprint (which is also a CUPS banner file type) are no longer provided in the cups RPM because they do no longer work since CUPS >= 1.6 (see http://www.cups.org/str.php?L4120 (http://www.cups.org/str.php?L4120) ) because there is no longer a filter that can convert the CUPS banner files. Since CUPS >= 1.6 only the banner files and testpage in the cups-filters package work via the cups-filters PDF workflow and the cups-filters package also provides the matching bannertopdf filter.

For details, see https://bugzilla.opensuse.org/show_bug.cgi?id=735404 (https://bugzilla.opensuse.org/show_bug.cgi?id=735404).

PDF Now Common Printing Data Format

There is a general move away from PostScript to PDF as the standard print job format. This change is advocated by the OpenPrinting workgroup of the Linux Foundation and the CUPS author.

This means that application programs usually no longer produce PostScript output by default when printing but instead PDF.

As a consequence the default processing how application programs printing output is converted into the "language" that the particular printer accepts (the so called "CUPS filter chain") has fundamentally changed from a PostScript-centric workflow to a PDF-centric workflow.

Accordingly the upstream standard for CUPS under Linux (using CUPS plus the cups-filters package) is now PDF-based job processing, letting every non-PDF input be converted to PDF first, page management options being applied by a pdftopdf filter and Ghostscript being called with PDF as input.

With PDF as the standard print job format traditional PostScript printers can no longer print application's printing output directly so that a conversion step in the printing workflow is required that converts PDF into PostScript. But there are also PostScript+PDF printers that can print both PostScript and PDF directly.

For details, see the section "Common printing data formats" in the SUSE wiki article "Concepts printing" at http://en.opensuse.org/Concepts_printing (http://en.opensuse.org/Concepts_printing) .

5 雜項

6 更多資訊與反饋

  • 閱讀安裝 CD 中的 README 檔案。

  • 從 RPM 獲取某個套件詳細的變動歷史資訊:

    rpm --changelog -qp <FILENAME>.rpm

    <FILENAME> 是該套件的名稱。

  • 請查看在安裝 DVD 最上層目錄下的 ChangeLog 檔案以了解所更新套件的變動歷史(按時間先後排序)。

  • 在安裝 DVD 中的 docu 目錄可找到更多的資訊。

  • https://activedoc.opensuse.org/ 包含了額外或是更新的文件。

  • 請造訪 http://www.opensuse.org 以了解 openSUSE 最新的產品訊息。

版權所有 © 2015 SUSE LLC

感謝使用 openSUSE。

openSUSE 團隊

列印此頁面