Introduction

Potential problems - -Sometimes, changes have side-effects we cannot reasonably avoid, or we expose -bugs somewhere else. We document here the issues we are aware of. Please also + +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 . -

Problems with devices related to udev Although udev has been tested @@ -35,20 +36,65 @@

-Some applications may no longer work with a 2.4 kernel +

+Migration of disk drivers from IDE to PATA subsystem -Some applications in &releasename; may no longer work with a 2.4 kernel, for example -because they require epoll() support, which is not available -in 2.4 kernels. Such applications may either not work at all or not work -correctly until the system has been rebooted with a 2.6 kernel. + 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. -One example is the HTTP proxy squid. + 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 + &releasename; 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.

+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 +&releasename;. 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 &releasename;. An +unbootable system may be rescued with Super Grub2 Disk +or grml. + +

+ +

+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). +As a workaround, the files can be recreated with db4.8_load, +from the db4.8-util package. + +

+ +

Certain network sites cannot be reached by TCP Since 2.6.17, Linux aggressively uses TCP window scaling which is @@ -66,7 +112,7 @@

Automatic poweroff stops working On some older systems, shutdown -h may not power off the @@ -104,7 +150,7 @@

Asynchronous network initialization may cause unpredictable behavior On systems which use udev to load @@ -120,7 +166,7 @@

Trouble when using <acronym>WPA</acronym> secured wireless networks WPA @@ -147,7 +193,7 @@

Problems with non-ASCII characters in filenames Mounting vfat, ntfs or iso9660 file systems with files that include non-ASCII @@ -164,7 +210,7 @@

Sound stops working In rare cases, sound might stop working after the upgrade. If this happens, @@ -204,7 +250,8 @@ check whether the command -cat /dev/urandom > /dev/dsp +cat /dev/urandom > /dev/audio +or the command speaker-test works for root. @@ -212,7 +259,7 @@

Potential Filesystem Corruption on upgrade Starting with Kernel 2.6.25, Linux on the s390 architecture @@ -233,167 +280,50 @@

- -

-Upgrading to a 2.6 kernel -TODO: This section can be removed for lenny! - -The 2.6 kernel series contains major changes from the 2.4 series. Modules have -been renamed and a lot of drivers have been partially or sometimes almost -completely rewritten. Upgrading to a 2.6 kernel from an earlier version is -therefore not a process to be undertaken lightly. This section aims to make -you aware of some of the issues you may face. - - -If you compile your own kernel from source, make sure you install module-init-tools before you reboot with the 2.6 -kernel. This package replaces modutils -for 2.6 kernels. If you install one of the Debian linux-image packages, this package will be -installed automatically because of dependencies. - - -If you use LVM, you should also install lvm2 before you reboot as the 2.6 kernel does not -directly support LVM1. To access LVM1 volumes, the compatibility layer of -lvm2 (the dm-mod module) is used. You -can leave lvm10 installed; the init -scripts will detect which kernel is used and execute the appropriate version. - - -If you have entries in the /etc/modules file (the list of -modules to be loaded during system boot), be aware that some module names may -have changed. If this happens you will have to update this file with the new -module names. - - -For some SATA disk controllers, the device assigned to a drive and its -partitions may change from /dev/hdX to -/dev/sdX. If this happens, you will have to modify your -/etc/fstab and bootloader configuration accordingly. -Unless these changes are made correctly, your system may not boot -correctly It will boot the kernel but will fail when trying to -mount the root file system and will abort with an error waiting for -root file system followed by unable to mount /dev/hdX -..not found. You can use the initramfs shell to -fix this issue, after you identify the newly assigned device names in the -kernel boot messages or by reviewing the contents of -/dev/disk/. . - - -Once you have installed your 2.6 kernel, but before you reboot, make sure you -have a recovery method. First, make sure that the bootloader configuration has -entries for both the new kernel and the old, working 2.4 kernel. You should -also ensure you have a rescue floppy or CD-ROM to hand, in case -misconfiguration of the bootloader prevents you from booting the old kernel. - -

-Keyboard configuration - -The most invasive change in the 2.6 kernels is a fundamental change of the -input layer. This change makes all keyboards look like normal PC keyboards. -This means that if you currently have a different type of keyboard selected -(e.g. a USB-MAC or Sun keyboard), you will very likely end up with a -non-working keyboard after rebooting with the new 2.6 kernel. - - -If you can SSH into the box from another system, you can resolve this issue by -running dpkg-reconfigure console-data, choosing the option -Select keymap from full list and selecting a pc keyboard. - - -If your console keyboard is affected, you will probably also need to -reconfigure your keyboard for the X Window System. You can do this either by -running dpkg-reconfigure xserver-xorg or by editing -/etc/X11/xorg.conf directly. Don't forget to read the -documentation referred to in . - - -This issue is unlikely to affect the &arch-title; architecture as all -PS/2 and most USB keyboards will already be configured as a normal PC -keyboard. - -Note that if you are using a USB keyboard, this -may be configured as either a normal PC keyboard or as a USB-MAC -keyboard. In the first case you will not be affected by this -issue. -

- -

-Mouse configuration - -Again because of the changes in the input layer, you may have to reconfigure -the X Window System and gpm if your -mouse is not working after upgrading to a 2.6 kernel. The most likely cause is -that the device which gets the data from the mouse has changed. You may also -need to load different modules. - -

- -

-Sound configuration -TODO: Do we still need this for lenny? - -For the 2.6 kernel series the ALSA sound drivers are recommended over the older -OSS sound drivers. ALSA sound drivers are provided as modules by default. In -order for sound to work, the ALSA modules appropriate for your sound hardware -need to be loaded. In general this will happen automatically if you have, in -addition to the alsa-base package, -the discover package installed. The -alsa-base package also blacklists OSS -modules to prevent discover -from loading them. If you have OSS modules listed in -/etc/modules, you should remove them. - -

- -

- <acronym>NFS</acronym> mounts now handled by nfs-common - +

+ Potential issues with diversions of /bin/sh - Since util-linux 2.13 - NFS mounts are no longer handled by util-linux itself, but by nfs-common. Since not all systems - mount NFS shares and to avoid a standard - portmapper installation util-linux only suggests nfs-common. If you need to mount - NFS shares, make sure nfs-common is installed on your - system. The preinstallation script of the mount package checks whether - NFS mounts exist and aborts if - /usr/sbin/mount.nfs from nfs-common is not present or if - nfs-common is - out-of-date. Either upgrade nfs-common or unmount any - NFS mounts prior to upgrading mount. + 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 +

- Change of Romanian (ro) keyboard layout +

+ + Change in kernel policy regarding resource conflicts - Because of the upgrade to xkb-data version 1.3 in &releasename; - the default variant for Romanian (ro) layout is now producing the - correct șț characters (comma below) instead of şţ (cedilla - below). Also some of the variants have been renamed. The old - variant names still work, but users are encouraged to update their - /etc/X11/xorg.conf. More info as well as - possible side effects due to this change are available in the - - wiki (Romanian language only). + 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.

+ +

Upgrading apache2 The apache2 default configuration has changed in some ways that @@ -440,7 +370,7 @@

<acronym>NIS</acronym> and Network Manager NIS Network Manager @@ -465,150 +395,376 @@

-Security status of Mozilla products +

+ <acronym>LDAP</acronym> support + LDAP + + 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 and + #545414. + +

+ + +

