lilo removal in squeeze (or, "please test grub2")
in [Debian]
|
From: Ferenc Wagner on 24 May 2010 16:20 Daniel Baumann <daniel(a)debian.org> writes: > On 05/24/2010 11:29 AM, Ferenc Wagner wrote: > >> You may want to try extlinux, it works much like LILO in this respect. >> It lacks a convenient configuration system, but that of grub-legacy >> would be easy to adapt, and I actually plan to work on this. > > sometime ago i've added extliux-install and update-extlinux. if fits my > setups well, however, any other/better ideas how to improve it are very > welcome, see #573042 for more information. Heh, yes, that's me again. :) I got distracted, but didn't give up work on this. Now I'm nosing around the current Grub2 method for ideas. Meanwhile, the unconditional destroying of extlinux.conf on update gave me the grief again. :-/ -- Cheers, Feri. -- To UNSUBSCRIBE, email to debian-devel-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/87d3wlyt1a.fsf(a)tac.ki.iif.hu
From: consul tores on 24 May 2010 18:40 2010/5/22 Sven Joachim <svenjoac(a)gmx.de>: > On 2010-05-23 07:47 +0200, Stan Hoeppner wrote: > >> No, resist forced conformity. This is Linux. We have multiple choice with >> everything else, so we should darn well have our choice of boot loader. > > You're welcome to work on lilo so that can cope with the increasing size > of kernel images and initramfs. > > Sven Again, and again; Debian depends of Linus Torvals; maybe it is time to seriously think about Debian kernels! I use lilo , and i am going to test other bootloaders as GAG. - Consultores Agropecuarios. Administracion, Produccion, Capacitacion. -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/AANLkTilY4nEiux0xQLyQveTT-VwI9d2dBJ1ibd7P_ONS(a)mail.gmail.com
From: Stan Hoeppner on 24 May 2010 18:50 Ferenc Wagner put forth on 5/24/2010 4:36 AM: > I chatted about this with the grub upstream a couple of days ago. > According to Vladimir, most of those bugs are already fixed, but there's > nobody around to do a new upload. Both grub maintainers (Felix Zielke > and Robert Millan) unexpectedly disappeared some time ago. So it would appear boot loaders in general have a lack of interested/committed developers? Both LILO and GRUB. <sarcasm> So instead of just LILO, why didn't the Debian team just throw both bootloaders out the window and start over with committed devs? </sarcasm> -- Stan -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4BFB0152.60305(a)hardwarefreak.com
From: Harald Braumann on 25 May 2010 05:10 Hi, On Sat, May 22, 2010 at 10:39:52PM -0500, William Pitcock wrote: > (4) Users need to test grub2 now. I've been using grub2 for quite some time now on several different systems with mixed success. On simple standard system -- one disk, one kernel in /boot, no fancy stuff -- it works quite well. On other systems it often breaks miserably. Updates leave my system unbootable every other time. One major problem are incompatible versions of the boot loader installed in the MBR and grub.cfg. Currently, automatic installation of grub in the MBR is a no-go for me, because of #554790 but I can't prevent grub from automatically updating grub.cfg which leads to incompatible versions, hence an unbootable system. On some systems the generated grub.cfg is useless for me. On each update I have to check for changes and incorporate them in my own hand-edited version. It is my belief, that the whole automagic configuration system as it is now is far to complex and convoluted. It is too inflexible to support any requirements by the user the developers haven't thought about and in this case you have to work actively against the system to get what you want. See #578576. I'm not sure if this can be fixed or if the whole system has to be rethought. Currently I'd tend to the latter. And because of the tight dependency between the loader and grub.cfg and zero-tolerance of the loader to unknown parameters in grub.cfg, it is far too fragile and very easily leads to an unbootable system. Because of this, coupled with the many open bugs and the lack of documentation, I'm not sure if grub2 is ready to be released to the unsuspecting public. Cheers, harry -- To UNSUBSCRIBE, email to debian-devel-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100525090027.GA30023(a)sbs288.lan
From: Mihamina Rakotomandimby on 25 May 2010 07:10
> William Pitcock <nenolod(a)dereferenced.org> : >This bug *can* be fixed, but not without a significant rewrite of the >way that lilo's stage2 loader code works. Given that there is no >active upstream and that the Debian lilo package carries many patches >for bug fixes that are alleviated by standardizing on grub2, this >seems like the best option for Debian. Agreed: dead (and buggy) softwares must be out of the distribution. Whatever happens. If LILO regains upstream coders, its return to the distribution is quite easy. -- Architecte Informatique chez Blueline/Gulfsat: Administration Systeme, Recherche & Developpement +261 3456 000 19 -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100525140820.0bc3613c(a)pbmiha.malagasy.com |