3 ms·
> Does booting an alternate OS still work to get around it, or have Apple thought of that route and somehow blocked it too? It's easier than that. It's just a
by __david__ 11y ago
> Does booting an alternate OS still work to get around it, or have Apple thought of that route and somehow blocked it too?
It's easier than that. It's just a kernel argument to disable it. Simply add "rootless=0" to your boot-args and you have control of your machine back.
I'm running the 10.11 beta and I've already had to disable rootless because I like to have /usr/local as a symlink to somewhere else and by default the rootless configuration prevents writes to /usr. :-/
- brobinson 11y agoDoes this break homebrew? Or does it only block writes to entries in /usr and not subdirectories like /usr/local ?
- __david__ 11y agoYou are allowed to write to /usr/local. But making /usr/local itself into a symlink requires writing to /usr which is prohibited. So I was screwed but for the normal case it should work fine.
- bdash 11y agoApple has stated that the "rootless=0" boot argument to disable System Integrity Protection is temporary and will be gone in the GM version of El Capitan. Allowing this route to disable the feature would defeat the entire purpose of it.
- mrpippy 11y agoSource? They said in the WWDC session (http://asciiwwdc.com/2015/sessions/706 http://asciiwwdc.com/2015/sessions/706) that the process to disable rootless may change during the beta, but didn't say that it won't be possible in the GM. They know that rootless will break some applications/drivers, plus some types of development may need it disabled.
- bdash 11y agoThe supported mechanism for disabling System Integrity Protection is via the recovery partition.
- arthurfm 11y agoApple have recently made a few changes to how you enable/disable System Integrity Protection... https://www.reddit.com/r/osx/comments/3hv3kk/update_on_rootless_the_configuration_mechanism/ https://www.reddit.com/r/osx/comments/3hv3kk/update_on_rootl...