LILO??? Are you serious???

[ajgringo619]

Running my normal updates routine a few minutes, and got a blast-from-the-past in the updates list:

Code: Select all

sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  lilo linux-headers-5.4.0-66 linux-headers-5.4.0-66-generic linux-image-5.4.0-66-generic linux-modules-5.4.0-66-generic linux-modules-extra-5.4.0-66-generic
The following packages will be upgraded:
  gir1.2-gdkpixbuf-2.0 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-bin libgdk-pixbuf2.0-common libgdk-pixbuf2.0-dev libldap-2.4-2 libldap-common linux-generic linux-headers-generic linux-image-generic linux-libc-dev
  qemu-block-extra qemu-utils
13 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
Need to get 77.1 MB of archives.
After this operation, 361 MB of additional disk space will be used.
Do you want to continue? [Y/n]

This is the first time I've gotten new kernel updates since removing grub and switching to systemd-boot. But why in the world is lilo being installed???

[ajgringo619]

UPDATE: this is coming from Ubuntu, not Mint. On my Ubuntu 20 VM, it tried to install GRUB and LILO after switching to systemd-boot (my Mint system already had a block of GRUB in-place). Not sure why these systems can't detect that a boot loader is already installed.

Does anyone here run rEFInd? Curious if this happens to them.

[antikythera]

rEFInd chainloads grub so no issue with lilo being installed by an update because rEFInd is a boot manager, not a boot loader. if you still have the log for that apt transaction it may tell you what the dependency that triggered lilo being installed was. Look at the file below:

/var/log/apt/term.log

[ajgringo619]

Weird...I tried looking at this file, both as me (fish shell) and root (bash) in xfce4-terminal, and it not only didn't show any transactions except from my original install (2/4), but I had to kill the terminals (would not reset, prompt was trashed, etc.). Opening the file in vim at least didn't crash my terminal, but there was nothing about LILO in there (probably since I aborted the update).

Any other place I can look? When I did the updates with both GRUB and LILO blocked, it ran fine - updated my systemd-boot entries after adding the new kernel as well.

[antikythera]

Any other place I can look?

Not sure, if there's an equivalent folder in /var/logs for apt-get look in there.

[ajgringo619]

Any other place I can look?

Not sure, if there's an equivalent folder in /var/logs for apt-get look in there.

Nope - nothing else.