Mainpage
Searchform
History
Versions
Categories
Contents
Deutsch
SuSE Linux: Versions since 5.0
If Bash is started as /bin/sh
, the POSIX mode is
activated by default. This mode forbids certain constructs that
were possible in earlier Bash versions,although they are not
strictly POSIX conform.
We know of the following differences:
{}
:{ command1; command2; command3 }new:
{ command1; command2; command3; }
In Bash 2.0, a command list must be terminated with a semi-colon.
case
... esac
In the old Bash, the ;;
after the last statement in a
case
statement is optional. As of Bash 2.0 it is
required.
Especially the two changes with semi-cola often occur within handwritten scripts.
Please note, that all mentioned differences may NOT be regarded as errors but only "changes". Indeed the new Bash provides a better conformance with the POSIX standard than the old one.
The decision to switch to Bash 2.0 was taken because Bash will become the standard in the near future. Together with the introduction of the new package management (RPM) and other major changes in S.u.S.E. Linux 5.0 it was the right moment to introduce the new Bash.
Besides the listed differences above, there are no other problems to be
expected with the new Bash 2.0 . On the contrary : The new Bash will offer you many interesting
features, Bash as an interactive shell becomes much more comfortable. Please read the manpage
and the documentation (/usr/doc/packages/bash/bashref.html
resp.
/usr/doc/packages/bash/FAQ
).
There are several possibilities :
cd /bin && mv bash bash2 && ln -s bash1 bash
set +o posix
. With
the command set -o
the current options will be printed.
/bin/bash
as the login shell, not /bin/sh
.
Keywords: BASH, 2.01, SHELL, COMMAND LINE, INPUT LINE, 5.0, INTERPRETER
Categories:
Applications
Mainpage
Searchform
History
Versions
Categories
Contents
Deutsch