You are not logged in.
I have LVM volumes:
/dev/disk1/main
/dev/disk1/mainboot
/dev/disk1/other
/dev/disk1/otherboot
I can boot main by using syslinux with syslinux.cfg including:
LABEL main
MENU LABEL Main
LINUX ../vmlinuz-linux
APPEND root=UUID={UUID} {kernel parameters}
INITRD ../initramfs-linux.img
(1) I see a lot of places saying syslinux can't boot a kernel on another partition, and that you have to use extlinux for this. But, then http://www.syslinux.org/wiki/index.php/Install says "[4.00+] EXTLINUX has been merged into SYSLINUX, and both use 'ldlinux.sys' as bootloader file." Does this mean syslinux can now boot a kernel on another partition? Or, am I misunderstanding the scope of the merge, and do I still need to use extlinux?
(2) What is the label I need to give in the .cfg to use kernel /dev/disk1/otherboot/vmlinuz-linux and initrd /dev/disk1/otherboot/initramfs-linux.img?
(3) Can I just have one installation of syslinux, or do I need to chain load a second? If so, how do I do this, using LVM volumes? The syntax I see documented is "com32 chain.c32 \ append hd0 0" which doesn't apply to LVM. My preference is one installation of syslinux, but I can chain load if necessary.
I need their respective boot partitions separate, because I'm using compressed btrfs on main and other, which syslinux can't boot off, so their boot partitions have to be uncompressed. And, the two installations can use different kernels.
I have read https://wiki.archlinux.org/index.php?ti … ux_systems, but it's a disputed section that I can see a lot is wrong with, is incomprehensible to me, and I don't see anything in it that would remotely indicate to syslinux to look on another partition.
Last edited by jamespharvey20 (2016-01-31 05:44:28)
Offline