Can dyld, dylib and shared cache be compress and decompress when required to solve storage problem?
panz
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
From
Milano
Post
Replies
Boosts
Views
Activity
Can someone actually explain me what dyld_shared_cache_x86_64 and other files located at /System/Library/dyld are? I know that dyld is the dynamic libraries loader which recursively load required dylib into memory for every launched process but i still dont get what dyld_cache and aot_cache exactly are? I'm looking to a detailed explanation about those.
I'm trying to load a kext following this official documentation page, but when i try to load the kext with:
sudo kextutil -t /tmp/resourceCompressor.kext/
I get this error:
Executing: /usr/bin/kmutil load --bundle-path /tmp/resourceCompressor.kext
Error Domain=KMErrorDomain Code=71 "Kernel request failed: (libkern/kext) not loadable (reason unspecified) (-603946989)" UserInfo={NSLocalizedDescription=Kernel request failed: (libkern/kext) not loadable (reason unspecified) (-603946989)}
Also if i try to use the no load option i get another error:
sudo kextutil -t -n /tmp/resourceCompressor.kext/
kextutil: -n is not a supported kmutil mode
As far as i understand the kextutil, kextload, kextunload binaries have been deprecated i favour of kmutil but i cant find any guide on how to use it, and still i dont know why my kext cant be load.
What can I do to load it?