• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Rebuilding kext caches
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Rebuilding kext caches


  • Subject: Re: Rebuilding kext caches
  • From: Philip Petev <email@hidden>
  • Date: Mon, 17 Jun 2013 13:48:01 +0300

No, no, currently I have

touch ${3}/System/Library/Extensions

at the end of the last postinstall script. I tried also

kextcache -system-prelinked-kernel
kextcache -system-cache

and it works as well, but I was wondering which one is better to use, because it seems sometimes the kext caches are not being rebuilt with the touch command.
The second approach has the disadvantage that can be used only for the root volume, which may be the package target volume, but is also may be not.
All I want is to be sure that the kext caches has been rebuilt, because the touch approach is an automated method (the system determines if the caches should be updated or not by their timestamps) and the second method is forced, no matter if the caches are already up to date or not. So, in short, I want to use forced method, but it has to work not for the root volume, but for the package target volume.
I don't know did I explained myself clearly...


On Mon, Jun 17, 2013 at 1:02 AM, Andrew Keller <email@hidden> wrote:
On Jun 16, 2013, at 5:38 AM, Philip Petev wrote:

Hi guys,
Can you tell me which is the right way to trigger update of the kext cache from a package, because currently I'm just "touching" /S/L/E in the final postinstall script, but I don't know when the rebuilding process has finished and as far as I know, it's not a good idea to restart the machine before this process is completed. Is there a way to rebuild the cache from a package and when the process is over, then the final Summary screen to appear? Thanks in advance.

I'm not sure what's causing it, but with our installer, Installer.app always waits for kextcache to finish before displaying the Install Succeeded screen.  Sometimes, kextcache fails, and Installer.app catches it and fails the install.  Either way, stdout and stderr from kextcache are always in the install log.

Is your install finishing before kextcache finishes?

Thanks,
Andrew Keller




--
A false life is equal to death. Be your true self... like me !!!
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Rebuilding kext caches (From: Philip Petev <email@hidden>)
 >Re: Rebuilding kext caches (From: Andrew Keller <email@hidden>)

  • Prev by Date: Re: Rebuilding kext caches
  • Next by Date: RE: Verify productsign on flat packages
  • Previous by thread: Re: Rebuilding kext caches
  • Next by thread: RE: Verify productsign on flat packages
  • Index(es):
    • Date
    • Thread