[BusyBox] [patch] ash problem with shell scripts (repost)

tom at ceisystems.com tom at ceisystems.com
Sat Sep 13 17:47:35 UTC 2003


Aren't you supposed to "source" a script that doesn't have "#!/bin/sh"
as the first line?  I've always done that, as it seems to be the
standard in every script I've seen.  So, out of curiosity, why can't you
have that on your first line, or source the script?

Good Luck,
Thomas Cameron
CEI Systems


-----Original Message-----
From: Glenn McGrath [mailto:bug1 at optushome.com.au] 
Sent: Friday, September 12, 2003 8:38 PM
To: Jean Wolter
Cc: busybox at busybox.net
Subject: Re: [BusyBox] [patch] ash problem with shell scripts (repost)


On 12 Sep 2003 14:37:39 +0200
Jean Wolter <jw5 at os.inf.tu-dresden.de> wrote:

> Glenn McGrath <bug1 at optushome.com.au> writes:
> 
> > On 12 Sep 2003 10:25:05 +0200
> > Jean Wolter <jw5 at os.inf.tu-dresden.de> wrote:
> > 
> > > ash is unable to execute a shell script without #! /bin/sh as the 
> > > first line, if the script can be found via $PATH, but isn't in the

> > > current working directory.
> > 
> > It seems to be working for me, you sure it hasnt been fixed it ?

> Did you try it on a system where busybox ash actually is your login 
> shell? It works, if ash is simply passing the script to bash, which 
> does a lookup via $PATH to find the script.

Ok, now i see the bug, i wasnt reading your description correctly,
sorry.

I change my /usr/buin/test.sh script to be just
echo "blah"

If i
#cd /usr/bin
#sh test.sh
blah

It works, but if try and run the script from / dir.
#cd /
#sh test.sh
sh: Can't open test.sh

But, i get the same error with and without your patch.


Glenn
_______________________________________________
busybox mailing list
busybox at mail.busybox.net http://busybox.net/mailman/listinfo/busybox



More information about the busybox mailing list