Command Prompt to Start a New Bourneagain Shell Session

GNU replacement for the Bourne trounce

Bash

Screenshot of a Bash session
Original author(s)	Brian Fox
Developer(s)	Chet Ramey[1] [2]
Initial release	June 8, 1989; 32 years ago  (1989-06-08)
Stable release	5.1.16[3] / five January 2022
Preview release	five.2-alpha[4] / xx January 2022
Repository	git.savannah.gnu.org/cgit/bash.git
Written in	C
Operating system	Unix-like[five] macOS (GPL-2.0-or-later; GPL-3.0-or-afterwards bachelor through 3rd parties) Windows (GPL-3.0-or-later)[half dozen] [7]
Platform	GNU
Available in	Multilingual (gettext)
Blazon	Unix beat out, control language
License	Since 4.0: GPL-iii.0-or-subsequently[8] i.xi? to 3.2: GPL-2.0-or-subsequently[9] 0.99? to i.05?: GPL-ane.0-or-later[10] [11] [12]
Website	www.gnu.org/software/fustigate/

Fustigate is a Unix shell and command linguistic communication written by Brian Trick for the GNU Project as a free software replacement for the Bourne crush.^{[xiii] [xiv]} First released in 1989,^[15] it has been used as the default login shell for most Linux distributions.^[16] A version is likewise available for Windows ten via the Windows Subsystem for Linux.^[17] It is also the default user shell in Solaris 11.^[xviii] Fustigate was also the default trounce in all versions of Apple macOS prior to the 2019 release of macOS Catalina, which inverse the default shell to zsh, although Bash remains available as an alternative shell.^[19]

Bash is a command processor that typically runs in a text window where the user types commands that cause actions. Bash can besides read and execute commands from a file, called a shell script. Like about Unix shells, it supports filename globbing (wildcard matching), piping, here documents, command substitution, variables, and command structures for condition-testing and iteration. The keywords, syntax, dynamically scoped variables and other basic features of the language are all copied from sh. Other features, due east.thousand., history, are copied from csh and ksh. Bash is a POSIX-compliant vanquish, but with a number of extensions.

The beat out's name is an acronym for Bourne Again Beat, a pun on the name of the Bourne vanquish that information technology replaces^[20] and the notion of being "born again".^{[21] [22]}

A security pigsty in Bash dating from version ane.03 (Baronial 1989),^[23] dubbed Shellshock, was discovered in early September 2014 and quickly led to a range of attacks across the Cyberspace.^{[24] [25] [26]} Patches to prepare the bugs were made available soon after the bugs were identified.

History [edit]

Brian Fox began coding Bash on January 10, 1988,^[27] afterwards Richard Stallman became dissatisfied with the lack of progress beingness fabricated by a prior developer.^[13] Stallman and the Free Software Foundation (FSF) considered a free crush that could run existing shell scripts then strategic to a completely free system built from BSD and GNU lawmaking that this was one of the few projects they funded themselves, with Fox undertaking the work as an employee of FSF.^{[thirteen] [28]} Fob released Bash as a beta, version .99, on June 8, 1989,^[15] and remained the primary maintainer until erstwhile between mid-1992^[29] and mid-1994,^[30] when he was laid off from FSF^[31] and his responsibility was transitioned to another early correspondent, Chet Ramey.^{[32] [33] [34]}

Since then, Bash has become by far the almost pop shell among users of Linux, becoming the default interactive crush on that operating system's various distributions^{[35] [36]} (although Almquist beat out may be the default scripting beat out) and on Apple'southward macOS releases earlier Catalina in October 2019.^{[37] [38] [sixteen]} Bash has too been ported to Microsoft Windows and distributed with Cygwin and MinGW, to DOS by the DJGPP project, to Novell NetWare, to OpenVMS by the GNV project,^[39] to ArcaOS,^[40] and to Android via various terminal emulation applications.

In September 2014, Stéphane Chazelas, a Unix/Linux specialist,^[41] discovered a security problems in the plan. The bug, first disclosed on September 24, was named Shellshock and assigned the numbers CVE-2014-6271, CVE-2014-6277 and CVE-2014-7169. The bug was regarded equally severe, since CGI scripts using Bash could be vulnerable, enabling capricious code execution. The bug was related to how Bash passes part definitions to subshells through surround variables.^[42]