+<literal>sieve</literal> service moving to its IANA-allocated port -Mozilla -The Mozilla programs firefox, -thunderbird, and -sunbird (rebranded in Debian to -iceweasel, icedove, and iceowl, respectively), are important tools for -many users. Unfortunately the upstream security policy is to urge users to -update to new upstream versions, which conflicts with Debian's policy of not -shipping large functional changes in security updates. We cannot predict it -today, but during the lifetime of &releasename; the Debian Security Team may come to a -point where supporting Mozilla products is no longer feasible and announce the -end of security support for Mozilla products. You should take this into -account when deploying Mozilla and consider alternatives available in Debian if -the absence of security support would pose a problem for you. +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. -iceape, the unbranded version -of the seamonkey internet -suite has been removed from &releasename; (with the exception of a few -internal library packages). +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. + + + +

KDE desktop -There are no huge changes in the KDE Desktop Enviroment from the version -shipped in etch. Lenny ships an updated translation and service release of KDE -3.5 that is a mixture of 3.5.9 and 3.5.10. Some modules are labeled as version -3.5.9, but have been updated and include most of the same changes found in 3.5.10. -Overall, lenny ships 3.5.10 without the kicker improvements shipped in kdebase -and some bug fixes in kdepim. +&Releasename; 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 to learn more about the changes. + +

+Upgrading from KDE 3 + -Lenny will be the last stable release including a KDE 3 series environment. +KDE 3 Desktop Environment is no longer supported in Debian &release;. +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. + + + +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 &release;. 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. +

-GNOME desktop changes and support -TODO: Remove the next three paragraphs for lenny? - -If you used the GNOME desktop in &oldreleasename; you will not benefit from some of the -changes introduced in the default configuration in Debian for &releasename;. In some -extreme cases the GNOME desktop might not properly handle your old -configuration and might not behave properly. +

+New KDE metapackages + +As noted earlier, Debian &release; 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 +by default, and a selected set of commonly used applications. - -If you have not heavily invested in configuring your GNOME desktop you might -want to move the .gconf directory in user's home -directories to a different name (such as .gconf.old) so -that it gets recreated, with the default configuration for &releasename;, upon starting -a new session. + + + +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 &oldrelease;. - -With the release of &releasename;, Debian no longer contains packages for most of the -obsolete version 1 release of GNOME, although some packages remain in order to -support some Debian packages which have not yet been updated to GNOME 2. -Packages for GTK1.2 remain fully maintained. + + + +For small form factor devices, there is an alternative environment +called +KDE Plasma Netbook +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. + + + + +

+ +

+GNOME desktop changes and support + There have been many changes in the GNOME desktop environment from the version shipped in &oldreleasename; to the version in &releasename;, you can find more information in the -GNOME 2.22 Release -Notes. +GNOME 2.30 Release +Notes. Specific issues are listed below. + +

+GDM 2.20 and 2.30 + +The GNOME Display Manager (GDM), is kept at version 2.20 for systems upgraded +from &oldreleasename;. 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 &releasename;. 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. +

-No default support for Unicode in emacs21* -Unicode +

+Device and other administrative permissions -Emacs21 and emacs21-nox are not configured to use Unicode by default. For more -information and a workaround please see Bug #419490. -Consider switching to emacs22, -emacs22-gtk, or emacs22-nox. +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 to +do so, instead of gksu. The recommended +way to give a user administrative rights is to add it to the +sudo group. +

- slurpd/replica will no longer work +

+ network-manager and ifupdown interaction - OpenLDAP has dropped support for LDAP - replication via the slurpd service in release 2.4.7. Existing - configurations need to be reconfigured for the - LDAP Sync Replication engine (syncrepl). More - verbose documentation can be found at http://www.openldap.org/doc/admin24/replication.html. + 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. -

- -

- Desktop not using full screen - The driver for Intel Mobile GM965 may wrongly detect a - VGA output and set the size of the screen to a - lower value to accomodate it. The symptom of this bug is that the - desktop manager will only use a fraction of the screen. Correct - behaviour can be forced by adding the following lines to the - /etc/X11/xorg.conf configuration file. - Section "Monitor" - Identifier "VGA" - Option "Ignore" "true" -EndSection - Please refer to the bug #496169 for more informations. + 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).

- &releasename; kernel fails to boot on Sparc workstations with PCI-Express +

+ Graphics stack changes - Due to an unfortunate interaction of a kernel fix with PCI Express - subsystem, Lenny default kernel will fail to boot on Sparc - workstations with PCI Express slots, like Ultra 25 and Ultra - 45. As this problem has been discovered very late in the release - cycle, we were unable to include a fix in the original Lenny - release, but we'll do our best to eliminate the problem for the - first point release. - Sun Ultra 25 - Sun Ultra 45 - PCI Express + There have been a number of changes to the X stack in Debian &release;. + This section lists the most important and user-visible. -

- <acronym>DHCP</acronym> failover issue +

+ 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. + +

- - When running a failover pair of DHCP servers, - the peer names need to be consistent, otherwise - DHCP will crash. - - - Please see and - for more information. - +

+ 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. + +

+ +

+ Input device hotplug + + The Xorg X server included in Debian &release; 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. + +

+ +

+ X server <quote>zapping</quote> + + Traditionally, the + CtrlAltBackspace + 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. + +

+ . Added: 437 Removed: 281 ERROR: language.ent has not a correct English version: Showing diffs for moreinfo.dbk... (ver: 5957:)Index: moreinfo.dbk =================================================================== --- moreinfo.dbk (revisión: 5957) +++ moreinfo.dbk (copia de trabajo) @@ -15,7 +15,8 @@ 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 DDP website. +url="&url-ddp;">Debian Documentation website and +Debian Wiki website Documentation for individual packages is installed into @@ -105,7 +106,7 @@ url="&url-bts;">submit bugs 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 or documentation or translate existing documentation into your own language. . Added: 4 Removed: 3 Showing diffs for old-stuff.dbk... (ver: 5957:)Index: old-stuff.dbk =================================================================== --- old-stuff.dbk (revisión: 5957) +++ old-stuff.dbk (copia de trabajo) @@ -5,7 +5,7 @@ ]> -Managing your &oldreleasename; system +Managing your &oldreleasename; system before the upgrade This appendix contains information on how to make sure you can install or upgrade &oldreleasename; packages before you upgrade to &releasename;. This should only be @@ -29,27 +29,29 @@ Checking your sources list If any of the lines in your /etc/apt/sources.list refer to -'stable', you are effectively already using &releasename;. If you have already run +'stable', you are effectively already using &releasename;. 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. -If you have also already installed packages from &releasename;, there probably is not -much point in installing packages from &oldreleasename; anymore. In that case you will -have to decide for yourself whether you want to continue or not. It is -possible to downgrade packages, but that is not covered here. +If you have also already installed packages from &releasename;, there probably +is not much point in installing packages from &oldreleasename; anymore. In +that case you will have to decide for yourself whether you want to continue or +not. It is possible to downgrade packages, but that is not covered here. Open the file /etc/apt/sources.list with your favorite -editor (as root) and check all lines beginning with deb -http: or deb ftp: for a reference to -stable. If you find any, change stable -to &oldreleasename;. +editor (as root) and check all lines beginning with +deb http: or deb ftp: for a reference to +stable. If you find any, change +stable to &oldreleasename;. If you have any lines starting with deb file:, you will have -to check for yourself if the location they refer to contains an &oldreleasename; or a &releasename; -archive. +to check for yourself if the location they refer to contains an +&oldreleasename; or a &releasename; archive. @@ -71,5 +73,27 @@

+ +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. + + +

