**wilkie (quilt appreciator)** @wilkie@mastodon.social · Oct 03, 2019, 22:54

**wilkie (quilt appreciator)** @wilkie@mastodon.social · Oct 03, 2019, 22:54

can you name and run an executable that's just <newline>?

Yes

**vilkoz** @vilkoz@computerfairi.es · 2019-10-03T23:15:47Z

vilkoz @vilkoz@computerfairi.es

@wilkie how your "script" was interperted with bash you have no shebang in that script?

**wilkie (quilt appreciator)** @wilkie@mastodon.social · Oct 03, 2019, 23:19

**wilkie (quilt appreciator)** @wilkie@mastodon.social · Oct 03, 2019, 23:19

@vilkoz it uses /bin/sh by default

**vilkoz** @vilkoz@computerfairi.es · Oct 03, 2019, 23:21

**vilkoz** @vilkoz@computerfairi.es · Oct 03, 2019, 23:21

vilkoz @vilkoz@computerfairi.es

@wilkie my shell doesn't do that (

**vilkoz** @vilkoz@computerfairi.es · Oct 03, 2019, 23:22

**vilkoz** @vilkoz@computerfairi.es · Oct 03, 2019, 23:22

vilkoz @vilkoz@computerfairi.es

@wilkie oh, I see it is default for bash to run unknown executable with /bin/sh

**wilkie (quilt appreciator)** @wilkie@mastodon.social · Oct 03, 2019, 23:23

**wilkie (quilt appreciator)** @wilkie@mastodon.social · Oct 03, 2019, 23:23

@vilkoz it's default for POSIX. it should do that in every posix shell. (Bash's default is actually a non-standard /bin/bash, iirc)