Features [edit]

The Bash control syntax is a superset of the Bourne shell command syntax. Bash supports brace expansion, command line completion (Programmable Completion),^[43] basic debugging^[44] and bespeak treatment (using trap) since bash 2.05a^[45] among other features. Bash can execute the vast majority of Bourne vanquish scripts without modification, with the exception of Bourne shell scripts stumbling into fringe syntax behavior interpreted differently in Bash or attempting to run a system command matching a newer Fustigate builtin, etc. Bash command syntax includes ideas drawn from the KornShell (ksh) and the C shell (csh) such as command line editing, control history (history control),^[46] the directory stack, the $RANDOM and $PPID variables, and POSIX command commutation syntax $(…).

When a user presses the tab key within an interactive command-shell, Fustigate automatically uses command line completion, since beta version 2.04,^[47] to match partly typed programme names, filenames and variable names. The Fustigate command-line completion system is very flexible and customizable, and is oft packaged with functions that consummate arguments and filenames for specific programs and tasks.

Bash's syntax has many extensions lacking in the Bourne shell. Bash can perform integer calculations ("arithmetics evaluation") without spawning external processes. Information technology uses the ((…)) command and the $((…)) variable syntax for this purpose. Its syntax simplifies I/O redirection. For case, it can redirect standard output (stdout) and standard fault (stderr) at the same time using the &> operator. This is simpler to type than the Bourne shell equivalent 'command > file ii>&1'. Bash supports process substitution using the <(command) and >(command)syntax, which substitutes the output of (or input to) a control where a filename is normally used. (This is implemented through /proc/fd/ unnamed pipes on systems that support that, or via temporary named pipes where necessary).

When using the 'function' keyword, Bash function declarations are not compatible with Bourne/Korn/POSIX scripts (the KornShell has the aforementioned trouble when using 'role'), but Bash accepts the same function declaration syntax as the Bourne and Korn shells, and is POSIX-conformant. Considering of these and other differences, Fustigate shell scripts are rarely runnable under the Bourne or Korn trounce interpreters unless deliberately written with that compatibility in mind, which is becoming less mutual as Linux becomes more than widespread. But in POSIX mode, Bash conforms with POSIX more closely.^[48]

Bash supports here documents. Since version 2.05b Bash can redirect standard input (stdin) from a "here string" using the <<< operator.

Fustigate 3.0 supports in-process regular expression matching using a syntax reminiscent of Perl.^[49]

In February 2009,^[50] Bash 4.0 introduced support for associative arrays.^[11] Associative assortment indices are strings, in a mode like to AWK or Tcl.^[51] They tin can exist used to emulate multidimensional arrays. Fustigate four also switches its license to GPL-iii.0-or-afterwards; some users suspect this licensing change is why MacOS continues to apply older versions.^[52] Apple finally stopped using Bash in their operating systems with the release of MacOS Catalina in 2019.^[19]

Brace expansion [edit]

Brace expansion, also called alternation, is a feature copied from the C crush. It generates a set up of alternative combinations. Generated results need not exist as files. The results of each expanded string are not sorted and left to right order is preserved:

                        $                        echo            a{p,c,d,b}e            ape ace ade abe            $                        echo            {a,b,c}{d,eastward,f}            ad ae af bd be bf cd ce cf          

Users should not utilise brace expansions in portable shell scripts, because the Bourne beat out does not produce the same output.

                        $                        # A traditional beat does not produce the same output            $            /bin/sh -c            'repeat a{p,c,d,b}due east'            a{p,c,d,b}due east          

When brace expansion is combined with wildcards, the braces are expanded first, and then the resulting wildcards are substituted normally. Hence, a listing of JPEG and PNG images in the current directory could exist obtained using:

            ls *.{jpg,jpeg,png}            # expands to *.jpg *.jpeg *.png - after which,            # the wildcards are candy            echo            *.{png,jp{due east,}m}            # repeat just show the expansions -            # and braces in braces are possible.          

In addition to alternation, brace expansion tin can exist used for sequential ranges between two integers or characters separated by double dots. Newer versions of Fustigate allow a 3rd integer to specify the increment.

                        $                        echo            {            one..10}            i 2 3 iv 5 6 7 8 nine 10            $                        echo            file{            1..iv}.txt            file1.txt file2.txt file3.txt file4.txt            $                        echo            {a..eastward}            a b c d eastward            $                        repeat            {            1..x..3}            1 4 7 x            $                        echo            {a..j..3}            a d g j          

