update manager refuses to upgrade kernel to newer version

[Tom H]

On Fri, Feb 12, 2016 at 5:45 PM, Ralf Mardorf <silver.bullet at zoho.com> wrote:
> On Fri, 12 Feb 2016 17:21:05 +0100, Tom H wrote:
>> On Fri, Feb 12, 2016 at 3:40 PM, Ralf Mardorf <silver.bullet at zoho.com>
>> wrote:
>>>
>>> A workaround is described here:
>>>
>>> http://edoceo.com/notabene/grub-probe-error-cannot-find-device-for-root
>>
>> Warning! The script on this page assumes that "/" is an extX
>> filesystem on "/dev/sda1".
>
> Important to me seems to be the idea to replace the bin by a script, if
> people won't disable GRUB2's auto-crap. However, the OP seems not to
> need a bootloader at all.

You might not like grub and it might not be suitable for your use-case
but it's the most widely used boot loader in Linux (and the default
for every major distribution) so it's working for the majority of
Linux users. So not only does the recommendation of not using
"update-grub" doesn't scale to the majority of users, but it's a
harmful contribution to the general, vanilla system-administration
knowledge base.

Your emails in this thread bring to mind one regular frustration that
I have on IT lists because there are often recommendations to make
changes that go against the OS's setup rather than use the OS's tools
in order to achieve what you want.

If changing variables in "/etc/default/grub" doesn't create the
appropriate grub menu entries for your use-case, you can set up custom
entries in "/boot/grub/grub.cfg" via "/etc/grub.cfg/4{0,1}_custom".
Jettisoning the grub infrastructure isn't necessary; it's fine for you
to do so privately and edit "/boot/grub/grub.cfg" directly but it's a
disservice to Ubuntu and Linux to recommend this as a run-of-the-mill
exercise.