![]() |
How to bypass /Extra from Loading?
Hi all,
Is there a way to bypass "/Extra" from loading at boot-up with a kernel flag? The reason I want this is that I have installed Snow Leopard and Leopard in my external hdd. This is how I configured my External HDD: Partition 1 = 30gb Snow Leopard Installed and this is where /Extra is installed (Chameleon RC3 Installed) Partition 2 = 30gb Leopard and there is no /Extra Partition 3 = 20gb NTFS I'm having problems booting in my Leopard partition because it loads the /Extra from the Snow Leopard partition as it was designed like that. Of course, my Leopard will have errors from the Snow kext. If it is not possible to bypass /Extra, what other methods do you suggest? Thank you. |
Put A Leopard Compatible /Extra On Your Leopard Partiton.
|
See this other thread on the same subject, I had more or less the same trouble.
It seems Chameleon always read the /Extra from the partition its booting from, despite of what the docs says... |
I am currently using BootThink v2.3 it provides different Extensions folders for 10.5 & 10.6 on the drive it's installed on. The more it allows to use two different Extensions folders for x86 & x64 Extensions for SL. :)
|
Hi all,
@STLVNUB - It was not working for me. It only loads /Extra on the partition where I installed Chameleon. It doesn't load any other /Extra folder. I really don't know why. @thorazine74 - I believe we have the same issue. I didn't read all of the thread, but I will (just read the 1st page). @lmkantus - I like bootthink also but they don't have themes. They don't right? Also, I had bad experience with VoodooTrackpad + Boothink. It becomes erratic. ------ My problems are somewhat solved but not fully. I also posted this topic in Chameleon forum and it was suggested that I make a 10.5 and 10.6 folder in /Extra/ It was working because it loads /Extra/10.6/Extensions folder when booting to snow. But when I boot to leopard, it doesn't boot the /Extra/10.5/Extensions folder. It just uses the S/L/E of Leopard which is fine with me. I don't know why it only recognizes the 10.6 folder. I think I'm doing something wrong. |