Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#12826 - Pacman won't detect GRUB2 while upgrading stock kernel

Attached to Project: Arch Linux
Opened by Lord LTSmash (LTSmash) - Saturday, 17 January 2009, 00:31 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 12 March 2009, 17:39 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity Very Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: This is perhaps a minus bug I found when upgrading to the latest kernel (if we can call this a bug):

While updating the kernel, the pacman output will say:

>>> You appear to be using the LILO bootloader. You should run
>>> 'lilo' before rebooting.

But this isn't correct since I'm using GRUB2... perhaps this is because the .install script checks for GRUB and if it doesn't finds it it will say we're using LILO?

I know it's not very important, but it can be a little confusing, and would be nice to have it detect our bootloader correctly.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Thursday, 12 March 2009, 17:39 GMT
Reason for closing:  Fixed
Additional comments about closing:  2.6.28.7-2
Comment by Dan McGee (toofishes) - Saturday, 17 January 2009, 06:00 GMT
Should we still be doing this lilo warning stuff?
Comment by Thomas Bächler (brain0) - Saturday, 17 January 2009, 11:10 GMT
I was in favor of throwing lilo away a year ago, but some people disagreed. Personally, I don't think we even need that warning.
Comment by Tobias Powalowski (tpowa) - Monday, 19 January 2009, 06:27 GMT
This warning is always given if you have lilo installed.
Comment by Greg (dolby) - Thursday, 12 February 2009, 17:15 GMT
+1 on removing lilo & the warning. Furthermore now that at least the official install media dont even reference lilo. Theres no way to automatically install it. Its just in [core].
Also even though that means nothing, the lilo website has been down for at least 3 months. Only http://freshmeat.net/projects/lilo/ and the mirror site works.
Comment by Alessandro Doro (adoroo) - Friday, 13 February 2009, 03:01 GMT
The warning is a very nice service for a *hypothetical* lilo user.

Anyway the detection is rather weak; we can't be totally sure about the bootloader.
If the message is to stay there maybe is better the generic warning:
if [ $haslilo -eq 0 ]; then
echo ">>>"
echo ">>> If you use the LILO bootloader, you should run 'lilo' before rebooting."
echo ">>>"
fi
Comment by Tobias Powalowski (tpowa) - Friday, 13 February 2009, 09:10 GMT
why does this warning hurt anyone?
if you don't have lilo installed it isn't even displayed.
Lilo still works fine for people who want to use it, official installer removed lilo, archboot still supports it.

Loading...