While trying to build the NumPy Python math module with Intel's Math Kernel Library (MKL) on OSX 10.8.3, I was running into some problems with the Accelerate and vecLib frameworks overriding the MKL. At any rate, I decided it would be a good idea to rename /System/Library/Frameworks/Accelerate.framework and /System/Library/Frameworks/vecLib.framework temporarily. Nothing happened (at least, on the command line) after moving Accelerate.framework. However, after entering

sudo mv vecLib.framework/ vecLib.framework.old

I got the following error:

sudo: unable to initialize PAM: No such file or directory

Oops. Unfortunately, the mv command worked, but now when I try to use sudo I get the same error, but the commands don't work. When I tried to rename vecLib through Finder, I get:

The operation can’t be completed.
An unexpected error occurred (error code -8076).

which apparently is some sort of permissions error.

So, my question is how can I get sudo working again? App Store.app won't even run, so I can't reinstall XCode (which is apparently where vecLib.framework comes from) or anything else. I'm afraid to reboot because I'm worried the computer will hang, whereas (as you can tell) at least it's working for now, albeit without any elevated permissions capabilities.

Any suggestions?

Normally I wouldn't cross-post, but I need to figure out a way to fix this ASAP.

  • Please: where is it indicated that -8076 relates to permissions? For me today, error -8076 occurred when attempting to rename a file or folder that was already renamed – when Finder had not yet shown the result of the first successful attempt to rename. – Graham Perrin Jan 18 '14 at 9:12
  • I ran into the same problem when I attempted to replace /usr/lib/libsqlite3.dylib with my own copy. Apparently, this sqlite3 library is also used by other system program(s) and OS/X is not happy about not finding it. The solution from @MattDMo works great and allows me to restore the original sqlite3 library – Tzunghsing David Wong Feb 19 '16 at 2:10

With OSX you can boot into single-user mode by holding down Command-S after rebooting. You essentially have password-less root access to the system, with no PAM or other authentication, so you can fix all sorts of system issues like lost passwords and accidental directory renames this way.

Yes, this is a potential security hole, but giving someone physical access to your machine is a security hole itself. It can be disable/password-protected if you want, and if you're really worried you can always encrypt your volumes so an intruder couldn't read your files even if they got this far.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.