![]() ![]() I would be interested in feedback from others, if you could verify that /S/L/C/boot.efi is protected on your systems at 10.11.2?įollow these instructions if you have just installed El Capitan, or are already using El Capitan and want automatically put the modifications in place during updates. I'm still investigating, all the mods seem to be in place, so I'm wondering if that efi file is now "hard coded" into SIP in some way. The bad news, it looks to me like the /S/L/C/boot.efi file is still protected by SIP in 10.11.2. ![]() Booted okay ( Boot64 did its thing a second time ).Upgraded to 10.11.1 using the Apple DMG from Support Downloads.Booted okay into the new disk ( pikify did its thing ).Created an installer using pikif圓.1.v5. ![]() I will upload new versions later, pikif圓.1.v5 and Boot64.v2. I have adapted both pikif圓.1 and Boot64 to take care of the boot.efi files and the paths file. Maybe I could adapt my Boot64 tools to take care of that too. My mistake sorry.īut it did get me to thinking. It needed to be re-edited because 10.11.1 overwrites it with the Apple version. I forgot to re-edit the paths file after the 10.11.1 update. I have realised that I overlooked a step before I ran the 10.11.2 update. I'll go check in the morning.Įither way it looks like there's currently a need to boot from another partition after each update to either replace the boot.efi files manually, or to re-edit the path file! It's probably because I hadn't edited the path file after updating to 10.11.1. Switching over.Ĭp: /System/Library/CoreServices/boot.efi: Operation not permittedĬp: /usr/standalone/i386/boot.efi: Operation not permitted Dec 8 23:53:07 admins-Mac-Pro.local ensureBoot.sh: Not using the grey boot.efi. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |