Message: previous - next
Month: February 2012

Re: [trinity-devel] KControl and the confusing mess it has become.

From: Darrell Anderson <humanreadable@...>
Date: Wed, 8 Feb 2012 19:55:23 -0800 (PST)
> > * Why in System Administration is there is a
> configuration option for LILO
> > but not for GRUB? Both should be supported. 
> > ...
>       I had a look here:
> I agree with 
> Darrell: "Both should be supported". <troll> In my
> mind, Lilo is for 
> bootstrap loaders what Trinity is for Windows managers: the
> latest versions 
> Grub2 and KDE4/gnome3 do not keep their promises. The
> universal usability 
> targeted by Grub may be reached today, but 99.999% of the
> standard PC + 
> Linux/Windows users dont care about that. I fill like having
> paid something 
> for that, like lost of time with re-intallation, for
> instance, especially 
> for problems of incompatibility between GRUB 1 and GRUB2.
> These systems "of 
> the future" are finaly good but for TESTs purpose
> only...</troll> So, I am 
> happy to see on that the
> project restarted 
> in June 2010. I will use LILO if its support is available at
> the moment I 
> will "definitively" install Trinity!

Check the etherpad for my comments. I don't want to see this option disappear but I recognize that people using distros that do not use LILO do not want to be bothered with the item. I recommended making this item a build option within the kcontrol cmake options. Those who want to see this item in kcontrol set a build option and those who don't tweak the opposite. Everybody wins.

I agree about GRUB. I still use 0.97 and have no desire to move to GRUB2 and the convoluted mess that app has become. A challenge with adding a kpart to kcontrol for GRUB is supporting both versions. Like LILO, GRUB 0.97 has not disappeared and is unlikely to disappear soon. So for now the best approach is to create a build option for the LILO option.