Message: previous - next
Month: February 2012

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

From: Patrick Serru <patrick@...>
Date: Wed, 8 Feb 2012 21:45:49 -0500
Le dimanche 05 février 2012, Darrell Anderson a écrit :
>> I'd like to undergo an effort to cleanup and
>> reorganize all of our kcm modules. Over time there have been
>> features added which are placed in the wrong section, other
>> times things have been done inefficiently or made to be
>> overly complicated.
>> I am going to open an etherpad for this. I would
>> also like any users/developers to respond to this email with
>> anything they find to be weird/out of place.
>> I'll start: the Kicker configure screen,
>> underneath appearance has an "advanced options"
>> button. There is nothing advanced about these options and it
>> should be more clearly organized.
> Okay, here are some conversation starters:
> ...

> * Why in System Administration is there is a configuration option for LILO
> but not for GRUB? Both should be supported. 
> ...
> Darrell
      Hi everybody

      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!


NB: Not directly related to Trinity, but thinking about this "final" 
installation, another concern is the support for ReiserFS. This file system 
seems being abandoned for EXT4 and is sometimes simply ignored by 
distributions at the time of installation. This will likely cause me