After reinstalling, I still get an error when I try to turn Rootless off. My computer is crippled.
sudo nvram boot-args="rootless=0"
sudo nvram boot-args="rootless 0"
I don't think it will be an issue. Those who dabble can disable it and those who don't can leave it on. If Apple ever revokes the ability to disable it, I think they'll see a mass exodus to Linux. Though I'd still buy their laptops... I just wouldn't run their OS or ecosystem.I guess in theory its a nice to have feature and we need to further protect the system files, but I wonder if it will get in the way for us who like to dabble.
I understand it can be disabled - for now. The time may come where apple will remove that option from OS X.
Even if apple locks down OS X to the degree that iOS is locked down, you'll not see a mass exodus to Linux. Linux has its place and its fans. I don't see it being a viable alternative to OS X regardless of what apple does.think they'll see a mass exodus to Linux
Agreed, but could go over to win 10. Hopefully Apple won't go to far with this. We have managed just fine without rootless, and I'm sure we will be just fine with it disabled as long as there is a way.Even if apple locks down OS X to the degree that iOS is locked down, you'll not see a mass exodus to Linux. Linux has its place and its fans. I don't see it being a viable alternative to OS X regardless of what apple does.
An operating system's job is to run apps and there is a huge night and day difference of what you can run on OS X and linux. Even the dabblers as I called them would mostly stick with OS X.
Agreed, but could go over to win 10. Hopefully Apple won't go to far with this. We have managed just fine without rootless, and I'm sure we will be just fine with it disabled as long as there is a way.
It does have it.Since OS X did get the rootless feature, is it safe to assume that iOS 9 has it implemented as well?
I work in CS/QA, I know all of the horror stories of users who have done stuff they shouldn't be doing in the first place such as installing hax that modifies Finder, theme mods, and so on. The systems were just horrible and everything was just unstable. Once everything is cleanly installed and the users were told not to do these "tools" anymore, they were actually happier in the end with no issues.
This is the point of rootless, prevent the general public from installing tools that modifies the system files.
I would be okay with Apple disabling the option to disable rootless, I can almost guarantee it will not lose a noticeable amount of customers. People who need this, are most likely already dabbling with Linux or even using Windows on a separate partition or VM.
If anything, Apple will add more APIs in the end to allow certain devs do what they need to provide the same tool. For an example, Finder Extensions that allowed Dropbox to offer its integration in Finder without injecting itself. That API actually improved the overall experience for the Dropbox users in the end. In fact, Apple already offer an option for some devs to migrate their service in a way that disables rootless already.
The privacy and security session goes into more details - when you hear about what it does and how developers are meant to use best practice then for most people outside of people who tinker, it will actually be business as usual.
The Apple Dev post quoted in that also says there will be a CLI tool to disable it when booted into recovery mode.Just read this in another thread. If accurate, El Capitan is going to be locked down. No more tinkering.
https://forums.macrumors.com/threads/el-capitan-and-trim-support.1890467/page-3#post-21447703
Thanks for pointing that out. I had missed that important part.The Apple Dev post quoted in that also says there will be a CLI tool to disable it when booted into recovery mode.
It's on my list to watch, just waiting for Apple to post it.
My follow-up question is "why does an NVRAM argument show up in Disk Utility in the first place?"The question is asking if rootless still shows as enabled in Disk Utility. The answer is yes, even after a restart with rootless disabled.
Here is the security video: https://developer.apple.com/videos/wwdc/2015/?id=706
Listed and available - doesn't go into much detail regarding rootless mode but from the information provided, as long as you use the correct directories as a developer then there shouldn't be any problems.
You can still modify any files stored on Mac partition from other systems, such as Windows. However you may need a third party software to enable access to that partition.After reinstalling, I still get an error when I try to turn Rootless off. My computer is crippled.
You can still modify any files stored on Mac partition from other systems, such as Windows. However you may need a third party software to enable access to that partition.
However if Apple implement system integrity check and prevent from booting up once detected unauthorised system file change, this could be another problem, for advanced users. (Such as hackers)Yeah, my thinking too. Boot Linux, make change, boot OS X.
However if Apple implement system integrity check and prevent from booting up once detected unauthorised system file change, this could be another problem, for advanced users. (Such as hackers)
Yeah.No argument there, we'll just have wait and see.
It's not a deal breaker for me, I'm booting an Apple/Samsung SSD blade, so I'm good either way.