Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

SOLVED: Turns out at one point while trying to copy files over to the thumb drive it must not have been mounted by OS X, and since I was root, it made the same mount point directory and copied into this "ghost" local disk. i.e. if you're trying to copy files to /Volumes/FOOBAR but the drive FOOBAR isn't mounted you'll create a FOOBAR dir in /Volumes/ and when you do mount the FOOBAR disk, it mounts at /Volumes/FOOBAR 1 (yes, with a one)

So I was changing the permissions of the wrong files and didn't know any better!

---------------------------------------------------------------------------------------

I've got a USB thumb drive with a raw XNU installation and some where along the way certain kexts in Extensions got permission: 501:wheel instead of root:wheel.

501 is my user account on my iMac, which I created the files on. Now if I plug in the thumb drive on my Mac, chown -R root:wheel Extensions/ it claims to have worked. Using ls -l all of the kext list as root:wheel.

But if I boot up XNU on the thumb drive and ls -l the stubborn files still show 501:wheel and I'm unable to change them even as root, getting "chmod: Unable to change file mode on System.kext/: Read-only file system"

No amount of changing permissions (777) helps.

I'm hoping this is just something stupid I'm missing...But why does my iMac show root:wheel when XNU itself on the thumb drive shows 501:wheel?

Ideas?

share|improve this question
1  
What filesystem? – Ignacio Vazquez-Abrams Nov 5 '10 at 5:37
    
Filesystem is HFS+ – Jay Nov 5 '10 at 6:54

Turns out at one point while trying to copy files over to the thumb drive it must not have been mounted by OS X, and since I was root, it made the same mount point directory and copied into this "ghost" local disk. i.e. if you're trying to copy files to /Volumes/FOOBAR but the drive FOOBAR isn't mounted you'll create a FOOBAR dir in /Volumes/ and when you do mount the FOOBAR disk, it mounts at /Volumes/FOOBAR 1 (yes, with a one)

So I was changing the permissions of the wrong files and didn't know any better!

share|improve this answer
    
Since this is solved, you should accept your own answer (this takes it off the list of questions needing attention). Thanks. – Ben Voigt Feb 19 '11 at 20:18

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .