There are a couple of different ways you can do this: Make the other script executable, add the #!/bin/bash line at the top, and the path where the file is to the $PATH environment variable. Then you can call it as a normal command; Or call it with the source command (alias is .), like … Read more
You need to add it to your ~/.profile or ~/.bashrc file. export PATH=”$PATH:/path/to/dir” Depending on what you’re doing, you also may want to symlink to binaries: cd /usr/bin sudo ln -s /path/to/binary binary-name Note that this will not automatically update your path for the remainder of the session. To do this, you should run: source … Read more
Using the Job Control of bash to send the process into the background: Ctrl+Z to stop (pause) the program and get back to the shell. bg to run it in the background. disown -h [job-spec] where [job-spec] is the job number (like %1 for the first running job; find about your number with the jobs … Read more
No need for basename, and especially no need for a subshell running pwd (which adds an extra, and expensive, fork operation); the shell can do this internally using parameter expansion: result=${PWD##*/} # to assign to a variable result=${result:-/} # to correct for the case where PWD=/ printf ‘%s\n’ “${PWD##*/}” # to print to stdout # … Read more
Your command does not work because the redirection is performed by your shell which does not have the permission to write to /root/test.out. The redirection of the output is not performed by sudo. There are multiple solutions: Run a shell with sudo and give the command to it by using the -c option: sudo sh … Read more
You can use Ctrl+U to clear up to the beginning. You can use Ctrl+W to delete just a word. You can also use Ctrl+C to cancel. If you want to keep the history, you can use Alt+Shift+# to make it a comment. Bash Emacs Editing Mode Cheat Sheet
Use “$@” to represent all the arguments: for var in “$@” do echo “$var” done This will iterate over each argument and print it out on a separate line. $@ behaves like $* except that when quoted the arguments are broken up properly if there are spaces in them: sh test.sh 1 2 ‘3 4’ … Read more
Very close to what you posted, actually. You can use something called Bash parameter expansion to accomplish this. To get the assigned value, or default if it’s missing: FOO=”${VARIABLE:-default}” # If variable not set or null, use default. # If VARIABLE was unset or null, it still is after this (no assignment done). Or to … Read more
Use “$@” instead of plain $@ if you actually wish your parameters to be passed the same. Observe: $ cat no_quotes.sh #!/bin/bash echo_args.sh $@ $ cat quotes.sh #!/bin/bash echo_args.sh “$@” $ cat echo_args.sh #!/bin/bash echo Received: $1 echo Received: $2 echo Received: $3 echo Received: $4 $ ./no_quotes.sh first second Received: first Received: second Received: … Read more
Using variables in if statements if [ “$x” = “valid” ]; then echo “x has the value ‘valid'” fi If you want to do something when they don’t match, replace = with !=. You can read more about string operations and arithmetic operations in their respective documentation. Why do we use quotes around $x? You … Read more