Shebang Post: 302518344

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Shebang

Hi, I am currently writing BASH shell scripts. I am using BASH on a Powerbook G4 running Leopard. Could somebody please explain the difference between #!/bin/bash and #!/bin/sh? I have been using the latter (#!/bin/sh), and things have been working fine. But is that the correct one to use...

2. Shell Programming and Scripting

Doubt in shebang line!!

Do we need to include the exclamatory mark in the shebang line??:confused: What if we dont include it??:eek: Actually what shebang line implies when we run a script?? shebang line--> #!/bin/ksh :p

3. Shell Programming and Scripting

Relacing the shebang line of a file

Can any one tell me how to replace a shebang line of a file using sed? Eg: If a file contains the following shebang line #!C:/InstantRails/ruby/bin/ruby I would like to replace it with #!/usr/local/bin/ruby The shebang line of the file can be obtained from the command cat...

4. Shell Programming and Scripting

Multiple shebang lines

*** EDIT: I found something close to my solution under an IIS 7 Module Handle.***** (Non-Homework question, simply an ease of use one) Odd question here and maybe its my newness to cgi/Perl, but is it possible to have 2 shebang lines? I write an test a ton of my homework code on my windows...

5. Shell Programming and Scripting

The Shebang!

Hi, I always thought that #!/usr/bin/ksh means that the script would be executed in korn shell i.e. when we'll execute the script with this line as the very first line then the shell spawns a korn shell (in this case as we are using #!/usr/bin/ksh ) and the script gets executed. But I am...

6. Shell Programming and Scripting

Hyphen char after shebang notation

Hi, I have a trivial question to ask, I am seeing in some shell scripts the '-' (hyphen) character following the first line of shell script (i.e) the shebang notation as follows: #!/bin/sh - #! /bin/bash - what does the hyphen signify? What will happen if it is not given explicitly?

7. Shell Programming and Scripting

csh shebang query

What does the "-f" mean in following interpreter code #!/bin/csh -f Thank you

8. Shell Programming and Scripting

Necessity of shebang line

Hi , I know about the shebang line in shell scripting. Just want to know whether is there any difference in execution of the program by keeping and not keeping the shebang line. Because without shebang line also the script is working. correct me if am wrong. Any help on this will be helpful

9. Shell Programming and Scripting

Scripts without shebang

I see lot of ad-hoc shell scripts in our servers which don't have a shebang at the beginning . Does this mean that it will run on any shell ? Is it a good practice to create scripts (even ad-hoc ones) without shebang ?

LEARN ABOUT OPENSOLARIS

echo

echo(1B)					     SunOS/BSD Compatibility Package Commands						  echo(1B)

NAME

       echo - echo arguments to standard output

SYNOPSIS

       /usr/ucb/echo [-n] [argument]

DESCRIPTION

       echo writes its arguments, separated by BLANKs and terminated by a NEWLINE, to the standard output.

       echo  is useful for producing diagnostics in command files and for sending known data into a pipe, and for displaying the contents of envi-
       ronment variables.

       For example, you can use echo to determine how many subdirectories below the root directory (/) is your current directory, as follows:

	   o	  echo your current-working-directory's full pathname

	   o	  pipe the output through tr to translate the path's embedded slash-characters into space-characters

	   o	  pipe that output through wc -w for a count of the names in your path.

		    example% /usr/bin/echo "echo $PWD | tr '/' ' ' | wc -w"

       See tr(1) and wc(1) for their functionality.

       The shells csh(1), ksh(1), and sh(1), each have an echo built-in command, which, by default, will have precedence, and will be  invoked	if
       the  user  calls  echo without a full pathname. /usr/ucb/echo and csh's echo() have an -n option, but do not understand back-slashed escape
       characters. sh's echo(), ksh's echo(), and /usr/bin/echo, on the other hand, understand the  black-slashed  escape  characters,	and  ksh's
       echo() also understands a as the audible bell character; however, these commands do not have an -n option.

OPTIONS

       -n    Do not add the NEWLINE to the output.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWscpu			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       csh(1), echo(1), ksh(1), sh(1), tr(1), wc(1), attributes(5)

NOTES

       The -n option is a transition aid for BSD applications, and may not be supported in future  releases.

SunOS 5.11							    3 Aug 1994								  echo(1B)