+ . Added: 37 Removed: 13 Showing diffs for release-notes.dbk... (ver: 6592:)Index: release-notes.dbk =================================================================== --- release-notes.dbk (revisión: 6592) +++ release-notes.dbk (copia de trabajo) @@ -1,6 +1,7 @@ %languagedata; %shareddata; ]> @@ -13,16 +14,31 @@ + Steve + Langasek + vorlon@debian.org + + W. Martin Borgert debacle@debian.org + + Javier + Fernandez-Sanguino + jfs@debian.org + + + Julien + Cristau + jcristau@debian.org + There were more people! - 2009-02-14 + 2010-11-12 This document is free software; you can redistribute it and/or modify @@ -44,7 +60,7 @@ The license text can also be found at + url="http://www.gnu.org/licenses/gpl-2.0.html"/> and /usr/share/common-licenses/GPL-2 on &debian;. @@ -76,7 +92,7 @@ Adam Di Carlo - previous release + previous releases , Andreas @@ -127,11 +143,11 @@ Esko Arajärvi rework X11 upgrade - + , Frans Pop - previous release + previous release (Etch) , Giovanni @@ -146,7 +162,7 @@ Javier Fernández-Sanguino Peña - previous release + previous release (Etch), Squeeze release , Jens @@ -161,7 +177,7 @@ Josip Rodin - previous release + previous releases , Justin B @@ -216,7 +232,7 @@ Rob Bradford - previous release + previous release (Etch) , Samuel @@ -241,7 +257,7 @@ Steve Langasek - previous release + previous release (Etch) , Tobias @@ -279,32 +295,7 @@ - - Lenny dedicated to Thiemo Seufer - - The Debian Project has lost an active member of its community. Thiemo Seufer - died on December 26th, 2008 in a tragic car accident. - - - Thiemo was involved in Debian in many ways. He maintained several packages - and was the main supporter of the Debian ports to the MIPS architecture. He was - also a member of our kernel team, as well as a member of the Debian Installer - team. His contributions reached far beyond the Debian project: he also worked - on the MIPS port of the Linux kernel, the MIPS emulation of qemu, and far too - many smaller projects to be named here. - - - Thiemo's work, dedication, broad technical knowledge and ability to share this - with others will be missed. His contributions will not be forgotten. - The high standards of Thiemo's work make it hard to pick up. - - - To honour his contributions to Debian, the project dedicates the release of - Debian GNU/Linux 5.0 Lenny to Thiemo. - - - @@ -366,7 +357,7 @@ LSB - Linux Standards Base + Linux Standard Base LVM @@ -405,6 +396,14 @@ Serial Advanced Technology Attachment + SSL + Secure Sockets Layer + + + TLS + Transport Layer Security + + USB Universal Serial Bus . Added: 35 Removed: 36 ../en/showdiffs.sh: (No es un recurso versionado) svn: Hubo un problema; vea otros informes de errores para más detalles ERROR: showdiffs.sh has not a correct English version: ENG_SVN_VER=$(sed -n 's/$.*$/\1/p' $i) Showing diffs for upgrading.dbk... (ver: 6668:)Index: upgrading.dbk =================================================================== --- upgrading.dbk (revisión: 6668) +++ upgrading.dbk (copia de trabajo) @@ -5,7 +5,7 @@ ]> -Upgrades from previous releases +Upgrades from Debian &oldrelease; (&oldreleasename;)

Preparing for the upgrade @@ -26,8 +26,10 @@ The main things you'll want to back up are the contents of /etc, /var/lib/dpkg, -/var/lib/aptitude/pkgstates and the output of -dpkg --get-selections "*" (the quotes are important). +/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. The upgrade process itself does not modify anything in the @@ -49,55 +51,86 @@ executing the upgrade. -

- Make sure you are on a suitable kernel - - &releasename;'s version of glibc will not work with kernels older - than 2.6.8 on any architecture and some - architectures have higher requirements. We strongly recommend that - you upgrade to and test an &oldreleasename; - 2.6.18 or 2.6.24 kernel or a - custom kernel of at least version 2.6.18 before - beginning the upgrade process. -

Inform users in advance It's wise to inform all users in advance of any upgrades you're planning, although users accessing your system via an ssh connection should notice little during the upgrade, and should be able to continue -working. +working. If you wish to take extra precautions, back up or unmount the /home partition before upgrading. -You will probably have to do a kernel upgrade when upgrading to &releasename;, so a -reboot will normally be necessary. Typically, this will be done after the -upgrade is finished. +You will have to do a kernel upgrade when upgrading to &releasename;, so a +reboot will be necessary. +

+ +

+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 unavailableIf 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. for a significant period of time. + + + +If the system being upgraded provides critical services for your users or +networkFor 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., you can reduce the downtime if +you do a minimal system upgrade, as described in , followed by a kernel upgrade and reboot (see ), and then upgrade the packages associated with your +critical services. Upgrade these packages prior to doing the full upgrade +described in . This way you can ensure that +these critical services are running and available through the full upgrade +process, and their downtime is reduced. + + +

Prepare for recovery -Because of the many changes in the kernel between &oldreleasename; and &releasename; regarding -drivers, hardware discovery and the naming and ordering of device files, there -is a real risk that you may experience problems rebooting your system after the -upgrade. A lot of known potential issues are documented in this and the next -chapters of these Release Notes. +Because of the many changes in the kernel between &oldreleasename; and +&releasename; regarding drivers, hardware discovery and the naming and ordering +of device files, there is a real risk that you may experience problems +rebooting your system after the upgrade. A lot of known potential issues are +documented in this and the next chapters of these Release Notes. For that reason it makes sense to ensure that you will be able to recover if your system should fail to reboot or, for remotely managed systems, fail to bring up networking. + + + If you are upgrading remotely via an ssh link it is highly recommended that you take the necessary precautions to be able to access the @@ -108,6 +141,7 @@ accidentally in the middle of an upgrade there is a chance you will need to recover using a local console. + The most obvious thing to try first is to reboot with your old kernel. However, for various reasons documented elsewhere in this document, this is not @@ -120,6 +154,9 @@ system and chroot into it to investigate and fix the problem. + + Another option we'd like to recommend is to use the rescue mode of the &releasename; Debian Installer. The advantage of using the @@ -164,8 +201,16 @@ The distribution upgrade should be done either locally from a textmode virtual console (or a directly connected serial terminal), or remotely via an -ssh link. +ssh link. + + + If you are using some VPN services (such as tinc) they might not be available + throughout the upgrade process. Please see + . + + In order to gain extra safety margin when upgrading remotely, we suggest that you run upgrade processes in the virtual console provided by the @@ -193,29 +238,16 @@

- Prepare initramfs for <acronym>LILO</acronym><indexterm><primary>LILO</primary></indexterm> - - Users using the LILO bootloader should note that the default - settings for initramfs-tools now generate an - initramfs that is too large for LILO to load. Such users should - either switch to grub, or - edit the file - /etc/initramfs-tools/initramfs.conf, changing - the line MODULES=most to read - MODULES=dep - - - Note, however, that doing this will cause initramfs-tools to install onto the - initramfs only those modules that are required for the particular - hardware that it is being run on. If you want to generate boot - media that will work on more hardware than just the machine you're - generating it on, you should leave the line as - MODULES=most and make sure you do - not use LILO. - +

+Remove conflicting packages + +Due to bug #512951, the splashy package needs to be purged prior to the +upgrade. + + # apt-get purge splashy + +

@@ -230,10 +262,18 @@ before you begin upgrading. +Direct upgrades from Debian releases older than &oldrelease; (&oldreleasename;) +are not supported. +Please follow the instructions in the Release +Notes for &debian; &oldrelease; to upgrade to &oldrelease; first. + + This procedure also assumes your system has been updated to the latest point release of &oldreleasename;. If you have not done this or are unsure, follow the instructions in . +

