mach_kernel now visible
I recently upgraded to 10.7.3 on my Macbook Pro late 2008.
Now there is a file called mach_kernel which visible on the hard drive.
Why is it there? What is it?
How can I get rid of it or make it invisible?
Thanks
I recently upgraded to 10.7.3 on my Macbook Pro late 2008.
Now there is a file called mach_kernel which visible on the hard drive.
Why is it there? What is it?
How can I get rid of it or make it invisible?
Thanks
You're not the first who has noticed this.
That file is supposed to be invisible by default. Don't touch it though, it's supposed to be there.
Could you do me a favour, run file permissions and see what else could be amiss?
Below find a thread discussing this problem.
I had no reason to use this solution.
But baltwo is an expert on these kinds of issues. Credit to him.
https://discussions.apple.com/thread/3430762?start=0&tstart=0
Be careful an follow the instructions.
Best.
Ran Veriphy and Repair Permissions....
Lots of permissions differed and were repaired.
A few files couldn't be repaired (see below).
Warning: SUID file “usr/bin/ipcs” has been modified and will not be repaired.
Warning: SUID file “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent” has been modified and will not be repaired.
Warning: SUID file “System/Library/Printers/IOMs/LPRIOM.plugin/Contents/MacOS/LPRIOMHelper” has been modified and will not be repaired.
Warning: SUID file “usr/lib/sa/sadc” has been modified and will not be repaired.
Warning: SUID file “System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/readconf ig” has been modified and will not be repaired.
Warning: SUID file “System/Library/PrivateFrameworks/Install.framework/Versions/A/Resources/runner ” has been modified and will not be repaired.
Warning: SUID file “usr/libexec/authopen” has been modified and will not be repaired.
thanks.
When I cut/paste chflags hidden /mach_kernel into the command line it says permission denied..
Hi Atul,
You've got to run this as sudo chflags hidden /mach_kernel
Then it works fine.
Andy
It worx:)
Andy Espo wrote:
Hi Atul,
You've got to run this as sudo chflags hidden /mach_kernel
Then it works fine.
Andy
Thank you Andy, you rock!
I tried the above method and got "No such file or directory" ?
Thanks
Is it me or does this seem like a sloppy programming mistake? OSX is starting to feel very PC-isk with random files junking up a usually clean directory
Just sayin'...
nataraja7 wrote:
I tried the above method and got "No such file or directory" ?
That implies you didn't copy and paste in the command and made a mistake. Do it again.
I've noticed the same. It is all over the place, I used to never have any issues with anything. Now it is starting to be scary in its similarieties to weird problems.
Same with iOS 7, it rendered my phone completely useless. Everything takes so much time I am loosing productivity. Before I was secure enough to walk and email business emails, the lagg I am experiencing with iOS 7 has made me worry. No trust in an OS makes for less productivity.
Same with OS X. There seems to be no way to completely clean install your OS. Once you've migrated to a new Mac all the problems from your old one come with it. I went to an Apple service point and asked if I could get a complete clean install. Was told that it cannot be done. So here I am.
I seriously hope this is just som hick-up where the organization is adapting to a life without Steve. But for gods sake stop making stupid mistakes, go back to perfectionism. I'd rather wait a year longer to have something that works.
I will be passing on buying the new iPhone 5s and a new MacBook Pro this year to see where it is heading. Worst comes to worst I'll have to sit with an Android phone and a Linux computer. Both options that I don't want to resort to.
On Topic: Yes I also see this mach_kernel file and I really would like to know why.
Because an engineer failed to add the chflags item to the intallation script. To hide it, run the command and get on with your life.
sudo chflags hidden /mach_kernel
How do you "run" this thing called sudo chflags hidden /mach_kernel?
mach_kernel now visible