Bug 1015 - detectloader misdetects the loader in some circumstances
: detectloader misdetects the loader in some circumstances
Status: CLOSED FIXED
: Sisyphus
(All bugs in Sisyphus/bootloader-utils)
: unstable
: all Linux
: P4 major
Assigned To:
:
:
:
:
: 7371
  Show dependency tree
 
Reported: 2002-06-18 02:46 by
Modified: 2009-09-16 17:31 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2002-06-18 02:46:22
In this loop:

    foreach (@disks) {
        $loader = typeOfMBR($_) and return $loader;
    }

The @disks list is not sorted by device name. This can lead to, e.g., /dev/hdd checked before /dev/hda. My /dev/hdd (my old drive) hosts LILO, and this is what detectloader finds first. This resulted in a hosed system when I have updated grub on my system which resides in /dev/hda.
---

---

------- Comment #1 From 2002-06-18 03:14:07 -------
I hereby propose a solution.
Make detectloader accept the optional device parameter, as a pathname or in
Grub format. Having this parameter specified, detectloader restricts probes to this device. The install scripts for Grub and Lilo should then determine target device from their respective configuration files.
------- Comment #2 From 2002-06-18 03:14:07 -------
I hereby propose a solution.
Make detectloader accept the optional device parameter, as a pathname or in
Grub format. Having this parameter specified, detectloader restricts probes to this device. The install scripts for Grub and Lilo should then determine target device from their respective configuration files.
------- Comment #3 From 2003-01-15 18:31:01 -------
добавлен skiplist
------- Comment #4 From 2003-01-15 18:31:01 -------
добавлен skiplist
------- Comment #5 From 2003-10-18 21:57:33 -------
1) skiplist - это не решение. Невозможно перечислить все места, где не надо
искать загрузчик - после подключения USB flash и прочих подобных устройств тоже
появляются записи в /proc/partitions. Должно быть ещё средство для явного
указания списка устройств.

2) Всё это должно быть документировано - запись "skiplist for mhz" в %changelog
пакета никак не может считаться документацией.
------- Comment #6 From 2004-06-03 20:16:21 -------
Reassigned to maintainer.
------- Comment #7 From 2006-02-09 16:49:03 -------
Неужто нельзя прочитать существующие конфиги, посмотреть где там у них должен
быть bootloader и уже там искать ?
------- Comment #8 From 2009-08-14 18:11:09 -------
Мужики, подсобите?
------- Comment #9 From 2009-09-16 17:31:02 -------
bootloader-utils-0.4.1-alt1 -> sisyphus:

* Wed Sep 16 2009 Vladislav Zavjalov <slazav@altlinux> 0.4.1-alt1

- installkernel:
  - change lilo restarting logic (closes #1014, #1015, #20695):
    old behaviour: restart lilo if first bootloader found in
      devices from /proc/partitions is lilo
    new one: restart lilo when lilo bootloader is found in
      device from boot= setting in lilo.conf
  - when detectliloboot.sh fails to find device, there are no
    need to run detectloader.sh (thx Dmitry V. Levin)
      (closes: #21106)
  - suppress unwanted output from cd -
- detectloader: replace by two shell scripts:
    detectliloboot.sh -- to get boot device from lilo.conf
    detectloader.sh -- to get bootloader type on the given device or file
- bootloader_utils.pm:
  - (getroot): recognize UUID and LABEL
      (thx Dmitry V. Levin) (closes: #2194, #18127)
  - remove unused functions (partitions, typeOfMBR) used in
      removed detectloader program
- rebootin
  - remove GRUB support
  - fix working with quoted labels in lilo.conf (closes: #11446).
  - cleanup code, improve error and help messages
  - add long options, add -l option for listing available labels.
  - update manpage
- remove URL and Packager tags (thx Dmitry V. Levin).