Advanced Bash Scripting Guide 5.2 (Stable branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Advanced Bash Scripting Guide 5.2 (Stable branch)
# 1  
Old 03-14-2008
Advanced Bash Scripting Guide 5.2 (Stable branch)

ImageThe Advanced Bash Scripting Guide is both areference and a tutorial on shell scripting. Thiscomprehensive book (the equivalent of 880+ printpages) covers almost every aspect of shellscripting. It contains 340 profusely commentedillustrative examples, a number of tables, and across-linked index/glossary. Not just a shellscripting tutorial, this book also provides anintroduction to basic programming techniques, suchas sorting and recursion. It is well suited foreither individual study or classroom use. Itcovers Bash, up to and including version 3.2x.License: GNU Free Documentation License (FDL)Changes:
Many bugfixes and stylistic cleanups were done.Four new example scripts were added. A newsubsection on version 3.2 Bash update was added.Explanations of certain difficult concepts wereclarified. This is an important update.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Can anyone guide me with the BASH scripting

Hi, I am new to BASH script. I am working on the script to parsing the log message . the followings are my task: 1. Read the multiple log files, such as N1-2009-10-01, N2-2009-10-2, N3-2010-01-02.... 2. Parse the specific message, such as "aaaa" 3. If found the "aaaa" message in the log... (11 Replies)
Discussion started by: shyork2001
11 Replies
Login or Register to Ask a Question
BASHBUG(1)						      General Commands Manual							BASHBUG(1)

NAME
bashbug - report a bug in bash SYNOPSIS
bashbug [--version] [--help] [email-address] DESCRIPTION
bashbug is a shell script to help the user compose and mail bug reports concerning bash in a standard format. bashbug invokes the editor specified by the environment variable EDITOR on a temporary copy of the bug report format outline. The user must fill in the appropriate fields and exit the editor. bashbug then mails the completed report to bug-bash@gnu.org, or email-address. If the report cannot be mailed, it is saved in the file dead.bashbug in the invoking user's home directory. The bug report format outline consists of several sections. The first section provides information about the machine, operating system, the bash version, and the compilation environment. The second section should be filled in with a description of the bug. The third sec- tion should be a description of how to reproduce the bug. The optional fourth section is for a proposed fix. Fixes are encouraged. ENVIRONMENT
bashbug will utilize the following environment variables if they exist: EDITOR Specifies the preferred editor. If EDITOR is not set, bashbug defaults to emacs. HOME Directory in which the failed bug report is saved if the mail fails. TMPDIR Directory in which to create temporary files and directories. SEE ALSO
bash(1) AUTHORS
Brian Fox, Free Software Foundation bfox@gnu.org Chet Ramey, Case Western Reserve University chet@po.cwru.edu GNU Bash-4.0 1998 July 30 BASHBUG(1)