Slackware and the grub boot loader.
Hi: Two questions:
(a) Do you know anybody using slackware with grub? I mean grub loads the Slackware operating system. (b) Does grub come with the Slackware installation disks? |
Yes and yes. Grub isn't used as the bootloader by default. You can install grub manually by chroot into your system.
at the elilo/lilo prompt open another console chroot /mnt then run grub-install and grub-mkconfig |
Everything that @colorpurple21859 wrote.
I think that I don't have any physical machines left that use lilo/elilo. In fact, I just installed grub 2.04 on my Slackware64 14.2 machine so I could easily boot into windows 10 on that particular machine. 2 of the other machines don't have to deal with windows, so I don't need to upgrade grub on them. The last machine is running -current, so grub 2.04 is already there. |
Thanks. Is there a detailed procedure, assuming I already have the grub boot loader in the MBR, to make the boot loader to load Slackware? I think the procedure is quite simple, only involving at most two steps. Perhaps in the Slackware documentation there are precise instructions to follow?
I have already tried using grub with Slackware in the past but the result has been complete failure and it is already three years that I lack Slackware in my machine. |
after installing bootloader to mbr run
Code:
grub-mkconfig -o /boot/grub/grub.cfg |
I use GRUB.
I've been using GRUB since before I started using Slackware, when GRUB was version 0.9x. Back in those days I was multi-booting a lot. I found GRUB more suited to that environment. Just edit menu.lst and not worry about forgetting to run lilo. I don't think GRUB was included in Slackware until around 10.1 and was in the /extra branch. I use lilo in throwaway Slackware VMs. |
Quote:
|
Quote:
|
Quote:
Code:
grub-install /dev/sda Yes you should be able to boot debian after running that command, but there maybe other issues that we aren't aware of at this time. |
This is the grub.cfg I got:
Code:
bill@darkstar:/boot/grub$ cat grub.cfg |
Quote:
|
Do you have an initrd.gz?
If you only use the first slackware entry to boot and it works without the initrd.gz line, I wouldn't worrry about it. Otherwise grub is versatile so there is several ways of doing this. 1. As per Richard Cranium post 11 2. Copy the slackware menu entries that you want to use to /etc/grub.d/40_custom and insert the initrd=/boot/initrd.gz between the vmlinuz line and the } line and run update-grub. Be aware that is file is static and won't change with a kernel version change. 3.Chainload slackware grub.cfg with this entry Code:
menuentry 'Slackware chainload (on /dev/mmcblk0p2)' --class slackware --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-2d63e598-b1b4-4e32-a781-9fe9ceae2c11' { |
I would like to ask how the approach to installing grub2 if you have uefi differs
Quote:
Previously I had a pc using bios; i booted up in lilo , removed it ,installed grub2 ran command grub-mkconfig -o /boot/grub/grub.cfg from memory and everything worked. Then if i understand it grub stage 1 was on mbr and that pointed to grub stage2. For myself and probably many others having a /dev/sda with a gpt label, a 100MB of EFI and presently using elilo ,how would the approach to installing grub2 differ than if you have say a bios pc and lilo? I see in boot there is a grub folder. Would installing grub2 put files there are creates another directory called grub2 ? |
@captain_sensible - you can preview what grub will see and how it will function if you have rEFInd installed for EFI booting. Just load your Slackware install media and select it with rEFInd and the grub bootloader for UEFI media boot will appear and display all the kernels it finds (even some you may have no intention of using excepting recovery) and you can test each and every one.
|
1 Attachment(s)
Quote:
|
All times are GMT -5. The time now is 11:48 AM. |