jazzyguy wrote:Just out of Curiosity what kind of cache are you referring to? A System wide cache? An XLR Cache? A system Cache? What exactly are we dealing with?
First of all thanks for the heads up over at VersionTracker that there could be trouble with this update.
I don't have an account over there so I don't post there (although it is my home page in Safari), but we seem to have similar taste in software so I'm always seeing your reviews, I do trust your reviews and judgement, so thanks.
Because of your warning, I backed up and took some extra precautions before attempting to run this 3.5 update.
It has been so long since I've had a problem with a LS update (or any update for that matter), that I'm embarrassed to say I've that become a little blasé when running updates without backing up, so thanks again for the heads up.
You may be right that there is still something fundamentally wrong with the 3.5 version itself, but the problems I was encountering were very similar in nature to others I've encountered running Yosemite on an unsupported machine with an unsupported bootloader.
Starting in Mavericks with 10.9.5, and now fully implemented in Yosemite, are some new security features having to do with kernel extensions (such as LS installs) all of these seemed to get lumped under the single term of "kext signing".
This new security feature insures that not only are all kernel extensions (.kext files) from "identified developers" who have registered with Apple the only ones OSX will load, but there are now extra checks in place to insure that the extensions that are loaded on each boot match the cache of previous boots, so no malware extensions can be injected in the boot sequence without a users notice.
If there is any discrepancy between which extensions the OS is expecting to see loaded from the boot cache, and the actual extensions that are presently loading, then the boot process will halt, to keep the OS from further harming itself or your data.
This is similar to Microsoft's "Driver Signing Certification", which has been around for a while, and it is a very good thing as long as nothing gets corrupted.
Usually the symptoms of a kext signing problem are either a big grey "no entry" symbol (circle with a slash through it), if the error happens late enough in the boot sequence.
If the problem happens earlier in the boot up sequence, then the symptom is just a lockup in the new Yosemite grey/ black progress bar.
Hopefully my explanation makes a little sense, as I'm not too good at typing out what it is I'm actually trying to say.
All I know is that by getting Yosemite to run on my unsupported system, I've had to jump through all sort of hoops to satisfy this new security protocol.
It may not apply to your system, but if you are still having trouble installing 3.5, you have nothing to lose by trying my procedure,it couldn't hurt.
I may have been lucky, but I just thought I would pass my findings along.
Hopefully this helps somebody at least.