Posted by jpluimers on 2020/09/07
For a simple comma separated list (no quotes), I was expecting a sed script (and indeed it is possible), but tr is more elegant:
Use
trto change , into newlines:
tr , "\n" < list.txt
Source: [WayBack] bash – convert comma separated values into a list of values using shell script – Stack Overflow.
–jeroen
Posted in *nix, *nix-tools, bash, bash, Development, Power User, Scripting, Software Development | Leave a Comment »
Posted by jpluimers on 2020/08/21
find . -type f -name '\.*' -printMust work if you want list every hidden file down in the directory hierarchy.
This sort of works on Linux, but fails on VMware ESXi (on Linux it only works when applying -maxdepth 1, deeper levels fails because they list all files where the top directory starts with a .):
If you want hidden files and hidden directories, without . and .. :find -regex '\./\..+' -print
This works on both Linux and VMware ESXi:
If you want hidden files and hidden directories, without . and .. :
find . \( -type f -o -type d \) -name '\.*' -print
Based on:
–jeroen
Posted in *nix, *nix-tools, bash, bash, Development, Power User, Scripting, Software Development | Leave a Comment »
Posted by jpluimers on 2020/07/09
Various ways are explained at [WayBack] linux – How do I use sudo to redirect output to a location I don’t have permission to write to? – Stack Overflow.
Some are for simple commands and can be a one liner (for instance using tee, or executing a secondary shell).
Others are more suited for longer command sequences.
–jeroen
Posted in *nix, *nix-tools, bash, bash, Development, Power User, Scripting, Software Development | Leave a Comment »
Posted by jpluimers on 2020/06/17
Cool: you can return strings both as a function result, and by reference: they are explained in the question, second and fourth answer of [WayBack] How to return a string value from a Bash function – Stack Overflow.
Returning them by reference has two important benefits:
echo (normally used to return a result) for debugging purposesI also needed a bit of switch magic which I found at [WayBack] bash – Switch case with fallthrough? – Stack Overflow and array magic (from [WayBack] Array variables) as arrays are far more readable than indirection (on the why not, see [WayBack] BashFAQ/006 – Greg’s Wiki: How can I use variable variables (indirect variables, pointers, references) or associative arrays?).
So here is a function that returns a specific IPv4 octet.
function getIpv4Octet() {
IPv4=$1
octetIndex=$2
outputVariable=$3
slice="${IPv4}"
count=1
while [ "${count}" -le 4 ]
do
octet[${count}]="${slice%%.*}"
slice="${slice#*.}"
count=$((count+1))
done
case "${octetIndex}" in
"1" | "2" | "3" | "4")
;;
*)
octetIndex="4"
;;
esac
eval $outputVariable="${octet[$octetIndex]}"
}
You call it like this:
$ getIpv4Octet "192.168.178.32" 3 result && echo ${result}
178
–jeroen
Posted in *nix, *nix-tools, bash, bash, Development, Power User, Scripting, Software Development | Leave a Comment »
Posted by jpluimers on 2020/06/16
I needed to enumerate all the parameters to a function and access many of them by index in the same function, so thanks to both these:
I got at this:
declare -a arguments=("$@")
for index in ${!arguments[@]}; do
echo $index/${#arguments[@]}:${arguments[$index]}
done
These are all forms of Array handling or Shell Parameter Expansion with special cases for array variables:
! does indirection, in this case from the array to the index of the array# gets the lengt of the parameter (for arrays: the number of elements)[] acccesse an array variable using an indexVia:
–jeroen
Posted in *nix, *nix-tools, bash, bash, Development, Power User, Scripting, Software Development | Leave a Comment »
