LILO on Mac does nothing but parses lilo.conf and updates os-chooser and yaboot.conf, it is not a real bootloader like on PC. You can safely remove it. SuSE did PPC LILO for IBM PowerPC workstations and to make PC people feel more comfortable on Mac.. During normal startup procedure yaboot pick ups kernel from /boot directory on Linux partition. vmlinux and ramdisk on HFS boot partition are actually needed ONLY for installtion and/or update of base system if startup CD does not work or do not exists. If you load vmlinux and ramdisk from HFS boot partition you can install or update base system from NFS or FTP.
The problem people encounter while trying to configure dual boot is they try different approaches while not completely understanding technical background of this process.
Precisely. The annoying thing is that it's really not that difficult so why are the instructions so ridiculous? It's such a fundamental part of the installation that it really should have taken a high priority. Some people would abandon the whole idea of Linux because they can't get this working.
PS. Procedure described in SuSE manual is rather too complicated and not clear. Basically you just need open firmware to evaluate os-chooser script. After that, either yaboot either MacOS will be started up. However, yaboot needs valid yaboot.conf file to load proper kernel. That's only two files to edit!
I did dual-boot without LILO and editing open firmware variables.
I still don't understand how LILO enters the equation? I haven't touched LILO and my system is working fine. I'm worried that I've missed something though. I think perhaps that Linux is picking up its kernel from my HFS partition or possibly even a ramdisk on my HFS partition?
An explanation of how Open Firmware, os-chooser, yaboot, yaboot.conf, lilo and lilo.conf all interract would be invaluable.
******************************************************** * Best Regards --- Andrei Verovski * * e-mail --- andrei.verovski@bigfoot.com * * * * Personal Home Page * * http://homepage.mac.com/macgurutemple/ * ********************************************************