If you're using a third-party SSD, use this command at your own risk. So why did Apple enable this? Well, it looks like this is an early implementation of something we expected in El Capitan, but many newer third-party SSDs don't have any trouble with trim support and will benefit from it, so it's a net positive.Īgain, if you're using a Mac equipped with a factory-installed SSD or one that uses an SSD that has a SandForce controller, this doesn't apply. The problem is that not all SSDs implement trim support the same way, and some models from some manufacturers appear to have very buggy trim implementations all together. The operating system barks back a long and potentially scary message about how using trimforce may cause "unintended data loss or data corruption" before turning it on.
OS X 10.10.4's new "trimforce" command is entered through the Terminal: While kext signing is still Yosemite's law of the land, 10.10.4 introduces a new "trimforce" command that enables trim on SSDs. Unfortunately, this meant that utilities which altered the way SSD drivers work stopped working on Yosemite. Kext signing makes sure system drivers stay unaltered to prevent potential security problems. That went away with the release of Yosemite, which enforced a new security measure called "kext signing." Kernel extensions, or kexts, are system drivers. With Mavericks and previous OS X releases, some Mac users who had upgraded their computers with third-party SSDs used Trim Enabler and other tools to get trim support to work on their drives. Third-party SSDs equipped with SandForce controllers, like the ones sold by Other World Computing (OWC), don't need any help, either. First party SSDs do their own garbage collection, so no changes are necessary for those systems. If you bought your Mac with an SSD factory-installed by Apple, you don't have to worry.
0 kommentar(er)
