On my system I have three partitions: one is shared between W7 and Linux Mint (NTFS), and the other two are OS-specific.
In my home directory I have created a symbolic link to another directory on the shared partition.
I have a simple .cpp file there which I compiled via g++ name.cpp. Usually, this would also make the file executable, but this time I had to manually chmod 755 it.
Strangely, this didn't work either, the console said it did not have the required permission. So I executed sudo chmod 755 a.out. This asked me for my password, and reported no errors. However, it had no effect. a.out was not executable. I've noticed some other strange behaviors in symlink directories too.
Whats going on and how can I fix it?
Edit:
My mount options:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda6 during installation
UUID=7c50dab1-730b-4d3c-a944-51da19c8e2c6 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda7 during installation
UUID=12e39b76-7f19-4c6d-a724-81ea29211db1 none swap sw 0 0
/dev/sda5 /media/yannbane/Shared ntfs defaults,fmask=117,dmask=007,gid=46 0 0
mountcommand options or in your/etc/fstab. – Leonid Jan 20 at 16:32