When brace expansion is combined with variable expansion (A.K.A. parameter expansion and parameter substitution) the variable expansion is performed after the caryatid expansion, which in some cases may necessitate the use of the eval born, thus:

                        $                        start            =            1            ;            terminate            =            10            $                        echo            {            $start..$end            }            # fails to expand due to the evaluation order            {ane..x}            $                        eval            echo            {            $start..$terminate            }            # variable expansion occurs then resulting cord is evaluated            1 two 3 4 5 half-dozen 7 8 9 10          

Startup scripts [edit]

When Fustigate starts, it executes the commands in a multifariousness of dot files. Different Bash crush scripts, dot files do not typically have execute permission enabled nor an interpreter directive similar #!/bin/bash.

Legacy-compatible Bash startup example [edit]

The skeleton ~/.bash_profile below is uniform with the Bourne beat and gives semantics similar to csh for the ~/.bashrc and ~/.bash_login. The [ -r filename ] && cmd is a short-circuit evaluation that tests if filename exists and is readable, skipping the part later the && if it is non.

                        [            -r ~/.contour            ]            &&            . ~/.profile            # prepare up environment, in one case, Bourne-sh syntax only            if            [            -n            "            $PS1            "            ]            ;            so            # are nosotros interactive?            [            -r ~/.bashrc            ]            &&            . ~/.bashrc            # tty/prompt/role setup for interactive shells            [            -r ~/.bash_login            ]            &&            . ~/.bash_login            # any at-login tasks for login crush just            fi            # Finish of "if" cake          

Operating arrangement issues in Fustigate startup [edit]

Some versions of Unix and Linux contain Bash system startup scripts, generally under the /etc directories. Bash calls these equally function of its standard initialization, merely other startup files tin read them in a different order than the documented Bash startup sequence. The default content of the root user's files may as well take problems, equally well equally the skeleton files the arrangement provides to new user accounts upon setup. The startup scripts that launch the X window organisation may also do surprising things with the user's Fustigate startup scripts in an try to set up user-environment variables before launching the window director. These bug can frequently be addressed using a ~/.xsession or ~/.xprofile file to read the ~/.profile — which provides the environment variables that Fustigate trounce windows spawned from the window manager need, such every bit xterm or Gnome Final.

Portability [edit]

Invoking Bash with the --posix choice or stating ready -o posix in a script causes Bash to conform very closely to the POSIX 1003.2 standard.^[53] Bash shell scripts intended for portability should have into account at least the POSIX shell standard. Some bash features not constitute in POSIX are:^{[53] [54]}

• Certain extended invocation options
• Brace expansion
• Arrays and associative arrays
• The double subclass [[ ... ]] extended examination construct and its regex matching
• The double-parentheses arithmetics-evaluation construct (simply (( ... )); $(( ... )) is POSIX)
• Sure string-manipulation operations in parameter expansion
• local for scoped variables
• Process substitution
• Bash-specific builtins
• Coprocesses
• $EPOCHSECONDS and $EPOCHREALTIME variables ^[55]

If a piece of code uses such a feature, it is called a "bashism" – a trouble for portable use. Debian's checkbashisms and Vidar Holen'southward shellcheck tin can exist used to brand sure that a script does not contain these parts.^{[56] [57]} The list varies depending on the actual target shell: Debian's policy allows some extensions in their scripts (as they are in the dash shell),^[54] while a script intending to support pre-POSIX Bourne shells, like autoconf's configure, are even more limited in the features they can use.^[58]

Keyboard shortcuts [edit]

Fustigate uses readline to provide keyboard shortcuts for command line editing using the default (Emacs) central bindings. Vi-bindings can exist enabled by running set -o vi.^[59]

Procedure management [edit]

The Bash crush has two modes of execution for commands: batch, and concurrent mode.

To execute commands in batch (i.e., in sequence) they must exist separated past the character ";", or on separate lines:

in this example, when command1 is finished, command2 is executed.

A background execution of command1 can occur using (symbol &) at the finish of an execution control, and procedure will be executed in groundwork returning immediately command to the shell and allowing continued execution of commands.

Or to accept a concurrent execution of ii command1 and command2, they must be executed in the Bash shell in the post-obit fashion:

In this case command1 is executed in the background & symbol, returning immediately control to the shell that executes command2 in the foreground.

A process can exist stopped and control returned to fustigate past typing Ctrl+z while the process is running in the foreground.^[60]

A list of all processes, both in the background and stopped, tin can be accomplished past running jobs:

                        $                        jobs            [1]-  Running                  command1 &            [ii]+  Stopped                  command2          

In the output, the number in brackets refers to the chore id. The plus sign signifies the default process for bg and fg. The text "Running" and "Stopped" refer to the Procedure state. The final string is the control that started the process.

The state of a process can be changed using various commands. The fg control brings a process to the foreground, while bg sets a stopped process running in the groundwork. bg and fg tin have a job id as their showtime argument, to specify the process to deed on. Without ane, they use the default procedure, identified by a plus sign in the output of jobs. The kill command can be used to end a procedure prematurely, past sending it a indicate. The task id must be specified after a percent sign:

Provisional execution [edit]

Bash supplies "conditional execution" command separators that brand execution of a control contingent on the get out code gear up by a precedent control. For example:

                        cd            "            $SOMEWHERE            "            &&            ./do_something            ||            echo            "An error occurred"            >&            2          

Where ./do_something is but executed if the cd (change directory) command was "successful" (returned an exit condition of cypher) and the repeat command would simply exist executed if either the cd or the ./do_something command render an "fault" (non-naught exit condition).

For all commands the exit status is stored in the special variable $?. Bash also supports if ...; then ...; else ...; fi and case $VARIABLE in $pattern )...;; $other_pattern )...;; esac forms of conditional control evaluation.

Bug reporting [edit]

"bashbug" redirects hither. For the widely reported September 2014 bug establish in Bash, run across Shellshock (software problems).

An external control called bashbug reports Fustigate shell bugs. When the command is invoked, it brings up the user'due south default editor with a course to fill in. The form is mailed to the Bash maintainers (or optionally to other e-mail addresses).^{[61] [62]}

Programmable completion [edit]

Bash supports programmable completion via built-in complete, compopt, and compgen commands.^[63] The feature has been available since the beta version of 2.04 released in 2000.^{[64] [65]} These commands enable circuitous and intelligent completion specification for commands (i.e. installed programs), functions, variables, and filenames.^[66]

The complete and compopt 2 commands specify how arguments of some available commands or options are going to be listed in the readline input. As of version 5.i completion of the command or the selection is usually activated by the Tab ↹ keystroke later typing its name.^[66]

Release history [edit]

Version	Release date	Release notes
bash-5.1	2020-12-07	github version history NEWS [11]
bash-five.0	2019-01-07	[67] [68] [69]
bash-v.0-rc1	2018-12-20
bash-five.0-beta2	2018-xi-28
fustigate-5.0-beta	2018-09-17
fustigate-5.0-blastoff	2018-05-22
fustigate-4.4	2016-09-xv	github version history NEWS v4.iv
bash-4.four-rc2	2016-08-22
fustigate-iv.4-rc1	2016-02-24
fustigate-iv.4-beta2	2016-07-11
bash-iv.4-beta	2015-ten-12
fustigate-iv.three	2014-02-26
bash-four.2	2011-02-13
bash-four.1	2009-12-31
bash-4.0	2009-02-20
bash-4.0-rc1	2009-01-12
bash-iii.two	2006-10-11
bash-3.1	2005-12-08
bash-3.0	2004-08-03
fustigate-ii.05b	2002-07-17
fustigate-two.05a	2001-11-16
bash-2.05	2001-04-09
bash-ii.04	2000-03-21
bash-2.03	1999-02-19
fustigate-2.02	1998-04-18
bash-two.01	1997-06-05
bash-ii.0	1996-12-31

Run across also [edit]

• Comparison of command shells

References [edit]

