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.
...Grub2 is offered for those who want it and people complain that it is there. I don't get it. ...
Didn't mean to offend. You know "teaching an old dog new tricks" and all that.
I'm all in with whatever PV decides on for Slackware's new boot loader.
Already studying grub2 manual. I hope it solves the initial efi boot problem.
It looks like it may be able to boot into setup from the install dvd while in UEFI mode.
That would be great news.
John
Didn't mean to offend. You know "teaching an old dog new tricks" and all that.
I'm all in with whatever PV decides on for Slackware's new boot loader.
LILO won't be going anywhere. GRUB was added purely because it's a nice option for UEFI (and LILO doesn't work there at all). So use it if you like (for UEFI or BIOS)... otherwise, don't.
LILO won't be going anywhere. GRUB was added purely because it's a nice option for UEFI (and LILO doesn't work there at all). So use it if you like (for UEFI or BIOS)... otherwise, don't.
LILO won't be going anywhere. GRUB was added purely because it's a nice option for UEFI (and LILO doesn't work there at all). So use it if you like (for UEFI or BIOS)... otherwise, don't.
Is ELILO not a suitable LILO replacement?
BTW: Today I tried grubx64.efi with 14.0: It seems to load the kernel (still 3.8.13 which works fine with ELILO) + initrd and then crashes the machine without further notice. Currently I have no idea how to debug this...
LILO won't be going anywhere. GRUB was added purely because it's a nice option for UEFI (and LILO doesn't work there at all). So use it if you like (for UEFI or BIOS)... otherwise, don't.
And syslinux is still in there. I know because I've been using it (literally, extlinux) for a few years, and have been with -current. I wanted more than what I could do in LILO, didn't want to have to re-run the lilo command every time I changed something, and ended up hating grub almost as soon as I tried it (installed from source back then).
While I can install syslinux from source (I have done so to test out new versions), I'd like to see it stay in Slackware.
I just upgraded a fresh install of Slackware 14.0 to -current today, following the instructions provided on SlackDocs. The upgrade went without any issues. Not that I would expect otherwise... It therefore seems highly likely that an up-to-date version of Slackware 14.0 would also upgrade to -current without issue. No doubt upgrades to the future release of Slackware 14.1 would similarly be flawless.
I'll prepare alpha releases of updated mirror lists for slackpkg this week. This time I'll additionally look for rsync mirrors for the mirrors.slackware.com website, and also include armedslack in addition to the x86 and x86_64 architectures for slackpkg. I think I'm correct in saying that Slackware releases aren't available for S/390 anymore, so I'll encourage Pat to remove that list from the slackpkg package. Hopefully I'll finalise the lists within a few weeks so that it doesn't interfere with the Slackware 14.1 release date (so to speak). I'll bump the relevant thread I created last year and post the pre- and final releases of the updated lists there. Anyway, happy Slacking!
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.
[..] 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) [...]
At boot time, when you see lilo's screen hit [Tab], and complete your command line, e.g.
Code:
Linux 3
Of course you can set any kernel or modules parameters that way.
Last edited by Didier Spaier; 09-23-2013 at 07:08 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.