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.
Most folks here do not seem to have gotten the 'joke'.
With regard to the color of the Model T's (1919 - 1925),
Henry Ford is quoted for having said that
"Any color the customer wants, as long as it's black."
This quote was never published in any newspaper,
rather it appears in his (co-written) autobiography, "My Life and Work," published in 1922.
___________________
Ford always gave the customer the choice of any color they would like
by simply repainting their Model T _after_ they drove it home.
Slackware has always given the choice of boot loaders
by simply choosing not to install a bootloader at-all during the initial install
but rather installing whichever bootloader one may prefer to use _after_ the initial install has completed.
Fontconfig-2.13.92 is 4 years old now and the current version if 2.14.2. I remember some of the releases after 2.13.92 were problematic, but it might be worth checking out the new version to see if those problems have be resolved.
So unless I am misinterpreting this, Slackware64 will be GRUB only, and 32-bit will be lilo ?
It's not 64bit vs 32bit but rather UEFI/Secure_boot vs BIOS MBR boot
I have 3 64bit machines all running slackware64-current.
All 3 of them are BIOS MBR boot via lilo
The problem seems to be that some newer machines that are UEFI/Secure_boot
do not work with elilo as boot manager and therefore GRUB is needed for such machines.
So unless I am misinterpreting this, Slackware64 will be GRUB only, and 32-bit will be lilo ?
I think that in this very thread it has been explained dozens of times that LILO, ELILO and SYSLINUX have big problems with modern hardware. All three are software abandoned more than 8 years ago by their authors.
Today, only one bootloader included in Slackware is actively maintained: GRUB2. I think the obvious answer is that Slackware must eliminate the "dead weight" that are the other bootloaders.
And GRUB2 is able to work with both BIOS only and UEFI only hardware. It can very well be used instead of LILO or SYSLINUX and ELILO.
I don't think you can bring any service to Slackware if you insist that they be included by default, and as default. I mean not only you, but also those who insist on this. Let's let these software rest in peace.
I think this is what Mr. Volkerding meant: it's time for Slackware to use only GRUB2, as all other Linux distributions do today.
Yes, the other Linux distributions today also have and use systemd-boot, but I don't think it is an option for Slackware.
It's not 64bit vs 32bit but rather UEFI/Secure_boot vs BIOS MBR boot
I have 3 64bit machines all running slackware64-current.
All 3 of them are BIOS MBR boot via lilo
The problem seems to be that some newer machines that are UEFI/Secure_boot
do not work with elilo as boot manager and therefore GRUB is needed for such machines.
I do not believe that. My computer does not have Secure Boot, but it has UEFI and CSM, but neither LILO nor ELILO works in it. But GRUB2 works. The problem is much more generic. These bootloaders are simply dead before my hardware was created.
It's true, today there are more and more computers where Secure Boot cannot be disabled and have no CSM. Coincidentally, there are 2 laptops of this kind in my family, which laptops are "Windows 11 ready". So I can precisely confirm that they exist and are more and more numerous.
Slackware has no support for Secure Boot, and GRUB2 alone does not change anything. Quite simply, today there are many computers in which Slackware does not even boot.
Now we will see who will win this battle of wills on hardware. Slackware or Microsoft with its Windows 11?
Last edited by ZhaoLin1457; 08-02-2023 at 09:31 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.