geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: Startup Scripts discussion ( GERONIMO-693 )
Date Tue, 05 Jul 2005 03:46:22 GMT
David Blevins <> wrote on 05/07/2005 12:54:29 PM:

> On Mon, Jul 04, 2005 at 06:48:21PM -0700, Jeremy Boynes wrote:
> > wrote:
> > >toby cabot <> wrote on 05/07/2005 12:59:14 AM:
> > >>
> > >>I like the idea of using a well-known baseline for the Geronimo
> > >>scripts, but could we call the shell script "geronimo" instead of
> > >>""?  I prefer to not expose the implementation (shell
> > >>script) in the interface.
> > >
> > >
> > >Are you concerned that we may change shells in the future?
> > >
> > >The startup script should have the following on the first line 
> > >the system which shell interpreter we are using.
> > >#! /bin/sh
> > >
> > 
> > Not every version of Unix places the shell in the same place which can 

> > make this problematic.
> > 
> > #!/bin/sh should work for most, /provided to stick to sh/ and don't 
> > ksh or bash extensions (just in case you happen to get a genuine sh 
> > implementation).

So is anyone not ok with specifying #!/bin/sh ?  If someone is on an 
obscure platform where this doesn't work, then they can set up a link or 
edit the script.

AFAIK if we ensure that the scripts only use original Bourne shell (sh) 
functionality then they should be compatible with other shells that may be 
linked to bin/sh such as ksh and bash, as they implement the Bourne shell 
environment.  Does that sound right?  If so, I will include some comments 
in the script so that people who edit it in the future are less likely to 
break it.

> > 
> Right.  And just an reminder, Linux and OSX don't actually have sh on
> the machine, it's just bash symlinked (linux) or copied (osx).
> Something to remember when testing the script.
> -David

This e-mail message and any attachments may contain confidential, 
proprietary or non-public information.  This information is intended 
solely for the designated recipient(s).  If an addressing or transmission 
error has misdirected this e-mail, please notify the sender immediately 
and destroy this e-mail.  Any review, dissemination, use or reliance upon 
this information by unintended recipients is prohibited.  Any opinions 
expressed in this e-mail are those of the author personally.

View raw message