Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#35916 - [linux] Nothing is wrong with checking for lilo.conf
Attached to Project:
Arch Linux
Opened by Connor Behan (connorbehan) - Monday, 24 June 2013, 19:35 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 26 June 2013, 08:00 GMT
Opened by Connor Behan (connorbehan) - Monday, 24 June 2013, 19:35 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 26 June 2013, 08:00 GMT
|
DetailsDescription: The last edit to linux.install is an overreliance on the fact that people are using official packages. I recommend putting a check back so that people with the /etc/lilo.conf file will see a warning telling them to run lilo after mkinitcpio finishes.
|
This task depends upon
Closed by Tobias Powalowski (tpowa)
Wednesday, 26 June 2013, 08:00 GMT
Reason for closing: Not a bug
Wednesday, 26 June 2013, 08:00 GMT
Reason for closing: Not a bug
Anyways, the detection done in the old .install file tries to detect if grub/grub2 is used when lilo.conf is present, but it doesn't take UEFI or syslinux stuff into account.