Re: Questions after doing update and upgrade on Stretch
On 27-05-17, Dejan Jocic wrote: > On 26-05-17, Fungi4All wrote: > > From: jode...@gmail.com > > As for reason why old one is not removed, it is because Debian keeps not > > just newly installed kernel, but also one previously installed. One > > before that was removed by apt-get autoremove. > > > > Unless different desktops have different autoremove behavior in my recent > > experience kernels can only be removed manually. If you get a current > > today's image of 8.8 and update/upgrade, then switch to testing and upd/upg, > > then unstable and upd/upg and autoremove as many times as you like, > > you will end up with 3 kernels as a choice to boot unstable from. > > I think in the past it did not work this way. > > Please, do not replay to me and cc it to the list, you mess things up. > No need to cc me either, I'm subscribed to the list. Thank you in > advance for that. > > As for subject itself, no, it is not desktop related. For your specific > case of upgrading from stable to unstable via testing, have no idea, > never did it that way. Just to clarify it a bit, what happens with your old kernel packages should be set with: /etc/kernel/postinst.d/apt-auto-removal which generates file: /etc/apt/apt.conf.d/01autoremove-kernels
Re: Questions after doing update and upgrade on Stretch
On 26-05-17, Fungi4All wrote: > From: jode...@gmail.com > As for reason why old one is not removed, it is because Debian keeps not > just newly installed kernel, but also one previously installed. One > before that was removed by apt-get autoremove. > > Unless different desktops have different autoremove behavior in my recent > experience kernels can only be removed manually. If you get a current > today's image of 8.8 and update/upgrade, then switch to testing and upd/upg, > then unstable and upd/upg and autoremove as many times as you like, > you will end up with 3 kernels as a choice to boot unstable from. > I think in the past it did not work this way. Please, do not replay to me and cc it to the list, you mess things up. No need to cc me either, I'm subscribed to the list. Thank you in advance for that. As for subject itself, no, it is not desktop related. For your specific case of upgrading from stable to unstable via testing, have no idea, never did it that way.
Re: Questions after doing update and upgrade on Stretch
From: jode...@gmail.com As for reason why old one is not removed, it is because Debian keeps not just newly installed kernel, but also one previously installed. One before that was removed by apt-get autoremove. Unless different desktops have different autoremove behavior in my recent experience kernels can only be removed manually. If you get a current today's image of 8.8 and update/upgrade, then switch to testing and upd/upg, then unstable and upd/upg and autoremove as many times as you like, you will end up with 3 kernels as a choice to boot unstable from. I think in the past it did not work this way.
Re: Questions after doing update and upgrade on Stretch
On 26-05-17, David Wright wrote: > On Mon 22 May 2017 at 11:12:02 (+0200), Dejan Jocic wrote: > > On 21-05-17, Brian wrote: > > > On Sun 21 May 2017 at 22:18:11 +0200, Dejan Jocic wrote: > > > > > > > On 21-05-17, David Wright wrote: > > > > > On Sun 21 May 2017 at 16:31:55 (+0200), Dejan Jocic wrote: > > > > > > > > > > > > > As for number 1 can't say much about it, I do not get it either. > > > > > > But 2 > > > > > > happens because you've used apt-get upgrade instead of apt-get > > > > > > dist-upgrade. Packages that will uninstall some packages already > > > > > > installed on your system and that will change some dependencies > > > > > > require dist-upgrade. > > > > > > > > > > Agreed. > > > > > > > > > > > It happens always in case of linux-image packages. > > > > > > > > > > Is this¹ new with stretch? My linux-images upgrade just like any other > > > > > package; here's the penultimate occasion for jessie: > > > > > > > > > > Start-Date: 2017-03-08 19:20:34 > > > > > Commandline: apt-get upgrade > > > > > Upgrade: linux-source-3.16:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > > > > > linux-headers-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > > > > > linux-image-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > > > > > linux-libc-dev:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > > > > > linux-compiler-gcc-4.8-x86:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > > > > > linux-headers-3.16.0-4-common:i386 (3.16.39-1+deb8u1, > > > > > 3.16.39-1+deb8u2) > > > > > End-Date: 2017-03-08 19:22:50 > > > > > > > > > > (The last one's log was rather larger.) > > > > > > > > Ehh, sorry not sure if it is new with Stretch, can't remember for > > > > Jessie. I'm certain that it was like that on Stretch and on Ubuntu > > > > 16.04. > > > > > > Rather than just a contrast, I was rather hoping to hear how David > > > Wright's observations (which I agree with)fit in with yours. > > > > > Sorry, not sure what I can add to it. > > > > > > > > It will leave your previous working linux-image on though, but will > > > > > > uninstall one older than that, so you will always end up with > > > > > > chance to > > > > > > boot in working kernel, if new one messes up some things. > > > > > > > > > > Same question. My wheezy system has had at least 28 linux-image > > > > > upgrades (3.2.57-3+deb7u2→3.2.60-1+deb7u1 to 3.2.86-1→3.2.88-1) > > > > > but there's still only one kernel image on the system: > > > > > > > > > > -rw-r--r-- 1 root root 134839 Apr 27 16:52 config-3.2.0-4-686-pae > > > > > drwxr-xr-x 3 root root 12288 Apr 28 07:44 grub > > > > > -rw-r--r-- 1 root root 2672854 Apr 28 07:44 initrd.img-3.2.0-4-686-pae > > > > > -rw-r--r-- 1 root root 1674268 Apr 27 16:52 System.map-3.2.0-4-686-pae > > > > > -rw-r--r-- 1 root root 2709184 Apr 27 16:51 vmlinuz-3.2.0-4-686-pae > > > > > > > > > > (I have to notice these upgrades myself because they overwrite > > > > > my edited version of /boot/grub/grub.cfg which I then replace.) > > > > > > > > > > Cheers, > > > > > David. > > > > > > > > > > ¹ I'm not disagreeing that something is holding back the upgrade > > > > > on this specific occasion, but this is unusual. > > > > > > This is what I have in /boot and, as stated above, usual outcome of > > upgrades, both in Stretch and in Ubuntu 16.04: > > > > -rw-r--r-- 1 root root 186695 Mar 30 03:16 config-4.9.0-2-amd64 > > -rw-r--r-- 1 root root 186380 May 2 17:21 config-4.9.0-3-amd64 > > drwxr-xr-x 5 root root 4096 May 19 08:55 grub > > -rw-r--r-- 1 root root 19660713 May 17 16:43 initrd.img-4.9.0-2-amd64 > > -rw-r--r-- 1 root root 19534447 May 18 08:40 initrd.img-4.9.0-3-amd64 > > -rw-r--r-- 1 root root 3169870 Mar 30 03:16 System.map-4.9.0-2-amd64 > > -rw-r--r-- 1 root root 3176652 May 2 17:21 System.map-4.9.0-3-amd64 > > -rw-r--r-- 1 root root 4193832 Mar 30 18:43 vmlinuz-4.9.0-2-amd64 > > -rw-r--r-- 1 root root 4204320 May 2 17:21 vmlinuz-4.9.0-3-amd64 > > > > As you can see, 2 kernels. All i do is my morning routine which consists > > of apt-get update && apt-get upgrade, followed by apt-get dist-upgrade > > in case of need(as stated before, usually case of need is kernel > > upgrade). Of course, it is followed by apt-get autoremove too.I do not > > have anything unusual on this system. It was fairly recent install of > > jessie(few months ago), followed by upgrade to stretch right after > > install. Was installed from unofficial net-install cd with firmware on > > it. Also, nothing was changed in apt preferences and stuff like that. > > OK, I've just been looking at kernel changelogs and that explains > what's going on here. There's nothing different about kernels in > particular, and the reason you've got two kernels is that they > are different kernels, so different Debian packages. > > I installed wheezy no earlier than May 2013 (ie not as a release > candidate) and 3.2.0-4 came out in Sept 2012, so as I said > I've had at least 28 upgrades of the one
Re: Questions after doing update and upgrade on Stretch
On Mon 22 May 2017 at 11:12:02 (+0200), Dejan Jocic wrote: > On 21-05-17, Brian wrote: > > On Sun 21 May 2017 at 22:18:11 +0200, Dejan Jocic wrote: > > > > > On 21-05-17, David Wright wrote: > > > > On Sun 21 May 2017 at 16:31:55 (+0200), Dejan Jocic wrote: > > > > > > > > > > > As for number 1 can't say much about it, I do not get it either. But 2 > > > > > happens because you've used apt-get upgrade instead of apt-get > > > > > dist-upgrade. Packages that will uninstall some packages already > > > > > installed on your system and that will change some dependencies > > > > > require dist-upgrade. > > > > > > > > Agreed. > > > > > > > > > It happens always in case of linux-image packages. > > > > > > > > Is this¹ new with stretch? My linux-images upgrade just like any other > > > > package; here's the penultimate occasion for jessie: > > > > > > > > Start-Date: 2017-03-08 19:20:34 > > > > Commandline: apt-get upgrade > > > > Upgrade: linux-source-3.16:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > > > > linux-headers-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > > > > linux-image-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > > > > linux-libc-dev:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > > > > linux-compiler-gcc-4.8-x86:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > > > > linux-headers-3.16.0-4-common:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2) > > > > End-Date: 2017-03-08 19:22:50 > > > > > > > > (The last one's log was rather larger.) > > > > > > Ehh, sorry not sure if it is new with Stretch, can't remember for > > > Jessie. I'm certain that it was like that on Stretch and on Ubuntu > > > 16.04. > > > > Rather than just a contrast, I was rather hoping to hear how David > > Wright's observations (which I agree with)fit in with yours. > > > Sorry, not sure what I can add to it. > > > > > > It will leave your previous working linux-image on though, but will > > > > > uninstall one older than that, so you will always end up with chance > > > > > to > > > > > boot in working kernel, if new one messes up some things. > > > > > > > > Same question. My wheezy system has had at least 28 linux-image > > > > upgrades (3.2.57-3+deb7u2→3.2.60-1+deb7u1 to 3.2.86-1→3.2.88-1) > > > > but there's still only one kernel image on the system: > > > > > > > > -rw-r--r-- 1 root root 134839 Apr 27 16:52 config-3.2.0-4-686-pae > > > > drwxr-xr-x 3 root root 12288 Apr 28 07:44 grub > > > > -rw-r--r-- 1 root root 2672854 Apr 28 07:44 initrd.img-3.2.0-4-686-pae > > > > -rw-r--r-- 1 root root 1674268 Apr 27 16:52 System.map-3.2.0-4-686-pae > > > > -rw-r--r-- 1 root root 2709184 Apr 27 16:51 vmlinuz-3.2.0-4-686-pae > > > > > > > > (I have to notice these upgrades myself because they overwrite > > > > my edited version of /boot/grub/grub.cfg which I then replace.) > > > > > > > > Cheers, > > > > David. > > > > > > > > ¹ I'm not disagreeing that something is holding back the upgrade > > > > on this specific occasion, but this is unusual. > > > This is what I have in /boot and, as stated above, usual outcome of > upgrades, both in Stretch and in Ubuntu 16.04: > > -rw-r--r-- 1 root root 186695 Mar 30 03:16 config-4.9.0-2-amd64 > -rw-r--r-- 1 root root 186380 May 2 17:21 config-4.9.0-3-amd64 > drwxr-xr-x 5 root root 4096 May 19 08:55 grub > -rw-r--r-- 1 root root 19660713 May 17 16:43 initrd.img-4.9.0-2-amd64 > -rw-r--r-- 1 root root 19534447 May 18 08:40 initrd.img-4.9.0-3-amd64 > -rw-r--r-- 1 root root 3169870 Mar 30 03:16 System.map-4.9.0-2-amd64 > -rw-r--r-- 1 root root 3176652 May 2 17:21 System.map-4.9.0-3-amd64 > -rw-r--r-- 1 root root 4193832 Mar 30 18:43 vmlinuz-4.9.0-2-amd64 > -rw-r--r-- 1 root root 4204320 May 2 17:21 vmlinuz-4.9.0-3-amd64 > > As you can see, 2 kernels. All i do is my morning routine which consists > of apt-get update && apt-get upgrade, followed by apt-get dist-upgrade > in case of need(as stated before, usually case of need is kernel > upgrade). Of course, it is followed by apt-get autoremove too.I do not > have anything unusual on this system. It was fairly recent install of > jessie(few months ago), followed by upgrade to stretch right after > install. Was installed from unofficial net-install cd with firmware on > it. Also, nothing was changed in apt preferences and stuff like that. OK, I've just been looking at kernel changelogs and that explains what's going on here. There's nothing different about kernels in particular, and the reason you've got two kernels is that they are different kernels, so different Debian packages. I installed wheezy no earlier than May 2013 (ie not as a release candidate) and 3.2.0-4 came out in Sept 2012, so as I said I've had at least 28 upgrades of the one kernel version. OTOH the only stretch system I have is currently a basic system, with just 248 packages (minimal install from RC3). The kernel version is linux-image-4.9.0-2 at Debian version 4.9.18-1 and that version is obsolete. Currently we seem
Re: Questions after doing update and upgrade on Stretch
On Sun, 21 May 2017 09:35:55 -0500, you wrote: >> Check with blkid that sda5 has this UUID. > >Gparted reports that UUID for /dev/sda5 'lsblk --fs' provides a human-friendly "graphical" tree view that includes UUID and LABEL of each partition on each disk.
Re: Questions after doing update and upgrade on Stretch
On Mon 22 May 2017 at 05:31:26 -0500, Richard Owlett wrote: > On 05/21/2017 09:31 AM, Dejan Jocic wrote: > >> > >As for number 1 can't say much about it, I do not get it either. But 2 > >happens because you've used apt-get upgrade instead of apt-get > >dist-upgrade. Packages that will uninstall some packages already > >installed on your system and that will change some dependencies > >require dist-upgrade. It happens always in case of linux-image packages. > >It will leave your previous working linux-image on though, but will > >uninstall one older than that, so you will always end up with chance > >to boot in working kernel, if new one messes up some things. > > > > If I had problems after doing apt-get dist-upgrade, > 1. how would I distinguish a kernel problem from other problems? Far too general a question. Better would be a description of the actual problem. > 2. how would I boot with the previous kernel? Replace the kernel version in the linux and initrd lines within the GRUB menu. For permanency, use /etc/grub.d/40_custom. > 3. is there some specific documentation I should be reading? On what? In general, at this stage of the freeze, dist-upgrade shouldn't give any problem. -- Brian
Re: Questions after doing update and upgrade on Stretch
On 22-05-17, Richard Owlett wrote: > On 05/21/2017 09:31 AM, Dejan Jocic wrote: > > On 21-05-17, Richard Owlett wrote: > > > [snip] > > > > > > My questions: > > > > > > 1. In the first run, I don't understand: > > > Processing triggers for initramfs-tools (0.130) ... > > > update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae > > > I: The initramfs will attempt to resume from /dev/sda5 > > > I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576) > > > I: Set the RESUME variable to override this. > > > As /dev/sda5 is my SWAP. > > > > > > 2. I don't understand any implications of: > > > The following packages have been kept back: > > >linux-image-686-pae xorg xserver-xorg > > > > > > TIA > > > > > > > > > > > > > > As for number 1 can't say much about it, I do not get it either. But 2 > > happens because you've used apt-get upgrade instead of apt-get > > dist-upgrade. Packages that will uninstall some packages already > > installed on your system and that will change some dependencies > > require dist-upgrade. It happens always in case of linux-image packages. > > It will leave your previous working linux-image on though, but will > > uninstall one older than that, so you will always end up with chance > > to boot in working kernel, if new one messes up some things. > > > > If I had problems after doing apt-get dist-upgrade, > 1. how would I distinguish a kernel problem from other problems? > 2. how would I boot with the previous kernel? > 3. is there some specific documentation I should be reading? > > I've done online upgrades before having relied on purchased DVD sets of > point releases due to bandwidth constraints. > > Thank you. > > 1. That would depend on problem itself, right? As for kernel problems, I was unusually lucky with them for years and have yet to run on problem with upgraded kernel. Must be that new kernels really loved my hardware. 2. It is easy task, as long as there is previous kernel present in your /boot. If everything works as expected you should have it. From debian administrator handbook: 8.11.1. Features of a Debian Kernel Package A Debian kernel package installs the kernel image (vmlinuz-version), its configuration (config-version) and its symbols table (System.map-version) in /boot/. The symbols table helps developers understand the meaning of a kernel error message; without it, kernel “oopses” (an “oops” is the kernel equivalent of a segmentation fault for user-space programs, in other words messages generated following an invalid pointer dereference) only contain numeric memory addresses, which is useless information without the table mapping these addresses to symbols and function names. The modules are installed in the /lib/modules/version/ directory. The package's configuration scripts automatically generate an initrd image, which is a mini-system designed to be loaded in memory (hence the name, which stands for “init ramdisk”) by the bootloader, and used by the Linux kernel solely for loading the modules needed to access the devices containing the complete Debian system (for example, the driver for SATA disks). Finally, the post-installation scripts update the symbolic links /vmlinuz, /vmlinuz.old, /initrd.img and /initrd.img.old so that they point to the latest two kernels installed, respectively, as well as the corresponding initrd images. Most of those tasks are offloaded to hook scripts in the /etc/kernel/*.d/ directories. For instance, the integration with grub relies on /etc/kernel/postinst.d/zz-update-grub and /etc/kernel/postrm.d/zz-update-grub to call update-grub when kernels are installed or removed. As you can see there, if everything works as intended, you will still have your old kernel installed, which you can choose from grub menu. Think that it is under advanced options, but did not use it recently and am not in mood to reboot now to check. Anyway, as long as you do not use apt-get autoremove, even your older than previous kernel packages should be around, though I did not have need for that. 3. https://debian-handbook.info/ and usual man pages for grub, kernel, apt-get and friends, I guess. Pleasure :)
Re: Questions after doing update and upgrade on Stretch
On 05/21/2017 09:31 AM, Dejan Jocic wrote: On 21-05-17, Richard Owlett wrote: [snip] My questions: 1. In the first run, I don't understand: Processing triggers for initramfs-tools (0.130) ... update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae I: The initramfs will attempt to resume from /dev/sda5 I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576) I: Set the RESUME variable to override this. As /dev/sda5 is my SWAP. 2. I don't understand any implications of: The following packages have been kept back: linux-image-686-pae xorg xserver-xorg TIA As for number 1 can't say much about it, I do not get it either. But 2 happens because you've used apt-get upgrade instead of apt-get dist-upgrade. Packages that will uninstall some packages already installed on your system and that will change some dependencies require dist-upgrade. It happens always in case of linux-image packages. It will leave your previous working linux-image on though, but will uninstall one older than that, so you will always end up with chance to boot in working kernel, if new one messes up some things. If I had problems after doing apt-get dist-upgrade, 1. how would I distinguish a kernel problem from other problems? 2. how would I boot with the previous kernel? 3. is there some specific documentation I should be reading? I've done online upgrades before having relied on purchased DVD sets of point releases due to bandwidth constraints. Thank you.
Re: Questions after doing update and upgrade on Stretch
On Mon 22 May 2017 at 11:12:02 +0200, Dejan Jocic wrote: > On 21-05-17, Brian wrote: > > On Sun 21 May 2017 at 22:18:11 +0200, Dejan Jocic wrote: > > > > > Sorry, but you are doing it wrong way. Grub 2 should not be customized > > > by editing /boot/grub/grub.cfg , but by editing /etc/default/grub and > > > files in /etc/grub.d/. Reason is obvious, your customization is lost > > > whenever something related to linux-image is upgraded. Just saying :) > > > > "Wrong" isn't quite the right way to put. For most people in most > > circumstances editing grub.cfg and using update-grub is a wise procedure > > and to be advocated. But a hand-crafted grub.cfg can be very useful. > > update-grub can be prevented from getting its hands on it with > > dpkg-divert, > > > > -- > > Brian. > > > > Well, I was always under assumption that in case of grub2 you can change > anything in grub.cfg by editing /etc/default/grub and files in > /etc/grub.d/. Perhaps I was wrong about it, in which case I do > apologise. No need to apologise. Your assumption is correct and your advice sound; 100% of Debian users should thank you for it. The 0.1% who wander from the straight and narrow presumably know what they are doing. -- Brian.
Re: Questions after doing update and upgrade on Stretch
On 21-05-17, Brian wrote: > On Sun 21 May 2017 at 22:18:11 +0200, Dejan Jocic wrote: > > > On 21-05-17, David Wright wrote: > > > On Sun 21 May 2017 at 16:31:55 (+0200), Dejan Jocic wrote: > > > > > > > > > As for number 1 can't say much about it, I do not get it either. But 2 > > > > happens because you've used apt-get upgrade instead of apt-get > > > > dist-upgrade. Packages that will uninstall some packages already > > > > installed on your system and that will change some dependencies > > > > require dist-upgrade. > > > > > > Agreed. > > > > > > > It happens always in case of linux-image packages. > > > > > > Is this¹ new with stretch? My linux-images upgrade just like any other > > > package; here's the penultimate occasion for jessie: > > > > > > Start-Date: 2017-03-08 19:20:34 > > > Commandline: apt-get upgrade > > > Upgrade: linux-source-3.16:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > > > linux-headers-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > > > linux-image-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > > > linux-libc-dev:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > > > linux-compiler-gcc-4.8-x86:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > > > linux-headers-3.16.0-4-common:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2) > > > End-Date: 2017-03-08 19:22:50 > > > > > > (The last one's log was rather larger.) > > > > Ehh, sorry not sure if it is new with Stretch, can't remember for > > Jessie. I'm certain that it was like that on Stretch and on Ubuntu > > 16.04. > > Rather than just a contrast, I was rather hoping to hear how David > Wright's observations (which I agree with)fit in with yours. > Sorry, not sure what I can add to it. > > > > It will leave your previous working linux-image on though, but will > > > > uninstall one older than that, so you will always end up with chance to > > > > boot in working kernel, if new one messes up some things. > > > > > > Same question. My wheezy system has had at least 28 linux-image > > > upgrades (3.2.57-3+deb7u2→3.2.60-1+deb7u1 to 3.2.86-1→3.2.88-1) > > > but there's still only one kernel image on the system: > > > > > > -rw-r--r-- 1 root root 134839 Apr 27 16:52 config-3.2.0-4-686-pae > > > drwxr-xr-x 3 root root 12288 Apr 28 07:44 grub > > > -rw-r--r-- 1 root root 2672854 Apr 28 07:44 initrd.img-3.2.0-4-686-pae > > > -rw-r--r-- 1 root root 1674268 Apr 27 16:52 System.map-3.2.0-4-686-pae > > > -rw-r--r-- 1 root root 2709184 Apr 27 16:51 vmlinuz-3.2.0-4-686-pae > > > > > > (I have to notice these upgrades myself because they overwrite > > > my edited version of /boot/grub/grub.cfg which I then replace.) > > > > > > Cheers, > > > David. > > > > > > ¹ I'm not disagreeing that something is holding back the upgrade > > > on this specific occasion, but this is unusual. This is what I have in /boot and, as stated above, usual outcome of upgrades, both in Stretch and in Ubuntu 16.04: -rw-r--r-- 1 root root 186695 Mar 30 03:16 config-4.9.0-2-amd64 -rw-r--r-- 1 root root 186380 May 2 17:21 config-4.9.0-3-amd64 drwxr-xr-x 5 root root 4096 May 19 08:55 grub -rw-r--r-- 1 root root 19660713 May 17 16:43 initrd.img-4.9.0-2-amd64 -rw-r--r-- 1 root root 19534447 May 18 08:40 initrd.img-4.9.0-3-amd64 -rw-r--r-- 1 root root 3169870 Mar 30 03:16 System.map-4.9.0-2-amd64 -rw-r--r-- 1 root root 3176652 May 2 17:21 System.map-4.9.0-3-amd64 -rw-r--r-- 1 root root 4193832 Mar 30 18:43 vmlinuz-4.9.0-2-amd64 -rw-r--r-- 1 root root 4204320 May 2 17:21 vmlinuz-4.9.0-3-amd64 As you can see, 2 kernels. All i do is my morning routine which consists of apt-get update && apt-get upgrade, followed by apt-get dist-upgrade in case of need(as stated before, usually case of need is kernel upgrade). Of course, it is followed by apt-get autoremove too.I do not have anything unusual on this system. It was fairly recent install of jessie(few months ago), followed by upgrade to stretch right after install. Was installed from unofficial net-install cd with firmware on it. Also, nothing was changed in apt preferences and stuff like that. > > > > Sorry, but you are doing it wrong way. Grub 2 should not be customized > > by editing /boot/grub/grub.cfg , but by editing /etc/default/grub and > > files in /etc/grub.d/. Reason is obvious, your customization is lost > > whenever something related to linux-image is upgraded. Just saying :) > > "Wrong" isn't quite the right way to put. For most people in most > circumstances editing grub.cfg and using update-grub is a wise procedure > and to be advocated. But a hand-crafted grub.cfg can be very useful. > update-grub can be prevented from getting its hands on it with > dpkg-divert, > > -- > Brian. > Well, I was always under assumption that in case of grub2 you can change anything in grub.cfg by editing /etc/default/grub and files in /etc/grub.d/. Perhaps I was wrong about it, in which case I do apologise.
Re: Questions after doing update and upgrade on Stretch
On Sun 21 May 2017 at 22:18:11 (+0200), Dejan Jocic wrote:
> On 21-05-17, David Wright wrote:
> > -rw-r--r-- 1 root root 134839 Apr 27 16:52 config-3.2.0-4-686-pae
> > drwxr-xr-x 3 root root 12288 Apr 28 07:44 grub
> > -rw-r--r-- 1 root root 2672854 Apr 28 07:44 initrd.img-3.2.0-4-686-pae
> > -rw-r--r-- 1 root root 1674268 Apr 27 16:52 System.map-3.2.0-4-686-pae
> > -rw-r--r-- 1 root root 2709184 Apr 27 16:51 vmlinuz-3.2.0-4-686-pae
> >
> > (I have to notice these upgrades myself because they overwrite
> > my edited version of /boot/grub/grub.cfg which I then replace.)
> >
>
> Sorry, but you are doing it wrong way. Grub 2 should not be customized
> by editing /boot/grub/grub.cfg , but by editing /etc/default/grub and
> files in /etc/grub.d/. Reason is obvious, your customization is lost
> whenever something related to linux-image is upgraded. Just saying :)
Yes, it would be nice to use the Debian Way. But there is not enough
flexibility in their scripts to do what I want.
a) the logic of
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to
Linux
#GRUB_DISABLE_LINUX_UUID=true
is odd and, unfortunately, there's no facility for
GRUB_ENABLE_LINUX_LABEL=true
(I did have a shot at modifying the scripts, but it's less trivial
than it would seem at first sight).
b) they insert entries for sysvinit and recovery but not for fsck.
I modify the first subentry, using the ids fsck and fsck so I can use
grub-reboot 'fsck>fsck'
to invoke it from a script that also logs a timestamp. I refuse to
type monstrosities like
grub-reboot 'Advanced options for Debian
GNU/Linux>gnulinux-advanced-7ccc1c1c-a690-418b-96c0-edcce6ebd3c1'
So it's far easier to write one python script to parse /run/udev/data,
automatically make the changes I want, and keep the original and
edited files as /boot/grub/grub.cfg-{uuids,edited}. After any upgrade,
if the former matches /boot/grub/grub.cfg, it gets overwritten by the
latter.
Cheers,
David.
Re: Questions after doing update and upgrade on Stretch
On Sun 21 May 2017 at 22:18:11 +0200, Dejan Jocic wrote: > On 21-05-17, David Wright wrote: > > On Sun 21 May 2017 at 16:31:55 (+0200), Dejan Jocic wrote: > > > > > > > As for number 1 can't say much about it, I do not get it either. But 2 > > > happens because you've used apt-get upgrade instead of apt-get > > > dist-upgrade. Packages that will uninstall some packages already > > > installed on your system and that will change some dependencies > > > require dist-upgrade. > > > > Agreed. > > > > > It happens always in case of linux-image packages. > > > > Is this¹ new with stretch? My linux-images upgrade just like any other > > package; here's the penultimate occasion for jessie: > > > > Start-Date: 2017-03-08 19:20:34 > > Commandline: apt-get upgrade > > Upgrade: linux-source-3.16:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > > linux-headers-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > > linux-image-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > > linux-libc-dev:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > > linux-compiler-gcc-4.8-x86:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > > linux-headers-3.16.0-4-common:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2) > > End-Date: 2017-03-08 19:22:50 > > > > (The last one's log was rather larger.) > > Ehh, sorry not sure if it is new with Stretch, can't remember for > Jessie. I'm certain that it was like that on Stretch and on Ubuntu > 16.04. Rather than just a contrast, I was rather hoping to hear how David Wright's observations (which I agree with)fit in with yours. > > > It will leave your previous working linux-image on though, but will > > > uninstall one older than that, so you will always end up with chance to > > > boot in working kernel, if new one messes up some things. > > > > Same question. My wheezy system has had at least 28 linux-image > > upgrades (3.2.57-3+deb7u2→3.2.60-1+deb7u1 to 3.2.86-1→3.2.88-1) > > but there's still only one kernel image on the system: > > > > -rw-r--r-- 1 root root 134839 Apr 27 16:52 config-3.2.0-4-686-pae > > drwxr-xr-x 3 root root 12288 Apr 28 07:44 grub > > -rw-r--r-- 1 root root 2672854 Apr 28 07:44 initrd.img-3.2.0-4-686-pae > > -rw-r--r-- 1 root root 1674268 Apr 27 16:52 System.map-3.2.0-4-686-pae > > -rw-r--r-- 1 root root 2709184 Apr 27 16:51 vmlinuz-3.2.0-4-686-pae > > > > (I have to notice these upgrades myself because they overwrite > > my edited version of /boot/grub/grub.cfg which I then replace.) > > > > Cheers, > > David. > > > > ¹ I'm not disagreeing that something is holding back the upgrade > > on this specific occasion, but this is unusual. > > Sorry, but you are doing it wrong way. Grub 2 should not be customized > by editing /boot/grub/grub.cfg , but by editing /etc/default/grub and > files in /etc/grub.d/. Reason is obvious, your customization is lost > whenever something related to linux-image is upgraded. Just saying :) "Wrong" isn't quite the right way to put. For most people in most circumstances editing grub.cfg and using update-grub is a wise procedure and to be advocated. But a hand-crafted grub.cfg can be very useful. update-grub can be prevented from getting its hands on it with dpkg-divert, -- Brian.
Re: Questions after doing update and upgrade on Stretch
On 21-05-17, David Wright wrote: > On Sun 21 May 2017 at 16:31:55 (+0200), Dejan Jocic wrote: > > On 21-05-17, Richard Owlett wrote: > > > I had done: > > > apt-get update > > > apt-get upgrade > > > The tail end of the output was: > > > ... > > > Setting up libkde3support4 (4:4.14.26-2) ... > > > Setting up libktexteditor4 (4:4.14.26-2) ... > > > Setting up libkdewebkit5 (4:4.14.26-2) ... > > > Setting up libkhtml5 (4:4.14.26-2) ... > > > Setting up libplasma3 (4:4.14.26-2) ... > > > Setting up kdelibs5-plugins (4:4.14.26-2) ... > > > Processing triggers for initramfs-tools (0.130) ... > > > update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae > > > I: The initramfs will attempt to resume from /dev/sda5 > > > I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576) > > > I: Set the RESUME variable to override this. > > > Processing triggers for libc-bin (2.24-10) ... > > > root@stretch-2nd:/home/richard# > > > > > > Before asking for confirmation to do the "upgrade" it said 3 packages > > > would > > > not be upgraded. > > > If it said which packages, I didn't spot it. > > > I then reran with following result. > > > > > > root@stretch-2nd:/home/richard# apt-get upgrade > > > Reading package lists... Done > > > Building dependency tree > > > Reading state information... Done > > > Calculating upgrade... Done > > > The following packages were automatically installed and are no longer > > > required: > > > dconf-cli gir1.2-notify-0.7 libconfig9 libgtkspell3-3-0 libindicator3-7 > > > mate-indicator-applet > > > mate-indicator-applet-common python3-psutil python3-setproctitle > > > Use 'apt autoremove' to remove them. > > > The following packages have been kept back: > > > linux-image-686-pae xorg xserver-xorg > > > 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. > > > root@stretch-2nd:/home/richard# > > > > > > My questions: > > > > > > 1. In the first run, I don't understand: > > > Processing triggers for initramfs-tools (0.130) ... > > > update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae > > > I: The initramfs will attempt to resume from /dev/sda5 > > > I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576) > > > I: Set the RESUME variable to override this. > > > As /dev/sda5 is my SWAP. > > > > > > 2. I don't understand any implications of: > > > The following packages have been kept back: > > >linux-image-686-pae xorg xserver-xorg > > > > > > TIA > > > > > > > > > > > > > > As for number 1 can't say much about it, I do not get it either. But 2 > > happens because you've used apt-get upgrade instead of apt-get > > dist-upgrade. Packages that will uninstall some packages already > > installed on your system and that will change some dependencies > > require dist-upgrade. > > Agreed. > > > It happens always in case of linux-image packages. > > Is this¹ new with stretch? My linux-images upgrade just like any other > package; here's the penultimate occasion for jessie: > > Start-Date: 2017-03-08 19:20:34 > Commandline: apt-get upgrade > Upgrade: linux-source-3.16:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > linux-headers-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > linux-image-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > linux-libc-dev:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > linux-compiler-gcc-4.8-x86:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), > linux-headers-3.16.0-4-common:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2) > End-Date: 2017-03-08 19:22:50 > > (The last one's log was rather larger.) Ehh, sorry not sure if it is new with Stretch, can't remember for Jessie. I'm certain that it was like that on Stretch and on Ubuntu 16.04. > > > It will leave your previous working linux-image on though, but will > > uninstall one older than that, so you will always end up with chance to > > boot in working kernel, if new one messes up some things. > > Same question. My wheezy system has had at least 28 linux-image > upgrades (3.2.57-3+deb7u2→3.2.60-1+deb7u1 to 3.2.86-1→3.2.88-1) > but there's still only one kernel image on the system: > > -rw-r--r-- 1 root root 134839 Apr 27 16:52 config-3.2.0-4-686-pae > drwxr-xr-x 3 root root 12288 Apr 28 07:44 grub > -rw-r--r-- 1 root root 2672854 Apr 28 07:44 initrd.img-3.2.0-4-686-pae > -rw-r--r-- 1 root root 1674268 Apr 27 16:52 System.map-3.2.0-4-686-pae > -rw-r--r-- 1 root root 2709184 Apr 27 16:51 vmlinuz-3.2.0-4-686-pae > > (I have to notice these upgrades myself because they overwrite > my edited version of /boot/grub/grub.cfg which I then replace.) > > Cheers, > David. > > ¹ I'm not disagreeing that something is holding back the upgrade > on this specific occasion, but this is unusual. > Sorry, but you are doing it wrong way. Grub 2 should not be customized by editing /boot/grub/grub.cfg , but by editing /etc/default/grub and files in /etc/grub.d/. Reason is obvious, your customization is lost whenever something related to linux-image is
Re: Questions after doing update and upgrade on Stretch
On Sun 21 May 2017 at 16:31:55 (+0200), Dejan Jocic wrote: > On 21-05-17, Richard Owlett wrote: > > I had done: > > apt-get update > > apt-get upgrade > > The tail end of the output was: > > ... > > Setting up libkde3support4 (4:4.14.26-2) ... > > Setting up libktexteditor4 (4:4.14.26-2) ... > > Setting up libkdewebkit5 (4:4.14.26-2) ... > > Setting up libkhtml5 (4:4.14.26-2) ... > > Setting up libplasma3 (4:4.14.26-2) ... > > Setting up kdelibs5-plugins (4:4.14.26-2) ... > > Processing triggers for initramfs-tools (0.130) ... > > update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae > > I: The initramfs will attempt to resume from /dev/sda5 > > I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576) > > I: Set the RESUME variable to override this. > > Processing triggers for libc-bin (2.24-10) ... > > root@stretch-2nd:/home/richard# > > > > Before asking for confirmation to do the "upgrade" it said 3 packages would > > not be upgraded. > > If it said which packages, I didn't spot it. > > I then reran with following result. > > > > root@stretch-2nd:/home/richard# apt-get upgrade > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > Calculating upgrade... Done > > The following packages were automatically installed and are no longer > > required: > > dconf-cli gir1.2-notify-0.7 libconfig9 libgtkspell3-3-0 libindicator3-7 > > mate-indicator-applet > > mate-indicator-applet-common python3-psutil python3-setproctitle > > Use 'apt autoremove' to remove them. > > The following packages have been kept back: > > linux-image-686-pae xorg xserver-xorg > > 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. > > root@stretch-2nd:/home/richard# > > > > My questions: > > > > 1. In the first run, I don't understand: > > Processing triggers for initramfs-tools (0.130) ... > > update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae > > I: The initramfs will attempt to resume from /dev/sda5 > > I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576) > > I: Set the RESUME variable to override this. > > As /dev/sda5 is my SWAP. > > > > 2. I don't understand any implications of: > > The following packages have been kept back: > >linux-image-686-pae xorg xserver-xorg > > > > TIA > > > > > > > > > As for number 1 can't say much about it, I do not get it either. But 2 > happens because you've used apt-get upgrade instead of apt-get > dist-upgrade. Packages that will uninstall some packages already > installed on your system and that will change some dependencies > require dist-upgrade. Agreed. > It happens always in case of linux-image packages. Is this¹ new with stretch? My linux-images upgrade just like any other package; here's the penultimate occasion for jessie: Start-Date: 2017-03-08 19:20:34 Commandline: apt-get upgrade Upgrade: linux-source-3.16:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), linux-headers-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), linux-image-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), linux-libc-dev:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), linux-compiler-gcc-4.8-x86:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), linux-headers-3.16.0-4-common:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2) End-Date: 2017-03-08 19:22:50 (The last one's log was rather larger.) > It will leave your previous working linux-image on though, but will > uninstall one older than that, so you will always end up with chance to > boot in working kernel, if new one messes up some things. Same question. My wheezy system has had at least 28 linux-image upgrades (3.2.57-3+deb7u2→3.2.60-1+deb7u1 to 3.2.86-1→3.2.88-1) but there's still only one kernel image on the system: -rw-r--r-- 1 root root 134839 Apr 27 16:52 config-3.2.0-4-686-pae drwxr-xr-x 3 root root 12288 Apr 28 07:44 grub -rw-r--r-- 1 root root 2672854 Apr 28 07:44 initrd.img-3.2.0-4-686-pae -rw-r--r-- 1 root root 1674268 Apr 27 16:52 System.map-3.2.0-4-686-pae -rw-r--r-- 1 root root 2709184 Apr 27 16:51 vmlinuz-3.2.0-4-686-pae (I have to notice these upgrades myself because they overwrite my edited version of /boot/grub/grub.cfg which I then replace.) Cheers, David. ¹ I'm not disagreeing that something is holding back the upgrade on this specific occasion, but this is unusual.
Re: Questions after doing update and upgrade on Stretch
On 21-05-17, Richard Owlett wrote: > I had done: > apt-get update > apt-get upgrade > The tail end of the output was: > ... > Setting up libkde3support4 (4:4.14.26-2) ... > Setting up libktexteditor4 (4:4.14.26-2) ... > Setting up libkdewebkit5 (4:4.14.26-2) ... > Setting up libkhtml5 (4:4.14.26-2) ... > Setting up libplasma3 (4:4.14.26-2) ... > Setting up kdelibs5-plugins (4:4.14.26-2) ... > Processing triggers for initramfs-tools (0.130) ... > update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae > I: The initramfs will attempt to resume from /dev/sda5 > I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576) > I: Set the RESUME variable to override this. > Processing triggers for libc-bin (2.24-10) ... > root@stretch-2nd:/home/richard# > > Before asking for confirmation to do the "upgrade" it said 3 packages would > not be upgraded. > If it said which packages, I didn't spot it. > I then reran with following result. > > root@stretch-2nd:/home/richard# apt-get upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages were automatically installed and are no longer > required: > dconf-cli gir1.2-notify-0.7 libconfig9 libgtkspell3-3-0 libindicator3-7 > mate-indicator-applet > mate-indicator-applet-common python3-psutil python3-setproctitle > Use 'apt autoremove' to remove them. > The following packages have been kept back: > linux-image-686-pae xorg xserver-xorg > 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. > root@stretch-2nd:/home/richard# > > My questions: > > 1. In the first run, I don't understand: > Processing triggers for initramfs-tools (0.130) ... > update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae > I: The initramfs will attempt to resume from /dev/sda5 > I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576) > I: Set the RESUME variable to override this. > As /dev/sda5 is my SWAP. > Actually, after bit of digging, that part became much more clear, because resume option is used to specify partition device for software suspend, and swap is logical choice for that.
Re: Questions after doing update and upgrade on Stretch
Le 21/05/2017 à 16:35, Richard Owlett a écrit : On 05/21/2017 09:23 AM, Pascal Hambourg wrote: Check with blkid that sda5 has this UUID. Gparted reports that UUID for /dev/sda5 Then it is fine. I'll hold off on that until I can double-check on packages that were reported as "automatically installed" but no longer needed. I thought that one was installed manually. Don't worry. These packages won't be automatically removed unless you run apt-get autoremove.
Re: Questions after doing update and upgrade on Stretch
Richard Owlett wrote: > I had done: >apt-get update >apt-get upgrade > The tail end of the output was: > ... > Setting up libkde3support4 (4:4.14.26-2) ... > Setting up libktexteditor4 (4:4.14.26-2) ... > Setting up libkdewebkit5 (4:4.14.26-2) ... > Setting up libkhtml5 (4:4.14.26-2) ... > Setting up libplasma3 (4:4.14.26-2) ... > Setting up kdelibs5-plugins (4:4.14.26-2) ... > Processing triggers for initramfs-tools (0.130) ... > update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae > I: The initramfs will attempt to resume from /dev/sda5 > I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576) > I: Set the RESUME variable to override this. > Processing triggers for libc-bin (2.24-10) ... > root@stretch-2nd:/home/richard# last bit is new message from initramfs upgrade. i edited my /etc/default/grub file to make sure there is no resume going on at all by changing the line: GRUB_CMDLINE_LINUX="root=LABEL=ROOT_00 noresume" your own line may look different. :) > Before asking for confirmation to do the "upgrade" it said 3 packages > would not be upgraded. > If it said which packages, I didn't spot it. you'd need dist-upgrade to grab the new kernel version that is all that is about. > I then reran with following result. > > root@stretch-2nd:/home/richard# apt-get upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages were automatically installed and are no longer > required: >dconf-cli gir1.2-notify-0.7 libconfig9 libgtkspell3-3-0 > libindicator3-7 mate-indicator-applet >mate-indicator-applet-common python3-psutil python3-setproctitle > Use 'apt autoremove' to remove them. > The following packages have been kept back: >linux-image-686-pae xorg xserver-xorg > 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. > root@stretch-2nd:/home/richard# > > My questions: > > 1. In the first run, I don't understand: > Processing triggers for initramfs-tools (0.130) ... > update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae > I: The initramfs will attempt to resume from /dev/sda5 > I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576) > I: Set the RESUME variable to override this. > As /dev/sda5 is my SWAP. 'splained above... > 2. I don't understand any implications of: > The following packages have been kept back: > linux-image-686-pae xorg xserver-xorg the difference between apt-get upgrade and apt-get dist-upgrade. covered by the man page. songbird
Re: Questions after doing update and upgrade on Stretch
On 05/21/2017 09:23 AM, Pascal Hambourg wrote: Le 21/05/2017 à 15:34, Richard Owlett a écrit : 1. In the first run, I don't understand: Processing triggers for initramfs-tools (0.130) ... update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae I: The initramfs will attempt to resume from /dev/sda5 I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576) I: Set the RESUME variable to override this. As /dev/sda5 is my SWAP. Check with blkid that sda5 has this UUID. Gparted reports that UUID for /dev/sda5 2. I don't understand any implications of: The following packages have been kept back: linux-image-686-pae xorg xserver-xorg These packages cannot be upgraded due to dependency changes. This is usually solved with dist-upgrade. I'll hold off on that until I can double-check on packages that were reported as "automatically installed" but no longer needed. I thought that one was installed manually. Won't be able to follow up until this afternoon. Thank you.
Re: Questions after doing update and upgrade on Stretch
On 21-05-17, Richard Owlett wrote: > I had done: > apt-get update > apt-get upgrade > The tail end of the output was: > ... > Setting up libkde3support4 (4:4.14.26-2) ... > Setting up libktexteditor4 (4:4.14.26-2) ... > Setting up libkdewebkit5 (4:4.14.26-2) ... > Setting up libkhtml5 (4:4.14.26-2) ... > Setting up libplasma3 (4:4.14.26-2) ... > Setting up kdelibs5-plugins (4:4.14.26-2) ... > Processing triggers for initramfs-tools (0.130) ... > update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae > I: The initramfs will attempt to resume from /dev/sda5 > I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576) > I: Set the RESUME variable to override this. > Processing triggers for libc-bin (2.24-10) ... > root@stretch-2nd:/home/richard# > > Before asking for confirmation to do the "upgrade" it said 3 packages would > not be upgraded. > If it said which packages, I didn't spot it. > I then reran with following result. > > root@stretch-2nd:/home/richard# apt-get upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages were automatically installed and are no longer > required: > dconf-cli gir1.2-notify-0.7 libconfig9 libgtkspell3-3-0 libindicator3-7 > mate-indicator-applet > mate-indicator-applet-common python3-psutil python3-setproctitle > Use 'apt autoremove' to remove them. > The following packages have been kept back: > linux-image-686-pae xorg xserver-xorg > 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. > root@stretch-2nd:/home/richard# > > My questions: > > 1. In the first run, I don't understand: > Processing triggers for initramfs-tools (0.130) ... > update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae > I: The initramfs will attempt to resume from /dev/sda5 > I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576) > I: Set the RESUME variable to override this. > As /dev/sda5 is my SWAP. > > 2. I don't understand any implications of: > The following packages have been kept back: >linux-image-686-pae xorg xserver-xorg > > TIA > > > > As for number 1 can't say much about it, I do not get it either. But 2 happens because you've used apt-get upgrade instead of apt-get dist-upgrade. Packages that will uninstall some packages already installed on your system and that will change some dependencies require dist-upgrade. It happens always in case of linux-image packages. It will leave your previous working linux-image on though, but will uninstall one older than that, so you will always end up with chance to boot in working kernel, if new one messes up some things.
Re: Questions after doing update and upgrade on Stretch
Le 21/05/2017 à 15:34, Richard Owlett a écrit : 1. In the first run, I don't understand: Processing triggers for initramfs-tools (0.130) ... update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae I: The initramfs will attempt to resume from /dev/sda5 I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576) I: Set the RESUME variable to override this. As /dev/sda5 is my SWAP. Check with blkid that sda5 has this UUID. 2. I don't understand any implications of: The following packages have been kept back: linux-image-686-pae xorg xserver-xorg These packages cannot be upgraded due to dependency changes. This is usually solved with dist-upgrade.
