Control: tags -1 pending
On Wed, 19 Jun 2013 04:08:38 +0300 Prekates Alexandros
apreka...@gmail.com wrote:
Package: release-notes
Severity: normal
Tags: d-i
In the 4.6 it says:
..
..
4.6.1. Installing the kernel metapackage
When you dist-upgrade from squeeze to wheezy, 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:
..
.
The ambiguity is that it leaves unclear whether the dist-upgrade will install
or not the kernel metapackage.
If i 'read' it another way maybe the intention of the author was: The dist-
upgrade process can install automatically the new kernel but in order to do
that you should
have in your current stable version installed the kernel metapackage
[...]
Hi,
Thanks for the report, I have rewritten parts of that section to
hopefully clarify the intention.
The change has been committed and will appear on [1] later to day. The
site is updated 4-6 times a day, so it may take a couple of hours from
this mail.
I have also attached the actual changes, which you can also review
immediately if you prefer.
Thanks,
~Niels
[1] https://www.debian.org/releases/jessie/releasenotes
From 56b8ea179c6b16a57d4dfa60bff41938c3a2ce61 Mon Sep 17 00:00:00 2001
From: nthykier nthykier@313b444b-1b9f-4f58-a734-7bb04f332e8d
Date: Tue, 17 Mar 2015 07:18:24 +
Subject: [PATCH] upgrading: Rewrite the kernel metapackage section #712737
Signed-off-by: Niels Thykier ni...@thykier.net
git-svn-id: svn+ssh://svn.debian.org/svn/ddp/manuals/trunk/release-notes@10660 313b444b-1b9f-4f58-a734-7bb04f332e8d
---
en/upgrading.dbk | 28
1 file changed, 16 insertions(+), 12 deletions(-)
diff --git a/en/upgrading.dbk b/en/upgrading.dbk
index d83d2c7..c175c88 100644
--- a/en/upgrading.dbk
+++ b/en/upgrading.dbk
@@ -1187,22 +1187,24 @@ does not require an initrd or if you use a different initrd generator, some of
the information may not be relevant for you.
/para
section id=kernel-metapackage
-titleInstalling the kernel metapackage/title
+titleInstalling a kernel metapackage/title
para
-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:
+When you dist-upgrade from oldreleasename; to releasename;, it is
+strongly recommended that you install a linux-image-* metapackage, if
+you have not done so before. These metapackages will automatically
+pull in a newer version of the kernel during upgrades. You can verify
+whether you have one installed by running:
/para
screen
-# dpkg -l linux-image* | grep ^ii
+# dpkg -l linux-image* | grep ^ii | grep -i meta
/screen
para
-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 metapackages, run:
+If you do not see any output, then you will either need to install a
+new linux-image package by hand or install a linux-image metapackage.
+To see a list of available linux-image metapackages, run:
/para
screen
-# apt-cache search linux-image- | grep -v transition
+ # apt-cache search linux-image- | grep -i meta | grep -v transition
/screen
para
@@ -1219,9 +1221,11 @@ available. For example:
# apt-cache show linux-image-amd64
/screen
para
-You should then use literalapt-get install/literal 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.
+You should then use literalapt-get install/literal 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. However, please have a look at xref linkend=nownownow /
+before performing the first reboot after the upgrade.
/para
para
For the more adventurous there is an easy way to compile your own custom
--
2.1.4
