Forums | MacLife
You are not logged in.
#1 2006-10-27 6:24 pm
- redbeard
- Member
- Registered: 2006-10-27
- Posts: 5
Locked myself out of OS X
Hi,
I've been a silly boy. I had my iBook hooked up to a network connection, and changed the permissions for the HD to protect my computer.
I've rebooted but I'm in Darwin / BSD.
It's accepted my login details but how do I get back to OS X, and how do I prevent this happening next time?
Offline
#2 2006-10-27 7:58 pm
- test
- Member
- From: Collingwood, Ont., CANADA
- Registered: 2002-12-13
- Posts: 5300
Re: Locked myself out of OS X
You could try sudo diskutil repairPermissions /. This does the same thing as repairing permissions with Disk Utility but without the GUI.
Last edited by test (2006-10-27 7:58 pm)
Patience is a virtue of the weak for it makes them stand still long enough for the strong to crush them with ease.
Offline
#3 2006-10-27 8:12 pm
- redbeard
- Member
- Registered: 2006-10-27
- Posts: 5
Re: Locked myself out of OS X
I've just tried that, but it's eventually gone back to the command prompt
What I'm seeing is:
MarksComputer:_ markp$
Offline
#4 2006-10-27 10:04 pm
Re: Locked myself out of OS X
After you repair the permissions, try rebooting. Also, you can boot from the install disk, then start Disk Utility from the menu, and repair permissions from there.
To prevent this from happening next time: make sure there isn't a next time!
Offline
#5 2007-01-17 11:40 pm
- ElectricSheep
- Member
- Registered: 2003-07-20
- Posts: 109
Re: Locked myself out of OS X
You should rarely, if ever, have to alter permissions outside of your home directory. Trying it without knowing exactly what you are doing can leave your system unbootable.
If you are looking to secure your computer when on a network, permissions aren't the first place to start. You should focus instead on packet filtering (firewalling) and authentication.
Offline
#6 2007-01-19 9:57 am
- reepicheep
- Member
- Registered: 2006-12-22
- Posts: 23
Re: Locked myself out of OS X
chmod -R 755 / in single user is a quick and dirty hack. I suggest you follow the above advice and try to repair the permissions first. You can do it from your install disk.
Last edited by reepicheep (2007-01-19 9:59 am)
Offline
