| rvdboom |
09-23-2013 05:49 AM |
Quote:
Originally Posted by hitest
(Post 5032168)
Yeah, I am also more comfortable with lilo and like how it works. When 14.1 comes out I may try GRUB on one of my boxes just for the novelty. :)
|
As always, use whatever works for you. I moved to grub because now and then I appreciate that I can just modify the boot command line, especially the kernel options or the run level, at boot time. Very handy when for some reason I want to boot on runlevel 3 (I usually go directly to 4) or when I run into a buggy kernel (I tend to compile my own kernels to test newer ones).
Funily, grub seems a bit more complicated in its 2.0 version than what it was in the legacy one, but there are enough tutorials on the web to quickly get the hand of it. It's rather simple.
Well, both works, happy to see grub in Slack since I use it.
What I did, to avoid having many entries called "Slackware 14" as someone told, is to go into /etc/grub.d, created one script per kernel I want to boot, as "0*_slackware_perso_*" and using the following syntax :
Code:
#!/bin/sh -e
cat << EOF
menuentry "Slackware Linux 3.11.1-vdb" {
set root=(hd0,1)
linux /boot/3.11.1-vdb root=/dev/sda1 ro resume=/dev/sda2 radeon.dpm=1
}
EOF
I numbered them in the order of apparence that I wanted, then removed execution rights (chmod -x) to the "10_linux", "20_linux_xen" and "30_os-prober" scripts, which do the autodetection I want to avoid.
Then a simple "grub-mkconfig -o /boot/grub/grub.cfg" compiles the changes and with the reboot, I just have the entries I created by myself.
It was actually much simpler to upgrade from grub legacy than I feared. Once the package was upgraded, a simple "grub-install /dev/sda" was enough to install the new grub on the MBR and set up the various files, then I did my configuration as above. |
