Release Notes for Debian GNU/Linux 4.0 ("etch"), Intel x86


As listed on the front page of the PDF version and in the footer of the HTML version.


With some modules from GNOME 2.16.


The old address will also remain valid for the time being.


The flag filetype should already be set on most file systems, except possibly on systems installed before sarge.


Some individual packages may no longer work correctly with a 2.4 kernel; see Some applications may no longer work with a 2.4 kernel, Section 5.1.2.


This feature can be disabled by adding the parameter panic=0 to your boot parameters.


Debian's package management system normally does not allow a package to remove or replace a file owned by another package unless it has been defined to replace that package.


Running this command at the beginning of the upgrade process may give an error, for the reasons described in the next sections. In that case you will need to wait until you've done the minimal system upgrade as in Minimal system upgrade, Section 4.5.4 and upgraded your kernel as in Upgrading the kernel, Section 4.5.5 before running this command to estimate the disk space.


This command will determine whether you need libfam0 and xlibmesa-glu installed, and auto-select them for you:

     # aptitude install x11-common \
       $(dpkg-query --showformat '${Package} ${Status}\n' -W libfam0c102 xlibmesa-glu \
         | grep 'ok installed$' | sed -e's/ .*//; s/c102//')


You can have the kernel modules needed by your system loaded statically through proper configuration of /etc/modules


The rules there are automatically generated by the script /etc/udev/rules.d/z45_persistent-net-generator.rules to have persistent names for network interfaces. Delete this symlink to disable persistent device naming for NICs by udev.


For more information on lilo's boot error codes please see The Linux Bootdisk HOWTO.


Or for as long as there is not another release in that time frame. Typically only two stable releases are supported at any given time.


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

Release Notes for Debian GNU/Linux 4.0 ("etch"), Intel x86

$Id: release-notes.en.sgml,v 1.312 2007-08-16 22:24:38 jseidel Exp $

Josip Rodin, Bob Hilliard, Adam Di Carlo, Anne Bezemer, Rob Bradford, Frans Pop (current), Andreas Barth (current), Javier Fernández-Sanguino Peña (current), Steve Langasek (current)