query: Why is "&" necessary to make a Unix fork bomb work?
positive_passages.docid: 146596
positive_passages.text: Why do these bash fork bombs work differently and what is the significance of & in it?
negative_passages.docid: 154604
negative_passages.text: Why is there a /bin/echo and why would I want to use it?
negative_passages.docid: 132222
negative_passages.text: Why does /bin/sh behave differently to /bin/bash even if one points to the other?
negative_passages.docid: 25478
negative_passages.text: What does ${1+"$@"} mean in a shell script, and how does it differ from "$@"?
negative_passages.docid: 107557
negative_passages.text: Shell usage of ":-" and advantage
negative_passages.docid: 126498
negative_passages.text: What is the purpose of the : (colon) GNU Bash builtin?
negative_passages.docid: 132176
negative_passages.text: Precedence of && over ||
negative_passages.docid: 110165
negative_passages.text: What is "x && foo()"?
negative_passages.docid: 69775
negative_passages.text: Why redirect output to 2>&1 and 1>&2?
negative_passages.docid: 143705
negative_passages.text: How can I run multiple commands which have & in one command line?
negative_passages.docid: 96838
negative_passages.text: Is the behaviour of .* to include . and .. defined in LSB or POSIX or some other specification?
negative_passages.docid: 18316
negative_passages.text: Security implications of forgetting to quote a variable in bash/POSIX shells
negative_passages.docid: 87515
negative_passages.text: Why is '.' a hard link in Unix?
negative_passages.docid: 46218
negative_passages.text: is there an escape for '&' character in the command prompt?
negative_passages.docid: 154673
negative_passages.text: In the shell, what does " 2>&1 " mean?
negative_passages.docid: 104429
negative_passages.text: Using &&'s short-circuiting as an if statement?
negative_passages.docid: 53030
negative_passages.text: Why do processes I fork get systemd as their parent?