Question

[Ubuntu] New /boot/grub/menu.lst after `apt-get upgrade`?

Hi there!

Just started a new droplet with Docker.

I wanted to make sure I have the newest version, so I ran apt-get update and apt-get upgrade after which I got the following in Terminal:

A new version of /boot/grub/menu.lst is available, but the version
     │ installed currently has been locally modified.
 
     │ What would you like to do about menu.lst?
 
     │      install the package maintainer's version
     │      keep the local version currently installed
     │      show the differences between the versions
     │      show a side-by-side difference between the versions
     │      show a 3-way difference between available versions
     │      do a 3-way merge between available versions (experimental)   
     │      start a new shell to examine the situation

I’ve never edited the menu.lst file, I imagine this is something done by DO.

What exactly is happening here, and what option should I select?

Thanks!

Dillon


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

I used the option to see differences…

“There are no non-whitespace differences in the files.”

OK then, new version it is!

Update: after finding this discussion, I chose to keep the current version (prompted twice). After that, I rebooted my server and crossed fingers and it looks like it survived the reboot.

So I suppose the “keep current version” is not an entirely bad option.

This is what worked for me to eliminate the GRUB conflict message during the initial “apt upgrade” after spinning a new Ubuntu server.

$ sudo apt update $ sudo rm /boot/grub/menu.lst $ sudo update-grub-legacy-ec2 -y $ sudo apt -y upgrade $ sudo reboot