1. ^ Hamilton, Naomi (May 30, 2008). "The A-Z of Programming Languages: BASH/Bourne-Again Beat". Computerworld. Archived from the original on November 8, 2016. Retrieved March i, 2022.
2. ^ Ramey, Chet (April twenty, 2021). "The GNU Bourne-Again Vanquish". Technology Infrastructure Services. Case Western Reserve University. Retrieved March one, 2022.
3. ^ "Fustigate-5.1 Official Patch 16". Retrieved February 4, 2022.
4. ^ Chet Ramey (January 21, 2022). "Fustigate-five.2-blastoff available". Retrieved February two, 2022.
5. ^ "Fustigate FAQ, version 4.14". Archived from the original on September 1, 2018. Retrieved April 9, 2016.
6. ^ "Missing source code - GPL compliance? · Result #107 · Microsoft/WSL". GitHub. Archived from the original on September 24, 2019. Retrieved July 8, 2016.
7. ^ "GNU Bash". Softpedia. SoftNews. January 23, 2010. Archived from the original on October 21, 2017. Retrieved April nine, 2016.
8. ^ GNU Project. "README file". Archived from the original on Apr 26, 2019. Retrieved Apr sixteen, 2014. Bash is complimentary software, distributed nether the terms of the [GNU] Full general Public License as published by the Free Software Foundation, version 3 of the License (or any subsequently version).
9. ^ "bash-1.xi". oldlinux.org. See test.c for GPL-2.0-or-later
10. ^ "fustigate-1.05.tar". oldlinux.org.
11. ^ ^{a b c} "BashFAQ/061 - Greg's Wiki". mywiki.wooledge.org. Archived from the original on March ii, 2021. Retrieved March 1, 2021.
12. ^ "Is at that place a style to download the presumably initial bash source bash-0.99?". unix.stackexchange.com.
13. ^ ^{a b c}
14. ^ Hamilton, Naomi (May 30, 2008), "The A-Z of Programming Languages: BASH/Bourne-Once more Shell", Computerworld: two, archived from the original on July half-dozen, 2011, retrieved March 21, 2011, When Richard Stallman decided to create a full replacement for the so-burdened Unix systems, he knew that he would eventually accept to have replacements for all of the mutual utilities, especially the standard shell, and those replacements would have to take adequate licensing.
15. ^ ^{a b} Brian Fox (forwarded by Leonard H. Belfry Jr.) (June 8, 1989). "Fustigate is in beta release!". Newsgroup: gnu.announce. Archived from the original on May four, 2013. Retrieved October 28, 2010.
16. ^ ^{a b} Warren, Tom (June iv, 2019). "Apple replaces fustigate with zsh as the default shell in macOS Catalina". The Verge. Archived from the original on June 10, 2019. Retrieved June xiii, 2019.
17. ^ "How to install Bash shell control-line tool on Windows 10". September 28, 2016. Archived from the original on Nov 20, 2016. Retrieved Nov 20, 2016.
18. ^ "User Environment Feature Changes". Oracle. Archived from the original on June 12, 2018. Retrieved June 8, 2018.
19. ^ ^{a b} Hughes, Matthew (June iv, 2019). "Why does macOS Catalina utilize Zsh instead of Fustigate? Licensing". The Next Spider web. Archived from the original on December 31, 2020. Retrieved January 12, 2021.
20. ^ "I Almost Get a Linux Editor and Compiler". Dr. Dobb's. Archived from the original on March 2, 2021. Retrieved September 12, 2020.
21. ^ Richard Stallman (Nov 12, 2010). "Near the GNU Project". Free Software Foundation. Archived from the original on April 24, 2011. Retrieved March xiii, 2011. "Bourne Once again Shell" is a play on the name Bourne Shell, which was the usual beat on Unix.
22. ^ Gattol, Markus (March thirteen, 2011), Bourne-once more Shell, archived from the original on March 9, 2011, retrieved March 13, 2011, The name is a pun on the proper name of the Bourne shell (sh), an early and important Unix shell written by Stephen Bourne and distributed with Version vii Unix circa 1978, and the concept of being "built-in again".
23. ^ Chazelas, Stephane (October four, 2014). "oss-sec mailing listing athenaeum". Seclists.org. Archived from the original on October 6, 2014. Retrieved Oct four, 2014.
24. ^ Leyden, John (September 24, 2014). "Patch Bash NOW: 'Beat Stupor' problems blasts OS X, Linux systems wide open up". The Register. Archived from the original on October sixteen, 2014. Retrieved September 25, 2014.
25. ^ Perlroth, Nicole (September 25, 2014). "Security Experts Await 'Shellshock' Software Issues in Bash to Exist Significant". The New York Times. Archived from the original on April five, 2019. Retrieved September 25, 2014.
26. ^ Seltzer, Larry (September 29, 2014). "Shellshock makes Heartbleed look insignificant". ZDNet. Archived from the original on May 14, 2016.
27. ^ Brian Fox (August 29, 1996), shell.c, Free Software Foundation, archived from the original on September 28, 2018, retrieved November 1, 2010, Birthdate: Sunday, January 10th, 1988. Initial author: Brian Play a trick on
28. ^ Richard Stallman (October 3, 2010). "Virtually the GNU Project". Free Software Foundation. Archived from the original on April 24, 2011. Retrieved March 21, 2011. Gratis Software Foundation employees have written and maintained a number of GNU software packages. Two notable ones are the C library and the shell. … We funded evolution of these programs considering the GNU Projection was not simply about tools or a development environment. Our goal was a complete operating arrangement, and these programs were needed for that goal.
29. ^ len (g...@prep.ai.mit.edu) (April 20, 1993). "January 1993 GNU'southward Bulletin". Newsgroup: gnu.denote. Usenet: gnusenet930421bulletin@prep.ai.mit.edu. Archived from the original on March ii, 2021. Retrieved October 28, 2010.
30. ^ Ramey, Chet (August i, 1994). "Bash - the GNU shell (Reflections and Lessons Learned)". Linux Periodical. Archived from the original on December 5, 2008. Retrieved November xiii, 2008.
31. ^ Chet Ramey (Oct 31, 2010), Dates in your Computerworld interview, archived from the original on July xx, 2012, retrieved October 31, 2010
32. ^ Chet Ramey (June 12, 1989). "Bash 0.99 fixes & improvements". Newsgroup: gnu.bash.issues. Archived from the original on Nov 10, 2012. Retrieved November 1, 2010.
33. ^ Chet Ramey (July 24, 1989). "Some bash-ane.02 fixes". Newsgroup: gnu.bash.bug. Archived from the original on November x, 2012. Retrieved October xxx, 2010.
34. ^ Brian Fox (March 2, 1990). "Availability of bash one.05". Newsgroup: gnu.bash.bug. Archived from the original on November 10, 2012. Retrieved October 30, 2010.
35. ^ Bresnahan, Christine; Blum, Richard (Apr 2015). CompTIA Linux+ Powered past Linux Professional Establish Report Guide: Exam LX0-103 and Test LX0-104 (3rd ed.). John Wiley & Sons, Inc. p. 5. ISBN978-1-119-02122-three. Archived from the original on March 2, 2021. Retrieved June 6, 2016. In Linux, most users run bash considering information technology is the about popular beat.
36. ^ Danesh, Arman; Jang, Michael (February 2006). Mastering Linux. John Wiley & Sons, Inc. p. 363. ISBN978-0-7821-5277-7. Archived from the original on March 2, 2021. Retrieved June 6, 2016. The Bourne Over again Shell (fustigate) is the most mutual beat out installed with Linux distributions.
37. ^ Foster-Johnson, Eric; Welch, John C.; Anderson, Micah (Apr 2005). Starting time Shell Scripting. John Wiley & Sons, Inc. p. 6. ISBN978-0-7645-9791-6. Archived from the original on March 2, 2021. Retrieved June 6, 2016. Bash is by far the most pop vanquish and forms the default shell on Linux and Mac OSX systems.
38. ^ "Utilize zsh every bit the default crush on your Mac - Apple tree Support". Archived from the original on December two, 2019. Retrieved July ane, 2019.
39. ^ "Installing the new GNV packages". Archived from the original on Oct 3, 2020. Retrieved September iv, 2020.
40. ^ "Compatibility Subsystems". Archived from the original on September 23, 2020. Retrieved September 4, 2020.
41. ^ Juliana, Cino (June 10, 2017). "Linux bash leave status and how to set exit condition in bash - Techolac". Archived from the original on June 21, 2019. Retrieved June 21, 2019.
42. ^ Huzaifa Sidhpurwala (September 24, 2014). "Bash specially-crafted surround variables code injection assail". Cherry Chapeau. Archived from the original on September 25, 2014. Retrieved September 25, 2014.
43. ^ "Fustigate Reference Manual". www.gnu.org. Archived from the original on March xv, 2018. Retrieved March 27, 2018.
44. ^ "Debugging Fustigate scripts". tldp.org. Archived from the original on Nov iv, 2018. Retrieved Nov 20, 2018.
45. ^ "Fustigate changes [Bash Hackers Wiki (DEV 20200708T2203)]". wiki-dev.bash-hackers.org. Archived from the original on September 23, 2019. Retrieved September 23, 2019.
46. ^ "Bash Reference Manual". www.gnu.org. Archived from the original on September xv, 2019. Retrieved September 15, 2019.
47. ^ "Working more productively with bash 2.ten/3.10". www.caliban.org. Archived from the original on June 29, 2018. Retrieved June 21, 2018.
48. ^ "six.xi Bash POSIX Mode", The GNU Bash Reference Manual, for Bash, Version four.one, Dec 23, 2009, archived from the original on Dec 3, 2010, retrieved October 26, 2010
49. ^ "Advanced Bash-Scripting Guide". world wide web.tldp.org. Section 37.2 (Bash, version 3). Archived from the original on May 5, 2017. Retrieved March five, 2017.
50. ^ "Bash, version four". tldp.org. Archived from the original on July i, 2018. Retrieved June 25, 2018.
51. ^ "Arrays (Bash Reference Manual)". www.gnu.org. Archived from the original on July xi, 2018. Retrieved July 4, 2018.
52. ^ "macos - Update bash to version 4.0 on OSX". Ask Different. Archived from the original on June 25, 2018. Retrieved June 25, 2018.
53. ^ ^{a b} Mendel Cooper. "Portability Issues". The Linux Documentation Project. ibiblio.org. Archived from the original on January 27, 2012. Retrieved January 26, 2012.
54. ^ ^{a b} "x. Files". Debian Policy Manual v4.5.0.2. Archived from the original on May 12, 2020. Retrieved May 11, 2020.
55. ^ "How To Format Date And Time In Linux, MacOS, And Bash?". Crush Tips!. Archived from the original on June three, 2020. Retrieved June iii, 2020.
56. ^ checkbashisms(1)  – Linux General Commands Transmission
57. ^ shellcheck(i)  – Linux General Commands Manual
58. ^ "Portable Shell". Autoconf. Archived from the original on March 2, 2021. Retrieved January 20, 2020.
59. ^ "Bash Assistance - A Bash Tutorial". Hypexr.org. October 5, 2012. Archived from the original on March 2, 2021. Retrieved July 21, 2013.
60. ^ "Fustigate Reference Manual". world wide web.gnu.org. Archived from the original on March fifteen, 2018. Retrieved March 27, 2018.
61. ^ bashbug(ane) Archived October 2, 2018, at the Wayback Motorcar, die.net
62. ^ "Linux / Unix Command: bashbug" Archived Oct 6, 2014, at the Wayback Machine, apple tree.com
63. ^ "Fustigate Reference Manual". tiswww.case.edu.
64. ^ "Working more than productively with bash 2.x/3.10". www.caliban.org. Archived from the original on June 29, 2018. Retrieved June 21, 2018.
65. ^ "Index of /gnu/bash". ftp.swin.edu.au. Archived from the original on March 8, 2020. Retrieved September 15, 2019.
66. ^ ^{a b} "An Introduction to Programmable Completion". tldp.org . Retrieved January 21, 2022.
67. ^ "github version history NEWS v5.0". GitHub. Archived from the original on September 10, 2020. Retrieved March 1, 2021.
68. ^ "Bash changes [Bash Hackers Wiki]". Archived from the original on March xviii, 2020. Retrieved Nov 25, 2019.
69. ^ "Fustigate-five.0 release available". lists.gnu.org. Archived from the original on November viii, 2020. Retrieved March i, 2021.

External links [edit]

Wikimedia Commons has media related to Bash.

• Official website
• Hamilton, Naomi (May 30, 2008). "The A-Z of Programming Languages: Bash/Bourne-Again Shell". Computerworld. Archived from the original on Nov 8, 2016. (interview with GNU Fustigate's maintainer, Chet Ramey)

rossoneustred.blogspot.com

Source: https://en.wikipedia.org/wiki/Bash_%28Unix_shell%29

Share this post