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.
Reply to: