Lähettäjä: Andrew McGlashanPäiväys: 2017-05-08 14:37 UTC Vastaanottaja: dngAihe: Re: [DNG] Linux 4.9 kernel
Hi,
On 08/05/17 23:58, Andrew McGlashan wrote:
> I've got good logs, now I'll try to work out exactly when it was
> installed (4.9) and if there were any other packages that were done at
> that time.
The /var/log/apt/history.log.N.gz files have the following:
Start-Date: 2016-10-26 06:43:14
Commandline: apt-get upgrade
Upgrade: linux-image-3.16.0-4-amd64:amd64 (3.16.36-1+deb8u1,
3.16.36-1+deb8u2), libgd3:amd64 (2.1.0-5+deb8u6, 2.1.0-5+deb8u7),
tar:amd64 (1.27.1-2+b1, 1.29b-1~bpo8+1)
End-Date: 2016-10-26 06:43:30
Start-Date: 2016-10-27 00:49:49
Commandline: apt-get upgrade
Upgrade: tzdata:amd64 (2016f-0+deb8u1, 2016h-0+deb8u1)
End-Date: 2016-10-27 00:49:50
Start-Date: 2016-10-30 16:05:42
Install: linux-image-4.7.0-0.bpo.1-amd64:amd64 (4.7.8-1~bpo8+1,
automatic), firmware-linux-free:amd64 (3.3, automatic), irqbalance:amd64
(1.1.0-2~bpo8+1, automatic)
Upgrade: linux-image-amd64:amd64 (3.16+63, 4.7+75~bpo8+1)
End-Date: 2016-10-30 16:06:10
And this from /var/log/apt/term.log.N.gz
Log started: 2016-10-30 16:05:42
Selecting previously unselected package firmware-linux-free.^M
(Reading database ... ^M(Reading database ... 5%^M(Reading database ...
10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading
database ... 25%^M(Reading database ... 30%^M(Reading database ...
35%^M(Reading database ... 40%^M(Reading database ... 45%^M(Reading
database ... 50%^M(Reading database ... 55%^M(Reading database ...
60%^M(Reading database ... 65%^M(Reading database ... 70%^M(Reading
database ... 75%^M(Reading database ... 80%^M(Reading database ...
85%^M(Reading database ... 90%^M(Reading database ... 95%^M(Reading
database ... 100%^M(Reading database ... 37528 files and directories
currently installed.)^M
Preparing to unpack .../firmware-linux-free_3.3_all.deb ...^M
Unpacking firmware-linux-free (3.3) ...^M
Selecting previously unselected package linux-image-4.7.0-0.bpo.1-amd64.^M
Preparing to unpack
.../linux-image-4.7.0-0.bpo.1-amd64_4.7.8-1~bpo8+1_amd64.deb ...^M
Unpacking linux-image-4.7.0-0.bpo.1-amd64 (4.7.8-1~bpo8+1) ...^M
Preparing to unpack .../linux-image-amd64_4.7+75~bpo8+1_amd64.deb ...^M
Unpacking linux-image-amd64 (4.7+75~bpo8+1) over (3.16+63) ...^M
Selecting previously unselected package irqbalance.^M
Preparing to unpack .../irqbalance_1.1.0-2~bpo8+1_amd64.deb ...^M
Unpacking irqbalance (1.1.0-2~bpo8+1) ...^M
Processing triggers for man-db (2.7.0.2-5) ...^M
Setting up firmware-linux-free (3.3) ...^M
update-initramfs: deferring update (trigger activated)^M
Setting up linux-image-4.7.0-0.bpo.1-amd64 (4.7.8-1~bpo8+1) ...^M
I: /vmlinuz.old is now a symlink to boot/vmlinuz-3.16.0-4-amd64^M
I: /initrd.img.old is now a symlink to boot/initrd.img-3.16.0-4-amd64^M
I: /vmlinuz is now a symlink to boot/vmlinuz-4.7.0-0.bpo.1-amd64^M
I: /initrd.img is now a symlink to boot/initrd.img-4.7.0-0.bpo.1-amd64^M
/etc/kernel/postinst.d/initramfs-tools:^M
update-initramfs: Generating /boot/initrd.img-4.7.0-0.bpo.1-amd64^M
...
...
...
The 3 3.16 kernel upgraded on the 26th of October (normally), then the
4.7 kernel was an "automatic" install.... no "Commandline:" entry?
It doesn't look like I manually chose to update, other than accepting
what was presented by perhaps "aptitude safe-upgrade -V" option.
Strange....
Kind Regards
AndrewM