Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I've always done:

chown nimmylebby:admins file

I see that this also works:

chown nimmylebby.admins file

Might seem like a silly question but I'm genuinely curious on how the latter works. It isn't documented in my chown's manpage (GNU coreutils 8.4, 10/10). Is this perhaps a Bash interpretation? Or a deprecated format for the argument?

share|improve this question
add comment

2 Answers

up vote 14 down vote accepted

from the chown(8) manpage on macos x 10.6.4.

COMPATIBILITY
     Previous versions of the chown utility used the dot (``.'') character to distin-
     guish the group name.  This has been changed to be a colon (``:'') character, so
     that user and group names may contain the dot character.

Good question, I learned something today ;)

share|improve this answer
add comment

From info coreutils 'chown invocation' for GNU coreutils:

Some older scripts may still use '.' in place of the ':' separator. POSIX 1003.1-2001 (*note Standards conformance::) does not require support for that, but for backward compatibility GNU 'chown' supports '.' so long as no ambiguity results. New scripts should avoid the use of '.' because it is not portable, and because it has undesirable results if the entire OWNER'.'GROUP happens to identify a user whose name contains '.'.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.