A little script of mine on a mounted windows partition refuses to be executed directly (shebang is #!/bin/bash), but interestingly calling it with sh works. The script is simply a collection of grep and sed commands.

The drive is mounted with full rights:

defaults,windows_names,rw,auto,user

Hence, for the the file got

-rwxrwxrwx 1 root root

for the file.

What's going on there?

A little script of mine on a mounted windows partition refuses to be executed directly (shebang is #!/bin/bash), but interestingly calling it with bash/sh works. The script is simply a collection of grep and sed commands.

The drive is mounted with full rights:

defaults,windows_names,rw,auto,user

Hence, for the the file got

-rwxrwxrwx 1 root root

for the file.

What's going on there?

A little script of mine on a mounted windows partition refuses to be executed directly (shebang is #!/bin/bash), but interestingly calling it with sh works. The script is simply a collection of grep and sed commands.

The drive is mounted with full rights. Hence, I got

-rwxrwxrwx 1 root root

for the file.

What's going on there?

A little script of mine on a mounted windows partition refuses to be executed directly (shebang is #!/bin/bash), but interestingly calling it with sh works. The script is simply a collection of grep and sed commands.

The drive is mounted with full rights:

defaults,windows_names,rw,auto,user

Hence, for the the file got

-rwxrwxrwx 1 root root

for the file.

What's going on there?