Unable to change the user or group of files, dirs

Jun 26, 2008 4:02am

forward 2 post(s)

I’ve created a new vault successfully. But when I try to chown or chgrp files or directories inside the vault, it will silently fail.

I’m going to hazard a guess that it is due to how it’s mounted.
/dev/disk1s2 on /Volumes/rails (hfs, local, nodev, nosuid, noowners, mounted by me)

The noowners flag seems to be the culprit:

noowners: Ignore the ownership field for the entire volume. This causes all objects to appear as owned by user ID 99 and group ID 99. User ID 99 is interpreted as the current effective user ID, while group ID 99 is used directly and translates to ``unknown’’.
http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/mount.8.html

That’s as far as I got into the problem. Is there a way to mess around with how Knox mounts sparse images?

Jun 26, 2008 6:38am

Marko Karppinen Administrator 67 post(s)

Your diagnosis is the right one. Unfortunately we don’t have a flag you could set for this at the moment, so your only choice would be to mount the vault manually with “hdiutil attach vault.sparseimage -owners on”.

Jul 11, 2008 1:53am

forward 2 post(s)

Sorry for the late reply. I thought “Monitoring topic” would notify me by email.

The manual way worked like a charm, thanks. Out of curiosity, is “-owners on” up for consideration for inclusion into the GUI in the near future?

MK&C Forum

Unable to change the user or group of files, dirs

Voices

Jun 26, 2008 4:02am forward 2 post(s)	I’ve created a new vault successfully. But when I try to chown or chgrp files or directories inside the vault, it will silently fail. I’m going to hazard a guess that it is due to how it’s mounted. /dev/disk1s2 on /Volumes/rails (hfs, local, nodev, nosuid, noowners, mounted by me) The noowners flag seems to be the culprit: noowners: Ignore the ownership field for the entire volume. This causes all objects to appear as owned by user ID 99 and group ID 99. User ID 99 is interpreted as the current effective user ID, while group ID 99 is used directly and translates to ``unknown’’. http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/mount.8.html That’s as far as I got into the problem. Is there a way to mess around with how Knox mounts sparse images?

Jun 26, 2008 6:38am Marko Karppinen Administrator 67 post(s)	Your diagnosis is the right one. Unfortunately we don’t have a flag you could set for this at the moment, so your only choice would be to mount the vault manually with “hdiutil attach vault.sparseimage -owners on”.

Jul 11, 2008 1:53am forward 2 post(s)	Sorry for the late reply. I thought “Monitoring topic” would notify me by email. The manual way worked like a charm, thanks. Out of curiosity, is “-owners on” up for consideration for inclusion into the GUI in the near future?