Felix Miata napsal(a):

Is this intended?

This is happening when removing old kernels left by multi-version enabling, which makes each kernel package (2 or 3 per kernel) removal take an absurd long time to accomplish. Or, is what looks like mkinitrd in fact perl-bootloader tripping over a large menu.lst that started with about 9 kernels?

Hi, perl-Bootloader doesn't have problems with many kernels in menu.lst. What is problem is large storage array (many disks, partitions, many software arrays), where it takes quite long time to initialize. You can test it by run update-kernel --refresh (I am not on suse, so maybe some typo in command). That call do nothing for grub, but initialize bootloader settings and is good for testing performance. JR -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Felix Miata napsal(a):

Is this intended?

This is happening when removing old kernels left by multi-version enabling, which makes each kernel package (2 or 3 per kernel) removal take an absurd long time to accomplish. Or, is what looks like mkinitrd in fact perl-bootloader tripping over a large menu.lst that started with about 9 kernels?

Hi, perl-Bootloader doesn't have problems with many kernels in menu.lst. What is problem is large storage array (many disks, partitions, many software arrays), where it takes quite long time to initialize. You can test it by run update-kernel --refresh (I am not on suse, so maybe some typo in command). That call do nothing for grub, but initialize bootloader settings and is good for testing performance. JR -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org