Bug#535331: marked as done (lilo not run after install/upgrade)

2010-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 21 Jun 2010 01:53:10 + with message-id and subject line Bug#505609: fixed in linux-2.6 2.6.26-24 has caused the Debian Bug report #505609, regarding lilo not run after install/upgrade to be marked as done. This means that you claim that the problem has been dealt with.

Bug#535331: lilo not run after install/upgrade

2009-12-17 Thread Mikołaj Menke
The problem is that installer wants to run update-grub, and if there is no grub the package cannot be fully installed, but it should be possible as there is lilo. Lilo can be run manually. dwf122:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information

Bug#535331: linux-image-2.6.32-trunk-amd64: FWIW, grub also isn't run after installation

2009-12-17 Thread Xavier Bestel
Package: linux-2.6 Version: 2.6.32-1 Severity: normal Hi, not only lilo, but grub also isn't run. Here's a part of aptitude's output (I'm really sorry, it's in French): Sélection du paquet linux-image-2.6.32-trunk-amd64 précédemment désélectionné. (Lecture de la base de données... 111898 fichi

Bug#535331: ditto

2009-11-07 Thread Josip Rodin
On Fri, Oct 23, 2009 at 11:54:21AM +0200, Josip Rodin wrote: > I've experienced the same problem. I've got two lenny machines which have [...] FWIW Here's the last upgrade output pasted exactly as it just happened: % sudo apt-get upgrade Reading package lists... Done Building dependency tree

Bug#535331: 2.6.26-17lenny2 => 2.6.26-19 OK, 2.6.26-19 => 2.6.26-19lenny1 NOT OK

2009-10-24 Thread Bjørn Mork
Just to add another data point, lilo failed to run again for me too on the 2.6.26-19lenny1 upgrade. Even after working on the previous kernel upgrade! I'm now totally lost wrt what triggers this bug... To summarize: 2.6.26-17lenny2 => 2.6.26-19 lilo OK 2.6.26-19 => 2.6.26-19lenny1 li

Bug#535331: ditto

2009-10-23 Thread Josip Rodin
On Fri, Oct 23, 2009 at 01:15:52PM +0200, maximilian attems wrote: > On Fri, Oct 23, 2009 at 11:54:21AM +0200, Josip Rodin wrote: > > Hi, > > > > I've experienced the same problem. I've got two lenny machines which have > > GPT paritition tables and Linux root on LVM, and they can't use anything b

Bug#535331: ditto

2009-10-23 Thread maximilian attems
On Fri, Oct 23, 2009 at 11:54:21AM +0200, Josip Rodin wrote: > Hi, > > I've experienced the same problem. I've got two lenny machines which have > GPT paritition tables and Linux root on LVM, and they can't use anything but > LILO (there are some novelty hacks for GRUB but I haven't been able to t

Bug#535331: ditto

2009-10-23 Thread Josip Rodin
Hi, I've experienced the same problem. I've got two lenny machines which have GPT paritition tables and Linux root on LVM, and they can't use anything but LILO (there are some novelty hacks for GRUB but I haven't been able to test them yet because this is in production). I have kernel-img.conf set

Bug#535331:

2009-09-08 Thread Bjørn Mork
I am sorry, but I'm afraid my previous analysis in this bug report is completely wrong. The kernel image maintainer scripts are not supposed to run lilo directly. They trigger an initramfs update, and that should in turn cause lilo to run after it's finished. The initramfs update must do this r

Bug#535331:

2009-09-07 Thread Oliver Seufer
Package: linux-image-2.6.26-2-686 Version: 2.6.26-19 Hello, this annoying bug still exists in version 2.6.26-19. Is there a plan to fix the issue? The best thing would be if you can set the boot loader in /etc/kernel-img.conf. Oliver -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.d

Bug#535331: Can anyone please explain why 'lilo' was removed from linux-image-*.postinst?

2009-07-31 Thread Bjørn Mork
maximilian attems writes: > thanks for your fine analysis, could you for completness please post > the output of the following: > cat /etc/kernel-img.conf Of course, but do note that there is nothing you can set there which will make the postinst script continue past the line last unless $loa

Bug#535331: Can anyone please explain why 'lilo' was removed from linux-image-*.postinst?

2009-07-31 Thread maximilian attems
On Fri, Jul 31, 2009 at 01:35:59PM +0200, Bjørn Mork wrote: > The issue is this difference: > > --- /var/lib/dpkg/info/linux-image-2.6.18-6-686.postinst2009-05-05 > 07:43:48.0 +0200 > +++ /var/lib/dpkg/info/linux-image-2.6.24-etchnhalf.1-686.postinst > 2009-07-27 06:37:00.00

Bug#535331: Can anyone please explain why 'lilo' was removed from linux-image-*.postinst?

2009-07-31 Thread Bjørn Mork
The issue is this difference: --- /var/lib/dpkg/info/linux-image-2.6.18-6-686.postinst2009-05-05 07:43:48.0 +0200 +++ /var/lib/dpkg/info/linux-image-2.6.24-etchnhalf.1-686.postinst 2009-07-27 06:37:00.0 +0200 @@ -25,7 +25,7 @@ $|=1; # Predefined values: -my $vers

Bug#535331: possible reason

2009-07-02 Thread Matus UHLAR - fantomas
Looking at differencies, there seems to be key differente between etch's 2.6.18 and 2.6.24 kernels' postinst scripts. the variable "$loader" gets initialized to "lilo" in 2.6.18, and to empty value in 2.6.24. I don't see any way to (preferrably) autodetect or configure this variable according to c

Bug#535331: lilo not run after install/upgrade

2009-07-01 Thread Matus UHLAR - fantomas
Package: linux-image-2.6.26-2-686 Version: 2.6.26-17 Hello, after installing linux image the lilo is not being called, which results into system not being bootable after upgrade. I've tried without kernel-img.conf also with it, containing "do_bootloader = Yes", nothing helped. If lilo isn't supp