Review actions pending in package manager @@ -325,13 +365,13 @@ upgraded. -The hold package state for aptitude can be changed using: +The hold package state for apt-get can be changed using: -# aptitude hold package_name +# echo package_name hold | dpkg --set-selections -Replace hold with unhold to unset the +Replace hold with install to unset the hold state. @@ -352,6 +392,7 @@

Unofficial sources and backports @@ -372,61 +413,9 @@ has some information on how to deal with file conflicts if they should occur. -

- Using <literal>backports.org</literal> packages - - backports.org is a semi-official repository - provided by &debian; developers, which provides newer packages for - the stable release, based on a rebuild from the packages from the - testing archive. - - - The backports.org repository mainly contains packages - from testing, with reduced version numbers - so that the upgrade path from &oldreleasename; backports to - &releasename; still works. However, there are a few backports - which are made from unstable: security updates, plus the following - exceptions: Firefox, the Linux kernel, OpenOffice.org, and X.Org. - - - If you do not use one of these exceptions, you can safely upgrade - to &releasename;. If you use one of these exceptions, set the - Pin-Priority (see apt_preferences 5 ) - temporarily to 1001 for all packages from &releasename;, - and you should be able to do a safe dist-upgrade too. See the - backports - FAQ. - -

-Manually unmarking packages - -To prevent aptitude from removing some packages that were -pulled in through dependencies, you need to manually unmark them as -auto packages. This includes OpenOffice and Vim for -desktop installs: - - -# aptitude unmarkauto openoffice.org vim - - -And 2.6 kernel images if you have installed them using a kernel metapackage: - - -# aptitude unmarkauto $(dpkg-query -W 'kernel-image-2.6.*' | cut -f1) - - - - You can review which packages are marked as auto in - aptitude by running: - - # aptitude search 'i~M' -

@@ -444,22 +433,6 @@ hard disk, then CD-ROMs, and then HTTP/FTP mirrors). - - - You might need to add an GPG checking exception - for DVDs and CD-ROMs. Add - the following line to /etc/apt/apt.conf, if - it's not already in - /etc/apt/apt.conf.d/00trustcdrom: - - APT::Authentication::TrustCDROM "true"; - - This does not work with - DVD/CD-ROM image files, - however. - - - A release can often be referred to both by its codename (e.g. &oldreleasename;, &releasename;) and by @@ -471,6 +444,7 @@ If you use the status name instead, you will just see loads of updates for packages available as soon as a release has happened. +

Adding APT Internet sources @@ -588,9 +562,11 @@ Upgrading packages The recommended way to upgrade from previous &debian; releases is to -use the package management tool aptitude. This program -makes safer decisions about package installations than running -apt-get directly. +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. Don't forget to mount all needed partitions (notably the root and @@ -606,12 +582,13 @@ any sources entries pointing to &oldreleasename;. - Source lines for a CD-ROM will often refer to + Source lines for a CD-ROM might sometimes refer to unstable; although this may be confusing, you should not change it. +

