Posix

tutorials
https://ryanstutorials.net/bash-scripting-tutorial/bash-if-statements.php
 * https://github.com/oilshell/oil and https://www.oilshell.org/cross-ref.html#oil-language bjourn shell replacement
 * https://www.grymoire.com/Unix/
 * https://github.com/alebcay/awesome-shell
 * https://github.com/dylanaraps/pure-bash-bible The goal of this book is to document commonly-known and lesser-known methods of doing various tasks using only built-in bash features. Using the snippets from this bible can help remove unneeded dependencies from scripts and in most cases make them faster. I came across these tips and discovered a few while developing neofetch, pxltrm and other smaller projects.
 * Mt xia scripts
 * http://mywiki.wooledge.org/BashFAQ/055, http://wiki.bash-hackers.org/scripting/copydescriptor redirecting 2>&1
 * http://wiki.bash-hackers.org/scripting/tutoriallist?s[]=links
 * http://guide.bash.academy
 * http://wiki.bash-hackers.org
 * http://www.gnu.org/software/bash/manual/bashref.html redirecting input, output piping section 3.6
 * http://sourcemage.org/Sorcery/Book shell style guide, a clone of Linuxfromscratch.com
 * http://www.codebind.com/linux-tutorials/bash-shell-scripting-statement-fi-else-fi-elif-else-fi/ if then else

http://tldp.org/LDP/abs/html/complexfunct.html

https://www.dartmouth.edu/~rc/classes/ksh/print_pages.shtml

https://sipb.mit.edu/doc/safe-shell/

http://www.davidpashley.com/articles/writing-robust-shell-scripts/

https://www.turnkeylinux.org/blog/shell-error-handling

https://www.cons.org/cracauer/sigint.html

startup files
http://www.linuxfromscratch.org/blfs/view/8.1/postlfs/profile.html see Linuxfromscratch.com

chmod
chmod -R a-x+X,u-x+rwX,go-wx+rX /home/j/cv2 remove execute permissions from a folder

https://unix.stackexchange.com/questions/399483/setting-an-ntfs-file-to-be-read-only-from-linux

https://askubuntu.com/questions/251206/mount-usb-drive-with-write-permissions-for-everyone-or-specific-user mounting for rw

ntfsfix /dev/sda2

commandlinefu
https://www.commandlinefu.com/commands/view/13324/sniff-network-traffic-on-a-given-interface-and-displays-the-ip-addresses-of-the-machines-communicating-with-the-current-host-one-ip-per-line


 * http://www.commandlinefu.com/commands/browse/25
 * http://www.commandlinefu.com/commands/view/19641/dd-with-progress-bar-and-statistics#comment
 * python -m SimpleHTTPServer #serve current directory at  http://localhost:8000
 * sudo e2fsck -y /dev/ recover partition

sh
https://sites.google.com/site/jdisnard/path-dupes remove duplicate paths. http://unix.stackexchange.com/questions/40749/remove-duplicate-path-entries-with-awk-command
 * https://stackoverflow.com/questions/793858/how-to-mkdir-only-if-a-dir-does-not-already-exist?rq=1 create directory.
 * https://stackoverflow.com/questions/8748831/when-do-we-need-curly-braces-in-variables-using-bash Curly braces.


 * http://www.tldp.org/LDP/abs/abs-guide.pdf 900 page guide
 * https://linuxacademy.com/blog/linux/conditions-in-bash-scripting-if-statements/ file conditions etc.
 * http://www.tutorialspoint.com/unix_commands/sh.htm
 * https://www.macs.hw.ac.uk/~hwloidl/Courses/LinuxIntro/x945.html
 * https://opensource.com/article/17/6/bash-parameter-expansion parameter expansion
 * Grep

if conditionals
https://unix.stackexchange.com/questions/270591/are-and-used-for-arithmetic-expressions-or-conditiona

t's very simple. You just have to understand [], and () as completely different beasts.

[ expression ] is just an invocation of a program [ (just a different name for test) and takes the expression as arguments, just like for all command calls in bash. That means, you must use whitespace between arguments, especially after [ and before ], and keywords and special characters have to be escaped or quoted, and variables are expanded in the usual way.

Within the expression, -gt, -lt and related are used for numerical comparison, while >, < and the sort, are for string comparisons. Think of [ as nothing to do with bash, just calling a command that evaluates expressions and returns 0 (true) or non-zero (false), as all programs do.

Boolean operators && and || can't be used in there, because they get interpreted by bash and not passed to test as arguments. -a and -o are used instead. But you can always do [ test1 ] && [ test2 ] || [ test3 ], which are 3 test invocations, combined by bash's usual boolean operators (that is, if first fails, the second is skipped).

Note that bash still comes with its own implementation of [ (builtin), but that doesn't change the way it's treated syntactically.

and are not builtin replacements for commands, but parts of a special syntax, so different rules apply. See man page for details on how variable names are wildcards are treated there. Boolean operators && and || have the usual meaning.

The  one is string-centered: all comparsions are for strings (but are more "modern", locale-aware than in [, although test could be platform-dependent). It handles also file tests, regex and so on.

The is for arithmetic expressions. Variable names don't require $ there, and you can mostly just write mathematical expressions in there - that of course includes comparisons (which are numerical). Comparisons in this case are no different from any other arithmetic expression, true is 1, false is 0, and you can write stuff like (( x=y*(z>4) )). If used in a conditional expression, nonzero is true and zero is false. You can also capture the result as $.

So:

string conditionals, pattern matching and file tests arithmetic expressions and conditionals [ ] test command: handles both, special nonstandard syntax for boolean operators and comparison operators

Forums

 * http://www.unix.com/shell-programming-and-scripting/170808-bash-clearing-value-variable.html
 * http://www.unix.com/
 * https://www.dwheeler.com/essays/filenames-in-shell.html

Unix stackexchange
https://unix.stackexchange.com/questions/23271/pipes-vs-process-substitution?rq=1

functions

 * https://stackoverflow.com/questions/64786/error-handling-in-bash/185900#185900
 * https://ubuntuforums.org/showthread.php?t=664657 store functions in separate file.
 * http://redsymbol.net/articles/bash-exit-traps/ exit traps
 * https://github.com/parallella/parallella-flash/blob/master/common.sh
 * https://github.com/parallella/parallella-flash/blob/master/linux/linux-flash.sh

http://www.codegist.net/code/bash-execute-gist/

youtube
https://www.youtube.com/watch?v=xC5NKqXmdUo Record All Screen Output to File - BASH -Linux 4,678 views

cat
https://stackoverflow.com/questions/2500436/how-does-cat-eof-work-in-bash

links
http://www.linux-mag.com/
 * Linuxfromscratch.com
 * LinuxNotes, ShellCommands Mesh networking shell commands
 * Gcc compiler

http://www.linux-mag.com/id/8797/