Hi,
I am little confused about Grub in Slackware 15.0
1. Is it Grub or Grub2?
2. Now my system is booted via elilo. Is it possible to
configure and install Grub2 directly into the system without
installing the theme from Slackbuild and making a bootable usb stick
first?


Thanks

it's grub, no need to install anything from slackbuild
slackware doesn't have the update-grub command. The /dev/sda will need to be changed accordingly for your setup.

Thanks! Much appreciated.

Shouldn't you swap those two?

grub-install will create the /boot/grub directory if it doesn't exist, grub-mkconfig will throw a error message if /boot/grub doesn't exist. Grub-install only needs to be ran once during installation, grub-mkconfig needs be run everytime there is a kernel update if you don't use symlinks.

1 members found this post helpful.

What used to be grub is called grub-legacy, found on SBo under that name.
What used to be grub2 is now found on Slackware DVD.

Opensuse, PclinuxOs, Fedora based distros use /boot/grub2, grub2-install, grub2-mkconfig
Most other distros use including Slackware use /boot/grub. grub-install, grub-mkconfig

They name these files grub2 because they used to ship both of them..
It doesn't matter in Slackware, since it does not use/install grub or grub-legacy.
What is packaged and shipped on Slackware DVD is grub-2.x so grub v2 or grub2 in short.

I beleive the op was referring to the grub command to use, to invoke grub2 commands on Fedora based distros among others are and the grub boot loader files go into /boot/grub2,

Slackware and others use and the grub files go in /boot/grub.

Slackware does not use or run this command by default.

Not trying to argue, just saying..

The OP is confused about Grub in 15.0 (fact).
Then the OP asks if Grub (legacy?) or Grub2 (current?) is shipped in Slackware.

I think that is a source of this little misunderstanding here.

The package already contains /boot/grub/.

In some cases you may need to run grub-install more than once.

The order of the commands might matter in the future. :-)

Hey, I missed this thing somehow..
It does not need to be run in Slackware, because Slackware kernel update packages use symlinks.
And if you compile a custom kernel, the resulting file will be called vmlinuz, so that is what you'd specify in grub config.

Furthermore, naming the files properly is very important on EFI partition which is FAT so it can't use symlinks.
So if you had named them properly you would not need mkconfig on each update, whoever told you that is either a debian or redhat user.

I’m well aware of all the exceptions to this rule. The key words are “if you don’t use symlinks” . There are those that prefer not to use the symlinks, neither name custom kernels as vmlinuz, or put kernels on the efi partition.

1 members found this post helpful.

But if it's a corner case, it cannot be marked as "Slackware does this".
If one doesn't use symlinks by choice, then it's also one's choice to use mkconfig on update or not.
It's not like the distributor forces mkconfig on you, which is the standard case with those other distros.

Same thing with grub-install, if the installer does not do that how can "Slackware use it" ?
It requires the user to exit the installer, drop to shell, and type the command.
Otherwise, one could say "ln -s grub-install grub128-install && grub128-install" is what "Slackware use" because it just happens to work like that.

In conclusion, it's the user who does it and not the distributor (I'd prefer to keep it that way TBH).