Code: Select all
sudo rmdir /tmp
sudo ln -s private/tmp /tmp
Code: Select all
sudo rmdir /tmp
sudo ln -s private/tmp /tmp
Code: Select all
$ ls -la /private/etc/sudoers
Code: Select all
-r--r----- 1 root wheel 1275 10 Feb 18:42 /private/etc/sudoers
Code: Select all
$ ls -lad / /private /private/etc
drwxr-xr-x 38 root wheel 1360 10 Feb 18:23 /
drwxr-xr-x@ 6 root wheel 204 20 Okt 09:34 /private
drwxr-xr-x 103 root wheel 3502 10 Feb 18:43 /private/etc
Code: Select all
ls -lad / /private /private/etc
drwxrwxr-t 38 root admin 1360 10 Feb 18:23 /
drwxr-xr-x@ 6 root wheel 204 20 Okt 09:34 /private
drwxr-xr-x 103 root wheel 3502 10 Feb 18:43 /private/etc
If you read that in a thread, it's the wrong advice. Do not start messing with your system's permissions or you'll create more problems. One thing that I'm looking at as we speak is the following line from your installation log:AndersD wrote:Even changed the group of / to "admin"... According to one of the threads.
Code: Select all
./postflight: /Library/Application Support/VirtualBox/VBoxDrv.kext failed to load - (libkern/kext) dependency resolution failure; check the system/kernel logs for errors or try kextutil(8).
It's always the last place you look.AndersD wrote:Yay!
I had success! I tried the "Reinstall OSX" without wiping the entire disk. After that I could get both VirtualBox and Parallels installed and all seems to work! It seems there was some error with OSX and/or permissions. My developer IDE however still doesn't work. But that's another issue. Thanks for all the encouraging help
It's much easier and faster to reinstall VirtualBox. Make sure to Uninstall it using the VirtualBox_Uninstall.tool first. If that doesn't work it would be time to think about re-instally OSX or doing a clean install of OSX.janpeter wrote:I have done both verify disk and repaired permissions from two different accounts
that both run VBox, but no look.
Do you think it is worthwhile to re-install VBox while keeping the VMs or it is rather
a re-installation of Mac OS X that is needed?