Lilo and Multi-boot x86 / x86_64
Hi,
I decided that it was about time I tried out 64bit Slack today. I've installed it beside my 32bit installation in logical partitions: Code:
pwatk@laptop:~$ cat /proc/partitions My first hurdle is amending my lilo.conf so I can boot both installations which is proving to be a task (I've never found lilo that intuitive anyway). Here's my current config can someone tell me where I'm going wrong here because I keep getting a fatal error because lilo can't find the kernels from my other installation: Code:
# LILO configuration file I used a script I made ages ago to create the initrd (I've never had issues with it before). Again can someone help me track down the problem here: Code:
#!/bin/sh |
About the initrd, I suggest copying /etc/mkinitrd.conf.sample to /etc/mkinitrd.conf, changing the lines as required, and then running `mkinitrd -c -F`.
About LILO, you need to have both kernels on mounted filesystems and reference those paths in your lilo.conf. For example, if you're running in the 64-bit installation, you need to have the 32-bit partition mounted (my example location will be /mnt/slack32). Then you have to point LILO to a kernel at path /mnt/slack32/boot/vmlinuz . |
Thanks for your reply,
I managed to figure out lilo. Helps to rtfm sometimes :), I thought the image had to be relative to the root (obviously not). I finally got around to using the mkinitrd_command_generator.sh script (it's only taken a year or two before I considered taking the easy route :) ) and that seams to have solved the issue with the generic kernel. I have bigger issues at the moment though. I ran slackpkg upgrade-all and it's managed to screw up something. I can't even login because apparently /bin/bash can't be found. Strange happenings but maybe not for this topic. I'm gonna reinstall and try again, it's less work than fixing the problem right now (even though bash exists). |
On the weird Bash issue, check that you uncommented a mirror of the right architecture (64 vs 32 bit) in /etc/slackpkg/mirrors. It's a common mistake.
Good luck! |
Got it one! I nearly done it on the second attempt as well :newbie: .
Nevermind, it's all sorted now. Thanks for your input. |
All times are GMT -5. The time now is 01:53 AM. |