Hi,
i made experiments with shell variable IFS which can declare '=' to be white space. When i do
echo -n x"$IFS"x | od -c
i get
0000000 x \t \n x 0000005
(The 'x' are for better recognizing the gaps of blank characters.)
Contrary to my expectation, the shell loop "for" does not react on IFS:
IFS="$IFS"= echo -n x"$IFS"x | od -c for i in /dev/sr0=ubuntu-16.04.6-desktop-amd64.iso ; do echo "$i" ; done )
yields
0000000 x \t \n = x 0000006 /dev/sr0=ubuntu-16.04.6-desktop-amd64.iso
But with functions, built-in commands, and programs IFS would be a possible explanation for growisofs' behavior:
show_args() { for i in $@ ; do echo $i ; done; } show_args /dev/sr0=ubuntu-16.04.6-desktop-amd64.iso
/dev/sr0 ubuntu-16.04.6-desktop-amd64.iso
Without seeing the '=', growisofs will employ genisoimage.
-----------------------------------------------------------------------
So what do you get from
Have a nice day :)
Thomas
Hi,
i made experiments with shell variable IFS which can declare '=' to
be white space.
When i do
echo -n x"$IFS"x | od -c
i get
0000000 x \t \n x
0000005
(The 'x' are for better recognizing the gaps of blank characters.)
Contrary to my expectation, the shell loop "for" does not react on IFS:
IFS="$IFS"= ubuntu- 16.04.6- desktop- amd64.iso ; do echo "$i" ; done )
echo -n x"$IFS"x | od -c
for i in /dev/sr0=
yields
0000000 x \t \n = x sr0=ubuntu- 16.04.6- desktop- amd64.iso
0000006
/dev/
But with functions, built-in commands, and programs IFS would be a possible
explanation for growisofs' behavior:
show_args() { for i in $@ ; do echo $i ; done; } ubuntu- 16.04.6- desktop- amd64.iso
show_args /dev/sr0=
yields
/dev/sr0 16.04.6- desktop- amd64.iso
ubuntu-
Without seeing the '=', growisofs will employ genisoimage.
------- ------- ------- ------- ------- ------- ------- ------- ------- ------- -
So what do you get from
echo -n x"$IFS"x | od -c
Have a nice day :)
Thomas