Recording the session @@ -630,7 +607,7 @@ The typescript will also allow you to review information that has scrolled -off-screen. Just switch to VT2 (using +off-screen. If you are at the system's console, just switch to VT2 (using AltF2) and, after logging in, use less -R ~root/upgrade-&releasename;.script to view @@ -642,8 +619,8 @@ -TODO: Could mention the script I provided in 400725 which is useful if you -have not dumped the timing file +TODO: (jfs) Could mention the script I provided in #400725 which is useful if +you have not dumped the timing file @@ -663,13 +640,8 @@ This is done by executing: -# aptitude update +# apt-get update - -Running this the first time new sources are updated will print out some -warnings related to the availability of the sources. These warnings are -harmless and will not appear if you rerun the command again. -

@@ -677,7 +649,7 @@ 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 . First, any package needed for installation that +linkend="upgrading-full"/>. 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 @@ -691,16 +663,16 @@ difficult to recover from. -Both aptitude and apt will 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 can show you detailed information of the disk +space needed for the installation. Before executing the upgrade, you can see +this estimate by running: -# aptitude -y -s -f --with-recommends dist-upgrade +# 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/yyyMB of archives. After unpacking AAAMB will be used. -Would download/install/remove packages. +Need to get xx.xMB of archives. +After this operation, AAAMB of additional disk space will be used. @@ -712,8 +684,16 @@ space. + -If you do not have enough space for the upgrade, make sure you free up 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: @@ -721,8 +701,8 @@ Remove packages that have been previously downloaded for installation (at /var/cache/apt/archives). Cleaning up the package cache by -running apt-get clean or aptitude clean -will remove all previously downloaded package files. +running apt-get clean will remove all previously downloaded +package files. @@ -749,14 +729,12 @@ You can list packages that take up most of the disk space with aptitude. Start -aptitude into visual mode, +aptitude in visual mode, select ViewsNew Flat Package -List (this menu entry is available only after etch -version), press l and enter ~i, press -S and enter ~installsize, then it -will give you nice list to work with. Doing this after upgrading -aptitude should give you -access to this new feature. +List, press l and enter +~i, press S and enter +~installsize, then it will give you nice list to work +with. @@ -771,10 +749,11 @@ -Temporarily move to another system, or permanently remove, system logs residing -under /var/log/. + Temporarily move to another system, or permanently remove, system logs + residing under /var/log/. + Use a temporary /var/cache/apt/archives: You @@ -833,7 +812,19 @@ is mounted on your system. + + + + Do a minimal upgrade of the system (see ) + 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. + + + + + Note that in order to safely remove packages, it is advisable to switch your sources.list back to &oldreleasename; as described in

- Upgrade apt and/or aptitude first - - Several bug reports have shown that the versions of the aptitude and apt packages in etch are often unable to - handle the upgrade to &releasename;. In &releasename;, apt is better at dealing with complex chains - of packages requiring immediate configuration and aptitude is smarter at searching for - solutions to satisfy the dependencies. These two features - are heavily involved during the dist-upgrade to &releasename;, so it - is necessary to upgrade these two packages before upgrading - anything else. For apt, run: - # apt-get install apt - and for aptitude (if you have - it installed) run: - # aptitude install aptitude - - - This step will automatically upgrade libc6 and locales and will pull in SELinux support libraries - (libselinux1). At this point, some - running services will be restarted, including xdm, - gdm and kdm. As a consequence, local X11 - sessions might be disconnected. - SELinux - -

- Using aptitude's list of automatically-installed packages with apt - - aptitude maintains a list - of packages that were installed automatically (for instance, as - dependencies of another package). In &releasename;, apt now has this feature as well. - - - The first time the &releasename; version of aptitude is run, it will read in its - list of automatically installed packages and convert it for use - with the &releasename; version of apt. If you have aptitude installed, you should at - least issue one aptitude - command to do the conversion. One way to do this is by searching for - a non-existent package: - # aptitude search "?false" - -

Minimal system upgrade -Because of certain necessary package conflicts between &oldreleasename; and &releasename;, running -aptitude dist-upgrade directly will often 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 dist-upgrade. +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 . -First, run: +To do this first, run: -# aptitude upgrade +# apt-get upgrade This has the effect of upgrading those packages which can be upgraded without requiring any other packages to be removed or installed. + -The next step will vary depending on the set of packages that you have -installed. These release notes give general advice about which method should -be used, but if in doubt, it is recommended that you examine the package -removals proposed by each method before proceeding. +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. - -Some common packages that are expected to be removed include base-config, hotplug, xlibs, netkit-inetd, python2.3, xfree86-common, and xserver-common. For more information about -packages obsoleted in &releasename;, see . - +

-Upgrading the kernel -TODO: This is outdated for lenny, right? + + +

+Upgrading the kernel and udev -The udev version in &releasename; does not -support kernel versions earlier than 2.6.15 (which includes &oldreleasename; 2.6.8 -kernels), and the udev version in &oldreleasename; -will not work properly with the latest kernels. In addition, installing the -&releasename; version of udev will force the -removal of hotplug, used by Linux 2.4 -kernels. +The udev version in &releasename; +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 &oldreleasename; (version 2.6.26) have +CONFIG_SYSFS_DEPRECATED enabled, and the udev version in &oldreleasename; 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. -As a consequence, the previous kernel package will probably not boot properly -after this upgrade. Similarly, there is a time window during the upgrade in -which udev has been upgraded but the -latest kernel has not been installed. If the system were to be rebooted at -this point, in the middle of the upgrade, it might not be bootable because of -drivers not being properly detected and loaded. (See for recommendations on preparing for this -possibility if you are upgrading remotely.) +Booting the 2.6.26 kernel from &oldreleasename; with the udev from &releasename; 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. + -Unless your system has the desktop task installed, or other -packages that would cause an unacceptable number of package removals, it is -therefore recommended that you upgrade the kernel on its own at this point. - - To proceed with this kernel upgrade, run: -# aptitude install linux-image-2.6-flavor +# apt-get install linux-image-2.6-flavor See for help in determining which flavor of kernel package you should install. + +Users of the grub bootloader should +make sure that update-grub is run as part of the kernel +upgrade, or run it manually. + -In the desktop case, it is unfortunately not possible to ensure the new kernel -package is installed immediately after the new udev is installed, so there is a window of unknown -length when your system will have no kernel installed with full hotplug -support. See for information on configuring your -system to not depend on hotplug for booting. +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 +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.. +You can do this by running: + + +# apt-get install udev + + + +Once you have upgraded both the kernel and udev the system should be rebooted. + +

-Upgrading the rest of the system + +

+Upgrading the system -You are now ready to continue with the main part of the upgrade. Execute: +Once you have taken the previous steps, you are now ready to continue +with the main part of the upgrade. Execute: -# aptitude dist-upgrade +# 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 &oldreleasename; to + &releasename;. + + This will perform a complete upgrade of the system, i.e. install the newest available versions of all packages, and resolve all possible dependency changes @@ -1004,34 +969,63 @@ 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 aptitude -f install +trying apt-get -f install package.

-Getting package signatures -TODO: Can be removed for lenny, right? +

+ +

+Possible issues during upgrade + -After the upgrade, with the new version of apt you can now -update your package information, which will include the new package signature -checking mechanism: +The following sections describe known issues that might appear +during an upgrade to &releasename;. - -# aptitude update - + +

+cryptoloop support not included in the &releasename; Linux kernel -The upgrade will have already retrieved and enabled the signing keys for -Debian's package archives. If you add other (unofficial) package sources, -apt will print warnings related to its inability to confirm -that packages downloaded from them are legitimate and have not been tampered -with. For more information please see . +Support for cryptoloop has been dropped from the Linux kernel packages +included in Debian &release;. Existing installations using cryptoloop need to +be transitioned to dm-crypt before the upgrade.

-Possible issues during upgrade +

+Expected removals +The upgrade process to &releasename; 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 &releasename;, see . + + +

+ +

+Errors running aptitude or apt-get + If an operation using aptitude, apt-get, or dpkg fails with the error @@ -1052,18 +1046,24 @@ This assumes that you do not yet have this variable set in that file. + +

+ +

+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. aptitude will alert you of this +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 aptitude command +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 -aptitude or +apt-get or # dpkg --remove package_name @@ -1072,7 +1072,7 @@ to eliminate some of the offending packages, or -# aptitude -f install +# apt-get -f install # dpkg --configure --pending @@ -1081,6 +1081,12 @@ # dpkg --install /path/to/package_name.deb + +

+ +

+File conflicts + File conflicts should not occur if you upgrade from a pure &oldreleasename; system, but can occur if you have unofficial backports installed. A file conflict will @@ -1104,16 +1110,22 @@ After fixing things up, you should be able to resume the upgrade by repeating -the previously described aptitude commands. +the previously described apt-get commands. + +

+ +

+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 or /etc/terminfo -directories, 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. +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. If you're not sure what to do, write down the name of the package or file and @@ -1122,8 +1134,64 @@

+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 +CtrlAltF1 +to switch back to the virtual terminal 1 if in the graphical startup screen or +use AltF1 +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 AltLeft Arrow or +AltRight +Arrow to switch between the different text-mode terminals. +

+Special care for specific packages + +In most cases, packages should upgrade smoothly between &oldreleasename; +and &releasename;. 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. + +

+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 &releasename;. + + +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. + +

+ +

Upgrading your kernel and related packages @@ -1157,29 +1225,34 @@ # 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.18-6-686', it is recommended that you install linux-image-2.6-686. (Note that the k7 flavor no -longer exists; if you are currently using the k7 kernel flavor, you should -install the 686 flavor instead.) 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: +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 aptitude install to install it. Once +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;. Install the kernel-package tool and read the documentation in -/usr/share/doc/kernel-package. +/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 @@ -1190,70 +1263,47 @@

Device enumeration reordering -&releasename; features a more robust mechanism for hardware discovery than previous -releases. However, this may cause changes in the order devices are discovered -on your system, affecting the order in which device names are assigned. 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. Please -note that the new mechanism means that if you e.g. exchange ethernet adapters -in a running &releasename; system, the new adapter will also get a new interface name. +In &oldreleasename; 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, you can avoid this reordering by using udev rules, more specifically, through the -definitions at -/etc/udev/rules.d/70-persistent-net.rules -The rules there are automatically generated by the script -/etc/udev/rules.d/75-persistent-net-generator.rules to -have persistent names for network interfaces. Delete this symlink to disable -persistent device naming for NICs by udev. . Alternatively you can -use the ifrename utility to bind physical devices to -specific names at boot time. See -ifrename 8 - and iftab -5 for more information. The two -alternatives (udev and -ifrename) should not be used at the same time. +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 &oldreleasename;, no additional action should be +required when upgrading to &releasename; 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 &releasename; +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 can avoid this reordering by using initramfs-tools and configuring it to load storage -device driver modules in the same order they are currently loaded. To do this, -identify the order the storage modules on your system were loaded by looking at -the output of lsmod. lsmod lists modules -in the reverse order that they were loaded in, i.e., the first module in the -list was the last one loaded. Note that this will only work for devices which -the kernel enumerates in a stable order (like PCI devices). +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 , 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 +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. +in the /dev/disk/by-uuid/ directory or LVM device names +in /dev/mapper/. - -However, removing and reloading modules after initial boot will affect this -order. Also, your kernel may have some drivers linked statically, and these -names will not appear in the output of lsmod. You may be -able to decipher these driver names and load order from looking at -/var/log/kern.log, or the output of -dmesg. - - -Add these module names to /etc/initramfs-tools/modules in -the order they should be loaded at boot time. Some module names may have -changed between &oldreleasename; and &releasename;. For example, sym53c8xx_2 has become sym53c8xx. - - -You will then need to regenerate your initramfs image(s) by executing -update-initramfs -u -k all. - - -Once you are running a &releasename; kernel and udev, you may reconfigure your system to access -disks by an alias that is not dependent upon driver load order. These aliases -reside in the /dev/disk/ hierarchy. -

Boot timing issues @@ -1279,20 +1329,35 @@

+ +

Things to do before rebooting -When aptitude dist-upgrade has finished, the formal upgrade +When apt-get dist-upgrade has finished, the formal upgrade is complete, but there are some other things that should be taken care of before the next reboot. -

+ + +There is probably no need at all to run lilo manually on upgrade anymore, +/etc/kernel/postinst.d/zz-lilo runs lilo unconditionally on kernel upgrade; +but don't throw this all away until the lilo maintainers confirm this +isn't required on upgrade for the second-stage bootloader. + + + +

Rerun lilo If you are using lilo as your bootloader (it is the default bootloader for some installations of &oldreleasename;) it is -strongly recommended that you rerun lilo after the upgrade: +strongly recommended that you rerun lilo after the +upgrade. The lilo package will +offer to do this for you as part of the upgrade, but if you decline or don't +see the prompt, you should run lilo by hand: # /sbin/lilo @@ -1308,9 +1373,9 @@ If you encounter any issues when running lilo, review the -symbolic links in / to vmlinuz and -initrd and the contents of your -/etc/lilo.conf for discrepancies. +symbolic links in / or /boot to +vmlinuz and initrd and the +contents of your /etc/lilo.conf for discrepancies. If you forgot to rerun lilo before the reboot or the system @@ -1324,6 +1389,7 @@

Upgrading mdadm TODO: Remove for lenny? @@ -1366,11 +1432,17 @@ hdc, hdd. The new drivers will name the same disks respectively sda, sdb, sdc, - sdd. The problem appears when the upgrade does + 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. + 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 &releasename; should cover both situations + automatically. @@ -1388,7 +1460,7 @@ 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. + supported in Debian since the etch release. @@ -1460,12 +1532,22 @@ Find out the universally unique identifier of your filesystem by issuing: - ls -l /dev/disk/by-uuid | grep hda6 + ls -l /dev/disk/by-uuid | grep hda6. You can also use blkid /dev/hda6. + + - You should get a line similar to this one: + 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" + + The UUID is the name of the symbolic link pointing to /dev/hda6 i.e.: d0dfcc8a-417a-41e3-ad2e-9736317f2d8a. @@ -1481,7 +1563,7 @@ Edit /boot/grub/menu.lst and change the line: # kopt=root=/dev/hda6 ro - to + to use UUID instead: # kopt=root=UUID=d0dfcc8a-417a-41e3-ad2e-9736317f2d8 ro @@ -1516,6 +1598,9 @@

How to recover from the problem after the upgrade @@ -1530,6 +1615,7 @@ linkend="solution3"/>. + @@ -1538,15 +1624,15 @@ related to this entry. You will see something like: root (hd0,0) -kernel /vmlinuz-2.6.26-1-686 root=/dev/hda6 ro -initrd /initrd.img-2.6.26-1-686 +kernel /vmlinuz-2.6.32-5-686 root=/dev/hda6 ro +initrd /initrd.img-2.6.32-5-686 Highlight the line - kernel /vmlinuz-2.6.26-1-686 root=/dev/hda6 ro + kernel /vmlinuz-2.6.32-5-686 root=/dev/hda6 ro press the e key and replace hdX with @@ -1556,7 +1642,7 @@ c or d depending of your system). In my example the line becomes: - kernel /vmlinuz-2.6.26-1-686 root=/dev/sda6 ro + kernel /vmlinuz-2.6.32-5-686 root=/dev/sda6 ro Then press Enter to save the modification. If other lines show @@ -1591,10 +1677,10 @@ to use as root file system. The proposed choices will look something like: - /dev/ide/host0/bus0/target0/lun0/part1 -/dev/ide/host0/bus0/target0/lun0/part2 -/dev/ide/host0/bus0/target0/lun0/part5 -/dev/ide/host0/bus0/target0/lun0/part6 + /dev/sda1 +/dev/sda2 +/dev/sda5 +/dev/sda6 @@ -1678,15 +1764,15 @@ Find the section similar to: ## ## End Default Options ## -title Debian GNU/Linux, kernel 2.6.26-1-686 +title Debian GNU/Linux, kernel 2.6.32-5-686 root (hd0,0) -kernel /vmlinuz-2.6.26-1-686 root=/dev/hda6 ro -initrd /initrd.img-2.6.26-1-686 +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.26-1-686 (single-user mode) +title Debian GNU/Linux, kernel 2.6.32-5-686 (single-user mode) root (hd0,0) -kernel /vmlinuz-2.6.26-1-686 root=/dev/hda6 ro single -initrd /initrd.img-2.6.26-1-686 +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 @@ -1728,54 +1814,85 @@ -If the new kernel image metapackage was pulled in as a dependency of the old -one, it will be marked as automatically installed, which should be corrected: - - -# aptitude unmarkauto $(dpkg-query -W 'linux-image-2.6-*' | cut -f1) - - - - Remove obsolete and unused packages as described in . You should review which configuration files they use and consider purging the packages to remove their configuration files. + +

