talking about boot loader with referencece to slack distro everybody talk about lilo. what about grub? does it suit finre to slack? why it is not the default loader?

tradition ?

I don't know why it is not the default, but it works well in slack and there is an official
grub package now. What I like the most with grub is that you don't need to reinstall it
in MBR after a config change.

I boot slack with grub, more often than not distros ship with lilo, don't know why this is since grub offers much more. Only problem is its strange 'we'll fix it one day' way of counting partitions.

Heh. I love grub, exactly because it's weird. If I wanted things to be easy, I'd be on MacOSX. The joy of linux is in fiddling!

It is not weird at all at boot you can have the grub shell with built-in commands like
clear, cat, reboot, quit, root, color, device, find...(type help)
Or just choose to boot from a menu like lilo.

Only thing is that grub has its way of naming partitions, that the only thing I could call weird in grub

LiLo does the job, has always done the job, and Grub doesn't really have anything over it. Grub isnt in official release yet (technichly still exp. I believe).

Why should slackware use grub when has always worked before and its not broken? I really don't think you need all those features in a bootloader, it seems very superfluous. All you really need is for it to boot your kernel every time you need to, and lilo does this well. I mean really... its a bootloader. If you can't remember to rerun lilo, or need to use those commands at boot you probably shouldn't be using slack.

I'm pretty sure that when grub2 becomes moderately functional this will begin to change..
but lilo is the simple way to go..

lilo is also much more concise. it's not at all necessary to load all the freekin stages that grub uses.. it just fits nicely in the mbr... but the price that comes with that is that you have to re-write the mbr every time you make changes of any sort to the lilo configuration or the kernel image itself