I'm not trying to write scripts that rely on the value of BASH. I only
discoverd the discrepancy while investigating the potential usefulness
of various variables set by the shell. Perhaps I just don't get the
point of having the variable in the first place.
Also I'm not very fond of Ubuntu's poin
On 2/12/16 10:38 AM, David Hunt wrote:
> I'm not trying to write scripts that rely on the value of BASH. I only
> discoverd the discrepancy while investigating the potential usefulness
> of various variables set by the shell. Perhaps I just don't get the
> point of having the variable in the first
On 2/8/16 7:09 PM, David Hunt wrote:
> Bash Version: 4.3
> Patch Level: 11
> Release Status: release
>
> Description:
> On my notebook running Ubuntu 14.04.3 LTS /bin/sh points to dash, not
> bash.
> To get sh behaviour from bash I use the command `exec -a sh /bin/bash'.
> When
hi,
I think the logic behind variables.c:723 get_bash_name is in this
case: put into BASH whatever valid command given to exec -a . E.g.: if
you put exec -a /bin/ksh /bin/bash and /bin/ksh exists and is
executable it will be seen in BASH variable.
sincerely,
pg
On Tue, Feb 9, 2016 at 1:09 AM
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE