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'm glad it works for you PROBLEMCHYLD. Do you multiboot?
Yes, I have Windows 7, Slackware and Redo Backup. I don't have any issues. I used the online configurator and never had to use it again. I change it manually now because all I do is update the kernel really. https://cloudclovereditor.altervista.../index.php#gui
I have for several years used a multi-boot system, rEFind with Slackware-current, Windows (now 11), and two other copies of Slackware. One of the slackware --current exists as a quick way to get into my main daily driver of -current in case I bork it some how (a few times each year). Another copy of -current is for experimenting and messing around and I wipe that partition out and start it over clean occasionally. I have had various Debian-oid derivative Linuces like Ubuntu, kali, pop!,and, even "Mint" (but not for long #$&@%!!!) on other boot options, but presently just 3 slackware and one Win11. rEFInd resides in its directory in /boot/efi/EFI/refind. my main daily driver Slackware is in /boot/efi/EFI/Slackware/ where a simple elilo.conf and elilo.efi and a vmlinuz copied in from the latest vmlinuz-huge reside. I just stick with -huge rather than -generic because rebuilding the rd seems more trouble than the benefit I get.
Using elilo means I have to remember to run eliloconfig after each kernel update or otherwise open one of my other linuces and manually copy vmlinuz-huge-X.xx.x into /boot/efi/EFI/Slackware (without the extension). The other accessory Slackware linuces i just let rEFInd locate for me. I dont permit eliloconfig to overwrite the efi boot entry table. I do rarely change the efi boot entry table via the UEFI interface provided by my AsRock motherboard, but generally boot rEFInd as the default. I dont have to update rEFInd when I change anything because it is the bootloader and runs by itself independently before anything else. I tried grub-ing it for awhile but i really dont like the whole GNU nanny-verse thing. [I had mistakenly thought that refind-install was packaged with slackware-current but had forgotten i got it from Rod's refind-bin.zip at his website long ago]
Thanks PROBLEMCHYLD, I was unaware of Redo and it looks quite cool. I'll have to try it out.
To everyone - I do recognize that I make my problem more complex by my choices. My boxes usually have many drives, at least 2 and as many as 6, each having several partitions with few exceptions. There exists numerous kernels from so many bootable systems and I don't always delete ones no longer in use in a timely fashion, so any auto detect like with rEFInd or Grub's OS-Prober, is more an annoyance than a benefit. Plus, I prefer to manually edit refind.conf so I can customize entries for differing purposes and identify them with custom icons and also delete any auto-detected entries, which is actually a really nice feature in rEFInd. I just wish I could see what entries rEFInd made automaticallyso I would learn what works, how it works, and what might be applicable to manual configuration.
Still, it seems to me it should be possible to simply designate what kernel, what partitions, what label, and what options much like LILO is for MBR, and have it work or fail just like LILO so one can actually learn reasons why. I despise paint-by-numbers. I'd much rather fail and learn.
That reminds me. Thank you guys for your contributions here and elsewhere. I think we agree that LQN is a great place to learn and also appreciate the relative expertise common to Slackers.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.