[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#703753: release-notes: much text in ch4 related to udev/kernel changes in lenny-to-squeeze

tags 703753 +patch

Please find attached a patch against the release-notes trying to clear
up some of the confusing text by either rephrasing, or removal (by

Index: release-notes/en/upgrading.dbk
--- release-notes/en/upgrading.dbk	(revision 9642)
+++ release-notes/en/upgrading.dbk	(working copy)
@@ -97,6 +97,9 @@
 system will fail to start.</para></footnote> for a significant period of time.
+<!-- FIXME: elbrus 2013-03-24: do we need to mention upgrading the kernel and udev
+for wheezy? The issues expererienced at that time are gone, right? See
+xref upgrading-udev -->
 If the system being upgraded provides critical services for your users or the
 network<footnote><para>For example: DNS or DHCP services, specially when
@@ -117,10 +120,9 @@
 <section id="recovery">
 <title>Prepare for recovery</title>
-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
+Although Debian tries to ensure that your system stays bootable at all times,
+there is always a chance that you may experience problems
+rebooting your system after the upgrade.  Known potential issues are
 documented in this and the next chapters of these Release Notes.
@@ -145,8 +147,7 @@
 <!-- FIXME: The next paragraph might not be true for Lenn? -->
 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
-guaranteed to work.
+However, this is not guaranteed to work.
 If that fails, you will need an alternative way to boot your system so you can
@@ -879,9 +880,13 @@
 that this is not absolutely required, users could do a dist-upgrade
 and then reboot. This is, however, the recommended path to be on the 
 safe side -->
+<!-- FIXME (elbrus 20130324) This text was meant for the lenny to squeeze
+upgrade, reading the above mentioned bugs I would say it is not needed
+anymore and confusing in the current style (at least &oldreleasename and
+&releasename should be replaced by hardcoded lenny and squeeze. -->
 <section id="upgrading-udev">
 <title>Upgrading the kernel and udev</title>
+<para condition="fixme">
 The <systemitem role="package">udev</systemitem> version in &releasename;
 requires a kernel of version 2.6.26 or newer with the
 <literal>CONFIG_SYSFS_DEPRECATED</literal> option disabled and the
@@ -894,7 +899,7 @@
 must be taken when upgrading to avoid putting your system in an unbootable
+<para condition="fixme">
 Booting the 2.6.26 kernel from &oldreleasename; with the <systemitem
 role="package">udev</systemitem> from &releasename; may result in a failure
 to correctly assign names to network devices, and will also fail to apply
@@ -910,16 +915,18 @@
 <!-- FIXME: Review if we have to upgrade the kernel *and* udev
 at the same time here -->
-To proceed with this kernel upgrade, run:
+To proceed with the kernel upgrade, run:
-# apt-get install linux-image-2.6-<replaceable>flavor</replaceable>
+# apt-get install linux-image-<replaceable>flavor</replaceable>
 See <xref linkend="kernel-metapackage"/> for help in determining which flavor
 of kernel package you should install.
+<!-- elbrus 2013-03-24: The move of the firmware out of the kernel was done
+in squeeze -->
+<para condition="fixme">
 The move of some firmware to separate packages in the non-free archive means
 that it may be necessary to install additional firmware packages after
 upgrading to the new kernel to support some hardware. Some hardware that was
@@ -941,7 +948,7 @@
 Immediately after upgrading the kernel, you should also install
 the new <systemitem role="package">udev</systemitem> to minimize the risk of
 other incompatibilities caused by using the old udev with a new kernel
-<footnote><para>There are also known incompatibilities between the old kernel
+<footnote condition="fixme"><para>There are also known incompatibilities between the old kernel
 and the new <systemitem role="package">udev</systemitem>. If you find
 issues after the reboot with the new kernel you will have to downgrade the 
 <systemitem role="package">udev</systemitem> in order 
@@ -1092,6 +1099,10 @@
 <!-- TODO (jfs): Review the message, it has changed in apt-get to
 "Dynamic MMap ran out of room. Please increase the size of APT::Cache-Limit. "
 "Current value: %lu. (man 5 apt.conf)" -->
+<!-- elbrus 2013-03-24:
+ * should the comment not be in /etc/apt/apt.conf.d/<some file>
+ * is 12500000 really enough?
 E: Dynamic MMap ran out of room
@@ -1305,32 +1316,32 @@
 <section id="kernel-metapackage">
 <title>Installing the kernel metapackage</title>
-When you dist-upgrade from &oldreleasename; to &releasename;, it is strongly recommended that you
-install a new linux-image-2.6-* metapackage.  This package may be installed
-automatically by the dist-upgrade process.  You can verify this by running:
+When you dist-upgrade from &oldreleasename; to &releasename;, it is strongly
+recommended that you install a linux-image-* metapackage, if you haven't done
+so before.  This package may be installed automatically by the dist-upgrade
+process.  You can verify this by running:
 # dpkg -l "linux-image*" | grep ^ii
 If you do not see any output, then you will need to install a new linux-image
-package by hand.  To see a list of available linux-image-2.6 metapackages, run:
+package by hand.  To see a list of available linux-image metapackages, run:
-# apt-cache search linux-image-2.6- | grep -v transition
+# apt-cache search linux-image- | grep -v transition
-<!-- FIXME: Review the Example for Squeeze -->
 If you are unsure about which package to select, run <literal>uname
 -r</literal> and look for a package with a similar name.  For example, if you
-see '<literal>2.6.26-2-686</literal>', it is recommended that you install
-<systemitem role="package">linux-image-2.6-686</systemitem>.  You may also
+see '<literal>2.6.32-5-686</literal>', it is recommended that you install
+<systemitem role="package">linux-image-686</systemitem>.  You may also
 use <command>apt-cache</command> 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
+# apt-cache show linux-image-686
 You should then use <literal>apt-get install</literal> to install it.  Once
@@ -1343,7 +1354,7 @@
 role="package">kernel-package</systemitem> tool and read the documentation in
 <filename>/usr/share/doc/kernel-package</filename>. Alternatively,
 you can also use the kernel sources, provided in the <systemitem
-role="package">linux-source-2.6</systemitem> package. You can make use of the
+role="package">linux-source</systemitem> package.  You can make use of the
 <literal>deb-pkg</literal> 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.
@@ -1358,7 +1369,8 @@
 <!-- FIXME: REVIEW for Squeeze this was written for Lenny - drop? (jfs) -->
-<section id="device-reorder">
+<!-- elbrus 2013-03-24: This should be really fixed by now, no? -->
+<section id="device-reorder" condition="fixme">
 <title>Device enumeration reordering</title>
 In &oldreleasename; and later, a new kernel mechanism for hardware discovery

Attachment: signature.asc
Description: OpenPGP digital signature

Reply to: