On 01/04/2012 04:38 PM, Paul Allen Newell wrote: > [inline] > > On 1/4/2012 12:32 AM, Ed Greshko wrote: >> >> Well, I'm sorry you'd panic.... > > I wish I had qualified that statement with a "smile" ... please allow > me to edit prior comment.
OK.... :-) > > >> We'd just use the "file" command to find out what the intended use is >> and adhere to a standard of putting #!/bin/bash or whatever shell as the >> first line of a file... >> > > In my world, nobody wanted to have to run "file" as we believe the > intent of the file should be obvious on a "ls". We tried to never > parse on extension, it was just used as a clue to what the intent was > Well, we always will put the files/command (end product of compilation) in directories that tend to clue one in on the purpose. /bin /sbin /usr/bin, etc. And, we only put +x on the files that really need them. Hardly ever needing to use the "file" command to determine if the file is to be executed directly. Just our way of doing things. -- A common mistake that people make when trying to design something completely foolproof was to underestimate the ingenuity of complete fools. -- Douglas Adams in "Mostly Harmless -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
