SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I use LILO in Debian, grub wasn't bad but grub2 is a mess. They've abandoned KISS principles and created a monstrous and tangled mess of scripts all in the name of automation and "automagic" installation... apparently editing one config file was just too much for some people...
For me Lilo is lighter and better - once you know how to configure it, you'll never look back.
for PACKAGE in `ls /var/log/packages`; do
echo "Why $PACKAGE ???"
done
Do I have to change my SN for a decent reply? Maybe... "SlackerMan" or something would yield more positive replies? You act as if I don't comprehend all your personal attacks towards me that you post in here I just ignore them. No I am not questioning every package on Slackware I just wanted to know why Lilo was chosen over Grub thats all...
You are forgetting that every time you attack me this reflects Slackware community on the forums.
The true answer to all queries similar to this is because Patrick Volkerding says so. There is no other reason than that. It is possible to use both grub and grub2 on Slackware but Slackware uses lilo because PV made it that way.
Mercury, you seem to have respect for Pat's posts. There's one of them where he explains it. It was even linked by another poster one of these days - if you search the first couple of pages on the forum, you might find it. Or just find Pat's profile and click on "Find more posts by volkerdi" then you'll find it, he doesn't have that many posts.
I just wanted to know why Lilo was chosen over Grub thats all...
There have been some good replies to your question already, but I wanted to follow up with some illustrations from the most recent two years of my chat logs. These are from system administrators working with production hardware at linux-based companies whose names everyone would recognize:
Quote:
I suspect plymouth is not your actual problem aside from its preventing you from seeing console output, and switching grub to turn off the "quiet" option will probably fix that, and let you see if/why X is failing to start.
Quote:
bleah. grub2 introduces some bourneshell-like scripting syntax but you still can't dynamically generate menu entries
Quote:
ugggghhh grub2! i know! let's make it huge and complicated and abstract every possible thing except what it would actually be useful to abstract!
Quote:
grub2 should just embed javascript and be done with it. (or lua, except that would actually be moderately sane.)
Quote:
my opinion of grub2 so far is that it seems to have managed to take a fairly simple concept and made it incredibly complicated to work correctly.
Quote:
g*d d*mm*t i hate grub
Quote:
f**k me f**king grub2 STILL can't deal with /boot being on a large partition! it's practically a whole operating system and has a huge disgusting config language but they couldn't bother to put in basic functionality it's lacked for 12 years
Quote:
in gpt you also need a bios_grub partition for grub to install in since it's so bloated
Quote:
look at grub2 in general. bleaaaaah. they should have grub3, the "yeah, let's pretend grub2 never happened" release.
Quote:
a forth bootloader would be SO MUCH BETTER than grub
Quote:
grub2 is a horror show
Quote:
haha "grub" and "works" in the same sentence
Quote:
grub2 has f**king loadable modules, it should be able to load from ANYTHING, because you know loadable modules are a GREAT IDEA in your BOOTLOADER
Quote:
i like it when grub says GRUBGRUBGRUBGRUBGRUBGRUBGRUBGRU all over the screen
Quote:
oh ffs grub-install can't be run in parallel because it uses a non-uniquized temp file name .. FU grub authors
To summarize: GRUB is an overcomplicated, buggy, ill-thought-out pile of junk which causes miles and miles of problems. By comparison, LILO is simple, stable, mature, and jfw. It seems like a no-brainer. Why *wouldn't* you stick with LILO?
Mercury, you seem to have respect for Pat's posts. There's one of them where he explains it. It was even linked by another poster one of these days - if you search the first couple of pages on the forum, you might find it. Or just find Pat's profile and click on "Find more posts by volkerdi" then you'll find it, he doesn't have that many posts.
I love to attack people I dislike but I can't do it "directly" on a forum so I have to do it in a "subtle" and passive aggressive way... that way he or nobody else will notice and I will subliminally start a flamewar in forums. Thats how we do things in France as we spread caviar onto our croissants.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
