Separate names with a comma.
Discussion in 'macOS' started by macswitcha2, Mar 22, 2010.
I heard that someone gained lots of gbs back by doing this...
Removing hidden core dump files.
What does running as root means?
It means using "sudo" before the command or logging in as root via the login window or terminal, although sudo is the preferred method.
So in terminal, I type sudo and then what? The below?
"you'll need to run as root. You can access the /cores folder through the Go -> Go to folder... menu, and then type "/cores."'
What does this mean?
Ok, I think I get it...open up Terminals and type Suno and then type go and the folder, then files, etc, etc...
I'll play around with it a little...thanks guys.
From the sound of it, you should BACKUP your data first.
"I did this one thing, and now my Mac shows a folder with a "NO" sign" thread in 3...2....1....
OP, I suggest you Google for a basic introduction to using a command line in UNIX, you need to learn the basics of getting around first. After that, study up a bit about permissions and the sudo command. Blindly going in with no clue what you are doing is a good way to break your whole system. Then we will laugh at you and tell you to do an archive and install.
Let me be the first to say that running as root gives you absolute power over OSX and that means its quite easy to mess up your system. Especially when executing terminal commands. The addition of a simple flag to rm could render your system unbootable.
Why not use the console log app in osx to manage your logs, or applications such as onyx. If you don't know your way around the terminal, experimenting with root is a risky endeavor.
I would advise that the OP forget about trying to remove these core dump files. First, he doesn't know much about Unix, so he could screw things up royally. Also, if he needs space, then get an external drive or a new hard drive. I just don't see this ending well.