I was farting around with dpkg on my recently re-installed system, looking for a way to see which packages took up the most space (which had been an issue previously) and discovered the following:
$ dpkg-query -W -f='${Installed-Size}t${Package}n' | sort -nr
158443 linux-image-extra-4.4.0-34-generic
158201 linux-image-extra-4.4.0-31-generic
121492 linux-firmware
109159 firefox
108164 libgl1-mesa-dri
68655 linux-headers-4.4.0-34
68628 linux-headers-4.4.0-31
58638 breeze-icon-theme
54242 linux-image-4.4.0-34-generic
54206 linux-image-4.4.0-31-generic
Excellent! I thought. I've got a new keel image. And thanks to it's new 'no reboot' magic...
$ uname -r
4.4.0-31-generic
Hmmm. That's not right. Shouldn't it be 4.4.0-34?
I was really looking forward to some absurdly long uptimes thanks to "no reboot" keel patching, and am under the impression that the system should be using the latest (-34) version. Is there some additional step I'm overlooking? Might a forthcoming update fix the issue? Or - say it's not so - is there a reboot in my future
Recent Questions...
ما را در سایت Recent Questions دنبال میکنید
برچسب:
نویسنده: استخدام کار
بازدید: 413
تاريخ: پنجشنبه
21 مرداد
1395 ساعت: 6:25