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.
Could Pkgtools be updated to use lbzip2 if present. I see that -current Pkgtools have already been updated recently in -current to use plzip instead of lzip if present. So this is a requested change along those lines (with the same kinds of benefits). Such a change should make .tbz packages a reasonable option for self-built packages for many users (those with the right hardware). In this thread I show some examples of the benefits of using different compressors with Pkgtools, including lbzip2. I also provide example patches for Pkgtools.
Use GRUB instead of lilo/elilo for configuration post-installation.
Why?
Because GRUB is a lot more versatile, works well for multiboot and is actively developed.
Because the same commands allow to reconfigure the boot loader, be it in BIOS or EFI mode.
Thanks to Cyrille Pontvieux (jrd) and Dimitris Tzemos (djemos) this replacement doesn't need much more than a review and inclusion of the grubconfig and setup.grubconfig scripts in Slackware and a small modification of the installer.
I made several tests in a virtual machine where I have installed Slint, Slackware, Debian and Manjaro.
GRUB works well run from Slint, Debian and Manjaro, both in BIOS and EFI mode.
Some adjustments are probably needed for some of the GRUB scripts, but all least all aforementioned system boot OK (they live in two hard disks, one with a DOS partition table and the other one with a GPT, including an ESP).
Amazingly, if I run eliloconfig from Slint it steals the show (I can only boot Slint) but if I then run grubconfig I get all boot entries back, including one for elilo that in turn allows to start Slint, as does the first one in the attached pic.
I am of course ready to help integrate this in Slackware.
Caveat: I didn't test a multi boot with Windows or a *BSD so far.
Last edited by Didier Spaier; 04-11-2018 at 02:59 PM.
At the moment Grub2 does not support, for example, direct download from Reiser4 partitions. I know, that you can use a separate /boot with ext2 or any other file system that Grub2 supports (i'm use reiserfs :-) ).
With the same result, you can use, for example, extlinux. :-)
This also very good bootloader. And its also present into Slackware Linux. ;-)
Got nothing against that, but apparently it's a controversial subject. Maybe an addition would be a better word than replacement.
Well it will be up to Pat to decide. Currently at the end of installation we are allowed to install lilo and|or elilo, however it doesn't make sense to install both grub and one of the others.
With the same result, you can use, for example, extlinux. :-)
This also very good bootloader. And its also present into Slackware Linux. ;-)
Yes but I wouldn't advise to use syslinux in an UEFI context and its development has stalled. Anyway it's not an answer to the multi boot issue, at least if a non Linux OS comes into play.
Last edited by Didier Spaier; 04-11-2018 at 04:13 PM.
Because GRUB is a lot more versatile, works well for multiboot and is actively developed.
Because the same commands allow to reconfigure the boot loader, be it in BIOS or EFI mode.
Thanks to Cyrille Pontvieux (jrd) and Dimitris Tzemos (djemos) this replacement doesn't need much more than a review and inclusion of the grubconfig and setup.grubconfig scripts in Slackware and a small modification of the installer.
I made several tests in a virtual machine where I have installed Slint, Slackware, Debian and Manjaro.
GRUB works well run from Slint, Debian and Manjaro, both in BIOS and EFI mode.
Some adjustments are probably needed for some of the GRUB scripts, but all least all aforementioned system boot OK (they live in two hard disks, one with a DOS partition table and the other one with a GPT, including an ESP).
Amazingly, if I run eliloconfig from Slint it steals the show (I can only boot Slint) but if I then run grubconfig I get all boot entries back, including one for elilo that in turn allows to start Slint, as does the first one in the attached pic.
I am of course ready to help integrate this in Slackware.
Caveat: I didn't test a multi boot with Windows or a *BSD so far.
Well it will be up to Pat to decide. Currently at the end of installation we are allowed to install lilo and|or elilo, however it doesn't make sense to install both grub and one of the others.
Can you quote the part where I said it makes sense to install multiple loaders, and where I said it's up to someone else?
It's controversial, because it resides above the kernel and distribution level.
Of course, whenever possible. But I am considering uses cases where using elilo or lilo are not an option. Not all users want to have only Slackware and|or another Linux on their computer.
Last edited by Didier Spaier; 04-11-2018 at 05:03 PM.
Can you quote the part where I said it makes sense to install multiple loaders, and where I said it's up to someone else?
I didn't pretend you said that. I am just saying that it is simpler for most users to be just proposed one tool, but also that I just make a suggestion and am open for discussion.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.