Author Topic: C2 RC2 - Wrong Extras for selected OS X partition  (Read 2453 times)

0 Members and 1 Guest are viewing this topic.


  • Entrant
  • Posts: 7
C2 RC2 - Wrong Extras for selected OS X partition
« on: August 13, 2009, 02:22:27 PM »
I think this might be a bug (or maybe a misunderstanding) about
how the Extra folder gets paired up with the root partition at
boot time.

I have three MacOS X systems installed on the same disk.
Each contains a top-level Extra folder with appropriate kexts, etc.
The EFI partition is not being used.

It appears that Chameleon is always using the first partition that
contains an "Extra" folder no matter which partition is selected
to run MacOS at boot time. After startup, the selected MacOS
becomes the root as it should. But when watching the startup
process, the Extra/Extensions are being loaded from the first
partition that contains an Extra folder. I think I'm clearing
the proper caches...

Is this not the right way to have multiple MacOS systems on
the same disk? I'm trying to do things this way so I can experiment
with completely different versions of MacOS that require different

As a concrete example, if I select "MacOS2" with the following layout,
the Extensions from the MacOS1 partition are loaded but then MacOS2
becomes the root:

Partition MacOS1

Partition MacOS2

Thanks for any suggestions.



  • Entrant
  • Posts: 7
Re: C2 RC2 - Wrong Extras for selected OS X partition
« Reply #1 on: August 15, 2009, 02:48:55 PM »
Perhaps this report should be moved to the "Feature Requests".

But it's not a bug: it is a misunderstanding.

From reading the source code, I now believe Chameleon loads
the kernel and Extra directory kexts from the first bootable
partition on the drive. Then the root partition selected
from the GUI is mounted. So you can have multiple MacOS
partitions, but they all must share the same mach_kernel,, and Extra/Extensions.

If anyone knows better, please post a correction.