The kernel upgrade section could be improved a bit specially related to the change in how kernels are installed by the installation system. We all like to think that everyone that has installed a kernel from woody's bf has upgrade to a package-based kernel but, based on the traffic on debian-security, I'm inclined to think people are still making that mistake. I believe it's worthwhile pointing this issue in the RN and also telling people to upgrade to non-versioned kernels so that they can track kernel updates done in the Release by the DSA. Regards Javier
Index: release-notes.en.sgml =================================================================== RCS file: /cvs/debian-doc/ddp/manuals.sgml/release-notes/en/release-notes.en.sgml,v retrieving revision 1.28 diff -u -r1.28 release-notes.en.sgml --- release-notes.en.sgml 16 May 2005 23:05:11 -0000 1.28 +++ release-notes.en.sgml 16 May 2005 23:28:07 -0000 @@ -647,6 +662,9 @@ procedures. You may wish to do so yourself, either by installing one of the <package/kernel-image-*/ packages or by compiling a customized kernel from sources.</p> +<!-- JFS: This is not strictly true, if the user was using a non-versioned + kernel (kernel-image-2.4-686) he _will_ upgrade the kernel if using + aptitude --> <![ %available-2.6 [ @@ -662,12 +680,23 @@ <!-- FJP: s/subarchitecture/subarchitecture and processor/ ??? --> <example> -apt-cache search ^kernel-image +$ apt-cache search ^kernel-image </example></p> <p>You should then use <tt/aptitude install/ to install it. Once this new kernel is installed you should reboot at the next available opportunity to get the benefit.</p> + + <p>Please notice that the installation system of &oldreleasename; + (and previous releases) did <em/not/ install the kernel as a package + in your system. This has changed in &releasename; and you can + install virtual packages to keep track of kernel changes. + These packages are named <tt/kernel-image-VERSION-ARCH/, with + <tt/VERSION/ corresponding to the kernel version number (2.4 or 2.6) + and <tt/ARCH/ corresponding to any of the supported + architectures. If you want to have security support for the + kernel integrated in package management please install any of + these kernel packages after the upgrade.</p> <p>For the more adventurous there is an easy way to compile your own custom kernel on &debian;. Install the
Attachment:
signature.asc
Description: Digital signature