1
I wanted to install certain software. The package had lots of files including some shell scripting files. Initially I had to select some files and then make it executable:
chmod 777 shellscr1
but then I realized that there are many such files which I will have to make executable. So as a shortcut, I did this:
chmod 777 *
and now all the files are executable.
Are there any serious consequences of doing this (apart from security)?
That answer is going to confuse the Hell out of people. It gives the erroneous impression that there's one standard
/bin/sh
and a lot of non-standard/bin/sh
s. It also gives the wrong impression that someone nowadays using#!/bin/sh
is intending a specific shell, a notion that went away in the 1980s-1990s when (POSIX) operating systems that didn't and couldn't have the non-free Bourne shell came about. There's a way of reading that answer as written such that it's right, but it's not the way that people who don't already know the right answer are going to read it. – JdeBP – 2014-01-18T11:19:36.497