I have the following code:
#!/bin/bash
FSTAB=` grep -vE "^#|swap|UUID" /etc/fstab | awk '{print $1,$2,$3}'`
for i in $FSTAB
do
echo "$i"
done
return this:
/dev/mapper/centos-root
/
xfs
/dev/sdb2
/hdos
xfs
The problem is that later I want to compare it, so I am returning it with line breaks and I want it to be returned in a single line without jumps, that is to say:
/dev/mapper/centos-root / xfs
/dev/sdb2 /hdos xfs
Your entire variable assignment command chain there can be done in one awk rather than piping grep's output into awk:
FSTAB=` grep -v "^#" /etc/fstab | grep . | grep -v "swap" | grep -v "UUID" | awk '{print $1,$2,$3}'`
can instead be
FSTAB="$(awk 'NF && $0 !~ /^#|swap|UUID/ {print $1, $2, $3}' /etc/fstab)"
Newlines will be embedded in the variable, so you don't need to loop anything, you can simply echo "$FSTAB".
However, rather than parsing /etc/fstab into a variable and then parsing that, it would probably be better to parse /etc/fstab directly with a more involved awk script that does exactly what you need to with the output you're currently scraping from it.
Regardless of how you fill the FSTAB variable, the unquoted expansion of it in the for loop removes the distinction between different kinds of white space. (See: When is double-quoting necessary? and Why does my shell script choke on whitespace or other special characters?)
To work around that, either set IFS to split only on newlines, or loop over the lines with a while read loop:
$ fstab=$(grep /etc/fstab ...)
$ while IFS= read -r line; do
printf "$line\n"
done <<< "$fstab"
You could also use while read -r dev mnt fs; do ... if you wanted the fields in separate variables.