+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; +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 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. + +

-Deprecated packages - -TODO: the only packages listed here at lenny release time were all packages -that are already gone in lenny; if there are other deprecations we want to -list here, someone will need to populate that list. - +

+ +

+Deprecated components With the next release of &debian; &nextrelease; (codenamed -&nextreleasename;) a bigger number of server packages -will be deprecated, thus updating to newer versions of those now will save you -from trouble when updating to &nextrelease;. +&nextreleasename;) some features will be deprecated. Users +will need to migrate to other alternatives to prevent +trouble when updating to &nextrelease;. + -This includes the following packages: +This includes the following features: + + + -apache (1.x), successor is -apache2 +OpenVZ and Linux-Vserver: &debian; &release; 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 for more information. + + + + +

Obsolete packages Introducing several thousand new packages, &releasename; also retires and omits more -than two thousand old packages that were in &oldreleasename;. It provides no upgrade path +than four thousand old packages that were in &oldreleasename;. 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 &releasename;'s release Or for as @@ -1800,15 +1917,20 @@ provides a similar section but the listing it presents might differ. -Also, if -you have used aptitude to manually install packages in &oldreleasename; +Also, if you have used aptitude or +apt-get to manually install packages in &oldreleasename; 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. Also, -aptitude, unlike deborphan will not mark -as obsolete packages that you manually installed, as opposed to those that were -automatically installed through dependencies. +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 + There are additional tools you can use to find obsolete packages such as deborphan, debfoster or @@ -1828,6 +1950,108 @@ url="&url-bts;cgi-bin/pkgreport.cgi?pkg=ftp.debian.org&archive=yes">ftp.debian.org pseudo-package. + + + + 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; system is the Unified Installer, available + for download from + + + + + 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 + &releasename; 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 &oldreleasename; to display a splash image at boot + time, usplash, is no longer + available. It has been replaced by + plymouth. + + + + +

Dummy packages @@ -1841,45 +2065,15 @@ 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 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. +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.

- -

- Plans for the next Debian release - -

- Drop of the ARM ABI port, in favor of the ARM EABI port - - - Debian lenny has two different and incompatible ARM ports: the - old ABI port (arm) and the new EABI port (armel). Debian lenny - is the last release with support for the ARM ABI port and future - releases will only support the ARM EABI or armel port. It's - therefore recommended to use armel for new installations of - lenny. - - - - With the exception of Netwinder, installer images for supported - ARM machines are available for both arm and armel in lenny. - Netwinder support is only available for arm and it will be - dropped after lenny along with the arm port. - Netwinder - - - - Please visit this page to - learn more about the ARM EABI (armel) port. - -

