-
All replies
-
Helpful answers
-
Oct 13, 2013 8:50 AM in response to thomas_r.by AstroMacMan,Thomas, thank you! I had the very same issue as the original poster-- the sudden appearance of the "mach_kernel" file at the root level.
It just may have appeared after a recent update, although with all that one does with a computer--it takes time before seeing that part of the file structure again.
I'm glad I checked here. I have from time to time gotten sys logs or sys info or other things that suddenly appear and have simply trashed them. Glad I didn't do that this time!
Your tip took care of things! Thanks!
-
Oct 13, 2013 12:12 PM in response to Kurt Langby tigger07,thank you so much kurt for saving me! i really appreciate your help and feedback. i did what you said: put the mach file back on the root drive authenticated and repaired permissions. everything seems to be working normally, but i still can't hide the mach_kernel file. i've unhidden everything again and it still shows up there hidden or not. i have noticed the files that are normally hidden are greyed out, but the mach_kernel file is not greyed out. i'm guessing that's why it's not hidden when i hide the files. ??? i tried sabatica's trick again, but to no avail. it will not hide. i even tried restarting my computer and still the same. i guess i should just leave it alone and let it remain visible? thanks in advance for the advice!
-
-
Oct 13, 2013 2:03 PM in response to tigger07by Kurt Lang,A bug in the 10.8.5 update changed a flag on the kernel file. Enter this in Terminal:
sudo chflags hidden /mach_kernel
It will then ask for your admin password to complete the command. After that, the kernel should be hidden.
-
Oct 13, 2013 2:10 PM in response to thomas_r.by nbar,Mine is visible as well since the supplemental update (though I didn't notice since I set finder to show hidden files/folders). Just changed the flags. Odd.
Just submitted a bug report.
Message was edited by: nbar
-
Oct 13, 2013 2:43 PM in response to Kurt Langby Elaine Morrison,Do you really have to repair permissions and all that stuff? I just hid it with 1 line as per Thomas. It's an admin file anyway, if I recall its permissions.
-
Oct 13, 2013 3:02 PM in response to thomas_r.by Krazykreatives,Works on mine! 10.8.5 MBPR Thanx a bunch!!!
This never happened before and I was gonna delete it. The system asked for a password and I thought I should have googled this before anything unreversable happened.
Thanx! Thamas
-
-
Oct 13, 2013 2:58 PM in response to Elaine Morrisonby Kurt Lang,Do you really have to repair permissions and all that stuff?
Not if you didn't move the file, as tigger07 did when he put it in the trash. As soon as he did that (and needed to enter his admin password to move the file), the file ownership permissions would have been changed to 501 (the user), rather than 0 (the OS).
-
-
Oct 13, 2013 10:31 PM in response to hurgaaAby EvanG123,Thank you for sharing this. I too saw the file appear as soon as updating to 10.8.5. This came along with a host of other serious issues including external drives being randomly disconnected with out being "properly ejected."
-
Oct 14, 2013 5:57 PM in response to Aurora1967by mark1179,I just noticed this file today. Since it said kernel I said I better google it. Trying to hide the file through usual means didnt work for me. The only thing that worked was the sudo command mentioned above by Kurt. Thanks for the tip.
-
Oct 17, 2013 6:21 AM in response to Kurt Langby Sazza,I also have the mach_kernel file showing in my Macintosh HD folder, in between Library and System.
But presumably Apple will correct the error in showing this normally hidden file in their next update?
Just thinking best if I don't do anything, unless it's in the wrong place.
Sarah
-
Oct 17, 2013 6:54 AM in response to Sazzaby Kurt Lang,It's actually a very simple error. Apple updated the kernel, but the script didn't set the hidden flag back on. Since it's not set as a hidden file, it will stay visible even if the system is correctly set to hide invisible items.
All you have to do is run the command I noted above to reset the flag where it should be.
You can leave it if you want. It doesn't hurt or change anything for it to be visible. You just have to remember to leave it alone.
-
Oct 17, 2013 1:03 PM in response to Aurora1967by istrico,Same issue here, to the date as well. I also noticed an "installer log file."