Recursion in Bash: share your opinion.

ehartman · 12-05-2019, 08:17 AM

Quote:

Originally Posted by wpeckham

Sonce the BASH scripts are identified as "Bourne-Again shell script" in my version, my identification of bash shells in a folder might look like

Code:

file /usr/bin/* | grep Bourne

Two remarks:
- Bourne-Again shell script will only be shown for scripts that have
#!/bin/bash
as their first line. Others may have POSIX shell script (/bin/sh or NO hashbang line), Korn shell script, Tenex C shell script or even Perl script and python script, depending ON that first line (or its lack) IN the script
- shell scripts (of any kind) can be located in the /usr/sbin, the /*bin and even the /usr/libexec directories too, not just in /usr/bin

wpeckham · 12-05-2019, 05:51 PM

Quote:

Originally Posted by ehartman

Two remarks:
- Bourne-Again shell script will only be shown for scripts that have
#!/bin/bash
as their first line. Others may have POSIX shell script (/bin/sh or NO hashbang line), Korn shell script, Tenex C shell script or even Perl script and python script, depending ON that first line (or its lack) IN the script
- shell scripts (of any kind) can be located in the /usr/sbin, the /*bin and even the /usr/libexec directories too, not just in /usr/bin

True, although the question I had in mind was specific to BASH scripts. If you wanted to find ALL scripts you could filter on "script" for those results.
There is nothing that limits scripts to those folders! Although one might expect that they would normally be in a folder somewhere in the default path, there is nothing to enforce such a restriction.

ondoho · 12-06-2019, 02:04 AM

Just pointing out that there's a whole lot of "professional" shell scripting going on on any Linux distro...

Checking $PATH is a quick way to show that.

Yes, to make it more complete one should probably start with

Code:

find /

Better:

Code:

for path in ${PATH//:/ }; do for i in $path/*; do file "$i"| grep -w shell; done; done | wc -l

and on my system that returns:

Code:

edit:
checking for explicit Bash scripts only is misleading because most scripts are marked '#!/bin/sh', yet the executing shell is often still bash.