. Added: 640 Removed: 446 Showing diffs for whats-new.dbk... (ver: 6592:)Index: whats-new.dbk =================================================================== --- whats-new.dbk (revisión: 6592) +++ whats-new.dbk (copia de trabajo) @@ -7,11 +7,19 @@ What's new in &debian; &release; -The Wiki has more information +The Wiki has more information about this topic. + + + -This release adds official support for the ARM EABI (armel). +This release drops official support for the HP +PA-RISC ('hppa'), Alpha ('alpha') and ARM ('arm') architectures. The following are the officially supported architectures for &debian; @@ -20,16 +28,11 @@ -Intel x86 ('i386') +32-bit PC ('i386') -Alpha ('alpha') - - - - SPARC ('sparc') @@ -40,11 +43,6 @@ -ARM ('arm') - - - - MIPS ('mips' (big-endian) and 'mipsel' (little-endian)) @@ -55,17 +53,12 @@ -HP PA-RISC ('hppa') - - - - S/390 ('s390') -AMD64 ('amd64') +64-bit PC ('amd64') @@ -74,16 +67,28 @@ + + +In addition to the officially supported architectures, &debian; 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. + + You can read more about port status, and port-specific information for your architecture at the Debian port web pages. - -TODO: freeBSD port not ready for lenny, but in very good shape - - +

What's new for ARM? @@ -117,17 +122,26 @@ role="package">ixp4xx-microcode in non-free. Installer images for Debian which include this microcode will continue to be made available from slug-firmware.net. + url="http://slug-firmware.net">slug-firmware.net.

+What's new for S390? + + The 32-bit s390 kernel flavour is no longer + provided. As a consequence, only hardware with z/Architecture support + will be supported in Debian &release;, using the + s390x kernel flavour. + +

What's new in the distribution? - TODO: Numbers need to be reviewed, these values have been obtained + TODO: Make sure you update the numbers in the .ent file using the changes-release.pl script found under ../ - DONE for lenny release @@ -143,41 +157,50 @@ see any updates for these packages and they will be marked as 'obsolete' in package management front-ends. + + + -With this release, &debian; updates from X.Org 7.1 to X.Org 7.3. +With this release, &debian; updates from X.Org 7.3 to X.Org 7.5. &debian; again ships with several desktop applications and environments. Among others it now includes the desktop environments GNOMEGNOME - 2.22 With some modules from GNOME 2.20. + 2.30 With some modules from GNOME 2.32. , KDEKDE - 3.5.10, XfceXfce 4.4.2, and - LXDELXDE 0.3.2.1+svn20080509. + 4.4.5, XfceXfce 4.6.2, and + LXDELXDE 0.5.0. Productivity applications have also been upgraded, including the office suites OpenOffice.orgOpenOffice.org - 2.4.1 and KOfficeKOffice - 1.6.3 as well as - GNUcashGNUcash 2.2.6, - GNUmericGNUmeric 1.8.3 and - AbiwordAbiword 2.6.4. + 3.2.1 and KOfficeKOffice + 2.2.1 as well as + GNUcashGNUcash 2.2.9, + GNUmericGNUmeric 1.10.8 and + AbiwordAbiword 2.8.2. Updates of other desktop applications include the upgrade to - EvolutionEvolution 2.22.3 - and PidginPidgin 2.4.3 (formerly known as GaimGaim). The - MozillaMozilla suite has + EvolutionEvolution 2.30.3 + and PidginPidgin 2.7.3. + The MozillaMozilla suite has also been updated: iceweasel - (version 3.0.6) is the unbranded + (version 3.5.13) is the unbranded FirefoxFirefox web browser and icedove - (version 2.0.0.19) is the unbranded + (version 3.0.7) is the unbranded ThunderbirdThunderbird mail client. + + + Among many others, this release also includes the following software updates: @@ -197,113 +220,118 @@ ApacheApache - 2.2.3 2.2.9 + 2.2.16 BINDBIND DNS Server - 9.3.4 - 9.5.0 + 9.6.0 + 9.7.1 CherokeeCherokee web server - 0.5.5 0.7.2 + 1.0.8 CourierCourier MTA - 0.53.3 0.60.0 + 0.63.0 DiaDia - 0.95.0 0.96.1 + 0.97.1 EkigaEkiga VoIP Client - 2.0.3 2.0.12 + 3.2.7 EximExim default email server - 4.63 4.69 + 4.72 GNU Compiler Collection as default compilerGCC - 4.1.1 4.3.2 + 4.4.5 GIMPGIMP - 2.2.13 2.4.7 + 2.6.10 the GNU C library - 2.3.6 2.7 + 2.11.2 lighttpd - 1.4.13 1.4.19 + 1.4.28 maradns - 1.2.12.04 1.3.07.09 + 1.4.03 MySQLMySQL - 5.0.32 5.0.51a + 5.1.49 OpenLDAP - 2.3.30 2.4.11 + 2.4.23 OpenSSHOpenSSH - 4.3 5.1p1 + 5.5p1 PHPPHP - 5.2.0 5.2.6 + 5.3.2 PostfixPostfix MTA - 2.3.8 2.5.5 + 2.7.1 PostgreSQLPostgreSQL - 8.1.15 8.3.5 + 8.4.5 Python - 2.4.4 2.5.2 + 2.6.6 + + Samba + 3.2.5 + 3.5.5 + TomcatTomcat - 5.5.20 5.5.26 + 6.0.28 - Note: No significant changes for Roxen4, Boa, and thttpd TODO: (JFS) List other server software? RADIUS? Streaming ? + The official &debian; distribution now ships on 4 to 5 binary DVDs DVD @@ -313,46 +341,170 @@ 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. For -the first time, &debian; is also released as Blu-ray +i386 architectures, along with the source code. +&debian; is also released as Blu-ray Blu-ray images, also for the amd64 and i386 architectures, along with the source code. -Debian now supports Linux Standards Base (LSB) version 3.2. -Debian &oldrelease; did support version 3.1. -Linux Standards Base +Debian still supports Linux Standard Base (LSB) version 3.2. +Linux Standard Base + +

+Firmware moved to the non-free section + +Some drivers included in the Linux kernel used to contain non-free firmware +blobs. Starting from &releasename; 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. + +

+ +

Package management + +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 &releasename; APT automatically installs recommended packages by defaultThis 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.. +This can be changed by adding the following line in +/etc/apt/apt.conf: +APT::Install-Recommends "false"; + + -TODO: is aptitude always prefered over apt-get? +TODO: Do we have to mention dpkg triggers here or elsewhere? +

+ +

+Dependency booting + -The preferred program for package management from the command line is -aptitude, which can perform the same package -management functions as apt-get and has proven to be -better at dependency resolution. If you are still using -dselect, you should switch to aptitude as the official front-end for package -management. +An important improvement in the &debian; 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 +&oldreleasename;, if possible. + -For &releasename; an advanced conflict resolving mechanism has been -implemented in aptitude that will try to find the -best solution if conflicts are detected because of changes in -dependencies between packages. +This feature is enabled through the use of insserv +by sysv-rc to order init.d scripts based on their declared +dependenciesThese dependences are declared through the use of +the header format specified in the Linux Standard Base (LSB). +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. - -TODO: Do we have to mention dpkg triggers here or elsewhere? - + +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. +

+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. + + +

+ +

+ 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 and in the Debian wiki. + +

+ +

+ <acronym>LDAP</acronym> support + LDAP + + 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. + +

