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.
Can someone including LC (whom I have a great deal of respect for on this forum) give me a solid reason why I should not use the rEFInd bootloader - either in 15.0 or -current? I ask only because I have been using it on multiple Desktop and Server machines without any issues.
Not me, anyway. Use what you see fit.
Quote:
It seems a lot of attention and emotion has been exerted on GRUB2 which might be a better solution??? Why??? Is it really more simple? Because simple rules in my domain when it comes to boot loaders...
Whether a solution be better than another one all depends on the use case, so only you can determine which is better for you. GRUB is certainly not more simple but has a way wider scope, as it can accommodate a lot of architectures and contexts, in Legacy as in EFI modes. As a result, really understand its usage and features certainly needs time and learning. On the other hand, once properly configured it can handle most use cases without any hassle. As an example users of a distribution I maintain (as most others) have nothing specific to do in case of a kernel upgrade, building a new initramfs and updating the boot menu accordingly is done automatically, both in Legacy and EFI modes.
TL,DR: if you are happy with rEFInd, keep it. Else, try GRUB.
Last edited by Didier Spaier; 08-04-2022 at 02:31 AM.
Can someone including LC (whom I have a great deal of respect for on this forum) give me a solid reason why I should not use the rEFInd bootloader - either in 15.0 or -current? I ask only because I have been using it on multiple Desktop and Server machines without any issues.
I use rEFInd on all of my PC. But, sadly, rEFInd does not work in qemu VM (I use edk2 firmware for UEFI support). I haven't try it vmware or hyper-V VM.
If your requests didn't make it into this iteration, perhaps
we will revisit them for the next -current cycle.
Some were just a little too late but will more than likely
be needed next time (I'm looking at Didier's grubconfig)
Yesterday we had some heated discussions about LILO, ELILO and GRUB2 boot loaders.
Here the solution is not too difficult to choose, there are already packages in Slackware.
For some time I have another problem and this involves systemd!
I use a commercial antivirus to protect the mail server (besides Clamav which still fails to be a good product, it does not even manage to ensure the updating of dependencies e.g. LLVM, 7-Zip) which will have its EOL in July 2023. Another product has been released, but unfortunately it has "Systemd supported and running" in the system requirements.
I tried to look for another antivirus that can be installed in Slackware and doesn't require systemd, but so far I haven't found it!
Does anyone have a solution in this case?
I'm a bit stuck, I don't know if there will ever be systemd in Slackware, and I haven't used another Linux distribution for servers (RedHat before it was a commercial distribution and Debian) for over 10 years.
Not using any commercial software of this kind, but I imagine there will be support centers for this kind of commercial software. Maybe if you ask support for non-systemd systems, they would patch the software or at least point you to a workaround
Not using any commercial software of this kind, but I imagine there will be support centers for this kind of commercial software. Maybe if you ask support for non-systemd systems, they would patch the software or at least point you to a workaround
Cheers,
ltlnx
All commercial antivirus products have/require SystemD support.
The current configuration for this antivirus software actually requires Systemd, I tested this in Ubuntu because in Slackware it can't even be installed.
I requested support for non-systemd systems, I told them that I am a long-time user of their products and that I use Slackware.
Maybe they didn't know Slackware existed if they didn't look through the logs to see what operating systems their antivirus was running on.
I don't really think I convinced them with this, even until now Slackware was not part of the supported platforms, but it was fully functional.
It would be cool to see that they added support for Slackware.
I use rEFInd on all of my PC. But, sadly, rEFInd does not work in qemu VM (I use edk2 firmware for UEFI support). I haven't try it vmware or hyper-V VM.
I did not try it on QEMU, just curious, are you using the binary package or the source package or have tried both, as they are compiled from different tool. Source are compile with the gnu elf tools while the binary release from the author is compiled with TianoCore EDK2.
I did not try it on QEMU, just curious, are you using the binary package or the source package or have tried both, as they are compiled from different tool. Source are compile with the gnu elf tools while the binary release from the author is compiled with TianoCore EDK2.
I use pre-compiled binaries from kraxel.org repository. Haven't tried building it myself.
Can someone clarify the ChangeLog entry? I don't have access to one of my -current systems ATM. What other than just installing (upgradepkg...) and rebooting is needed? Has anyone tried it?
Quote:
> Fri Aug 5 21:04:39 UTC 2022
...
> a/elilo-3.16-x86_64-13.txz: Rebuilt.
> Patched to disable the Confidential Computing blob for SEV-SNP, which
> fixes booting a 5.19 kernel with the EFI stub enabled. If you use elilo,
> be sure to either run eliloconfig again or manually copy (and rename) the
> proper elilo binary to your EFI System Partition.
Can someone clarify the ChangeLog entry? I don't have access to one of my -current systems ATM. What other than just installing (upgradepkg...) and rebooting is needed? Has anyone tried it?
Yep, at least 2 of us reported that the update elilo works on the original 5.19.0.
Thanks Chuck56. I forgot the upgradepkg only puts the binaries in /boot -not- the ESP mount point "/boot/efi/EFI/Slackware". You would then also need to rerun eliloconfig or the efibootmgr to register the new binary.
Quote:
Yep, at least 2 of us reported that the update elilo works on the original 5.19.0.
Thanks Chuck56. I forgot the upgradepkg only puts the binaries in /boot -not- the ESP mount point "/boot/efi/EFI/Slackware". You would then also need to rerun eliloconfig or the efibootmgr to register the new binary.
If you manually copy & rename the .efi file to the ESG then it's not necessary to rerun elioconfig or efibootmgr. If the .efi name changes in the ESG then yes rerun eliloconfig or efibootmgr.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
