Solved

Differences in chmod a+x between OSX 10.6 and 10.8?

Posted on 2013-06-20
5
525 Views
Last Modified: 2013-06-21
Hi,
If I run the following sequence on an OSX 10.6 machine:
chmod a+x filename
ls -l

Open in new window

the results of ls show the "filaname" in red and with an asterisk (*).  

If I do the same on an OSX 10.8 machine, it sets the +x permission but does not show red and asterisk.  



I am not sure if it really is significant, but I believe that it is affecting an XCode project I am working on, where I am triggering the file and receive a  "../devtools/bin/odfrc-cmd: Not a directory" error.

What am I missing?
0
Comment
Question by:TechBento
  • 3
  • 2
5 Comments
 
LVL 33

Accepted Solution

by:
pgnatyuk earned 300 total points
ID: 39265057
It's about the colors but not about the OS version.
Change the Appearance of Terminal Windows Quickly

A bit more complicated way:
How to Fix Colors on Mac OSX Terminal

You need to edit .bash_profile and add something like:
export CLICOLOR=1
export LSCOLORS=GxFxCxDxBxegedabagaced

(In Teminal type "nano .bash_profile"  to edit this file, Ctrl-O, Ctrl-X,... - to save changes, etc. )

You can find few color chemes in github, for example:
https://github.com/mbadolato/iTerm2-Color-Schemes
0
 
LVL 2

Author Comment

by:TechBento
ID: 39265503
I am familiar with that, but I don't believe that's entirely it.    Still does not address the lack of "*" at the end of the file name (which signifies executable) and the obvious error when I try to access the script from xCode.     I am convinced I have a shell script execution issue tied to security, and I think this behavior is a symptom of it.

Also, on the 10.6 machine, chmod +x causes the file to be "black" with no "*" while "chmod a+x" gives it the characteristics.
0
 
LVL 33

Expert Comment

by:pgnatyuk
ID: 39266193
chmod +x change the file attribute ('x' means eXecutable permission). That's all what it does.
chmod
0
 
LVL 2

Author Comment

by:TechBento
ID: 39266241
Mystery solved.. Sort of...

You were right about the colors, and the executable attribute is present.

ls -l was not the best command to use to confirm this;  "ls -F" indicates the "*" and confirms we're good there.  

This leaves me with the main problem: why on earth I can't run that file from xCode.  Oh well, closing this thread..
0
 
LVL 33

Expert Comment

by:pgnatyuk
ID: 39267526
If you are talking about the chmod, you can launch before or after the project building in Xcode.
0

Featured Post

Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
backup apps from mac 4 76
Firefox crashing on Mac 3 211
Unzip files in macOS Sierra - How? 4 122
MacBook Upgrade OS 6 17
Deploystudio is a system which can be used to deploy OSX clients and servers within the small/medium or large business environments. The system is built onto of the OSX Server NetBoot system and uses images & workflows as its core assets. While work…
Today, still in the boom of Apple, PC's and products, nearly 50% of the computer users use Windows as graphical operating systems. If you are among those users who love windows, but are grappling to keep the system's hard drive optimized, then you s…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …

830 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question