Introduction
============
-This is GNU Bash, version 2.02.1. Bash is the GNU Project's Bourne
+This is GNU Bash, version 3.2. Bash is the GNU Project's Bourne
Again SHell, a complete implementation of the POSIX.2 shell spec,
but also with interactive command line editing, job control on
architectures that support it, csh-like features such as history
large Unix-style man page. The man page is the definitive description
of the shell's features.
-See the file CWRU/POSIX.NOTES for a discussion of how Bash differs
+See the file POSIX for a discussion of how the Bash defaults differ
from the POSIX.2 spec and a description of the Bash `posix mode'.
There are some user-visible incompatibilities between this version
-of Bash and the previous widely-distributed version, bash-1.14.
-For details, see the file COMPAT. The NEWS file tersely lists
-features that are new in this release.
+of Bash and previous widely-distributed versions, bash-1.14 and
+bash-2.05b. For details, see the file COMPAT. The NEWS file tersely
+lists features that are new in this release.
-Bash is free software, distributed under the terms of the GNU Public
-License, version 2. For more information, see the file COPYING.
+Bash is free software, distributed under the terms of the [GNU]
+General Public License, version 2. For more information, see the
+file COPYING.
A number of frequently-asked questions are answered in the file
`doc/FAQ'.
Reporting Bugs
==============
-Bug reports for bash-2.02.1 should be sent to:
+Bug reports for bash should be sent to:
- bug-bash@prep.ai.mit.edu
+ bug-bash@gnu.org
using the `bashbug' program that is built and installed at the same
time as bash.
-The discussion list `bug-bash@prep.ai.mit.edu' often contains
-information about new ports of Bash, or discussions of new features or
-behavior changes that people would like. This mailing list is also
-available as a usenet newsgroup: gnu.bash.bug.
+The discussion list `bug-bash@gnu.org' often contains information
+about new ports of Bash, or discussions of new features or behavior
+changes that people would like. This mailing list is also available
+as a usenet newsgroup: gnu.bash.bug.
When you send a bug report, please use the `bashbug' program that is
built at the same time as bash. If bash fails to build, try building
bashbug directly with `make bashbug'. If you cannot build `bashbug',
-please send mail to bug-bash@prep.ai.mit.edu with the following
-information:
+please send mail to bug-bash@gnu.org with the following information:
- * the version number and release status of Bash (e.g., 2.02.1-release)
- * the machine and OS that it is running on (look at the file
- `.made' in the bash build directory)
+ * the version number and release status of Bash (e.g., 2.05a-release)
+ * the machine and OS that it is running on (you may run
+ `bashversion -l' from the bash build directory for this information)
* a list of the compilation flags or the contents of `config.h', if
appropriate
* a description of the bug
The `bashbug' program includes much of this automatically.
If you would like to contact the Bash maintainers directly, send mail
-to bash-maintainers@prep.ai.mit.edu.
+to bash-maintainers@gnu.org.
While the Bash maintainers do not promise to fix all bugs, we would
like this shell to be the best that we can make it.
Enjoy!
Chet Ramey
-chet@po.cwru.edu
+chet.ramey@case.edu