Debian GNU/Linux 6.0 (squeeze), 32-bit PC 的發行公告 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ The Debian Documentation Project (http://www.debian.org/doc/)     這份文件是自由軟體；您可以在自由軟體基金會所發行的 GNU 通用公共授 權第二版的條款規範下重新發佈及/或修改它。 希望這份文件的發行能對您有所幫助，但不附帶任何保証；甚至不包括因     為商業行為或為了符合特定用途所帶來的隱含保証。詳情請參閱 GNU 通用 公共授權。 您應該和這個程式一起得到一份 GNU 通用公共授權的副本。若沒有，請寫     信到 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA。 The license text can also be found at http://www.gnu.org/licenses     /gpl-2.0.html (http://www.gnu.org/licenses/gpl-2.0.html) and /usr /share/common-licenses/GPL-2 on Debian GNU/Linux. 2010-11-12 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 內容目錄 1. 引言 1.1. 回報這份文件的錯誤 1.2. 提交升級報告 1.3. 這份文件的來源資訊 2. 在 Debian GNU/Linux 6.0 中有什麼新增功能 2.1. 在這次的發行版本中有什麼新變化？ 2.1.1. Firmware moved to the non-free section 2.1.2. 套件管理 2.1.3. Dependency booting 2.1.4. Unified keyboard settings 2.1.5. Kernel mode setting 2.1.6. LDAP support 2.1.7. 升級計劃 2.1.8. The stable-updates section 2.1.9. backports.org/backports.debian.org 2.2. Debian Live 2.3. Comprehensive support for neuroimaging research 3. 系統安裝 3.1. 安裝系統有何改變？ 3.1.1. 主要改變 3.1.2. 自動安裝 4. Upgrades from Debian 5.0 (lenny) 4.1. 系統升級之準備 4.1.1. 備份資料及設定資訊 4.1.2. 事先知會使用者 4.1.3. Prepare for downtime on services 4.1.4. 回復準備 4.1.5. 準備一個安全無虞的環境以進行升級 4.1.6. Remove conflicting packages 4.2. 檢查系統的狀況 4.2.1. 重新檢視在套件管理程式的懸而未決之動作 4.2.2. 關閉 APT 的釘鎖 (Pinning) 功能 4.2.3. 檢查套件的狀態 4.2.4. proposed-updates 4.2.5. 非官方的來源及 backports 4.3. APT 來源之準備工作 4.3.1. 加入網際網路上的 APT 套件來源 4.3.2. 增加 APT 的本機鏡像套件來源 4.3.3. 增加 APT 的 CD-ROM 或 DVD 的套件來源 4.4. 進行套件的升級 4.4.1. 記錄歷程 4.4.2. 更新套件的列表 4.4.3. 確認您有足夠的空間可以用來進行升級 4.4.4. 系統最低限度升級 4.4.5. Upgrading the kernel and udev 4.4.6. Upgrading the system 4.5. 在升級過程中可能會發生的問題 4.5.1. cryptoloop support not included in the squeeze Linux kernel 4.5.2. Expected removals 4.5.3. Errors running aptitude or apt-get 4.5.4. Conflicts or Pre-Depends loops 4.5.5. File conflicts 4.5.6. Configuration changes 4.5.7. Change of session to console 4.5.8. Special care for specific packages 4.6. 替您的 Kernel 及相關套件進行升級 4.6.1. 安裝 Kernel 的虛擬套件 4.6.2. 重新排序裝置列表 4.6.3. 開機時機問題 4.7. 系統開機時當在 Waiting for root file system 4.7.1. 如何在升級之前避開這個問題 4.7.2. 如何在升級後再修復這個問題 4.8. 替下一個釋出版本進行準備 4.8.1. Upgrade to GRUB 2 4.9. Deprecated components 4.10. 被廢棄的套件 4.10.1. 替代 (Dummy) 套件 5. 在 squeeze 裡您必須知道的一些問題 5.1. 潛在的問題 5.1.1. Migration of disk drivers from IDE to PATA subsystem 5.1.2. mdadm metadata format change requires recent Grub 5.1.3. pam_userdb.so breakage with newer libdb 5.1.4. Potential issues with diversions of /bin/sh 5.1.5. Change in kernel policy regarding resource conflicts 5.2. LDAP support 5.3. sieve service moving to its IANA-allocated port 5.4. KDE 桌面 5.4.1. Upgrading from KDE 3 5.4.2. New KDE metapackages 5.5. GNOME 桌面的變更和支援 5.5.1. GDM 2.20 and 2.30 5.5.2. Device and other administrative permissions 5.5.3. network-manager and ifupdown interaction 5.6. Graphics stack changes 5.6.1. Obsolete Xorg drivers 5.6.2. Kernel mode setting 5.6.3. Input device hotplug 5.6.4. X server “zapping” 6. 更多關於 Debian GNU/Linux 的資訊 6.1. 閱讀更多資訊 6.2. 取得協助 6.2.1. 郵件論壇 6.2.2. IRC(Internet Relay Chat) 網路聊天室 6.3. 回報錯誤 6.4. 如何對 Debian 做出貢獻 A. Managing your lenny system before the upgrade A.1. 更新您的 lenny 系統 A.2. 檢查您的來源列表 A.3. Upgrade legacy locales to UTF-8 B. Contributors to the Release Notes 索引 小辭彙 章 1. 引言     This document informs users of the Debian GNU/Linux distribution about major changes in version 6.0 (codenamed squeeze). The release notes provide information on how to upgrade safely     from release 5.0 (codenamed lenny) to the current release and inform users of known potential issues they could encounter in that process. You can get the most recent version of this document from http:// www.debian.org/releases/squeeze/releasenotes (http://     www.debian.org/releases/squeeze/releasenotes) . If in doubt, check the date on the first page to make sure you are reading a current version. 注意     請注意到，要列出所有的已知問題是不可能的任務。因此，這些都是在經 過篩選之後，被認為是普遍存在且重大的問題。 請注意到，在此只會提供及記述從上一個 Debian 發行版本進行升級的資     訊。（也就是說，由 lenny 進行升級）。如果您必須從更為早期的發行版 進行升級的話，我們建議您能參閱舊有的發行情報，並先升級至 lenny。 1.1. 回報這份文件的錯誤 We have attempted to test all the different upgrade steps     described in this document and to anticipate all the possible issues our users might encounter. Nevertheless, if you think you have found a bug (incorrect information or information that is missing) in this documentation, please file a bug in the bug tracking system (http://bugs.debian.org/) against the release-notes package. You     might want to review first the existing bug reports (http:// bugs.debian.org/release-notes) in case the issue you've found has already been reported. Feel free to add additional information to existing bug reports if you can contribute content for this document. We appreciate, and encourage, reports providing patches to the     document's sources. You will find more information describing how to obtain the sources of this document in 節 1.3, “這份文件的來源 資訊”. 1.2. 提交升級報告 我們十分歡迎使用者回報有關由 lenny 升級至 squeeze 的任何資訊。如     果您願意分享這些資訊，請到錯誤回報系統 (http://bugs.debian.org/) 將您的成果向 upgrade-reports 套件發送錯誤回報。我們希望您能先將所 有附加檔案（使用 gzip）壓縮後再進行傳送。     在遞交您的升級報告時，請包含以下資訊： ● The status of your package database before and after the upgrade: dpkg's status database available at /var/lib/dpkg/ status and apt's package state information, available at /var /lib/apt/extended_states. You should have made a backup before the upgrade as described at 節 4.1.1, “備份資料及設定 資訊”, but you can also find backups of /var/lib/dpkg/status     in /var/backups. ● Session logs created using script, as described in 節 4.4.1, “記錄歷程”. ● 可由 /var/log/apt/term.log 取得您的 apt 日誌，或是由 /var/log /aptitude 取得您的 aptitude 日誌。 注     在錯誤回報裡引用這些資訊之前，您應該花點時間去重新檢視這些資訊， 並移除任何敏感及/或私密資料。因為這些資訊將會發佈在公共的資料庫上 。 1.3. 這份文件的來源資訊 The source of this document is in DocBook XML format. The HTML version is generated using docbook-xsl and xsltproc. The PDF version is generated using dblatex or xmlroff. Sources for the Release Notes are available in the SVN repository of the Debian     Documentation Project. You can use the web interface (http:// svn.debian.org/viewsvn/ddp/manuals/trunk/release-notes/) to access its files individually through the web and see their changes. For more information on how to access the SVN please consult the Debian Documentation Project SVN information pages (http://www.debian.org/doc/cvs) . 章 2. 在 Debian GNU/Linux 6.0 中有什麼新增功能     The Wiki (http://wiki.debian.org/NewInSqueeze) has more information about this topic. This release drops official support for the HP PA-RISC ('hppa')     (http://lists.debian.org/debian-devel-announce/2010/09/ msg00008.html) , Alpha ('alpha') and ARM ('arm') architectures.     以下是 Debian GNU/Linux squeeze 官方所支援的硬體平台： ● 32-bit PC ('i386') ● SPARC ('sparc') ● PowerPC ('powerpc') ● MIPS ('mips' (big endian) 及 'mipsel' (little endian))     ● Intel Itanium ('ia64') ● S/390 ('s390') ● 64-bit PC ('amd64') ● ARM EABI ('armel') In addition to the officially supported architectures, Debian GNU /Linux squeeze introduces the GNU/kFreeBSD ports ('kfreebsd-amd64' and 'kfreebsd-i386') as a technology preview. These ports are the first ones included in a Debian release which aren't based on the Linux kernel, but instead use the FreeBSD kernel with a GNU userland. Users of these versions however     should be warned that the quality of these ports is still catching up with the outstanding high quality of our Linux ports, and that some advanced desktop features are not supported yet. However, the support of common server software is strong and extends the features of Linux-based Debian versions by the unique features known from the BSD world. This is the first time a Linux distribution has been extended to also allow use of a non-Linux kernel. 您可以在 Debian 硬體架構網頁 (http://www.debian.org/ports/) 中取     得更多關於各個平台移植的情況，以及針對移植至您的硬體平台的相關資 訊。 2.1. 在這次的發行版本中有什麼新變化？ 比起之前的 lenny，新的 Debian 發行版再度收集了更多的軟體；在這次 的發行版本裡包含了超過 10352 個新套件，總數則超過了 29050 個套件 。大部份的軟體都被更新了：超過 15436 個套件（大約佔了 lenny 的套     件數量的 67%）。當然囉，因為種種的原因，也有不少的軟體（超過 4238 個，大約佔了 lenny 的套件數量的 18%）在這次的發行版本裡被移除掉了 。您會發覺到這些套件的版本已不再更新，並且在套件的管理介面裡它們 會被標記為 '廢棄(obsolete)' 套件。     With this release, Debian GNU/Linux updates from X.Org 7.3 to X.Org 7.5. Debian GNU/Linux again ships with several desktop applications and environments. Among others it now includes the desktop environments GNOME 2.30^[1], KDE 4.4.5, Xfce 4.6.2, and LXDE     0.5.0. Productivity applications have also been upgraded, including the office suites OpenOffice.org 3.2.1 and KOffice 2.2.1 as well as GNUcash 2.2.9, GNUmeric 1.10.8 and Abiword 2.8.2. Updates of other desktop applications include the upgrade to Evolution 2.30.3 and Pidgin 2.7.3. The Mozilla suite has also     been updated: iceweasel (version 3.5.13) is the unbranded Firefox web browser and icedove (version 3.0.7) is the unbranded Thunderbird mail client.     除此之外，在此發行版中也包含了以下的軟體更新： ┌───────────────────────────┬────────────────┬──────────────────┐ │ 套件 │ 在 5.0 (lenny) │ 在 6.0 (squeeze) │ │ │ 裡的版本 │ 裡的版本 │ ├───────────────────────────┼────────────────┼──────────────────┤ │Apache │2.2.9 │2.2.16 │ ├───────────────────────────┼────────────────┼──────────────────┤ │BIND DNS 伺服器 │9.6.0 │9.7.1 │ ├───────────────────────────┼────────────────┼──────────────────┤ │Cherokee web server │0.7.2 │1.0.8 │ ├───────────────────────────┼────────────────┼──────────────────┤ │Courier MTA │0.60.0 │0.63.0 │ ├───────────────────────────┼────────────────┼──────────────────┤ │Dia │0.96.1 │0.97.1 │ ├───────────────────────────┼────────────────┼──────────────────┤ │Ekiga VoIP Client │2.0.12 │3.2.7 │ ├───────────────────────────┼────────────────┼──────────────────┤ │Exim 預設的郵件伺服器 │4.69 │4.72 │ ├───────────────────────────┼────────────────┼──────────────────┤ │GNU 編譯器套裝程式以做為預 │4.3.2 │4.4.5 │ │設的編譯程式 │ │ │ ├───────────────────────────┼────────────────┼──────────────────┤ │GIMP │2.4.7 │2.6.10 │ ├───────────────────────────┼────────────────┼──────────────────┤     │GNU C 函式庫 │2.7 │2.11.2 │ ├───────────────────────────┼────────────────┼──────────────────┤ │lighttpd │1.4.19 │1.4.28 │ ├───────────────────────────┼────────────────┼──────────────────┤ │maradns │1.3.07.09 │1.4.03 │ ├───────────────────────────┼────────────────┼──────────────────┤ │MySQL │5.0.51a │5.1.49 │ ├───────────────────────────┼────────────────┼──────────────────┤ │OpenLDAP │2.4.11 │2.4.23 │ ├───────────────────────────┼────────────────┼──────────────────┤ │OpenSSH │5.1p1 │5.5p1 │ ├───────────────────────────┼────────────────┼──────────────────┤ │PHP │5.2.6 │5.3.2 │ ├───────────────────────────┼────────────────┼──────────────────┤ │Postfix MTA │2.5.2 │2.7.1 │ ├───────────────────────────┼────────────────┼──────────────────┤ │PostgreSQL │8.3.5 │8.4.5 │ ├───────────────────────────┼────────────────┼──────────────────┤ │Python │2.5.2 │2.6.6 │ ├───────────────────────────┼────────────────┼──────────────────┤ │Samba │3.2.5 │3.5.5 │ ├───────────────────────────┼────────────────┼──────────────────┤ │Tomcat │5.5.26 │6.0.28 │ └───────────────────────────┴────────────────┴──────────────────┘ The official Debian GNU/Linux distribution now ships on 4 to 5 binary DVDs or 28 to 32 binary CDs (depending on the architecture) and 4 source DVDs or 28 source CDs. Additionally,     there is a multi-arch DVD, with a subset of the release for the amd64 and i386 architectures, along with the source code. Debian GNU/Linux is also released as Blu-ray images, also for the amd64 and i386 architectures, along with the source code.     Debian still supports Linux Standard Base (LSB) version 3.2. 2.1.1. Firmware moved to the non-free section Some drivers included in the Linux kernel used to contain non-free firmware blobs. Starting from squeeze this firmware has     been moved to separate packages in the non-free section of the archive, such as firmware-linux. If such packages are installed, the firmware will be loaded automatically when required. 2.1.2. 套件管理 The preferred program for interactive package management from a terminal is aptitude. For a non-interactive command line     interface for package management, it is recommended to use apt-get. apt-get is also the preferred tool for upgrades between major releases. If you are still using dselect, you should switch to aptitude as the official front-end for package management. For squeeze APT automatically installs recommended packages by default^[2]. This can be changed by adding the following line in     /etc/apt/apt.conf: APT::Install-Recommends "false"; 2.1.3. Dependency booting An important improvement in the Debian GNU/Linux boot system is     the introduction of dependency-based boot sequencing and parallel boot. This feature is enabled by default in new installs and it will be enabled for upgrades from lenny, if possible. This feature is enabled through the use of insserv by sysv-rc to order init.d scripts based on their declared dependencies^[3]. It     has been possible after a sustained effort to adapt all the boot scripts of packages provided in the distribution as well as the boot system itself. With dependency-based boot sequencing it is also now possible to run the boot system scripts in parallel which can, under most circumstances, improve the speed of the boot process. This feature is enabled by default, in new systems and upgrades, whenever possible. To disable it specify     CONCURRENCY=none in /etc/default/rcS. For more information on this feature refer to the information available in /usr/share/doc/insserv/ README.Debian. 2.1.4. Unified keyboard settings In this new release, the settings for the keyboard have been unified so that both the console and the Xorg server use the same     settings. The keyboard settings are now defined in the /etc/ default/keyboard configuration file which overrides the keyboard defined in Xorg's configuration file. The console-setup package now handles the keyboard for both environments as well as the font configuration for the console.     You can reconfigure the keyboard layout and related settings by executing dpkg-reconfigure keyboard-configuration or by manually editing the /etc/default/keyboard configuration file. 2.1.5. Kernel mode setting Graphics mode setting code for the most common desktop chipsets (from Intel, ATI/AMD and NVIDIA) has moved from the respective Xorg drivers to the Linux kernel. This provides a number of advantages, such as:     ● More reliable suspend and resume ● Ability to use graphics devices without X ● Faster VT switch ● Native mode text console     More details are in 節 5.6, “Graphics stack changes” and in the Debian wiki (http://wiki.debian.org/KernelModesetting) . 2.1.6. LDAP support     This Debian release comes with several options for implementing     client-side authentication using LDAP. Users of the libnss-ldap and libpam-ldap packages should consider upgrading to libnss-ldapd and libpam-ldapd. These newer packages delegate the LDAP queries to a central unprivileged daemon (nslcd) that provides separation between the process using the LDAP information and the daemon performing LDAP     queries. This simplifies handling of secured LDAP connections, LDAP authentication credentials, provides a simpler mechanism to perform connection fail-over and debugging and avoids loading LDAP and related libraries into most applications. Upgrading to libnss-ldapd and libpam-ldapd should be easy as     existing configuration information will be mostly reused. Only for advanced configuration should any manual reconfiguration be necessary. These packages however currently lack support for nested groups     and only support password change using the LDAP password modify EXOP operation. 2.1.7. 升級計劃 All changes to the released stable distribution (and to oldstable) go through an extended testing period before they are     accepted into the archives. Each such update of the stable (or oldstable) release is called a point release. Preparation of point releases is done through the proposed-updates mechanism. Packages can enter proposed-updates in two ways. Firstly, security-patched packages added to security.debian.org are automatically added to proposed-updates as well. Secondly, Debian     GNU/Linux developers may upload new packages to proposed-updates, where they get added after review by the Stable Release Managers. The current list of packages can be seen at http:// ftp-master.debian.org/proposed-updates.html (http:// ftp-master.debian.org/proposed-updates.html) .     如果在這些套件正式加入小改版之前您想要幫忙測試這些更新的話，您可 以將 proposed-updates 區段加入您的 sources.list裡：     deb http://mirrors.kernel.org/debian squeeze-proposed-updates main contrib deb-src http://mirrors.kernel.org/debian squeeze-proposed-updates main contrib The next time you run apt-get update, the system will become     aware of the packages in the proposed-updates section and will consider them when looking for packages to upgrade.     這嚴格來說並不是 Debian 的新功能，只是之前不太為人所知罷了。 2.1.8. The stable-updates section Some packages from proposed-updates may also be made available via the squeeze-updates mechanism. This path will be used for     updates which many users may wish to install on their systems before the next point release is made, such as updates to virus scanners and timezone data. All packages from squeeze-updates will be included in point releases.     Note that this replaces the functionality previously provided by the volatile.debian.org archive (http://volatile.debian.org/) .     In order to use packages from squeeze-updates, you can add an entry to your sources.list:     deb http://mirrors.kernel.org/debian squeeze-updates main contrib deb-src http://mirrors.kernel.org/debian squeeze-updates main contrib The next time you run apt-get update, the system will become     aware of the packages in the squeeze-updates section and will consider them when looking for packages to upgrade. When a new package is made available via squeeze-updates, this     will be announced on the debian-stable-announce (http:// lists.debian.org/debian-stable-announce/) mailing list. 2.1.9. backports.org/backports.debian.org The service provided by the backports.org repositories has been     integrated in Debian infrastructure and is now an official Debian service (http://www.debian.org/News/2010/20100905) , hosted at backports.debian.org (http://backports.debian.org/) . 2.2. Debian Live     With squeeze Debian provides official Live systems for the amd64 and i386 architectures. A Debian Live system is a Debian system that can be booted directly from removable media (CD-ROMs, DVDs, USB keys) or from another computer over the network without the need of     installation. The images are produced by a tool named live-build, which can easily be used to create custom live images. More information about the Debian Live project can be found at http:// live.debian.net/ (http://live.debian.net/) . 2.3. Comprehensive support for neuroimaging research Debian GNU/Linux 6.0 is the first GNU/Linux distribution release ever to offer comprehensive support for magnetic resonance imaging (MRI) based neuroimaging research. It comes with up-to-date software for structural image analysis (e.g. ants), diffusion imaging and tractography (e.g. mrtrix), stimulus delivery (e.g. psychopy), MRI sequence development (e.g. odin),     as well as a number of versatile data processing and analysis suites (e.g. nipype). Moreover, this release has built-in support for all major neuroimaging data formats. See the Debian Science (http://blends.alioth.debian.org/science/tasks/ neuroscience-cognitive) and Debian Med (http:// debian-med.alioth.debian.org/tasks/imaging) task pages for a comprehensive list of included software and the NeuroDebian webpage (http://neuro.debian.net) for further information. ━━━━━━━━━━━━━━     ^[1] With some modules from GNOME 2.32. ^[2] This change implies that disk requirements for tasks selected through the debian installer have increased too. For     more information please see the “Disk Space Needed for Tasks” chapter in the Installation Guide (http://www.debian.org/releases /stable/installmanual) .     ^[3] These dependences are declared through the use of the header format specified in the Linux Standard Base (LSB) 章 3. 系統安裝     Debian Installer 是 Debian 的官方安裝系統。它提供了多種不同的安裝 方式。您可以依據您硬體架構的不同而有種種不同的安裝方式可供選擇。     可以在 Debian 站台 (http://www.debian.org/releases/stable/ debian-installer/) 上同時取得 squeeze 的安裝影像檔以及安裝指引。     安裝指引也同時會包含在 Debian 官方的 CD/DVD 集裡的第一張 CD/DVD 的：     /doc/install/manual/language/index.html 您還可以到戡誤表 (http://www.debian.org/releases/stable/     debian-installer/index#errata) 上查看 debian-installer 的一些已知 問題之列表。 3.1. 安裝系統有何改變？ There has been a lot of development on the Debian Installer since     its first official release with Debian GNU/Linux 3.1 (sarge) resulting in both improved hardware support and some exciting new features. 在本發行情報裡，我們只會列出在安裝程式裡的一些重大改變。如果您想     知道在 lenny 之後它的一些詳盡的改變列表，請檢閱在 Debian Installer 的新聞歷程 (http://www.debian.org/devel/ debian-installer/News/) 上有關 squeeze beta 及 RC 版發行公告。 3.1.1. 主要改變 Dropped platforms Support for the Alpha ('alpha'), ARM ('arm') and HP PA-RISC ('hppa') architectures has been dropped from the installer. The 'arm' architecture is obsoleted by the ARM EABI ('armel') port. Support for kFreeBSD The installer can be used to install the kFreeBSD instead of the Linux kernel and test the technology preview. To use this feature the appropriate installation image (or CD/DVD set) has to be used. GRUB 2 is the default bootloader The bootloader that will be installed by default is grub-pc (GRUB 2). Help during the installation process The dialogs presented during the installation process now provide help information. Although not currently used in all dialogs, this feature would be increasingly used in future releases. This will improve the user experience during the installation process, especially for new users. Installation of Recommended packages The installation system will install all recommended packages by default throughout the process except for some specific situations in which the general setting gives undesired results. Automatic installation of hardware-specific packages The system will automatically select for installation hardware-specific packages when they are appropriate. This is achieved through the use of discover-pkginstall from the discover package. Support for installation of previous releases The installation system can be also used for the installation of previous release, such as lenny. Improved mirror selection The installation system provides better support for installing both squeeze as well as lenny and older releases (through the use of archive.debian.org). In addition, it will also check that the selected mirror is consistent and holds the selected release. Changes in partitioning features This release of the installer supports the use of the ext4 file system and it also simplifies the creation of RAID, LVM and crypto protected partitioning systems. Support for the reiserfs file system is no longer included by default, although it can be optionally loaded.     Support for loading firmware debs during installation It is now possible to load firmware package files from the installation media in addition to removable media, allowing the creation of PXE images and CDs/DVDs with included firmware packages. Starting with Debian 6.0, non-free firmware has been moved out of main. To install Debian on hardware that needs non-free firmware, you can either provide the firmware yourself during installation or use pre-made non-free CDs/ DVDs which include the firmware. See the Getting Debian section (http://www.debian.org/distrib) on the Debian website for more information. 新語系 Thanks to the huge efforts of translators, Debian GNU/Linux can now be installed in 67 languages. This is three more languages than in lenny. Most languages are available in both the text-based installation user interface and the graphical user interface, while some are only available in the graphical user interface. Languages added in this release include: ● Asturian, Estonian, Kazakh and Persian have been added to the graphical and text-based installer. ● Kannada and Telugu have been added to the graphical installer. ● Thai, previously available only in the graphical user interface, is now available also in the text-based installation user interface too. Due to the lack of translation updates two languages were dropped in this release: Wolof and Welsh. Improved localisation selection The selection of localisation-related values (language, location and locale settings) is now less interdependent and more flexible. Users will be able to customize the system to their localisation needs more easily while still make it comfortable to use for users that want to select the locale most common for the country they reside in. Additionally, the consequences of localisation choices (such as timezone, keymap and mirror selection) are now more obvious to the user. Live system installation The installer now supports live systems in two ways. First, an installer included on live system media can use the contents of the live system in place of the regular installation of the base system. Second, the installer may now be launched while running the live system, allowing the user to do other things with the live system during the install. Both features are built into the Debian Live images offered at http://cdimage.debian.org/ (http:// cdimage.debian.org/) . 3.1.2. 自動安裝 在之前的章節中所提到了許多的改變，其中也包含了在安裝程式裡利用事     先準備好的設定檔來進行自動安裝。這意謂著，如果您手上有著用來和 lenny 安裝程式搭配使用的事先準備好的設定檔，若未經修改將難以和新 的安裝程式搭配使用。 在安裝指引 (http://www.debian.org/releases/stable/installmanual)     上已有更新了的獨立附錄，上有如何使用事先準備好的設定檔之大量資訊 。 章 4. Upgrades from Debian 5.0 (lenny) 4.1. 系統升級之準備 在進行升級之前，我們建議您能同時參閱章 5, 在 squeeze 裡您必須知道     的一些問題所提供的資訊。在那個章節裡包含了一些和升級程序無直接相 關，但在開始之前您仍然得要知道的可能潛在問題。 4.1.1. 備份資料及設定資訊 在升級您的系統之前，我們強烈建議您能進行一次完整的備份，或至少您     也應該把那些絕對不能出任何差錯的資料和設定資訊給備份起來。升級時 所使用的工具和升級過程應該不會出什麼差錯，但在升級過程中若發生了 什麼硬體錯誤可能會導致系統嚴重受損。 The main things you'll want to back up are the contents of /etc, /var/lib/dpkg, /var/lib/apt/extended_states and the output of     dpkg --get-selections "*" (the quotes are important). If you use aptitude to manage packages on your system, you will also want to back up /var/lib/aptitude/pkgstates. 這個升級的程序它本身並不會修改在 /home 目錄裡的任何資料，但是已知 有某些應用程式（例如：部份的 Mozilla 家族程式及 GNOME、KDE 桌面環 境）在使用者第一次以新的版本啟動時，會以新的預設值覆蓋使用者原有     的設定。為了以防萬一，您也許想要針對在使用者的主目錄裡的隱藏檔案 及目錄（“dotfiles”，以 . 開頭的檔案或目錄）進行備份。這個備份可以 用來回復或重新建立舊有的設定。您也許有必要讓使用者知道有這個問題 存在。 Any package installation operation must be run with superuser     privileges, so either log in as root or use su or sudo to gain the necessary access rights.     升級有其必要條件，您應該在實地進行升級之前先行確認一次。 4.1.2. 事先知會使用者 您應該在進行任何升級之前先把您的計畫告知所有使用者，雖然一些像是 利用 ssh 連線來從遠端存取系統的使用者在升級過程中可能不會發現什麼     異狀，且他們的工作也應該不會因而中斷。如果您希望能採取額外的預防 措施的話，請在升級前備份或卸載使用者的分割區 (/home)。除非您計劃 同時進行 Kernel 的升級，否則您在升級前後通常並不需要重新開機。     If you wish to take extra precautions, back up or unmount the / home partition before upgrading.     You will have to do a kernel upgrade when upgrading to squeeze, so a reboot will be necessary. 4.1.3. Prepare for downtime on services During the upgrade process, there might be services associated with packages that will be include in the upgrade. If this is the     case, these services might be stopped while the packages that are going to be upgraded are being replaced and configured. During this time, these services will not be available. The precise downtime for these service will vary depending on the number of packages being upgraded in the system, and it also includes the time the system administrator answers the     configuration questions from different package upgrades (if any). Notice that if the upgrade process is left unattended and the system requests input throughout the upgrade there is a high possibility of services being unavailable^[4] for a significant period of time. If the system being upgraded provides critical services for your users or network^[5], you can reduce the downtime if you do a minimal system upgrade, as described in 節 4.4.4, “系統最低限度升 級”, followed by a kernel upgrade and reboot (see 節 4.4.5,     “Upgrading the kernel and udev”), and then upgrade the packages associated with your critical services. Upgrade these packages prior to doing the full upgrade described in 節 4.4.6, “Upgrading the system”. This way you can ensure that these critical services are running and available through the full upgrade process, and their downtime is reduced. 4.1.4. 回復準備 由於 lenny 和 squeeze 間的 kernel 在像是驅動程式、硬體偵測、命名     方式及裝置檔的順序上之變動太大了，在升級完成之後、重新啟動系統之 時，您必須冒著可能會遭遇問題的風險。一些已知的可能問題記述於發行 情報中的這個及下個章節。     也因此，當您的系統可能會再也無法開機，或者是無法啟用網路（對於遠 端管理系統而言）之時，確保您有辨法進行回復就變得很重要了。 如果您是藉由 ssh 連線來從遠端進行更新的話，在此非常建議您能採取必 要的預防措施，讓您能有辨法經由遠端序列終端來存取伺服器。這是因為     偶爾在升級 Kernel 並重新開機之後，有些裝置的名稱被改變了（如同節  4.6.2, “重新排序裝置列表” 裡的說明），導致您得經由本機主控台才能 修正系統的設定。同樣的，如果系統在升級途中意外得重新開機了，您將 可能得由本機主控台才能進行修復。     第一個最顯而易見的方法是試著用您舊的 Kernel 開機，儘管如此，由於 在本文件其它地方所陳述的種種原因，這個方法無法保証一定有效。 如果這個方法失敗了，您必須另尋其它方式來啟動您的系統，讓您可以進     行存取並修復它。方法之一是利用特定的救援影像檔或 Linux 的 live CD 。利用它們開機之後，您應該可以掛載您的 root 檔案系統並 chroot 進 去以檢查並修復問題。 另一個我們建議的作法是使用 squeeze Debian 安裝程式的 rescue mode 。使用安裝程式的好處是您可以在它所提供的許多安裝方式中選擇一個最     符合您的狀況的方式。請參閱在 Installation Guide (http:// www.debian.org/releases/stable/installmanual) 的第 8 節“回復毀損 的系統”及 Debian Installer FAQ (http://wiki.debian.org/ DebianInstaller/FAQ) 以取得更詳盡的資訊。 4.1.4.1. 在開機過程中使用 initrd 的除錯介面 (debug shell) initramfs-tools 會在它所產生的 initrds 裡放入一個 debug shell^[6]     。比如說，當您無法掛載您的 root 檔案系統時，您會進入這個提供了一 些基本功能的 debug shell，以用來追蹤問題並試著修復它。 基本的檢查包括了：在 /dev 中是否有出現正確的裝置檔；已載入了哪些 模組（cat /proc/modules）；在 dmesg 的輸出裡是否有驅動無法載入的     資訊。在 dmesg 的輸出裡也會顯示了哪個裝置檔已被指定為使用哪個磁碟 ；您應該把它和 echo $ROOT 的輸出進行比較以確保 root 檔案系統是掛 載在正確的裝置上。 如果您已採取行動解決問題，鍵入 exit 將會跳出除錯介面並會由開機失     敗的地方繼續進行開機。當然了，您也必須由根本修復問題並重新產生 initrd，讓下次開機時不會又因而失敗。 4.1.5. 準備一個安全無虞的環境以進行升級     您應該在本機透過文字模式的虛擬主控台（或直接連線的序列終端機）、 或由遠端透過 ssh 連線來進行發行版間的升級。 重要     If you are using some VPN services (such as tinc) they might not be available throughout the upgrade process. Please see 節 4.1.3, “Prepare for downtime on services”. 在以遠端進行更新時，為了能得到更多的安全保障，在此建議您在 screen     程式所提供的虛擬主控台裡進行升級程序。它能夠讓您一再地重複連線， 以確保如果遠端連線中斷時，也不會干擾到升級程序的進行。 重要     您不應該透過 telnet、rlogin、rsh，或是由您要進行升級的機器上的 xdm、gdm 或 kdm 等等所管理的 X 行程來進行升級。這是因為這些服務在 升級的過程中都可能會被中斷，因而將會留下了一個只完成部分升級而無 法存取的系統。 4.1.6. Remove conflicting packages Due to bug #512951 (http://bugs.debian.org/512951) , the splashy     package needs to be purged prior to the upgrade. # apt-get purge splashy 4.2. 檢查系統的狀況 在這個章節中所說明的升級過程是專門為“純粹的” lenny 所寫的，也就是     在系統中沒有安裝任何其它協力套件。為了確保升級程序能平順進行，您 也許會希望在升級之前先從系統裡移除那些協力套件。 Direct upgrades from Debian releases older than 5.0 (lenny) are     not supported. Please follow the instructions in the Release Notes for Debian GNU/Linux 5.0 (http://www.debian.org/releases/ lenny/releasenotes) to upgrade to 5.0 first. 而在這個過程中也假設您的系統已更新至 lenny 的最新釋出版本。如果您     尚未完成或是您根本無從確定，請遵循在節 A.1, “更新您的 lenny 系統” 裡的相關說明。 4.2.1. 重新檢視在套件管理程式的懸而未決之動作 在某些情況下，使用 apt-get 而不是 aptitude 來安裝套件可能會讓     aptitude 認為某個套件是“無用”的且會計劃要將其移除。一般來說，您應 該在進行升級程序前確保系統已完全更新且“乾淨”。 Because of this you should review if there are any pending actions in the package manager aptitude. If a package is     scheduled for removal or update in the package manager, it might negatively impact the upgrade procedure. Note that correcting this is only possible if your sources.list still points to lenny and not to stable or squeeze; see 節 A.2, “檢查您的來源列表”. To perform this review, launch aptitude in “visual mode” and press g (“Go”). If it shows any actions, you should review them     and either fix them or implement the suggested actions. If no actions are suggested you will be presented with a message saying “No packages are scheduled to be installed, removed, or upgraded”. 4.2.2. 關閉 APT 的釘鎖 (Pinning) 功能 如果您將 APT 設定為可以安裝除了 stable 發行版之外的套件，（像是： testing），您可能必須修改您的 APT 的釘鎖 (Pinning) 設定（儲存於 /     etc/apt/preferences 中）來讓將要進行升級的套件能夠升級至新的 stable 發行版。您可以在 apt_preferences(5) 取得 APT 的釘鎖功能的 更多詳盡資訊。 4.2.3. 檢查套件的狀態 不論您是用什麼方式進行系統的更新，我們都建議您先檢查所有套件的狀     態，並確認所有的套件都能夠順利升級。以下的指令會顯示所有狀態為半 安裝 (Half-Installed) 或設定失敗 (Failed-Config) 或有其他任何錯誤 的套件。     # dpkg --audit     除此之外，檢查系統中所有套件狀態的方法還包括使用使用 dselect、 aptitude、或是利用以下的指令：     # dpkg -l | pager     或是     # dpkg --get-selections "*" > ~/curr-pkgs.txt 最佳的做法是在進行系統升級前將所有的套件解除保留 (hold) 狀態。如     果在升級過程中有任何的關鍵套件的狀態被設定為保留，那麼升級的作業 就會失敗。 請注意到，aptitude 使用了和 apt-get 及 dselect 迥然不同的方式來登     錄哪些是保留套件。您可以使用以下方式來確認在 aptitude 裡有哪些套 件是被保留住的：     # aptitude search "~ahold" | grep "^.h"     如果您想要檢查那些套件是被 apt-get 所保留住的，請使用：     # dpkg --get-selections | grep hold 如果您自行在系統中變更並重新編譯了某個套件，但卻沒有將其更名或在     版本號碼中使用 epoch（自行定義版本號碼），那您就必須把它設定為保 留狀態，以防止它被升級到新的版本。     The “hold” package state for apt-get can be changed using:     # echo package_name hold | dpkg --set-selections     Replace hold with install to unset the “hold” state.     如果還有什麼地方尚待修正，最好再次確認您的 sources.list 仍然是指 向 lenny，如同節 A.2, “檢查您的來源列表” 裡的說明。 4.2.4. proposed-updates 如果您有把 proposed-updates 區段加入了您的 /etc/apt/sources.list     檔中的話，您應當在進行系統升級之前把它從檔案中移除。這是降低潛在 的衝突發生前的預防工作。 4.2.5. 非官方的來源及 backports 如果在您的系統裡安裝了不是由 Debian 所提供的套件，您必須要知道， 在升級的過程中它們可能會因為相依性的關係而被移除掉。如果這些套件     是先在 /etc/apt/sources.list 新增了額外的套件檔案庫然後再加以安裝 的，您應該檢查一下那個檔案庫是否也提供了特別為 squeeze 而編譯的套 件，在替 Debian 變更套件來源時也同時適當得修改這些套件的來源項目 。 也許有些使用者會在他們的 lenny 上安裝了在 Debian 已有套件的非官方     但“較新”的 backported 版本。這些套件很可能在升級的時候產生檔案衝 突的問題，^[7]。在節 4.5, “在升級過程中可能會發生的問題” 有一些當 發生了檔案衝突時該如何解決的資訊。 4.3. APT 來源之準備工作     在開始進行升級之前，您必須先在 apt 的設定檔 /etc/apt/sources.list 中設定套件列表。 apt will consider all packages that can be found via any “deb” line, and install the package with the highest version number,     giving priority to the first line in the file (thus where you have multiple mirror locations, you'd typically first name a local hard disk, then CD-ROMs, and then HTTP/FTP mirrors). 發行版通常可以使用它的代碼（如，lenny、squeeze）或是它的狀態名稱 （如，oldstable、stable、testing、unstable）來表示。使用發行版的     代碼有個好處是您將不用為了新的發行版的到來而感到不安，這也是為什 麼會在此提出這個技巧的原因。理所當然的，這也表示了您必須自行去注 意發行版是何時發佈的。如果您是替而使用狀態名稱的，在新的發行版發 佈的同時，您將會立即發覺大量套件已有新的版本可供更新。 4.3.1. 加入網際網路上的 APT 套件來源 雖然系統的預設設定是使用 Debian 在網際網路上的主要伺服器來進行安     裝，但您還是可能會希望修改 /etc/apt/sources.list 來改為使用在網路 上離您最近的其它鏡像站。 您也可以在 http://www.debian.org/distrib/ftplist (http://     www.debian.org/distrib/ftplist) 取得 Debian 的 HTTP 或 FTP 鏡像站 的位址（請參考 “list of mirrors” 小節）。HTTP 鏡像站的傳輸速度通 常會比 FTP 鏡像站來得快。 舉例來說，假設離您最近的 Debian 鏡像站是 http://     mirrors.kernel.org。當您透過網頁瀏覽器或 FTP 程式來檢視這個網站時 ，您會發現其中的主要目錄架構會像是這個樣子：     http://mirrors.kernel.org/debian/dists/squeeze/main/binary-i386/... http://mirrors.kernel.org/debian/dists/squeeze/contrib/binary-i386/...     為了要讓 apt 能夠使用這個鏡像站，請把以下的這一行加入您的 sources.list 檔案之中：     deb http://mirrors.kernel.org/debian squeeze main contrib     請注意，`dists' 將會被自動加到路徑中，而在發佈代號之後的參數則會 被用來展開成多個不同目錄的路徑。     在加入了新的來源之後，請在 sources.list 中原本的 “deb” 項目前加上 井字符號 (#) 以關閉這些套件來源。 4.3.2. 增加 APT 的本機鏡像套件來源 您可能也會想修改 /etc/apt/sources.list 中的設定，以使用本機（像是     透過 NFS 掛載的）磁碟上的鏡像資料來取代透過 HTTP 或 FTP 存取遠端 的套件鏡像站。     舉例來說，如果您的套件鏡像是放在 /var/ftp/debian/ 之下，而主要的 目錄看起來是像這樣的話：     /var/ftp/debian/dists/squeeze/main/binary-i386/... /var/ftp/debian/dists/squeeze/contrib/binary-i386/...     如果要和 apt 搭配使用，請把下行加入 sources.list 檔案之中：     deb file:/var/ftp/debian squeeze main contrib     請注意，`dists' 將會被自動加到路徑中，而在發佈代號之後的參數則會 被用來展開成多個不同目錄的路徑。     在加入了新的來源之後，請在 sources.list 中原本的 “deb” 項目前加上 井字符號 (#) 以關閉這些套件來源。 4.3.3. 增加 APT 的 CD-ROM 或 DVD 的套件來源     如果光碟是唯一您想使用的媒體，請在 /etc/apt/sources.list 中原有的 “deb” 設定行前加入井字符號 (#) 以關閉這些套件來源。 請確定在 /etc/fstab 中有著能讓您的光碟機掛載在 /cdrom 這個掛載點     下的項目（apt-cdrom 限定掛載點必須是 /cdrom）。舉例來說，如果您的 光碟機的裝置是 /dev/hdc，那麼 /etc/fstab 中就應該要有像這樣的一行 ：     /dev/hdc /cdrom auto defaults,noauto,ro 0 0     請注意在第四欄的 defaults,noauto,ro 的字中間一定不能參雜空白字元 。     要確認您的設定是否正確，請放入一張光碟片，並試著執行 # mount /cdrom # 這樣將會將這張 CD 掛載在該掛載點上     # ls -alF /cdrom # 這樣將會列出 CD 的根目錄 # umount /cdrom # 這樣將會卸載這張 CD     接下來對每一張 Debian 的程式光碟執行     # apt-cdrom add     來把每一張光碟的資料加到 APT 的資料庫中。 4.4. 進行套件的升級 The recommended way to upgrade from previous Debian GNU/Linux releases is to use the package management tool apt-get. In     previous releases, aptitude was recommended for this purpose, but recent versions of apt-get provide equivalent functionality and also have shown to more consistently give the desired upgrade results.     不要忘了用類似以下的指令把所有會用到的分割區（特別是 /usr 和 root 分割區）重新以可讀寫的模式掛載：     # mount -o remount,rw /mountpoint 接下來，您必須再次確認在 /etc/apt/sources.list 中的 APT 來源項目 是指向 “squeeze” 或是 “stable”，且應該沒有任何來源項目是指向 lenny。 ┌──────────────────────────────────────────────────┐     │注 │ │ │ │Source lines for a CD-ROM might sometimes refer to│ │“unstable”; although this may be confusing, you │ │should not change it. │ └──────────────────────────────────────────────────┘ 4.4.1. 記錄歷程 我們強烈建議您使用 /usr/bin/script 這個程式來記錄升級的完整過程。     因為一旦發生了任何問題，您手上就會有發生了什麼問題的確實記錄，而 在必要之時，在錯誤報告中也能據此提供確實的資訊。若要開始進行記錄 ，請使用     # script -t 2>~/upgrade-squeeze.time -a ~/upgrade-squeeze.script 或類似的指令。請不要把記錄檔放在像是 /tmp 或 /var/tmp 之類的暫存     目錄下（這些目錄中的檔案可能會在升級的過程中或在重新開機時被清除 掉）。 The typescript will also allow you to review information that has     scrolled off-screen. If you are at the system's console, just switch to VT2 (using Alt+F2) and, after logging in, use less -R ~root/upgrade-squeeze.script to view the file.     在您完成升級作業後，您可以藉由在命令列上鍵入 exit 來關閉 script。     如果您在 script 上使用了 -t 參數，您可以利用 scriptreplay 程式來 重新播放整個過程：     # scriptreplay ~/upgrade-squeeze.time ~/upgrade-squeeze.script 4.4.2. 更新套件的列表     首先，必須先取得在新釋出版上的可取用的套件列表。這可以利用以下指 令進行：     # apt-get update 4.4.3. 確認您有足夠的空間可以用來進行升級 You have to make sure before upgrading your system that you have sufficient hard disk space when you start the full system upgrade described in 節 4.4.6, “Upgrading the system”. First, any package needed for installation that is fetched from the network is stored in /var/cache/apt/archives (and the partial/ subdirectory, during download), so you must make sure you have enough space on     the file system partition that holds /var/ to temporarily download the packages that will be installed in your system. After the download, you will probably need more space in other file system partitions in order to both install upgraded packages (which might contain bigger binaries or more data) and new packages that will be pulled in for the upgrade. If your system does not have sufficient space you might end up with an incomplete upgrade that might be difficult to recover from. apt-get can show you detailed information of the disk space     needed for the installation. Before executing the upgrade, you can see this estimate by running: # apt-get -o APT::Get::Trivial-Only=true dist-upgrade [ ... ]     XXX upgraded, XXX newly installed, XXX to remove and XXX not upgraded. Need to get xx.xMB of archives. After this operation, AAAMB of additional disk space will be used. 注 Running this command at the beginning of the upgrade process may     give an error, for the reasons described in the next sections. In that case you will need to wait until you've done the minimal system upgrade as in 節 4.4.4, “系統最低限度升級” and upgraded your kernel before running this command to estimate the disk space.     If you do not have enough space for the upgrade, apt-get will warn you with a message like this:     E: You don't have enough free space in /var/cache/apt/archives/.     In this situation, make sure you free up space beforehand. You can: ● Remove packages that have been previously downloaded for installation (at /var/cache/apt/archives). Cleaning up the package cache by running apt-get clean will remove all previously downloaded package files. ● Remove forgotten packages. If you have popularity-contest installed, you can use popcon-largest-unused to list the packages you do not use that occupy the most space. You can also use deborphan or debfoster to find obsolete packages (see 節 4.10, “ 被廢棄的套件” ). Alternatively you can start aptitude in “visual mode” and find obsolete packages under “Obsolete and Locally Created Packages”. ● Remove packages that take up too much space and are not currently needed (you can always reinstall them after the upgrade). You can list the packages that take up the most disk space with dpigs (available in the debian-goodies package) or with wajig (running wajig size). You can list packages that take up most of the disk space with aptitude. Start aptitude in “visual mode”, select Views → New Flat Package List, press l and enter ~i, press S and enter ~installsize, then it will give you nice list to work with. ● Remove translations and localization files from the system if they are not needed. You can install the localepurge package and configure it so that only a few selected locales are kept in the system. This will reduce the disk space consumed at /usr/share/ locale. ● 把存放在 /var/log/ 裡的系統記錄檔暫時移至其它的系統，或是乾脆刪除 它們。 ● 使用暫時的 /var/cache/apt/archives：您可以使用位於另一個檔案系統 （USB 儲存裝置、暫用的硬碟、正在使用中的檔案系統...）上的暫存快取     目錄。 ┌─────────────────────────────────────────────────────┐ │注 │ │ │ │不要使用 NFS 掛載點，因為網路連線可能會在升級的過程中│ │中斷。 │ └─────────────────────────────────────────────────────┘ 比如說，如果您有個 USB 裝置掛載在 /media/usbkey 上： 1. 移除之前在安裝時所下載的套件： # apt-get clean 2. 把 /var/cache/apt/archives 目錄複製到 USB 裝置： # cp -ax /var/cache/apt/archives /media/usbkey/ 3. 將暫存快取目錄掛載到該目錄上： # mount --bind /media/usbkey/archives /var/cache/apt/archives 4. 在升級完畢後，還原原本的 /var/cache/apt/archives 目錄： # umount /media/usbkey/archives 5. 移除剩下的 /media/usbkey/archives。 您可以在任何已掛載於您的系統的檔案系統上建立暫存快取目錄。 ● Do a minimal upgrade of the system (see 節 4.4.4, “系統最低限度升 級”) or partial upgrades of the system followed by a full upgrade. This will make it possible to upgrade the system partially, and allow you to clean the package cache before the full upgrade.     請注意到，為了能夠安全得移除套件，最好將您的 sources.list 換回 lenny，如同節 A.2, “檢查您的來源列表” 裡的說明。 4.4.4. 系統最低限度升級 In some cases, doing the full upgrade (as described below) directly might remove large numbers of packages that you will     want to keep. We therefore recommend a two-part upgrade process, first a minimal upgrade to overcome these conflicts, then a full upgrade as described in 節 4.4.6, “Upgrading the system”.     To do this first, run:     # apt-get upgrade     這樣會將那些在升級過程中不需要移除或安裝到其它套件的套件進行升級 。 The minimal system upgrade can also be useful when the system is     tight on space and a full upgrade cannot be run due to space constrains. 4.4.5. Upgrading the kernel and udev The udev version in squeeze requires a kernel of version 2.6.26 or newer with the CONFIG_SYSFS_DEPRECATED option disabled and the CONFIG_INOTIFY_USER and CONFIG_SIGNALFD options enabled. Because     the standard Debian kernels in lenny (version 2.6.26) have CONFIG_SYSFS_DEPRECATED enabled, and the udev version in lenny will not provide all the functionality expected by the latest kernels, special care must be taken when upgrading to avoid putting your system in an unbootable state. Booting the 2.6.26 kernel from lenny with the udev from squeeze may result in a failure to correctly assign names to network devices, and will also fail to apply certain additional permissions to block devices (such as access by the disk group).     The software itself will appear to be working, but some rules (for example, network-based rules) will not be loaded properly. It is therefore strongly recommended that you upgrade the kernel on its own at this point, to ensure a compatible kernel is available before upgrading udev.     要進行 kernel 的升級，請執行：     # apt-get install linux-image-2.6-flavor     請參閱節 4.6.1, “安裝 Kernel 的虛擬套件” 來幫助您決定您該安裝的 kernel 套件的類別。     Users of the grub bootloader should make sure that update-grub is run as part of the kernel upgrade, or run it manually. Immediately after upgrading the kernel, you should also install     the new udev to minimize the risk of other incompatibilities caused by using the old udev with a new kernel ^[8]. You can do this by running:     # apt-get install udev     Once you have upgraded both the kernel and udev the system should be rebooted. 4.4.6. Upgrading the system     Once you have taken the previous steps, you are now ready to continue with the main part of the upgrade. Execute:     # apt-get dist-upgrade 注     The upgrade process for other releases recommended the use of aptitude for the upgrade. This tool is not recommended for upgrades from lenny to squeeze. 這將會在您的系統上進行完整的更新，也就是安裝所有套件目前所提供的     最新版本，並解決套件在不同發行版之間可能會有的相依性問題。如果有 必要的話，它也會安裝一些新的套件（通常是新版的函式庫或是被更名的 套件），並移除任何和新版套件發生衝突的過時套件。 When upgrading from a set of CD-ROMs (or DVDs), you will be asked     to insert specific CDs at several points during the upgrade. You might have to insert the same CD multiple times; this is due to inter-related packages that have been spread out over the CDs. New versions of currently installed packages that cannot be upgraded without changing the install status of another package     will be left at their current version (displayed as “held back”). This can be resolved by either using aptitude to choose these packages for installation or by trying apt-get -f install package . 4.5. 在升級過程中可能會發生的問題     The following sections describe known issues that might appear during an upgrade to squeeze. 4.5.1. cryptoloop support not included in the squeeze Linux kernel Support for cryptoloop has been dropped from the Linux kernel     packages included in Debian 6.0. Existing installations using cryptoloop need to be transitioned to dm-crypt before the upgrade. 4.5.2. Expected removals The upgrade process to squeeze might ask for removal of packages in the system. The precise list of packages will vary depending     on the set of packages that you have installed. These release notes give general advice on these removals, but if in doubt, it is recommended that you examine the package removals proposed by each method before proceeding. Some common packages that are expected to be removed include: autofs (replaced by autofs5), dhcp3 (replaced by isc-dhcp),     madwifi-source, python-setuptools and python2.4 (replaced by python2.6). For more information about packages obsoleted in squeeze, see 節 4.10, “被廢棄的套件”. 4.5.3. Errors running aptitude or apt-get     如果在使用 aptitude、apt-get 或 dpkg 的過程中失敗了並顯示以下錯誤     E: Dynamic MMap ran out of room the default cache space is insufficient. You can solve this by either removing or commenting lines you don't need in /etc/apt/     sources.list or increasing the cache size. The cache size can be increased by setting APT::Cache-Limit in /etc/apt/apt.conf. The following command will set it to a value that should be sufficient for the upgrade:     # echo 'APT::Cache-Limit "12500000";' >> /etc/apt/apt.conf     在此則假設了您尚未在該檔案中設定這個變數。 4.5.4. Conflicts or Pre-Depends loops Sometimes it's necessary to enable the APT::Force-LoopBreak option in APT to be able to temporarily remove an essential     package due to a Conflicts/Pre-Depends loop. apt-get will alert you of this and abort the upgrade. You can work around this by specifying the option -o APT::Force-LoopBreak=1 on the apt-get command line. It is possible that a system's dependency structure can be so     corrupt as to require manual intervention. Usually this means using apt-get or     # dpkg --remove package_name     來清除一些會造成問題的套件，或     # apt-get -f install # dpkg --configure --pending     在極端的情況下，您可能需要利用類似以下的指令來強制進行重新安裝的 動作：     # dpkg --install /path/to/package_name.deb 4.5.5. File conflicts 如果您是由一個“純粹”的 lenny 進行升級的話，應該不會有檔案衝突的情     況發生；但如果您安裝了非官方的 backports 套件時就不一定了。如果發 生檔案衝突時，會產生類似以下的錯誤： 正在解開 （由 ）... dpkg: 在處理時出錯 (--install): 試圖覆寫 `'，     但它同時包含於套件 中 dpkg-deb: 子程序 paste 因錯誤訊息（損毀的 pipe）而被中斷 在處理時發生了錯誤：     您可以強制移除出現在錯誤訊息裡最後一行的那個套件，以解決檔案衝突 的問題：     # dpkg -r --force-depends package_name     After fixing things up, you should be able to resume the upgrade by repeating the previously described apt-get commands. 4.5.6. Configuration changes During the upgrade, you will be asked questions regarding the configuration or re-configuration of several packages. When you are asked if any file in the /etc/init.d directory, or the /etc/     manpath.config file should be replaced by the package maintainer's version, it's usually necessary to answer `yes' to ensure system consistency. You can always revert to the old versions, since they will be saved with a .dpkg-old extension. 如果您不太確定要怎麼做的話，把套件或檔案的名稱寫下來，等稍後再想     辨法理出頭緒來。您可以在記錄檔中搜尋，以便能重新檢視在系統升級時 出現在螢幕上的資訊。 4.5.7. Change of session to console If you are running the upgrade using the system's local console you might find that at some points during the upgrade the console     is shifted over to a different view and you lose visibility of the upgrade process. For example, this will happen in desktop systems when gdm is restarted. To recover the console where the upgrade was running you will have to use Ctrl+Alt+F1 to switch back to the virtual terminal 1 if in the graphical startup screen or use Alt+F1 if in the local     text-mode console. Replace F1 with the function key with the same number of the virtual terminal the upgrade was running in. You can also use Alt+Left Arrow or Alt+Right Arrow to switch between the different text-mode terminals. 4.5.8. Special care for specific packages In most cases, packages should upgrade smoothly between lenny and     squeeze. There are a small number of cases where some intervention may be required, either before or during the upgrade; these are detailed below on a per-package basis. 4.5.8.1. Evolution Evolution (the GNOME Desktop mail client) has been updated from version 2.22 to 2.30. This changes the storage format used by the package for local data and there is a possibility of data loss if     the upgrade is performed whilst evolution is running. Exiting the application itself may not be sufficient, as various related components will continue to run in the background. To avoid any potential issues, it is recommended that you completely exit your desktop environment before beginning the upgrade to squeeze. As part of the upgrade process, evolution will check whether any related processes are running and will recommend that they be     closed. A secondary check for processes will then be performed; if necessary, a choice will be offered between allowing the remaining processes to be killed or aborting the upgrade in order to resolve the situation by hand. 4.6. 替您的 Kernel 及相關套件進行升級 這一節中解釋了如何升級您的 kernel 及和升級有關的潛在問題。您可以     安裝由 Debian 提供的某個 linux-image-* 套件，或是由原始碼自行編譯 一個自訂的 kernel。 請注意到，在這一節中的許多資訊是假設了您使用著某個模組化、和     initramfs-tools 及 udev 搭配使用的 Kernel。如果您是使用不需 initrd 的自訂 kernel 或是您使用的是另一種 initrd 產生程式，這些資 訊中有些是和您無關的。 4.6.1. 安裝 Kernel 的虛擬套件 當您由 lenny 完整升級至 squeeze 後，強烈建議您安裝某個     linux-image-2.6-* 虛擬套件。這個套件可能會在完整升級的過程中被自 動安裝。若想確認，請執行：     # dpkg -l "linux-image*" | grep ^ii 如果您沒有看到任何輸出文字，那麼您將得手動安裝一個新的     linux-image 虛擬套件。若想得到可用的 linux-image-2.6 虛擬套件列表 ，請執行：     # apt-cache search linux-image-2.6- | grep -v transition If you are unsure about which package to select, run uname -r and look for a package with a similar name. For example, if you see     '2.6.26-2-686', it is recommended that you install linux-image-2.6-686. You may also use apt-cache to see a long description of each package in order to help choose the best one available. For example:     # apt-cache show linux-image-2.6-686 You should then use apt-get install to install it. Once this new     kernel is installed you should reboot at the next available opportunity to get the benefits provided by the new kernel version. For the more adventurous there is an easy way to compile your own custom kernel on Debian GNU/Linux. Install the kernel-package tool and read the documentation in /usr/share/doc/kernel-package.     Alternatively, you can also use the kernel sources, provided in the linux-source-2.6 package. You can make use of the deb-pkg target available in the sources' makefile for building a binary package. There are some differences in these two approaches, please consult the respective package's documentation. If possible, it is to your advantage to upgrade the kernel package separately from the main dist-upgrade to reduce the     chances of a temporarily non-bootable system. Note that this should only be done after the minimal upgrade process described in 節 4.4.4, “系統最低限度升級”. 4.6.2. 重新排序裝置列表 In lenny and later, a new kernel mechanism for hardware discovery may change the order in which devices are discovered on your     system on each boot, affecting the device names assigned to them. For example, if you have two network adapters that are associated with two different drivers, the devices eth0 and eth1 refer to may be swapped. For network devices, this reordering is normally avoided by the definitions at /etc/udev/rules.d/70-persistent-net.rules for udev . Since these rules were already in place in lenny, no additional action should be required when upgrading to squeeze to get the benefit of stable network device names. Please note, however,     that this udev mechanism means that a given network device name is tied to a particular piece of hardware; if you, for instance, exchange ethernet adapters in a deployed squeeze system, the new adapter will get a new interface name instead of using the existing one. To reuse an existing device name for new hardware, you will need to delete the associated entry from /etc/udev/ rules.d/70-persistent-net.rules. For storage devices, you may be able to avoid this reordering by using initramfs-tools and configuring it to load storage device driver modules in the same order they are currently loaded. However, in light of other changes to the storage subsystem of     the Linux kernel as described at 節 5.1.1, “Migration of disk drivers from IDE to PATA subsystem”, this is usually not worth the effort and it is recommended instead to use device names that are guaranteed to be stable over time, such as the UUID aliases ^ [9] in the /dev/disk/by-uuid/ directory or LVM device names in / dev/mapper/. 4.6.3. 開機時機問題     如果使用由 initramfs-tools 產生的 initrd 來開機的話，在某些狀況下 udev 建立裝置檔的時機比開機 scripts 的動作還慢。 一般而言，無法正常開機的原因多是因為無法掛載 root 檔案系統，然後     您會進入一個除錯介面。但若您在稍後再進行檢查時，卻發現所有必要的 裝置都已出現於 /dev 內。這種情況會發生在 root 檔案系統是放在 USB 裝置或 RAID 上，尤其又和 LILO 搭配運用時。     要避開這個問題的方法是使用 rootdelay=9 開機參數。其中的秒數可能得 視情況再加以調整。 4.7. 系統開機時當在 Waiting for root file system 回復已變為 /dev/sda 的 /dev/hda 的步驟         Some users have reported that an upgrade could cause the kernel not to find the system root partition after a system reboot. 此時，系統開機會當掉，並顯示如下資訊：     Waiting for root file system ... and after a few seconds a bare busybox prompt will appear. This problem can occur when the upgrade of the kernel introduces     the use of the new generation of IDE drivers. The IDE disk naming convention for the old drivers was hda, hdb, hdc, hdd. The new drivers will name the same disks respectively sda, sdb, sdc, sdd. The problem appears when the upgrade does not generate a new / boot/grub/menu.lst file to take the new naming convention into account. During the boot, Grub will pass a system root partition     to the kernel that the kernel doesn't find. It can also appear when mounting filesystems if the /etc/fstab has not been updated accordingly. Although the upgrade process to squeeze should cover both situations automatically.     如果您在升級後遇到了這個問題，請參閱節 4.7.2, “如何在升級後再修復 這個問題”。而關於如何在升級之前避開這個問題，請繼續閱讀。 4.7.1. 如何在升級之前避開這個問題 One can avoid this problem entirely by using an identifier for the root filesystem that does not change from one boot to the     next. There are two possible methods for doing this - labeling the filesystem, or using the filesystem's universally unique identifier (UUID). These methods are supported in Debian since the etch release. The two approaches have advantages and disadvantages. The labeling approach is more readable, but there may be problems if     another filesystem on your machine has the same label. The UUID approach is uglier, but having two clashing UUIDs is highly unlikely. 在以下的範例中，我們假設 root 檔案系統是位於 /dev/hda6。我們也同     時假設了您的系統安裝並使用了 udev，同時使用的是 ext2 或 ext3 檔案 系統。 To implement the labeling approach: 1. 可以利用以下指令來替檔案系統命名（該名稱必須 < 16 個字元）： e2label /dev/hda6 rootfilesys 2. 然後，編輯 /boot/grub/menu.lst 並將以下這一行： # kopt=root=/dev/hda6 ro 修改為 # kopt=root=LABEL=rootfilesys ro ┌─────────────────────────────────────────────────────┐     │注 │ │ │ │請不要刪掉最開頭的 #。它是必要的。 │ └─────────────────────────────────────────────────────┘ 3. 執行 update-grub 指令，讓它更新 menu.lst 裡的 kernel 設定。 4. 修改 /etc/fstab，修改用來掛載 / 分割區的那一行，例如： /dev/hda6 / ext3 defaults,errors=remount-ro 0 1 修改為 LABEL=rootfilesys / ext3 defaults,errors=remount-ro 0 1 在此主要是修改第一個欄位，您不需要修改該行中的其它欄位。 To implement the UUID approach: 1. Find out the universally unique identifier of your filesystem by issuing: ls -l /dev/disk/by-uuid | grep hda6. You can also use blkid /dev/hda6. If you list the contents in /dev/disk/by-uuid, you should get a line similar to this one: lrwxrwxrwx 1 root root 24 2008-09-25 08:16 d0dfcc8a-417a-41e3-ad2e-9736317f2d8a -> ../../hda6 If you use blkid, you should get an output similar to this one: /dev/hda6: UUID="d0dfcc8a-417a-41e3-ad2e-9736317f2d8a" TYPE="ext3" UUID 就是那個指向 /dev/hda6 的符號連結。亦即： d0dfcc8a-417a-41e3-ad2e-9736317f2d8a。 ┌─────────────────────────────────────────────────────┐ │注 │ │ │ │您的檔案系統的 UUID 應該會是一個完全不同的字串。 │ └─────────────────────────────────────────────────────┘     2. 然後，編輯 /boot/grub/menu.lst 並將以下這一行： # kopt=root=/dev/hda6 ro to use UUID instead: # kopt=root=UUID=d0dfcc8a-417a-41e3-ad2e-9736317f2d8 ro ┌─────────────────────────────────────────────────────┐ │注 │ │ │ │請不要刪掉最開頭的 #。它是必要的。 │ └─────────────────────────────────────────────────────┘ 3. 執行 update-grub 指令，讓它更新 menu.lst 裡的 kernel 設定。 4. 修改 /etc/fstab，修改用來掛載 / 分割區的那一行，例如： /dev/hda6 / ext3 defaults,errors=remount-ro 0 1 修改為 UUID=d0dfcc8a-417a-41e3-ad2e-9736317f2d8 / ext3 defaults,errors=remount-ro 0 1 在此主要是修改第一個欄位，您不需要修改該行中的其它欄位。 4.7.2. 如何在升級後再修復這個問題 4.7.2.1. 方案 1 讓 Grub 顯示開機選單，讓您能夠選擇您要從哪個項目開機是個很合乎情     理的作法。但若這個選單沒有出現，請在 kernel 開機之前按下 Esc 鍵即 可讓這個選單出現。如果還是沒辨法弄出這個選單的話，請試試節  4.7.2.2, “方案 2” 或節 4.7.2.3, “方案 3”。 1. 在 Grub 選單上，選擇您想要開機的項目，然後按下 e 鍵來修改這個 項目的相關選項。您會看到類似的文字如下： root (hd0,0) kernel /vmlinuz-2.6.32-5-686 root=/dev/hda6 ro initrd /initrd.img-2.6.32-5-686 2. 選擇該項目 kernel /vmlinuz-2.6.32-5-686 root=/dev/hda6 ro     按下 e 鍵並將 hdX 取代為 sdX（其中的 X 為字母 a、b、c 或 d， 依您的系統而定）。在這個例子中，這個項目就變成了： kernel /vmlinuz-2.6.32-5-686 root=/dev/sda6 ro 然後按下 Enter 來儲存這些修改。如果有其它的項目中也有 show hd X，請也同時修改。不要將這些項目修改成類似 root (hd0,0)。在全 數修改完成後，按下 b 鍵，然後您的系統應該就能正常開機了。 3. 等到您的系統開完機，您必須手動修復這個問題。請參閱節 4.7.1, “ 如何在升級之前避開這個問題” 並從 2 個解決方案之中選擇其中 1 個進行。 4.7.2.2. 方案 2 Boot from Debian GNU/Linux installation media (CD/DVD) and when prompted, pick rescue to launch rescue mode. Select your language, location, and keyboard mapping; then let it configure the network (no matter whether it succeeds or not). After a while, you should be asked to select the partition you want to     use as root file system. The proposed choices will look something like: /dev/sda1 /dev/sda2 /dev/sda5 /dev/sda6 如果您知道哪個分割區是您的 root 檔案系統，請逕行選擇。否則，請直 接嘗試第一個。如果程式回覆說這並不是一個 root 檔案系統，再試下一     個，依此類推。這樣依次嘗試並不會對您的分割區造成什麼影響，但如果 您的磁碟上只安裝了一個作業系統的話，您可以輕易得找到正確的 root 檔案系統分割區。但如果您在您的磁碟上安裝了好幾個作業系統，那麼您 最好能清楚得知道哪個才是正確的分割區。 一旦您選擇了某個分割區，會出現一系列的選項供您使用。請選擇在選定     的分割區上執行一個 Shell 的那個選項。如果程式回應說無法進行，請再 試另一個分割區。 Now you should have shell access as user root on your root file system mounted on /target. You need access to the contents of the /boot, /sbin and /usr directories on your hard disk, which should     now be available under /target/boot, /target/sbin and /target/ usr. If these directories need to be mounted from other partitions, do so (see /etc/fstab if you have no idea of which partition to mount). 請參閱節 4.7.1, “如何在升級之前避開這個問題” 並採取 2 種解決方案     之一來手動修正這些問題。然後按下 exit 來離開這個救援 shell，然後 選擇 reboot 來將系統重新開機（別忘了要取出開機媒體）。 4.7.2.3. 方案 3 1. 從您想用的 LiveCD 發行版，像是 Debian Live、Knoppix、Ubuntu Live 來進行開機。 2. 將您的 /boot 分割區給掛載起來。如果您不清楚是哪一個，請利用 dmesg 命令的輸出文字來找出您的磁碟是 hda、hdb、hdc、hdd 或是 sda、sdb、 sdc、sdd。等到您知道是哪個磁碟後，比如說是 sdb，執行以下命令來檢 視該碟碟的磁碟分割表，並找到正確的分割區：fdisk -l /dev/sdb 3. 在此假設您已將正確的分割區掛載在 /mnt 下，且這個分割區也包含了 / boot 目錄及裡面的所有東西，然後修改 /mnt/boot/grub/menu.lst 檔案 ， 找到類似的段落如下： ## ## End Default Options ## title Debian GNU/Linux, kernel 2.6.32-5-686 root (hd0,0)     kernel /vmlinuz-2.6.32-5-686 root=/dev/hda6 ro initrd /initrd.img-2.6.32-5-686 title Debian GNU/Linux, kernel 2.6.32-5-686 (single-user mode) root (hd0,0) kernel /vmlinuz-2.6.32-5-686 root=/dev/hda6 ro single initrd /initrd.img-2.6.32-5-686 ### END DEBIAN AUTOMAGIC KERNELS LIST and replace every hda, hdb, hdc, hdd with sda, sdb, sdc, sdd, as appropriate. Don't modify the line similar to: root (hd0,0) 4. 將系統重新開機，移除 LiveCD 然後您的系統應該能正常開機了。 5. 在關機後，請採取在節 4.7.1, “如何在升級之前避開這個問題” 中那 2 種解決方案之一來手動修正這些問題。 4.8. 替下一個釋出版本進行準備     在更新完畢之後，您可以進行某些工作來替下一個釋出版本進行準備： ● 將在節 4.10, “被廢棄的套件” 裡所說明的已廢棄及已不再使用的套     件移除掉。您應該重新檢視它們使用了哪些設定檔並考慮完全將套件 清除 (purge) 掉以移去它們的設定檔。 4.8.1. Upgrade to GRUB 2 During the upgrade, you will normally have been offered the option to "chainload" GRUB 2: that is, to keep GRUB Legacy as the     primary boot loader but to add an option to it to load GRUB 2 and then start your Debian GNU/Linux system from that. This allows you to verify that GRUB 2 works on your system before committing to use it permanently. Once you have confirmed that GRUB 2 works, you should switch to     using it properly: the chainloading setup is only intended to be used temporarily. You can do this by running upgrade-from-grub-legacy. The GRUB Manual has more information (http://www.gnu.org/software /grub/manual/grub.html#Changes-from-GRUB-Legacy) on the changes     between GRUB Legacy and GRUB 2, some of which may require changes to complex configurations. If you have not modified your boot loader configuration, you should not need to do anything further. 4.9. Deprecated components With the next release of Debian GNU/Linux 7.0 (codenamed wheezy)     some features will be deprecated. Users will need to migrate to other alternatives to prevent trouble when updating to 7.0.     This includes the following features: ● OpenVZ and Linux-Vserver: Debian GNU/Linux 6.0 will be the last release to include Linux kernel virtualization featuresets outside of mainline. This means that the OpenVZ and Linux-Vserver featuresets should be considered deprecated, and users should migrate to linux-2.6 upstream     merged virtualization solutions like KVM, Linux Containers or Xen. ● The gdm package (GNOME Display Manager version 2.20) will be obsoleted by gdm3, a rewritten version. See 節 5.5, “GNOME 桌 面的變更和支援” for more information. 4.10. 被廢棄的套件 Introducing several thousand new packages, squeeze also retires and omits more than four thousand old packages that were in lenny. It provides no upgrade path for these obsolete packages. While nothing prevents you from continuing to use an obsolete     package where desired, the Debian project will usually discontinue security support for it a year after squeeze's release^[10]，而除此之外，我們在這段期間內一般並不會再提供其它方 面的支援。如果可以的話，我們建議您能採用其它的替代方案來取代這些 套件。 而這些套件為什麼會從發行版中移去的原因不一而足：有的是因為它的原 始程式已經沒有人在繼續維護了；有的是因為已經沒有 Debian 的開發者     有意願想要繼續維護這些套件了；有的是因為它們所提供的功能已經被其 它的軟體（或是新的版本）所取代了；有的是因為它們本身所包含的一些 Bug 使得我們認為它們已無法和 squeeze 相容。如果是最後一個情況，這 些套件很可能是被放在 “unstable” 這個分類裡。 Detecting which packages in an updated system are “obsolete” is easy since the package management front-ends will mark them as     such. If you are using aptitude, you will see a listing of these packages in the “Obsolete and Locally Created Packages” entry. dselect provides a similar section but the listing it presents might differ. Also, if you have used aptitude or apt-get to manually install packages in lenny it will have kept track of those packages you manually installed and will be able to mark as obsolete those packages pulled in by dependencies alone which are no longer     needed if a package has been removed. aptitude and apt, unlike deborphan, will not mark for removal packages that you manually installed, as opposed to those that were automatically installed through dependencies. To remove automatically installed packages that are no longer used, run:     # apt-get autoremove 還有一些其它的套件可以讓您用來尋找這些廢棄了的套件，像是 deborphan、debfoster 或 cruft。其中推薦使用 deborphan，因為它在預 設的模式下只會報告已遭廢棄了的函式庫：位於 “libs” 或 “oldlibs” 區 的套件就表示它們已不再被其它的套件所使用了。但請不要輕率得依據這     些工具所回報的列表就把這些套件給移掉了，尤其是您在執行時使用的不 是預設的，而是較為寬鬆的選項時，它們很可能會因而做出不正確的判定 。因此在此強烈建議您，在進行移除的動作之前，您必須親自再重新檢視 一次這些將要被移除的套件，包括它們的內容、大小，及它們的詳細說明 。 在 Debian 錯誤追蹤系統 (http://bugs.debian.org/) 裡常常會提供了為 什麼某個套件會被移掉的相關資訊。您可以使用該套件本身的錯誤回報資     料庫，或是在 ftp.debian.org pseudo-package (http:// bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=ftp.debian.org&archive= yes) 裡的錯誤回報資料庫來重新檢視這些資訊。 The list of obsolete packages includes: ● The plone content management suite. This has been done on request by the developers to use the Unified Installer for Linux, which they consider their only supported deployment platform. The recommended tool for installing Plone on a Debian GNU/Linux system is the Unified Installer, available for download from http://plone.org/ (http://plone.org/) ● nessus, the vulnerability scanning server and its associated libraries and other software. It has been deprecated in favor of the software provided by OpenVAS which includes openvas-server and openvas-client. As there is no automatic upgrade path you will have to install OpenVAS and manually move over your Nessus service configuration (users, certificates, etc.) to OpenVAS. ● postgresql-8.3, successor is postgresql-8.4. ● mysql-server-5.0, successor is mysql-server-5.1.     ● python2.4, successor is python2.6. ● Java 5 software including the packages sun-java5-jre and sun-java5-bin, successor is Java 6: sun-java6-jre and associated packages. ● apt-proxy is no longer provided, alternatives to this tool include apt-cacher-ng, apt-cacher and approx. Although no automatic upgrade path exists, user of apt-proxy can switch to these alternatives by manually installing any of these packages. ● Some of Xorg's video drivers are no longer available in squeeze and are obsolete. This includes xserver-xorg-video-cyrix, xserver-xorg-video-i810, xserver-xorg-video-imstt, xserver-xorg-video-nsc, xserver-xorg-video-sunbw2, and xserver-xorg-video-vga. They might be removed through the upgrade. Users should install xserver-xorg-video-all instead. ● The utility used in lenny to display a splash image at boot time, usplash, is no longer available. It has been replaced by plymouth. 4.10.1. 替代 (Dummy) 套件 有時為了讓系統能更易於管理，有些原來是包含於 lenny 的套件在 squeeze 裡已被分開成數個套件。在此況狀下，為了能讓升級的過程更加     順遂，squeeze 通常會採取提供“替代 (Dummy)”套件的方式：使用一個和 原本是包含於 lenny 的套件相同名稱的套件，但它的內容卻是空的，但利 用相依上的關聯性來使得新的套件能被安裝。這些“替代”套件在升級之後 就會被視同廢棄套件了，您可以放心得移除它們。 Most (but not all) dummy packages' descriptions indicate their purpose. Package descriptions for dummy packages are not uniform, however, so you might also find deborphan with the --guess-*     options (e.g. --guess-dummy) useful to detect them in your system. Note that some dummy packages are not intended to be removed after an upgrade but are, instead, used to keep track of the current available version of a program over time. ━━━━━━━━━━━━━━ ^[4] If the debconf priority is set to a very high level you     might prevent configuration prompts, but services that rely on default answers that are not applicable to your system will fail to start. ^[5] For example: DNS or DHCP services, specially when there is     no redundancy or failover. In the DHCP case end-users might be disconnected from the network if the lease time is lower than the time it takes for the upgrade process to complete.     ^[6] 可以在開機參數上加上 panic=0 參數來關閉這個功能。     ^[7] 因為 Debian 的套件管理程式不允許某一個套件移除或取代了屬於另 一個套件的檔案，除非那一個套件本來就是用來取代這個套件的。 ^[8] There are also known incompatibilities between the old     kernel and the new udev. If you find issues after the reboot with the new kernel you will have to downgrade the udev in order to use the old one. ^[9] Some devices, such as those used by crypt, RAID or LVM have     stable non-UUID identifiers. In these cases you should use the name of the devices, which are already unambiguous and stable.     ^[10] 或是直到在這段期間內有新的發行版推出為止。基本上，我們只會 同時維護兩個 stable 的發行版。 章 5. 在 squeeze 裡您必須知道的一些問題 5.1. 潛在的問題 Sometimes, changes introduced in a new release have side-effects we cannot reasonably avoid, or they expose bugs somewhere else.     This section documents issues we are aware of. Please also read the errata, the relevant packages' documentation, bug reports and other information mentioned in 節 6.1, “閱讀更多資訊”. 5.1.1. Migration of disk drivers from IDE to PATA subsystem The new Linux kernel version provides different drivers for some     PATA (IDE) controllers. The names of some hard disk, CD-ROM, and tape devices may change. It is now recommended to identify disk devices in configuration files by label or UUID (unique identifier) rather than by device name, which will work with both old and new kernel versions. Upon upgrading to the squeeze version of the Debian kernel packages, the linux-base package will offer to do this conversion for you     in the config files for most of the filesystem-related packages on the system, including the various bootloaders included in Debian. If you choose not to update the system configuration automatically, or if you are not using the Debian kernel packages, you must update device IDs yourself before the next system reboot to ensure the system remains bootable. 5.1.2. mdadm metadata format change requires recent Grub The following only applies to users who want to let the grub-pc bootloader load the kernel directly off a RAID device created with mdadm 3.x and default values, or when the metadata version     is explicitly set using -e. Specifically, this includes all arrays created during or after the installation of Debian squeeze. Arrays created with older mdadm versions, and RAIDs created with the command-line option -e 0.9 are not affected. Versions of grub-pc older than 1.98+20100720-1 will not be able to boot directly off a RAID with the 1.x metadata formats (the new default is 1.2). To ensure a bootable system, please make     sure to use grub-pc 1.98+20100720-1 or later, which is provided by Debian squeeze. An unbootable system may be rescued with Super Grub2 Disk (http://www.supergrubdisk.org/super-grub2-disk/) or grml (http://grml.org) . 5.1.3. pam_userdb.so breakage with newer libdb Some Berkeley Database version 7 files created with libdb3 cannot     be read by newer libdb versions (see bug #521860 (http:// bugs.debian.org/521860) ). As a workaround, the files can be recreated with db4.8_load, from the db4.8-util package. 5.1.4. Potential issues with diversions of /bin/sh If you have previously added a local diversion for /bin/sh, or modified the /bin/sh symlink to point to somewhere other than /     bin/bash, then you may encounter problems when upgrading the dash or bash packages. Note that this includes changes made by allowing other packages (for example mksh) to become the default system shell by taking over /bin/sh. If you encounter any such issues, please remove the local     diversion and ensure that the symlinks for both /bin/sh and its manual page point to the files provided by the bash package and then dpkg-reconfigure --force dash. dpkg-divert --remove /bin/sh dpkg-divert --remove /usr/share/man/man1/sh.1.gz     ln -sf bash /bin/sh ln -sf bash.1.gz /usr/share/man/man1/sh.1.gz 5.1.5. Change in kernel policy regarding resource conflicts The default setting for the acpi_enforce_resources parameter in the Linux kernel has changed to be “strict” by default. This can     lead some legacy sensor drivers to be denied access to the sensors' hardware. One workaround is to append “acpi_enforce_resources=lax” to the kernel command line. 5.2. LDAP support     A feature in the cryptography libraries used in the LDAP libraries causes programs that use LDAP and attempt to change     their effective privileges to fail when connecting to an LDAP server using TLS or SSL. This can cause problems for suid programs on systems using libnss-ldap like sudo, su or schroot and for suid programs that perform LDAP searches like sudo-ldap. It is recommended to replace the libnss-ldap package with     libnss-ldapd, a newer library which uses separate daemon (nslcd) for all LDAP lookups. The replacement for libpam-ldap is libpam-ldapd. Note that libnss-ldapd recommends the NSS caching daemon (nscd)     which you should evaluate for suitability in your environment before installing. As an alternative to nscd you can consider unscd. Further information is available in bugs #566351 (http://     bugs.debian.org/566351) and #545414 (http://bugs.debian.org/ 545414) . 5.3. sieve service moving to its IANA-allocated port The IANA port allocated for ManageSieve is 4190/tcp, and the old port used by timsieved and other managesieve software in many     distributions (2000/tcp) is allocated for Cisco SCCP usage, according to the IANA registry (http://www.iana.org/assignments/ port-numbers) . Starting with the version 4.38 of the Debian netbase package, the     sieve service will be moved from port 2000 to port 4190 in the / etc/services file. Any installs which used the sieve service name instead of a     numeric port number will switch to the new port number as soon as the services are restarted or reloaded, and in some cases, immediately after /etc/services is updated.     This will affect Cyrus IMAP. This may also affect other sieve-enabled software such as DoveCot. In order to avoid downtime problems, mail cluster administrators using Debian are urged to verify their Cyrus (and probably also     DoveCot) installs, and take measures to avoid services moving from port 2000/tcp to port 4190/tcp by surprise in either servers or clients. It is worth noting that: ● /etc/services will only be automatically updated if you never made any modifications to it. Otherwise, you will be presented with a prompt by dpkg asking you about the changes. ● You can edit /etc/services and change the sieve port back to 2000 if you want (this is not recommended, though).     ● You can edit /etc/cyrus.conf and any other relevant configuration files for your mail/webmail cluster (e.g. on the sieve web frontends) ahead of time to force them all to a static port number. ● You can configure cyrus master to listen on both ports (2000 and 4190) at the same time, and thus avoid the problem entirely. This also allows for a much more smooth migration from port 2000 to port 4190. 5.4. KDE 桌面 Squeeze is the first Debian release to ship with the full support for the next generation KDE that is based on Qt 4. Most official     KDE applications are at version 4.4.5 with the exception of kdepim that is at version 4.4.7. You can read the announcements from the KDE Project (http://www.kde.org/announcements/) to learn more about the changes. 5.4.1. Upgrading from KDE 3 KDE 3 Desktop Environment is no longer supported in Debian 6.0. It will be automatically replaced by the new 4.4 series on     upgrade. As this is a major change, users should take some precautions in order to ensure as smooth of an upgrade process as possible. 重要     It is discouraged to upgrade while there is an active KDE 3 session on the system. Otherwise, the process might render the running session dysfunctional with the possibility of data loss. Upon the first login on the upgraded system, existing users will be prompted with the Debian-KDE guided migration procedure called     kaboom which will assist in the process of migrating the user's personal data and optionally backing up old KDE configuration. For more information, visit the Kaboom homepage (http:// pkg-kde.alioth.debian.org/kaboom.html) . While KDE 3 based desktop environment is no longer supported, users can still install and use some individual KDE 3 applications since the core libraries and binaries of KDE 3 (kdelibs) and Qt 3 are still available in Debian 6.0. However,     please note that these applications might not be well integrated with the new environment. What's more, neither KDE 3 nor Qt 3 will be supported in any form in the next Debian release so if you are using them, you are strongly advised to port your software to the new platform. 5.4.2. New KDE metapackages As noted earlier, Debian 6.0 introduces a new set of KDE related metapackages: ● You are strongly advised to install the kde-standard package for normal desktop usage. kde-standard will pull in the KDE Plasma Desktop (http://www.kde.org/workspaces/plasmadesktop/) by default, and a selected set of commonly used applications. ● If you want a minimal desktop you can install the kde-plasma-desktop package and manually pick the applications you need. This is a rough equivalent of the kde-minimal     package as shipped in Debian 5.0. ● For small form factor devices, there is an alternative environment called KDE Plasma Netbook (http://www.kde.org/ workspaces/plasmanetbook/) that can be installed with the kde-plasma-netbook package. Plasma Netbook and Plasma Desktop can live in the same system and the default can be configured in System Settings (replacement of the former KControl). ● If you want a full set of official KDE applications, you have the possibility to install the kde-full package. It will install KDE Plasma Desktop by default. 5.5. GNOME 桌面的變更和支援 There have been many changes in the GNOME desktop environment from the version shipped in lenny to the version in squeeze, you     can find more information in the GNOME 2.30 Release Notes (http:/ /library.gnome.org/misc/release-notes/2.30/) . Specific issues are listed below. 5.5.1. GDM 2.20 and 2.30 The GNOME Display Manager (GDM), is kept at version 2.20 for systems upgraded from lenny. This version will still be maintained for the squeeze cycle but it is the last release to do so. Newly installed systems will get GDM 2.30 instead, provided     by the gdm3 package. Because of incompatibilities between both versions, this upgrade is not automatic, but it is recommended to install gdm3 after the upgrade to squeeze. This should be done from the console, or with only one open GNOME session. Note that settings from GDM 2.20 will not be migrated. For a standard desktop system, however, simply installing gdm3 should be enough. 5.5.2. Device and other administrative permissions Specific permissions on devices are granted automatically to the user currently logged on physically to the system: video and     audio devices, network roaming, power management, device mounting. The cdrom, floppy, audio, video, plugdev and powerdev groups are no longer useful. See the consolekit documentation for more information. Most graphical programs requiring root permissions now rely on     PolicyKit (http://www.freedesktop.org/wiki/Software/PolicyKit) to do so, instead of gksu. The recommended way to give a user administrative rights is to add it to the sudo group. 5.5.3. network-manager and ifupdown interaction Upon upgrading the network-manager package, interfaces configured in /etc/network/interfaces to use DHCP with no other options will be disabled in that file, and handled by NetworkManager instead.     Therefore the ifup and ifdown commands will not work. These interfaces can be managed using the NetworkManager frontends instead, see the NetworkManager documentation (http:// live.gnome.org/NetworkManager/SystemSettings) . Conversely, any interfaces configured in /etc/network/interfaces     with more options will be ignored by NetworkManager. This applies in particular to wireless interfaces used during the installation of Debian (see bug #606268 (http://bugs.debian.org/606268) ). 5.6. Graphics stack changes     There have been a number of changes to the X stack in Debian 6.0. This section lists the most important and user-visible. 5.6.1. Obsolete Xorg drivers The cyrix, imstt, sunbw2 and vga Xorg video drivers are no longer     provided. Users should switch to a generic such as vesa or fbdev instead. The old via driver was no longer maintained, and has been     replaced by the openchrome driver, which will be used automatically after the upgrade. The nv and radeonhd drivers are still present in this release,     but are deprecated. Users should consider the nouveau and radeon drivers instead, respectively. The calcomp, citron, digitaledge, dmc, dynapro, elo2300, fpit, hyperpen, jamstudio, magellan, microtouch, mutouch, palmax, spaceorb, summa, tek4957 and ur98 X input drivers have been     discontinued and are not included in this release. Users of these devices might want to switch to a suitable kernel driver and the evdev X driver. For many serial devices, the inputattach utility allows attaching them to a Linux input device which can be recognized by the evdev X driver. 5.6.2. Kernel mode setting Kernel drivers for Intel (starting from i830), ATI/AMD (from the     original Radeon to the Radeon HD 5xxx “Evergreen” series) and for NVIDIA graphics chipsets now support native mode setting. Support for old-style userspace mode setting is discontinued in     the intel X driver, which requires a recent kernel. Users of custom kernels should make sure that their configuration includes CONFIG_DRM_I915_KMS=y. 5.6.3. Input device hotplug The Xorg X server included in Debian 6.0 provides improved support for hotplugging of input devices (mice, keyboards, tablets, …). The old xserver-xorg-input-kbd and xserver-xorg-input-mouse packages are replaced by     xserver-xorg-input-evdev, which requires a kernel with the CONFIG_INPUT_EVDEV option enabled. Additionally, some of the keycodes produced by this driver differ from those traditionally associated with the same keys. Users of programs like xmodmap and xbindkeys will need to adjust their configurations for the new keycodes. 5.6.4. X server “zapping” Traditionally, the Ctrl+Alt+Backspace combination would kill the X server. This combination is no longer active by default, but     can be re-enabled by reconfiguring the keyboard-configuration package (system-wide), or using your desktop environment's keyboard preferences application. 章 6. 更多關於 Debian GNU/Linux 的資訊 6.1. 閱讀更多資訊 Beyond these release notes and the installation guide, further documentation on Debian GNU/Linux is available from the Debian Documentation Project (DDP), whose goal is to create high-quality documentation for Debian users and developers. Documentation,     including the Debian Reference, Debian New Maintainers Guide, and Debian FAQ are available, and many more. For full details of the existing resources see the Debian Documentation website (http:// www.debian.org/doc/) and the Debian Wiki website (http:// wiki.debian.org/) 個別套件的說明文件則會被安裝到 /usr/share/doc/package 目錄之中，     其中可能會包含了版權資訊，專屬於 Debian 的一些訊息，以及任何原作 者所提供的說明文件。 6.2. 取得協助 Debian 的使用者可以從許多的管道取得協助、建議、和支援，但您應該只     有在用盡了各種手段卻依然找不到問題的解答時才考慮尋求協助。這一節 簡單的介紹了對 Debian 的新使用者可能會很有幫助的求助管道。 6.2.1. 郵件論壇 Debian 的使用者最感興趣的郵件論壇應該是 debian-user 論壇（英文） 以及其他的 debian-user-language 論壇（其他語言）了。您可以在http:     //lists.debian.org/ (http://lists.debian.org/) 取得這些論壇的相關 細節，以及訂閱的方法。請您在論壇中發言前先檢查過去的論壇存檔中是 否已經提供了問題的解答，並請遵守郵件論壇上的基本禮節。 6.2.2. IRC(Internet Relay Chat) 網路聊天室 Debian 在 OFTC IRC 上開設了一個 IRC 頻道，專門用來支援並幫助     Debian 的使用者。您只要把您慣用的 IRC 客戶端程式指向 irc.debian.org 並加入 #debian 就可以連上這個頻道了。 Please follow the channel guidelines, respecting other users     fully. The guidelines are available at the Debian Wiki (http:// wiki.debian.org/DebianIRC) .     可以在 website (http://www.oftc.net/) 上取得更多 OFTC 的相關資訊 。 6.3. 回報錯誤 我們盡心盡力地讓 Debian GNU/Linux 成為一個高品質的作業系統，但這 並不表示我們所提供的套件都是完全沒有任何問題的。為了和 Debian 一     貫的“開放發展”原則相互呼應，也為了能對我們的使用者提供更好的服務 ，我們在我們自己的錯誤追蹤系統 (BTS) 中提供了對所有報告過的錯誤的 所有資訊。您可以在 http://bugs.debian.org/ (http:// bugs.debian.org/) 瀏覽錯誤追蹤系統的網站。 如果您在我們的系統發行或其中的套件中發現了任何問題，請向我們回報 ，這樣我們才能在日後的發行版中將它修復。您需要擁有一個正確的電子     郵件信箱才能夠回報問題，會有這個限制是因為這樣我們才能藉此追蹤錯 誤報告的進展，而當開發人員需要更多資訊的時候也才能和原問題報告者 取得連繫。 您可以藉由 reportbug 程式或是自行使用電子郵件來進行回報錯誤，您可     以閱讀相關的參考文件（如果您有安裝 doc-debian 的話，可以在 /usr/ share/doc/debian 裡找到）或到問題追蹤系統 (http://bugs.debian.org /) 的線上網頁取得更多如何使用錯誤追蹤系統及其它的相關資訊。 6.4. 如何對 Debian 做出貢獻 You do not need to be an expert to contribute to Debian. By assisting users with problems on the various user support lists (http://lists.debian.org/) you are contributing to the community. Identifying (and also solving) problems related to the development of the distribution by participating on the development lists (http://lists.debian.org/) is also extremely     helpful. To maintain Debian's high quality distribution, submit bugs (http://bugs.debian.org/) and help developers track them down and fix them. If you have a way with words then you may want to contribute more actively by helping to write documentation (http://www.debian.org/doc/cvs) or translate (http:// www.debian.org/international/) existing documentation into your own language. 如果您能投注更多的時間的話，您可以負責維護 Debian 中一部分的自由 軟體。如果您能夠接續或維護其他使用者希望 Debian 所能提供的軟體的 話就更好了，您可以在亟需人手以及受到期待的套件資料庫 (WNPP)     (http://www.debian.org/devel/wnpp/) 中取得相關的資訊。如果您的興 趣是集中在特別的領域之中，那您可能會想要參加像是某個特定硬體平台 的系統移植、Debian Jr. (http://www.debian.org/devel/debian-jr/) 以及 Debian Med (http://www.debian.org/devel/debian-med/) 之類在 Debian 中的子計畫。 不論如何，只要您以任何的方式參加了自由軟體社群的活動，不管是身為     使用者、程式員、作者、還是譯者，您就已經對自由軟體的群體努力做出 貢獻了。貢獻本身就是一件非常有益而有趣的事情，除了能讓您不斷地遇 見新的伙伴之外，也能讓您的心中充滿了溫暖的感覺。 附錄 A. Managing your lenny system before the upgrade     這個附錄包含了在您升級至 squeeze 之前，如何讓您能夠順利地安裝或更 新 lenny 套件的相關說明。這只有在某些特殊狀況之下才會有這個需求。 A.1. 更新您的 lenny 系統 基本上，這和您所進行過的 lenny 的升級並沒有什麼不同。唯一的不同是     您必須先確認您的套件列表是否還是指向 lenny，請參考在節 A.2, “檢查 您的來源列表” 裡的說明。     如果您是使用 Debian 鏡像站來更新您的系統的話，它會自動得被更新至 lenny 的最新釋出版。 A.2. 檢查您的來源列表 If any of the lines in your /etc/apt/sources.list refer to 'stable', you are effectively already “using” squeeze. This might     not be what you want if you are not ready yet for the upgrade. If you have already run apt-get update, you can still get back without problems following the procedure below. 如果您已經安裝了來自 squeeze 的套件，那麼再安裝來自 lenny 的套件     就已經沒有太多意義了。在此狀況之下，您應該要自行決定是否要繼續進 行。進行套件的降級並不是不可能的事，但是在此並沒有針對這個加以說 明。 使用您慣用的編輯器，以 root 的身份開啟 /etc/apt/sources.list 這個     檔案，然後檢查所有以 deb http: 或 deb ftp: 開頭的項目，看看是否有 參照至 “stable”。如果有的話，將其中的 stable 改為 lenny。     如果您有任何項目是以 deb file: 開頭的，您必須自行檢查這些項目所提 供的是 lenny 還是 squeeze 的檔案庫。 重要     不要修改任何以 deb cdrom: 開頭的項目。否則，這些項目將會因而無法 使用，使得您只能再執行一次 apt-cdrom。如果您發現某個 'cdrom' 的來 源項目是指向 “unstable” 時請不要覺得太訝異。雖然有點奇怪，但這卻 是很正常的。     如果您進行了任何改變，將檔案儲存並執行     # apt-get update     來更新套件的列表。 A.3. Upgrade legacy locales to UTF-8 If your system is localised and is using a locale that is not based on UTF-8 you should strongly consider switching your system over to using UTF-8 locales. In the past, there have been bugs     identified that manifest itself only when using a non-UTF-8 locale. On the desktop, such legacy locales are supported through ugly hacks in the libraries internals, and we cannot decently provide support for users who still use them. To configure your system's locale you can run dpkg-reconfigure locales. Ensure you select an UTF-8 locale when you are presented     with the question asking which locale to use as a default in the system. In addition, you should review the locale settings of your users and ensure that they do not have legacy locales definitions in their configuration environment. 附錄 B. Contributors to the Release Notes     Many people helped with the release notes, including, but not limited to Adam Di Carlo, Andreas Barth, Andrei Popescu, Anne Bezemer, Bob Hilliard, Charles Plessy, Christian Perrier, Daniel Baumann, Eddy Petrișor, Emmanuel Kasper, Esko Arajärvi, Frans Pop, Giovanni Rapagnani, Gordon Farquharson, Javier Fernández-Sanguino Peña,     Jens Seidel, Jonas Meurer, Josip Rodin, Justin B Rye, LaMont Jones, Luk Claes, Martin Michlmayr, Michael Biebl, Moritz Mühlenhoff, Noah Meyerhans, Noritada Kobayashi, Osamu Aoki, Peter Green, Rob Bradford, Samuel Thibault, Simon Bienlein, Simon Paillard, Stefan Fritsch, Steve Langasek, Tobias Scherer, Vincent McIntyre, and W. Martin Borgert.     This document has been translated into many languages. Many thanks to the translators! 索引 A Abiword, 在這次的發行版本中有什麼新變化？ Apache, 在這次的發行版本中有什麼新變化？ B BIND, 在這次的發行版本中有什麼新變化？ Blu-ray, 在這次的發行版本中有什麼新變化？ C CD, 在這次的發行版本中有什麼新變化？ Cherokee, 在這次的發行版本中有什麼新變化？ Courier, 在這次的發行版本中有什麼新變化？ D Debian Live, Debian Live Debian Med, Comprehensive support for neuroimaging research Debian Science, Comprehensive support for neuroimaging research Dia, 在這次的發行版本中有什麼新變化？ DocBook XML, 這份文件的來源資訊 DVD, 在這次的發行版本中有什麼新變化？ E Ekiga, 在這次的發行版本中有什麼新變化？ Evolution, 在這次的發行版本中有什麼新變化？ Exim, 在這次的發行版本中有什麼新變化？ F Firefox, 在這次的發行版本中有什麼新變化？ G GCC, 在這次的發行版本中有什麼新變化？ GIMP, 在這次的發行版本中有什麼新變化？ GNOME, 在這次的發行版本中有什麼新變化？ GNUcash, 在這次的發行版本中有什麼新變化？ GNUmeric, 在這次的發行版本中有什麼新變化？ K KDE, 在這次的發行版本中有什麼新變化？ KOffice, 在這次的發行版本中有什麼新變化？ L LDAP, LDAP support, LDAP support LILO, 開機時機問題 Linux Standard Base, 在這次的發行版本中有什麼新變化？ Live system, Debian Live LXDE, 在這次的發行版本中有什麼新變化？ M Mozilla, 在這次的發行版本中有什麼新變化？ MySQL, 在這次的發行版本中有什麼新變化？ N NeuroDebian, Comprehensive support for neuroimaging research neuroimaging research, Comprehensive support for neuroimaging research O OpenOffice.org, 在這次的發行版本中有什麼新變化？ OpenSSH, 在這次的發行版本中有什麼新變化？ P packages ants, Comprehensive support for neuroimaging research approx, 被廢棄的套件 apt, 提交升級報告, APT 來源之準備工作, 加入網際網路上的 APT 套件 來源, 增加 APT 的本機鏡像套件來源, 被廢棄的套件 apt-cacher, 被廢棄的套件 apt-cacher-ng, 被廢棄的套件 apt-proxy, 被廢棄的套件 aptitude, 套件管理, 確認您有足夠的空間可以用來進行升級 autofs, Expected removals autofs5, Expected removals bash, Potential issues with diversions of /bin/sh console-setup, Unified keyboard settings consolekit, Device and other administrative permissions dash, Potential issues with diversions of /bin/sh db4.8-util, pam_userdb.so breakage with newer libdb dblatex, 這份文件的來源資訊 debian-goodies, 確認您有足夠的空間可以用來進行升級 dhcp3, Expected removals discover, 主要改變 doc-debian, 回報錯誤 docbook-xsl, 這份文件的來源資訊 evolution, Evolution firmware-linux, Firmware moved to the non-free section gdm, Deprecated components gdm3, Deprecated components, GDM 2.20 and 2.30 gksu, Device and other administrative permissions grub, Upgrading the kernel and udev grub-pc, 主要改變, mdadm metadata format change requires recent Grub icedove, 在這次的發行版本中有什麼新變化？ iceweasel, 在這次的發行版本中有什麼新變化？ initramfs-tools, 在開機過程中使用 initrd 的除錯介面 (debug shell) , 替您的 Kernel 及相關套件進行升級, 重新排序裝置列表, 開機時 機問題 insserv, Dependency booting isc-dhcp, Expected removals kaboom, Upgrading from KDE 3 kde-full, New KDE metapackages kde-minimal, New KDE metapackages kde-plasma-desktop, New KDE metapackages kde-plasma-netbook, New KDE metapackages kde-standard, New KDE metapackages kdelibs, Upgrading from KDE 3 kdepim, KDE 桌面 kernel-package, 安裝 Kernel 的虛擬套件 keyboard-configuration, X server “zapping” libnss-ldap, LDAP support, LDAP support libnss-ldapd, LDAP support, LDAP support libpam-ldap, LDAP support, LDAP support libpam-ldapd, LDAP support, LDAP support linux-base, Migration of disk drivers from IDE to PATA subsystem linux-image-*, 替您的 Kernel 及相關套件進行升級 linux-image-2.6-686, 安裝 Kernel 的虛擬套件 linux-source-2.6, 安裝 Kernel 的虛擬套件 live-build, Debian Live localepurge, 確認您有足夠的空間可以用來進行升級 madwifi-source, Expected removals mdadm, mdadm metadata format change requires recent Grub mksh, Potential issues with diversions of /bin/sh mrtrix, Comprehensive support for neuroimaging research mysql-server-5.0, 被廢棄的套件 mysql-server-5.1, 被廢棄的套件 nessus, 被廢棄的套件 netbase, sieve service moving to its IANA-allocated port network-manager, network-manager and ifupdown interaction nipype, Comprehensive support for neuroimaging research nscd, LDAP support odin, Comprehensive support for neuroimaging research openvas-client, 被廢棄的套件 openvas-server, 被廢棄的套件 plone, 被廢棄的套件 plymouth, 被廢棄的套件 popularity-contest, 確認您有足夠的空間可以用來進行升級 postgresql-8.3, 被廢棄的套件 postgresql-8.4, 被廢棄的套件 psychopy, Comprehensive support for neuroimaging research python-setuptools, Expected removals python2.4, Expected removals, 被廢棄的套件 python2.6, Expected removals, 被廢棄的套件 release-notes, 回報這份文件的錯誤 splashy, Remove conflicting packages sudo-ldap, LDAP support sun-java5-bin, 被廢棄的套件 sun-java5-jre, 被廢棄的套件 sun-java6-jre, 被廢棄的套件 tinc, 準備一個安全無虞的環境以進行升級 udev, Upgrading the kernel and udev, 替您的 Kernel 及相關套件進行 升級, 重新排序裝置列表, 開機時機問題 unscd, LDAP support upgrade-reports, 提交升級報告 usplash, 被廢棄的套件 xmlroff, 這份文件的來源資訊 xserver-xorg-input-evdev, Input device hotplug xserver-xorg-input-kbd, Input device hotplug xserver-xorg-input-mouse, Input device hotplug xserver-xorg-video-all, 被廢棄的套件 xserver-xorg-video-cyrix, 被廢棄的套件 xserver-xorg-video-i810, 被廢棄的套件 xserver-xorg-video-imstt, 被廢棄的套件 xserver-xorg-video-nsc, 被廢棄的套件 xserver-xorg-video-sunbw2, 被廢棄的套件 xserver-xorg-video-vga, 被廢棄的套件 xsltproc, 這份文件的來源資訊 PHP, 在這次的發行版本中有什麼新變化？ Pidgin, 在這次的發行版本中有什麼新變化？ Postfix, 在這次的發行版本中有什麼新變化？ PostgreSQL, 在這次的發行版本中有什麼新變化？ T Thunderbird, 在這次的發行版本中有什麼新變化？ Tomcat, 在這次的發行版本中有什麼新變化？ X Xfce, 在這次的發行版本中有什麼新變化？ 小辭彙 ACPI 電源進階設定介面 ALSA 先進 Linux 音效架構 APM 進階電源管理 CD Compact Disc CD-ROM Compact Disc Read Only Memory DHCP Dynamic Host Configuration Protocol DNS 網域名稱系統 DVD 數位光碟 GIMP GNU 圖形處理程式 GNU GNU's Not Unix GPG GNU Privacy Guard IDE 集成設備電路 LDAP 輕量級目錄存取協定 LILO Linux 載入程式 LSB Linux Standard Base LVM 邏輯卷軸管理程式 MTA 郵件傳送代理程式 NFS 網路檔案系統 NIC 網路介面卡 NIS 網路資訊服務 OSS 開放音效系統 RAID 磁碟陣列 RPC Remote Procedure Call SATA 串列式傳輸介面技術 SSL Secure Sockets Layer TLS Transport Layer Security USB 通用序列匯流排 UUID 通用唯一識別碼 VGA 視訊圖像陳列 WPA Wi-Fi 存取協定