mach_kernel

HI Paul,

Go here and read: http://support.apple.com/kb/TS1892

It is important, do not delete it.




Carolyn 🙂

In fact it should not be visible. Are there any other items listed such as "var" or "etc"? If so then something went slightly amiss during the update. It won't affect you in any way, but these items should be invisible.

See Apple - Support - Discussions - Invisible files become visible for ways to restore invisibility.

Go right ahead and make it hidden again. What you are seeing is just a file that is part of the underlying unix-like structure that OS X is built upon.

I'm not certain why after updates, the file seems to pop up, unless it's some backup or copy left over from the update.

HI Kappy,

I see what you did... never mind.




Carolyn 🙂

LOL.

Delete it. Then blame Apple if you have issues :-/

Why don't you just tell the guy how to recursively trash his whole system for gallows humor?

doug pennington wrote:
Why don't you just tell the guy how to recursively trash his whole system for gallows humor?

Clearly you completely misunderstood the post to which you are responding.
The response was not to the OP but to Kappy.
Measure twice; cut once, my grandpappy always said.

Hmmm, I don't know why that happened. Let's try it again and see if I get it right this time:

Mac OS X 10.5 Help- Recovering items using Time Machine and Spotlight.webloc.

Message was edited by: Kappy

The response by Lloyd was directed to Paul Monaco is what I see.

Well, this isn't working right either, so here's the URL plain:

http://discussions.apple.com/thread.jspa?messageID=6811003&#6811003

Now I'm confused.

There are several ways to make the file invisible. But we have to know which way to proceed.
First, in a terminal, enter the following command (we are only looking, not doing anything yet)
ls -al@ /
and then copy the line ending with
mach_kernel
which should read something like this:
-rw-r--r--@ 1 root wheel 10318880 Nov 24 20:39 mach_kernel

and copy the line below it if it exists. It will start with

com.apple.FinderInfo

and may have a number after it.

Once we see what the file descriptors are we can move on and fix it.
Most likely a simple
chmod
will suffice.

Message was edited by: nerowolfe

Visit the link I provided. I apologize that the original post somehow got messed up, but the one with the plain URL seems to work. Click on it and follow the instructions.