1015 2002-06-18 02:46:22 +0400 detectloader misdetects the loader in some circumstances 2009-09-16 17:31:02 +0400 1 1 4 Development Sisyphus bootloader-utils unstable all Linux CLOSED FIXED P4 major --- 7371 1 mhz placeholder at bga boyarsh crux glebfm inger ldv mike placeholder rider sem slazav sr vitty vsu vt qa-sisyphus oldest_to_newest 968 0 mhz 2002-06-18 02:46:22 +0400 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. --- --- 3775 1 mhz 2002-06-18 03:14:07 +0400 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. 7140 2 mhz 2002-06-18 03:14:07 +0400 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. 3776 3 inger 2003-01-15 18:31:01 +0300 добавлен skiplist 7141 4 inger 2003-01-15 18:31:01 +0300 добавлен skiplist 10291 5 vsu 2003-10-18 21:57:33 +0400 1) skiplist - это не решение. Невозможно перечислить все места, где не надо искать загрузчик - после подключения USB flash и прочих подобных устройств тоже появляются записи в /proc/partitions. Должно быть ещё средство для явного указания списка устройств. 2) Всё это должно быть документировано - запись "skiplist for mhz" в %changelog пакета никак не может считаться документацией. 14679 6 ldv 2004-06-03 20:16:21 +0400 Reassigned to maintainer. 35560 7 rider 2006-02-09 16:49:03 +0300 Неужто нельзя прочитать существующие конфиги, посмотреть где там у них должен быть bootloader и уже там искать ? 96454 8 mike 2009-08-14 18:11:09 +0400 Мужики, подсобите? 99200 9 repository-robot 2009-09-16 17:31:02 +0400 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).