Debian Bug report logs - #274484
The shell script /usr/bin/bsh should work as a script interpreter.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Adam Sherman <adam@sherman.ca>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: The shell script /usr/bin/bsh should work as a script interpreter.

Date: Fri, 01 Oct 2004 23:14:07 -0400

Package: bsh
Version: 1.3.0-2
Severity: wishlist

It would be great if the shell script at /usr/bin/bsh would work when used as the bang-path in a 
script:

#!/usr/bin/bsh
print("Hello, World!");

At the moment, bash seems to try and interpret the file for an unknown reason.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-686
Locale: LANG=en_CA, LC_CTYPE=en_CA

Versions of packages bsh depends on:
ii  java-common                   0.22       Base of all Java packages
ii  sun-j2sdk1.5 [java-virtual-ma 1.5.0      Java(TM) 2 SDK, Standard Edition, 
ii  sun-j2sdk1.5debian [java-virt 0.14       Debian specific parts of Java(TM) 

-- no debconf information

Message #10 received at 274484@bugs.debian.org (full text, mbox, reply):

From: Michael Koch <konqueror@gmx.de>

To: Adam Sherman <adam@sherman.ca>

Cc: 274484@bugs.debian.org

Subject: Re: The shell script /usr/bin/bsh should work as a script interpreter.

Date: Tue, 26 Jun 2007 10:45:45 +0200

On Fri, Oct 01, 2004 at 11:14:07PM -0400, Adam Sherman wrote:
> Package: bsh
> Version: 1.3.0-2
> Severity: wishlist
> 
> It would be great if the shell script at /usr/bin/bsh would work when used as the bang-path in a 
> script:
> 
> #!/usr/bin/bsh
> print("Hello, World!");
> 
> At the moment, bash seems to try and interpret the file for an unknown reason.

Currently /usr/bin/bsh is a shell script. The kernel uses the sh (bash)
as interpreter for bsh script for security reasons. This cant be
circumvented. To make this work we need to write a native application
starting the java runtime. This is a bigger task. Perhaps we can reuse
one of the launchers from openjdk or harmony.


Cheers,
Michael
-- 
 .''`.  | Michael Koch <konqueror@gmx.de>
: :' :  | Free Java Developer <http://www.classpath.org>
`. `'   |
  `-    | 1024D/BAC5 4B28 D436 95E6 F2E0 BD11 5923 A008 2763 483B

Message #13 received at 274484-submitter@bugs.debian.org (full text, mbox, reply):

From: Vincent Fourmond <fourmond@debian.org>

To: 274484-submitter@bugs.debian.org

Subject: bsh shebang line: it works

Date: Thu, 10 Jan 2008 23:50:03 +0100

  Hello,

  It seems it now works:

~ ./biniou
Hello, World!

~ cat ./biniou
#!/usr/bin/bsh
print("Hello, World!");

  It is probably due to kernel improvements. Shall we close this bug ?

  Cheers,

	Vincent

-- 
Vincent Fourmond, Debian Developer
http://vince-debian.blogspot.com/
-- pretty boring signature, isn't it ?

Message #18 received at 274484@bugs.debian.org (full text, mbox, reply):

From: Niels Thykier <niels@thykier.net>

To: 274484@bugs.debian.org

Cc: 274484-submitter@bugs.debian.org

Subject: Re: bsh shebang line: it works

Date: Fri, 24 Jul 2009 09:43:07 +0200

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi

I just tested this with bsh (version 2.0b4) and it does not seem to work
for me. Neither the previous example nor


String a = "Hello"
System.out.println(a);

Which works directly in bsh, but not from a #!/usr/bin/bsh shell.

My kernel version is: 2.6.26-2-686

~Niels
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkppZggACgkQVCqoiq1YlqwtvwCfVkPu+FZvI1zk0mbf7o10p0G5
Q20An2iluaInOT1SFbmNJmikipt+x+pn
=fMwf
-----END PGP SIGNATURE-----

Message #26 received at 274484@bugs.debian.org (full text, mbox, reply):

From: Ludovic Claude <ludovic.claude@laposte.net>

To: Niels Thykier <niels@thykier.net>, 274484@bugs.debian.org

Cc: 274484-submitter@bugs.debian.org

Subject: Re: Bug#274484: bsh shebang line: it works

Date: Fri, 24 Jul 2009 09:10:17 +0100

Hi Niels,

This works for me:

#!/usr/bin/bsh
String a = "Hello";
System.out.println(a);

Maybe you were missing the semi colon after "Hello". You need also to
make your hello.bsh file executable

My test script:

cat > hello.bsh <<EOF
#!/usr/bin/bsh
String a = "Hello";
System.out.println(a);
EOF
chmod u+x hello.bsh
./hello.bsh

Can you give the exact version number for bsh on your system? Use
dpkg --status bsh

Ludovic

Niels Thykier a écrit :
> Hi
> 
> I just tested this with bsh (version 2.0b4) and it does not seem to work
> for me. Neither the previous example nor
> 
> 
> String a = "Hello"
> System.out.println(a);
> 
> Which works directly in bsh, but not from a #!/usr/bin/bsh shell.
> 
> My kernel version is: 2.6.26-2-686
> 
> ~Niels

_______________________________________________
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers

Message #34 received at 274484@bugs.debian.org (full text, mbox, reply):

From: Niels Thykier <niels@thykier.net>

To: 274484@bugs.debian.org

Subject: [Fwd: Re: Bug#274484: bsh shebang line: it works]

Date: Fri, 24 Jul 2009 12:53:32 +0200

Forgot to CC bugs.

Ludovic Claude wrote:
> Hi Niels,
>
> This works for me:
>
> #!/usr/bin/bsh
> String a = "Hello";
> System.out.println(a);
>
> Maybe you were missing the semi colon after "Hello". You need also to
> make your hello.bsh file executable
>
> My test script:
>
> cat > hello.bsh <<EOF
> #!/usr/bin/bsh
> String a = "Hello";
> System.out.println(a);
> EOF
> chmod u+x hello.bsh
> ./hello.bsh
>

Hi,

I am afraid it is not the semi-colon - I may have forgotten it in my
original test, but my problem is that it is looking for a command called
"String".

$ cat > hello.bsh <<EOF
> #!/usr/bin/bsh
> String a = "Hello";
> System.out.println(a);
> EOF
$ chmod u+x hello.bsh
$ ./hello.bsh
./hello.bsh: line 2: String: command not found
./hello.bsh: line 3: syntax error near unexpected token `a'
./hello.bsh: line 3: `System.out.println(a);'

For the sake of it I also tried experimental - same result.

However the following works (only used bsh/testing for these):

$ bsh <<EOF
String a = "Hello";
System.out.println(a);
EOF

(In terms of executing the code - The bsh prompt however makes it rather
useless for other intentions)

And calling bsh directly works as well:
$ bsh hello.bsh
Hello


> Can you give the exact version number for bsh on your system? Use
> dpkg --status bsh
>
Testing:

[...]
Version: 2.0b4-8
[...]


When I tried experimental:

[...]
Version: 2.0b4-9
[...]


My /usr/bin/java is the non-free sun6, though I doubt it is the cause of
the problem.

> Ludovic
>

~Niels

> Niels Thykier a écrit :
>> Hi
>>
>> I just tested this with bsh (version 2.0b4) and it does not seem to work
>> for me. Neither the previous example nor
>>
>>
>> String a = "Hello"
>> System.out.println(a);
>>
>> Which works directly in bsh, but not from a #!/usr/bin/bsh shell.
>>
>> My kernel version is: 2.6.26-2-686
>>
>> ~Niels
>
> _______________________________________________
> pkg-java-maintainers mailing list
> pkg-java-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
>
>
>

Message #39 received at 274484@bugs.debian.org (full text, mbox, reply):

From: Niels Thykier <niels@thykier.net>

To: Ludovic Claude <ludovic.claude@laposte.net>

Cc: 274484@bugs.debian.org

Subject: Re: Bug#274484: bsh shebang line: it works

Date: Fri, 24 Jul 2009 19:49:04 +0200

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ludovic Claude wrote:
> Maybe you've got something else called bsh in your path.
> 
> Can you send me the result for those commands:
> 
> echo $PATH
> bsh --version
> /usr/bin/bsh --version
> 
> 

"which bsh" says that bsh is /usr/bin/bsh
"type -a bsh" says I have no other bsh than /usr/bin/bsh.
Last but not least:

$ echo $PATH
/home/user/bin:/usr/local/bin:/usr/bin:/bin:/usr/games
$ for FILE in `echo $PATH | sed 's/:/\n/g' | sed 's@$@/bsh@g'` ; do
$>   test -f "$FILE" && ls -l "$FILE"
$> done
- -rwxr-xr-x 1 root root 230 2008-04-27 23:13 /usr/bin/bsh
$

confirms this (I remember something about "type" catching its results,
so just in case, I had the shell check manually).


> It should print for both commands
>  File not found: java.io.FileNotFoundException: /home/ludo/tmp/--version
> (No such file or directory)
> 

Both of the commands fails as expected.

$ bsh --version
File not found: java.io.FileNotFoundException: /home/user/--version (No
such file or directory)
$ /usr/bin/bsh --version
File not found: java.io.FileNotFoundException: /home/user/--version (No
such file or directory)

So I am afraid this is not the issue. Let me know if you have other
tests, that we can use to narrow down the problem.

> Ludovic
> 

~Niels

> Niels Thykier a écrit :
>> Ludovic Claude wrote:
>>> [...]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpp8zMACgkQVCqoiq1YlqxTtACfeviuNPQYSu8n+F7vVIjJmHU6
OnkAoISoePzQtwrI5c72XtU61Izjpdec
=Ziof
-----END PGP SIGNATURE-----

Message #44 received at 274484@bugs.debian.org (full text, mbox, reply):

From: Ludovic Claude <ludovic.claude@laposte.net>

To: Niels Thykier <niels@thykier.net>

Cc: 274484@bugs.debian.org

Subject: Re: Bug#274484: bsh shebang line: it works

Date: Fri, 24 Jul 2009 19:34:44 +0100

Sorry Niels, I don't have any more ideas.
Looking at the bug history - and the error messages, it looks like bash
is trying to run the script instead of bsh.

I'm running Ubuntu 9.04, and all works well. There may be something in
the configuration of bash in Debian that's not letting it run the bsh
script from a shebang line, but I don't know what it is.

Ludovic


Niels Thykier a écrit :
> Ludovic Claude wrote:
>> Maybe you've got something else called bsh in your path.
> 
>> Can you send me the result for those commands:
> 
>> echo $PATH
>> bsh --version
>> /usr/bin/bsh --version
> 
> 
> 
> "which bsh" says that bsh is /usr/bin/bsh
> "type -a bsh" says I have no other bsh than /usr/bin/bsh.
> Last but not least:
> 
> $ echo $PATH
> /home/user/bin:/usr/local/bin:/usr/bin:/bin:/usr/games
> $ for FILE in `echo $PATH | sed 's/:/\n/g' | sed 's@$@/bsh@g'` ; do
> $>   test -f "$FILE" && ls -l "$FILE"
> $> done
> -rwxr-xr-x 1 root root 230 2008-04-27 23:13 /usr/bin/bsh
> $
> 
> confirms this (I remember something about "type" catching its results,
> so just in case, I had the shell check manually).
> 
> 
>> It should print for both commands
>>  File not found: java.io.FileNotFoundException: /home/ludo/tmp/--version
>> (No such file or directory)
> 
> 
> Both of the commands fails as expected.
> 
> $ bsh --version
> File not found: java.io.FileNotFoundException: /home/user/--version (No
> such file or directory)
> $ /usr/bin/bsh --version
> File not found: java.io.FileNotFoundException: /home/user/--version (No
> such file or directory)
> 
> So I am afraid this is not the issue. Let me know if you have other
> tests, that we can use to narrow down the problem.
> 
>> Ludovic
> 
> 
> ~Niels
> 
>> Niels Thykier a écrit :
>>> Ludovic Claude wrote:
>>>> [...]
> 

Message #49 received at 274484@bugs.debian.org (full text, mbox, reply):

From: Michael Koch <konqueror@gmx.de>

To: Niels Thykier <niels@thykier.net>, 274484@bugs.debian.org

Cc: 274484-submitter@bugs.debian.org

Subject: Re: Bug#274484: bsh shebang line: it works

Date: Fri, 24 Jul 2009 21:54:28 +0200

On Fri, Jul 24, 2009 at 09:43:07AM +0200, Niels Thykier wrote:
> Hi
> 
> I just tested this with bsh (version 2.0b4) and it does not seem to work
> for me. Neither the previous example nor
> 
> 
> String a = "Hello"
> System.out.println(a);
> 
> Which works directly in bsh, but not from a #!/usr/bin/bsh shell.
> 
> My kernel version is: 2.6.26-2-686

I just tried your example with the version of bsh from lenny aka stable
and sid aka unstable and I can't reproduce the bug. It just works.

That's really a strange bug.


Cheers,
Michael

Message #57 received at 274484@bugs.debian.org (full text, mbox, reply):

From: Niels Thykier <niels@thykier.net>

To: Michael Koch <konqueror@gmx.de>, 274484@bugs.debian.org

Subject: Re: Bug#274484: bsh shebang line: it works

Date: Sun, 26 Jul 2009 00:35:15 +0200

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael Koch wrote:
> On Fri, Jul 24, 2009 at 09:43:07AM +0200, Niels Thykier wrote:
>> Hi
>>
>> I just tested this with bsh (version 2.0b4) and it does not seem to work
>> for me. Neither the previous example nor
>>
>>
>> String a = "Hello"
>> System.out.println(a);
>>
>> Which works directly in bsh, but not from a #!/usr/bin/bsh shell.
>>
>> My kernel version is: 2.6.26-2-686
> 
> I just tried your example with the version of bsh from lenny aka stable
> and sid aka unstable and I can't reproduce the bug. It just works.
> 
> That's really a strange bug.
> 
> 
> Cheers,
> Michael
> 

Yeah, I am running out of ideas here as well.

I have gotten reportbug to gather the standard information related to
bsh on my system, hopefully it can help in narrowing down the issue.

For the record, while my /bin/sh is linked to /bin/dash instead of
/bin/bash, I did try to relink to /bin/bash without any success - as
well as using /bin/bash as interpreter for the shell script
/usr/bin/bsh. (NB: I reverted my changes to /usr/bin/bsh between tests
by reinstalling/purge+installing it)


~Niels

- -- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages bsh depends on:
ii  default-jre [java2-runtime]   1.5-32     Standard Java or Java
compatible R
ii  gcj-jre [java2-runtime]       4:4.3.3-9  Java runtime environment
using GIJ
ii  java-gcj-compat [java2-runtim 1.0.80-5.1 Java runtime environment
using GIJ
ii  libjline-java                 0.9.94-1   Java library for handling
console
ii  openjdk-6-jre [java2-runtime] 6b16-4     OpenJDK Java runtime, using
Hotspo
ii  sun-java5-jre [java2-runtime] 1.5.0-19-1 Sun Java(TM) Runtime
Environment (
ii  sun-java6-jre [java2-runtime] 6-14-1     Sun Java(TM) Runtime
Environment (

Versions of packages bsh recommends:
ii  bsh-gcj                       2.0b4-8    Java scripting environment
(BeanSh
ii  libgcj8-1-awt                 4.2.4-4    AWT peer runtime libraries
for use

Versions of packages bsh suggests:
pn  bsh-doc                       <none>     (no description available)
pn  libservlet2.3-java            <none>     (no description available)

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpriKAACgkQVCqoiq1Ylqya9gCfRA4u1nYD4KsAsiMZzNJJ/MVA
a5cAoIbXvao2DKsGkAm1VdC5n0qHRGyf
=McLs
-----END PGP SIGNATURE-----

Message #62 received at 274484@bugs.debian.org (full text, mbox, reply):

From: Jan-Pascal van Best <janpascal@vanbest.org>

To: 274484@bugs.debian.org

Subject: bsh shebang line: confirm failure

Date: Sun, 26 Jul 2009 09:23:55 +0200

just to confirm it isn't something extremely singular with the
reporter's system, I'd like to confirm that on my system, running the
sample bsh script with ./test.bsh also fails.

Jan-Pascal

Message #67 received at 274484@bugs.debian.org (full text, mbox, reply):

From: Gabriele Giacone <1o5g4r8o@gmail.com>

To: 274484@bugs.debian.org

Subject: workaround

Date: Sun, 02 May 2010 01:30:15 +0200

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

It seems to have been solved between 2.6.27 and 2.6.28 kernels.

http://bugs.gentoo.org/show_bug.cgi?id=279915#c63


Workaround for lenny:
replace
#!/usr/bin/bsh
with
#!/usr/bin/env bsh


- --
Gabriele
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkvcuYEACgkQp3cdCbVcnCtx7gCeON/5AZJWyaGM0lYchhOHQ/0/
k6gAnAnuF5xB9V8DcJNjiIYQaPEnWn1L
=0cvf
-----END PGP SIGNATURE-----

Message #72 received at 274484-done@bugs.debian.org (full text, mbox, reply):

From: Emmanuel Bourg <ebourg@apache.org>

To: 274484-done@bugs.debian.org

Subject: Re: workaround

Date: Thu, 30 Nov 2017 01:01:10 +0100

I confirm it works with recent kernels (tested with 2.6.32 and 4.9)

Emmanuel Bourg

Send a report that this bug log contains spam.