virtualbox.org

Speaking of tiring…

origin1tech wrote:This endless attempt to pin a problem on a user is tiring...

Quit defaulting to "it's your fault" mentality. It helps no one.

How to Verify & Repair Permissions in OS X El Capitan

I see where I went wrong. I installed OSX 10.11.1 in two more Macs. Then installed VB 5.0.10 in each along with the extension packs without a problem. Then to be sure, I purposely changed the permissions for /Applications then ran the verify and repair terminal commands mentioned above which changed them back.

Just to be extra, extra thorough, I installed VB 5.0.10 in an OSX 10.11.1 VM without a problem.

The logical conclusion is obvious. I have magical Macs and magical copies of VirtualBox. I'm not sure why I doubted origin1tech.

You're pretty dense.

Please repair your Applications folder with SIP enabled and get back to me thx. for playing. It doesn't work per Apple.

Actually that's not what Apple says. SIP is to hopefully prevent unwanted permission changes and to be self-repairing with updates. Yours changed in case you forgot.

Where did I say I ever disabled SIP?

Did you or did you not just post a link showing incorrect information for updating the Applications folder? Following that link will get you no where when dealing with System monitored dirs. Period no exceptions. Not sure why you keep posting or referring to it.

It won't work no matter how many times you say or post the same thing.

Secondly based on your statement and the fact that you've now been enlighten/brought into the know that System folders cannot be repaired without disabling SIP, how in the world were they changed in the first place? You just conceded that this is the purpose of SIP. Namely preventing this. How was it circumvented then?

I'm glad all the worlds aligned for you in your upgrade, however this brand new 4500.00 Mac Pro from the factory didn't. I don't care why.

For those reading this thread in the future don't waste your time go to the 5 or 6 steps I listed on the 1st page, you'll be good end of story.

FWIW, seeing there is so far only one report by one user who no doubt disabled SIP himself, changed permissions himself, essentially breaking his own computer, I wouldn't pay much attention to his posts.