Jump to content
2 posts in this topic

Recommended Posts

It doesn't matter what "method" you use to boot your Hackintosh or your install DVD. In the end it's all based on the Chameleon boot loader, even the EFI-X uses code blatantly stolen from Chameleon, the people behind it passing it off as their own special boot loader, talking about how fantastic and proprietary it is, when in reality it's an USB flash drive with Chameleon installed on it.

 

What matters is how you configure Chameleon and how you apply the patches and fixes that allow you to run OS X.

 

Obviously, the less modifications you make to your main installation, the more updateable it is.

 

If everything is placed in /Extra rather than in system folders, or if the modifications you make does not entail editing system files, then you have done what you can.

 

Nearly every hackintosh modification necessary has a way to prevent it from getting obliterated by an update.

 

For example;

 

Those unable to run the vanilla kernel can name their patched kernel "my_patched_kernel" and load that kernel via /Extra/com.apple.Boot.plist. That way when an update overwrites the "vanilla" kernel nothing will happen.

 

Instead of patching a kernel extension in /System/Library/Extensions, we can use Legacy- or p-list only kexts. This way, when a kernel extension gets updated, the legacy/p-list only kext will continue working, injecting its properties into the updated kernel extension. I have been doing this since 10.5.6 for my Marvell 88E8056 on-board ethernet.

 

And so on.

 

Sometimes Apple changes things and previously working modifications stop working. There's nothing we can do about that until someone discovers a new way to fix it.

Link to comment
https://www.insanelymac.com/forum/topic/253447-mac-updates/#findComment-1662017
Share on other sites

×
×
  • Create New...