ehird
January 24th, 2007, 11:42 AM
Facts:
1. Uses rEFIt as the bootloader, which calls the linux partition "Linux on ". You could probably get rid of it after using its sync tool but I'm too scared :P
2. After booting the linux one on that, you'll get a lilo menu. Standard stuff, works fine.
3. No nice bootup splash screen! Enjoy pages and pages of text before GDM comes up.
4. Untested things right now: ATI drivers (1024x768, yay!), Airport, Bluetooth (know these don't work - will find out), ..., profit, etc.
5. Uses Boot Camp, but after partitioning it it will be b0rked and you will never be able to use Boot Camp again without destroying your linux partitions.
I... haven't actually tested booting into OS X after syncing yet, but - it was relatively easy once I found out what to do, and I'll post a HOWTO if anyone's interested.
Edit: Oh yes, you'll have to manually edit a config file and rerun lilo after every kernel update.
Edit: ARRRRGH! turns out i installed the 32bit edition.... gaaah
1. Uses rEFIt as the bootloader, which calls the linux partition "Linux on ". You could probably get rid of it after using its sync tool but I'm too scared :P
2. After booting the linux one on that, you'll get a lilo menu. Standard stuff, works fine.
3. No nice bootup splash screen! Enjoy pages and pages of text before GDM comes up.
4. Untested things right now: ATI drivers (1024x768, yay!), Airport, Bluetooth (know these don't work - will find out), ..., profit, etc.
5. Uses Boot Camp, but after partitioning it it will be b0rked and you will never be able to use Boot Camp again without destroying your linux partitions.
I... haven't actually tested booting into OS X after syncing yet, but - it was relatively easy once I found out what to do, and I'll post a HOWTO if anyone's interested.
Edit: Oh yes, you'll have to manually edit a config file and rerun lilo after every kernel update.
Edit: ARRRRGH! turns out i installed the 32bit edition.... gaaah