I did something very, very, VERY stupid.

W

Withstanding

Registered
You're going to laugh. I need someone to tell me just exactly how badly I've stuffed up.

chmod -R 777 /

It's a really long story. Are you done laughing yet? Anyway after spending about an hour figuring out how to get sudo working again, I'm piecing together the permissions of some kernel extensions trying to get some basic functionality back. :D

:x
 
:eek:

Have you tried booting from the installation disk and running "Repair Permissions" from its copy of Disk Utility? I think that ought to fix at least the system files. (Although I can't say I've ever tested it with such extensive permission damage.)
 
chevy said:
have your tried rm -fR *.* ?

(hem... DON'T DO IT.... !!!!)
Click to expand...

See, after my frantic jerry-rigging spree last night I know way better than that command.

Um, as far as Disk Permissions go, I was hoping there would be an easier way to do it but if I need a disk, meh.
 
i know what chmod 777 does, what is this one? why is bad? does it change every file on disk to read and write for everyone?
 
there are a lot of things that need specific permission settings to work properly (Also yes it changes every file on the disk to 777)

i.e. I found out that kernel extension files need to be 755 while every file inside them is 644. So I had to go into SUM again and fix sudo so i could use chmod.
 
Got out my install disk and repaired permissions.

Rebooted the MacBook and got an instant kernel panic "Cannot find driver for a platform: ACPI" (or something extremely similar)

Help :x The only tool I have left is Terminal (through install disk)
 
Withstanding said:
"Cannot find driver for a platform: ACPI"
Click to expand...

Thats an odd error. I'd try a "repair" of the HD followed by another repair of the permissions. May not help but can't hurt.

If that fails, the only other idea I have is reinstall just the OS. Don't blow everything away, let install do an upgrade.
 
As mentioned somewhere on another forum, I installed the 4.10 combopack through an external HD and it repaired the damaged system files.

Good to go! (Except at startup the system tells me that connectusb.kext, hypervisor.kext and pvsnet.kext are corrupt. Dunno.)
 
You must log in or register to reply here.
Back
Top