Paul Jarc wrote:
> Charlse Darwin wrote:
> > i.e. How do I get the latest to be the login shell?
>
> You could add "exec bash" as the last command in ~/.bash_profile.
I think I would avoid doing that unless the user is aware of the
sublte and complex relationships that exist there. The bash_prof
he /etc/passwd file (e.g. using 'vipw') and make the changes
directly.
> Which bash is being used by the system; 3.2.33(1)-release or 2.05b.0
> (1)-release?
The system will continue to use the system version of bash. It won't
know about your local copy installed into /us
Charlse Darwin <[EMAIL PROTECTED]> wrote:
> i.e. How do I get the latest to be the login shell?
You could add "exec bash" as the last command in ~/.bash_profile.
paul
Feb 24, 2008, at 7:56 AM, Bernd Eggink wrote:
Charlse Darwin schrieb:
$ echo $BASH_VERSION
2.05b.0(1)-release
$ bash --version
GNU bash, version 3.2.33(1)-release (powerpc-apple-darwin8.11.0)
Copyright (C) 2007 Free Software Foundation, Inc.
$ which bash
/opt/local/bin/bash
$
# Which bash is being
Charlse Darwin schrieb:
$ echo $BASH_VERSION
2.05b.0(1)-release
$ bash --version
GNU bash, version 3.2.33(1)-release (powerpc-apple-darwin8.11.0)
Copyright (C) 2007 Free Software Foundation, Inc.
$ which bash
/opt/local/bin/bash
$
# Which bash is being used by the system; 3.2.33(1)-release or
$ echo $BASH_VERSION
2.05b.0(1)-release
$ bash --version
GNU bash, version 3.2.33(1)-release (powerpc-apple-darwin8.11.0)
Copyright (C) 2007 Free Software Foundation, Inc.
$ which bash
/opt/local/bin/bash
$
# Which bash is being used by the system; 3.2.33(1)-release or 2.05b.0
(1)-release?
A few months ago we went through a POSIX-compatibility sweep of
coreutils, and in my nonexistent spare time I'd like to migrate some
of those fixes into the Bash builtins that duplicate coreutils.
Conversely, I'd like to migrate any fixes made by Bash in this area
into coreutils.
Which version of