The proposed-updates section @@ -364,12 +516,12 @@ 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; - developers may upload new packages directly to - proposed-updates. The current list of packages - can be seen at proposed-updates as well. + Secondly, &debian; 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 + &url-ftpmaster;/proposed-updates.html. @@ -381,7 +533,7 @@ deb &url-debian-mirror-eg;/debian &releasename;-proposed-updates main contrib deb-src &url-debian-mirror-eg;/debian &releasename;-proposed-updates main contrib - The next time you run aptitude update, the + 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. @@ -392,118 +544,60 @@

-backports.org/backports.debian.org -TODO: write about probability backports.org becoming official +

+ The stable-updates section + + Some packages from proposed-updates may also be made + available via the &releasename;-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 + &releasename;-updates will be included in point + releases. + + + Note that this replaces the functionality previously provided by the + volatile.debian.org archive. + + + In order to use packages from &releasename;-updates, + you can add an entry to your sources.list: + + deb &url-debian-mirror-eg;/debian &releasename;-updates main contrib +deb-src &url-debian-mirror-eg;/debian &releasename;-updates main contrib + + The next time you run apt-get update, the + system will become aware of the packages in the + &releasename;-updates section and will consider them + when looking for packages to upgrade. + + + When a new package is made available via &releasename;-updates, + this will be announced on the debian-stable-announce mailing list. +

+backports.org/backports.debian.org -

-System improvements - -There have been a number of changes in the distribution that will benefit new -installations of &releasename;, but may not be automatically applied on upgrades from -&oldreleasename;. This section gives an overview of the most relevant changes. + +The service provided by the backports.org repositories has been integrated in +Debian infrastructure and is now an official Debian +service, hosted at backports.debian.org. - - -SELinux priority standard, but not enabled by default - -SELinux - -The packages needed for SELinux (Security-Enhanced Linux) support have been promoted to priority -standard. This means that they will be installed by -default during new installations. For existing systems you can install SELinux -using: - - -# aptitude install selinux-basics - - -Note that SELinux support is not enabled by default. -Information on setting up and enabling SELinux can be found on the Debian Wiki. - - - - -New default inet superdaemon - -TODO: Remove for lenny? - -The default inet superdaemon for &releasename; is openbsd-inetd instead of inetutils-inetd. It will not be started if no -services are configured, as is the case by default. The new default daemon will -be installed automatically on upgrade. - - - - -New default syslog daemon - - -The package rsyslog takes -over as default system and kernel logging daemon for Debian &release;, -replacing syslogd and klogd. -With stock logging rules, it can be used as a drop-in replacement; if -you have custom rules, you should migrate them to the new configuration -file, /etc/rsyslog.conf. - - -Users upgrading from &oldreleasename; need to install rsyslog and remove sysklogd manually. The default syslog daemon is -not replaced automatically at the upgrade to &releasename;. - - - - -Changes in default features for ext2/ext3 - -TODO: Remove for lenny? - -New ext2 and ext3 file systems will be created with features -dir_index and resize_inode enabled by -default. The first feature speeds up operations on directories with many -files; the second makes it possible to resize a file system on-line (i.e. -while it is mounted). - - -Users upgrading from &oldreleasename; could consider adding the -dir_index flag manually using -tune2fs The flag -filetype should already be set on most file systems, -except possibly on systems installed before &oldreleasename;. ; the -resize_inode flag cannot be added to an existing file -system. It is possible to check which flags are set for a file system using -dumpe2fs -h. - - - - -Better support for UTF-8 - - -A number of additional applications will be set up to use UTF-8 by -default or have better UTF-8 support than before. See at &url-wiki;UTF8BrokenApps about -applications that still have difficulties in handling UTF-8. - - - - - -The Debian Wiki -has some additional information about changes between &oldreleasename; and &releasename;. - +

+ +

Debian Live -With &releasename; Debian presents official Live systems for the amd64 +With &releasename; Debian provides official Live systems for the amd64 and i386 architectures. Live system Debian Live @@ -515,138 +609,39 @@ produced by a tool named live-helper, which can easily be used to create custom live images. More information about the Debian Live project -can be found at . +can be found at .

-Major kernel-related changes +

+Comprehensive support for neuroimaging research -&debian; &release; ships with kernel version &kernelversion; for all -architectures. +&debian; &release; 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 and Debian Med +task pages for a comprehensive list of included software and the NeuroDebian webpage for further +information. +neuroimaging research +Debian Med +Debian Science +NeuroDebian +packagesants +packagesmrtrix +packagespsychopy +packagesodin +packagesnipype - -There have been major changes both in the kernel itself and in the -packaging of the kernel for Debian. Some of these changes complicate -the upgrade procedure and can potentially result in problems while -rebooting the system after the upgrade to &releasename;. This section -gives an overview of the most important changes; information on how -to work around potential issues is included in later chapters. - -

-Changes in kernel packaging - - -New OpenVZOpenVZ kernel flavor - - -&debian; &release; provides pre-built kernel images for OpenVZ, a -second virtualization solution to go alongside the Linux-VServer -support included in &oldreleasename;. Advantages of OpenVZ include -support for live migration, at the expense of a slightly higher -overhead. -virtualization -VServer - - - - -Kernel x86 packages unified - - -In previous releases there was a special -k7 kernel -flavor for 32-bit AMD Athlon/Duron/Sempron processors. This variant -has been dropped; the single single flavor -686 -now handles all AMD/Intel/VIA 686 class processors. - - - - - -Where possible, dummy transition packages that depend on the new packages have -been provided for the dropped packages. -

-New utilities to generate initrds -TODO: Remove for lenny? - -The Debian kernel image packages for &arch-title; require an initrd -for booting the system. Because of changes in the kernel, the utility -used to generate initrds in &oldreleasename;, initrd-tools is not included anymore. -Two new utilities have been developed that replace -it: initramfs-tools and -yaird. The concepts behind -the new utilities are very different; an overview is available on the -Debian -Wiki. Both will generate an initrd using the -initramfs file system, which is a compressed -cpio archive. The default and recommended utility -is initramfs-tools. -yaird is not included in &releasename;. - - -Upgrading to a &releasename; kernel will cause initramfs-tools to be installed by default. If you -are upgrading from a 2.4 kernel to a 2.6 Debian kernel, you must use -initramfs-tools. -TODO: Remove? yaird is not in lenny! -Using yaird will cause linux-image-2.6 -installations to fail if you are running a 2.2 or 2.4 kernel. - -

- -

- - Emdebian 1.0 (based on &debian; &releasename; &release;) - Emdebian - - - Lenny now contains the build tools for Emdebian which allow Debian - source packages to be cross-built and shrunk to suit embedded ARM - systems. - - - - The Emdebian 1.0 distribution itself contains prebuilt ARM packages - sufficient to create root filesystems that can be customised for - specific machines and machine variants. Kernels and kernel modules - need to be provided separately. Support for armel and i386 is under - development. - - See the Emdebian - webpage for further information. - -

- -

- Netbook support - - - Netbooks, such as the Eee PC by Asus, are now supported by - Debian. For the Eee PC, have a look at the eeepc-acpi-scripts. Also, Debian - features a new Lightweight X11 Desktop Environment, lxde, which is beneficial for - netbooks or other computers with relatively low performance. - -

- -

- Java now in Debian - - The OpenJDK Java Runtime Environment openjdk-6-jre and Development Kit - openjdk-6-jdk, needed - for executing Java GUI and Webstart programs or building such - programs, are now in Debian. The packages are built using the - IcedTea build support and patches from the IcedTea project. - Java - IcedTea - OpenJDK - -

. Added: 315 Removed: 320