If I try to set this option for a file on an external drive it just unmarks itself. Doing chmod +x
has no effect. The drive is mounted with default options.
If I try to set this option for a file on an external drive it just unmarks itself. Doing chmod +x
has no effect. The drive is mounted with default options.
Your external disk is likely formatted NTFS or FAT32. Those filesystems do no support Linux file permissions.
You've now at least five options:
ext4
filesystem. This can be done using the Disk Utility or GPartedbash /path/to/your/file.sh
python /path/to/your/file.py
perl /path/to/your/file.pl
wine /path/to/your/file.exe
/lib/ld-linux.so.2 /path/to/your/file
/lib/ld-linux-x86-64.so.2 /path/to/your/file
(possibly dangerous) Mount the partition with the execute bit set for all files. To do so, follow these instructions:
Open a terminal and run:
If you cannot write / access files, run the command with
,uid=$(id -u)
afterfmask=022
:"Possibly dangerous" because you grant execute permissions to all files, only use this option if the other methods do not work.
If the filesystem is formatted as FAT or NTFS, you could always mount it with appropriate permissions. The default permissions when you mount from command line include execution permissions for all users.
To obtain more specific results, see the manual pages of
mount.ntfs-3g
andmount
, the latter in the section Mount options for fat, in particular take a look at optionsuid
,gid
,umask
,fmask
,dmask
,Ubuntu 10.04 had no problem setting permissions to run programs or read/write on external drives.
It's an enduring trait for me that makes it the best version to ever run on a USB.
Whatever was taken away to stop this - and it's poor default wireless connectivity - is what makes 10.10 and beyond such a mess of frustration.
Fixing stuff like this should not be the job of the user. If mobile execution is a must, use 10.04.