Why Lilo?

[TheGatorade]

Hey everyone!

I have an idea: remove LILO and put GRUB instead. Grub2 is more good looking and advanced.

[thenktor]

Because LiLo is KISS

[Shador]

And because it's what Slackware uses. Actually it's enough to get you going and you can stll change afterwards if it's insuffivient.

[yves04]

Please keep Lilo.
It's much more simple to change lilo.conf than modify grub2.
Have a nice day.

[sqlpython]

Not really difficult at all.
I was a lilo user from 95 thru 02 and the switched to PCgrub which is much better/easier.
...
I just edit /boot/grub/grub.cfg..
It is a simple txt file.. For the unsure and hesitate of us simply make a backup of the original renaming it to say grub.txt
in the event you want to return to the original..
simple comme bonjour

[Shador]

I just edit /boot/grub/grub.cfg..
It is a simple txt file.. For the unsure and hesitate of us simply make a backup of the original renaming it to say grub.txt
in the event you want to return to the original..
simple comme bonjour

Yes, that's no problem. The warning is just there because it's overwritten on invocation of update-grub/grub-mkconfig and you should be aware of that when modifying that file directly. Unlike other distributions like Debian with Salix no hooks are setup to invoke update-grub automagically as needed, so unless you run it yourself, editing that file doesn't matter at all.