Hello there,

I just got my hands on a macbook and immediatly installed a debian on it. Although it was one of the longest installation I've ever made, I strangely enough managed to get everything work (without actually knowing how, I truely can't remember what I did to get lilo work as I wanted to).

Anyway, I decided to reinstall Mac OS X into the small partition I had left for it, and realized just now that I can't boot to linux anymore... I tried to reinstall lilo, that helped only a bit. The boot process started this time, but I got a nice kernel panic can find init, or something of that sort. My root and boot declaration in lilo.conf are correct, and I've checked every possible detail I could. And then I realized that there's something really fishy with my partitions. In order to install lilo again, I used the debian installation CD, mounted /dev/sda4 (root partition) and /dev/sda6 (boot) and did a chroot. The funny thing is that after that I run 'mount' and the listing says:
/dev/sda6 on /
/dev/sda4 on /boot
How is that possible ? The gparted tool of debian installer is correct, but apparently for a strange reason, my debian installation messes everything up, hence the init problem I have...

Is there any tip for me here ? I would hate to reinstall just for that. I've checked all webpages I could find (debian wiki, the gentoo wiki and mactel website (can't remember the exact name)), but didn't find a thing.

Thanks in advance for your help,
acp

that sounds a little confusing to me, are you saying that /boot and / switch when you mount them?

Yes, that's right. The associated devices seem to switch... Anyway, I decided to do it the dirty way, I reinstalled a couple of times until I got it right... which I did, finaly !

Not that I solved the problem above, but I got linux installed. The trick is (at least for the new macbooks and dual booting, not windows) to install lilo in the mbr (although 90% of the websites I saw said to do otherwise) and then use refit to choose which OS you want to use.

Anyway, everything seems quite fine now.

Thanks for your comment,
acp