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.
Do we need grub2 as default boot loader?
Isn't it enough that it's shipped and you can use it if you want.
I use grub2 but i don't mind that it's not default, i used elilo earlier.
It's certainly enough and that's what every slacker uses if they need grub. We've reached a point where the developer is abandoning the project stating "NOTE: I have finished development of LILO at December 2015 because of some limitations (e.g. with BTFS, GPT, RAID). If someone want to develop this nice software further, please let me know ...". If this isn't giving Pat at least some pause for thought, I guess we're okay.
It's certainly enough and that's what every slacker uses if they need grub. We've reached a point where the developer is abandoning the project stating "NOTE: I have finished development of LILO at December 2015 because of some limitations (e.g. with BTFS, GPT, RAID). If someone want to develop this nice software further, please let me know ...". If this isn't giving Pat at least some pause for thought, I guess we're okay.
Consider my LILO development question uninformed and now answered, thank you.
Unless /boot partitions on BIOS systems change from any of the known formats to something else unknown then we have little to worry about with LILO, and I doubt that will happen.
Unless /boot partitions on BIOS systems change from any of the known formats to something else unknown then we have little to worry about with LILO, and I doubt that will happen.
That time might come sooner than you think I was able to make LILO to fail to load the kernel on my NUC machine.
I don't remember the exact details, but it was something about the amount of the memory assigned to graphics via BIOS.
If the memory amount was too high, LILO simply wasn't able to boot the kernel.
It's not that big deal for the moment, since the graphics memory in BIOS can be set to something low and then the OS enlarges it as it needs.
Anyway, at that moment I switched to syslinux, since LILO was marked EOL already.
That time might come sooner than you think I was able to make LILO to fail to load the kernel on my NUC machine.
I don't remember the exact details, but it was something about the amount of the memory assigned to graphics via BIOS.
If the memory amount was too high, LILO simply wasn't able to boot the kernel.
Is it the bug for which Sl4ck3ver provided a patch in this thread? I ask because it has been fixed:
Code:
Sun Apr 24 03:44:25 UTC 2016
✀---
a/lilo-24.2-i586-2.txz: Rebuilt.
Patched usable memory bug. Thanks to Sl4ck3ver.
Anyway Slackware provides lilo, elilo, grub and syslinux so we have enough software to be able to boot most machines.
Last edited by Didier Spaier; 04-26-2016 at 09:02 AM.
Reason: Last sentence rephrased
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.