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
kexts.
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
mach_kernel
com.apple.Boot.plist
Extra/
Extensions/
...
Partition MacOS2
mach_kernel
com.apple.Boot.plist
Extra/
Extensions/
...
Thanks for any suggestions.
-hsparks